Fresh Ubuntu install - tcam-capture not working (or any other code)

Hello, working with a DMK 33GX178e that works properly from windows, however linux code is not working.
Installed a fresh image of Ubuntu 18.04 on my laptop, installed required packages from readme. Installed OpenCV from source with extras and when running the CPP example Saving images using OpenCV I get these errors:
https://pastebin.com/z8WzZfup
I have manually set the GST Plugins directory (which resolved errors about gst binaries not found). Attempted both packaged version (per README) and built GStreamer from source. I am getting issues with properties being read from the camera in all applications, including tcam capture.
tcam-capture errors: https://pastebin.com/WchYC7uK
Guessing there is a missing dependency or required version of something missing from documentation as I had this issue before re-installing Ubuntu.

Hello Ryan
I am sorry for asking, but did you follow the the building steps documented on our Readme at https://github.com/TheImagingSource/tiscamera?
Stefan

Yes, as stated in original post, I used the readme. I copied and pasted all required packages. I believe that list is incomplete because I know for some of the examples you require GTK-3.0, however that library is not included in your required packages.
Please let me know what information i can provide for further troubleshooting. Again, this was a fresh install of Ubuntu that I copied and pasted the instructions from the readme and it does not work.
Thanks

Ryan
one test please
Does
gst-launch-1.0 tcambin ! videoconvert ! ximagesink
work on the terminal?
Stefan

No, i get a blank output with the following messages in console:
$ gst-launch-1.0 tcambin ! videoconvert ! ximagesink
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
INFO:
Working with src caps: video/x-raw, framerate=(fraction)19/2, width=(int)3072, height=(int)2048, format=(string)GRAY16_LE
Setting pipeline to PLAYING ...
New clock: GstSystemClock
ERROR: from element /GstPipeline:pipeline0/GstTcamBin:tcambin0/GstTcamSrc:tcambin-source: Device lost
Additional debug info:
/home/ryan/projects/tiscamera/src/gstreamer-1.0/gsttcamsrc.cpp(1045): gst_tcam_src_device_lost_callback (): /GstPipeline:pipeline0/GstTcamBin:tcambin0/GstTcamSrc:tcambin-source
Execution ended after 0:00:21.265382708
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...

Which computer model do you use?
Does the green LED light on the camera?

The Camera works from windows using your IC Capture app. It is a GigE camera, so the PC is irrelevant.
It is an XPS13 Developer edition running Ubuntu 18.04.

Please excuse me asking. I asked, because the reported error happens, if the camera is connected to a 100mBit network. Therefore, I asked for the green LED, that indicates 1GB speed.

Yes, it is plugged into a juniper EX-2200-24P
It shows green currently.

ok, ruled one possible problem out.
You should not get a device lost, when starting the live video, obviously, even if 16 bit video formats are used.
So next step....
gst-launch-1.0 tcambin ! video/x-raw, format=BGRx, width=640, height=480, framerate=30/1 !  videoconvert ! ximagesink
Makes a small colored video format. I am not sure, whether BGRx can be exchanged against GRAY8.
Please let me know the result.
Sorry for all this guessing around.

small blank box - no image.
Here's the console output:  https://pastebin.com/ivubGQFi
Thanks

I was able to get a C++ program to at least give me additional information:
double property 'DeviceTemperature': value = 58.500000 default = 58.500000 min = -179769313486231570814527423731704356798070567525844996598917476803157260780028538760589558632766878171540458953514382464234321326889464182768467546703537516986049910576551282076245490090389328944075868508455133942304583236903222948165808559332123348274797826204144723168738177180919299881250404026184124858368.000000 max =<PHONE_NUMBER>86231570814527423731704356798070567525844996598917476803157260780028538760589558632766878171540458953514382464234321326889464182768467546703537516986049910576551282076245490090389328944075868508455133942304583236903222948165808559332123348274797826204144723168738177180919299881250404026184124858368.000000 step_size = 0.001000
I believe this is what tcam-capture is choking on, but I still don't have image output.
Thanks

Console output on your next suggestion:  https://pastebin.com/HecWpx27
Still blank box.
To verify that my gstreamer is working, I tested with my webcam and was successful with this pipeline: gst-launch-1.0 v4l2src ! videoconvert ! autovideosink
Tried replacing ximagesink with autovideosink and no luck there either.

There seems to be a negotiation error in the tcambin. This prevents GRAY8/GRAY16_LE -> BGRx, which is something tcam-capture implicitly expects to work.
gst-launch-1.0 tcamsrc ! video/x-raw, format=GRAY16_LE, width=640, height=480, framerate=30/1 ! videoconvert ! ximagesink

This pipeline should work. If not I would require the output of
export TCAM_LOG=DEBUG
gst-launch-1.0 --gst-debug=tcamsrc:5 tcamsrc ! video/x-raw, format=GRAY16_LE, width=640, height=480, framerate=30/1 ! videoconvert ! ximagesink

With a 33 mono camera all auto-adjustmenst are in-camera so the bin offers little/to no advantage for you.
As a potential workaround you could try the development branch of the upcoming 0.11.0 release, as this issue seems to be resolved there.

top pipeline did not work.
Without Sudo getting permissions errors on the gige service pid file:
https://pastebin.com/YzaSPL4z
With Sudo: https://pastebin.com/wmuhYqgZ
Is there anything special I need to do to try out the development branch?

Simply call git checkout development.
Please uninstall tiscamera before doing that. It is also recommended to use a new build folder.
Can you give me your procedure for building gstreamer?
All our tests show that a GRAY16 pipeline should be running, and with gstreamer installed from the repositories it definitely runs. The custom gstreamer may cause the issues, but I would like to verify that before saying anything with certainty.

I actually re-installed Ubuntu again thinking the same thing. I only have Gstreamer from packages now - no custom build. OpenCV is installed and working (as far as i can tell thus far).
I did the following:
git checkout development
git pull
cd tiscamera/build
sudo make uninstall
cd ..
rm -rf build
mkdir build
cd build
cmake -DBUILD_ARAVIS=ON -DBUILD_GST_1_0=ON -DBUILD_TOOLS=ON -DBUILD_V4L2=ON -DCMAKE_INSTALL_PREFIX=/usr ..
make
sudo make install
then trying the
gst-launch-1.0 tcamsrc ! video/x-raw, format=GRAY16_LE, width=640, height=480, framerate=30/1 ! videoconvert ! ximagesink
Pipeline I am still seeing errors, but I see video for the first time in this whole lovely ordeal.
I still cannot launch tcam-capture successfully - complains of disconnect.

Good to hear, that at least a basic stream is working,
tcam-capture is a bit aggressive when it comes to device-lost events. Those are typically triggered by errors reported by the backend such as too many missing images, missing heartbeats, etc.
A common cause may be a low mtu. You can change it with
sudo ip link set dev eth0 mtu 9000 where eth0 should be replaced with your interface in question.
If that does not resolve the problems I would require a new log of the current situation.
export TCAM_LOG=DEBUG
gst-launch-1.0 --gst-debug=tcamsrc:5 tcamsrc ! video/x-raw,format=GRAY16_LE,width=640,height=480,framerate=30/1 ! videoconvert ! ximagesink

tcam-capture should give a somewhat identical log, but stop the stream after the first error.

Looking into MTU, my switch is not configured for jumbo frames, and I was not aware it was a requirement of the GIGE cameras. I have verified proper MTU and am using a different USB NIC on my laptop successfully for tcam-capture only on the Development Branch though. master does not yield images.

Additionally, now trying to build the latest linux examples, i am getting YAML related errors.
What version of yaml-cpp should be installed?

