not working through tramp

Hello,
I am mostly using emacs with remote file I access through tramp
\plinkx:puttySessionName:remote/path/to/file
For some reason, copilot works fine on local files, but not on remote ones.
Any suggestions?
Here is my .emacs init file in case that helps
(custom-set-variables
 ;; custom-set-variables was added by Custom.
 ;; If you edit it by hand, you could mess it up, so be careful.
 ;; Your init file should contain only one such instance.
 ;; If there is more than one, they won't work right.
 '(custom-enabled-themes '(wheatgrass))
 '(package-selected-packages '(ess use-package)))
(custom-set-faces
 ;; custom-set-faces was added by Custom.
 ;; If you edit it by hand, you could mess it up, so be careful.
 ;; Your init file should contain only one such instance.
 ;; If there is more than one, they won't work right.
 )

;;(require 'tramp)
;;(setq tramp-default-method "plink")

(require 'package)
(add-to-list 'package-archives '("melpa" . "https://melpa.org/packages/"))
;; Copilot dependencies
(require 'dash)
(require 's)
(require 'editorconfig)

;; Load Copilot
(add-to-list 'load-path "C:\\Users\\jsp67\\copilot.el")
(require 'copilot)
;; Enable completion
(add-hook 'prog-mode-hook 'copilot-mode)
;; Set completion acceptation
(defun my/copilot-tab ()
  (interactive)
  (or (copilot-accept-completion)
      (indent-for-tab-command)))
(with-eval-after-load 'copilot
  (define-key copilot-mode-map (kbd "<tab>") #'my/copilot-tab))
;; Set completion cycling
(global-set-key (kbd "C-.") 'copilot-next-completion)
(global-set-key (kbd "C-,") 'copilot-previous-completion)
(global-set-key (kbd "C-'") 'copilot-complete)
(global-set-key (kbd "C-;") 'copilot-clear-overlay)

Thanks for the great work and fore the help!
Sébastien

Set copilot-log-max to nil and take a look at buffer *copilot events*.
Copilot on remote ssh files (through tramp) works for me.


How to read key/value from disk

Initially my wrapper (using variable length structs) had code similar to this:
do {
  status = _faster.Read(...);
  if (status == Status.PENDING)
    _faster.CompletePending(true);
} while (status == Status.PENDING);

However once I flushed (FlushAndEvict(true) and restarted app) I was getting infinite loop as Read(...) was always returning Status.PENDING. After investigation I found that ReadCompletionCallback is being invoked in this case.
My question - is this the intended way to read value:
status = _faster.Read(.., ref output);
if (status == Status.PENDING)
{
  _faster.CompletePending(true);
  return RetrieveValueFromReadCompletionCallback(...); // return value from ReadCompletionCallback
}
return output;

If status is PENDING then (at some point) call CompletePending(...) and retrieve/use the value provided in ReadCompletionCallback, otherwise (status != PENDING) simply return/use output value.

Correct, reads can either return PENDING or not. If PENDING, you can call CompletePending, and the system will return the value via the ReadCompletionCallback, which allows you to populate the "output" variable.
If your "output" were a class object, then the write performed into output by the callback would be available in the main thread as well (after CompletePending is over).

Got it, thanks.


Add createDirectory function

Hi, this basically just exposes the createDirectory method from DirectoryFile.

I may not have done the README permalink correctly...


NET Core SDK Installer and Visual Studio Build tasks conflict with each other

Type: Bug
Task Name: Visual Studio Build
Environment

Server - Azure Pipelines
Agent: Private
OS: Windows 10 1803
Agent Version: 2.150.3

Issue Description
We have a pipeline that currently uses the .NET Core SDK Installer task to install SDK version "2.1.503" which corresponds to runtime version 2.1.7. this installs as expected.
Later in the pipeline the Visual Studio Build task is used to build a solution. The solution has both .Net framework and .Net Core projects. This task will fail as visual studio cant detect the version of .Net core that was task installed earlier in the pipeline. Visual studio will only find the version of .Net Core that was manually installed on the machine, in this case 2.1.9 and the following error is displayed
error : NETSDK1061: The project was restored using Microsoft.NETCore.App version 2.1.7, but with current settings, version 2.1.9 would be used instead. To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish. Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore. For more information, see https://aka.ms/dotnet-runtime-patch-selection.
I dont think this would be an issue if the dotnet build task was used but i expected the visual studio build task could also be used with the sln file.
The project is a service fabric application.

Thank you for describing the entire scenario. The 2.1.9 version is probably installed in global namespace and is taking precedence over the version installed via .Net Core SDK installer task. You can read about how multi-level lookup works within .NET here.
Can you uncheck the option "Perform Multi Level Lookup" for .Net Core SDK Installer task for version 1.* or 2.*  and try, this would ensure the version specified by the task is used.

Thanks for the response. I didn't realise there was 2 newer preview versions of the task. What you explained will be correct regarding the global and agent namespaces.
I changed our images to include multiple versions of the dotnet core SDK in the global namespace so it will take me a few days to prep for testing this alongside my day job. I will report back once tested

Hi @andyfisher100 Did you get a chance to test this out?

I did, it appeared to fix the issue, thanks!
How come both versions 1 and 2 of the task re both in preview? And when will they be out of preview?

We will soon roll these versions out of the preview.

Closing this. Feel free to reopen or open a new issue in case of you need any further help.

Closing this. Feel free to reopen or open a new issue in case of you need any further help.


Fix two issues in Usage.md

path to main.swift was wrong
tools-version was missing from Package.swift snippet

@swift-ci please smoke test

@swift-ci please smoke test


Link to the new meeting minutes doc

@scovetta I refer to the readme as one of the sources of up to date info on this group. I saw that the old meeting doc was retired a few weeks ago, so I am updating the links to the new meeting minutes doc.


B 17910 h&al sc creates or modifies a shipment int

Agility B-17910
Summary
I have verified the items in the H&AL are correctly shown, and have added the downstream action of the closeout office added to the H&AL, as that is part of the flow for editing/creating a move for the SM.
Verification Steps for the Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Have the Agility acceptance criteria been met for this change?

Verification Steps for Reviewers
(Playwright test for the SM creating a move and the SC getting to the H&AL page not included)
These are to be checked by a reviewer.

[ ] Has the branch been pulled in and checked out?
[ ] Have the BL acceptance criteria been met for this change?
[ ] Was the CircleCI build successful?
[ ] Has the code been reviewed from a standards and best practices point of view?

Setup to Run the Code

Instructions for starting the MilMove application
Instructions for running tests

How to test

Access the
Login as a service member
Create a ppm
Log in as SC
Navigate to the move that was newly created
Edit details of the move
Observe the changes populate properly in the audit history tab
Create a new PPM for the service member
Observe the changes populate in the audit history tab

Frontend

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, Edge).
[ ] There are no new console errors in the browser devtools.
[ ] There are no new console errors in the test output.
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.
[ ] This change meets the standards for Section 508 compliance.

Backend

[ ] Code follows the guidelines for Logging.
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Database
The history fetcher sql file has changed
https://github.com/transcom/mymove/blob/2d9d1bbeb70cdb73a8283892c5265953b539e329/pkg/assets/sql_scripts/move_history_fetcher.sql
move_logs AS (
  SELECT
    audit_history.*,
    jsonb_agg(jsonb_strip_nulls(
      jsonb_build_object(
        'closeout_office_name',
        (SELECT transportation_offices.name FROM transportation_offices WHERE transportation_offices.id = uuid(c.closeout_office_id))
      ))
    )::TEXT AS context,
    NULL AS context_id
  FROM
    audit_history
  JOIN move ON audit_history.object_id = move.id
  JOIN jsonb_to_record(audit_history.changed_data) as c(closeout_office_id TEXT) on TRUE
  WHERE audit_history.table_name = 'moves' group by audit_history.id
),

Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys.
[ ] Have been communicated to #g-database.
[ ] Secure migrations have been tested following the instructions in our docs.

Screenshots

Warnings

:warning:

Files located in legacy directories (src/shared or src/scenes) have
been edited. Are you sure you don’t want to also relocate them to the new file structure?
View the frontend file org ADR for more information

  Generated by :no_entry_sign: dangerJS against 2f09cddde04e28d6eb020618d6f2ba7ef4ab7961


Don't install systemd by default

Most users don't run systemd as their init system inside a container. So it's unnecessary to bloat the base images with all of systemd's machinations (anybody can zypper in ... if they want).

Unfortunately we have to do that for openSUSE 13.2 and 42.1 because some systems tools (like ps) are dynamically linked against libsystemd, which is shipped inside of the systemd package. That is a major pita that has been solved by tumbleweed and SLE12 SP1 by splitting the systemd packages in two parts (one being libsystemd).
$ cat /etc/os-release
NAME="openSUSE Leap"
VERSION="42.1"
VERSION_ID="42.1"
PRETTY_NAME="openSUSE Leap 42.1 (x86_64)"
ID=opensuse
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:opensuse:42.1"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://opensuse.org/"
ID_LIKE="suse"
$ ldd `which ps`
	linux-vdso.so.1 (0x00007fffebdbc000)
	libprocps.so.3 => /usr/lib64/libprocps.so.3 (0x00007f8a72b95000)
	libsystemd.so.0 => /usr/lib64/libsystemd.so.0 (0x00007f8a7296b000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007f8a72766000)
	libc.so.6 => /lib64/libc.so.6 (0x00007f8a723be000)
	liblzma.so.5 => /usr/lib64/liblzma.so.5 (0x00007f8a72198000)
	libgcrypt.so.20 => /usr/lib64/libgcrypt.so.20 (0x00007f8a71eb1000)
	librt.so.1 => /lib64/librt.so.1 (0x00007f8a71ca9000)
	libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f8a71a92000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f8a71874000)
	/lib64/ld-linux-x86-64.so.2 (0x00005650d8c44000)
	libgpg-error.so.0 => /usr/lib64/libgpg-error.so.0 (0x00007f8a7166f000)
$ rpm -qf /usr/lib64/libsystemd.so.0
systemd-210-86.1.x86_64

<insert rant about libsystemd and why lib[your init system] is a bad idea for making libraries>
But seriously, can we bring this up with the systemd maintainers? Seems like something that we should fix.

This has already been fixed inside of tumbleweed and sle12 sp2. We cannot do this change right now inside of 42.1, things are going to be better with the next release of leap


add sampson distance error measure

@paroj, thank you for the contribution! functionality-wise the code is great, but it's not that efficient because of the excessive use of heavy-weight cv::Mat to process just a pair of points. Probably, this function should either be made batch, to process multiple pair of points, or use Vec & Matx internally to speedup things. what do you think?

updated to use matx

sorry for delay :+1:


FixedWindowRoller: rotate log files in a separate thread

Compression of large files during log rotation may take several seconds. At this time, all threads writing logs are blocked, which can lead to undesirable delays.
The problem is resolved when the rotation is executed in a separate thread. Library users can enable new behavior using feature async_rotation.

Sorry for the delay in answering.
I rebased the branch.

@yakov-bakhmatov  Thanks!

@yakov-bakhmatov  also, if you're interested, I'd love to add that code that showed the issue as a bench test. Would you be interested in submitting another pr? Or do you mind if I lift that code?


Added imageGaleries

Commit Message Guidelines
Header
Blank Line
Body
Blank Line
Footer

The header should look like:
<type>(<scope>): <subject>

The body should have any necessary detailed info about the commit:
An example, references as to where this idea came from, etc.

The footer should have all the issues tagged:
Fixes #123, Fixes #456

So a commit should look like:
feat(users): Add new Yahoo authentication

Yahoo authentication idea proposed by @codydaig
Example implementation in file.js

Fixes #82

Types:

feat - Features, Enhancements, and overall Improvements
fix - Fixes, Bugs, HotFixs, etc...
doc - Changes to the Documentation and doesn't actually touch any code.

Scope:

The scope should be where the change took place.
Examples: users, core, config, articles

Subject:

The subject line should be clear and concise as to what is being accomplished in the commit.

General Rules:

No Line in the Commit message can be longer than 80 characters.

Reference: Angular Conventions

@ashokachu12 Can you fill in the commit guidelines above and explain why this is needed/wanted, what it bring to the table, etc.... Thanks!!

This seems like an interesting idea. One of the biggest hurdles that I faced with my MEANJS app, was the management of uploaded data (i.e. image, pdf, documents, etc).
It would be nice to have a foundation for a solution that allows users to upload files to add, edit, and share with others users. I realize that's a tall order, and isn't the aim of this PR. However, it seems to be touching up on the same concept/pattern.
@ashokachu12 I agree with Cody, that we need more details on the relevance of this feature, and the intention. I see there isn't a way for a User to upload these images that the gallery uses. Seems like there might be some other missing parts as well; e.g. the hard-coded list of image-names.

@ashokachu12 Any update on the above asks?

Closing this. @ashokachu12 Feel free to reopen if you want to discuss this more.


New transforms, CiceroEdit for migration, Tests revisions and Bug fixes

Changes

Fixes async bug in markdown-transform
Adds --via option to CLI, allowing to specify intermediate steps in the transform
Slate DOM changes:

clause node now include the elementType field
clause node only have a src field when available
variable nodes can also have an identifiedBy field

Changes to the transform:

revert changes to commonmark format with wrapped variables so it is consistent with the last markdown-transform release
new ciceroedit with import to ciceromark which is based on the previous commonmark -> ciceromark transform. Kept around only for migration.
distinguishes between ciceromark and ciceromark_untyped the latter is used for ciceroedit transform.
commonmark -> ciceromark transform now only identifies clause nodes
ciceromark -> commonmark transform does not create wrap variables anymore. Remove corresponding duplicate code from markdown-template package.

Testing:

Completely revised to adjust to the new transforms. Prior tests from markdown to slate/html etc are not in the markdown-transform package.
CommonMark tests are split in separate files (for ciceromark, ciceroedit and the spec)

Coverage decreased (-6.02%) to 84.835% when pulling a09f2e55edd42351b4551b89010b29a17dd632a9 on parserv2 into 45d0552a9f99ffd6acf23b29b88674f278c750a6 on master.


No togg button on new Jira Dialog

Environment details

Operation system: Windows 10
Extension version: 1.10.7

Expected behavior
To have toogle button into the new Dialog
Actual behavior
No button
Steps to reproduce the behavior
In Jira sprint overview, when you click on a card a modal appears without the toggle button.
Additional details

screenshots or screencapture

Case /17878407579

Case/17878407579


Adds tests and modifies h5py as optional dependency

This PR:

Adds tests for np.longdouble, list and str.
Modifies h5py as optional dependency and skips relevant tests if it is not installed.

NOT ready to be merged yet.

Coverage decreased (-2.6%) to 89.119% when pulling af2bfd95b6fc0cf50afa6829dbbeb96ee0e48848 on usmanwardag:hdf5_readwrite into 5917dc792bd22697a75956ff97e286c48ee009aa on OrkoHunter:io_readwrite.

@OrkoHunter This is ready to merge now.

Cool. Btw. why are we not installing/testing h5py on travis and appveyor ?

Right. We probably should do that. Let me set it up.


Add NeurIPS 2023

👷 Deploy Preview for gladia processing.

Name
Link

🔨 Latest commit
4ddd400d06b5c4f4fc716b421a6328b7390bd414

🔍 Latest deploy log
https://app.netlify.com/sites/gladia/deploys/65764836e40548000858fcc4


Error: /app/main/resources/app.asar.unpacked/node_modules/better-sqlite3/build/Release/better_sqlite3.node: undefined symbol: _ZN2v88internal20CanHaveInternalFieldEi

Describe the bug
I did this once before but hadn't tried in a while;  it used to work fine.
Now, when doing a Test Connection during connection setup I see this error right away:

Error: /app/main/resources/app.asar.unpacked/node_modules/better-sqlite3/build/Release/better_sqlite3.node: undefined symbol: _ZN2v88internal20CanHaveInternalFieldEi

To Reproduce
Steps to reproduce the behavior:

Go to Add Connection
Click on Client | SQLite
Browse to the .dat file
See error

Expected behavior
The database should open and become available to query.
Screenshots
Enclosed.
Application (please complete the following information):

Installation source: Linux Mint Software Manager (via FlatPak)

Environment (please complete the following information):

OS name: Linux Mint
OS version: 21.2 Cinnamon
DB name: SQLite

Additional context
I tried uninstalling and re-installing the Antares FlatPak.  I further used Flatsweep & Warehouse to ensure there were no leftover files before doing another re-install.  Same behavior, so I don't immediately suspect a damaged installation.
/var/lib/flatpak/app/it.fabiodistasio.AntaresSQL/x86_64/stable/4970c786432ab9c97f7ab7844f59234cbdd93f3a4215088d0ca9e1a7992b3d5f/files/main/resources/app.asar.unpacked/node_modules/better-sqlite3/build/Release# ll
total 1.1M
drwxr-xr-x 3 root root    5 Dec 31  1969 ./
drwxr-xr-x 5 root root    5 Dec 31  1969 ../
-rwxr-xr-x 2 root root 1.5M Dec 28 17:22 better_sqlite3.node*
drwxr-xr-x 3 root root    3 Dec 31  1969 obj/
-rwxr-xr-x 2 root root  14K Dec 28 17:22 test_extension.node*
/var/lib/flatpak/app/it.fabiodistasio.AntaresSQL/x86_64/stable/4970c786432ab9c97f7ab7844f59234cbdd93f3a4215088d0ca9e1a7992b3d5f/files/main/resources/app.asar.unpacked/node_modules/better-sqlite3/build/Release# file better_sqlite3.node
better_sqlite3.node: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=3ca8327c5e6639d2bb5977629121079a0a68e1a4, stripped
I can open the DB w/o any issues using DB Browser for SQLite.

Thank you for the report.
It is a problem with the flatpak version. This is the second release published on Flathub and unfortunately given the nature of flatpak, what you test locally is not always then what Flathub compiles and distributes...
I should be able to fix it with the next release but until then, if you can, I recommend using the AppImage or deb version, which are not affected by the flatpak-related problems.

On next ours (shoyls be 3 or 4) will be available on flatpak an update ot the same version (0.7.20) but with te fix in build process.
If you don't get the update notification please try to reinstall.

The new update DOES fix the problem.  I can access the DBs now.  Thanks!


serde aux function to get names for fields as they are serialized

from https://github.com/serde-rs/serde/issues/1110
Do you prefer a different method name?
I combined the function to get the field names from structs and enums so its easier to use.  It was possible to use the wrong method for the type for the original implementation.
I will try address any comments.

There are some unsuccessful pipelines. I suggest you run cargo clippy and cargo fmt locally and that will help you solve everything easily.

Sure, edits by maintainer is checked for this PR.
I didn't understand what you meant by the removing example colon so I left that to you.
Feel free to make any more edits if you need to thanks :)

Sure, edits by maintainer is checked for this PR.
I didn't understand what you meant by the removing example colon so I left that to you, I saw it in other places?
Feel free to make any more edits if you need to thanks :)

Yes, so in "cool" markdown, the colons after headers aren't welcomed, just a style. For example, here you won't see : after features or Optional features headers.

I'll merge once the checks are done. Thanks again!


Lock Vscode

A button that allows to lock vscode while I take a cup of coffee or when I communicate not to type code not desired

I don't think it's practical for vscode to guarantee any type of security - you will have to lock your screen at the OS level for this


[Event Request] codeunit 7320 "Whse. Undo Quantity" - OnFindPostedWhseShptLine

In codeunit 7320 "Whse. Undo Quantity" please add the following event:
    procedure FindPostedWhseShptLine(var PostedWhseShptLine: Record "Posted Whse. Shipment Line"; UndoType: Integer; UndoID: Code[20]; SourceType: Integer; SourceSubtype: Integer; SourceID: Code[20]; SourceRefNo: Integer) Ok: Boolean
    var
        PostedWhseShptLine2: Record "Posted Whse. Shipment Line";
        WhseManagement: Codeunit "Whse. Management";
        // New variable
        IsHandled: Boolean;
        // New variable
    begin
        if not PostedWhseShptLine.ReadPermission then
            exit;
        with PostedWhseShptLine do begin
            Reset;
            case UndoType of
                DATABASE::"Sales Shipment Line",
              DATABASE::"Service Shipment Line":
                    SetRange("Posted Source Document", "Posted Source Document"::"Posted Shipment");
                DATABASE::"Return Shipment Line":
                    SetRange("Posted Source Document", "Posted Source Document"::"Posted Return Shipment");
                else
                    // New event
                    //exit;
                    begin
                        OnFindPostedWhseShptLine(PostedWhseShptLine, UndoType, UndoID, SourceType, SourceSubtype, SourceID, SourceRefNo, IsHandled);
                        if not IsHandled then
                            exit;
                    end;
                    // New event
            end;
            WhseManagement.SetSourceFilterForPostedWhseShptLine(PostedWhseShptLine, SourceType, SourceSubtype, SourceID, SourceRefNo, true);
            SetRange("Posted Source No.", UndoID);
            OnFindPostedWhseShptLineOnAfterSetFilters(PostedWhseShptLine);

    [IntegrationEvent(false, false)]
    local procedure OnFindPostedWhseShptLine(var PostedWhseShptLine: Record "Posted Whse. Shipment Line"; UndoType: Integer; UndoID: Code[20]; SourceType: Integer; SourceSubtype: Integer; SourceID: Code[20]; SourceRefNo: Integer; var IsHandled: Boolean)
    begin
    end;

Thank you

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Getting a toolchain with debuginfo_level

First of all, thank you for your work on rust-overlay!
the perfbook mentions https://nnethercote.github.io/perf-book/profiling.html#debug-info debuginfo_level for the rust std to include more information useful for profiling tools.
Is there any way to have it with rust-overlay ? I couldn't find anything in the reference, so just asking here.
Thank you again for providing this critical piece of software for rust and nix !

https://nnethercote.github.io/perf-book/profiling.html#debug-info debuginfo_level for the rust std to include more information useful for profiling tools.

It reads:

The most reliable way around this is to build your own version of the compiler and standard library, following these
instructions, and adding the following lines to the config.toml file:
[rust]
debuginfo-level = 1

It's a configuration to "build your own" rust. See here.
rust-overlay ships precompiled binaries from official rustup server and patch them for Nix use. We don't build rustc and std on our own, thus we are not able to change configurations for building std.


Is there any update for VS2019 ?

Is there any update for VS2019 ?

he stopped using Windows, but you can build the latest commit and use it without any trouble


Support sendmmsg

The main motivation is to support DNS protocol analysis, some DNS requests are sent by sendmmsg.
Some descriptions:

For eBPF, MAX_MSG_LEN and MAX_SENDMMSG_IOVCNT are set to 4 and 7 separately due to the limitation of 4096 instructions, which may miss some data.
For kernel module,  no x86_32 support.

So what will happen if it is used on x86_32?


Memory leak in LogisticRegression

Describe the bug
Memory leak in daal4py.sklearn.linear_model._logistic_path_0_22.LogisticRegression was appeared in according tests in PR https://github.com/IntelPython/daal4py/pull/553.
CI link: https://github.com/IntelPython/daal4py/runs/2085105525
To Reproduce
Steps to reproduce the behavior:

Remove 'LogisticRegression' from BANNED_ESTIMATORS in daal4py/sklearn/test/test_memory_usage.py
Run test

Expected behavior
Absence of memory leak
Output
   AssertionError: Size of extra allocated memory is greater than 25% of input data:
     	Input data size: 816000 bytes
     	Extra allocated memory size: 7632826 bytes / 935.4 %
   assert 7632826 < (0.25 * 816000)

Environment:

OS: all
Compiler: all
Version: 2019.3, 2021.1, master branch

https://github.com/scikit-learn/scikit-learn/issues/20061

https://github.com/intel/scikit-learn-intelex/pull/654


Change SQL Server to SQLite

All excercises and the demo require SQL Server, which is problematic for people running macOS and Linux. I would suggest using SQLite since it will run everywhere.

Originally it was all based on SQLite, we had so many threading issues that we decided to switch to something more reliable. Now that SQL Server is available for Linux and can be run in a container the issues seems less relevant. Thoughts?

Hmm, we usually run integrated tests with SQLite and I don't remember threading issues to come up. May be these are already fixed? SQL Server container alone is several gigabytes. May be using a database abstraction and allow people using something like PostgreSQL?

It's the first time this has been suggested, but I can sympathise with the reasoning. I suggest that we poll for opinion on the prerequisites in some of the upcoming workshops we have and then revisit this.

I with great certainty can predict that this will be a demand very soon, as the .NET Core will spread and people will use more of containerised environments. PgSQL container is like 100Mb and SQL Server is a few gigabytes.

As soon as the upcoming support for PostgreSQL in SQL Persistence is out, transitioning everything to PostgreSQL and containers is a feasible step.


URL safe object notation dialect

Summary
Following the idea of using a JSON inspired notation for complex values in URLs (see https://github.com/Nanonid/rison ) and considering that the following characters are safe to use in URLs...
 A-Z a-z 0-9 - . _ ~ ( ) ' ! * : @ , ;

...the following modifications could be made to standard JSON to create a URL safe object notation that easily can be transcribed to JSON while providing a more user friendly surface notation:

member properties are restricted to A-Z a-z 0-9 - . _ @ but must start with a letter or @
member properties are not quoted
numbers can only be given in simple integer and floating point notation (no exponent notation)
positive numbers must not use +
string literals use single quotes '...'
string escaping works the same except the escaped "end of literal" \" becomes \'
objects and arrays use round brackets instead of square or curly; (...); () is the empty array; empty objects are omitted

The literals stay

true => true
false => false
null => null

Motivations and Goals

URL safe syntax that leans on URL encoding for special characters in string literals
keep the notation very close to JSON so users can remember and apply a few simple rules of how to convert it in their mind
allow in-place transcription to JSON; that means the notation uses the same length (or more) symbols

Example
JSON
{
  "name": "John",
  "age": 42,
  "license": false,
  "keywords": ["hello", "world"]
}

URL Object Notation
(name:'John',age:42,license:false,keywords:('hello','world'))

Array vs Object
It certainly is not ideal to parse the notation when both objects and arrays use round brackets. But since round brackets are the only URL safe type of brackets this is the most user friendly option. This means the parser potentially needs more look-ahead then JSON would require. However, since property names are not quoted but start with a letter there is only a small clash when the first letter is t, f or n. In that case this may be atrue, false, null literal or the start of a property. Only in those cases the parser needs to read-ahead and see if a , or : is found first.
The only case where array and object become indistinguishable is the empty array vs the empty object.
As empty objects are usually equivalent to "no property is defined" () should only be used for the empty array
while empty objects should simply left out.
URL Encoding
As this notation is intended to be used for complex value specified as URL parameter value the URL decoding will be applied to the entire value in one operation. This should make it obvious that the encoding equally can and should be applied to the entire value. Therefore it should also be obvious that white-space can occur like it can in JSON but that it will look ugly when looking at the URL encoded value.

See #61


Remove multiple verilog build targets generated by lua

With the new AXI interface test methodology, examples/makefile should only write out the verilog file once. Then, if we need to add stuff around it (ps7), concat this in the makefile.
Currently, metadata.lua gets clobbered, b/c we write it out multiple times!

Done


How i need initialize FirebaseApp?

How i need initialize FirebaseApp for use Firebase.auth?
Now I am getting an error: Default FirebaseApp is not initialized in this process by.iba.relocation.android. Make sure to call FirebaseApp.initializeApp(Context) first. when i'm use Firebase.auth(Firebase.app)

You need to call
import dev.gitlive.firebase.Firebase
import dev.gitlive.firebase.FirebaseOptions
import dev.gitlive.firebase.firestore.firestore
import dev.gitlive.firebase.initialize

        val app = Firebase.initialize(
            options = FirebaseOptions(
                applicationId = "",
                apiKey = "",
                databaseUrl = "",
                gaTrackingId = "",
                storageBucket = "",
                projectId = "",
                gcmSenderId = "",
                authDomain = "",
            )
        )
        val store = Firebase.firestore(app)

My android app is crashing if I initialize it like this, complaining that context is null, any idea ?

@gergirod I don't think we need to configure FirebaseOptions in the case of Android. We can just pass it a context and it should be good to go.

It would be great to have some guide. Meanwhile, what worked for me:

For android
a. Add android app using firebase console. Note, my android module has package name com.example.app and android part of shared module (I use firebase inside that module) has name com.example.app.shared. So I had to use com.example.app.shared package name when adding (which was not very intuitive).
b. Firebase suggests you to download google-services.json file, I put it inside shared module (in the same dir with shared module build.gradle.kts file).
c. After doing that, launching app was able to initialise from file. So I was able to get db reference using simple val db = Firebase.firestore
For ios:
a. Add ios app using firebase console. Note, in that one I had to use package name of ios module, not shared (com.example.app in my case)
b. As in instructions from console in xcode -> file -> add packages -> https://github.com/firebase/firebase-ios-sdk -> Choose required services from the list (for me it was only firestore)
c. In main swift code of ios module I added import FirebaseCore and FirebaseApp.configure() in func application
d. File from firebase console (GoogleService-Info.plist) put into the same folder with that main swift file (also there was Info.plist in that dir).
e. And the most undocumented step: we need to make sure xcode sees that file. In my case I had to manually add it by left click on project dir (the same we place file in) -> add files to "app" -> add GoogleService-Info.plist
After following actions a got firebase working on android and ios.

Disclaimer:
I had no idea what I was doing, just randomly applying solutions from the internet to fix errors appearing. Probably my solution is not correct, but it works. I hope in future there will be some guide for setting up firebase multiplatform.

@dimitree54 Would you be able to share your build.gradle.kts? I'm having the same issue and I suspect I'm importing the libraries incorrectly in the gradle.
I have added the  implementation("dev.gitlive:firebase-firestore:1.8.0") to commonMain dependencies. I'm unsure of how to import the google-services plugin correctly in Kotlin Gradle DSL

Hello @javierlcontreras,
Maybe you can find something useful in my abandoned project https://github.com/dimitree54/buboc_ui (also follow submodule cuboc_core, some firebase setup done there).
But I do not develop that project for some time already, so could not comment that code.

Hello @javierlcontreras,
Please add inside the plugins of  id("com.google.gms.google-services").version("4.3.14").apply(false) in the build.gradle.kts(Module :Project) and add id("com.google.gms.google-services")  in the plugins {} of build.gradle.kts(Module :androidApp).
Note: Don't forget to add google-services.json in the android app

So thanks to @dimitree54 's steps I managed to get my app initialized, and Firebase Auth and Firestore are working on both Android and IOS. I have a secondary issue now, though: I added Google One Tap Sign in, which uses the com.google.android.gms:play-services-auth library, as an Android-specific feature. It's executing the service call right, but it's getting an com.google.android.gms.common.api.ApiException: 10 exception, which is usually an indication that the app's SHA-1 fingerprint isn't set up right on Firebase/present in the google-services.json file (double-checked, it's there in both). Has anybody else encountered that/managed to get it working?
A side note I only have the google-services.json file in the shared module, when I tried adding it to the androidApp module
Execution failed for task ':androidApp:processDebugGoogleServices'.

No matching client found for package name 'com.example.app.MyApplication'

which is really weird, if anyone can tell me why it's doing that I'd appreciate it


Add keyboard chat request example

Thank you

https://github.com/2ei/tgram/assets/173957402/d589e866-ef69-4e11-9ca7-7f1933f49927

doc_2024-06-30_16-17-39.mp4

lol i didn't know that we can comment gif here..

here the best place to do everything you want /s


ERR_CONNECTION / CORS Request did not succeed

"webpack": "^4.41.5"
vue --version @vue/cli 4.1.2
Bug report

I already asked questions in vue.js forum, in stackoverflow, and in other github reports.
What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce.

https://github.com/marcoippolito/testproject

Description of the problem:
I created a brand new tiny webapp with vue cli, so without adding anything, apart from what the empty vue-cli scaffolding brings:
(base) marco@pc:~/vueMatters/testproject$ npm run serve

><EMAIL_ADDRESS>serve /home/marco/vueMatters/testproject
> vue-cli-service serve

INFO Starting development server...
98% after emitting CopyPlugin

DONE Compiled successfully in 1409ms 8:14:46 PM

And get this error message : https://drive.google.com/open?id=10GcVFmqNVGRjox3wklJtcrAkIWM3kOp8
"GET https://localhost/sockjs-node/info?t=1580228998416 net::ERR_CONNECTION_REFUSED"

Using firefox as web browser, I get this error message: https://drive.google.com/open?id=1l6USIHrbHl6kBcQtormXplOgx0J653ko
"Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at
https://localhost/sockjs-node/info?t=1580304400023. (Reason: CORS request did not succeed)."

Looking at Mozilla Developer explanation:
https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSDidNotSucceed?utm_source=devtools&utm_medium=firefox-cors-errors&utm_campaign=default
"What went wrong?

The HTTP request which makes use of CORS failed because the HTTP connection failed at
either the network or protocol level. The error is not directly related to CORS, but is a fundamental
network error of some kind.

In many cases, it is caused by a browser plugin (e.g. an ad blocker or privacy protector) blocking
the request.

Other possible causes include:

Trying to access an https resource that has an invalid certificate will cause this error.
Trying to access an http resource from a page with an https origin will also cause this error.
As of Firefox 68, https pages are not permitted to access http://localhost, although this may be
changed by Bug 1488740.
The server did not respond to the actual request (even if it responded to the Preflight request).
One scenario might be an HTTP service being developed that panicked without returning any
data.

"
In order to understand where the problem could lie, I checked various aspects:

Checked the TLS Certificates with https://www.digicert.com/help/ : and the result is:
" TLS Certificate has not been revoked.
TLS Certificate expires soon. The primary TLS Certificate expires on February 28, 2020 (30 days
remaining)
Certificate Name matches ggc.world
TLS Certificate is correctly installed "

curled the url both from within the PC-Server, and from a laptop:
-From within the PC-Server:
(base) marco@pc:~$ curl -Iki https://localhost/sockjs-node/info?t=1580397983088
HTTP/2 405
server: nginx/1.14.0 (Ubuntu)
date: Fri, 31 Jan 2020 08:19:02 GMT
allow: OPTIONS, GET
(base) marco@pc:~/vueMatters/testproject$ curl -vk https://localhost/sockjs-
node/info?t=1580397983088
  Trying ::1…
  TCP_NODELAY set
  connect to ::1 port 443 failed: Connection refused
  Trying <IP_ADDRESS>…
  TCP_NODELAY set
  Connected to localhost (<IP_ADDRESS>) port 443 (#0)
  ALPN, offering h2
  ALPN, offering http/1.1
  successfully set certificate verify locations:
  CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
  TLSv1.3 (OUT), TLS handshake, Client hello (1):
  TLSv1.3 (IN), TLS handshake, Server hello (2):
  TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
  TLSv1.3 (IN), TLS handshake, Unknown (8):
  TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
  TLSv1.3 (IN), TLS handshake, Certificate (11):
  TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
  TLSv1.3 (IN), TLS handshake, CERT verify (15):
  TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
  TLSv1.3 (IN), TLS handshake, Finished (20):
  TLSv1.3 (OUT), TLS change cipher, Client hello (1):
  TLSv1.3 (OUT), TLS Unknown, Certificate Status (22):
  TLSv1.3 (OUT), TLS handshake, Finished (20):
  SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
  ALPN, server accepted to use h2
  Server certificate:
  subject: CN=ggc.world
  start date: Nov 30 11:22:10 2019 GMT
  expire date: Feb 28 11:22:10 2020 GMT
  issuer: C=US; O=Let’s Encrypt; CN=Let’s Encrypt Authority X3
  SSL certificate verify ok.
  Using HTTP2, server supports multi-use
  Connection state changed (HTTP/2 confirmed)
  Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
  TLSv1.3 (OUT), TLS Unknown, Unknown (23):
  TLSv1.3 (OUT), TLS Unknown, Unknown (23):
  TLSv1.3 (OUT), TLS Unknown, Unknown (23):
  Using Stream ID: 1 (easy handle 0x559bc64c5580)
  TLSv1.3 (OUT), TLS Unknown, Unknown (23):

  GET /sockjs-node/info?t=1580397983088 HTTP/2
  Host: localhost
  User-Agent: curl/7.58.0
  Accept: /

  TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
  TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
  TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
  TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
  TLSv1.3 (IN), TLS Unknown, Unknown (23):
  Connection state changed (MAX_CONCURRENT_STREAMS updated)!

  TCP_NODELAY set
  Connected to ggc.world (<IP_ADDRESS>) port 443 (#0)
  ALPN, offering http/1.1
  successfully set certificate verify locations:
  CAfile: /home/marco/anaconda3/ssl/cacert.pem
  CApath: none
 TLSv1.3 (OUT), TLS handshake, Client hello (1):
  TLSv1.3 (IN), TLS handshake, Server hello (2):
  TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
  TLSv1.3 (IN), TLS handshake, Certificate (11):
  TLSv1.3 (IN), TLS handshake, CERT verify (15):
  TLSv1.3 (IN), TLS handshake, Finished (20):
  TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
  TLSv1.3 (OUT), TLS handshake, Finished (20):
  SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
  ALPN, server accepted to use http/1.1
  Server certificate:
  subject: CN=ggc.world
  start date: Nov 30 11:22:10 2019 GMT
  expire date: Feb 28 11:22:10 2020 GMT
  issuer: C=US; O=Let’s Encrypt; CN=Let’s Encrypt Authority X3
  SSL certificate verify ok.

  GET /sockjs-node/info?t=1580397983088 HTTP/1.1
  Host: ggc.world
  User-Agent: curl/7.65.2
  Accept: /

  TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
  TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
  old SSL session ID is stale, removing
  Mark bundle as not supporting multiuse
  < HTTP/1.1 200 OK
  < Server: nginx/1.14.0 (Ubuntu)
  < Date: Fri, 31 Jan 2020 14:04:11 GMT
  < Content-Type: application/json; charset=UTF-8
  < Transfer-Encoding: chunked
  < Connection: keep-alive
  < Access-Control-Allow-Origin: *
  < Vary: Origin
  < Cache-Control: no-store, no-cache, no-transform, must-revalidate, max-age=0
  < Strict-Transport-Security: max-age=31536000
  <
  Connection #0 to host ggc.world left intact
  {“websocket”:true,“origins”:[":"],“cookie_needed”:false,“entropy”:1587194190}

This is the output of the "Network" tab :
https://drive.google.com/open?id=1QJMe8FEBrEuWacHWeJ_TQegMkF0v68AY

This is the "view source" of the html page:

testproject

We're sorry but testproject doesn't work properly without JavaScript enabled. Please
  enable it to continue.

This is the result of the "localhost" word search in app.js:
https://drive.google.com/open?id=11QpJKjd4PLKNMnO7m2utCJ9PrzO8Oyji  :
  /***/ }),

  /***/ 1:

/!********************************************************************************************************************************************************************!
!*** multi (webpack)-dev-server/client?http://localhost (webpack)/hot/dev-server.js (webpack)-
dev-server/client?http://<IP_ADDRESS>:8080/sockjs-node ./src/main.js !
**************************************************************************************************************************************************************/
/! no static exports found /
// (function(module, exports, webpack_require) {
    __webpack_require__(/*! /home/marco/vueMatters/testproject/node_modules/webpack-dev-
server/client
    /index.js?http://localhost */"./node_modules/webpack-dev-server/client/index.js?http:
//localhost");
    __webpack_require__(/*! /home/marco/vueMatters/testproject/node_modules/webpack
/hot/dev-server.js
    */"./node_modules/webpack/hot/dev-server.js");
    __webpack_require__(/*! /home/marco/vueMatters/testproject/node_modules/webpack-dev-
server/client
    /index.js?http://<IP_ADDRESS>:8080/sockjs-node */"./node_modules/webpack-dev-server/client
/index.js?http:
    //<IP_ADDRESS>:8080/sockjs-node");
    module.exports = __webpack_require__(/*! ./src/main.js */"./src/main.js");
    /***/ })
    /******/ });

These are the results of the "localhost" word search in chunk-vendors.js :

https://drive.google.com/open?id=13EPYKgb7Vv4DHOTxD0jxYk_CbDDrJkMy
https://drive.google.com/open?id=1UjWDsPyT-87GF4WJhVr-UhzOFGiBW8tH
https://drive.google.com/open?id=1eq5pWm51sjCYQkIaQn5GZ6uEmrmS36Od
https://drive.google.com/open?id=19QzxljB37HH5cvJ0jffdyX97u9hlBDsV

In this GitHub repository you can find all the related files: https://github.com/marcoippolito/testproject
The sudo nano /etc/nginx/conf.d/default.conf is the following:
server {
    listen 443 ssl http2 default_server;
    server_name ggc.world;

    ssl_certificate /etc/ssl/certs/chained.pem;
    ssl_certificate_key /etc/ssl/private/domain.key;
    ssl_session_timeout 5m;
    ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3;
    ssl_ciphers EECDH+CHACHA20:EECDH+CHACHA20-

draft:EECDH+AES128:RSA+AES128:EECDH+AES256:RSA+AES256:EECDH+3DES:RSA+3DES:!

Marco

Please open issue in vue-cli

@evilebottnawi Are you 100% sure it's a problem of vue-cli? I'm going to open issue in vue-cli, but if they bounced me back here, I will definetely open it again

@evilebottnawi I reported the problem in vue-cli GitHub page: https://github.com/vuejs/vue-cli/issues/5129
Looking forward a joint effort and help

Hi @marcoippolito
It works fine on Firefox on Ubuntu:

Hi @appsparkler
I stopped nginx server, and executed npm run serve:
(base) marco@pc:~/vueMatters/testproject$ sudo systemctl stop nginx
[sudo] password for marco:
(base) marco@pc:~/vueMatters/testproject$ sudo systemctl status nginx
● nginx.service - A high performance web server and a reverse proxy server
   Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Sun 2020-02-02 09:58:36 CET; 6s ago
     Docs: man:nginx(8)
  Process: 4359 ExecStop=/sbin/start-stop-daemon --quiet --stop --retry QUIT/5 --pidfile
/run/nginx.pid (code=exited, status=0/SUCCESS)
  Process: 983 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited,
status=0/SUCCESS)
  Process: 872 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited,
status=0/SUCCESS)
 Main PID: 1001 (code=exited, status=0/SUCCESS)

Feb 02 09:18:32 pc systemd[1]: Starting A high performance web server and a reverse proxy
server...
Feb 02 09:18:33 pc systemd[1]: Started A high performance web server and a reverse proxy
server.
Feb 02 09:58:36 pc systemd[1]: Stopping A high performance web server and a reverse proxy
server...
Feb 02 09:58:36 pc systemd[1]: Stopped A high performance web server and a reverse proxy
server.
(base) marco@pc:~/vueMatters/testproject$ npm run serve

><EMAIL_ADDRESS>serve /home/marco/vueMatters/testproject
> vue-cli-service serve

 INFO  Starting development server...
98% after emitting CopyPlugin

 DONE  Compiled successfully in 986ms
9:58:54 AM

  App running at:
  - Local:   http://localhost:8080
  - Network: http://<IP_ADDRESS>:8080

  Note that the development build is not optimized.
  To create a production build, run npm run build.

But still get the error in Firefox: "Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:8080/sockjs-node/info?t=1580634450627. (Reason: CORS request did not succeed)."

And in Google Chrome the error: "GET http://localhost:8080/sockjs-node/info?t=1580634002894 net::ERR_CONNECTION_REFUSED" :

Hi @marcoippolito
Please see the screenshots from my Ubuntu.  Note that it is not Ubuntu server.  Maybe you are facing this issue due to Ubuntu Server OS.
Firefox

Chrome

@appsparkler I do not understand... might it be an issue related to the Ubuntu installed in the PC?
(base) marco@pc:~$ vue info

Environment Info:

  System:
    OS: Linux 4.15 Ubuntu 18.04.4 LTS (Bionic Beaver)
    CPU: (8) x64 Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
  Binaries:
    Node: 12.10.0 - ~/.nvm/versions/node/v12.10.0/bin/node
    Yarn: 2.0.0-rc.27 - ~/.nvm/versions/node/v12.10.0/bin/yarn
    npm: 6.13.6 - ~/.nvm/versions/node/v12.10.0/bin/npm
  Browsers:
    Chrome: Not Found
    Firefox: Not Found
  npmGlobalPackages:
    @vue/cli: 4.1.2

I checked also the add-on installed in Google Chrome:

and the installed add-on in FireFox:

So... what kind of issue might be related to the specific Ubuntu OS Server Edition installed in the PC?

Yes @marcoippolito
In the information provided; your OS is  Ubuntu 18.04.03 Server Edition.  This may be the problem.
You can install Oracle VM Virtual Machine and load an Ubuntu Desktop image.  Then clone your repository, install the node_modules and start the server (i.e npm serve or yarn serve).  If this works then the issue may be related to Ubuntu 18.04.03 Server Edition OS.

@appsparkler
I'm using Ubuntu Server Edition in my development machine because I need to use an environment as close as possible to the production environment.
To me it's not clear why a Server Edition should interfere with sockjs-node if, opening in the browser the files before the ERR_CONNECTION failures I read, when searcing for sockjs-node and use of localhost, references to webpack:

Anyway, I'm going to post an issue in Ubuntu Server Edition's platform, referring to this github's issue and your hypothesis about a bug/problem related to the Ubuntu 18.04.03 Server Edition.
And I will keep you informed about the results in other forums

@appsparkler
In the PC I installed ex-novo Ubuntu 18.04.3 Desktop and I verified that the problem disappeared.
I ran the same tiny webapp in both laptop and pc, and using localhost and the ip-address both from within the laptop/PC and from the other device (PC/laptop) gave no error. I reported everything here
https://askubuntu.com/questions/1207812/webapp-fails-with-neterr-connection-refused-with-ubuntu-18-04-4-server-edition
According to you, what kind of problems/missing parts/lacking features or whatever the Ubuntu 18.04.4 Server Edition could have compared to the Ubuntu 18.04.4 Desktop Edition?
It would be great if we could give to the Ubuntu's people some hints/suggestions and help in solving this problem.

Hi @marcoippolito ,

According to you, what kind of problems/missing parts/lacking features or whatever the Ubuntu 18.04.4 Server Edition could have compared to the Ubuntu 18.04.4 Desktop Edition?

Not sure about this.  Lets hope someone responds with a solution in the askubuntu forum.  Please update this discussion if you get any info.
Good Luck...


sz error

Version: 1.0.184
Platform: Windows x64 10.0.19042
Plugins:tabby-trzsz
Frontend: xterm-webgl
https://github.com/Eugeny/tabby/issues/5132
https://github.com/Eugeny/tabby/issues/5196
$ sz f4973ced-310a-40fd-b0ec-2faf3d4fce9b.jpg
 ZMODEM  Session started
------------------------
 Received  f4973ced-310a-40fd-b0ec-2faf3d4fce9b.jpg
 Error  PROTOCOL: Only thing after ZFIN should be “OO” (79,79), not: 27,93,48,59,117,98,117,110,116,117,64,105,110,115,116,97,110,99,101,45,50,48,50,49,48,54,48,49,45,49,48,50,54,58,32,126,7,27,91,48,49,59,51,50,109,117,98,117,110,116,117,64,105,110,115,116,97,110,99,101,45,50,48,50,49,48,54,48,49,45,49,48,50,54,27,91,48,48,109,58,27,91,48,49,59,51,52,109,126,27,91,48,48,109,36,32

trzsz plugin should use trz and tsz instead.
You can install the python version , or the go version.


Add support for firmware 3.6

This PR add support for firmware 3.6.
It is full of breaking change and will only work with firmware >= 3.6

The backend of the picture has changed, therefore the server is consuming more memory and is a bit more CPU intensive (but it remains around 20% use).
the color values have changed
the RLE is not encoding packets of 15 anymore which leads on average on a huge reduction of the amount of data transfered.

should fix #58

This is close, but still buggy


Support Power9

cc @jayfurmanek

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Added support for ISO 8601 week (Weeks start with Monday)

For use this feature just add an attribute iso-week="true".

Hi! Any updates?


Add german translation

See https://github.com/vchlum/hue-lights/discussions/29#discussioncomment-1376239

Thank you!


Empty page  each test run

Karma behaved unpredictably on cleaning the page so I've decided to enforce this via mocha configuration.
Hopefully, this is the las time when we bother about such issues.
js target is not covered but I suggest to introduce it when we'll fix js tests
May be later or we should take care of events as well, but as of know this is overkill. To make sure that there's nothing on page apart of container we need is all we would we'll need for a long time (if not for forever).

@eymar  that goes without saying - nothing will be merged till the set of pipelines we consider minimal requirement to be passed.
I know why this happens - for some reason styles in head (where they are actually supposed to be) causing this troubles in docker - if one comment out styles completely exactly this tests will fail.
I'll work on fix and let you know.


dbt-core Dockerfile does not work for dbt-spark due to PyHive

Just realized that the Docker build from the dbt-core project (https://github.com/dbt-labs/dbt-core/tree/main/docker) does not work for dbt-spark when using the PyHive version (or the default all)
docker build --tag my-dbt-spark:1.6.0 --target dbt-spark --build-arg<EMAIL_ADDRESS>--build-arg<EMAIL_ADDRESS>--build-arg dbt_spark_version=PyHive .
produces an error:
...
107.2   note: This error originates from a subprocess, and is likely not a problem with pip.
107.2   ERROR: Failed building wheel for sasl
107.2   Running setup.py clean for sasl
107.4   Building wheel for future (setup.py): started
108.0   Building wheel for future (setup.py): finished with status 'done'
108.0   Created wheel for future: filename=future-0.18.3-py3-none-any.whl size=492023 sha256=0dced4fde8484b7cf07f3ca722cbe787880c6fcb8eb27af37c82213dd20b48b8
108.0   Stored in directory: /tmp/pip-ephem-wheel-cache-pgg_8qmj/wheels/da/19/ca/9d8c44cd311a955509d7e13da3f0bea42400c469ef825b580b
108.0   Building wheel for PyHive (setup.py): started
108.3   Building wheel for PyHive (setup.py): finished with status 'done'
108.3   Created wheel for PyHive: filename=PyHive-0.6.5-py3-none-any.whl size=51554 sha256=b78987c7c11b9d3a18704d5339f9d1caf6221976e1f4c572f609fac9dd9da102
108.3   Stored in directory: /tmp/pip-ephem-wheel-cache-pgg_8qmj/wheels/cc/b2/8d/74115da1b8e1ee44544ec7870783c9fbf1127b66d296f6c4be
108.3   Building wheel for pure-sasl (setup.py): started
108.6   Building wheel for pure-sasl (setup.py): finished with status 'done'
108.6   Created wheel for pure-sasl: filename=pure_sasl-0.6.2-py3-none-any.whl size=11423 sha256=ef452afe0aeb515f2ad15f63e0df15ea5c620fef4e4f7d4413de8ebdb05b064e
108.6   Stored in directory: /tmp/pip-ephem-wheel-cache-pgg_8qmj/wheels/be/bd/15/23761a50b737a712aacac51c718906ce3563705a336d2c4ffc
108.6 Successfully built pyspark thrift dbt-spark logbook minimal-snowplow-tracker future PyHive pure-sasl
108.6 Failed to build sasl
108.6 ERROR: Could not build wheels for sasl, which is required to install pyproject.toml-based projects
------
Dockerfile:104
--------------------
 102 |         /tmp/* \
 103 |         /var/tmp/*
 104 | >>> RUN python -m pip install --no-cache-dir "git+https://github.com/dbt-labs/${dbt_spark_ref}#egg=dbt-spark[${dbt_spark_version}]"
 105 |
 106 |
--------------------
ERROR: failed to solve: process "/bin/sh -c python -m pip install --no-cache-dir \"git+https://github.com/dbt-labs/${dbt_spark_ref}#egg=dbt-spark[${dbt_spark_version}]\"" did not complete successfully: exit code: 1

It works fine if I'm using the ODBC spark version.
Update: I have the same problem locally (not in docker) if I switch from Python 3.10 to 3.11. So problem is related to https://github.com/dbt-labs/dbt-spark/issues/864
Originally posted by @gschmutz in https://github.com/dbt-labs/dbt-spark/issues/873#issuecomment-1679177998

Proposed solution is described here: https://github.com/dbt-labs/dbt-spark/issues/873#issuecomment-1795150406

Closing as a duplicate of https://github.com/dbt-labs/dbt-spark/issues/864


OWASP Android project integration

Hello,
I've integrated OWASP into my Android project.
I've used the convention plugin to integrate Owasp into all my modules.
`fun Project.configureOwasp() {
val dependencyPropsFile = file("owasp.dependency")
val dependencyProps = Properties()
if (dependencyPropsFile.exists()) {
    dependencyProps.load(FileInputStream(dependencyPropsFile))
}

val nvdApiKey = dependencyProps.getProperty("NVD_KEY")
extensions.configure<DependencyCheckExtension> {
    scanConfigurations = listOf("releaseCompileClasspath")
    failBuildOnCVSS = 11f
    failOnError = false
    suppressionFile =
<EMAIL_ADDRESS>
    analyzers.apply {
        assemblyEnabled = false
        experimentalEnabled = true
        archiveEnabled = true
        jarEnabled = true
        centralEnabled = true
        pyDistributionEnabled = false
        pyPackageEnabled = false
        rubygemsEnabled = false
        opensslEnabled = false
        nuspecEnabled = false
        assemblyEnabled = false
        cmakeEnabled = false
        autoconfEnabled = true
        composerEnabled = false
        nodeEnabled = true
    }

    formats = listOf("XML", "HTML")

    nvd.apiKey = nvdApiKey
}

}
`
However, when I call the dependencyCheckAggregate command, it generates a report per module. Is there a way to generate only one report? My problem with more reports is that SonarQube only accepts one file, not multiple ones.
Thanks!

For dependencyCheckAggregate you should configure dependencyCheck plugin in a toplevel build file. It is supposed to report on the entire module hierarchy when configured with the aggregate goal in the toplevel project. See also #3847

So this means I don't have to set OWASP for every project? Or do I still have to do it in my top-level grade file? Do you know if I need to add this?
check.dependsOn dependencyCheckAggregate

I've already added to my root gradle file the owasp plugin inside the plugin block.

Sorry, this didn't help. I've tried to add it only to the root project, but it will still run a report per module. @aikebah

@PRobi23 I'm not a gradle user myself, so I can't help you get your config right, but I do know that you need to configure the gradle plugin to run only in the root-project if you intend to run it as an aggregate plugin (invoking the dependencyCheckAggregate task) in order to obtain a single report for your multi-module project.

@aikebah  that's what I've did.
In my root gradle file I've added this
   alias(libs.plugins.owasp) apply false (inside the plugins section),
which points to
owasp = { id = "org.owasp.dependencycheck", version.ref = "owasp" }
owasp = "10.0.4"

and then I'm running the  ./gradlew dependencyCheckAggregate command. Still it generates the dependency report per module, and I don't get it why.

@PRobi23 As said: I'm not a gradler... having said that, a quick google on the alias you quote leads me to this stackoverflow https://stackoverflow.com/questions/78672954/why-is-my-build-gradle-looking-like-this-aliaslibs-plugins-com-android-applic in which it's clearly visible that you've not configured the plugin to 'run in root , but not in submodules', but instead you configured it to 'not run in root, but only in submodules'

yes you are right thanks for your help @aikebah


alpha version demo

We will have an alpha version demonstration
After finishing the alpha version, we will have more specific and better standard for further development.

https://github.com/scipp/beamlime/pull/68