Weird Behavior Caused by abbreviation_scale

Hi,
I don't know if this is an issue/bug or is intentional, but here is an example of a weird behavior:
>>> affinegap.affineGapDistance("TED A", "TD A",
+       matchWeight = 0, spaceWeight = 2, gapWeight = 10,
+       abbreviation_scale = 0.125)
12.0 # Correct. Open a gap and insert a space for "E".

>>> affinegap.affineGapDistance("TESD A", "TD A",
+       matchWeight = 0, spaceWeight = 2, gapWeight = 10,
+       abbreviation_scale = 0.125)
14.0 # Correct. Continue the gap and insert a space for "S".

>>> affinegap.affineGapDistance("TESTD A", "TD A",
+       matchWeight = 0, spaceWeight = 2, gapWeight = 10,
+       abbreviation_scale = 0.125)
16.0 # Correct. Continue the gap and insert a space for "T".

>>> affinegap.affineGapDistance("TESTED A", "TD A",
+       matchWeight = 0, spaceWeight = 2, gapWeight = 10,
+       abbreviation_scale = 0.125)
16.25 # Weird.
      # This is because the second "E" is at position 5, which is greater
      # than the length of the second string.
      # So the score for the additional space for "E" is scaled.

I believe it is triggered by https://github.com/dedupeio/affinegap/blob/853f3d3d02d9a9adc1ec92dd9448949f51748e87/affinegap/affinegap.pyx#L79 by accident.
It would be great if you could take a look. Thanks.

I'm not super familiar with the algorithm, sorry. Can you explain a little more? What is the expected match pattern?
1:
TESTED A
TxxxxD A

or 2:
TESTED A
yyyTzD A

and can you explain how you think it's calculating that 16.25?


 The following package is imported correctly:

import "github.com/jroimartin/proxy"

And, as expected, the following error is reported by flymake:
compiler [BrokenImport]: could not import github.com/jroimartin/proxy (no required module provides package "github.com/jroimartin/proxy")

go mod tidy
As expected, the flymake error goes away
Delete the import github.com/jroimartin/proxy
Save the file
The package is not imported again

What did you expect to see?
After saving the file, the package github.com/jroimartin/proxy should be imported again.
What did you see instead?
No package is imported.
Editor and settings
Editor: GNU Emacs 28.2
LSP client: eglot 1.15
Relevant init.el snippet:
(add-hook 'go-mode-hook
	  #'(lambda ()
	      (eglot-ensure)
	      (add-hook 'before-save-hook
			#'(lambda ()
			    (call-interactively #'eglot-code-action-organize-imports))
			nil
			t)
	      (add-hook 'before-save-hook #'eglot-format-buffer nil t)))

;; Look for the nearest parent go.mod file as the project root
(defun jrm-project-find-go-module (dir)
  (when-let ((root (locate-dominating-file dir "go.mod")))
    (cons 'go-module root)))

(cl-defmethod project-root ((project (head go-module)))
  (cdr project))

(add-hook 'project-find-functions #'jrm-project-find-go-module)

Logs
I'm not sure if it is related, but the following error caught my attention:
	  (:type 3 :message "2023/08/28 20:09:39 background refresh finished after 16.488675ms: empty GOPATH\n"))

Extra info
If I do M-x eglot and tell it to restart gopls, the "organize imports" functionality starts working again.

Thanks for the issue, and the repro. We will take a look.

This doesn't seem to reproduce any more, at least in vscode. Is it still an issue, or could it be closed?

@pjweinb I believe this is related to emacs support of didChangeWatchedFile. I am curious if it still reproduces, with the recent changes to goimports.
@adonovan would you be able to do a quick test in eglot?

I just tried this with GNU Emacs 29.3 and eglot-1.17.  Here's what I saw:

go mod init github.com/jroimartin/goplsissue
Create a file main.go with the following contents:...
Save the file. The following package is imported correctly:
import "github.com/jroimartin/proxy"

At this point, the import that was added in my case was a different one: "github.com/docker/go-connections/proxy".
I assume that's because the imports algorithm uses my GOMODCACHE state as an input, and no two users' caches are alike. So I ran go get github.com/jroimartin/proxy and then deleted the newly added require line in the go.mod, and tried again, and this time the jroimartin/proxy package was imported, as expected.

And, as expected, the following error is reported by flymake:
compiler [BrokenImport]: could not import github.com/jroimartin/proxy (no required module provides package "github.com/jroimartin/proxy")

The flymake error I saw here actually related to the previous docker package, even though the source code no longer mentions it. (There's a metadata inconsistency somewhere.) Only after deleting the import and saving, so that organize-imports ran again, did the import and the error message become consistent about the jroimartin package.

go mod tidy

(To be clear, I ran this on the shell, not through gopls from the go.mod file.)

As expected, the flymake error goes away

No, I still see the error. Another inconsistency.

Delete the import github.com/jroimartin/proxy
Save the file
The package is not imported again

No, the package was imported again, and this time without error.
Unfortunately I think there are at least two bugs here.

@adonovan are you getting didChangeWatchedFiles notifications? If not, I think that explains the inconsistency. Gopls is not notified of the go.mod change, and therefore does not reload.
Deleting and reimporting causes a reload, which is why the error goes away the second time.

Closing this specific issue as unactionable, though some team members who use eglot are hoping to work on improving the status quo here in #67529.

I know pretty much nothing about the eglot internals, but why can't we make eglot/go-mode watch go.mod?

I know pretty much nothing about the eglot internals, but why can't we make eglot/go-mode watch go.mod? This bug is an Emacs quirk. We can just fix it in Emacs, right?

Exactly. The server gopls tells the client eglot which files to watch, and I think that set includes go.mod, but for some reason it does not seem to be taking effect.


feat: support new active-active databases

Adds support for managing active-active subscriptions, databases, regions, and VPC peerings.
Brings together the work from @greg-oc, @pvegh-oc, and @byron-oc.
Need to merge https://github.com/RedisLabs/rediscloud-go-api/pull/94, then retag and update the go.mod file before this PR can be merged

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.4 out of 5 committers have signed the CLA.:white_check_mark: greg-oc:white_check_mark: pvegh-oc:white_check_mark: danielarbiv:white_check_mark: bengesoff:x: noham14You have signed the CLA already but the status is still pending? Let us recheck it.


Assertion failed

Any way to fix?

I would try building osiris again

if that doesn't work i would wait for Daniel to help you.

Have you made any modifications to the source code?


[Android]timestamp in gesture event different from iOS

Two problems:

Android is using 'timeStamp' while iOS is using 'timestamp'; (Seems an old issue)
Android is using nano seconds while iOS is using milliseconds.(Brought in by this commit)

Those problems force us to check the platform when using the timestamp, which could be avoided.

It would be awesome if you can send a PR by changing both to timeStamp and fix android to use milliseconds.

The timestamp accuracy will be fixed with this pull request https://github.com/facebook/react-native/pull/8199
Is anyone working on renaming 'timestamp' to  'timeStamp' in iOS already?

@0rland0 There was a PR, but I don't think it's active. Send a new PR please :)

Ok I will try to do that.
@ldn0x7dc Would it be possible to upload the code where you used the gesture so I can directly test on that?

Does this issue really still exist? I just tried it out with the PanResponderExample which uses touch events. On Android AND iOS I could access the timestamp of the touch event with
e.timeStamp. Calling e.timestamp gave me on both platforms an 'undefined'.
I tested it with setting a breakpoint in different methods in the PanResponderExample e.g. in th _handlePanResponderMove method.

@0rland0
I've just tested with RN 0.28 and on android it's 'timeStamp' while on iOS it's 'timestamp'.
You can check file TouchesHelper, which assign 'timeStamp' to TIMESTAMP_KEY

The naming on Android has been changed to timestamp (iOS style) in this commit: https://github.com/facebook/react-native/commit/8aeeb4d6a06e4c3cb3e480bbad3f55f83b78a626
It's already on master.


Error on composer install

When installing by composer I get the following error
Symfony \ Component \ Debug \ Exception \ FatalThrowableError (E_ERROR)
Class 'Nova\Cron\CronServiceProvider' not found
Called: /var/ ....../vendor/nova-framework/system/src/Foundation/ProviderRepository.php

Sorry I haven't been keeping this up to date with the changes from the main framework. It's out of sync I'll update this in a few hours time.

This is now fixed.


google-japanese-input-np: Add version 2.25.3700.0

Google Japanese Input (homepage) (Wikipedia) is a Japanese input method (IME) published by Google.
Notes:

checkver: I couldn't find an official page that has the latest version number. Therefore I use a third-party website instead. Is this acceptable?

Thank you!


Toolkit UI is quite different from the screenshot

Step 3 implies that the user will see a simple Add capabilities page, but the actual page seen at this point is much different. Here's a screenshot:

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

ID: 8f876156-cc1e-468f-4647-5143a5de03b1
Version Independent ID: 618f43a3-3371-ad99-13aa-087b9303298c
Content: Get started - Build and run your first app - Teams
Content Source: msteams-platform/build-your-first-app/build-and-run.md
Product: msteams
GitHub Login: @heath-hamilton
Microsoft Alias: lajanuar

We are looking into the issue we will get back to you

Hi @Rick-Kirkham, the content page mentioned provides an overview for the Get started module. Please specify the doc link.

@v-rpatkur  You've changed the file and even the file names so much since I created this issue, that I don't know where the misleading text is now.

@surbhigupta12, need your assistance.

Hi,
The article is updated as an step-by-step guide. The step "Create project workspace for your tab app" allows the user to select a capability in the Teams Toolkit.

@v-ypalikila - Could you please close the issue if it is already fixed?


Create a FAQ section

What would that feature address
It is no possible for the users to find quick solutions to frequently met issues.
Description of the ideal solution
Create a FAQ with a troubleshooting section.
Caveats
This FAQ section should share solid bounds with the documentation and be regularly updated with users feedbacks.
Acceptance Criteria

[ ] Ensure new code is unit tested, and check code coverage is at least 90%
[ ] Propagate any change on the demos and run all of them to ensure there is no breaking change
[ ] Ensure any change is well documented

Florian J can provide some.
Put in Website.

1 - When running a Taipy GUI application, why do we have a warning :
 * Server starting on http://<IP_ADDRESS>:5000
 * Serving Flask app 'Taipy' (lazy loading)
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: on
 * Server starting on http://<IP_ADDRESS>:5000

It is normal. Taipy wants to make it easy to run the GUI when you are developing your app. The easiest way is to use a development server (provided by Flask). When it comes to deploy the application on a production environment, please refer to the doc to use a production server.

https://www.taipy.io/faq/

Plotfly usage (ploty-js)


Partially fix resolver_component_tests_runner test in gcc_musl portability suite

Partially fixes an error in gcc_musl portability test
Introduce a template from cxx_alpine_x64 docker image.

Original error:
+ test/cpp/naming/utils/dns_resolver.py -s <IP_ADDRESS> -p 22960 -n health-check-local-dns-server-is-alive.resolver-tests.grpctestingexp. -t 1
+ grep <IP_ADDRESS>
Traceback (most recent call last):
  File "test/cpp/naming/utils/dns_resolver.py", line 20, in <module>
    import twisted.internet.task as task
ImportError: No module named twisted.internet.task
+ RETRY=1
+ test/cpp/naming/utils/tcp_connect.py -s <IP_ADDRESS> -p 22960 -t 1
Traceback (most recent call last):
  File "test/cpp/naming/utils/tcp_connect.py", line 35, in <module>
    main()
  File "test/cpp/naming/utils/tcp_connect.py", line 32, in main
    socket.create_connection([args.server_host, args.server_port])
  File "/usr/lib/python2.7/socket.py", line 575, in create_connection
    raise err
socket.error: [Errno 111] Connection refused

https://sponge.corp.google.com/target?id=0c3336e8-0f8d-475c-94c6-d591d4aca246&target=github/grpc/cpp_linux_dbg_native_x64_gcc_musl&searchFor=&show=FAILED&sortBy=STATUS
The test still fails with:
+ echo 'FAILED TO START LOCAL DNS SERVER'
FAILED TO START LOCAL DNS SERVER
+ kill -SIGTERM 22544

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

LGTM for the added dependencies in that dockerfiel, but this test is not running per PR, correct? What runs this test?

Yes, the test is not running per PR.

@matt-kwong  I realized I also need an owner approval.


Update named_templates.md

Add space.

What this PR does / why we need it:
Special notes for your reviewer:
If applicable:

[x] this PR contains documentation
[ ] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

Add some spaces.

This was intended as part of the documentation. Please see the lines above and below the example.

The output will not be what we expect:

Note that the indentation on app_version is wrong in both places.


Create nixpkgs-help

nixos-help and using w3m like in the installation iso tty, is described in https://github.com/NixOS/nixpkgs/blob/d600f006643e074c2ef1d72e462e218b647a096c/nixos/modules/misc/documentation.nix
We should create commands for the other manuals as well and xref them in the manuals.
(fwiw, I tried to search for similar issues but the keywords didn't filter very far)
I probably wont get around to this for a while, so if anyone wants to pick it up that would be great.

See also https://discourse.nixos.org/t/does-something-like-nixos-help-exist-for-the-nix-or-nixpkgs-manuals/2705

If things can be properly rendered, it would also be good to render them as man pages and/or pdf.


Inconsistensy between Routing strategies

Build Information : Docker Build on Ubuntu 20.04
PDK Information : sky130A, variant - sky130_fd_sc_hd, typical op condition - tt_025C_1v80
I have observed the following error on two of my designs and on spi controller (raven_spi) from Raven-SOC.

The flow exits after track assignment begins when using routing strategies 0 through 3. I have used the inputs from tritonRoute.param file and have successfully ran TritonRoute on those independently. All the designs were successfully routed on routing strategy 14.
Screenshot of PDK_PDK_VARIANT_config.tcl used on raven_spi is attached below:

I am unsure where the problem is. Kindly look into it.
Thank you.

@diecaptain which version of open_pdks are you using/ could you share the tracks.info file? it should be copied into the run directory under tmp.

I am using the open_pdks 1.0 tag rc2. The tracks.info_copy file in tmp directory is the same as the tracks.info file generated by open_pdks. The copy file is as below:

Thank you.

@diecaptain Can you share all the logs under the run directory for any of the runs or can you share the (design, configurations) for us to replicate the error?

This is the whole directory of raven_spi that I ran. The code itself is from efabless's Raven SOC. The run directory has two runs, the old one is the successful run using Routing strategy 14. The new one is the failed run using Routing strategy 0 which i reran now. I cleaned the failed runs so I dont have their logs. It fails on routing strategies 0,1,2 and 3, but passes on 14.
raven_spi.tar.gz

@diecaptain I was unable to replicate the error you're facing. I ran with ROUTING_STRATEGY 0 and 1, using the openlane::rc2, and got a DRC/LVS/Antenna clean raven_spi run. However, looking at the logs you attached, I'm familiar with the pin access issue that is flagged in your tritonRoute log, as far as I've experienced, this happens when you use incompatible versions of skywater-pdk (newer) and open_pdks (older). So please make sure you checkout to the commits specified in the readme. TR14 works around this issue which is quite interesting.
If you insist on using the latest version of skywater-pdk then you might want to check this #23. It's still being tested tho.

Okay, thank you for your time. If I want to roll back my skywater-pdk version, which version is compatible with open_pdks 1.0 rc2? I didnt pay head to the pin access issue because after a few errors, it logs that 100% pin access was achieved. Right now, I have moved to steadily use TR14. However, while testing with the examples provided in openlane/designs, some of them do work for all routing strategies. It is also quite interesting to see that some designs give a clean run even with incompatible versions of skywater-pdk and open_pdks, that this issue is not uniform. Could you please guide me towards any documentation available on the differences between routing strategies 0 through 3 and 14? It would be a massive help to understand issues intuitively and come up with ideas.
Thank you very much for your time once again.

This is a documentation of all configuration parameters used in OpenLane: configuration/README.md.
However, in brief, from 0 to 3, this is a variant from TR13, and they are not really different "routing strategies", but different "routing optimization iterations". You can check the source code here to see the differences, which only show up in this function FlexDR::main() src.
As for routing strategy 14, that uses TR14, which is much more 0-DRC capable but it takes more time and consumes more memory, that's why we are keeping the TR13 variant as well.
You can try them all on your design using an exploration sweep as described in this file

Thank you.


Installation fails outright on macOS

Prerequisites

[N/A] I am running the latest version. (up upgrade)
[X] I searched to see if the issue already exists.
[N/A] I inspected the verbose debug output with the -v, --verbose flag.

Description
Installing from npm or curl|bash the script fails with a 404.

From the looks of it, the file downloads successfully but the checksum fails.
Steps to Reproduce
Try installing up if it isn't already  installed with any method involving that script. It ends up 404ing.
Love Up?
Please consider donating https://opencollective.com/apex-up/donate to help the project.
Just have a general question? Join us on Slack https://apex-dev.azurewebsites.net/

This is a workaround in case you can't wait.
curl -sfL https://gist.githubusercontent.com/quocnguyen/4fdb93be6049f2311c7be6d2eaf90238/raw/7b85022f0ac5ff5fa72b7a0b8d21e955396ff4c7/install.sh | sh


Convert children to JsArrays to work around react-id issue in dart2js

In dart2js-transpiled code, automatic List conversion of React children causes react-id attributes to contain lots of extraneous .$o:0:0:$_jsObject: parts, and bogs down rendering performance.
This PR eliminates that automatic conversion by always passing in JsArray, and resolves this issue.
@hleumas @todbachman-wf @trentgrover-wf @maxwellpeterson-wf

+1

+1
@hleumas please review


Add gfortran-13 to ubuntu:22.04

Description
The GCC 13 toolchain is missing gfortran-13.
This seems to be a recurring theme:

https://github.com/actions/runner-images/pull/2103
https://github.com/actions/runner-images/pull/6736

Related issue:
Check list

[ ] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

/azp run ubuntu2204

CI failure seems unreleated?

@haampie yep, not your fault. I'll rerun it later, when merged fix.

looks like you need rebase :)

I've rebased the two lines of change

How/when will this become available @mikhailkoliada ?

@haampie looking at the list of Ubuntu 22.04 PRs, there's a new image per every couple of days. (I am waiting for one myself, although not because of this issue; I am waiting for Chrome 119 that fixes some bugs breaking my builds)

@haampie this PR is what we both need. :) https://github.com/actions/runner-images/pull/8819


Increase main task stack on all-clusters-app for ESP32

Attempting to force commissioning mode causes a stack overflow.

Problem
stack overflows on all-clusters-app when attempting to force the device into commissioning mode.

Summary of Changes
Increases stack size - was previously 3584, now set to 4096.

Fixes #6823

@msandstedt @andy31415 @jepenven-silabs ?


TF Framework regularizers_test missing test case add

test_regularization_shared_layer
test_regularization_shared_model
test_regularization_shared_layer_in_different_models
test cases added

@fchollet
thanks for quick reiew, changes done as per comments, please review the new changes.

@Dayananda-V could you please resolve the conflicts? Thanks!

Closing this PR due to write perssion denied, same changes will be track with new PR #28542.


Ambiguous use of from

The library is great! Having one issue when I drag the RxBluetooth source code directly into my project. I get an error on every use of Observable.from, saying that use of from is ambiguous.
Any idea why this may be happening or how I can debug this?

Works great when I use Carthage

Hi there,
We have never tried to integrate it directly, so it may not work as it should at the moment. We'll check it tomorrow and let you know about the solution right away .
Thank you very much for feedback,

Hi,
Could you include sample project here? It would be very helpful. :-)

@AndrewSB @Kacper20 any update here?


Config changes to reflect the default branch from master to main. Please merge to complete the default branch renaming job.

Auto branch renaming content.

Docs Build status updates of commit 0c4a4eb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Private vs Public repos for connector instructors?

@anthonysuen, @papajohn : Do you know if the dsten organization has the capacity to offer private repositories for connector instructors?  Following the strategy of the core course, private repositories seem better suited for making exercises and the like available to other DS8 instructors without tempting students not to do their own work.
As an intermediate solution, instructors could host their own private repos for that purpose, but it seems more streamlined to have them here, particularly if the goal is to share with instructors while not being public to students.  Again the core course seems to have a very nice set-up where student-facing material goes on the gh-pages branch and becomes public, while assignments remain private on the repo master branch.  Of course, gh-pages might not be amenable to everyone.
Connector instructors: I'd be curious to hear thoughts of other connector instructors on how you have or plan to manage this aspect.  Would a private repository for the connector be helpful?

Yes, we can set up private repos. If individuals want their own, that's
fine with me, but I'd rather not pre-create one per instructor when most
won't use them. The fewer repos the better.
On Mon, Dec 14, 2015 at 9:55 AM, Carl Boettiger<EMAIL_ADDRESS>wrote:

@anthonysuen https://github.com/anthonysuen, @papajohn
https://github.com/papajohn : Do you know if the dsten organization has
the capacity to offer private repositories for connector instructors?
Following the strategy of the core course, private repositories seem better
suited for making exercises and the like available to other DS8 instructors
without tempting students not to do their own work.
As an intermediate solution, instructors could host their own private
repos for that purpose, but it seems more streamlined to have them here,
particularly if the goal is to share with instructors while not being
public to students. Again the core course seems to have a very nice set-up
where student-facing material goes on the gh-pages branch and becomes
public, while assignments remain private on the repo master branch. Of
course, gh-pages might not be amenable to everyone.
Connector instructors: I'd be curious to hear thoughts of other connector
instructors on how you have or plan to manage this aspect. Would a private
repository for the connector be helpful?
—
Reply to this email directly or view it on GitHub
https://github.com/dsten/connector-instructors/issues/2.

@papajohn Thanks.  It looks like @anthonysuen has already created a repo for many of the connectors; so I was just wondering if we'd discussed if those were most useful as public or private repos.
Having not-too-many repos in the org account certainly makes things cleaner.  I suppose connector repos could all be created in a separate org account if that's an option.
If we are getting lots of connector repos, we might want to have more discussion on naming convention for those repos?  The current names are reasonably semantic but might not scale.
Apologies if I'm rehashing discussions you've already had about how best to organize this (or if I'm just overthinking things).

These are great points @cboettig:

I do think by next semester we need to figure out how to deal with the ever growing list of repos. Not sure about the practices since I don't know many universities that runs on our foundational course, connector model.
Perhaps we could just make the all connector repos private? I am not sure having both a private and public repos for one connector make sense.
Naming conventions definitely make sense. Could I suggest we start with class titles like ESPM 88 with the complete name to follow?

Any additional thoughts @choldgraf

@cboettig can you make a fork of a repo private? I wonder if you could set up public connector repos on the dsten account. Then fork that, make it private, and use PRs to pull in updated content to the main class.

Alternatively you could just keep it public and assume that students won't go to visit it in general. Can't you look at repository traffic statistics for visits etc? Maybe you can use that to infer whether students are peeking

@anthonysuen My suggestions would be:

Name each connector repository with the course number, since those are registered, predictable and unique values that mean something to everyone.
Make connector repositories private by default.
If @papajohn & the other dsten foundation core team prefer keeping the dsten github org slim, then we should consider all connectors under a separate connector org.  (Of course, that would break the current import-notebook strategy, because connector gh-pages would no longer be under the data8.org domain name, see https://github.com/dsten/connector-instructors/blob/master/README.md )

@choldgraf @anthonysuen Re public and private, as I mention above there's no need for multiple repositories or forks to have both; we can do what the core course already does with https://github.com/dsten/text : the repo itself private, public information goes on the gh-pages branch where it is published as a public webpage automatically (at http://data8.org/.  Does that make sense?
(p.s. my course is ESPM 88B, we also have ESPM-88A.  If other departments end up with more than one connector, this may arise again).

I'm +1 for that to see how it goes. I doubt a ton of instructors will do all of this (at least this first round) so maybe it won't get too cluttered. If this becomes a success story for how to organize the connectors, then perhaps it'll be worth thinking about scaling that upwards at that point.

@choldgraf that makes sense to me to. Right, connector instructors will no doubt continue to do a wide variety of things (bcourses etc), and many might have no use for GitHub repos anyhow. @anthonysuen I think you were intending to create repos for instructors anyhow, if only to create communication channels via issues tracker?  Given that John is wary of having too many repos, maybe that strategy needs further discussion?

Sorry for the delay in responding. I think this raises a lot of interesting quetsions. Right now I am actually in the process of setting up connector web pages within the data8.org domain which might make long term migration to a seperate organization more difficult. The goal of the repos are not only for communication, but also to commit code and serve as the web infrastructure for the connector courses.

@anthonysuen I think we can work around the technical stuff if we know what we want, though I agree it makes things more complicated.
For instance, if John and others really would prefer connectors on a separate org, we can set that org up with CNAME connector.data8.org.  But yeah, I agree it's all simpler if connectors stay here but want to make sure we're all happy with that (particularly those having to admin the big picture).

We're going to go with defaulting to a private repo for connectors, but not until #9 gets implemented.
Until then, we're going to have one private repo and one public repo per connector. (Students pull from the public one.)

We could wait until a connector instructor actually requests a private one
before creating it, just to maintain a bit of order.
On Tue, Jan 19, 2016 at 9:32 PM, Sam Lau<EMAIL_ADDRESS>wrote:

We're going to go with defaulting to a private repo for connectors, but
not until #9 https://github.com/data-8/connector-instructors/issues/9
gets implemented.
Until then, we're going to have one private repo and one public repo per
connector. (Students pull from the public one.)
—
Reply to this email directly or view it on GitHub
https://github.com/data-8/connector-instructors/issues/2#issuecomment-173093319
.

Agreed.
ᐧ
On Tue, Jan 19, 2016 at 9:39 PM, John DeNero<EMAIL_ADDRESS>wrote:

We could wait until a connector instructor actually requests a private one
before creating it, just to maintain a bit of order.
On Tue, Jan 19, 2016 at 9:32 PM, Sam Lau<EMAIL_ADDRESS>wrote:

We're going to go with defaulting to a private repo for connectors, but
not until #9 https://github.com/data-8/connector-instructors/issues/9
gets implemented.
Until then, we're going to have one private repo and one public repo per
connector. (Students pull from the public one.)
—
Reply to this email directly or view it on GitHub
<
https://github.com/data-8/connector-instructors/issues/2#issuecomment-173093319
.

—
Reply to this email directly or view it on GitHub
https://github.com/data-8/connector-instructors/issues/2#issuecomment-173094031
.

--
Sam Lau
EECS | UC Berkeley | May 2017
(562) 565-4336 |<EMAIL_ADDRESS>

In which case, perhaps the docs should inform connector instructors that they will need to request a repository before they can follow the rest of the instructions (and specify who the point of contact is for that), otherwise we may have more confusion?
Likewise we should probably add something to the docs telling connector instructors that they will need to request a data8.berkeley.edu account as well?

That sounds like a good suggestion, FYI I've created an Issue for keeping track of common gotchas / problems / questions. Check out #10 and feel free to add any thoughts.


EES-4643 Minor tests cleanup to make them a bit clearer

use helper function capabilities
use backticks to reduce number of escaped chars
use zaptest to get logs in the failed tests output

+1

+1


Allow use of pygame with SDL2

Building with SDL2 forcibly disables pygame. I'd fix it but I'm not familiar with the packaging issue that required this.

Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

My suggestion would be to still keep them seaprate. Having them both compiled at the same time would lead to compilations issues with conflicting method signatures being present in both libsdl1.2 and libsdl2.
I'd suggest disabling sdl2 compilation if USE_SDL2=0 env var is set.

That has never been an issue for me on Linux. For example, I can use window_pygame with image_sdl2, or window_sdl2 with text_pygame with no issues.

This becomes a issue when packaged and frozen with a tool like pyinstaller which tends to get confused with these, effects the runtime of the package

kived on linux, so, but on other platform like OSX, you get a warning cause some symbol are declared twice in the binary, at 2 different location. Imagine the confusion when you want to use the IMG_Load, which one exactly, the one in SDL or SDL2 ? The binary don't make the difference, and can lead to crash :/

@kived i had problems when mixing pygame and sdl2 providers.
https://github.com/kivy/kivy/issues/2550

That's exactly what i'm describing. Exclusion is the only way to be safe.

After some more discussion on irc it seems @kived doesn't see the issue with packages as he manages his own packages just for debian. There does not seem to be a good way to use packagers like pyinstaller and keep both pygame and sdl2.
Please reopen if a solution can be found for this packaging issue.


feat(backend): 集群标准化新增业务模块导航与mysql单节点、主从集群列表汇总接口 #6593

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.v_xcngxu seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Add global Registry. Closes #2

Solves #2 by creating a global (singleton) Registry for Resources — something like how mongoose Schemas must be registered to Models. The changes are minimal but breaking.
Changes

When defining a Resource containing Ref or Refs, a name must be used instead of a direct reference to the linked resource.
Resources must be registered by calling Registry.add(name, resource).

Benefits

Allows for circular references (as in #2).
Allows for Resources to be defined in separate files that do not need to require each other.
Makes Resources available more easily: Registry.get() returns an array with a list of all the registered Resources; Registry.get(name) returns a reference to the Resource registered with name.

Example (the one in #2)
/**
 * models/thread.js
 */

import mongoose from 'mongoose';

const threadSchema = new mongoose.Schema({
  title: String,
  posts: [{
    type: mongoose.Schema.ObjectId,
    ref: 'Post'
  }]
});

export default mongoose.model('Thread', threadSchema);

/**
 * models/post.js
 */

import mongoose from 'mongoose';

const postSchema = new mongoose.Schema({
  body: String,
  thread: {
    type: mongoose.Schema.ObjectId,
    ref: 'Thread'
  }
});

export default mongoose.model('Post', postSchema);

/**
 * models/index.js
 */

import Thread from './thread';
import Post from './post';

export default { Thread, Post };

/**
 * resources/thread.js
 */

import { Registry, Resource, Property, Refs } from 'jsonapify';
import { Thread } from '../models';

const threadResource = new Resource(Thread, {
  type: 'threads',
  id: new Property('_id'),
  attributes: {
    title: new Property('title')
  },
  relationships: {
    posts: new Refs('Post', 'posts')
  }
});

Registry.add('Thread', threadResource);

export default threadResource;

/**
 * resources/post.js
 */

import { Registry, Resource, Property, Ref } from 'jsonapify';
import { Post } from '../models';

const postResource = new Resource(Post, {
  type: 'posts',
  id: new Property('_id'),
  attributes: {
    body: new Property('body')
  },
  relationships: {
    thread: new Ref('Thread', 'thread');
  }
});

Registry.add('Post', postResource);

export default postResource;

/**
 * resources/index.js
 */

// Not really needed, since they are on the `Registry` singleton...

import Thread from './thread';
import Post from './post';

export default { Thread, Post };

Tests and docs
Existing tests pass (with the appropriate modifications). I have not written any for Registry though. I also haven't touched the README file.

Thanks for your contribution!


Fix: Splitter handling offset.

Hi
There is an offset problem when moving the splitter bar beyond its limit position in parent. The offset of the pointer isn't calculated and gets visual displacement. The method _is_moving in the patch is a refactored version of the following example (that is only for the fist if branch in Splitter.strip_move):
if diff_y == 0:
    return
elif diff_y > 0:
    if sz_frm == 't' and touch.y <= self.top:
        return
    elif sz_frm == 'b' and touch.y <= self.y:
        return
elif diff_y < 0:
    if sz_frm == 't' and touch.y >= self.top:
        return True
    elif sz_frm == 'b' and touch.y >= self.y:
        return

Note this check don't keep pointer's on_touch_down position within the widget because that requires to add instance variables.

Can you give more details on what’s the offset issue? I only see a issue with your branch, master seems to work as expected when testing with running python kivy/uix/splitter.py

It's very specific to the splitter:

As it receives a delta It goes down and up ok because is always moving but when it goes down again the pointer don't visually reach the splitter bar to move it down which is the behavior I see in other frameworks in general:

ok, seems you fixed it only on vertical movement.

@smrg-lm nice work 👍

Thank you, I was rebasing and pushing but you solved it.


Allow setting custom certificates in Windows containers

Signed-off-by: Shubham Sharma<EMAIL_ADDRESS>Description
With the feature to add volume mounts using #4662, it is possible for users to mount a volume with custom certificates. On Linux containers, the SSL_CERT_DIR environment variable can be used to make the daprd sidecar trust these certificates. On Windows, we need to add a special entry-point script that adds these certificates to the root store.
With this PR, we make the following changes

In the Windows base Docker image, add the certoc utility and the certificate setup script to be able to add certs to the root store.
Add an entrypoint to run the setup script and accept args to cmd for running dapr.
This script looks for the env variable SSL_CERT_DIR and if present, it adds the certificates present in the directory point by the environment variable to the root store.
In pod_patch.go, we no longer use both Command and Args. Command in container spec translated to the Docker ENTRYPOINT, which we no longer override. The ENTRYPOINT is either explicitly specified (as for Windows), or the default is used (as for Linux). pod_patch.go passes Args to the ENTRYPOINT to invoke Dapr (or Delve).
Also, if SSL_CERT_DIR is set, pod_patch.go configures the Windows container to use the ContainerAdministrator user. This is required by certoc.exe to install certificates to the root store.

Issue reference
Please reference the issue this PR will close: #4587
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[X] Code compiles correctly
[ ] Created/updated tests
[ ] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: https://github.com/dapr/docs/issues/2570
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

@shubham1172 there's something happening on Windows and all apps fail to deploy :(

/ok-to-test

@shubham1172 i think I know why windows tests fail. It's because you modified the base containers and our E2E tests do not rebuild the base containers in every run (for perf reasons).
To test this PR, what you need to do is:

Build docker/Dockerfile-windows-base and push it to your own container registry (for example a public Docker hub)
TEMPORARILY change docker/Dockerfile-windows to point to your base image
Run the tests
When tests pass, revert change at point 2

By the way, do you think we should create an E2E test specifically for root cert injection?

From the logs:
{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:127,Signal:0,Reason:ContainerCannotRun,Message:container 2f63d3bb85ddfd03718dccd5a9b50e5afdaf1efcd978c4496964fe542b296ec0 encountered an error during hcsshim::System::CreateProcess: failure in a Windows system call: The system cannot find the file specified. (0x2),StartedAt:2022-06-25 12:45:11 +0000 UTC,FinishedAt:2022-06-25 12:45:11 +0000 UTC,ContainerID:docker://2f63d3bb85ddfd03718dccd5a9b50e5afdaf1efcd978c4496964fe542b296ec0,}
Makes sense, let me push the suggested temporary changes to this PR and try again.
For E2E test, do you suggest using the HTTP binding scenario? Also, can we track it separately from this PR?

Makes sense, let me push the suggested temporary changes to this PR and try again.

Thanks! Now that we have build-tools I can also look into automating this for future PRs. I'll do that on Monday.

For E2E test, do you suggest using the HTTP binding scenario?

I think that's fine. Perhaps:

Deploy an app that offers an HTTP server with a TLS cert signed by a custom CA.
This test would invoke the app directly (to get a baseline and make sure the root cert is injected)
Then it would try to invoke via HTTP binding to test another scenario.

Also, can we track it separately from this PR?

Of course.

/ok-to-test

Following @ItalyPaleAle's suggestion, the e2e test on Windows are now passing. I will revert the last commit to use the original Windows base image if this looks good to everyone. Note, we will probably have to manually trigger a windows-base image build once the PR is merged.
E2E test issue: #4835

Update: this PR has been targeted to release-1.8 now.

Why did you change command to args?
"AKS with virtual kubelet/ACI" doesn't work with this change.
https://github.com/dapr/dapr/commit/9822921a92ecfce8f271feeb3e9825bfda95e295#diff-877ab4b4bd43d88fc79f83e7a1cbe540f963a07cea4b571b16ef6303dc0bf2f1R744-R745

@itac-admin can you please provide more details? What's the error?

@ItalyPaleAle
The following error occurs when deploying with "aks with aci".

Events:
Type     Reason                Age                From                                   Message

Normal   Scheduled             10s                default-scheduler                      Successfully assigned backend-test/nginx-deployment-67f6b7c46-qvbnp to virtual-node-aci-linux
Warning  ProviderCreateFailed  4s (x10 over 10s)  virtual-node-aci-linux/pod-controller  ACI does not support providing args without specifying the command. Please supply both command and args to the pod spec.

daprd:
Image:       mcr.microsoft.com/daprio/daprd:1.8.4
Ports:       3500/TCP, 50001/TCP, 50002/TCP, 9090/TCP
Host Ports:  0/TCP, 0/TCP, 0/TCP, 0/TCP
Args:
/daprd
--mode
kubernetes

Thanks. I'm trying to connect with the ACI team and get their take on this too.

thank you.
I want to use the latest Dapr.

@itac-admin  can you confirm if you're using Windows or Linux containers?

@itac-admin to close the loop on this, @shubham1172 has identified a possible solution and is working on it. PR is here: https://github.com/dapr/dapr/pull/5024
Feel free to provide some feedback there!


[Feature Request] Add Array List and arrays

🚀 Arrays and Array List
Both Array and ArrayList are important in programming for different use cases, offering distinct advantages based on their structures and functionalities.
Add their algorithm for performing operations
I would like to work on it. Can you please assign me and add gssoc-ext label

Solved it #227


chore: Prepare for 3.9.0 Release

Summary

Prepare for 3.9.0 release

Pull Request Test Coverage Report for Build 1838

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.517%

Totals

Change from base Build 1832:
0.0%

Covered Lines:
4725

Relevant Lines:
5220

💛  - Coveralls

Pull Request Test Coverage Report for Build 1838

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.517%

Totals

Change from base Build 1832:
0.0%

Covered Lines:
4725

Relevant Lines:
5220

💛  - Coveralls


What does FilterManager.shaderCache do ?

In FilterManager , I found  there is a map named shaderCache, it will cache the shader of filter.
But In PIXI , never read anything from filterManager.shaderCache .
So, What does FilterManager.shaderCache do ?

The shader cache is an internal object used to cache programs we compile for a given context. It allows us to not have to recompile a shader every time you create an instance of a filter.
It is not for external use.


first Build.cmd failed on windows

I have windows10 and vs2017 with all the updates.
CheckFSharpInstallation.fsproj(19,5): error : File Microsoft.FSharp.Targets not found. Is F# correctly installed on this system?
I have Microsoft.FSharp.Targets in following locations. I am confused

full output:
Checking Paket version (downloading latest stable)...
Paket.exe 4.8.7 is up to date.
Paket version 4.8.7
1 second - ready.
Paket version 4.8.7
Resolving packages for group Build:
 - Octokit 0.24.0
 - FAKE 4.61.3
 - FSharp.Formatting 2.14.4
 - SourceLink.Fake 1.1.0
 - Microsoft.Net.Http 2.2.29
 - FSharpVSPowerTools.Core 2.3.0
 - FSharp.Compiler.Service <IP_ADDRESS>
 - Microsoft.Bcl 1.1.10
 - Microsoft.Bcl.Build 1.0.21
Resolving packages for group Main:
 - FSharp.Core <IP_ADDRESS>
Resolving packages for group Test:
 - NUnit 2.6.4
 - NUnit.Runners 2.6.4
C:\Users\dsusloparov\Google Drive\Workspace\tensorF\paket.lock is already up-to-date
4 seconds - ready.
Building project: CheckFSharpInstallation.fsproj
  C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\MSBuild.exe  CheckFSharpInstallation.fsproj /t:CheckFSharpInstallation /m      /p:RestorePackages="False" /p:OutputPath="C:\Users\dsusloparov\Google Drive\Workspace\tensorF" /p:Configuration="Release" /logger:Fake.MsBuildLogger+ErrorLogger,"C:\Users\dsusloparov\Google Drive\Workspace\tensorF\packages\build\FAKE\tools\FakeLib.dll"
Microsoft (R) Build Engine version 15.1.1012.6693
Copyright (C) Microsoft Corporation. All rights reserved.

Build started 6/9/2017 2:07:13 PM.
     1>Project "C:\Users\dsusloparov\Google Drive\Workspace\tensorF\CheckFSharpInstallation.fsproj" on node 1 (CheckFSh
       arpInstallation target(s)).
     1>C:\Users\dsusloparov\Google Drive\Workspace\tensorF\CheckFSharpInstallation.fsproj(19,5): error : File Microsoft
       .FSharp.Targets not found. Is F# correctly installed on this system?
     1>Done Building Project "C:\Users\dsusloparov\Google Drive\Workspace\tensorF\CheckFSharpInstallation.fsproj" (Chec
       kFSharpInstallation target(s)) -- FAILED.

Build FAILED.

       "C:\Users\dsusloparov\Google Drive\Workspace\tensorF\CheckFSharpInstallation.fsproj" (CheckFSharpInstallation ta
       rget) (1) ->
       (CheckFSharpInstallation target) ->
         C:\Users\dsusloparov\Google Drive\Workspace\tensorF\CheckFSharpInstallation.fsproj(19,5): error : File Microso
       ft.FSharp.Targets not found. Is F# correctly installed on this system?

    0 Warning(s)
    1 Error(s)

Time Elapsed 00:00:00.03
F# does not seem to be installed.
Please install F# (see http://fsharp.org/use/windows/ for instructions),
then run the build script again.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Exception: Build script aborted: please install F# and try again.
   at <StartupCode$FSI_0005>.$FSI_0005_Init$fsx.main@()
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at Fake.FSIHelper.runScriptCached@315.Invoke(Unit unitVar0) in C:\code\fake\src\app\FakeLib\FSIHelper.fs:line 323
System.Exception: Build script aborted: please install F# and try again.
   at <StartupCode$FSI_0005>.$FSI_0005_Init$fsx.main@() in C:\Users\dsusloparov\Google Drive\Workspace\tensorF\init.fsx:line 36
Stopped due to error

Build failed.
Error:
Could not find file 'C:\Users\dsusloparov\Google Drive\Workspace\tensorF\build.fsx'.

Silly question: does the project build correctly if you just open it in Visual Studio?

OK. I can confirm. This seems to be happen for me (and a few others based on some Slack comments). It looks like the code for detecting the presence of F# is reporting false negatives in some case.

@pblasucci I'll fix this now (was about to make the changes to remove SourceLink)

@susloparovdenis @pblasucci I can't repro this.  Which prompt are you running from - a VS2017 developer prompt or...
Could you try again now https://github.com/fsprojects/ProjectScaffold/pull/296 has been merged?  thanks

@dsyme just tried again... same results. I'm using a bog standard instance of cmd.exe.

OK. I found a clue. It's looking in:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v\FSharp\Microsoft.FSharp.Targets
Notice the \v\ ? That should probably be \v15.0\ (or at least some number after the v). Not sure how to fix this (yet).

Yes, VisualStudioVersion is not set, I have no idea why.  I thought it was always set.

Can you try ToolsVersion="15.0" at the top of the project files?  Just wondering.

@pblasucci Note that using a VS2017 developer command prompt will work.  But we should make it work from cmd.exe as well

Changing the tools version did not alter the behavior. And, just to confirm, the VS2017 developer command prompt does work. This is due to the dev prompt is putting the Visual Studio version into an environment variable (which the vanilla is absent in the vanilla prompt). Also, as an aside, even though the dev prompt works correctly, it emits a (spurious) warning about F# Tools not being installed... but one issue at a time.  :-)

Do you know which MSBUILD is being run?   When I use
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\MSBuild.exe

it works but when I use the very old
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe

it doesn't. I assume FAKE is in charge of choosing the right MSBuild, but I thought that FAKE 4.61.3 had an appropriate fix to always find the right version in all circumstances

Seems it's using
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\MSBuild.exe

Seems it's using  C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\MSBuild.exe

Does it work when you invoke that MSBUILD.EXE directly?
BTW here's a relevant FAKE issue:
https://github.com/fsharp/FAKE/issues/1442

Here's the list of search paths it uses to find MSBuild.exe: https://github.com/fsharp/FAKE/blob/master/src/app/FakeLib/MSBuildHelper.fs#L25

No luck. Invoking MSBuild.exe directly causes the same result.

How about if you add
  <Import Project="$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props" Condition="Exists('$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props')" />

to CheckFSharpInstallation.fsproj

OK, adding the Microsoft.Common.Props entry fixes this for me
(I can repro this now.  I was not focusing on CheckFSharpInstallation.fsproj - I was building the generated project (which has the Microsoft.Common.props entry))

Print the exception being caught here:
let checkFSharpInstallation () =
  try
    MSBuildRelease "." "CheckFSharpInstallation" ["CheckFSharpInstallation.fsproj"] |> ignore
    true
  with e ->
    false

Make sure you're starting from clean each time, i.e.
git reset --hard master
git clean -xfd .

I'd been starting clean each time. But printing the caught error seems to have fixed everything. No idea why/how, though
O_o
Anyway, at least we have the fixes... now someone just needs to prepare PR.

Done: https://github.com/fsprojects/ProjectScaffold/pull/297

@pblasucci Could you verify?  There is no printing of the caught error in that PR (did you actually get an error printed?)

Yup. Everything looks peachy now!  👍


Map to vector v2 (this was PR #37)

Add NimBLEAdvertisedDevice *getDevice(const NimBLEAddress &address) to get a pointer to an advertised device by address.
This is useful for devices that send information in their service data. Now you can do:
NimBLEAdvertisedDevice *dev = pBLEScan->getResults().getDevice(NimBLEAddress("58:2d:34:39:22:58"));
if(dev != nullptr && dev->haveServiceData()) {
  const uint8_t * pData = (const uint8_t*)(dev->getServiceData().data());
  ... do something with the service data ...
}

This was PR #37, but since @h2zero merged master into this PR at May 15, 2020, I could not push my branch again. So I created a new branch by pulling from PR #37. So this branch includes the master merged by @h2zero. I am not aware if this leads to additional diffs from that master with PR #37 ...

@Jeroen88 sorry about that, I thought you were done with the PR, I was fixing up conflicts. Will merge #37 soon.

sorry about that

No problem!

@h2zero I just realized that the getDevice() using an index currently in master is incorrect on an index out-of-bounds! I think it will crash if no devices are found yet while still calling getDevice(), otherwise it will always return the first device discovered if the index is out-of-bounds.

@h2zero I updated all my open PR's except #42 to the latest master


SyncProducer’s SendMessage accepts a sarama.ProducerMessage

Rationale:

This is in line with the AsyncProducer.
This makes it easier to switch between SyncProducer and AsyncProducer if the need arises.
This allows you to use to ManualPartioner, because now you can set the Partition field.

@Shopify/kafka Last API change I promise :)

it may or may not be worth noting that the Metadata field gets overridden in this api?

It stores the Metadata before overriding it, and sets the old metadata back afterwards using a defer, so I am not sure it's relevant. The Metadata object is basically only useful for the AsyncProducer, but I decided to mimic the async's producer behaviour in the sync API so people don't have any nasty surprises if they switch between sync and async.

LGTM


Adding image labels and publishing

Description
There is no way to take the existing awsutils container and cleanly publish it to a registry. Additionally since we are using the derivations for the image tags we have no way of identifying what versions of pkgs are contained in the container without running it.
New Behavior

image push script
adding unstable pin to use the newest version of skopeo
pkg versions be included in image as label: com.nebulaworks.packages

Tests
Current awsutils image published to our dockerhub registry:
$ skopeo inspect docker://docker.io/nebulaworks/awsutils:dz783iaashdby6phqf9pcydxsw1bbjq0
{
    "Name": "docker.io/nebulaworks/awsutils",
    "Digest": "sha256:4df34c1e6ab561b3aa6f0c250122ce121ff18e6803d72733f041978b87979df4",
    "RepoTags": [
        "dz783iaashdby6phqf9pcydxsw1bbjq0"
    ],
    "Created": "1970-01-01T00:00:01Z",
    "DockerVersion": "",
    "Labels": {
        "com.nebulaworks.packages": "awscli:1.17.13,bash:4.4,coreutils:8.31,curl:7.68.0,jq:1.6",
        "org.opencontainers.image.authors": "Nebulaworks Inc.",
        "org.opencontainers.image.source": "https://github.com/Nebulaworks/nix-garage"
    },
    "Architecture": "amd64",
    "Os": "linux",
    "Layers": [
        "sha256:6f29a11d541b258cbfb4956ccc442ac0ecf8a6c052f10d1ed0d6d6078ae30f2a"
    ],
    "Env": [
        "PATH=/bin/"
    ]
}

@Lynty @jamesnebulaworks Should be ready to :shipit:


[Feat.Req] Bulk insert of failed receipts

Problem statement
We have a loop that inserts all the failed receipts, but it's way more efficient if we insert via bulk.

Hi, I was willing to contribute, did you meant this part:-

Hi, I was willing to contribute, did you meant this part of the code:-

Hi, I was wishing to contribute, did you meant this part of the code:-

Hello @taslimmuhammed, sorry for the late response. So, the expected code for this issue is to use the same type of code on your screenshot but for the invalid/failed receipts.
The code that we'd like to update to look more like the screenshot is located here.
Let me know if you still have plans to contribute.

thanks for the reply

could you assign the issue to me, I'll finish it this weekend.

Hi, when you have time please go through the code


Max Slippage per transaction in SDK

Background
There is no reason to have max slippage globally configured in the SDK.
Linked Issues & Documentation
Definition Of Done
Max slippage is not required by SDK to instantiate and is passed in where needed into SDK.

This is already optional and not used.


UrlStr not available anymore in new pydantic version

Bug
In [1]: from pydantic import UrlStr
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-1-7415c2080b43> in <module>
----> 1 from pydantic import UrlStr

ImportError: cannot import name 'UrlStr' from 'pydantic' (/...../lib/python3.7/site-packages/pydantic/__init__.py)

pydantic version 1.0

Please read the docs. Including the release notes, three URL types names have changed.

it doesn't show up in the release notes here

Breaking Change: complete rewrite of URL parsing logic

Breaking Change: complete rewrite of URL parsing logic
Seems a bit short on details, in any event I got the "cannot import name 'UrlStr'" error - hopefully this will help others.
UrlStr has been removed (see https://github.com/samuelcolvin/pydantic/pull/755 for more details). AnyUrl is likely what you should change it to but there's also AnyUrl, AnyHttpUrl, HttpUrl, and HttpsUrl.

Hei,
I got caught in that one too. Might I suggest the HISTORY to be a bit clearer when fields are removed? Cheers.


feat: Always use POST to normalize request serialization

This intention is for GET to be used when possible, but blocking issues mean we need to use POST until we can ensure consistent request serialization and parsing for the query string.

whats the motivation here?

@seveibar motivation: https://hello-seam.slack.com/archives/C01D0J9ACLF/p1698670175221979

For all those who cannot see internal Slack threads, here are the details on this change.

All SDKs are moving to generated form. Until this nexlove issue is resolved, all the generated SDK will only use POST (since they don't have access to GET in the openapi spec): https://github.com/seamapi/nextlove/issues/117
Seam fully intends to prefer GET in the SDK and docs when GET is supported.
(2) is not ready yet due to some blocking issues:

(1) as noted above.
Serialization / parsing of array params. All SDKs need to implement a consistent serializer. (This serializer could be used as a reference model https://github.com/seamapi/javascript-http/blob/main/src/lib/params-serializer.ts). And this issue needs to be addressed https://github.com/seamapi/nextlove/issues/77


add possibility to context menu for files in explorer sidebar

https://github.com/everettjf/vscode-filter-line/issues/10#issuecomment-504636107

version 1.4.x added

There is a regression in the last version: context menu's commands stopped work for big files


EfficientDet implementation

Do author plan to implement EfficientDet "EfficientDet: Scalable and Efficient Object Detection" into mmdet framework
That would be great!
Thanks

PRs are welcome!

Is there any plan to implement it? It is currently the state of the art for object detection.
Thanks.

Expecting EfficientDet too！

A Pytorch version: https://github.com/zylo117/Yet-Another-EfficientDet-Pytorch

A Pytorch version: https://github.com/zylo117/Yet-Another-EfficientDet-Pytorch

It is LGPL v3 license, apache 2.0 license version is here: https://github.com/rwightman/efficientdet-pytorch

Looking forward for EfficientDet  and EfficientDetLite (which is the embedded friendly variant) as supported in https://github.com/rwightman/efficientdet-pytorch

Looking forward for EfficientDet  and EfficientDetLite (which is the embedded friendly variant) as supported in https://github.com/rwightman/efficientdet-pytorch

EfficientNet has been supported. PRs of EfficientDet is welcomed.


[21.11] zlib: 1.2.11 -> 1.2.12

Description of changes
Backport #165642 #166451
Supersedes #165951

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
22.05 Release Notes (or backporting 21.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Closes https://github.com/NixOS/nixpkgs/issues/166708?

I can't confirm it yet (I am without access with a Linux machine at the moment), however this will probably break all packages depending on GraalVM and using the zip module in Java. This is a known bug: https://github.com/oracle/graal/issues/4439 (yeah, it is closed because the original bug report is for the removal of 1.2.11 version from zlib website, but the issue itself is not fixed and I am trying to raise this), but I think the Oracle folks didn't realize yet this is a security issue).
Given this issue and the one with Perl linked above, wouldn't it better that we just backport the security patches (#165951) instead for release-21.11 instead? I fear that this may break more things than expected.


Update tab runtime_dependencies on pour.

Otherwise we end up making revisions for no real reason.

The problem is stuff already poured so we still need to revision bump.

This should be updated instead to be an audit to make sure these revisions happen when necessary (e.g. when deps change).

This should be updated instead to be an audit to make sure these revisions happen when necessary (e.g. when deps change).

Change of plan: this should check if first layer dependencies seem to match or similar.

Myanmar language
On Wed, 21 Mar 2018 4:52 pm Mike McQuaid<EMAIL_ADDRESS>wrote:

This should be updated instead to be an audit to make sure these revisions
happen when necessary (e.g. when deps change).
Change of plan: this should check if first layer dependencies seem to
match or similar.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Homebrew/brew/pull/3935#issuecomment-374868787, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AidWVGtXLEhska14uEHCdLJbGZdtz5u-ks5tghTVgaJpZM4StgHa
.

Changing the approach here enough to warrant just a new PR.


feature importance plot label overlap

Environment info
Operating System:
Windows 10 x64
Compiler:
Package used (python/R/jvm/C++):
python
xgboost version used:
0.6
If you are using python package, please provide

The python version and distribution

python 3.5.2 in anaconda 64bit

The command to install xgboost if you are not installing from source

wheel package from http://www.lfd.uci.edu/~gohlke/pythonlibs/#xgboost .
Steps to reproduce

Train a model using gb_classifier = xgb.XGBClassifier() , gb_classifier.fit()
xgb.plot_importance(gb_classifier ,  height=0.2)
see the image

The labels along y axis overlap badly. How can I fix the plot?

Get the fscores manually and use a complete feature filled plotting library to plot it better ... this is a very basic visualization meant for quickly seeing the results..
Reference: https://github.com/dmlc/xgboost/blob/master/python-package/xgboost/plotting.py#L14


Add helpers to Math.sol and Cast.sol

This PR creates two new files, Cast.sol and Math.sol, consisting of all the respective "cast" and "math" libraries.
The previous files have been kept for backwards compatibility purposes as many are used by non-upgradable contracts like the Cauldron, Ladle, and Witch.
A few notes:

Should RDiv.sol be added to the aggregated math library? (since the library is for wads and not rays, or should we just name it Math.sol or something?)
We could probably deprecate MinimalTransferHelper.sol as well if it weren't used by the NotionalJoin

It feels silly to have Math.sol in utils but Cast.sol on its own directory. You can move both to utils.
I'm also thinking that it feels silly to have a utils folder inside a utils repo. If we can't find a grouping for those contracts, we might as well pull them out to contracts.
I don't think that we need to keep the old contracts for backwards compatibility. The contracts that use them in vault-v2 and elsewhere should be refactored.
It might take a bit of effort to do each one and republish everything though npm finishing at environments-v2, but it is the cleaner way to do it.

It feels silly to have Math.sol in utils but Cast.sol on its own directory. You can move both to utils.
I'm also thinking that it feels silly to have a utils folder inside a utils repo. If we can't find a grouping for those contracts, we might as well pull them out to contracts.
I don't think that we need to keep the old contracts for backwards compatibility. The contracts that use them in vault-v2 and elsewhere should be refactored.
It might take a bit of effort to do each one and republish everything though npm finishing at environments-v2, but it is the cleaner way to do it.

I put the Math.sol in the utils/ folder to follow the same convention in Solmate with FixedPointMathLib.sol.
Having both in utils/ makes the most sense to me. Let me know what you think.


install ps and cmp commands in Dockerfile

Checklist before submitting

[x] Did you read the contributor guide?
[ ] Did you update any affected documentation?
[ ] Did you write any tests to validate this change?

Description
Install diffutils to fix the following error observed during build of jansson-feedstock
../test/suites/encoding-flags/run: line 20: cmp: command not found
F../test/suites/encoding-flags/run: line 20: cmp: command not found
F../test/suites/encoding-flags/run: line 20: cmp: command not found

Also install procps to fix the following error observed with uwsgi tests:
/opt/conda/conda-bld/uwsgi_1631802569680/test_tmp/run_test.sh: line 22: ps: command not found
Tests failed for uwsgi-<IP_ADDRESS>-py38hffb238b_3.tar.bz2 - moving package to /opt/conda/conda-bld/broken

Review process to land

All tests and other checks must succeed.
At least one maintainer must review and approve.
If any  maintainer requests changes, they must be addressed.

I didn't see the above error in 10.2 containers, but I have updated corresponding files too for consistency.


[PDI-18318] Calculator step produces incorrect result using BigNumber…

… as datatype.
@pentaho/tatooine
@pentaho-lmartins @ssamora
@mbatchelor

:gear: Build finished in 2m 49s with command:
mvn clean verify -B -e -Daether.connector.resumeDownloads=false -amd -Daudit -P !assemblies -pl core

:ok_hand: All tests passed!

Total
Failed
Skipped

1101
0
0

Details

:information_source:  This is an automatic message

:gear: Build finished in 16m 20s with command:
mvn clean verify -B -e -Daether.connector.resumeDownloads=false -amd -Daudit -P !assemblies -pl core,engine

:ok_hand: All tests passed!

Total
Failed
Skipped

4644
0
7

Details

:information_source:  This is an automatic message

:gear: Build finished in 17m 4s with command:
mvn clean verify -B -e -Daether.connector.resumeDownloads=false -amd -Daudit -P !assemblies -pl core,engine

:ok_hand: All tests passed!

Total
Failed
Skipped

4648
0
7

Details

:information_source:  This is an automatic message

:gear: Build finished in 23m 34s with command:
mvn clean verify -B -e -Daether.connector.resumeDownloads=false -amd -Daudit -P !assemblies -pl core,engine

:ok_hand: All tests passed!

Total
Failed
Skipped

4648
0
7

Details

:information_source:  This is an automatic message

:gear: Build finished in 29m 47s with command:
mvn clean verify -B -e -Daether.connector.resumeDownloads=false -amd -Daudit -P !assemblies -pl core,engine

:ok_hand: All tests passed!

Total
Failed
Skipped

4648
0
7

Details

:information_source:  This is an automatic message

:gear: Build finished in 24m 8s with command:
mvn clean verify -B -e -Daether.connector.resumeDownloads=false -amd -Daudit -P !assemblies -pl core,engine

:ok_hand: All tests passed!

Total
Failed
Skipped

4647
0
7

Details

:information_source:  This is an automatic message

:gear: Build finished in 23m 24s with command:
mvn clean verify -B -e -Daether.connector.resumeDownloads=false -amd -Daudit -P !assemblies -pl core,engine

:ok_hand: All tests passed!

Total
Failed
Skipped

4649
0
7

Details

:information_source:  This is an automatic message

:gear: Build finished in 23m 26s with command:
mvn clean verify -B -e -Daether.connector.resumeDownloads=false -amd -Daudit -P !assemblies -pl core,engine

:ok_hand: All tests passed!

Total
Failed
Skipped

4650
0
7

Details

:information_source:  This is an automatic message

@mbatchelor please review

:gear: Build finished in 23m 14s with command:
mvn clean verify -B -e -Daether.connector.resumeDownloads=false -amd \
-Daudit -P !assemblies -pl core,engine

:ok_hand: All tests passed!

Total
Failed
Skipped

4653
0
7

Details

:information_source:  This is an automatic message

:gear: Build finished in 16m 51s with command:
mvn clean verify -B -e -Daether.connector.resumeDownloads=false -amd \
-Daudit -P !assemblies -pl core,engine

:warning: Failed Tests

:cloud_with_lightning_and_rain: 8 test(s) failed:

org.pentaho.di.core.row.ValueDataUtilTest.testDivisionBigNumbersWithPrecision1AndRoundingModeHalfDown

    expected:<2> but was:<2.4>

org.pentaho.di.core.row.ValueDataUtilTest.testDivisionBigNumbersWithPrecision1AndRoundingModeHalfEven

    expected:<2> but was:<2.4>

org.pentaho.di.core.row.ValueDataUtilTest.testDivisionBigNumbersWithDefaultPrecision

    expected:<123456789012345678901.12> but was:<123456789012345678901.1234567890123456789>

org.pentaho.di.core.row.ValueDataUtilTest.testDivisionBigNumbersWithPrecision1AndRoundingModeUp

    expected:<3> but was:<2.3>

org.pentaho.di.core.row.ValueDataUtilTest.testDivisionBigNumbersWithPrecision1AndRoundingModeFloor

    expected:<2> but was:<2.3>

org.pentaho.di.core.row.ValueDataUtilTest.testDivisionBigNumbersWithPrecision1AndRoundingModeDown

    expected:<2> but was:<2.3>

org.pentaho.di.core.row.ValueDataUtilTest.testDivisionBigNumbersWithPrecision1AndRoundingModeCeiling

    expected:<3> but was:<2.3>

org.pentaho.di.core.row.ValueDataUtilTest.testDivisionBigNumbersWithPrecision1AndRoundingModeHalfUp

    expected:<2> but was:<2.4>

Total
Failed
Skipped

4653
8
7

Details

:information_source:  This is an automatic message

:gear: Build finished in 16m 40s with command:
mvn clean verify -B -e -Daether.connector.resumeDownloads=false -amd \
-Daudit -P !assemblies -pl core,engine

:ok_hand: All tests passed!

Total
Failed
Skipped

4653
0
7

Details

:information_source:  This is an automatic message

:gear: Build finished in 2m 53s with command:
mvn clean verify -B -e -Daether.connector.resumeDownloads=false -amd \
-Daudit -P !assemblies -pl core,engine

:ok_hand: All tests passed!

Total
Failed
Skipped

1101
0
0

Details

:information_source:  This is an automatic message

:gear: Build finished in 16m 23s with command:
mvn clean verify -B -e -Daether.connector.resumeDownloads=false -amd \
-Daudit -P !assemblies -pl core,engine

:ok_hand: All tests passed!

Total
Failed
Skipped

4656
0
7

Details

:information_source:  This is an automatic message

:gear: Build finished in 23m 9s with command:
mvn clean verify -B -e -Daether.connector.resumeDownloads=false -amd \
-Daudit -P !assemblies -pl core,engine

:ok_hand: All tests passed!

Total
Failed
Skipped

4669
0
7

Details

:information_source:  This is an automatic message

:gear: Build finished in 25m 12s with command:
mvn clean verify -B -e -Daether.connector.resumeDownloads=false -amd \
-Daudit -P !assemblies -pl core,engine

:ok_hand: All tests passed!

Total
Failed
Skipped

4669
0
7

Details

:information_source:  This is an automatic message

:gear: Build finished in 16m 34s with command:
mvn clean verify -B -e -Daether.connector.resumeDownloads=false -amd \
-Daudit -P !assemblies -pl core,engine

:ok_hand: All tests passed!

Total
Failed
Skipped

4666
0
7

Details

:information_source:  This is an automatic message

:gear: Build finished in 25m 31s with command:
mvn clean verify -B -e -Daether.connector.resumeDownloads=false -amd \
-Daudit -P !assemblies -pl core,engine

:ok_hand: All tests passed!

Total
Failed
Skipped

4666
0
7

Details

:information_source:  This is an automatic message

:gear: Build finished in 4m 52s with command:
mvn clean verify -B -e -Daether.connector.resumeDownloads=false -amd \
-Daudit -P !assemblies -pl core,engine

:ok_hand: All tests passed!

Total
Failed
Skipped

1103
0
0

Details

:information_source:  This is an automatic message

:gear: Build finished in 24m 12s with command:
mvn clean verify -B -e -Daether.connector.resumeDownloads=false -amd \
-Daudit -P !assemblies -pl core,engine

:ok_hand: All tests passed!

Total
Failed
Skipped

4668
0
7

Details

:information_source:  This is an automatic message

:gear: Build finished in 26m 7s with command:
mvn clean verify -B -e -Daether.connector.resumeDownloads=false -amd \
-Daudit -P !assemblies -pl core,engine

:warning: Failed Tests

:cloud_with_lightning_and_rain: 1 test(s) failed:

org.pentaho.di.trans.step.mqtt.MQTTStreamSourceTest.testMqttStreamSingleTopic

    ${result.errorDetails}

Total
Failed
Skipped

4668
1
7

Details

:information_source:  This is an automatic message

AFAICT, the failing test started failing after it was successful in an area of code unrelated to the changes.


Concurrent "send console input" schedules can break

Bug Report
System Information

OS: Ubuntu Linux (20.04 LTS)
AMP: v2.3.2, built 31/01/2022 (Mainline)

I confirm:

[x] that I have searched for an existing bug report for this issue.
[x] that I am using the latest available version of AMP.
[x] that my operating system is up-to-date.

Symptoms

What are you trying to do?
Setting multiple schedules that may trigger in the same minute, each sending their own command to the input of the Minecraft server.
What are you expecting to happen?
Commands get run sequentially, in any order.
What is actually happening? ('Nothing' is not an acceptable answer!)
The commands sometimes work independently and sometimes get concatenated.

Reproduction

Set up a Minecraft server (tried Fabric and Paper 1.18.1 so far)

Create 2 schedules, each triggering every minute

Set a command for each, for example say test1 and say test2

Put a bit of load on ther server. It doesn't have to be laggy, just joining the server does the trick it seems.

Wait. (In testing, i'm getting a wrongly formatted command every 3-4 minutes, YMMV)

Interesting. Looks like a locking issue, should be simple enough to fix.

Still present in the latest version


Fix 'running' status format

Found while implementing https://github.com/rabbitmq/rabbitmq-shovel/issues/22

Was this meant to be submitted against live?

oops, yes! closing and resubmitting


Add missing url

Relates to #4286

Learn Build status updates of commit 48bc0c7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/cpp/exceptions-and-stack-unwinding-in-cpp.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


removed redundant assignment to AccountSetupBasics

removed null affectation because it’s done automatically

What @artbristol said.
Also, local variables aren't initialized automatically. See JLS, chapter 16 to learn more.

Thanks for your contribution!
I added the changes suggested by @artbristol: https://github.com/k9mail/k-9/commit/abd2b208508b18d3112903d858a7db7a2a450d03


get pdf -> print, ignores right paragraphs in the text

hi, so i tried to print the abhorsen handbook, and when i get to the printing part, it ignores the second colmuns (right oriented, for example spellcasting habilities, and fightingstyle )
Share Link : http://homebrewery.naturalcrit.com/share/B1vibnUiW

does work for me just fine. maybe you have selected a wrong papersize in your print settings?

I tried using firefox instead vivaldi and that solved the things for me


Translating all texts

Previous/next links in blog posts
Dates in blog thumbnails
Contact form

Date locale: "pl" + format (blog-list_home.js, blog-posts.js)


GUI: Network configuration different after GUI initialization

The GUI does not reconstruct the same network connectivity and drives after reconstruction from widget values.
Test:

Load test network configuration hnn_core/tests/assets/jones2009_3x3_drives.json. This config has all drive types (evoked, bursty, poisson) and tonic bias added.
Run a simulation
Compare the Network used to run the simulation (derived from GUI widget values) to a Network created by the API read_network_connectivity function.

Problems:

Number of connections is not the same. There are more bursty and poisson connections.

The GUI passes weights and constants dictionaries by cell types to the add_x_drive functions. Because there is an input box for each cell type, even weights with 0 are passed into the drive construction. This creates additional unnecessary null-weight connections.
The GUI doesn't have an input widget for the n_drive_cells parameter. It uses the defaults 'n_cells' for evoked and poisson, and 1 for bursty. The synchronous inputs checkbox does send a n_drive_cells value to drive construction but otherwise the parameter is hidden from user input. But with the default bursty drives are always synchronous.

The order of the drives is not the same. They are sorted alphabetically when read into the GUI.

gid_ranges and pos_dict are not the same as a consequence of 1 and 2

Tonic bias is not in the GUI-derived Network

This is because there isn't a way to load tonics into the GUI from file yet.

Cell parameters are not the same. This is being addressed in #848

To Do:

[x]  Fix drive order when loading drives https://github.com/jonescompneurolab/hnn-core/pull/851
[x]  Add tonic loading from file #852
[x]  Filter weights and constants for only cells with non-zero weights during drive construction. #853
[ ]  Add n_drive_cells input widget

@ntolley
I'm working on the n_drive_cells and sync_input rework today. I just want to make sure I understand the API correctly. Is this understanding correct?
1.n_drive_cells=1 and cell_specific=False - Synchronous input: 1 drive cell is connected to all network cells
2.n_drive_cells=3 and cell_specific=False - 3 drive cells are connected to all network cells
3.n_drive_cells='n_cells' and cell_specific=True - a unique drive cell gets assigned to each available simulated cell in the network with 1-to-1 connectivity
4.n_drive_cells='n_cells' and cell_specific=False - This is invalid
5.n_drive_cells=3 and cell_specific=True - This is invalid

This is all correct!


Bloxstrap mutes Voice chat

When you try to use voicechat with the Bloxstrap launcher it will fully mute everyone.
I had to uninstall Bloxstrap just to play with voicechat once, I will reinstall it as soon as I stop using voicechat or when its fixed.

I don't have voice chat (yet) so I can't confirm, but I'll check with people who do, and get it fixed soon. Thank you for reporting.

Got voice chat and just checked, and I'm unable to reproduce. Are you sure you have the correct output device selected in settings?

Got voice chat and just checked, and I'm unable to reproduce. Are you sure you have the correct output device selected in settings?

yes, I tried the same settings in the "Normal" roblox application and there it did work.
Mabye I will just have to reïnstall Bloxstrap

I'm less inclined to believe this is a bug with Bloxstrap... checked with some other friends and they say that audio output works just fine. Besides, I don't really see what Bloxstrap would be doing to cause such an oddly specific change.
I can only really see this issue coming from some misconfigured audio setting somewhere.

Are you on a specific channel or have you modified the FFlags?

I'm less inclined to believe this is a bug with Bloxstrap... checked with some other friends and they say that audio output works just fine. Besides, I don't really see what Bloxstrap would be doing to cause such an oddly specific change. I can only really see this issue coming from some misconfigured audio setting somewhere.

I guess thats the problem, if I still have the problem I will reopen the issue.


dm-lwm2m: fix tc_util.h include location

Follow upstream change of location:
tests/include -> subsys/testsuite/include
Fixes tc_util.h not found error during compile.
Signed-off-by: Michael Scott<EMAIL_ADDRESS>

ci-retest

This failure is to be expected until we merge the Zephyr changes.

ci-retest

All green lights.  Merging.

Oh funky.. there's another test running.  I'll wait.

the completion of one test triggers the other.

Ok now it's good :P


Exposed methods are hidden in the last release

Hi,
I asked to expose the following methods in the Issue #2117
SetDoNotFillQtytoHandle in the Report "Get Source Documents"
GetLastReceiptHeader in the Report "Get Source Documents"
SetOneCreatedShptHeader in the Report "Get Source Documents"
SetOneCreatedReceiptHeader in the Report "Get Source Documents"
SetSkipBlocked in the Report "Get Source Documents"
SetHideValidationDialog in the Codeunit "TransferOrder-Post Receipt"
Calculate in the Codeunit "Calculate Prod. Order"
I updated the latest package today and found those methods are not exposed anymore. Can someone take a look what's going on ?
Thanks,

I am using "Developing for Dynamics 365 Business Central". The packages in
the VS Code are "Microsoft_Application_12.3.23590.23730.app" and
"Microsoft_System_12.0.12928.0.app".
The last working packages are "Microsoft_Application_13.0.22070.0.app" and
"Microsoft_System_13.0.12928.0.app".
On Wed, Aug 8, 2018 at 1:49 AM Stanislaw Stempin<EMAIL_ADDRESS>wrote:

All these methods are still External on the latest builds. Are you sure
you're using the right version of the product?
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/
https://blogs.msdn.microsoft.com/freddyk/2018/04/16/which-docker-image-is-the-right-for-you/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/AL/issues/3156#issuecomment-411318748, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AkGBgzSfdq8Wz7wZx0Q30SUkViijVWXQks5uOpghgaJpZM4Vyk3K
.

Yes, precisely. Issues fixed on GitHub will currently end up in version 13.0.XXX. So you moved from version 13.0 back to 12.3 - that's why you see these methods as Internal.

Thanks, I re-created another VM with 13.0.XX version. Everything is working
fine.
On Wed, Aug 8, 2018 at 1:03 PM Stanislaw Stempin<EMAIL_ADDRESS>wrote:

Yes, precisely. Issues fixed on GitHub will currently end up in version
13.0.XXX. So you moved from version 13.0 back to 12.3 - that's why you see
these methods as Internal.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/AL/issues/3156#issuecomment-411516814, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AkGBg4Fxu_v4QJBSXHeTR8pOiS6Vgbwmks5uOzYOgaJpZM4Vyk3K
.


Update otel collector contrib to v0.105.0

@ridwanmsharif should we also push a git tag to the repo for manifests v0.1.0?

should we also push a git tag to the repo for manifests v0.1.0?

Yup, once this lands - lets push a git tag

should we also push a git tag to the repo for manifests v0.1.0?

Yup, once this lands - lets push a git tag

Done - https://github.com/GoogleCloudPlatform/otlp-k8s-ingest/tree/v0.1.0

Also created a release 🎉 https://github.com/GoogleCloudPlatform/otlp-k8s-ingest/releases/tag/v0.1.0


Show angry smile after foe name

Fixes #887

Could you post a screenshot of the result? :)

@Geosearchef would u review again?


Add EOL parsers

[ ] carriage return
[ ] line feed
[ ] crlf
[ ] combination eol parser that handles the common occurrences of these
[ ] orEOL function?

Done in v0.6.0


chore(api-docs): the api docs plugin should be published

Hey, I just made a Pull Request!
Looks like this is the default of create plugin and one has to change it 🙄 A release won't be possible without it...
:heavy_check_mark: Checklist

[ ] All tests are passing yarn test
[ ] Screenshots attached (for UI changes)
[ ] Relevant documentation updated
[ ] Prettier run on changed files
[ ] Tests added for new functionality
[ ] Regression tests added for bug fixes

@Fox32
Your build points to another problem:
Incorrect type dependencies in @backstage/plugin-api-docs:
10
  Missing a type dependency: @types/react


Licence?

There doesn't appear to be any licence headers for any of this code, this would be useful to have as I want to modify it to work with different SoC peripheral configurations (I'm not using the xilinx uart).

I've added the MIT license to this repo.
Hope that helps.

Thanks, much appreciated.


How can I transform xml with xsl

I want to know that how I can transform xml using xsl in xml package.

There is no built in support for XSL, but this is definitely something that could be built on top of this library. I do not have the expertise or interest to do this though (see https://github.com/renggli/dart-xml/issues/91).

Using Dart code, by querying, updating and re-building the DOM.


New Package: FreeDV.FreeDV version 1.8.4

Resolve #111388

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/115359&drop=dogfoodAlpha

@wingetbot run


Fixed grammar mistakes/typos

Fixed grammar mistakes/typos throughout the text

Thank you for these fixes!


Client Allocation Request for: KDEE ASSOCIATION

Client Allocation Questions
Core Information

Name: KDEE ASSOCIATION
Website / Social Media: http://kdee.co.kr
Region: Asia (excl. Greater China)
DataCap Requested: 10TiB
Addresses to be Notarized: f154edhkgzxsgre6xixd7icdnuak5xrtm2ne2l4wi
Notary Requested: MasaakiNawatani

@chenbinjgoanwiegn Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

Hi @chenbinjgoanwiegn
Thanks for your response. I am currently having some technical issues allocating datacap to anyone. I'm still working things out with Notary Admins. Please feel free to reach out to other Notaries in the same region. I will close this for now.


Setup Kanban 💪

In this project we were 4 :

@leehaney254
@tanveerisonline
@codehass
@Josphat205

The link to our project can be found here.
The link to our front end issues page can be found here
The image to our kanban board

Hi Team,
In my opinion, you are ready to move on to the next step! ⏭
Good luck! 🎉
Highlights

All issues have descriptions 👍
All issues are distributed equitably among team members 👍
Screenshot and info can be seen from this issue description 👍

Optional suggestions

[OPTIONAL] Consider adding labels to make it easier to filter by and classify issues in the project board. [OPTIONAL]

Feel free to leave any questions or comments in the Issue thread if something is not 100% clear.
Cheers and Happy coding!👏👏👏

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

Thank you @mcrd25  💪


Fix a void* cast in cudart with CUDA11

You run into:legion/runtime/realm/cuda/cudart_hijack.cc:436:22: error:
invalid conversion from ‘const void*’ to ‘void*’ [-fpermissive]
attr->hostPointer = (const void*) ptr;
^~~~~~~~~~~~~~~~~
TEST: Verify legion builds
Change-Id: Ia15247b728d85860154446b6cffcad1bc868827b

Yep, this looks like the right way to fix this.  I'll double-check on my system and then merge.  Thanks!

I ended up spelling it slightly differently, but this should be fixed in the master branch with commit 1ad3e22.  Thanks again for catching this!

Looks great. Thanks.


[DISCUSSION GUIDE] Open Data

Agenda:

45 minutes for review

Answer questions about last week -- include search OSM for a different location, and submitting portfolio posts/assignments.
Asking for edits in the upcoming week: do a map in a different location, write 2-3 sentence site description, and include at least one citation (hyperlink)
Mention the code review

15 minutes to talk about FAIR and CARE
30 minutes to introduce the climate coding challenge: https://cu-esiil-edu.github.io/esiil-learning-portal/foundations/notebooks/01-climate/climate.html

/adminteamassign @earthlab-education/ea-instructors


Make addresses searchable at explorer start

And other info, like simple transactions, name register transactions etc.
Fix for https://phantasma.atlassian.net/browse/EXP-9

Merging post successful verification


Unable to encode the CHOICE type

Hey, I am trying to encode a CHOICE type to UPER but it is always failing.
I have the following specifications:
ChoiceTest ::= CHOICE {
    intCode INTEGER,
    boolCode BOOLEAN
}

And I encode this CHOICE using the following C code:
uint8_t *buffer = (uint8_t *) malloc(sizeof *buffer);
ChoiceTest_t *test = (ChoiceTest_t*) calloc(1, sizeof *test);
test->choice.intCode = 5;
asn_per_constraints_t *constraints = NULL;

const ssize_t ec = uper_encode_to_new_buffer(&asn_DEF_S1AP_PDU,
                                                   constraints,
                                                   test,
                                                   (void **)&buffer);

The encoding fails and uper_encode_to_new_buffer returns -1.
Kindly help me in this.

Hi @AliNawazish,

ChoiceTest ::= CHOICE {
    intCode INTEGER,
    boolCode BOOLEAN
}

And I encode this CHOICE using the following C code:
uint8_t *buffer = (uint8_t *) malloc(sizeof *buffer);
ChoiceTest_t *test = (ChoiceTest_t*) calloc(1, sizeof *test);
test->choice.intCode = 5;
asn_per_constraints_t *constraints = NULL;

const ssize_t ec = uper_encode_to_new_buffer(&asn_DEF_S1AP_PDU,
                                                   constraints,
                                                   test,
                                                   (void **)&buffer);

The encoding fails and uper_encode_to_new_buffer returns -1.

Most probably it fails because the first argument is wrong, it should be  something like &asn_DEF_ChoiceTest and not &asn_DEF_S1AP_PDU as you are not trying to encode S1AP_PDU.
Also you should not allocate the buffer as it is an output parameter and it's allocated in uper_encode_to_new_buffer

@velichkov Thanks for the reply.
I have now changed &asn_DEF_S1AP_PDU to &asn_DEF_ChoiceTest and removed the buffer allocation before calling uper_encode_to_new_buffer. However, the problem still persists.
Any help would be appreciated.

Hi @AliNawazish,
Could you share the full source code, the asn.1 file and all commands that you use to compile it in order to be able to reproduce this failure?

test.asn file:
Messages DEFINITIONS ::= BEGIN
    ChoiceTest ::= CHOICE {
        intCode INTEGER,
        boolCode BOOLEAN
    }
END

test.c file:
#include "compileddir/ChoiceTest.h"

int main(){
    uint8_t *buffer;

    ChoiceTest_t *test = (ChoiceTest_t*) calloc(1, sizeof *test);
    test->choice.intCode = 1;

    asn_per_constraints_t *constraints = NULL;

    const ssize_t ec = uper_encode_to_new_buffer(&asn_DEF_ChoiceTest,
                                                constraints,
                                                test,
                                                (void **)&buffer);

    printf("Buffer size: %d\n", ec);
}

Commands used to generate the asn1 file:
cd compileddir
asn1c ../test.asn
Command to compile the c code:
gcc test.c -o output -Icompileddir compileddir/*.c

You need to set the present field to ChoiceTest_PR_intCode
test->present = ChoiceTest_PR_intCode;
test->choice.intCode = 1;

In order to get some debug messages recompile with -DASN_EMIT_DEBUG=1 in CFLAGS
gcc test.c -DASN_DISABLE_OER_SUPPORT -DASN_EMIT_DEBUG=1 -o output -Icompileddir compileddir/*.c

./output
Encoding ChoiceTest as CHOICE (compileddir/constr_CHOICE.c:932)
Encoding ChoiceTest CHOICE element 0 (compileddir/constr_CHOICE.c:950)
CHOICE member "intCode" 0 (as 1) (compileddir/constr_CHOICE.c:983)
[PER put 1 bits 1 to 0x7ffc297b09e8+0 bits] (compileddir/asn_bit_data.c:200)
[PER out 1 1/1 (t=0,o=1) 0&0=0] (compileddir/asn_bit_data.c:243)
[PER out 128/80 => 80 buf+0] (compileddir/asn_bit_data.c:274)
Encoding NativeInteger INTEGER 1 (UPER) (compileddir/NativeInteger.c:306)
[PER put 8 bits 1 to 0x7ffc297b09e8+1 bits] (compileddir/asn_bit_data.c:200)
[PER out 8 1/1 (t=1,o=9) 80&80=80] (compileddir/asn_bit_data.c:243)
[PER out 128/80 => 80 buf+0] (compileddir/asn_bit_data.c:274)
[PER put 8 bits 1 to 0x7ffc297b09e8+9 bits] (compileddir/asn_bit_data.c:200)
[PER out 8 1/1 (t=1,o=9) 80&80=80] (compileddir/asn_bit_data.c:243)
[PER out 128/80 => 80 buf+1] (compileddir/asn_bit_data.c:274)
Freeing INTEGER as a primitive type (compileddir/asn_codecs_prim.c:125)
Complete encoded in 17 bits (compileddir/per_encoder.c:139)
Buffer size: 3

@velichkov It works now. Really appreciate your help.


8 BUGS:   1. Shortcut's reset button closes the alert without saving the change. 2. Text selection markup color is invisible  3. ... 4. 5. 6. 7.

None of these bugs happened before (https://github.com/code-for-charity/SATUS/blob/master/Jan2022_Satus.js ).    To see it working  install: 3.965.zip  (=ImprovedTube Repo october7)   More precisely: https://github.com/code-for-charity/SATUS/issues/6

[x] #7

[x] #8

[ ]  3. the input field up/down arrows have not been migrated from 3.965    (forced volume, forced speed)
component: 'slider',
text: 'volume',
step: 1,
max: 400,
value: 100

[ ] 4. Textarea  selection markup is unfinished. (Disabled it in satus.css for now)    compare https://github.com/code-for-charity/ultimate-REGEX-extension to understand what this is about (input markup rules)
(also will help in https://github.com/code-charity/History-Manager-with-indexedDB/blob/main/readme.md )

[ ] 5. The "page-swipe" animation is nervous/flashy  with the red buttons. ( + The yellowish background of ImprovedTube 3.965 is nicer(?) )

[ ]  6. (Analyzer) Charting doesn't happen anymore either  (worked before too!)  #1527
(didnt happend in 2021: either https://github.com/code-for-charity/ImprovedTube-for-YouTube/blob/70c7f03a12c51ac7736dbc740d073b417bc6f135/satus.js
https://github.com/code-for-charity/ImprovedTube-for-YouTube/blob/70c7f03a12c51ac7736dbc740d073b417bc6f135/satus.css )

[ ] 7.  these checkboxes  ignore clicks 😆 (only the whole items an be clicked but not the checkbox itself)

Text selection markup color is invisible

Shortcut's reset button closes the alert without saving the change.

I am first time on dev. Can you provide some video ?

@systemaworking both bugs appear in the current ImprovedTube versions released in Google Chrome Webstore.

yet the older versions dont show these bugs, including Firefox Edge Opera as of now & the Github Repo until:  October 9 https://github.com/code-for-charity/ImprovedTube-for-YouTube/archive/28f1bef13c0f77c2b9c5200ec9c7868b8d354629.zip )

@systemaworking both bugs appear in the current ImprovedTube versions released in Google Chrome Webstore

I fixed the trivial ones.
3. looks easy, will look at it next
6. I never used Analyzer so dont even know how its supposed to look when its working :)
7. I dont know where this is, cant find it in current YouTube-Extension

yes
just printing a charting at all

yes
just printing a chart at all