ryan@ryan-XPS-13-9343:~/projects/Linux-tiscamera-Programming-Samples/Simple Snap Image in C++/build$ make
[ 25%] Linking CXX executable simple-snapimage
CMakeFiles/simple-snapimage.dir/home/ryan/projects/tiscamera/examples/cpp/common/tcamcamera.cpp.o: In function gsttcam::TcamCamera::store_device_state(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >)': /home/ryan/projects/tiscamera/examples/cpp/common/tcamcamera.cpp:690: undefined reference to YAML::operator<<(std::ostream&, YAML::Node const&)'
CMakeFiles/simple-snapimage.dir/home/ryan/projects/tiscamera/examples/cpp/common/tcamcamera.cpp.o: In function gsttcam::TcamCamera::restore_device_state(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >)': /home/ryan/projects/tiscamera/examples/cpp/common/tcamcamera.cpp:697: undefined reference to YAML::LoadFile(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&)'
CMakeFiles/simple-snapimage.dir/home/ryan/projects/tiscamera/examples/cpp/common/tcamcamera.cpp.o: In function YAML::detail::memory_holder::create_node()': /usr/include/yaml-cpp/node/detail/memory.h:39: undefined reference to YAML::detail::memory::create_node()'
CMakeFiles/simple-snapimage.dir/home/ryan/projects/tiscamera/examples/cpp/common/tcamcamera.cpp.o: In function YAML::detail::node_ref::mark_defined()': /usr/include/yaml-cpp/node/detail/node_ref.h:28: undefined reference to YAML::detail::node_data::mark_defined()'
CMakeFiles/simple-snapimage.dir/home/ryan/projects/tiscamera/examples/cpp/common/tcamcamera.cpp.o: In function YAML::detail::node_ref::set_null()': /usr/include/yaml-cpp/node/detail/node_ref.h:33: undefined reference to YAML::detail::node_data::set_null()'
CMakeFiles/simple-snapimage.dir/home/ryan/projects/tiscamera/examples/cpp/common/tcamcamera.cpp.o: In function YAML::detail::node_ref::set_scalar(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)': /usr/include/yaml-cpp/node/detail/node_ref.h:34: undefined reference to YAML::detail::node_data::set_scalar(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&)'
CMakeFiles/simple-snapimage.dir/home/ryan/projects/tiscamera/examples/cpp/common/tcamcamera.cpp.o: In function YAML::detail::node_ref::begin()': /usr/include/yaml-cpp/node/detail/node_ref.h:43: undefined reference to YAML::detail::node_data::begin()'
CMakeFiles/simple-snapimage.dir/home/ryan/projects/tiscamera/examples/cpp/common/tcamcamera.cpp.o: In function YAML::detail::node_ref::end()': /usr/include/yaml-cpp/node/detail/node_ref.h:48: undefined reference to YAML::detail::node_data::end()'
CMakeFiles/simple-snapimage.dir/home/ryan/projects/tiscamera/examples/cpp/common/tcamcamera.cpp.o: In function YAML::Node::Scalar[abi:cxx11]() const': /usr/include/yaml-cpp/node/impl.h:152: undefined reference to YAML::detail::node_data::empty_scalar[abi:cxx11]'
CMakeFiles/simple-snapimage.dir/home/ryan/projects/tiscamera/examples/cpp/common/tcamcamera.cpp.o: In function YAML::Node::AssignData(YAML::Node const&)': /usr/include/yaml-cpp/node/impl.h:250: undefined reference to YAML::detail::memory_holder::merge(YAML::detail::memory_holder&)'
CMakeFiles/simple-snapimage.dir/home/ryan/projects/tiscamera/examples/cpp/common/tcamcamera.cpp.o: In function YAML::as_if<bool, void>::operator()() const': /usr/include/yaml-cpp/node/impl.h:116: undefined reference to YAML::convert::decode(YAML::Node const&, bool&)'
CMakeFiles/simple-snapimage.dir/home/ryan/projects/tiscamera/examples/cpp/common/tcamcamera.cpp.o: In function YAML::detail::node& YAML::detail::node_data::get<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, boost::shared_ptr<YAML::detail::memory_holder>)': /usr/include/yaml-cpp/node/detail/impl.h:112: undefined reference to YAML::detail::node_data::convert_to_map(boost::shared_ptrYAML::detail::memory_holder)'
/usr/include/yaml-cpp/node/detail/impl.h:126: undefined reference to YAML::detail::node_data::insert_map_pair(YAML::detail::node&, YAML::detail::node&)' CMakeFiles/simple-snapimage.dir/home/ryan/projects/tiscamera/examples/cpp/common/tcamcamera.cpp.o: In function YAML::detail::node& YAML::detail::node_data::convert_to_node<std::__cxx11::basic_string<char, std::char_traits, std::allocator > >(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&, boost::shared_ptrYAML::detail::memory_holder)':
/usr/include/yaml-cpp/node/detail/impl.h:171: undefined reference to `YAML::detail::memory_holder::merge(YAML::detail::memory_holder&)'
collect2: error: ld returned 1 exit status
CMakeFiles/simple-snapimage.dir/build.make:161: recipe for target 'simple-snapimage' failed
make[2]: *** [simple-snapimage] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/simple-snapimage.dir/all' failed
make[1]: *** [CMakeFiles/simple-snapimage.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2

The package libyaml-cpp-dev should contain all required dependencies for that example.

That is the package I have installed and am now getting the YAML issues and cannot compile them. Is there a bug related to this in the development branch?

It is not. The example compiles as expected on Ubuntu 18.04.
Could you try a new build directory for the example? I am currently suspecting a caching issue in cmake.

Followed the same steps as above for cleaning and recreating - i cannot build the example files without a YAML related error message

I found the problem. It was that the example failed to link against yaml-cpp.
The fixes have been pushed to the development branch of the Samples repository.
cd ~/projects/Linux-tiscamera-Programming-Samples/Simple Snap Image in C++/build
git pull
git checkout development
make


Enable transfer from IBM z/OS MVS data sets

As far as I can tell, the Atom remote-ftp package requires a Unix-style leading slash (/) on FTP file paths.
Unfortunately, that doesn't work for accessing MVS data sets on IBM z/OS (mainframes).
MVS data set names (dsnames) don't use a slash as a separator. Instead, dsnames consist of a sequence of qualifiers separated by periods. For example, MYUID.PDS is a dsname that consists of two qualifiers. A dsname might refer to a file or to a directory (in MVS terminology: a library, or partitioned data set).
So, currently, there appears to be no way to access MVS data sets via remote-ftp.
I'd like to be able to specify the following setting in a .ftpconfig file:
"remote": "'MYUID.'"

(the single quotes are significant)
in the same way that, in a command-line FTP client session (on Windows), I can specify:
cd 'MYUID.'

resulting in:
250 "MYUID." is the working directory name prefix.

I understand that you might not have access to a z/OS system to test this; I'd be happy to be a tester.

You sound like you know a lot more about this than me. I would happily accept this as a pr if you put the work in. If you are up for this it would be best to make it a separate connector to those found in /lib/connectors


[Enhancement Request] Design Decisions influenced by Personas

What would you like to be added:
As from our last community meeting taken away as action item, it would be nice to define different user personas and their update rationale. E.g. personas for

Application Architect
App Developer
Infrastructure Engineering Lead
Big Data Engineer
DC Operator

Why is this needed:
When looking at the iteration of e.g. dynamic CRDs this could go many ways. For example one way would be ops heavy such as multiple permissions are required etc., or it could be developer heavy to empower developers to control these type of things more. Design decisions would depend here on how we defined different personas, who should be able to do what and with what set of permissions would it come.

ref https://github.com/kudobuilder/kudo/pull/304#issuecomment-499778578

closing for now.   please reopen with more action details.


iOS API

This adds interface for the following:

Load scene and load scene async
Scene updates
Feature picking
Long/Lat to screen position
Map view delegate for feature picking and scene loading callbacks

https://github.com/tangrams/tangram-es/issues/1027

@msmollin please give this a review.

@msmollin changes updated, please give this another look.

@karimnaaji changes look good.


Remove oci_ prefix to follow Go style guide

See https://go.dev/doc/effective_go#package-names
Another convention is that the package name is the base name of its source directory; the package in src/encoding/base64 is imported as "encoding/base64" but has name base64, not encoding_base64 and not encodingBase64.

+1 we should stick with the standards!

Can we rebase and I will gladly merge?

@krisnova rebased!


Improve password hashing

Storing passwords as a salted SHA256 hash is not safe now that GPU cracking is commonplace.
Modern password storage should use a memory-hard key derivation function (such as scrypt or the more recent Argon2) in order to thwart GPU attacks.

And the C# implementation - Replicon.Cryptography.SCrypt.

This issue could be done together with Replace client side hashing with client side encryption.

Implemented by me and checked by @warpech. Closing the issue.


Remove circular dependency

Currently, ol/Map.js depends on ol/control.js, ol/control.js depends on ol/control/OverviewMap.js, and ol/control/OverviewMap.js depends on ol/Map.js.
This branch moves the defaults function to ol/control/defaults.js to break the circular dependency.  The interactions get the same treatment.

In ol/Map the controls and interactions options description should point to the new location of the defaults functions.

Done.

Strangely the import example is only available for the interaction defaults function: https://deploy-preview-13967--ol-site.netlify.app/en/latest/apidoc/module-ol_interaction_defaults.html https://deploy-preview-13967--ol-site.netlify.app/en/latest/apidoc/module-ol_control_defaults.html

Good catch, @MoonE.  This was due to the condition that splits on ol/ here: https://github.com/openlayers/openlayers/blob/c327740108c4904d3df3866aceef2fccc88871da/config/jsdoc/api/template/tmpl/method.tmpl#L37
So import statements for methods with more than one ol/ in the name (like ol/control/defaults.defaults) were not being written.
Maybe @KaiVolland remembers what condition this was guarding against in 9860699d5f72bfacd70053b36fa0da0d48fd7643.
I remove that condition in the latest commit.  In a quick check of the published doc, I don't see any bad import statements written, but there may be some I haven't found yet.

Should the defaults methods be the default export in their respective modules?
I pushed a commit that corrects the generated import statement in case you think that's better.

Should the defaults methods be the default export in their respective modules?

Our convention is to only have a default export for modules with UppercaseFirstLetters that export a constructor (or an enum historically).  Modules that start with a lowercase first letter always only have named exports.


Support for enums as record keys

This adds support for a ZodEnum to be used as record keys.
Example:
zodToJsonSchema(
  z.record(
    z.enum(['foo', 'bar']),
    z.number()
  )
)

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "additionalProperties": { "type": "number" },
  "propertyNames": { "enum": [ "foo", "bar" ] }
}

Nice! This is now released in 3.11.3

@johngeorgewright Nice! This is now released in 3.11.3

@StefanTerdell Note that this breaks compatibility with OpenAPI 3.0 - see list of unsupported keywords in https://swagger.io/docs/specification/data-models/keywords/


Issues with multiple calls with responsive option

If you add more than one call to ellipsis() with responsive option (on different elements), it will fail: event listeners won't work because it's not unique.
Adding only one call with responsive handling it'll work, but it's needed to work with N calls.

Fixed in PR #25


Make getting started experience quicker and easier

Aim to reduce steps needed to set-up and run LaVague locally and then update with new shorter steps


Fix: unreserve utxos

Motivation:
Creation of a draft transaction will mark UTXOs as reserved, and those UTXOs can't be used for another transaction.
If a draft transaction was created, but the "record transaction" process failed, UTXOs will still be reserved and can't be used for another payment.
A mechanism for unreserving UTXOs should be added for such cases.
PR includes:

http PATCH endpoint for unreserve UTXOs
graphQL mutation for unreserve UTXOs
tests refactorization -> introducing Test Base functions

@arkadiuszos4chain linter failed, few fixes required.

Going to merge and fix it


Cherrypick/6048

Overview
Cherry picks #6048 into stabilization.
Verification

This optional section is a place where you can detail the specific type of verification
you want from reviewers. For example, if you want reviewers to checkout the PR locally
and validate the functionality of specific scenarios, provide instructions
on the specific scenarios and what you want verified.
If there are specific areas of concern or question feel free to highlight them here so
that reviewers can watch out for those issues.
As a reviewer, it is possible to check out this change locally by using the following
commands (substituting {PR_ID} with the ID of this pull request):
git fetch origin pull/{PR_ID}/head:name_of_local_branch
git checkout name_of_local_branch

/azp run

will merge once validation completes

Hitting the following error building for standalone in validation, Will investigate: Assets\MixedRealityToolkit.Tests\PlayModeTests\PressableButtonTests.cs(615,29): error CS0111: Type 'PressableButtonTests' already defines a member called 'AreApproximatelyEqual' with the same parameter types

I think I forgot to push a change, since it worked for me locally. Will check when I get in.

I think I forgot to push a change, since it worked for me locally. Will check when I get in.

I'm also trying it locally

/azp run

/azp run


return 429 instead of forbidden

In Line https://github.com/tony-joseph/crimson_antispam/blob/master/antispam/decorators.py#L43
you should return:
429 Too Many Requests: The user has sent too many requests in a given amount of time. Intended for use with rate limiting schemes.
instead of a forbidden

It should be a 429. Thanks for pointing out.


Dell .exe causing security prompt needing manual intervention

We're seeing that the new Dell .exe type files are requiring a manual prompt (which is sometimes hidden behind the main window) to run the exe file for expanding the drivers.  The GUI log sees that it's a Dell EXE type, then hangs on "Extracting Dell drivers to .....{location}".  Then a Windows Security prompt pops up with "We can't verify who created this file.
This is requiring manual intervention at every driver download, which negates the ability for the tool to run automatically and on a schedule.  Additionally if the prompt is cancelled, the process continues on and creates a driver package with no contents which then fails at the Modern Driver Management step in a TS.
Any help fixing this issue would be significantly helpful.
OS:  Windows Server 2019
DAT Version: 7.1.9 (and prior versions supporting Dell EXEs)
Screenshots attached.

I'm not sure what changed to where this is now occuring, but I do know the cause is due to alternate streams added to the .exe when grabbed from the internet.  right-click the .exe -> properties and it will state "Unblock" at the bottom.
Here's a site that details working with alternate file streams in powershell.  should help with a fix:
https://jdhitsolutions.com/blog/scripting/8888/friday-fun-with-powershell-and-alternate-data-streams/


[DOC] Databricks container doc put usage first

Report incorrect documentation
Location of incorrect documentation
https://github.com/NVIDIA/spark-rapids-container/blob/main/Databricks/README.md
I think we should rearrange this to put the usage first and then after it put build instructions if they are needed. Most people should not need to build it.

I have updated the description to point to the usage section. Close.


Add Returning Domain Objects from CUD commands to documentation

I eventually figured out how to do this after stepping through the code execution but adding some documentation for others would be useful. Especially given the current lack of documentation on mappers.
Informing developers on how to uniformly return domain objects from both commands and queries would have been useful for me.
Just a simple example + description like:
module Types
  include Dry::Types.module
end

class Account < Dry::Struct
  attribute :id, Types::Int
  attribute :email, Types::String
end

class AccountsMapper < ROM::Mapper
  relation :accounts
  register_as :entity
  model Account
end

rom_config.register_mapper(AccountsMapper)

class AccountRepo < ROM::Repository[:accounts]
  commands :create, update: :by_pk, delete: :by_pk, mapper: :entity

  def query(conditions)
    accounts.where(conditions).as(Account)
  end
end

Closing this since things changed in rom 4.0 and it works consistently via setting struct namespace. Docs will be updated along with 4.0 final.


Terms and Condition option is duplicated

Description
Terms and condition option is duplicated in the collapsed menu in mobile view
Screenshots

Additional information
How to Replicate the issue?
visit hemmelig.app on mobile device and open collapsed menu

Hey!
Can you please assign this issue to me?
this would be my first contribution

Hello. Thanks for reporting. I have assigned to you, so feel free to solve it if you'd like :)

Thank you @m4-droid 🎉

@m4-droid https://github.com/HemmeligOrg/Hemmelig.app/releases/tag/v5.13.3


Refactor Test JUL Config so it may be reused #30

I created the attached tests as suggested.

831759f87f82dc9308274cca91545467ca71384f


Prefer executables in explicitly defined JAVA_HOME

Closes #46
This is a quick PR made trough GitHub web interface.

@AlexFalappa Can you please sign the CLA before we merge this change?

@abhinayagarwal CLA signed.


Add scripts to easily destroy tfstate backend

what

Reorganize scripts into scripts/ folder
Standardize around Makefile as the task runner
Add scripts/destroy.sh to easily destroy tfstate bucket
Annotate all scripts to explain what's going on

why

Easy destruction of state bucket is needed for CI/CD testing environments

demo
Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
null_resource.default: Refreshing state... (ID:<PHONE_NUMBER>78034330)
null_resource.default: Refreshing state... (ID:<PHONE_NUMBER>588873110)
aws_s3_bucket.default: Refreshing state... (ID: eg-staging-test-state)
aws_dynamodb_table.with_server_side_encryption: Refreshing state... (ID: eg-staging-test-state-lock)
module.tfstate_backend.aws_s3_bucket.default: Destroying... (ID: eg-staging-test-state)
module.tfstate_backend.aws_dynamodb_table.with_server_side_encryption: Destroying... (ID: eg-staging-test-state-lock)
module.tfstate_backend.aws_s3_bucket.default: Destruction complete after 1s
module.tfstate_backend.module.s3_bucket_label.null_resource.default: Destroying... (ID:<PHONE_NUMBER>78034330)
module.tfstate_backend.module.s3_bucket_label.null_resource.default: Destruction complete after 0s
module.tfstate_backend.aws_dynamodb_table.with_server_side_encryption: Destruction complete after 1s
module.tfstate_backend.module.dynamodb_table_label.null_resource.default: Destroying... (ID:<PHONE_NUMBER>588873110)
module.tfstate_backend.module.dynamodb_table_label.null_resource.default: Destruction complete after 0s

Destroy complete! Resources: 4 destroyed.

Updated the README.md - please review


Kubernetes API default firewall rules

Stories
-As a Giant Swarm operations engineer, I want connections to be allowed by default from the Giant Swarm VPN exit endpoints to the CAPG Kubernetes API for management and workload clusters in order to do support for CAPG clusters.
-As a cluster admin, I want connections to be allowed by default from the CAPG management cluster to the CAPG workload cluster's Kubernetes API in order to manage and monitor workload clusters.
-As a cluster admin, I want to have a default firewall rule with the lowest priority to drop all network traffic in order to have a secure cluster out of the box.
Background
The Giant Swarm CAPG provider has support to configure firewall rules for, but the Giant Swarm VPN exit points and the management cluster's NAT gateway have to be specified for each workload and management cluster in the values.yml files. This makes the creation of new clusters cumbersome and error prone. It also allows the customer to modify and overwrite by mistake some of the firewall rules which are critical for Giant Swarm to support and monitor the clusters.
Requirements

traffic to the workload cluster's Kubernetes API (destination port 443) must be allowed from the management cluster. All clusters have a NAT gateway its public IP(s) need to be allowed;
traffic to the workload cluster's Kubernetes API (destination port 443) must be allowed from Giant Swarm's VPN exit endpoints on the Internet. The VPN endpoints' public IP(s) be allowed;
all other traffic must be blocked by default. This rule must have the lowest priority.

Outcome
A new cluster will have 3 firewall rules configured if no other rules are configured for the Kubernetes API loadbalancer. See previous requirements section for their exact behavior.
Any additional firewall rules configure in values.yml, if there are any, will be present besides the default rules.
Checks

[x] traffic is allowed from the management cluster;
[x] traffic is allowed from the VPN endpoints;
[x] all other traffic is dropped by default;
[x] any extra firewall rules have higher priority then the default block everything rule;
[x] opsctl login works for management clusters;
[x] opsctl login works for workload clusters;
[x] kubectl-gs get nodes lists all nodes.

Resources

Cloud NAT;
Giant Swarm VPN.

This is done with v0.5.1 release of capg-firewall-rule-operator


fix promise usage. enhance source map

Supercedes PR: https://github.com/feross/timidity/pull/11

Released as 1.3.0


Failed action: Zoning Tax lots - 📁 DataLoading

Run history here

@fvankrieken maybe this is from migrating from library to ingest and deleting the old templates?

Ah shoot. Will fix shortly

Dataloading has passed on my dev branch here
@jackrosacker all set, ztl should be built soon. No need for you to re-run anything

2024-12-01 built and promoted to draft


feat: add limit flag

Signed-off-by: slayer321<EMAIL_ADDRESS>add limit flag
--limit

related issue #40
cc @nyrahul @daemon1024

Can you please fix the conflict by rebasing and please check the review comment ? Thanks


GitHub pages markdown/docsify wiki

Is your feature request related to a problem?
Not it's not.
Describe the solution you'd like
Moving the wiki and '/docs' to a uniformed folder (something like /wiki/...).
With docsify making a searchable and pretty good-looking wiki would then be pretty easy.

files are still markdown
hosted with GitHub Pages

I created a repo with most of the Setup:
https://github.com/m-gschwandtner/memos-test-wiki
Here is the GitHub pages link:
https://m-gschwandtner.github.io/memos-test-wiki/#/
Would make the Wiki a bit easier to use / navigate and to contribute to,
not sure if it currently makes a lot of sense since there are not a lot of wiki page.
Merry Christmas! :purple_heart:
PS. Open to creating PR.
Additional context
https://m-gschwandtner.github.io/memos-test-wiki/#/

Thanks for sharing! I'd really like to have a documentation site for memo. But our current content is very poor, only a few "articles". IMO, writing more wiki/docs has higher priority.
When we get the full documentation content, the separate documentation site can be done with few works.
Merry Christmas!! 💗


[OpenAI Translator]  It would be great to add a two-way translation feature.

Extension
https://www.raycast.com/douo/openai-translator
Description
For example, as a native Chinese speaker, I can set my primary language to be Chinese and also set a target language. For instance, if I want my input to be translated into English, then I can set the target language as English. When I type in a non-Chinese language, the system will automatically recognize the language and translate it into the target language which is English in this case. If I type in my native language which is Chinese, then the system will default to translating it into my chosen target language which is English.
Who will benefit from this feature?
I think the majority of users use translation tools mainly to translate unfamiliar languages. With this feature, users can input in their familiar language and get the another translation result. This issue was translated from Chinese to English through ChatGPT. If this feature can be added, it will allow users like me to achieve this goal more efficiently.
Anything else?
No response

Thank you, @dylan237.  Very helpful advice. However, the accuracy of language detection is only 55% now.(ref:https://github.com/yetone/openai-translator/pull/306)
After I implement a better replacement solution, I should be able to implement the auto invert function you mentioned.


Library drop-down active font color

In the library section, there's an "ALL MUSIC" drop-down next to shuffle which allows you to toggle Purchased vs. Uploaded content. When open, the text of the active element will turn orange upon mouse-over, regardless of theme modifications. (Just found this app by the way, it's absolutely killer.)

Can you please move this issue to https://github.com/gmusic-utils/gmusic-theme.js
Cheers


0.7.0

Upgrades deno_ast.

I'm going to do a new deno_ast release once https://github.com/swc-project/swc/pull/2407 is merged then merge this pr


Allow install to directrory that isn't QHOME

Changed README. Can use env variables Q_SCRIPT_DIR / Q_SHARED_LIB_DIR to override install locations.


llama-cpp-python support

I have added llama-cpp-python support. I also created a example notebook on how to use it!

@microsoft-github-policy-service agree

Thank you!

@alxspiker I found a couple of problems with my implementation and are fixing them right now!

Anyway to support mmap? Seems like its not.

llama_print_timings:        load time =  4772.70 ms
llama_print_timings:      sample time =     3.01 ms /     1 runs   (    3.01 ms per run)
llama_print_timings: prompt eval time = 11246.46 ms /    23 tokens (  488.98 ms per token)
llama_print_timings:        eval time =     0.00 ms /     1 runs   (    0.00 ms per run)
llama_print_timings:       total time = 12235.80 ms
Traceback (most recent call last):
  File "C:\Users\Haley The Retard\Documents\GitHub\AI-X\guidance\_program_executor.py", line 94, in run
    await self.visit(self.parse_tree)
  File "C:\Users\Haley The Retard\Documents\GitHub\AI-X\guidance\_program_executor.py", line 428, in visit
    visited_children.append(await self.visit(child, inner_next_node, inner_next_next_node, inner_prev_node, node, parent_node))
  File "C:\Users\Haley The Retard\Documents\GitHub\AI-X\guidance\_program_executor.py", line 428, in visit
    visited_children.append(await self.visit(child, inner_next_node, inner_next_next_node, inner_prev_node, node, parent_node))
  File "C:\Users\Haley The Retard\Documents\GitHub\AI-X\guidance\_program_executor.py", line 395, in visit
    command_output = await command_function(*positional_args, **named_args)
  File "C:\Users\Haley The Retard\Documents\GitHub\AI-X\guidance\library\_select.py", line 158, in select
    option_logprobs = await recursive_select("")
  File "C:\Users\Haley The Retard\Documents\GitHub\AI-X\guidance\library\_select.py", line 131, in recursive_select
    sub_logprobs = await recursive_select(rec_prefix, allow_token_extension=False)
  File "C:\Users\Haley The Retard\Documents\GitHub\AI-X\guidance\library\_select.py", line 131, in recursive_select
    sub_logprobs = await recursive_select(rec_prefix, allow_token_extension=False)
  File "C:\Users\Haley The Retard\Documents\GitHub\AI-X\guidance\library\_select.py", line 131, in recursive_select
    sub_logprobs = await recursive_select(rec_prefix, allow_token_extension=False)
  [Previous line repeated 477 more times]
  File "C:\Users\Haley The Retard\Documents\GitHub\AI-X\guidance\library\_select.py", line 107, in recursive_select
    gen_obj = await parser.llm_session(
  File "C:\Users\Haley The Retard\Documents\GitHub\AI-X\guidance\llms\_llama_cpp.py", line 244, in __call__
    key = self._cache_key(locals())
  File "C:\Users\Haley The Retard\Documents\GitHub\AI-X\guidance\llms\_llm.py", line 76, in _cache_key
    key = self._gen_key(args_dict)
  File "C:\Users\Haley The Retard\Documents\GitHub\AI-X\guidance\llms\_llm.py", line 69, in _gen_key
    return "_---_".join([str(v) for v in ([args_dict[k] for k in var_names] + [self.llm.model_name, self.llm.__class__.__name__, self.llm.cache_version])])
  File "C:\Users\Haley The Retard\Documents\GitHub\AI-X\guidance\llms\_llm.py", line 69, in <listcomp>
    return "_---_".join([str(v) for v in ([args_dict[k] for k in var_names] + [self.llm.model_name, self.llm.__class__.__name__, self.llm.cache_version])])
RecursionError: maximum recursion depth exceeded while getting the repr of an object

Error in program:  maximum recursion depth exceeded while getting the repr of an object

@alxspiker I have fixed all errors on my side but couldn't reproduce your error, but I added nmap to the settings!

@alxspiker At the moment you have to use my fork of llama-cpp-python to use guidance.
You will find the fork here:
https://github.com/Maximilian-Winter/llama-cpp-python

Related PR in llama-cpp-python: https://github.com/abetlen/llama-cpp-python/pull/252

@Maximilian-Winter this is great, thanks! It will probably be Monday before I can review it properly. Are the there any basic units tests we can add for this? (with small LMs that don't slow down the test process too much) ...might not be possible with LLaMA, but even a file with test that only run locally would be good so we can make sure this stays working :)

(I also just approved the unit tests to run for this)

@slundberg I have added a test file in the tests/llms folder called "test_llamacpp.py".
I used the test_transformers file as a template.

After many attempts I could not get the role chat to work
I've use this code:
import re
import guidance

# define the model we will use

settings = guidance.llms.LlamaCppSettings()
settings.n_gpu_layers = 14
settings.n_threads = 16
settings.n_ctx = 1024
settings.use_mlock = True
settings.model = "path/to/model"
# Create a LlamaCpp instance and pass the settings to it.
llama = guidance.llms.LlamaCpp(settings=settings)
guidance.llm = llama
def parse_best(prosandcons, options):
    best = int(re.findall(r'Best=(\d+)', prosandcons)[0])
    return options[best]

create_plan = guidance('''
{{#system~}}
You are a helpful assistant.
{{~/system}}

{{! generate five potential ways to accomplish a goal }}
{{#block hidden=True}}
{{#user~}}
I want to {{goal}}.
{{~! generate potential options ~}}
Can you please generate one option for how to accomplish this?
Please make the option very short, at most one line.
{{~/user}}

{{#assistant~}}
{{gen 'options' n=5 temperature=1.0 max_tokens=500}}
{{~/assistant}}
{{/block}}

{{! generate pros and cons for each option and select the best option }}
{{#block hidden=True}}
{{#user~}}
I want to {{goal}}.

Can you please comment on the pros and cons of each of the following options, and then pick the best option?
---{{#each options}}
Option {{@index}}: {{this}}{{/each}}
---
Please discuss each option very briefly (one line for pros, one for cons), and end by saying Best=X, where X is the best option.
{{~/user}}

{{#assistant~}}
{{gen 'prosandcons' temperature=0.0 max_tokens=500}}
{{~/assistant}}
{{/block}}

{{! generate a plan to accomplish the chosen option }}
{{#user~}}
I want to {{goal}}.
{{~! Create a plan }}
Here is my plan:
{{parse_best prosandcons options}}
Please elaborate on this plan, and tell me how to best accomplish it.
{{~/user}}

{{#assistant~}}
{{gen 'plan' max_tokens=500}}
{{~/assistant}}''')
out = create_plan(
    goal='read more books',
    parse_best=parse_best # a custom python function we call in the program
)

I appreciate your work, sir. Looking forward to trying this out. Would be amazing to run local ggml models with guidance.

I have fixed most errors without token healing(only produce garbage right now)
Right now I have to use the original tokenizer from huggingface.
Chat mode isn't avaible right now. But patterns, select and stop should work!

I also implemented logit and stop processors into llama-cpp-python and waiting for my pull request to be accepted.
https://github.com/abetlen/llama-cpp-python/pull/271

Thanks! Looking good. I'll take a pass once the PR for llama cpp merges

@slundberg I added a configurable chat mode implementation and added code as a example to the notebook.

@slundberg My logit processor and stop criteria extension was merged into llama-cpp-python

Excellent! I am working to merge support for programatic streaming support, then I'll dig into this. Hope to get through it before the long weekend but we shall see.

@Maximilian-Winter I've published a new version of llama-cpp-python (v0.1.55) that includes the stopping_criteria and logits_processor, I've tested it with your branch and it works.
Just made two changes

            from llama_cpp import LogitsProcessorList, StoppingCriteriaList
            last_token_str = ""
            processors = LogitsProcessorList()
            stoppers = StoppingCriteriaList()

and
                logits_processor=processors,
                stopping_criteria=stoppers,

@abetlen I have implemented it this way:
logits_processor=LogitsProcessorList(processors),
stopping_criteria=StoppingCriteriaList(stoppers),

@abetlen I have implemented it this way:
 logits_processor=LogitsProcessorList(processors),
 stopping_criteria=StoppingCriteriaList(stoppers),

That works too as LogitsProcessorList just extends list

@slundberg Tests are failing because llama-cpp-python is not there. Wasn't sure about adding it as a dependency. How should I handle that and the existence of a model to test?

We can add the dependency to the test section of setup.py. As for a model download, we can try and find a really small model to test with and then download it in the test setup if not already present. Alternatively can test just locally, and skip the tests when run on GitHub runners (like already happens for OpenAI models).
Great work. I went through everything and made a few changes, see what you think (I am about to push). Here are some highlights:

I changed the settings to just be kwargs instead of separate type. That aligns better with the other LLM objects and I think leads to cleaner code for most setups (you can always define a dict first if you want and then pass as kwargs).
I changed tokenizer_name to tokenizer so people could pass object as well as strings. However, I am not sure if long term we can get the tokenizer from llama-cpp-python directly. Is that possible?

One error that seems to remain is that when we turn on streaming for the generation call I get the following error that seems to imply an API difference with hugging face. Any thoughts? (note we can avoid this error when silent=True since then we don't stream by default)
TypeError: create_completion() got an unexpected keyword argument 'streamer'
Another error is that llm.role_end is mean to be callable so right now that chat example fails. Should be a fairly easy fix I think.
Thanks!!

@slundberg I have implemented proper role_end again, also implemented streaming support.

@slundberg I think the best way would be to test just locally. The smallest model right now is a 7B parameter model which is already 3.8gb of memory.

Just a note here, I was still getting some tokenization issues and realized it is going to be hard to maintain so much code that is similar between transformers and llamacpp, so I am going to try and push a proposal to share more code tonight.

I pushed a proposal in the form of LlamaCpp2, along with lots of updates to Transformers that are related because we will want to depend on them. I think we need to inherit from the Transformers LLM class because otherwise we duplicate lots of code that is tricky and should only live in one place :)
LlamaCpp2 does not work fully yet, but I am pushing to to see what you think @Maximilian-Winter.
thanks again for all the hard work pushing on this :)

@slundberg Will take a look later today

@slundberg Looks good to me! But I think the tokenizer of llama.cpp is bugged because it refuse to give me the eos or bos token.
It is always empty when I try to decode it from the id!

@slundberg Looks good to me! But I think the tokenizer of llama.cpp is bugged because it refuse to give me the eos or bos token.
It is always empty when I try to decode it from the id!

Yeah, I just think we can just return "" directly for now. I just pushed a few more fixes. Can I hand this back over to you to wrap up? There is some difference with the way the logprobs are returned that is not quite matching how transformers returns it yet, but otherwise I think we are close!
I also noticed that logit bias processor in inside llama-cpp-python seems to save the bias values after the local logits variable is already set:
https://github.com/abetlen/llama-cpp-python/blob/232880cbc677db1998afa240c25e58090f399072/llama_cpp/llama.py#L373-L383

@slundberg I will try to make it work later!

Please merge this microsoft or at least help support it. This would be HUGE for guidance

Any progress?

Hmm. Looks like there's a conflict with 47b1cd4a624b4b0c0f23ae5e2b3d870b6cff2c69. Trying to use a519012368fcb7946789bad50688858beef4a294, a merge with brings the former commit into the PR...
>>> import guidance
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/nix/store/0j6zxl1kvqkvhcw0i2chdqxx22xsi5sf-python3-3.10.11-env/lib/python3.10/site-packages/guidance/__init__.py", line 7, in <module>
    from ._program import Program
  File "/nix/store/0j6zxl1kvqkvhcw0i2chdqxx22xsi5sf-python3-3.10.11-env/lib/python3.10/site-packages/guidance/_program.py", line 17, in <module>
    from .llms import _openai
  File "/nix/store/0j6zxl1kvqkvhcw0i2chdqxx22xsi5sf-python3-3.10.11-env/lib/python3.10/site-packages/guidance/llms/__init__.py", line 7, in <module>
    from ._llama_cpp import LlamaCpp
  File "/nix/store/0j6zxl1kvqkvhcw0i2chdqxx22xsi5sf-python3-3.10.11-env/lib/python3.10/site-packages/guidance/llms/_llama_cpp.py", line 17, in <module>
    class LlamaCpp(LLM):
  File "/nix/store/0j6zxl1kvqkvhcw0i2chdqxx22xsi5sf-python3-3.10.11-env/lib/python3.10/site-packages/guidance/llms/_llama_cpp.py", line 21, in LlamaCpp
    cache = LLM._open_cache("_llama_cpp.diskcache")
AttributeError: type object 'LLM' has no attribute '_open_cache'

yeah this needs to be updated. I've tried forking Max's and git pulling Microsoft's main branch, but there have been a lot of changes since June so lots of things need tweaking.

Any updates on this?

Any plans on merging this at some point?

guidance's templating is miles more friendly to use than lmql.
But... guidance, are you still alive?

any update on this ???

@Maximilian-Winter thank you so much for all your hard work on this! Due to some external circumstances over the summer I couldn't come back to push it over the finish line until this fall (with v0.1). This PR strongly informed the design decisions we made for Llama.cpp support in v0.1 though so it was very useful.
I am closing this now since we now have full llama.cpp support in v0.1 :)


nimble/ll: Fix sending HCI Number of Completed Packets event

The calculations for sending this HCI event periodically seem strange,
probably something was mixed up in the past here.
After fix I believe this does what it is supposed to do: every X ticks
we'll just go through all connections and send HCI event no matter if
there is something to send or not.
Also added some with reference to spec section.

Ok, so I had to write this step-by-step on a paper in order to find out that it seems to work, but I find it really hard to understand - especially the part that 'rate' is added to 'last time' at the end of function and the fact that BLE_NUM_COMP_PKT_RATE is defined in ticks but in code it is multiplied by OS_TICKS_PER_SEC only add to the mystery :-)
Also I found an issue with my change as well so in new patch version I updated only two things I find most difficult to follow.

I certainly agree the original code is very confusing and could be written differently to make it clearer. I would have used a timer for it but wanted to save memory. So all good...


[website] Update website

sunlarin yanina sitedeki proje description guncelleme de ekleyelim:
"GroceryBee is a robot to assist grocery stores in keeping up with their online orders. GroceryBee will help grocery store employees by collecting the items which are required for an online order from the store shelves, thus speeding up the delivery process. GroceryBee is designed to make decisions in an uncertain environment, so it is able to exploit real-time information from RGB-D cameras to make real-time changes in planning. GroceryBee is able to collect required items in response to the orders while navigating between the supermarket aisles without crashing. It can easily detect requested items on the shelves, picks them up safely and brings them to the delivery point for speedy delivery to customers."
final report guncelleme
gecen donem ve bu donem demo slidelarini koyma
videoyu guncelleme

add documents to the repo


E2e tests for higher level resources

Some higher level resources need e2e tests for actual end to end functionality validation. Below is the list of current such resources which certainly need additional e2e tests:

[ ] ReplicaSchedulingPreferences as in #46.
[ ] MultiClusterDNS as in #59

The implementation of these tests is dependent on #89 (or some other strategy, for example self validation external to CI using managed clusters or BYOC).

@irfanurrehman Can RSP testing be considered complete with the merging of #392?
@shashidharatd Is there additional testing needed to satisfy the e2e requirement listed above?

There were some test cases missing like cluster fail-over which required 2 clusters to test. Now we have support for deploying multiple clusters in CI, we should add such test cases.

@shashidharatd Would you please add detail to this issue to aid in either implementation or review of that testing?

@shashidharatd can we consider the e2e testing complete for service dns now?


scroll bug in man pages

Hello, I believe I have found a bug with scrolling in the man pages. I couldn't find it reported anywhere, but if you open a man page and hit enter, the : position marker drops down but the screen does not scroll with it, and you cannot scroll to follow the : and see the rest of the man page.
If this is not an exceptionally hard bug (as per the markings you have given other issues) I would love to take a crack at this in my spare time.

Here's what I see after hitting enter a few times. Do you see something different?

Yes, my : disappears off screen and does not follow the scroll, and I'm not sure of why everything is underlined?

Fixed.


Parsing error for logic operator in WHERE clause

The related function is https://github.com/ddkang/aidb/blob/0d466fe3c44e17f467f0c7dcf10a14af9baa7a29/aidb/query/query.py#L181-L211
In WHERE clause, the AND operator has higher priority than OR operator.
e.g. WHERE x_min > 600 OR objects00.frame > 700 AND x_min = 1 OR x_max = 1
the correct parsing result should be same as the  parsing result of 'WHERE x_min > 600 OR (objects00.frame > 700 AND x_min = 1) OR x_max = 1
However, current parsing result is same as 'WHERE ((x_min > 600 OR objects00.frame > 700) AND x_min = 1) OR x_max = 1'
To avoid this issue, please use () in WHERE clause for complex logic operation.

@ttt-77 is this done?

No

Hi @ttt-77, can I try helping with this?

Sure


Buffering issue

https://github.com/itszechs/DriveStream/assets/105588608/1d8542a7-8d5a-46fc-9b31-6733cdfbe36d

I don't why it is so much buffering during playing video even wifi speed is good..
Please give me some solution of it please 🙏🏻
Attached video of buffering and wifi speed

You're playing on TV and the speedtest is from the phone.
Though it isn't mentioned anywhere, but Google Drive sort of has a "shadow ban" which limits download speed of a file by alot <2Mbps.
I don't why it happens or when, but it is fixed if your IP Address changes.
This is most likely to be the reason, or your TV is on 2.4Ghz WiFi incapable of providing enough bandwidth for streaming any huge files.
In any case, streaming is handled by mpv and ExoPlayer.

I dont know what is main issue but tv is connected to 5Ghz and mostly it works really fine even file is 50gb but sometimes it buffering so much even file is 2gb 🥲

Google Drive sometimes works mysterious ways

Ok bro.. if you say so.. thnkx


Update turpial-description.md

changed WROOM back to WROVER and changed hyperlink to the one found in the turpial-firmware repo README (which is also a cleaner hyperlink)

I am actually still confused about this board. Documentation says this is the board used for the Turpial, but it does not look like the Turpial board photos on the main README page. Can anyone clarify?

@xmrhaelan We actually use the ESP-WROVER-KIT and the LAUNCHXL-CC1312R1 boards to develop and test the source code, these are the same include the components that are in the Turpial boards.

Exactly, if you want to create a complete Tutorial from scratch, you need 3 main components.

One ESP32 dev Board
Something like this WROVER-KIT
One Radio Module CC1312 or similar, CC1310, CC1350, CC1352, etc.
If we want a battery powered system: LiPo Charger & Gauge Fuel + battery

All the elements described above are included in the board shown in the README.md file and that board is in pre-production stage right now. there are some elements must be improved


Options for selecting preferred dark theme

fixes https://github.com/bluesky-social/social-app/issues/2595
Adds preference in settings to choose between the default dark theme or the OLED dark theme. To support this, we needed to make some changes (which incidentally will make adding additional themes down the road much easier):

Create a dimTheme theme which uses all of the base tokens from darkTheme but sets backgroundColor a dim color instead of black
Both the ALF and the legacy ThemeProvider take in the name of a theme now rather than a particular color mode. Options are light, dark, or dim. dim is the default dark theme on a new install.
useColorMode and useSetColorMode is changed to useThemePrefs and useSetThemePrefs. Respectively, both contexts have colorMode, darkTheme and setColorMode, setDarkTheme as their values
useColorModeTheme is changed to return the memoized theme name, and we handle the logic here to determine which theme name to use regardless of the color mode being system/light/dark.
Small modification to default to a black background when loading the web app and your system color mode is set to dark

Additionally on web since there are some styles inside of the root HTML document, it seems better to change this logic a bit. Instead of relying on @media here, we can use use the existing updateDocument() from the color mode context to set the particular theme that is being used (light, dark, or dim). Instead of adding/changing the class name inside of the context's useEffect however, we can handle that when the useColorModeTheme memo updates.
https://github.com/bluesky-social/social-app/assets/153161762/d264b21a-2845-4f70-8cc7-a78b3272650e

"Dim" and "Dark" are good name!


Storybook V7 Support

I recently tried to upgrade to storybook7 and Vite but the package is giving this error- _No matching export in<EMAIL_ADDRESS>from import "app".
 I'm using<EMAIL_ADDRESS>and getting different issue which is blocking me from being able to test my package.
Once these are resolved I should be able to test storybook-vue3-router BUT I expect having read the migration guide that the package as it currently stands will not be compatible so ill need to refactor / fix bugs and then I will release a new major version to function with<EMAIL_ADDRESS>Ill be working on this in my storybook-7 branch: https://github.com/NickMcBurney/storybook-vue3-router/tree/storybook-7 and will update here once new version is published.

Storybook 7 is officially launched tomorrow. I too get this issue, will you be publishing a fix?
X [ERROR] No matching export in "../../node_modules/.pnpm/@storybook+vue3@7.0.0-rc.2_vue<EMAIL_ADDRESS> for import "app"

<EMAIL_ADDRESS>er.js:7:9:
      7 │ import { app } from "@storybook/vue3";

https://github.com/storybookjs/storybook/issues/19200

Thanks for linking that issue @blowsie, I have been trying to get decorator working with storybook 7 but with app export missing I've been unable to. Issue I have is that although I have code which should implement vue-router, the decorator is loaded after component mounts (which throws errors because vue-router not ready).
I'll keep my eye on that issue and hopefully get this working soon.

Hi @NickMcBurney , please see my comments over here...
https://github.com/NickMcBurney/storybook-vue3-router/pull/39

Here is my working version with vue3 and vite
https://github.com/blowsie/storybook-vue-router/tree/sb-7

@blowsie thanks for your example. I've fixed the issue and migrated to @storybook/vue3-vite.
PR Updated and working: #39
I need to do more testing and publish new version but looking good so far.

Looks like you beat me to it. Good work. Glad I could help a little

@shinodkharim you can try installing this version 3.0.0-next.0
npm i -D<EMAIL_ADDRESS>Once Storybook publishes v7 (non-prerelease) I'll publish v3.0.0 (non-prerelease).

New version published using<EMAIL_ADDRESS><EMAIL_ADDRESS>

Hey @NickMcBurney, we found that using new setup function exported from @storybook/vue3 (sb7)
As documented [here ](https://github.com/storybookjs/storybook/blob/325c0c22c3de17efa93fcc73867f22ecda7ac95b/MIGRATION.md#70-breaking-changes
There is an issue with this approach, especially for addon authors.
The issue is that the setup function can only be called once... see here
https://github.com/storybookjs/storybook/blob/next/code/renderers/vue3/src/render.ts#L19
This means that an addon author is not able to safely use this setup method, since once it is called in the preview.ts in the users storybook, it will break.
There are a few workarounds here, but ultimately it leads to inconsistency when using addons and setup in the preview file.
I raised this with the storybook in team, here
https://discord.com/channels/486522875931656193/490822288736780288/1090996147620950067
Hopefully we can make a nice workaround to this issue.

Hey @blowsie, thanks for bringing this to my attention.
Do have any examples of the issues caused/weird behaviour? I've not noticed anything when testing myself - but my tests are very simple and not a great representation of real-life uses.

Note to anyone discovering this issue. With<EMAIL_ADDRESS>This import:
import vueRouter from 'storybook-vue3-router'

...must be changed to:
import { vueRouter } from 'storybook-vue3-router'

I've publish new 3.0.0 version with storybook 7 support. Also readme is updated explaining issue mentioned by @matthew-dean - I had this noted in PR but it must have been missed.


Use a fixed default connection pool size

See https://github.com/vapor/fluent/issues/564#issuecomment-416194623 for discussion. Open to changing the exact value of the constant.

Didn’t notice
https://github.com/vapor/database-kit/pull/47, sorry.


iPXE boot not always load cloud-init if there are more than one interace run dhcp

RancherOS Version: (ros os version)
v.1.1.0
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
As suggested with Sven in https://github.com/rancher/os/issues/1790 I open this issue.
This happens If you have more than one interface on your machine. To reproduce, create a KVM VM with two interfaces, pxe boot from one of the interface. In case you also have another dhcp server running on another interface, it is almost 100% fails.
I guess this is a timing issue, related to https://github.com/rancher/os/issues/2141

Tested with RancherOS v1.2.0-rc2
Fixed, closed it.


[feat:host-env] To deploy fullstack on AWS Fargate, added HOST environment to expose service externally

Fargate is the only way to deploy of dioxus fullstack on AWS.

However, <IP_ADDRESS> blocks to expose port to ESC Service.

Currently, we can change host address by addr function. However, to use it, we need to handle complicated entry point at apps.

You can also change the address fullstack uses with the --addr command line option on the dioxus-cli or the the server binary dioxus fullstack builds

You can also change the address fullstack uses with the --addr command line option on the dioxus-cli or the the server binary dioxus fullstack builds

does dx build also support the --addr? I can't see --addr option in dx build --help.
When deploying its binary to fargate, we need --addr option in dx build or in built biyard. @ealmloff

You can also change the address fullstack uses with the --addr command line option on the dioxus-cli or the the server binary dioxus fullstack builds

does dx build also support the --addr? I can't see --addr option in dx build --help. For deploying its binary to fargate, we need --addr option in dx build or in built biyard. @ealmloff

--addr is supported in dx serve and when running the final server binary standalone

You can also change the address fullstack uses with the --addr command line option on the dioxus-cli or the the server binary dioxus fullstack builds

does dx build also support the --addr? I can't see --addr option in dx build --help. For deploying its binary to fargate, we need --addr option in dx build or in built biyard. @ealmloff

--addr is supported in dx serve and when running the final server binary standalone

I meant that the final server binary is dist/{service} binary after dx build --release.
I think we need to use the dist and built binary for docker, instead of dx serve

I meant that the final server binary is dist/{service} binary after dx build --release. I think we need to use the dist and built binary by dx build --release for production, instead of dx serve

Yes, you can pass the --addr to the binary built with dx serve. dist/{service} --addr <IP_ADDRESS> --port 1111

I meant that the final server binary is dist/{service} binary after dx build --release. I think we need to use the dist and built binary by dx build --release for production, instead of dx serve

Yes, you can pass the --addr to the binary built with dx build. dist/{service} --addr <IP_ADDRESS> --port 1111

@ealmloff I've tested on binary built with dx build --release --platform fullstack of dx v0.5.6.
However, --addr <IP_ADDRESS> --port 5000 does not work for me.

--addr <IP_ADDRESS> --port 5000 for fullstack only works in the git version of dioxus if you are using the launch function or launch builder

--addr <IP_ADDRESS> --port 5000 for fullstack only works in the git version of dioxus if you are using the launch function or launch builder

Thank you for the information. However, it seem not to work with environment variables. I tried to build below.
VERSION=v0.1.0 COMMIT=b0c608b LOG_LEVEL=debug DATE="" dx build --release --platform fullstack

And the environment variables will used in server code below
#[server(endpoint = "/version", input=GetUrl)]
pub async fn version() -> Result<String, ServerFnError> {
    Ok(match option_env!("VERSION") {
        Some(version) => match option_env!("COMMIT") {
            Some(commit) => format!("{}-{}", version, commit),
            None => format!("{}", version),
        },
        None => match option_env!("DATE") {
            Some(date) => date.to_string(),
            None => "unknown".to_string(),
        },
    }
    .to_string())
}

And the web build cause panic as below
thread 'tokio-runtime-worker' panicked at /home/hackartist/.cargo/git/checkouts/dioxus-1e619ce595d3799d/40f936d/packages/cli/src/builder/web.rs:96:18:
called `Result::unwrap()` on an `Err` value: failed reading '/home/hackartist/data/devel/github.com/biyard/photodek/dist/photodek.wasm'

Caused by:
    No such file or directory (os error 2)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2024-07-23T02:58:02.484577Z ERROR dioxus_cli::builder::web: Bindgen build failed: JoinError::Panic(Id(31), ...)
thread 'tokio-runtime-worker' panicked at /home/hackartist/.cargo/git/checkouts/dioxus-1e619ce595d3799d/40f936d/packages/cli/src/builder/web.rs:96:18:
called `Result::unwrap()` on an `Err` value: failed reading '/home/hackartist/data/devel/github.com/biyard/photodek/dist/photodek.wasm'

Caused by:
    No such file or directory (os error 2)
Error: 🚫 Building project failed:

Caused by:
    Failed to build project

no dx git version does work properly. @ealmloff

--addr <IP_ADDRESS> --port 5000 for fullstack only works in the git version of dioxus if you are using the launch function or launch builder

@ealmloff Thank you for the information.
I've tested with git version. However, the git version seems to be unstable, right?
I've installed dx with git version, right now. But it doesn't generate any binary in dist directory. In fact, I previously used dx git version. However, from yesterday, it couldn't serve my project with address already used in error, but practically no program binding that port by sudo netstat -nltp.
And dx cargo version does work properly and generate binary file in dist on the same project.

The versions of the dioxus-cli and dioxus itself must match because they communicate with each other at build time. The new version of the CLI proxies fullstack in dev mode. The old version of dioxus and the CLI could both be trying to serve on the same port. Updating dioxus should fix that issue

cargo install --git https://github.com/DioxusLabs/dioxus dioxus-cli

Thank you. Finally, I've check it out and it does work with below.

Cargo.toml: dioxus-html for file-engine feature.

[dependencies]
dioxus = { git = "https://github.com/DioxusLabs/dioxus", version = "0.5",  features = ["router", "fullstack"] }
dioxus-html = { git = "https://github.com/DioxusLabs/dioxus", version = "0.5" }

Running script

dist/bootstrap --addr <IP_ADDRESS> --port 8080

I will close this PR.


Support optparse-applicative 0.13

Hi,
I noticed the constraint added in #752. Would it be possible to support optparse-applicative 0.13?

Sure, but it'll involve a code adjustment to deal with the breaking changes of 0.13. I'll look into it after the next major postgrest release which is coming soon.

That's great to hear! We'll wait for the next major release to add into Arch Linux's official repositories then. Thanks!

Much appreciated!

The release is out and new binaries are available at https://github.com/begriffs/postgrest/releases/tag/v<IP_ADDRESS>
Do Arch packages require building from source, or do one of those binaries suffice?

We will be building from source, thanks for the update :)

v.0.4 is still contraining optparse-applicative < <IP_ADDRESS> which mean postgrest won't appear in the next stack LTS-8  that should be released in a week or so.
Can I try and help on this issue ?

I have just realized that postgrest is not on stackage ... so the urgency point is just moot.

@begriffs let me know if you need some help regarding this issue. Maybe you maintain a branch that has already incorporated such changes. If you haven't done any work on this, I am willing to give it a shot in a couple of days).

Sorry for the delayed response. I'd love some help upgrading optparse-applicative if you want to give it a shot.

@begriffs Could we get this change in a 4.0.1 release or something ? That would really help to get it to stackage, which in turn helps to get it into nixpkgs, which in turn help (me) when trying building satellite project such as postgrest-ws.


New project with manually typed path failed to open in 1.1.0

After creating a new project by manually typing in a folder name, an error is displayed: "Open project failed". More details are displayed in the console.
No problem opening the new project manually by the way.
This problem occurs in 1.1.0 but not in 1.0.9.
Example video

Fixed already, thanks~


Input to control the dimmer with a wall switch

@JeffResc One thing I'm missing in the Sonoff D1 Dimmer module is an input to control it with a momentary wall switch. Short press would switch the dimmer on/off, long press would cycle through the brightness level back and forth.
Did you consider adding such option to your custom configs? If I'm not mistaken the GPIO2 pin is broken out on the boards, and could probably be used for that.

BTW there is also pad #5 exposed which is connected to GPIO5 (and nothing else) - see top right corner.

Tested the binary_sensor automations and they do what I need. Thanks again @JeffResc 😀


Fail when there are no selected streams

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3192
Originally created by @vischous on 2022-01-31 15:01:53

Hit something today similar to this, want to add / change this to

Fail when there are no selected streams

Use cases

When starting a project if you forget to select any streams, you'll get a failure
If you're using the select filter override and the tap you're using doesn't have that stream (ie no streams are selected) you'll fail, instead of succeeding with a 0 error code

Idea is similar to https://gitlab.com/meltano/meltano/-/issues/2861, but more for every day runs of meltano than just for configuring meltano.

I think we can do this rather than in Meltano, but it would be nice if we could eventually pair this with https://github.com/meltano/sdk/issues/1409.
For now, we could at least emit a warning when no stream is selected.

Related:

#1409


fix pasting to file by adding 'w' mode to open

Thanks for the bug fix. For any future pull requests, please send it to the dev branch instead of master. Thank you!


Allow DROP VIEW and DROP MATERIALIZED VIEW

The DeleteTables function was only dropping tables, despite the rest of the project being aware of all BigQuery table types. This PR moves those table types to internal/types to be used more easily, and then checks for the table type when dropping a table.
@ohaibbq I had made a different candidate branch candidate/rb20240815, but saw that our fork of this repo and go-zetasqlite have some mismatch with goccy's when I rebased it (both ours and his have quite a few changes). Do you think it would be easier to get our forks in sync before getting this change in? (I'm not sure what the upstream response time is).
This change would unblock a few issues for us, so I'd be happy to make a new release for us with this change and then spend some time contributing to syncing with goccy when I am back from PTO.

Let's make a new release to candidate/rb20240328. I had spent some time in August rebasing but did not follow through with a release. I'm likely going to plan some emulator maintenance for Q1 which would include getting our fork up to date.


Create simple webserver system for testing

Related to:

#21
#23

After working with this software for a while, I'm becoming aware that there are many valid site configurations out there that we are unable to navigate due to the limitations of the spider and harvesting system.
Given the above planned features for the spider, it would improve code testing significantly to set up a simple web server with a robots.txt and sitemap.xml at the base that delivers content in some of the ways commonly used by data repositories. For example, being able to test the navigation of javascript elements that render JSON-LD content after the page is loaded (i.e. MagIC DataONEorg/member-repos#16), an application/ld+json delivery system (i.e. Harvard Dataverse DataONEorg/member-repos#52, some valid but alternative configurations of schema.org data (i.e. CanWIN DataONEorg/member-repos#67) and perhaps some misconfigured robots.txt scenarios (i.e. Borealis DataONEorg/member-repos#51), without needing to crawl the repositories themselves.

Also potentially useful for testing #35

Example server tree:
├── metadata
│   ├── CANWIN.jsonld
│   ├── HAKAI_IYS.jsonld
│   └── HD.jsonld
├── robots.txt
└── sitemap.xml

Content negotiation using Django REST framework: https://www.django-rest-framework.org/api-guide/content-negotiation/

Removing label as this is not necessarily related to a version.


Cross platform python

These build-script changes have been tested on cmake, and the generated python bindings pass the tests in test.py on both linux and MacOS.
The defaults for the build script should make it behave the same as before adding cmake support, to avoid breaking existing workflow for core devs, but this still needs to be tested by someone who actually uses xcode.

Hi! Somehow I totally missed this PR until now; sorry!


TextSearchFacet refreshes unnecessarily

When you ctrl/PageUp or ctrl/PageDn into a page, the TextSearchFacet's event handler fires when e.g. the PageUp key is released, causing a complete facet refresh even though the value in the input field hasn't changed.  This is annoying in trivial cases, but can be a real pain if the current facet setup is expensive to compute.
The event handler is set up in TextSearchFacet._initializeUI()

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/4081046-textsearchfacet-refreshes-unnecessarily?utm_campaign=plugin&utm_content=tracker%2F32795&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F32795&utm_medium=issues&utm_source=github).

Hi @tfmorris,
I recently started experimenting with Open Refine and found that it is a pretty neat tool.
I decided that maybe I should begin contributing code as well and thought that it might be a good idea to start with smaller issues like this one.
May I work on this issue and submit a pr?

@gideonthomas thank you for proposing your help. We will be more than happy to review your contribution.
If you have any questions you can post on the [developer mailing list] (https://groups.google.com/forum/?fromgroups#!forum/openrefine-dev)


Is the ds4 bt audio still worked on?

Ryochan made some impressive progress but its only updates on this are well not in any way affecting the actual feature. He kinda gave up since he didnt have enough support and time to figure it out.

It is but it's reached a dead end that is difficult to explain since the source of the problem is not yet well understood. Is it an implementation issue? Or OS shipped driver issue? Nobody knows, nobody helps, so it depends on reverse engineering, trial and error and last but not least: luck.

Even if, what good would that be for? I can't and won't delegate work to random hobbyists... That's not how open-source works.


Smart charging Test excluding stations

In some tests generated logs are used to check certain functionalities

@OliveGerste PR in Draft but in To Be Reviewed pipeline?

@OliveGerste PR in Draft but in To Be Reviewed pipeline?

Hi @LucasBrazi06, I would need a review on the new approach. (For excluding charging stations and testing with generated logs)
Especially if you can think of another case, where a charging station needs to be excluded. Besides of the cases implemented. Should we also take into account the charging station capabilities?
Drafts need to be put in dev cross for a review then right?

Drafts need to be put in dev cross for a review then right?

Yes and you assign someone to review your PR :-).
Thanks!


Dart spec does not explain that != calls operator ==

Look at this code:
class A {
  bool operator==(A other) {
    return false;
  }
}

main() {
  A a = new A();
  print(a == a);
  print(a != a);
}

Straightforward.
Here, the expression a != a calls A's operator==. I can't find ANYWHERE in the Dart docs that says so. If this fact is indeed missing, it would be very nice to add.

Thanks for the input! I think Lasse's excerpt shows that the language specification does make this fact explicit, but I also think that it would be useful to have it mentioned here: https://www.dartlang.org/guides/language/language-tour#overridable-operators. So I'll change the label to area-documentation and suggest such a change.

Thanks. I had tried Googling for this but it took me a couple of days of
doing so until I found it this morning, after I thought to add "spec" to my
search.
I haven't followed the link in the email above yet but I imagine it's to
the ECMA spec I found this morning.
I did not mean to suggest this fact was completely undocumented, only that
the documentation was not readily discoverable. Adding it to the Language
Tour would no doubt fix this. The Language Tour is of course meant as a
high-level document, while the spec is very detailed; it's unfortunate that
there seems to be nothing in-between.
Googling for 'dart "operator =="' does list the Language Tour on the first
page, amid a bunch of less interesting hits. Curiously, so does searching
for 'dart "operator !="' ! In either case, the spec does not appear until
far below.
BTW, I work at Google. I had initially filed this bug at Google, then
refiled it here. I think it probably got a little garbled in the refiling.
Thanks!
Cheers,
John
On Thu, Sep 28, 2017 at 2:46 AM Erik Ernst<EMAIL_ADDRESS>wrote:

Thanks for the input! I think Lasse's excerpt shows that the language
specification does make this fact explicit, but I also think that it would
be useful to have it mentioned here:
https://www.dartlang.org/guides/language/language-tour#overridable-operators.
So I'll change the label to area-documentation and suggest such a change.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/sdk/issues/30896#issuecomment-332786034,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYXMuzTsa3FVXtEQ_z_DOVF4W0Jit0eks5sm2sRgaJpZM4Pkuo3
.

--
Cheers,
John

One thing we could do is to mention it in the Object.== operator documentation.
It's still not possible to look up != directly, but finding == is probably the next thing a user will try.

On Fri, Sep 29, 2017 at 2:06 AM, John DeTreville<EMAIL_ADDRESS>wrote:

Thanks. I had tried Googling for this but it took me a couple of days of
doing so until I found it this morning, after I thought to add "spec" to my
search.
I haven't followed the link in the email above yet but I imagine it's to
the ECMA spec I found this morning.
I did not mean to suggest this fact was completely undocumented, only that
the documentation was not readily discoverable. Adding it to the Language
Tour would no doubt fix this. The Language Tour is of course meant as a
high-level document, while the spec is very detailed; it's unfortunate that
there seems to be nothing in-between.
Googling for 'dart "operator =="' does list the Language Tour on the first
page, amid a bunch of less interesting hits. Curiously, so does searching
for 'dart "operator !="' ! In either case, the spec does not appear until
far below.
BTW, I work at Google. I had initially filed this bug at Google, then
refiled it here. I think it probably got a little garbled in the refiling.

Hello John,
just curious, what does 'filed this bug at Google' mean? In the context
where I'm working (on the Dart language team), we don't have any other
issue manager than github, so I'm not sure how any other issue management
system could be used to file a bug that we would ever hear about...

Thanks!
Cheers,
John
On Thu, Sep 28, 2017 at 2:46 AM Erik Ernst<EMAIL_ADDRESS>wrote:

Thanks for the input! I think Lasse's excerpt shows that the language
specification does make this fact explicit, but I also think that it
would
be useful to have it mentioned here:
https://www.dartlang.org/guides/language/language-tour#
overridable-operators.
So I'll change the label to area-documentation and suggest such a change.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/sdk/issues/30896#issuecomment-332786034,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAYXMuzTsa3FVXtEQ_z_
DOVF4W0Jit0eks5sm2sRgaJpZM4Pkuo3>
.

--
Cheers,
John
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/sdk/issues/30896#issuecomment-332996041,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJKXUtMmSpbex4NUQirJ_cLfEuvFVR1Tks5snDR-gaJpZM4Pkuo3
.

--
Erik Ernst  -  Google Danmark ApS
Skt Petri Passage 5, 2 sal, 1165 København K, Denmark
CVR no. 28866984

I haven't followed the link in the email above yet but I imagine it's to the ECMA spec I found this morning.

The ECMA spec is a number of steps behind the development of the language. The bleeding edge spec can be found at https://github.com/dart-lang/sdk/blob/master/docs/language/dartLangSpec.tex.

Excellent; thanks!
Cheers,
John
On Fri, Sep 29, 2017 at 1:41 AM Erik Ernst<EMAIL_ADDRESS>wrote:

I haven't followed the link in the email above yet but I imagine it's to
the ECMA spec I found this morning.
The ECMA spec is a number of steps behind the development of the language.
The bleeding edge spec can be found at
https://github.com/dart-lang/sdk/blob/master/docs/language/dartLangSpec.tex
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/sdk/issues/30896#issuecomment-333067871,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYXMoKGa2waQ1xEBix1bqc8fiT6wyMPks5snK0egaJpZM4Pkuo3
.

--
Cheers,
John

This issue was moved to dart-lang/site-www#1081


Str::snake does not work correctly with Unicode

Laravel Version: 9.17.0
PHP Version: 8.1
Database Driver & Version: MySQL 8

Description:
Str::snake('простаяСтрока') returns 'простаястрока', but should return 'простая_строка'.

Since the function does not work correctly with unicode, this test, although it passes, returns incorrect results. Actually, the result should be like this - żółta_łódka

The same way would happen on a language that doesn't have uppercase, like arabic, chinese, korean or japanese.
You may need to create an snake function for your language exclusively.

You'll need to create your own function for this.


[Impeller] Create a utility to create zero-copy growable device buffers.

This is a property of impeller::HostBuffer that is useful when building up buffers that will eventually be sent to the device incrementally. However, as the name implies host buffer do create an allocation on the host before eventual upload.
To reduce programmer errors and make the API around managing buffers nicer to work with, there should be a growable device buffer utility. To make this utility zero copy in all cases (especially OpenGL backends where there needs to be a transfer to the reactor), the mapping will have to ref-ptrs.

cc @bdero

Closing as cant-fix.


Unify dart:html/dart:io WebSocket interfaces.

This issue was originally filed by<EMAIL_ADDRESS>
The WbeSocket interface in dart:html is different than the one defined in dart:io.
So when you have a class that could perfectly well work on both the console and the browser (e.g. a client for a websocket protocol) you have to create and maintain two slightly different versions.

Why was this closed?


Custom Component Support

Hello again.
I intend on using this InputTag component: https://www.npmjs.com/package/vue-input-tag
I have added the name to the config.
config: {
        components: {
          'InputTag':InputTag
        },
}

But I don't know how to get this to work.
Any suggestion?
Thanks.

Hi,
You also imported the component?
Maybe you need to write a wrapper around, because the low code widgets have
a certain API, on how to read data etc..
Michael Kingsley @.***> schrieb am Di., 18. Mai 2021,
16:47:

Hello again.
I intend on using this InputTag component:
https://www.npmjs.com/package/vue-input-tag
I have added the name to the config.
config: {
components: {
'InputTag':InputTag
},
}
But I don't know how to get this to work.
Any suggestion?
Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/KlausSchaefers/vue-low-code/issues/12, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABWHOQEDFA7Y2IW7VVZOJ3DTOKD2FANCNFSM45CZPLEA
.

Hi,
take a look here: https://github.com/KlausSchaefers/figma-low-code-custom-component
I wrote a wrapper around the Tag List, to pass the data from the viewMode into the tag list and back. This workaround is a little ugly, I will think about making it better.
Please also node, that you might need to add a frame around the component in Figma, otherwise the position might be wrong.

The code of the component is
<template>  <div class="">      <InputTag v-model="tags" @input="onChange"/>  </div></template>

<script>import InputTag from 'vue-input-tag'export default {  name: "MyComponent",  props: ['value', 'element', 'model', 'config'], // here we get the data passed. The value is the viewModel  data: function () {    return {      tags: ['A']    };  },  components: {    'InputTag': InputTag  },  methods: {    onChange (e) {      // write the changes back      this.value.tags = e    }  },  mounted () {    // read the tags from the viewModel    this.tags = this.value.tags  }};</script>

The home imports the component as this
<template>

    <Figma :figma="figmaJSON" v-model="viewModel" :config="config"/>

{{viewModel}}

</template>

The result will look like this. The pink box is replaced with your component, which adds the TagList.

INCREDIBLE!!!!
This worked.
And wrapping it in a frame helped with the positioning issue I encountered.
I can't thank you enough for this. 🙏
I really appreciate @KlausSchaefers . 🙌

Thanks for the kind works. I also appreciate that you put all the effort in helping me fix those issues. I saw your latest updates, the page look very good! Honestly, I am a bit surprised how good the transformation  :D. If you are done with your project, we could maybe write a short article to advertise the project a little?
I will add in one of the next release some 'auto-wrapping' that should make it easier to include custom components.

Yes. Thank you @KlausSchaefers
Still making little progress:
Here I hosted the work in progress: https://figma-low-code.herokuapp.com/
This is a video demo of main functionality as at now: https://drive.google.com/file/d/1Dz698AIR1OH49qOLi4X1O6LA8N6Q50bC/view?usp=sharing
Still building, and vue-low-code makes development faster. So would be done soon.

Very nice!


Unable to Launch Flowser

Describe the bug
Failed at the<EMAIL_ADDRESS>dev:logs script 'docker-compose --env-file .env.dev -f docker-compose.yml -f docker-compose.dev.yml logs -f'.
To Reproduce
Installed Flowser and all dependencies as per documentation. npm run dev:start from root directory leads to Docker compose issue.
Expected behavior
Flowser instatiates.
Desktop (please complete the following information):

Linux Mint
Chrome

Log
Add any other context about the problem here.
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'dev:logs' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'predev:logs', 'dev:logs', 'postdev:logs' ]
5 info lifecycle flowser@1.0.0~predev:logs<EMAIL_ADDRESS>6 silly lifecycle flowser@1.0.0~predev:logs: no script for predev:logs, continuing
7 info lifecycle flowser@1.0.0~dev:logs<EMAIL_ADDRESS>8 verbose lifecycle flowser@1.0.0~dev:logs: unsafe-perm in lifecycle true
9 verbose lifecycle flowser@1.0.0~dev:logs: PATH: /usr/share/npm/bin/node-gyp-bin:/home/abulut/flowser/node_modules/.bin:/home/abulut/Downloads/GoLand-2021.3.4/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
10 verbose lifecycle flowser@1.0.0~dev:logs: CWD: /home/abulut/flowser
11 silly lifecycle flowser@1.0.0~dev:logs: Args: [ '-c',
11 silly lifecycle   'docker-compose --env-file .env.dev -f docker-compose.yml -f docker-compose.dev.yml logs -f' ]
12 silly lifecycle flowser@1.0.0~dev:logs: Returned: code: 1  signal: null
13 info lifecycle flowser@1.0.0~dev:logs: Failed to exec dev:logs script
14 verbose stack Error<EMAIL_ADDRESS>dev:logs: `docker-compose --env-file .env.dev -f docker-compose.yml -f docker-compose.dev.yml logs -f`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/usr/share/npm/lib/utils/lifecycle.js:232:16)
14 verbose stack     at emitTwo (events.js:126:13)
14 verbose stack     at EventEmitter.emit (events.js:214:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/share/npm/lib/utils/spawn.js:24:14)
14 verbose stack     at emitTwo (events.js:126:13)
14 verbose stack     at ChildProcess.emit (events.js:214:7)
14 verbose stack     at maybeClose (internal/child_process.js:925:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd /home/abulut/flowser
17 error Linux 5.4.0-110-generic
18 error argv "/usr/bin/node" "/usr/bin/npm" "run" "dev:logs"
19 error node v8.10.0
20 error npm  v3.5.2
21 error code ELIFECYCLE
22 error<EMAIL_ADDRESS>dev:logs: `docker-compose --env-file .env.dev -f docker-compose.yml -f docker-compose.dev.yml logs -f`
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>dev:logs script 'docker-compose --env-file .env.dev -f docker-compose.yml -f docker-compose.dev.yml logs -f'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the flowser package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     docker-compose --env-file .env.dev -f docker-compose.yml -f docker-compose.dev.yml logs -f
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs flowser
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls flowser
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

Hey @AliSMAmin, thanks for reporting this issue!
The log that you provided is an output ofnpm run dev:logs, correct ? Can you also provide the output you receive after running the npm run dev:start command itself ?
Also just a note, the prefered command for running Flowser app for non-development purpouses is npm run prod:start

Hey @bartolomej, here is the output for npm run dev:start
npm ERR! Linux 5.4.0-110-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "run" "dev:start"
npm ERR! node v8.10.0
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>dev:start: `docker-compose --env-file .env.dev -f docker-compose.yml -f docker-compose.dev.yml up -d`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>dev:start script 'docker-compose --env-file .env.dev -f docker-compose.yml -f docker-compose.dev.yml up -d'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the flowser package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     docker-compose --env-file .env.dev -f docker-compose.yml -f docker-compose.dev.yml up -d
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs flowser
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls flowser
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/abulut/flowser/npm-debug.log

npm run prod:start
><EMAIL_ADDRESS>prod:start /home/abulut/flowser
> docker-compose --env-file .env.prod -f docker-compose.yml -f docker-compose.prod.yml up -d

Define and run multi-container applications with Docker.

Usage:
  docker-compose [-f <arg>...] [options] [COMMAND] [ARGS...]
  docker-compose -h|--help

Options:
  -f, --file FILE             Specify an alternate compose file (default: docker-compose.yml)
  -p, --project-name NAME     Specify an alternate project name (default: directory name)
  --verbose                   Show more output
  --no-ansi                   Do not print ANSI control characters
  -v, --version               Print version and exit
  -H, --host HOST             Daemon socket to connect to

  --tls                       Use TLS; implied by --tlsverify
  --tlscacert CA_PATH         Trust certs signed only by this CA
  --tlscert CLIENT_CERT_PATH  Path to TLS certificate file
  --tlskey TLS_KEY_PATH       Path to TLS key file
  --tlsverify                 Use TLS and verify the remote
  --skip-hostname-check       Don't check the daemon's hostname against the name specified
                              in the client certificate (for example if your docker host
                              is an IP address)
  --project-directory PATH    Specify an alternate working directory
                              (default: the path of the Compose file)

Commands:
  build              Build or rebuild services
  bundle             Generate a Docker bundle from the Compose file
  config             Validate and view the Compose file
  create             Create services
  down               Stop and remove containers, networks, images, and volumes
  events             Receive real time events from containers
  exec               Execute a command in a running container
  help               Get help on a command
  images             List images
  kill               Kill containers
  logs               View output from containers
  pause              Pause services
  port               Print the public port for a port binding
  ps                 List containers
  pull               Pull service images
  push               Push service images
  restart            Restart services
  rm                 Remove stopped containers
  run                Run a one-off command
  scale              Set number of containers for a service
  start              Start services
  stop               Stop services
  top                Display the running processes
  unpause            Unpause services
  up                 Create and start containers
  version            Show the Docker-Compose version information

npm ERR! Linux 5.4.0-110-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "run" "prod:start"
npm ERR! node v8.10.0
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prod:start: `docker-compose --env-file .env.prod -f docker-compose.yml -f docker-compose.prod.yml up -d`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prod:start script 'docker-compose --env-file .env.prod -f docker-compose.yml -f docker-compose.prod.yml up -d'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the flowser package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     docker-compose --env-file .env.prod -f docker-compose.yml -f docker-compose.prod.yml up -d
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs flowser
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls flowser
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/abulut/flowser/npm-debug.log

Hey @AliSMAmin! Sorry for not responding earlier, but we've been very busy with our upcomming release of flowser desktop app.
This change should also fix the issue that you had here, so maybe follow us on Twitter for live updates: https://twitter.com/onflowser


chore: add python runtime tests

Description
Added runtime tests for python

Related Issue
Fixes #1745

@jonaslagoni , can you review this PR

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 remained the same at 92.364%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5869

Relevant Lines:
6193

💛  - Coveralls

@jonaslagoni , thank you for the reviews, added new changes

@AkhilJ321 have you had time to take a look at the problem above?

@AkhilJ321 have you had time to take a look at the problem above?

yes, tried debugging it in execCommand code also, guess its some issue with the way Python tests give output.
will try to get a proper solution for this soon.

It also slightly looks like that there is an exception thrown that the test ignores (based on the CI logs)

@AkhilJ321 have you giving up on the effort here?

@AkhilJ321 have you giving up on the effort here?

Sorry for not reaching out to you.Earlier when I made changes, and then fetched the latest results from the repository. From then I wasn't able to run the tests command

Tried resolving this issue but nothing helped.

After manually running your test command, you should be able to get the exit code from the command using echo $? to check whether it is a problem i.e. that it returns 1 when tests are successful.

It returns 0 on successful execution.
But python tests also return some information even on successful execution which is coming in stderr. so I made allowStdError =true.
So now this thing is resolved.

Awesome @AkhilJ321 :v:

@all-contributors please add @AkhilJ321  for code, test


Sphere with stereo image and position of GVRSceneObject

Hi! I have a question regarding relationships between stereoscopic environment and SDK objects.
To be precise, I have a sphere with texture which is rendered using shader UnlitVerticalStereo. It works just fine. Problem appears when I try to add object, which should be bound to something in texture - in my case it is GVRVideoSceneObject. I want video object be associated with TV screen in texture. Image for left and right eye is different, hence video object is located in different positions for each eye.
Is there any way to render same object with different position for every eye?

Issue was resolved by setting correct distance between eyes (as on rendered image) in configuration file (interpupillaryDistance).

@adiliqbl Can you please open a new issue and add a bit more detail? Like snippet of code, a screenshot.. Thanks.