Data pipeline to postgres

Reworks acquire_data.py to read/write to/from postgres instead of from file.

Left some comments, but otherwise it looks great. Did you try syncing this up with the full demo pipeline (devnet -> bot trades -> postgres -> streamlit)? I think that would be a good test to do before merging.

This was tested with the demo pipeline.


Consider treating -up.X as a release version when evaluating Crossplane constraints for package

What problem are you facing?

Crossplane will refuse to install packages that don't specify Crossplane constraints with -0 if the Crossplane version is not a release version. However, because UXP uses a -up.X versioning scheme, all releases are considered non-release versions.
How could Upbound help solve your problem?

We should consider special-casing -up.X versions as release versions and allowing install of packages that restrict to only release versions.

I believe this would a package manager change in upbound/crossplane, at the lines where we check the XP version.

It looks like we have indeed fixed this with https://github.com/upbound/crossplane/pull/17, but somehow missed including this in the recent release branches of upbound/crossplane due to the existing manual release process and branch preparation.
@phisco is working on improving and automating our release process and catched this and opened a fix https://github.com/upbound/crossplane/pull/84 to include it in the upcoming v1.12 release.
So, we will no longer need a special treatment with xp version dependencies as mentioned in this issue.

We just released v1.12.1-up.1 with the backported fix.
Crossplane dependency should now work with UXP in the same way as upstream, for example:
spec:
  crossplane:
    version: ">=v1.12.0"


Add Contributing

see e.g. Contributing at CE.

Things I think the document should mention to help new contributors (i.e. these would have helped me):

Short introduction to the workflow (fork, branch, commit, push, check CI, pull request) - no need to describe each step in detail, but at least link the needed resources (I more or less had to learn git, github, and travis by myself to contribute)
Notes about versioning: what can you do, and what mustn't you do in a minor version (see issue #196)
Branching strategy (if/when we'll have one)
Add tests!
Install editorconfig for your editor to not mess up tabs and spaces
Naming and style conventions (eg. where to put spaces)
Differences between gsl_HAVE, gsl_CONFIG, gsl_FEATURE macros, how to name a new macro?


Dragging over an inner target of (dom) nested drop targets does not generate any events

This issue was imported from Closure Library's previous home at http://closure-library.googlecode.com
The link to the original issue is:
https://code.google.com/p/closure-library/issues/detail?id=275

fixed in https://github.com/google/closure-library/commit/a3737f04b763af9f193223f0dace98175c8ee9f8


[refactor] code refactor.

Issue Description
Type: feature request
There are many problems in the code of sealer. It becomes hard to make people join us in developing sealer. It's time for us to spend time refactoring our code.
Describe what feature you want
I propose this issue, and record some refactor of works (TODO list) here. These works are also suitable for sealer new developers.

[ ] Runtime module (doing @starComingup)
[ ] Semantic fuzziness in code - especially in shell. (detailed description is on the way @justadogistaken)
[ ] Too many shell in go - (detailed description is on the way @justadogistaken)
[ ] Too many getSSHClient, CmdAsync() ... - maybe we can come up with a struct that describes host or host pool. And Cmd/SCP are under that struct. (detailed description is on the way @justadogistaken)
[ ] Image module - includes build/push/pull/compatible with oci (doing @justadogistaken )
[ ] Welcome to add more.

for Semantic fuzziness in code, could you pls give us example ? i am confused about this topic.
for Too many getSSHClient, CmdAsync()，separate defining and useage of ssh client include "platform.go under ssh package".


link error

Visual studio 2022
a.obj : error LNK2005: "void (__cdecl* obf::draw)(char const *)" (?draw@obf@@3P6AXPEBD@ZEA) already defined in b.obj

The problem is either because your compiler doesn't support #pragma once, or because you used namespace obf:: and the draw from it is conflicting with another method from your project.
I replaced #pragma once with include guard, changed the draw method name to a less conflicting one
https://github.com/ac3ss0r/obfusheader.h/commit/85f741e236eb2dcfd32d12801d0e1c34d277a4b7
The issue should be resolved now, if it's not reopen it with more information


ACM-4616: Ansible log faliure fix

regarding: https://issues.redhat.com/browse/ACM-4616

/hold

Preparing live cluster testing ahead of review.

/retest-required

/retest-required

Update: Added code to also cover StatusField component.

/retest-required

/retest-required

/hold

/lgtm

/unhold


Document how to load Multi-Label Classification data from CSV

Is your feature request related to a problem? Please describe.
I was trying to follow the Multi-Label Classification tutorial, but my data is in CSV files. It took a while to figure out (by tracing through the code) that unlike with single-label classification, the labels are each expected to be in a separate column with the strings true/false to indicate if each row has that output label. Based on how single-label classification works, I was expecting to have multiple label columns (e.g., label 1, label 2, etc.) with one label in each column (blanks allowed if the example has fewer labels than the max allowed).
Describe the solution you'd like
Now that I understand how CSV data needs to be formatted I have no issue with it. What I'd like is better documentation on what the CSVLoader is expecting the data to look like. This would ideally go in the javadocs, but a tutorial on how to structure data would be nice, too.
Describe alternatives you've considered
Tracing through the code worked (I was able to figure it out) but was painful.

Sure we can improve the docs there. The preferred method for working with more complex CSV data is to use CSVDataSource and the RowProcessor machinery, but that's also not obvious for multilabel data so needs better documentation (you can see how it should work by looking at the code for CSVLoader as CSVLoader constructs a RowProcessor under the covers).

Yeah, that's what I basically ended up doing. What made it extra confusing is that CSVLoader has some constructors with an argument called responseName, which is used in the single-label case to indicate the name of a column that contains the labels (e.g., a bunch of strings), but for the multi-label case the argument is called responseNames, but indicates columns whose names are the labels, and whose contents are strings that can be mapped to booleans. These two different usages of responseName really threw me for a loop. The javadoc for each is even the same. I think if the javadoc for each were updated to explain what was expected of those columns, it would be much clearer.

Ok, we'll definitely fix that. Modifying the javadoc is easy, writing fresh tutorials requires more thought.

Part of the problem is that MultiLabelFactory doesn't let the user select the split character (unlike RegressionFactory) and it defaults to , so you can't present a delimited list of labels in a single column of a csv file without juggling. I think the longer term solution is to fix that issue in MultiLabelFactory, then revise CSVLoader and the response processors to better handle multi-output things. We'd done a pass of this before the initial v4 release (which is how RegressionFactory got fixed), but it could do with another one.

The PR adds a test for the quoting behaviour and improves the documentation. Changing MultiLabelFactory will involve changing the serialized representation and so that needs a little more thought. We'll put it on the todo list for v5, but that's unlikely to be backported to a v4.3.x release.


Add comments and questions.

merged this so the mainline will have the test fixes, but as always please reopen with more questions!


Reenable FreeBSD 14 CI, and update definitions to match 14.0-RC1.

This reverts commit c9643c8768541b18017bbff90b0d6c582e402ed9.
New FreeBSD images have been available in gcloud since July.  Update the testing image to the latest, 14.0-BETA2

It looks like FreeBSD 14 has removed IFF_KNOWSEPOCH (https://cgit.freebsd.org/src/commit/?id=a6b55ee6be15a41792839095d19b589e25d0f7f7) and IFF_NOGROUP (https://cgit.freebsd.org/src/commit/?id=7ff9ae90f0bd133f56930858bb478a309da3982b) and also made some changes to struct tcp_info (https://cgit.freebsd.org/src/commit/?id=dc485b968ddeb070d23354f55164a8c336acf081).  I'll fix it.

Note that the change to struct tcp_info is actually a FreeBSD bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273902 .

@JohnTitor ready for review.

@bors r+

:pushpin: Commit b9671de6c93789c8ba42bac79e93c34b54e0e2df has been approved by JohnTitor
It is now in the queue for this repository.

:hourglass: Testing commit b9671de6c93789c8ba42bac79e93c34b54e0e2df with merge 5cd9cd7e716411fb9fec926c93a5c6d32115d74f...

:broken_heart: Test failed - checks-cirrus-freebsd-14

Hmm, weird. Has something been changed today?

Hmm, weird. Has something been changed today?

Nothing in the image.  Maybe some kind of merge error?  Let's see what happens when I rebase.

Seems fixed, thanks! @bors r+

:pushpin: Commit 2c3bf6fb5f716a165d5fdc906c13852316cc644e has been approved by JohnTitor
It is now in the queue for this repository.

:hourglass: Testing commit 2c3bf6fb5f716a165d5fdc906c13852316cc644e with merge 1a675aa1257ed095c8c51f99fbd79c08a6f08063...

:broken_heart: Test failed - checks-actions

Could you drop mips-related changes? Seems it's still broken :(

@bors r+

:hourglass: Testing commit 58121b2cc0592f6f55aa1ca4d2518be450730b63 with merge 0644a872dce01c7e744957444efa6aa6a0149848...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13, checks-cirrus-freebsd-14
Approved by: JohnTitor
Pushing 0644a872dce01c7e744957444efa6aa6a0149848 to main...

Yay!  Thanks for your patience, guys.


Link to Identifiers in html DRAFT is stale

I'm currently familiarizing myself with the WIS topic hierarchy (WTH) and noted that the link at https://wmo-im.github.io/wis2-topic-hierarchy/standard/wis2-topic-hierarchy-DRAFT.html#_codelists_bundle pointing to http://wis.wmo.int/spec/wth/1 is stale as http://wis.wmo.int/spec/ does not exist.
Best regards,
Johann

@gespau this is expected.  We do plan to resolve specification/conformance URIs as part of future updates..


Signed-off-by: Pritam Saha<EMAIL_ADDRESS>

Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Not sure this PR was meant for this repo. Also if that's your New Relic key I suggest changing it and revoking that token.


Merge PR when their commits are on target branch

Fixes #31433

Code needs some refactoring and probably unit tests. The complexity here is mostly the number of PR for the pushed branch(es). I would like to avoid querying the database multiple times for branch information and PR data but I haven't figured out how to do this in xorm with one join. I've assumed that Branch info is all that is needed but then I found AGit workflow type just now ... hence this PR is marked as Draft.
I haven't looked at the AGit workflow -- is this where the head branch in the DB refers to a CommitID?

OK, so AGit PR looks like a ref/ only thing added in https://github.com/go-gitea/gitea/commit/370516883717de0e6e2087c12d368eb1465ee3b0 and described in https://git-repo.info/en/2020/03/agit-flow-and-git-repo/


pose detection works

Also, major edits to the package's structure - more in line with conventional standard now. Making it so that its able to be installed on pypi.

This is due to an issue with installing opencv. For now I will make a note of that in the readme.
Changed variable name.
improved readme, now has pose data process

made some more changes after offline discussion. Thoughts?


day5 compilation error

Got this error in archlinux:
gcc -Wall -Wno-format -Wno-unused -std=gnu99 -static -m32 -I ../libc/include -ffunction-sections -nostdlib -nostdinc -fno-builtin -ffreestanding -fno-pie -c ../libc/stdio/stdio.c -o ../libc/stdio/stdio.bin
ld -m elf_i386 --oformat binary -o kernel.sys -T kernel.ld bootpack.bin io.bin pm.bin hankaku.bin ../libc/stdio/stdio.bin
ld: ../libc/stdio/stdio.bin: in function `sprintf':
stdio.c:(.text.sprintf+0x48): undefined reference to `__stack_chk_fail'

Temp workaround is to modify Makefile by adding "-fno-stack-protector" to CFLAGS:
CFLAGS += -ffunction-sections -nostdlib -nostdinc -fno-builtin -ffreestanding -fno-stack-protector

Hello, thank you for your issue about this problem.
I've added a stack protector placeholder function, and this issue should be fixed. The -fno-stack-protector option is also a choice to fix it.


Update tests. Part of UIORG-92.

yarn run v1.9.4
$ eslint .
/home/jenkins/workspace/folio-org/ui-organization/PR-146/test/ui-testing/locations.js
152:67  error  Strings must use singlequote             quotes
160:25  error  Missing semicolon                        semi
502:5   error  Block must not be padded by blank lines  padded-blocks
✖ 3 problems (3 errors, 0 warnings)
3 errors and 0 warnings potentially fixable with the --fix option.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.


Azure Government - Error loading property

Storage Explorer Version: 1.4.2
Platform/OS Version: Windows 10 and Mac OS High Sierra 10.13.6
Architecture: x64
Regression From: Was not using a previous version
Steps to Reproduce:

Connect to Azure Government subscription
Click on storage account name under Azure Government subscription
View Properties

Expected Experience:
Expect all functions, properties and details of a storage account to be enumerated
Actual Experience:
Can enumerate storage accounts and a limited set of the properties of the storage account but nothing underneath them nor functions. Have tried 3 different Azure Government subscriptions from 3 different computers.

Duplicate of #696.  There is a workaround outlined in #696 if you are blocked.  We are working on a build to revert back to the old API until all Azure supports the new API.  Should be available soon.


[Tabs] Allow tabs component to be controlled or uncontrolled

This will allow developers to programmatically set the selected tab. This issue will resolve #465.

Fixed by #1232


Util functions/test clean up

Share common util functions
Export fitBounds util
Consolidate test cases
Add test for distance scale

The following util functions are still not covered by tests:

getMercatorMeterZoom
getFov
getClippingPlanes

I'm not sure what they are used for.


feat: added bulk access control management

References
Add references/links to any related issues or PRs. These may include:

Fixes #781
Requires DSpace/DSpace#8844

Description
Added bulk access control management page, and access control tab in community, collection and item pages.
Instructions for Reviewers

Login
Go to an item and select the Access Control tab (http://localhost:4000/items/0d66c0aa-51dc-465a-91b5-6618992c83af/edit/access-control)
Update item or metadata access control conditions
Click Execute button
See the Process that was created and it's details

Checklist
This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

[ ] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
[x] My PR passes ESLint validation using yarn lint
[x] My PR doesn't introduce circular dependencies (verified via yarn check-circ-deps)
[x] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
[x] My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
[x] If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
[x] If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
[x] If my PR fixes an issue ticket, I've linked them together.

@enea4science : If possible could you rebase this to resolve the merge conflicts and make it easier for others to review?
Also, it appears this PR is adding a circular dependency & that's why all the tests are failing.  You should be able to see this locally by running yarn run check-circ-deps. We need that to be analyzed and fixed if at all possible. Thanks!

@enea4science or @atarix83 : Could you get the merge conflict resolved in this PR when you have a chance?

@enea4science & @atarix83 : You misunderstood my comment about date validation.  In you video, the problem that I reported is visible.
If you pause the video at about 4 seconds in, you can see the contents of the calendar popup.  Notice how it will allow you to select dates which are greater than 3 years (36 months).  So, for example, if you try to select June 30, 2026... the calendar popup will allow you to do that, even though it will throw an error as that date is invalid for embargoes.   The calendar popup will also allow you to select a date in 2027 or 2030 or similar, which should not be allowed.

@tdonohue
The other comments are now resolved.

Hello @artlowel
Your comments are now resolved.

Hello @tdonohue @artlowel
If this is alright can we merge it? Before other merge conflicts show up 😅

@enea4science : I would also like to merge this quickly, but it's waiting on the backend PR to get a second approval.  I'll do my best though to get this PR finalized or merged either Thurs or Friday.  Thanks for your patience.


No Mods to Technic Solder, So Please Adds Mods to Technic Solder

We Want To Add Mods To Technic Solder

????????????

I want to add mod to technic solder website

#356


[ROS2] Install ROS2_java on an EV3 Brick

Feature: Test ROS2 with Java on an EV3 Brick
It is necessary to analyze the difficult to use the Java library for ROS2

    Scenario: Test in local the library
        Given The library ros2_java
        Then It is necessary to test the classic example Listener & Talker
        And evaluate how to complex is the usage of the library for a Robotics environment.

ROS2_java:
https://github.com/esteve/ros2_java
Related issue:
https://github.com/esteve/ros2_java/issues/30

It is necessary to install this tool:
https://github.com/dirk-thomas/vcstool
https://packages.debian.org/sid/python-vcstools

vi /etc/apt/sources.list
deb http://http.debian.net/debian sid main

robot@ev3dev:/etc/apt$ sudo apt-get install python-vcstool
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package python-vcstool
robot@ev3dev:/etc/apt$

@jabrena vcstool can be installed directly from PyPI:
$ sudo pip3 install vcstool
However, since the Raspberry Pi is fairly slow, you can use CMake toolchain (for example https://github.com/ruslo/polly) and crosscompile ros2_java instead of compiling on the RPI itself. I can give you more details tomorrow about the whole process, but basically you pass --cmake-args -DCMAKE_TOOLCHAIN_FILE=PATH_TO_THE_POLLY_TOOLCHAIN -- to ament and follow https://github.com/ruslo/polly/wiki/Toolchain-list#raspberrypi2-cxx11 (similar to the ROS2 bindings for the iPhone https://github.com/esteve/ros2_objc#ios)
I've used this to crosscompile ROS2 to the RaspberryPi and the ODroid and it works pretty well.

Yes, of course, I will do it.
If you like, I will test in this order:
OSX > Raspi 3 > EV3 Brick.

It is not a priority


Network Schema doesnt support fabric node chaincode

Describe the bug
The network schema doesn't have node in the enum so fails the build, it says on the docs that it's supported? Is it?
https://github.com/hyperledger/bevel/blob/28ff161b268d5869c131be5c81c86eaebe602e3e/platforms/network-schema.json#L677
I'll add a PR if it is.

Seems like a miss, please send a PR. I will assign this to you.


Preserve props on partial reloads

This PR introduces an ability to preserve properties on partial reloads even if they aren't specified on a request.
Inertia::preserveProperties(['alert']);

While only is great within a context, there could be a global state with properties that need to present on every get request. So, it makes sense to control them from a backend to ensure that required props are always present on the response.
Examples:

Alert notifications
Popups (onboarding)
Auth user data

So, any global state that's independent of a current context.

See https://github.com/inertiajs/inertia-laravel/pull/621


[flutter_tools] _flutter.renderFrameWithRasterStats: (-32601) Unknown method

on beta/3.1.0-9.0.pre
Command: flutter run -d chrome
RPCError: _flutter.renderFrameWithRasterStats: (-32601) Unknown method "_flutter.renderFrameWithRasterStats".
at new _OutstandingRequest(vm_service.dart:1742)
at VmService._call(vm_service.dart:2255)
at VmService.callServiceExtension(vm_service.dart:2226)
at VmService.callMethod(vm_service.dart:2208)
at FlutterVmService.callMethodWrapper(vmservice.dart:453)
at FlutterVmService.renderFrameWithRasterStats(vmservice.dart:552)
at ResidentHandlers.debugFrameJankMetrics(resident_runner.dart:692)
at <asynchronous gap>(async)
at TerminalHandler.processTerminalInput(resident_runner.dart:1741)
at <asynchronous gap>(async)

@iskakaushik should this RPC method never be called on web?

@iskakaushik friendly ping

@christopherfujino sorry, this fell off my radar. This method isn't implemented for web. Is there a way to disable it on web?

@christopherfujino sorry, this fell off my radar. This method isn't implemented for web. Is there a way to disable it on web?

Cool, I'll ask someone on the tools team to look into disabling this.


added enforce privileged on the namespace resource for talos clusters

security-minded clusters don't allow running privileged pods unless a label is set on them

these _topo-ns.yml files look, ehm, suspicious?

LGTM 🔥


Consolidate Kotlin sample data calls?

I was looking at the kotlin sample module, and I noticed that there are three activities and all pull them a different way:

CommitsActivity uses co-routines
MainActivity uses an apollo callback
RepositoryDetail uses RxJava

As a new person looking at the sample, this can be confusing and not really clear what the "best practice" is. I was wondering if we could:

Refactor to one consistent option
Pull this flow out into a GitHubRepository interface, and then have three implementations like ApolloRxJavaService, ApolloCoroutinesService, ApolloCallbackService and people can see those three individually, rather than a mixed bag.

I'm happy to contribute either, but I wanted to ask here first if the three options were intentional - because if that is what we want to show people I would refactor in a way to ensure that happens.

It was not intentional. Your suggestions sound great, feel free to open a pr with a refactor.

Will do!

PR: https://github.com/apollographql/apollo-android/pull/1302


How to build the mmdetection3d in google colab?

Is there any tutorial about building the mmdetection3d in colab?   Many thanks!!!!! @MMLAB-CUHK @encore-zhou @hellock

@liyang0522 Did you find any tutorial on building the mmdetection3d in colab?

found then share mate


Add an rpm dependency on openscap-scanner

@jrafanie @carbonin @simon3z please review

@moolitayer  Looks good. Is this in the base centos OS repo or somewhere else?  For future reference, it's helpful to list the yum repo that a rpm can be found.

@moolitayer Looks good. Is this in the base centos OS repo or somewhere else? For future reference, it's helpful to list the yum repo that a rpm can be found.

@jrafanie I believe it is in the base repo:

http://mirror.centos.org/centos/6/os/x86_64/Packages/openscap-scanner-1.0.10-3.el6.centos.x86_64.rpm
http://mirror.centos.org/centos/7/os/x86_64/Packages/openscap-scanner-1.2.5-3.el7.x86_64.rpm

LGTM, thanks @moolitayer, @simaishi @carbonin are you fine with this?

Yes, looks good.

:+1:

:tada:


change open prop behavior

changes open prop to close the modal if open is set to false. (#498)

@Talor-A give me a unit test and I'll merge it, thanks.

Sure! I hope to get around to it next week


operation.image_overlay

I try to create a RGB overlay of three Images, as described in operations/element.py:
parrot = hv.RGB.load_image('/home/a/src/holoviews/doc/assets/macaw.png', array=True)
rgb_parrot = hv.RGB(parrot, label='Macaw')
red = hv.Image(parrot[:,:,0], label='R')
green = hv.Image(parrot[:,:,1], label='G')
blue = hv.Image(parrot[:,:,2], label='B')
hv.operation.image_overlay(red*green*blue)

---------------------------------------------------------------------------
NotImplementedError                       Traceback (most recent call last)
<ipython-input-11-f356536b857c> in <module>()
----> 1 hv.operation.image_overlay(red*green*blue)

/home/a/src/param/param/parameterized.pyc in __new__(class_, *args, **params)
   1845         inst = class_.instance()
   1846         inst._set_name(class_.__name__)
-> 1847         return inst.__call__(*args,**params)
   1848
   1849     def __call__(self,*args,**kw):

/home/a/src/holoviews/holoviews/core/operation.pyc in __call__(self, element, **params)
    109
    110         if isinstance(element, ViewableElement):
--> 111             processed = self._process(element)
    112         elif isinstance(element, GridSpace):
    113             # Initialize an empty axis layout

/home/a/src/holoviews/holoviews/operation/element.pyc in _process(self, raster, key)
    239     def _process(self, raster, key=None):
    240         specs = tuple(el.strip() for el in self.p.spec.split('*'))
--> 241         ordering, strengths = self._match_overlay(raster, specs)
    242         if all(el is None for el in ordering):
    243             raise Exception("The image_overlay operation requires at least one match")

/home/a/src/holoviews/holoviews/operation/element.pyc in _match_overlay(self, raster, overlay_spec)
    228         for el in elements:
    229             for pos in range(len(overlay_spec)):
--> 230                 strength = self._match(el, overlay_spec[pos])
    231                 if strength is None:               continue  # No match
    232                 elif (strength <= strengths[pos]): continue  # Weaker match

/home/a/src/holoviews/holoviews/operation/element.pyc in _match(cls, el, spec)
    203         spec_dict = dict(zip(['type', 'group', 'label'], spec.split('.')))
    204         if not isinstance(el, Image) or spec_dict['type'] != 'Image':
--> 205             raise NotImplementedError("Only Image currently supported")
    206
    207         sanitizers = {'group':group_sanitizer, 'label':label_sanitizer}

NotImplementedError: Only Image currently supported

Is it possible to create an RGB image from three Images?
I would like to do it from a HoloMap, with three Rasters, which do not have the right labels.

The image_overlay operation has a name that may suggest that it what you want, but actually that designed  for a fairly special case that wouldn't be worth explaining here. What you want is directly supported by the RGB`` constructor:
parrot = hv.RGB.load_image('doc/assets/penguins.png', array=True)
rgb_parrot = hv.RGB(parrot, label='Macaw')
red = hv.Image(parrot[:,:,0], label='R', vdims=[hv.Dimension('Intensity', range=(0,1))])
green = hv.Image(parrot[:,:,1], label='G', vdims=[hv.Dimension('Intensity', range=(0,1))])
blue = hv.Image(parrot[:,:,2], label='B', vdims=[hv.Dimension('Intensity', range=(0,1))])
hv.RGB(red*green*blue)

Note that you need the dimension ranges as we don't want to assume the Image data is always normalized in some way but we need to know the relative strength between the color channels. I hope that helps!

Not sure why this is still open, closing.


QdrantDocumentStore type errors when adding to DocumentWriter

Describe the bug
"QdrantDocumentStore" is incompatible with protocol "DocumentStore"
    "write_documents" is an incompatible type
      Type "(documents: List[Document], policy: DuplicatePolicy = DuplicatePolicy.FAIL) -> (int | None)" cannot be assigned to type "(documents: List[Document], policy: DuplicatePolicy = DuplicatePolicy.NONE) -> int"
        Function return type "int | None" is incompatible with type "int"
          Type "int | None" cannot be assigned to type "int"
    "delete_documents" is an incompatible type
      Type "(ids: List[str]) -> None" cannot be assigned to type "(document_ids: List[str]) -> None"
        Parameter name mismatch: "document_ids" versus "ids"

To Reproduce
Run type-checking on this code:
from haystack_integrations.document_stores.qdrant import QdrantDocumentStore
from haystack.components.writers import DocumentWriter

store = QdrantDocumentStore()
writer = DocumentWriter(store)

Describe your environment (please complete the following information):

OS: macOS 14.5
Haystack version: 2.4.0
Integration version: 4.2.0

I agree, these are bugs. Thanks for reporting them.
Luckily, they do not seem hard to fix.
Would you like to open a PR?
Let us know... Otherwise, we will fix them soon.

Sure, I’ll take a look at it.
On Fri, Aug 30, 2024 at 3:18 AM Stefano Fiorucci @.***>
wrote:

I agree, these are bugs. Thanks for reporting them.
Luckily, they do not seem hard to fix.
Would you like to open a PR?
Let us know... Otherwise, we will fix them soon.
—
Reply to this email directly, view it on GitHub
https://github.com/deepset-ai/haystack-core-integrations/issues/1039#issuecomment-2320453094,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABTUFRDATFZ7TFOSJNZN7LZUATEBAVCNFSM6AAAAABNLI67MSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRQGQ2TGMBZGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Submitted a quick PR. Please note that it technically has a breaking change because of an argument name change.


Add solver_microservice cookbook with setup recipe

It installs pipenv, sync assignment repo and starts microservice
https://dekeo.atlassian.net/browse/ALPHA-4292

closing for now


test all script, in different envirorments

All the scripts right now are used only under Windows.
Can be useful to expand compatibility at least with MacOs.
Desiderable is to test it under ubuntu and other linux distro.

Close thanks to #21


Added documentation for 'bidRequestsCount' key in bid request

Documentation for Prebid.js#2940

was released with 1.20


Added functionality

This list could be much more useful if it contained an object for each coin instead of a parameter list:
{
    "name" : "Bitcoin",
    "symbol" : "bts",
    "uri" : {
        "coin": "bitcoin",
        "amount" : "amount",
        "message" : "message",
        "label" : "label"
    }
}

The URI object would be particularly useful because it's required for wallets that present QR codes. These URI's don't use the symbol, they use a long name for the currency an those lists aren't easy to find freely. Also, many coin URI's have a different set of terminology for the message. Some call it a memo. So, if you could normalize this through this library, it would be pretty powerful as well.

Nice idea! I am all for making this list more useful. PR welcome, otherwise I can try to get to this sometime soon.

Maybe it should be a /v2 document in case others are using it as it? Happy to issue a PR if you can devise a way for it to be backwards compatible.

Hiya boyz. Joining the pack here. and great work so far.
Regarding backwards compat, If the 2 original parameters remain the same and at their positions, any added one would not break any "proper" integration.
An interim period where both co-exist, with a message to upgrade to latest version and an end-of-life for the root parameters would go a long way.
I can see many usages of the uri data, and even on top of that, consider 'protocol' (POS, POW etc), 'Algorithm' if mined (POW).
Willing to contribute the pitiful spare time i got ;)

@angelexevior thanks for the kudos! :)
How do you see the current list co-existing with this list that was proposed by @wmbutler above?
The current list has a structure of:
{
  "42": "42 Coin",
  "300": "300 token",
  "365": "365Coin"
}

whereas a new structure was proposed of:
{
    "name" : "Bitcoin",
    "symbol" : "bts",
    "uri" : {
        "coin": "bitcoin",
        "amount" : "amount",
        "message" : "message",
        "label" : "label"
    }
}

So I am not seeing a way to make these two lists compatible, unless I am missing something?

@angelexevior, another option is just maintain a few different lists, and the user just pulls in the list they need. There are use cases for having different types of lists (such as #16), so I would not be against having different lists, but then again, its more work. Perhaps there is some value in keeping one list, and then let the user generate their own ideal list if they need something a bit more stripped down. Either way is fine with me.

Two lists is probably not a great idea. What about this?
{
    "bts" : {
      "name" : "Bitcoin",
       "uri" : {
          "coin": "bitcoin",
          "amount" : "amount",
          "message" : "message",
          "label" : "label"
       }
    }
}

@wmbutler I like your proposed structure
{
    "bts" : {
      "name" : "Bitcoin",
       "uri" : {
          "coin": "bitcoin",
          "amount" : "amount",
          "message" : "message",
          "label" : "label"
       }
    }
}

👍

D'accord @wmbutler @radiovisual
Just had a thorough look in the code. Correct me if i'm wrong but the list is just a flat file, not generated by someone automatically(or semi).
A good way forward would be to centralize the list db into something we can utilize to generate any sort of list we want... Perhaps a mysql, a csv, even a google spreadsheet (Use APIs to pull data), so we can add any sort of additional data, and generate any list structures we see fit.
Also, consider adding a small API framework to it (REST) for a wider reach.
*I can suggest a framework i deved in the past.
**I would volunteer to host the API and mini-site

@angelexevior

Correct me if i'm wrong but the list is just a flat file, not generated by someone automatically(or semi).

This list is generated semi-automatically by running the npm run build. It grabs the latest currency data from the cryptocompare API to generate the flat list

A good way forward would be to centralize the list db into something we can utilize to generate any sort of list we want

This is one of the utilities of a flat list like this, where anyone that pulls this list into their project can use it to generate anything they might need. Feel free to build/host anything you like that uses this list (help is always welcome) in a separate repo so we can still keep this flat list a small dependency. I would love to see some tooling spring up around this list.

RealBank(RBT)-1ede817398a84d4c8533f423444681cf


🚀 Feature: Backstage Theme Creator

🔖 Feature description
Customizing the theme of Backstage can be tricky. Not only are there several Material UI ThemeOptions, but there are also custom options for Backstage that have been added over time. It is not always easy to understand which theme variables are used where and what the impact of changes will be. Furthermore, customizing the theme can be tricky for people without knowledge of TypeScript & Material UI.
With the Backstage Theme Creator, you can customize the theme variables of Material UI & Backstage through both a UI and a code editor on a single web page. The application is designed to make it easy for anyone to create a custom theme.
✌ Possible Implementation

MVP: https://backstage-theme-creator.vercel.app
The current MVP was created in a separate repository: https://github.com/tudi2d/backstage-theme-creator. With forking the original [mui-theme-creator](https://github.com/bareynol/mui-theme-creator) project, there are a lot of nice features supported out of the box, but also a lot of legacy code that needs to be either removed or updated.
Features:

Monaco Code Editor with code highlighting & suggestions for Backstage ThemeOptions
UI to change Material UI palette colors, font & add common patterns
Save & load different themes
Visualize most Material UI components separately to see the impact of theme changes

The MVP repository is open for contribuiton. If there is genuine interest in the idea I would be happy to move the repository to the Backstage organisation.
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

This is so awesome! 🔥

+1 really awesome work! 🔥

I feel like this should be shared in some of the other forums we have, not sure if this came up in the Community session today? I missed most of it.

Yeah - might makes sense - I will consider it.

I feel like this should be shared in some of the other forums we have, not sure if this came up in the Community session today? I missed most of it.

@awanlin I suggested the same yesterday 😄


Supervision::Behaviors, and ::Configuration elements.

This celluloid/celluloid#511 refactor process has been a bit involved over the last few days. I've refactored twice so far, only pushed pieces of it, and I am going for a third and final refactor. A lot changed, but it was mostly theoretical, trying to correct the design. I'll just skip to the end result design.
I'm posting this for advanced warning, feedback, etc. Please tread carefully as I'm trying to clarify a pretty complex aspect of the system. It's sort of an ActorSystem superstructural layer, and yet similar to Call and Proxy in how far-reaching and potentially convoluted if not done right the first time. On that note, I am going to do the new way first, then backport. I was backporting simultaneously, and I that was pure insanity. I will keep the existing tests unchanged, and add tests for the new areas. And I will populate the depreciation sections with the monkey patches needed to keep things going in 0.16.0 ... and from what I've seen, monkey patched or not, it still a lot faster and stronger.

Here are the key elements I am going to build tests for, then flesh out. If one is using this in backported mode, none of this will be exposed. The standard behaviors reveal none of the complexity, but benefit from the greater efficiency, flexibility, and robustness:

Configuration object ( #8 ) parameters.

:type [ required ] : the class of Actor. More in Container on this one.
:as [ optional ] : the registry stored name of the Actor.
:args [ optional ] : an array of arguments to send the Actor(s) at initialization.
:block [ optional ] : a block passed all the way into Actor initializations.
:injections [ special, plugin layer ] : More in Injections and Behavior
:method [ special, plugin layer ] : More on this in Behavior objects.
:size  [ plugin ] : More on this in Behavior objects: Pool.
:routers [ plugin ] : More on this in Behavior objects: Coordinator.
:supervise [ special, plugin layer ] : More on this In Behavior objects: Tree.
:registry [ optional ] : override the default registry ( Services::Public )

Aliases:
:name => :as
:kind => :type
:pool => size

:class cannot be used as a parameter.
Each parameter is also a method of Instance and Configuration objects.
class is a keyword, so it cannot be used as a method. The Configuration parameter methods point to the specific Instance being configured at that moment. I'm particularly excited to show how easy and powerful it is to have Actors build their own Instances, Containers, Trees, etc.

Foundational objects:

Container a module, which if included turns the object into a foundry of sorts.

Right now that's two objects who can spawn supervised Actor(s):

Configuration
Group ( this one is going away, with legacy protection...
because Group is both too vague and inaccurate,
as it could be supervising one Actor only,
or be an entire Pool or Coordinator.

This is where the repeated refactoring came in.
Container will become a class. More in Behaviors...

Configuration which wraps Instances and keeps them ordered.

Mostly class methods, and a collection of ordered Instances kept static.
Can be reused, sent between scopes, etc. It is not an Actor. It is blueprints.

Instances are the point of Configuration just as Member(s) are the point of Containers.

Injections create plugins.
Right now we have PoolManager living on by passing a Hash of :injections into Member who offers special handling, by special classes insertion points at certain points in the flow of the Member lifecycle:

:before_initialization : New injection allows for a complete plugin system.
:after_initialization : Previous way of turning a Pool into a supervisor.
:before_start: Also pre-existing injection used by Pool.
:before_restart: Unused, left there for the future during the Pool refactor.

Behaviors bring in Injections and mix-in plugin classes.
Using Pool ( no longer PoolManager except in backported mode ) as the model, there will also be a completion of Coordinator and the transformation of Group into Tree -- with the essential pieces from Group staying in Container and being provided to all Behavior objects, as well as being itself in abstract form ( for a la carte Supervisors and the generic Group of supervised Actors )
Using Injections then, the catching parameters as flags, certain Behaviors can be called the old way -- Actor.pool or PoolManagerDescendent.new -- but are much more easily instantiated by just using a parameter with implications. For example :size ( or it's "on the nose" alias :pool ) would be caught by :before_initialization high-performance classifier, and turned into a Supervision::Behavior::Pool ... same for :routers and Supervision::Behavior::Coordinator and :supervises becoming Supervision::Behavior::Tree.

All of this is being done with #11 in mind, which is a lot easier than it sounds, if supervision trees are back, and/or there's a :root supervisor again. That right there changes almost everything.

Supervision::Services and the return of the Tree
Now, there are two supervisors spawned by default, which is actually exactly as many as before, by default; except one is supervising the other, and one is the general population supervisor.
These are part of the Supervision::Services::Root supervision Container ( was Group ); in order of instantiation:

:notification_fanout ...is Celluloid::Notifications::Fanout
:default_incident_reporter ...is Celluloid::IncidentReporter
:group_manager ...is Group::Manager ( part of why Supervision::Group became Supervision::Container also... less ambiguity going forward )
:public_services ...is Supervision::Services::Public ...

This one is not supervising anything at start. It could even be run! at first use, but all the one-off unspecifically instantiated Actor supervision happens here... all the unclaimed supervisors, rather than spawning an entire Container for each Actor ... if that behavior is desired, that can still be done, but it's no longer the default.
Reason being, it's caused radical increase of threads in use those instantiating many single Actors they don't particularly care about, but need to be supervised nonetheless.
Also, because supervisors have been dying and never returning ( #2 ).

:servers ...[ future ] Once Reel and I'd imagine celluloid-dns adapt to the celluloid-supervision refactor.

This "trunk" and these "branches" are a primitive beginning for the new supervision Tree implementation, starting from one Root class, then expanding in multiple ordered layers.

As I endure the process of this gem and I beating the crap out of each other, the prospect of people enjoying building supervisors and those complex or simple supervisors always remaining stable, flexible, efficient, is pretty exciting. I don't expect this next refactor pass to be non-negotiable, but I'd like to get it down before getting into the minutia of how it all works. The code speaks for itself, and we can piece it apart that way. But for now, anything that jumps out at you: hit me with what strikes you.

/cc: @tarcieri, @niamster, @ioquatix, @asmod4n

Done with this, need to document this though.

Should :default_incident_reporter just be :incident_reporter?

I'm not trying to bike shed :)

No @ioquatix I appreciate the scrutiny. I've changed it to that, grepped all the libraries for use of that Symbol, and am testing with the changed ( better ) name.

Can you explain :servers in relation to rubydns

@ioquatix now there are no "unsupervised supervisors" unless we explicitly decide to create a supervisor outside the root supervision tree.
This piece is fledgling/conceptional right now, but there are at least two "service containers" going all the time: the root supervisor, and the public services container, which is a child of the root supervisor. I'm talking about another child of the root, parallel to the public services ( which are generally a la carte supervised actors ) ... So if you instantiate Reel supervised, or RubyDNS for example, it would supervised by the :servers service.
If your server fails, the servers service restarts it -- not a one-off supervisor like now. And if the servers service fails, the root restarts that container. This addresses #2 but also brings in #9 -- but like I said it's still a work in progress.
There is no :servers service at the moment, that is vaporware until 0.17.5 in my mind... once I double-back to update Reel to run celluloid/current non-backported to 0.16.0 behavior.

@ioquatix to automatically link-in to the :servers service, I'm thinking something like server! in the class definition below include Celluloid could do it.. just for example.

And the :servers service would not exist until there were one or more servers present, and instantiated.

I like the idea of servers, except it might encourage people to depend on global state. Does it make sense for there to be shared global actors? I can see arguments both ways. What's so bad about instantiating your own supervised/linked DNS resolver and just using that directly? A global shared DNS resolver maximises the value of cached records - on the other hand, this might be a security problem (cache poisoning) or a contention issue..
A name like server! while simple and obvious, also might be too generic. Similar to how Celluloid::Logger breaks all existing code that expects Logger to be ::Logger (that's since been fixed right? Moved to Celluloid::Internals?), server! might be too generic.. perhaps something with celluloid in the name, e.g. supervised_celluloid_server! or something a bit more specific?
Perhaps we need to discuss the idea of servers in more detail once celluloid-dns takes shape.

Does it make sense for there to be shared global actors?

Erlang has them

Does that mean yes?

Works for them :stuck_out_tongue_winking_eye:

Is there any reason to NOT have a global DNS resolver?

@ioquatix I think there's a misunderstanding, but I agree supervised_service! :servers would be better than servers!
The misunderstanding that might be happening, is that there's no real change other than increased supervision. We already had shared global actors a la Celluloid::Actor[:registry_key] unless I'm misreading you there, what is added is now we have a supervision tree again. When I get back later I will post a diagram and start diagramming things more.

@ioquatix this is more what I was trying to say:

.services actors is where your RubyDNS actor would be supervised, unless you distinguished it as to be supervised by .servers ... and I'm just proposing two ways to do that:

Celluloid.servers.supervise as: :blah, type: Celluloid::DNS

or Celluloid::DNS.supervise as: :blah, branch: :servers

Adding supervised_service! :servers to the `Class

This looks awesome.

Glad you think so! This functionality is "in" but not really properly documented, or demonstrated. I will remember to do that in Reel so you can port that over to Celluloid::DNS!


On SP update, node images are updated

Nothing on this document talks of the process requiring a reimage of the nodes on service principal update. Could be updated to reflect this.

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

ID: 0b842222-f6ac-5266-227f-7e400610e07b
Version Independent ID: 429cd3bf-2691-f633-2e0d-e70e5d8d0e03
Content: Reset the credentials for a cluster - Azure Kubernetes Service
Content Source: articles/aks/update-credentials.md
Service: container-service
GitHub Login: @mlearned
Microsoft Alias: mlearned

Since AKS Release 2021-01-25, the Reset Service Principal operation now perform a node image upgrade in-order to update the configuration of each agent node.
The link you mentioned does have this behavior documented here:

Hope this helps!


Severe mouse slowdown/latency when my Unity app runs, but only on one computer, not another

I'm getting extremely slow, laggy, barely controllable mouse movement when my Unity build is running. When I run the same app on my older computers however, it runs perfectly.
The mouse movement is better when over the Unity app window, but still slow.
I've narrowed it down to the RawInput code, but again, only one machine runs it slow; the other two (substantially weaker) machines run it with RawInput perfectly.
I've tried to illustrate the difference in mouse control by drawing little circles, first inside the Unity app window, the outside. The RawInput script is inactive in the first gif, active in the second. You can see in the second how the mouse goes flying off at the end, this is a result of the latency. How can I narrow down the cause?

Make sure run in background is enabled in build settings.

Ok, I tried changing the DPI with my mouse buttons with no change. Thanks for the suggestion, let me know if you think of anything else I can try. Just strange it only affects my most powerful machine... 🤔

Try removing the mouse hook to check whether it's related with mouse at all: https://github.com/Elringus/UnityRawInput/blob/master/Assets/UnityRawInput/Runtime/RawInput.cs#L75

I'm having the same problem, when I try to run my unity application at low framerates to save GPU usage, it ends up affecting the mouse. It seems like the fps is limiting how many times per second the mouse is allowed to update/move. Its working fine when I'm using the app in the unity editor, its only when I make a final build that I'm having problems. And yes removing the mouse hook removes the mouse lag, but then I'm not able to detect mouse clicks anymore.

Weird that FPS cap is affecting this. The hook processing shouldn't depend on Unity's render loop in any way.
Ideally we would opt-out of receiving mouse position callbacks, but not sure if that's possible.

For now I will just manually set the framerate to something higher while I'm checking for Raw Input over a button, but I would love a better solution, since this makes the GPU usage of the application go from 1.5% to 10-15%.

Thank you guys! I set my project to sync every V-blank and it resolved the mouse lag. As far as I'm concerned this issue can be resolved. Should I close it?

sync every V-blank and it resolved the mouse lag

So it looks like the render loop is actually affecting input hook procs (or vice versa).
Let's keep the issue open; maybe someone will figure how to solve this or at least why this is happening.

The slowdown happens because hooks are processed on Unity's main thread. The best practice is to spawn a separate thread to handle the event loop like described here: https://stackoverflow.com/a/52201983
Alternatively you can also change HookType.WH_MOUSE_LL to HookType.WH_MOUSE in the RawInput class.
Personally, since I only needed to catch the mouse events in the editor itself, and not outside of it, I've changed the SetHooks method to look like this:
private static void SetHooks ()
{
    uint threadId = Win32API.GetCurrentThreadId();
    hooks.Add(Win32API.SetWindowsHookEx(HookType.WH_KEYBOARD, HandleKeyboardProc, IntPtr.Zero, threadId));
    hooks.Add(Win32API.SetWindowsHookEx(HookType.WH_MOUSE, HandleMouseProc, IntPtr.Zero, threadId));
}

This limits the amount of processing needed to a point where no separate thread is needed. Of course my change is useless for people who need actual global events, but this helped with lag in my case so I'll leave it at that.


Origin/feat/#198 fixing the player's spawn point

Purpose of this PR:
move the player's position to the startDoor prefab. also make the player face the startDoor prefab.
How to test:
in any scene when the room transition happens, the player will move to the startDoor prefab's position and face the door.
links:
https://github.com/SillyBusinessInc/SillyBusinessGame/issues/198

I am going to merge it even though there are no reviews yet
but i am doing this because this has been open for a while now & the functionality it is trying to fix has been fixed & it is crusial for a functional game.


Implement gql in Extension method on String

With the release of Dart 2.7 we can now use extension methods. I would be slick if we could create an extension method on the String type to run the gql.

Wow, that's cool and would make it easier to parse documents to document nodes.

neat idea but I feel like 'longquery'.gql would be less legible than gql('longquery'). Maybe a builder api for options could be cool though.
class extension GqlAble on String {
  get gql => _gql(this);
}

idk I think we should close this and leave it in "userland"


doc: ByteBuffer improvements

A few improvements to the docs for ByteBuffer.
Motivation:
Improve the docs.
Modifications:

ByteBufferAllocator().buffer is not static.
Datatypes in get should be capitalised like Data already is.
readerIndex/writerIndex should be documented under sequential access, not random access.
changeCapacity() parameter is to not capacity.

Result:
More accurate documentation.

@swift-nio-bot test this please

@ianpartridge let me know once addressed and rebased .

@normanmaurer Done.

@swift-nio-bot ok to test


System check issues when running: manage.py runserver

django-content-settings: v0.10
Django: 4.2.9 & python 3.11.8
I'm getting the following warnings when running "manage.py runserver":
System check identified some issues:

WARNINGS:
content_settings.ContentSetting: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'.
	HINT: Configure the DEFAULT_AUTO_FIELD setting or the StaticContentConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'.
content_settings.HistoryContentSetting: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'.
	HINT: Configure the DEFAULT_AUTO_FIELD setting or the StaticContentConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'.
content_settings.UserTagSetting: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'.
	HINT: Configure the DEFAULT_AUTO_FIELD setting or the StaticContentConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'.

System check identified 3 issues (1 silenced).

will be released in 0.10.1

2 of the 3 warnings have been resolved with v0.10.1. One remains:
System check identified some issues:

WARNINGS:
content_settings.UserTagSetting: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'.
	HINT: Configure the DEFAULT_AUTO_FIELD setting or the StaticContentConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'.

System check identified 1 issue (1 silenced).

@richardbrockie sorry, I've missed this one

@oduvan All working - thanks for considering my suggestions. This is a really useful package - I will be using django-content-settings to manage some parameters that are currently treated as constants in my Django app.
It's just a few bools & ints, so nothing too sophisticated. Changing them has required editing the code and redeploying, slow and annoying. I started developing something similar to d-c-s, but your package is much better than my crude effort. Thanks!

Your suggestions are awesome! I really appreciate your help.


Running Designer Locally Fails With 500 Error

xgovformbuilder-error120721.txt
Describe the bug
Unable to run Designer application locally.
To Reproduce
Clone repo in new directory
Run "yarn" in command-line
Once completed, run "yarn build" in command-line
Once completed, run "yarn designer start" from the command-line
Browse to http://localhost:3000/
Below error is shown:
{"statusCode":500,"error":"Internal Server Error","message":"An internal server error occurred"}
Expected behavior
Designer homepage is shown.
Screenshots
Attached.

Repository
Designer.
Desktop (please complete the following information):

OS: MacOS
Browser: All
NPM: 6.14.12
Yarn: 2.4.0
Node: 12.22.1

Additional context
Seems its searching for a designer.html which doesn't exist within the compiled "dist" directory.

Hi @jenbutongit ,
I'm having the same issue. Can you please share how did you manage to solve it?

hey @neculaionutni,
could you first let me know which git tag/version you are on?
For the latest versions of XGovFormBuilder you must be running node 16. Try these steps, and show me any stack traces if you get any.
If you want to run this via yarn/node:

run yarn
run yarn install model
run yarn model build
run yarn designer build
run yarn runner install
run yarn runner build
run yarn runner dev (or yarn runner start)
run yarn designer dev (or yarn designer start).

Alternatively via docker
docker compose up will start redis, designer and runner.


Angular Project Template does not work with ng commands

Issues with Existing Topic
https://docs.microsoft.com/en-us/aspnet/core/spa/angular?tabs=netcore-cli
This comment is as of April 7, 2018, and pretty much spells out the issue:
Well... This is no good... Installed .NET Core SDK 2.1.
Ran "dotnet new angular -o myproject"
went to the newly created directory and ran NPM install.
*Everything is great... ran the application and it loads on my web browser
Then went to the ClientApp directory and ran "ng g c mycomponent"
and got this error: "Unable to find any apps in .angular-cli.json"
Looked at the directory and noticed that there is no .angular-cli.json file at the root of the ClientApp directory.
Tried it twice BTW, and same results. I know I can go an create the file, but I'm pretty new to angular, and now I got to break my head because the template is not complete.
So basically, there is something missing from the template install.

Moved issue to https://github.com/aspnet/templating/issues/473 for review.


Document that Foreman secretly sets the PORT environment variable to 5000

I've just spent an afternoon debugging why Puma would start on a different port when introducing Foreman to the application.
Hindsight is of course 20/20, but it took quite a long time to figure out that the culprit here was actually Foreman.
It would be very beneficial if somewhere (like e.g. on the man-page) the behaviour that Foreman sets $PORT to 5000 for the top process in the Procfile.

It is explained on the Getting Started page.

Port Assignment
Foreman starts port assignments at 5000 by default, and assigns them in blocks of 100 per process type in the order used in your Procfile
For the Procfile used at the top of this post, web.1 would be assigned port 5000, worker.1 would be 5100, and clock.1 would be 5200. If you were ran 2 web processes, web.2 would be assigned 5001.
You can specify an alternate starting port for foreman to use with the -p option.


"refer back" vs. "refer"

In the lesson on Basic Javascript: Record Collection, I think that the term is "refer" instead of "refer back". I read in a Reader's Digest Magazine that the latter is redundant.

I don't think there's a problem with 'refer back' here. I read this article - and specifically this sentence...
“In 1995, 65 percent of the Panel disapproved of this construction, but by 2011, 81 percent accepted it in the sentence To answer your question it is necessary to refer back to the minutes of the previous meeting.”
And in the case of the challenge, users are being asked to "refer back" to a previous challenge, so back has some purpose here I think.

Okay.
On Thu, Apr 9, 2020 at 3:55 PM Tom<EMAIL_ADDRESS>wrote:

I don't think there's a problem with 'refer back' here. I read this
article https://www.grammarphobia.com/blog/2013/06/refer-back.html -
and specifically this sentence...
“In 1995, 65 percent of the Panel disapproved of this construction, but by
2011, 81 percent accepted it in the sentence To answer your question it
is necessary to refer back to the minutes of the previous meeting.”
And in the case of the challenge, users are being asked to "refer back" to
a previous challenge, so back has some purpose here I think.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/issues/38519#issuecomment-611722941,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AORKPDGMK2RFNMHQIIJZBITRLYR2ZANCNFSM4ME46OVQ
.

Thanks for reporting. We can leave the issue open for now in case someone else wants to weigh in.

I think refer back makes sense here.


Docker: can't build and start docker according to documentation

According to this:
https://github.com/neo-project/neo-node#build-into-docker
There is a way of build docker image from neo-cli directory.
cd neo-cli
docker build -t neo-cli .

This won't work since neo-cli doesn't contain Dockerfile.
But I was able to build docker image from the root repo. And
docker run -p 10332:10332 -p 10333:10333 --name=neo-cli-mainnet neo-cli shuts down immediately and doesn't have any logs.

Thanks for your suggestion, we will fix it.


Coverage is only collected from javascript files

💥 Regression Report
Coverage data is only collected from javascript files, but not from e.g. vue files, although configured to collect data from vue files as well.
Last working version
Worked up to version: 24.9.0
Stopped working in version: 25.1.0
To Reproduce
Steps to reproduce the behavior:
Have a repository with js and vue files and configure jest to report coverage for both file types using this configuration:
"jest": {
	"moduleFileExtensions": [
		"js",
		"vue"
	],
	"moduleNameMapper": {
		"^@/(.*)$": "<rootDir>/src/$1"
	},
	"testEnvironment": "jest-environment-jsdom-sixteen",
	"transform": {
		"^.+\\.js$": "<rootDir>/node_modules/babel-jest",
		".*\\.(vue)$": "<rootDir>/node_modules/vue-jest"
	},
	"snapshotSerializers": [
		"<rootDir>/node_modules/jest-serializer-vue"
	],
	"setupFilesAfterEnv": [
		"./tests/javascript/unit/setup.js"
	],
	"coverageDirectory": "./coverage/",
	"collectCoverage": true,
	"collectCoverageFrom": [
		"<rootDir>/src/**/*.{js,vue}",
		"!**/node_modules/**"
	],
	"coverageReporters": [
		"json",
		"text",
		"html",
		"lcov",
		"clover"
	]
},

Run jest and see that coverage is only reported for js files. The problem might be related to #9464.
Expected behavior
Coverage should be reported for js and vue files.
Link to repl or repo (highly encouraged)
The repository is https://github.com/nextcloud/tasks. If a minimal example is preferred I can provide one as well.
Run npx envinfo --preset jest
npx: Installierte 1 in 1.749s

  System:
    OS: Linux 4.9 Debian GNU/Linux 9 (stretch) 9 (stretch)
    CPU: (2) x64 Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
  Binaries:
    Node: 13.7.0 - /usr/local/bin/node
    npm: 6.13.6 - /usr/local/bin/npm
  npmPackages:
    jest: ^25.1.0 => 25.1.0

Can confirm, jest 25.1 stopped to collect coverage from vue files. 24.9 is fine.

Same here. Downgrading to Jest 24 fixes the issue and .vue files show coverage. Using similar config as the OP that explicitly enables coverage collection for the extension:
module.exports = {
  collectCoverage: true,
  collectCoverageFrom: [
    '**/*.{js,vue}',
    [...]

I'm facing the same issue, but if I try to downgrade to 24 my tests fails
Test suite failed to run

.../node_modules/@babel/runtime-corejs2/helpers/esm/defineProperty.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import _Object$defineProperty from "../../core-js/object/define-property";
                                                                                ^^^^^^^^^^^^^^^^^^^^^^

    SyntaxError: Unexpected identifier

The update to Jest 25.2.4 (possibly earlier already) seems to have fixed the issue. With https://github.com/nextcloud/tasks/commit/5dd7179258e23191b8a3765a1e21ce7025dd6e22 I see the coverage being reported for vue files again.

I close this since the issue is fixed with 25.2.4..


Does not like running on windows

Uploaded, but where it should have created subdirectories it's just banged the file up there with the folder in the name. I assume it's due to the backslash on windows vs forward slash on linux.
e.g. a using this plugin it's put the resources up there but with the key font-awesome\css\font-awesome.min.css (instead of creating subfolders).

I'm having the same issue, is there maybe an update available to solve this? Otherwise it sadly renders the plugin unusable for windows users.

I have no windows machines to test on.
I do almost no Node development, either, so I don't know what the de facto solution to supporting platform-dependent path separators is.
I was hoping someone else who does use Windows would have had some input on this... clearly not :/


DR across 2 AVS instances?

This document covers DR process set up between on-prem VMware site and an AVS private clouds instance.
Is this guidance applicable between 2 AVS private clouds instances (in the same region or across regions)?
If yes, how will 2 AVS private clouds instances be connected(e.g. Vnet peering, expressroute, etc.) ?

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

ID: 52509702-f713-c176-1f8a-5843e328f20f
Version Independent ID: 53aae11a-243f-eec4-ca53-26b924e0c0f9
Content: Complete a disaster recovery of virtual machines - Azure VMWare Solution
Content Source: articles/azure-vmware/disaster-recovery-for-virtual-machines.md
Service: azure-vmware
GitHub Login: @shortpatti
Microsoft Alias: v-patsho

#assign @shortpatti

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

#assign @jreypo

#assign @jreypo

@Mahesh-MSFT HCX in a cloud to cloud scenario is supported. We are in the process to update the HCX part of the documentation. Thanks a lot for the feedback.

@Mahesh-MSFT HCX in a cloud to cloud scenario is supported. We are in the process to update the HCX part of the documentation. Thanks a lot for the feedback.

#please-close


fix(telegraf): replace grok tool link, typo, and style (#4757)

Closes #4757

Replace broken link with link to Grok Constructor.

Fix link format.

Fix style and typos.

[ ] Signed the InfluxData CLA
(if necessary)

[ ] Rebased/mergeable

👌🏻 LGTM

Can you approve? I don't have permission to merge without it.


Nextjs error - SyntaxError: Named export 'saveAs' not found. The requested module 'file-saver' is a CommonJS module

Using dynamic import is not a solution, I need to be able to import extentions to generate html from JSON on server.

@stefan-krajnik how to can you get this error? can you share a repo?

@hunghg255 I don't have it anywhere publicly available, but it's easy to reproduce.
If you import the editor anywhere where it runs on server, e.g. pages/* or pages/api/* it crashes.
It only works if I separate it to a component which is then dynamically imported.
next 14.2.13

The issue is here
https://github.com/hunghg255/reactjs-tiptap-editor/blob/5b0b4aa21ab5539c4c3eb464d7c825f01da05180/src/extensions/ExportWord/ExportWord.ts#L2
I'd recommend either to use another package or import the package asynchronously when save is triggered
So here
https://github.com/hunghg255/reactjs-tiptap-editor/blob/5b0b4aa21ab5539c4c3eb464d7c825f01da05180/src/extensions/ExportWord/ExportWord.ts#L65-L67
I'd do something like
const fileSaver = await import('file-saver')
const wordDocument = docxSerializer.serialize(editor.state.doc, opts)
Packer.toBlob(wordDocument).then(blob => fileSaver.saveAs(new Blob([blob]), 'document.docx'))
return true

You can do the same even if you decide to use different library for saving files, it doesn't need to be part of the main bundle

The issue is here
https://github.com/hunghg255/reactjs-tiptap-editor/blob/5b0b4aa21ab5539c4c3eb464d7c825f01da05180/src/extensions/ExportWord/ExportWord.ts#L2
I'd recommend either to use another package or import the package asynchronously when save is triggered
So here
https://github.com/hunghg255/reactjs-tiptap-editor/blob/5b0b4aa21ab5539c4c3eb464d7c825f01da05180/src/extensions/ExportWord/ExportWord.ts#L65-L67
I'd do something like
const fileSaver = await import('file-saver')
const wordDocument = docxSerializer.serialize(editor.state.doc, opts)
Packer.toBlob(wordDocument).then(blob => fileSaver.saveAs(new Blob([blob]), 'document.docx'))
return true

You can do the same even if you decide to use different library for saving files, it doesn't need to be part of the main bundle

oke, I got it, I will check late-night

@hunghg255 any progress?

@hunghg255 any progress?

@hunghg255 any progress?

try config next.config.js
const nextConfig = {
  transpilePackages: ['shiki'],
};


increases test coverage for gitlab parsing tests and fixes issues.

just an fyi am getting some test failures
--- FAIL: TestInheritKeys_Error (0.00s)
    go-convert/convert/gitlab/yaml/inherit_test.go:59: Expect error, got failed to unmarshal inherit keys
--- FAIL: TestJob (0.00s)
    go-convert/convert/gitlab/yaml/job_test.go:119: yaml: unmarshal errors:
          line 1: cannot unmarshal !!seq into yaml.Job
--- FAIL: TestJob_Error (0.00s)
    go-convert/convert/gitlab/yaml/job_test.go:132: Expect error, got yaml: unmarshal errors:
          line 1: cannot unmarshal !!int `123` into yaml.Job

another things I noticed is that the golden files don't produce a valid gitlab yaml
jobs:
    job:
        artifacts:
            paths:
                - binaries/
                - .config

it is important that the golden file be a valid gitlab yaml to ensure we can accurately serialize.  it also makes it easier for a third party (like myself) to read the tests and verify accuracy.

I can't run the unit tests to verify, but I feel like we should be able to simplify the unmarshal logic. note that this still would require a custom marshal function for the golden files to work.
type (
	// Pipeline defines a gitlab pipeline.
	Pipeline struct {
		Default      *Default             `yaml:"default,omitempty"`
		Include      []*Include           `yaml:"include,omitempty"`
		Image        *Image               `yaml:"image,omitempty"`
		Jobs         map[string]*Job      `yaml:"jobs,inline"`
		TemplateJobs map[string]*Job      `yaml:"-"`
		Stages       []string             `yaml:"stages,omitempty"`
		Variables    map[string]*Variable `yaml:"variables,omitempty"`
		Workflow     *Workflow            `yaml:"workflow,omitempty"`
	}

	// Default defines global pipeline defaults.
	Default struct {
		After         Stringorslice `yaml:"after_script,omitempty"`
		Before        Stringorslice `yaml:"before_script,omitempty"`
		Artifacts     *Artifacts    `yaml:"artifacts,omitempty"`
		Cache         *Cache        `yaml:"cache,omitempty"`
		Image         *Image        `yaml:"image,omitempty"`
		Interruptible bool          `yaml:"interruptible,omitempty"`
		Retry         *Retry        `yaml:"retry,omitempty"`
		Services      []*Image      `yaml:"services,omitempty"`
		Tags          Stringorslice `yaml:"tags,omitempty"`
		Timeout       string        `yaml:"duration,omitempty"`
	}
)

func (p *Pipeline) UnmarshalYAML(unmarshal func(interface{}) error) error {
	out1 := struct {
		Default      *Default             `yaml:"default,omitempty"`
		Include      []*Include           `yaml:"include,omitempty"`
		Image        *Image               `yaml:"image,omitempty"`
		Jobs         map[string]*Job      `yaml:"jobs,omitempty"`
		TemplateJobs map[string]*Job      `yaml:"-"`
		Stages       []string             `yaml:"stages,omitempty"`
		Variables    map[string]*Variable `yaml:"variables,omitempty"`
		Workflow     *Workflow            `yaml:"workflow,omitempty"`
	}{}

	if err := unmarshal(&out1); err != nil {
		return err
	}

	p.Default = out1.Default
	p.Include = out1.Include
	p.Image = out1.Image
	p.Jobs = out1.Jobs
	p.Stages = out1.Stages
	p.Variables = out1.Variables
	p.Workflow = out1.Workflow

	for k, v := range out1.Jobs {
		if strings.HasPrefix(k, ".") {
			delete(p.Jobs, k)
			p.TemplateJobs[k] = v
		}
	}
	return nil
}

another things I noticed is that the golden files don't produce a valid gitlab yaml
jobs:
    job:
        artifacts:
            paths:
                - binaries/
                - .config

This probably means we are missing a custom marshal function in one or more places. It is important that the golden file be a valid gitlab yaml to ensure we can accurately serialize. it also makes it easier for a third party (like myself) to read the tests and verify accuracy.
Note that anywhere we do a custom unmarshal, we should verify that it produces a correct golden file. If not we need to implement custom marshaling (you can search the codebase for MarshalYaml for examples)

Fixed this.


FTP Upload sample code for .NET Framework uses C# 8

[Enter feedback here]

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

ID: a421182a-dac9-c619-b501-240dd2aafd7b
Version Independent ID: 30940ebd-4501-8580-2efc-c6abf522fe93
Content: How to: Upload files with FTP - .NET Framework
Content Source: docs/framework/network-programming/how-to-upload-files-with-ftp.md
Product: dotnet-framework
Technology: dotnet-networking
GitHub Login: @karelz
Microsoft Alias: ncldev

Hi @GnoZ - is there an issue with this sample using C# 8? If not, let's close this.

Hi, C# 8 is not supported on Net Framework, only Net core 3.0 and above
BRES Clément

From: David Pine @.>
Sent: Wednesday, May 11, 2022 9:50:05 PM
To: dotnet/docs @.>
Cc: GnoZ @.>; Mention @.>
Subject: Re: [dotnet/docs] FTP Upload sample code for .NET Framework uses C# 8 (Issue #29363)
Hi @GnoZhttps://github.com/GnoZ - is there an issue with this sample using C# 8? If not, let's close this.
—
Reply to this email directly, view it on GitHubhttps://github.com/dotnet/docs/issues/29363#issuecomment-1124225027, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADXVA2ZTA6BIF4FTIXM4FFTVJQFO3ANCNFSM5VUK4ZMA.
You are receiving this because you were mentioned.Message ID: @.***>

Hi @GnoZ - see https://github.com/dotnet/docs/pull/29448


Test breakpoint code

Add hooks field to yaml, and use before and after hooks to add / check for breakpoints

It's probably not worth it to support this functionality in test case recorder.  See #490 for example of how to write simple manual breakpoint tests


azk : Depends: lxc-docker but it is not installable in apt-get install azk

I try to install but received this error:
joridos@ceicom:~$ sudo apt-get install azk
The following information may help to resolve the situation:
The following packages have unmet dependencies:
 azk : Depends: lxc-docker but it is not installable
E: Unable to correct problems, you have held broken packages.

Distributor ID:	elementary OS
Description:	elementary OS Freya
Release:	0.3
Codename:	freya

joridos@ceicom:~$ uname -a
Linux ceicom 3.13.0-52-generic #86-Ubuntu SMP Mon May 4 04:32:59 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

@joridos sorry about the error :(. @saitodisse do you know what might be the problem?

@joridos, your docker installation must be from docker.io and azk depends on lxc-docker which is the package maintained by Docker's team.
We recommend you to replace your current Docker installation with lxc-docker as shown in azk documentation.
However Elementary OS is based on Ubuntu we recommend using instructions for Ubuntu 12.04: http://docs.azk.io/en/installation/linux.html#ubuntu-precise-1204-lts-64-bit

Okay, I'm gonna try this way

@joridos worked for you?

WOW, I removed my current docker, and installed just the lxc-docker, and works. :smile: cheers.

Nice. So I will close this issue.


Add stream argument to request data

Overview
This PR adds stream argument to request data. Additionally, filtering can now use reference designator, not just name of region, site, and instrument.

Pull Request Test Coverage Report for Build 126

0 of 0   changed or added relevant lines in 0 files are covered.
44 unchanged lines in 1 file lost coverage.
Overall coverage remained the same at 48.291%

Files with Coverage Reduction
New Missed Lines
%

/home/travis/miniconda/envs/TEST/lib/python3.6/site-packages/yodapy/datasources/ooi/init.py
44
46.71%

Totals

Change from base Build 124:
0.0%

Covered Lines:
325

Relevant Lines:
673

💛  - Coveralls

All checks passed. Merging.


fix when alias is missing in value result

@cantino this is what is needed to fix the gem for es1.x as far as I can tell, this should be ok to get into master of this gem which will ease migrations

Oops, this is based from the wrong thing


Add Restful API document

Issue: https://github.com/tektoncd/pipeline/issues/2055

Changes

Add Restful API document
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Includes tests (if functionality changed/added)
[x] Includes docs (if user facing)
[x] Commit messages follow commit message best practices

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
The document is for describing Pipeline restful API.

Sorry, wrong commit. :D


Response cutting off at around 256 tokens

The response cuts off at around 256tokens.
# .env
CRIA_MODEL_PATH=/home/bala/Models/llama-2-13b-chat.ggmlv3.q8_0.bin

# Other environement variables to set
CRIA_SERVICE_NAME=cria
CRIA_HOST=<IP_ADDRESS>
CRIA_PORT=3000
CRIA_MODEL_ARCHITECTURE=llama
CRIA_USE_GPU=false
CRIA_GPU_LAYERS=32
CRIA_ZIPKIN_ENDPOINT=http://zipkin-server:9411/api/v2/spans

Input
{
  "prompt":"[INST]<<SYS>>.<</SYS>>How do I get from UNSW to Central Station?[/INST]",
  "temperature":0.1
}

Output
console.log(response.choices[0].text)

There are several ways to get from the University of New South Wales (UNSW) to Central Station in Sydney. Here are some options: 1. Train: The easiest and most convenient way to get to Central Station from UNSW is by train. The UNSW campus is located near the Kensington station, which is on the Airport & South Line. You can take a train from Kensington station to Central Station. The journey takes around 20 minutes. 2. Bus: You can also take a bus from UNSW to Central Station. The UNSW campus is served by several bus routes, including the 395, 397, and 398. These buses run frequently throughout the day and the journey takes around 45-60 minutes, depending on traffic. 3. Light Rail: Another option is to take the light rail from UNSW to Central Station. The light rail runs along Anzac Parade and stops at Central Station. The journey takes around 30-40 minutes. 4. Taxi or Ride-sharing: You can also take a taxi or ride-sharing service such as Uber or Ly

Is there a way to increase this?

cria replicates the OpenAI API, so you can set the max_tokens value into your POST request. Here is an example :
curl http://localhost:3000/v1/completions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -d '{
    "model": "gpt-3.5-turbo-instruct",
    "prompt": "Say this is a test",
    "max_tokens": 512,
    "temperature": 0
  }'


Kani fails to detect for loop bound after upgrade to nightly-2024-03-15

While upgrading to nightly-2024-03-15, we had to add a few #[kani::unwind] attributes to harnesses with for loops with simple integer ranges. We need to investigate why this is no longer the case, and hopefully improve the loop bound detection algorithm.
Here is an example of a test case (tests/expected/iterator/main.rs):
#[kani::proof]
#[kani::unwind(4)] // Kani will unwind forever if we remove this attribute.
fn main() {
    let mut z = 1;
    for i in 1..4 {
        z *= i;
    }
    assert!(z == 6);
}

using the following command line invocation:
kani main.rs

with Kani version: https://github.com/model-checking/kani/pull/3084
I expected to see this happen: Kani should be able to automatically detect the loop bound.

Instead, this happened: Kani requires an unwind attribute.

This appears to also affect incredibly simple cases like:
#[kani::proof]
fn check() {
  for _ in 0..1 {}
}

Note 0..0 still works

With apologies for not actually posting on this issue: https://github.com/diffblue/cbmc/pull/8247 fixes this problem on the CBMC side. We just need to get this merged plus a new CBMC release to be produced.


Make part=content take the full available height

Though the component takes the full height, part="content" is not forced to take the available height.
So if developer declares a <vaadin-app-layout> like this:

<vaadin-app-layout>

Application Name

  <vaadin-tabs slot="menu">
      <vaadin-tab>Page 1</vaadin-tab>
      <vaadin-tab>Page 2</vaadin-tab>
  </vaadin-tabs>

      Page content

Side menu item

Side menu item

Side menu item

Side menu item

</vaadin-app-layout>

This would be what they get:

I don’t see the issue. The content behaves just as the CSS says it should work. If you want the content to take all the available space, you should use height. 100%, right?

I agree that it should be possible to be able to make the content (user-defined) use the available space. But we should not force that by default.

Take a look at this example where the div.page is set to height: 100%, but still it doesn't grow to take the full height even though when you inspect the content part it will show as using it.

Yeah, I edited my previous comment and added another one. Hope those clarify my concern.

What would the expectation of a developer be? can we make it easier for them then having to define a separate bit of boilerplate css? This is after all a very basic use case.

This is after all a very basic use case.

Yes, agreed. And I would expect the expectation of a developer to be that they only need to define the height of the content they provide as 100% to make it stretch. For example:
<vaadin-app-layout>

</vaadin-app-layout>


workshop folder not found --404

please check why workshop folder and the contents not found anymore. thanks

o i saw already move to doc folder. ok understood


nvexec start_detached test is hanging when run with compute-sanitizer

This may in fact be expected. @senior-zero writes:

Compute sanitizer might be blocking on kernel completion. The start detached test is a communication pattern: device: while(cpu_mem); host: start_detached(); sleep(); cpu_mem = 0; So if the launch is blocked, there'll be no progress.


Doesn't save window splits

This doesn't seem to save window splits.
Am I missing something?

Sorry, not sure what you mean

If you do a window split (e.g. with :vsplit), the split is not saved

@raffaem It should be saving window sizes.
Can you share your auto-session config and the value of vim.o.sessionoptions?

return {
  {
    'rmagatti/auto-session',
    dependencies = {
      'nvim-telescope/telescope.nvim', -- Only needed if you want to use sesssion lens
    },
    config = function()
      require('auto-session').setup({
        auto_session_suppress_dirs = { '~/', '~/Projects', '~/Downloads', '/' },
      })
    end,
  },
}

:lua =vim.o.sessionoptions
blank,buffers,curdir,folds,help,tabpages,winsize,terminal,globals

That should work so there must be something else going on. Can you see if this minimal config works correctly for you:
--[[ Minimal config to reproduce issues ]]
--
--  Usage: `nvim -u repro.lua`

-- DO NOT change the paths
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
	vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
	vim.fn.system({
		"git",
		"clone",
		"--filter=blob:none",
		"--single-branch",
		"https://github.com/folke/lazy.nvim.git",
		lazypath,
	})
end
vim.opt.runtimepath:prepend(lazypath)

vim.o.sessionoptions = "blank,buffers,curdir,folds,help,tabpages,winsize,terminal,globals"

-- install plugins
local plugins = {
	-- add any other plugins here
	{
		"rmagatti/auto-session",
		lazy = false, -- Needs to restore session on Neovim start.
		config = true,
	},
}
require("lazy").setup(plugins, {
	root = root .. "/plugins",
})

Can you describe more about your environment? What version of nvim are you using?

It is working now, my bad.
Sorry for that.


Specify which exceptions are caught and which are not

Catching all exceptions with a blanket 'except:' is an
anti-pattern, and one that a client library like this
library should not be doing, because it to aggressively
catches things that it should not catch.
Read over:
https://docs.python.org/2/howto/doanddont.html#except

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[ ] I've read and agree to the Code of Conduct.
[ ] I've been mindful about doing atomic commits, adding documentation to my changes, not refactoring too much.
[ ] I've a descriptive title and added any useful information for the reviewer. Where appropriate, I've attached a screenshot and/or screencast (gif preferably).
[ ] I've written tests to cover the new code and functionality included in this PR.
[ ] I've read, agree to, and signed the Contributor License Agreement (CLA).

PR Summary
Related Issues
Test strategy

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

@harlowja I'm going to take a look at why the test are failing on this today. If you don't mind, can you sign the CLA when you get a chance? (CLA is a blocker)

@harlowja we need to update this test:
https://github.com/slackapi/python-slackclient/blob/master/tests/test_server.py#L46-L48
def test_Server_cantconnect(server):
    with pytest.raises(SlackLoginError):
        reply = server.ping()

Change server.ping() to server.rtm_connect()

Ah, yes, I'll talk to my folks about updating and getting the CLA signed. Sorry about lack of responding, didn't see the responses till today :-/

Is this being monitored?

@aeckard87 sorry, there hasn't been much attention on this issue lately. i think this is a pretty important change, so we'll try to assign a priority soon.
@harlowja would you mind updating the PR to resolve conflicts with master?


Fixes #117 - ext. clock now triggers on rising value.

Previously, the external clock would trigger on a falling value, which was made very apparent if the clock signal was a 50% duty square wave or similar.

LGTM, thanks for reporting the bug and sending over a fix!


Reduce of accuracy after update to version 0.7

Hi,
noticed that after upgrade to version 0.7 accuracy of trained models from 0.63 reduces on a few percentage.
And it would be not so critical, but retraining from scratch on version 0.7 can't get previous results. Unfortunately can't provide some code as efficient-net is only small part of the system. We use b3 network and crop size 288.
Could you provide an example how to change image size? It's a single part that differs our code from your examples.

Thanks for the issue. This seems important and I will investigate.
For the image size, it's just changed with the normal PyTirch data transforms (i.e. Resize(300))


Fixed Link validation

In cases where you tried to save a Document with a field containing a Link/DBRef instead of the wrapped object itself, the validate_on_save hook would stop working, and return an error.
This was because the Link object was first serialized into a dict, and any further validation with Link.validate would always fail trying to deserialize a dict like {"id": ..., "collection": ...} as a real Document rather than a Link.
I've committed a simple solution, however, you can refine it to make it more elegant.
As my reserch has shown, there is no sense tweaking the way Document.validate_self validates the document. Instead, the easiest way would be to teach the Link to recognize its own schema.
This approach has the only obvious corner case: if the user creates a custom model with the same structure as Link, and then tries to wrap it with Link, he would get an unexpected behavior.

Ping?

Hi! Sorry for the delay. Thank you for the PR!
I'll check it by the end of this week

Merged! Thank you! It will be published by the end of this week with others.


[Nix] Packaging of local dependencies

I am starting an obelisk project for a webstore and erp, however since there will be two obelisk sites I am opting for creating a local package which would be a common dependency.
local-library (schema, library-functions, etc)
public-site [obelisk] (no admin routes)
- backend
- common
- frontend
private-site [obelisk] (no public routes)
- backend
- common
- frontend

However, when adding such a dependency to the cabal.project files
packages =
  backend
  common
  frontend
 ../local-library

ob run et al. fail with a nix error:
 ~/D/L/LaTiendita   package-doubt  latiendita-web  ob run                                                   17s  Thu 26 Mar 2020 12:36:19 PM CST
error: anonymous function at /nix/store/fw7m0a5y7ywzr227bkc9aw32bgrmksr7-cabal2nix-backend/default.nix:1:1 called without required argument 'local-library', at /nix/store/ws6z2fm6q4wpw89rygxvrh08g104ixzw-source/pkgs/development/haskell-modules/make-package-set.nix:87:27
(use '--show-trace' to show detailed location information)

With verbose, it seems like argstr should take into consideration extra dependencies and currently doesn't:
'--argstr' 'pkgs' '{"backend":"/home/fabian/Development/LibreCybernetics/LaTiendita/latiendita-web/backend","common":"/home/fabian/Development/LibreCybernetics/LaTiendita/latiendita-web/common","frontend":"/home/fabian/Development/LibreCybernetics/LaTiendita/latiendita-web/frontend"}
As a workaround, I moved local-library into one of the sites to start learning some obelisk. It seems like a packaging issue of local libraries however I am not familiar enough with neither nix nor obelisk to further debug the issue or open a Merge Request. (Though I will be reading the obelisk code to see if I can find something)
Real World Example:
Attempted structure: https://gitlab.com/LibreCybernetics/LaTiendita/-/tree/639299c70d08901d1afddbae1a0f6cb6023915b7
Current workaround: https://gitlab.com/LibreCybernetics/LaTiendita/-/tree/1fac2a5d80f1be429d66d73b5903149c3b0f7383
I see in #108 that there is a way to override the hackage/nix dependencies in case of incompatibility and that instructions for fetching from hackage were added to the readme ( https://github.com/obsidiansystems/obelisk/blob/develop/README.md#adding-package-overrides ) however it would be a bit annoying to be pinning the version/hash of the common library assuming it would be changing as often as the obelisk code (And as such would be desirable for the time being to host on a single git repo).
  overrides = self: super: {
    time-recurrence = pkgs.haskell.lib.doJailbreak super.time-recurrence;
  };

However I am still unfamiliar with using nix to bring in local extra dependencies. :C

Thanks for the detailed report! There is a bug with ob run where it won't find local packages that are in a parent directory. As a workaround make a symlink in each of your sub-obelisk-projects to the library. This way ob run will find them. Let me know how that goes. We are trying to make ob run handle this case properly by reading the paths directly from your nix instead.

Oh, the symlink was one of the things I tried and nix won't package it either. :C

Can you paste your default.nix for one of the obelisk projects that's not working? I suspect you need to add this library to the nix set of packages too.

{ obelisk ? import ./.obelisk/impl {
    system = builtins.currentSystem;
  }
}:
with obelisk;
project ./. ({ ... }: {})

Try something like this:
{ obelisk ? import ./.obelisk/impl {
    system = builtins.currentSystem;
  }
}:
with obelisk;
project ./. ({ ... }: {
  packages = {
    my-package = ../my-package;
  };
})

Oh that fixed it, thanks for the support @3noch. ^_^

Clearly this needs to be documented better! Thanks for the feedback!

 Without the symlink I believe it will try to build your common package once with nix and any changes will require you to restart ob run.


Fix documentation for Sphinx 4

Summary
Sphinx 4 is more particular about disallowing the same Python object to
be documented in multiple toctree entries.  The culprits were Barrier,
Reset and Measure in the circuit library; the library re-exports
them from their canonical locations, and used autosummary to generate
extra links to them.  We still re-export them, but change the
autosummary tables to link to the existing definitions.
This then builds the documentation without errors on Sphinx 4, and
consequently the pin on sphinx-panels can be removed.  Previously the
pin was applied because an update to that package caused the
documentation build to break; in reality, it's just that
sphinx-panels<0.6 pinned itself to Sphinx<4, whereas version 0.6
allowed Sphinx 4 - there were no breaking changes for us.

Details and comments
This currently doesn't add any behaviour that requires Sphinx 4.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.005%) to 83.117%

Totals

Change from base Build<PHONE_NUMBER>:
0.005%

Covered Lines:
51944

Relevant Lines:
62495

💛  - Coveralls


Allow compile cli output-path to be specified for each emitter

It will be common for specs that execute multiple emitters that each emitter will require a different path.  Allow specifying output-path in the emitter configuration of each emitter to override the default output-path
We might also allow different emitters to specify additional compilation files in cadl-project.yaml. This would allow inclusion of sidecar files in some emitters.

rename output-path to output-dir
retain an alias for output-path
remove from cli help
``
cadl-autorest:
output-dir:
output-file: openapi.json   // {$output-path}/${version}/openapi.json  or ${output-path}/openapi.json
cadl-python
output-dir: