R-CoprManager for RHEL 8?

Hi, The last step sudo dnf install R-CoprManager doesn't work on RHEL 8. Is there an rpm for R-CoprManager that I could download and use for a compatible install on RHEL 8? Thanks

Thanks, I had discovered rspm in the meanwhile and it helped solve my particular challenge of installing ResistanceGA. As RHEL 8 doesn’t have a texlike-grffile package, I had to download the ResistanceGA  package from github, change the image file names to contain only a single “.” immediately preceding the file type and render the corresponding naming consistent in the ResistanceGA.Rmd file, then perform a devtools::install.local, all simply to circumnavigate the final error (of many others with Libgdal and Libxceres) of LaTex not recognizing the x.y.z.pdf file format.
Thanks again for your help and advice.
Cheers
Fra: Iñaki Ucar @.>
Dato: torsdag, 25. mai 2023 kl. 18:23
Til: Enchufa2/cran2copr @.>
Kopi: Rob Wilson @.>, Author @.>
Emne: Re: [Enchufa2/cran2copr] R-CoprManager for RHEL 8? (Issue #33)
To be more specific, it's not that this particular step fails, it's that there's no RHEL chroot available, so
$ podman run --rm -it centos:stream8
$ dnf -y install 'dnf-command(copr)'
$ dnf -y copr enable iucar/cran
$ dnf -y install R-CRAN-car
Failed to set locale, defaulting to C.UTF-8
Last metadata expiration check: 0:00:34 ago on Thu May 25 16:17:11 2023.
No match for argument: R-CRAN-car
Error: Unable to find a match: R-CRAN-car
there's no repo available. I suggest that you take a look at the rspmhttps://github.com/Enchufa2/rspm project, which was specifically made with RHELs and derivatives in mind. Or, maybe even better yet, you could install the toolbox package in RHEL, create a Fedora toolbox and use this project instead.
—
Reply to this email directly, view it on GitHubhttps://github.com/Enchufa2/cran2copr/issues/33#issuecomment-1563183984, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABHPFJKP2JPW34DOUHUVVZLXH6BO3ANCNFSM6AAAAAAYNKMQOA.
You are receiving this because you authored the thread.Message ID: @.***>


super-productivity: 8.0.7 -> 8.0.10

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/super-productivity/versions.
meta.description for super-productivity is: To Do List / Time Tracker with Jira Integration
meta.homepage for super-productivity is: https://super-productivity.com
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 8.0.9 with grep in /nix/store/8hf2x21fwp4ygbfx11jbcdhn1795qk96-super-productivity-8.0.9
found 8.0.9 in filename of file in /nix/store/8hf2x21fwp4ygbfx11jbcdhn1795qk96-super-productivity-8.0.9

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

super-productivity

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8hf2x21fwp4ygbfx11jbcdhn1795qk96-super-productivity-8.0.9 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A super-productivity https://github.com/r-ryantm/nixpkgs/archive/4df5b699cfe759afee16a3207421d54cc94c5db3.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/4df5b699cfe759afee16a3207421d54cc94c5db3#super-productivity

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8hf2x21fwp4ygbfx11jbcdhn1795qk96-super-productivity-8.0.9
ls -la /nix/store/8hf2x21fwp4ygbfx11jbcdhn1795qk96-super-productivity-8.0.9/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

super-productivity

Maintainer pings
cc @offlinehacker for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/johannesjo/super-productivity/releases.
meta.description for super-productivity is: To Do List / Time Tracker with Jira Integration
meta.homepage for super-productivity is: https://super-productivity.com
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 8.0.10 with grep in /nix/store/mxpvhzsi0gxg4gjr01hdxjkadh4b9dgn-super-productivity-8.0.10
found 8.0.10 in filename of file in /nix/store/mxpvhzsi0gxg4gjr01hdxjkadh4b9dgn-super-productivity-8.0.10

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

super-productivity

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mxpvhzsi0gxg4gjr01hdxjkadh4b9dgn-super-productivity-8.0.10 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A super-productivity https://github.com/r-ryantm/nixpkgs/archive/d42810fb29ed0ff3d54c6357bb69fe6cd613ffe4.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/d42810fb29ed0ff3d54c6357bb69fe6cd613ffe4#super-productivity

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mxpvhzsi0gxg4gjr01hdxjkadh4b9dgn-super-productivity-8.0.10
ls -la /nix/store/mxpvhzsi0gxg4gjr01hdxjkadh4b9dgn-super-productivity-8.0.10/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

super-productivity

Maintainer pings
cc @offlinehacker for testing.


Rewrite synology camera by intruducing Api and SurveillanceStation …

…classes to get cameras, motion settings, enable/disable motion detection, etc ...

Synology camera now shows correct state based on is_recording and is_streaming flag. Also it now supports enable / disable motion detection and show the correct motion detection status
Newly added Api and SurveillanceStation classes will be moved to a lib but it's here just for review

Description:
This is to rewrite Synology camera component so that Synology APIs are hidden from HA device. I've also added more features to this component:

show correct camera state based on is_recording/is_streaming flag
show correct motion detection status in device attribute
added support to enable / disable motion detection
periodically polls from Synology APIs to get latest camera states

My plan is to move the newly added classes (e.g. Api, Camera, MotionSetting, SurveillanceStation, ...) to a lib. I included the new classes in this PR so it can be reviewed first before I move them to lib.
Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Just some general advice on commit messages and PR names:

The first line of the commit message is the header and should be within 50 characters. Don't end it with a period. Write the header in imperative mode: "Add new feature X". Don't start all commit messages with a dash.
Separate the header from the body with a blank line.
The body of the commit message should be within 72 characters. The body you right as you want. Markdown is nice.
Github will automatically use the header of your commit message as the name of the PR, if you only submit one commit when creating the PR. If multiple commits are present at the time the branch name will be used instead.
Don't start the PR name with a dash. Write the name in imperative mode like the commit message header.

Synology API related codes are moved to https://github.com/snjoetw/py-synology
I've added py-synology as the requirement for this component


[FEATURES] DataLoad e2e test case (alluxioruntime)

What feature you'd like to add:
DataLoad e2e test case base on AlluxioRuntime

/assign @allenhaozi


Question: Can you enable specific days (disabling all others)?

Something like:
$('.datepicker').datepicker({
    enableDates: [ moment("4/2/2014"), new Date(2014, 4 - 1, 3), "4/4/2014 00:53" ]
})

Answer provided, closing issue


Problems with glow layer once parsed from a serialized scene

Bugs

Bug repro on playground:
Expected result: the glow layer is parsed and no error happen while loading the scene
Current result: the scene looks loaded correctly but an error happens in the console only if a glow layer is added to the source scene being serialized.

With this new playground, you can also see that the glow layer is parsed because it is working in the scene: https://www.babylonjs-playground.com/#558RAP#8 but the error still happens in the console.


Centralise more locks

Investigating https://github.com/square/okhttp/issues/8388 - trying to ensure we have a central place to reason about our locks.

The idea is with a central place of inlined locking primitives, I can experiment like
https://github.com/square/okhttp/blob/44dc78f53ee188268f9e8a2a57c9f2537be9b7a9/okhttp/src/main/kotlin/okhttp3/internal/connection/Locks.kt
In ways we will never land, but without a lot of refactoring to do so.


Updating OSA SHA to 12.0.12 causes upgrading nova_console to fail

What version (commit) do you encounter this issue on?
master
What type of issue is this (bug, feature, documentation, regression)?
bug
What is the expected behavior?
The task 'Get package from git' in 'playbooks/roles/os_nova/tasks/nova_console_spice_install.yml' should update the spice-html5 repo to the version specified in 'playbooks/defaults/repo_packages/openstack_other.yml'.
What is actually happening?
Updating the OSA SHA to 12.0.12 causes this task to fail, an extract of the error message returned by Ansible is " {'msg': 'Failed to checkout 54cc41299bea8cd681ed0262735e0fd821cd774a', 'failed': True, 'attempts': 5}".
How can we reproduce this issue?
Deploy r11.1.7 then checkout master, change the OSA SHA to 12.0.12 and perform an upgrade.
How can we verify your issue is addressed?
Run a successful upgrade where the SHA for the Spice console software is different for the two versions.
If this is a large issue, what can be done immediately to alleviate the issue while working on a longer-term solution?
I have not tested this but I suspect 'git pull' on the master branch of the spice-html5 repo (/var/www/repo/openstackgit/spice-html5) on the repo server, prior to an upgrade, would resolve the issue.
What is your evaluation on the importance of this issue, and why?
Hugh, this is preventing the project from updating to the latest OSA liberty release.
What branches / milestones do you believe this issue should target?
The list below is what is currently supported for backports
Remove branches (lines) you do not wish to target.

[x] Master
[x] liberty-12.2
[ ] liberty-12.1

rpc-repo was fixed
The issue was that building the upper-reqs was removed from the repo-build role.  We pinned the version of that role on the rpc-repo box and now we are fixed (after kicking off a job).

I'm not sure why updating the Kilo repo is required to make sure Liberty has the correct version available however the immediate issue is resolved so closing this issue.


Issue #11: Shuttle Bus custom path

#11:

When selecting shuttle bus as the mode of transportation, a custom path is drawn from SGW to Loyola campus. Once the polygon is fixed for Loyola campus, we can make it so that it works in vice versa direction.

Closing this PR.
The work related to this PR has been officially moved to the PR #51
😄


function strings.new_builder is private'

table.new_table and time.new_timer are same
I guess xxx.new_xxx is treated as private

The offending code is found here: vlib/v/checker/checker.v at line 1924. I'm not sure what criteria on the if statement made it go to that path

Closed. Should be fixed on the latest version of VLS.


The \overline character doesn't stretch in FF3.6 in NativeMML mode

The overline character (U+203E) is not stretchy in FF3.6 (though it is in FF4 and 5).  It would be possible for MathJax to use U+00AF instead, which stretches in all versions of FF.

http://devel.mathjax.org/testing/testsuite/LaTeXToMathML/above-below/accents-1.html


⚠ ClamAV has degraded performance

In 801bf6c, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 595 ms

Resolved: ClamAV performance has improved in 043edeb.


Initialization of coo matrix with non-float arguments yields float index error

When initiating a sparse coordinate matrix with 3 uint64 arrays (with the 3rd instantiation as defined here), the coo_matrix call fails with a numpy.float64 indexing error. The issue does not happen for uint32 and below.
I've pinned this down to some potentially unexpected behavior (I might need to escalate this to numpy? not sure) in coo.py, specifically where the M and N are calculated: https://github.com/scipy/scipy/blob/master/scipy/sparse/coo.py#L148
>>> s = np.ones(200).astype(np.uint32)
>>> np.max(s)
1
>>> np.max(s) + 1
2
>>> s = np.ones(200).astype(np.uint64)
>>> np.max(s)
1
>>> np.max(s) + 1
'2.0'

The way arithmetic operations are done on a max(<uint64>) appear to cast the return value as not only a float, but a float within a string.
Reproducing code example:
>>> import scipy.sparse as sp
>>> import numpy as np
>>> a = np.ones(200).astype(np.uint64)
>>> b = np.ones(200).astype(np.uint64)
>>> obj = np.ones(len(a), dtype=np.uint64)
>>> sp.coo_matrix((obj, (a, b)))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/aether/programs/anaconda3/envs/cp3testnp14-3/lib/python2.7/site-packages/scipy/sparse/coo.py", line 150, in __init__
    self._shape = check_shape((M, N))
  File "/home/aether/programs/anaconda3/envs/cp3testnp14-3/lib/python2.7/site-packages/scipy/sparse/sputils.py", line 281, in check_shape
    new_shape = tuple(operator.index(arg) for arg in args)
  File "/home/aether/programs/anaconda3/envs/cp3testnp14-3/lib/python2.7/site-packages/scipy/sparse/sputils.py", line 281, in <genexpr>
    new_shape = tuple(operator.index(arg) for arg in args)
TypeError: 'numpy.float64' object cannot be interpreted as an index

Error message:
TypeError: 'numpy.float64' object cannot be interpreted as an index

Scipy/Numpy/Python version information:
('1.1.0', '1.14.3', sys.version_info(major=2, minor=7, micro=14, releaselevel='final', serial=0))

What would you suggest changing about the shape check?

The following code passes on the current main branch (macOS):

        a = np.ones(200).astype(np.uint64)
        b = np.ones(200).astype(np.uint64)
        obj = np.ones(len(a), dtype=np.uint64)
        coo_matrix((obj, (a, b)))

@rgommers should we close this?

This is indeed all fixed. The second part of the issue description now gives a float (2.0) rather than a string with that value:
>>> s = np.ones(200).astype(np.uint64)
>>> np.max(s)
1
>>> np.max(s) + 1
2.0

Closing. Thanks for the detailed report @AetherUnbound, and for looking into it @pv and @v0dro.


Orbit seems to be incorrect

Screenshot taken today, local time in Romania.

Can you provide more information on what looks wrong?

I would expect the orbit trace to be continous.

A satellites orbit doesn't come back to the same point each turn. If more points where drawn it would look more like this:
https://upload.wikimedia.org/wikipedia/commons/a/aa/ISS_orbits_04132013.jpg
The gab is normal.


Alter .addEmbed to accept array as second argument

Alter .addEmbed to accept array as second argument, and add appropriate tests. After that, just a few JSHint changes.

I wonder if this ever going to be merged?

thanks !!


alasql bin file - alacon

I was of the impression that alacon would be a binary file to be executed. I find only .js files in bin/ and console/ folders (its not  totally clear to me that the difference is). I see no installation information in wiki about how to proceed. So I have a feeling one needs Node to run AlaSQL from the commandline in the moment.
If that is true I have an idea for future emprovements:

Check if AlaSQL runs correctly with http://duktape.org/ (200kb javascript engine written in c)
(If it does) wrap duktape and alasql in a bin executable of alasql.js

I suggest Go as wrapper as it compiles to mac, freebsd, linux and windows (both 386 and 64bit version for all) with one command.
(if we use Go we can use www.github.com/mitchellh/cli or www.github.com/tcnksm/cli-init/ to implement console )

alacon is a small file in bin folder. It requires alasql.js and passes own parameters to it.

If you install alasql globally:
    npm install -g alasql

it will install alacon to command line.

ducktape: not sure... let's try!

I thought to merge alacon and alaserver into one utility and create something like REST interface.

That is really awesome. Did not know that installing globally would give you the commandline interface. do you call the command alacon or alasql in the commandline?
If it works lets just skip the wrapping thing and focus on node...
Idea: call alacon with parameters will start the http server - so one cool but 2 functions ?
Im not sure REST interface is the best solution when we dont know anything about the data.

Ok. I totally get it now.
Question: when I write alacon purely I get this instruction
alacon - Alasql command-line utility (version 0.1.9)
Usage:
node alacon "sql-statement" [ param0 ]... - run SQL statement
node alacon -f file.sql [ param0 ]...     - run SQL from file
Samples:
node alacon 'select 2+2'
node alacon 'select count(*) from txt()' <city.txt
node alacon 'select * into xlsx("city.xlsx") from txt("city.txt")'
matmac:alasqltest mrw$ alacon
alacon - Alasql command-line utility (version 0.1.9)
Usage:
node alacon "sql-statement" [ param0 ]... - run SQL statement
node alacon -f file.sql [ param0 ]...     - run SQL from file
Samples:
node alacon 'select 2+2'
node alacon 'select count(*) from txt()' <city.txt
node alacon 'select * into xlsx("city.xlsx") from txt("city.txt")'
All the examples have node i front - but as its installed globally its not needed. Should we remove node from the examples as its more ment to be used with global install?
Question 2 - how some you ended up with the name alacon for "Alasql command-line utility" It makes sense to call it alacom (or just alasql) - but cant figure the connection to the
'n'
it states (version 0.1.9) - we must remember to update

Q1: We need to remove node from documentation.
Q2: What if we call this utility alasql? We can modify alasql.js to check if the word alasql is in process.argv[1]?
Numbers: ... I will write templater to put proper number in all places.
PS. Sorry, I am inactive in this week, hope I will have more time on the next week.

No problem. We all contribute when we can...

Must say that to me it makes more sense that when you globally install AlaSQL from npm - then you can call > alasql 'SELECT 3+4' afterwards.

Added to the next release. From the next version this should work:
    > alasql 'SELECT 2+3'

sweeeeet!


Handling updates in background

Is there a way to register handlers and then loop forever while processing them?
I tried this naive way of doing so:
  while client.alive?
  end

However this pegs the CPU at 100%.
Here's something I've tried instead:
diff --git a/lib/tdlib/client.rb b/lib/tdlib/client.rb
index 54356a9..3d8279f 100644
--- a/lib/tdlib/client.rb
+++ b/lib/tdlib/client.rb
@@ -49,10 +49,14 @@ class TD::Client
       end
     end

-    @update_manager.run
+    @thread = @update_manager.run
     ready
   end

+  def wait
+    @thread.join if @thread
+  end
+
   # Sends asynchronous request to the TDLib client and returns Promise object
   # @see TD::ClientMethods List of available queries as methods
   # @see https://github.com/ruby-concurrency/concurrent-ruby/blob/master/docs-source/promises.in.md

This assigns the thread returned by UpdateManager#run to an instance variable so that it can be joined in the Client#wait method.
Then I create some signal handlers to call Client#dispose on interrupt (which causes the thread started by UpdateManager to return), and wait on the client:
diff --git a/README.md b/README.md
index 5e1ba88..b3a162c 100644
--- a/README.md
+++ b/README.md
@@ -75,7 +75,7 @@ begin
               nil
             end
   end
-
+
   client.connect

   loop do
@@ -99,6 +99,25 @@ begin
     sleep 0.1
   end

+  client.on(TD::Types::Update) do |update|
+      puts 'Got update:'
+      puts update
+    end
+
+    Signal.trap("INT") {
+      Thread.start do
+        client.dispose
+      end
+    }
+
+    Signal.trap("TERM") {
+      Thread.start do
+        client.dispose
+      end
+    }
+
+    client.wait
+
 ensure
   client.dispose
 end

This processes updates continuously without spinning.

Would this work for you?
while client.alive?
  sleep 1
end

sleep will put the current running thread to sleep and schedule the execution of another thread.
But I agree that we should think about implementing the built-in way of doing this. Joining UpdateManager thread is a good idea, but I will think a bit more about the public API.

Cool, that works.
Did a simple comparison between the three methods:
Modified Client:
$ time timeout 5 bundle exec ruby example.rb

real	0m5.020s
user	0m0.496s
sys	0m0.211s

While loop without sleep:
$ time timeout 5 bundle exec ruby example.rb

real	0m5.017s
user	0m4.720s
sys	0m0.182s

While loop with sleep 1:
$ time timeout 5 bundle exec ruby example.rb

real	0m5.025s
user	0m0.454s
sys	0m0.175s

The while loop without sleep spends almost all of its time in user mode, while both joining the UpdateManager thread and a while loop with sleep 1 perform similarly.


OWASP ZAP Show Rule Applied

Problem
At the moment it is not possible to see the rule OWASP ZAP is currently testing the page with.
Solution
Log what rule OWASP ZAP is using currently to scan the page (URL). For example:
scanning: my.page.example.org/
applying: 6_path_traversal
applying: 40018_sql_injection
…

In addition, one could log the time it takes to apply each rule.

First have a look, if there is a way using the API and have a look at: https://github.com/zaproxy/zaproxy/issues


Remove duende from the core identity docs

While Duende does use Identity to manage users that is unrelated to explaining is at it's core.
We already have an external link to the Dueude identity server, this doc shouldn't mention it when explaining what identity is.

cc @blowdart @HaoK


⚠ Bofrost.de has degraded performance

In d8e0abe, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1946 ms

Resolved: Bofrost.de performance has improved in dcb4d66 after 6 minutes.


feat(error handling): add an error event

Do you want to request a feature or report a bug?
It would be good to have an error event triggered by instantsearch.js when an API/network error occurs.
What is the current behavior?
Right now there's no (official) way to react to any error form Algolia's side
What is the expected behavior?
Having the capability to register a handler, something like search.on('error', (err) => { ... })

Would it be ok if we just forward the error even from the helper?

I'm not sure we'd need more actually!


Adds VLM Training support to SFTTrainer + VSFT script

draft for now to test the updated SFTTrainer in H4

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


v4 EnablePullRequestAutoMergeInput MERGE should be in backticks

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/graphql/reference/input-objects#enablepullrequestautomergeinput
What part(s) of the article would you like to see updated?
'MERGE' should probably be MERGE.
Additional information
(This occurs twice on this page, but it's the only content of this form on this page.)

@jsoref Thanks for opening this issue. We notified internal teams, we cant promise when it gets fixed.


fix: icon should center align vertical

Description
Icon no center alignment when it's size larger, because the line height of icon's TextSpan is not 1.
Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (Please read [Handling breaking changes]). Replace this with a link to the e-mail where you asked for input on this proposed change.
[x] No, this is not a breaking change.

@googlebot I signed it!

@Hixie This patch so too simple, so no test cases.

This patch so too simple, so no test cases.

This will still need a test. The test should fail if we don't set this (it's not clear to me that we should set a Height here).

@unordered Could you provide a before/after screenshot or test to explain what this fixes exactly, or link a issue that does so?
It is unclear to me as well as to how this change visually impacts the result. In most cases, setting height: 1 will cause the final height of the icon to be slightly shorter, which can impact the alignment.

@GaryQian Maybe my patch is wrong, this issue is related to the font, the material icon does not have this problem, but Cupertino icons and my custom icons has.

This issue is related to the font, i closed it.


netopeer2 with new libnetconf2 API

Initial changes for netopeer2 in order to use new libnetconf2 API.
Some of the most notable changes include:

removal of configuration callbacks, it's handled by ln2
removal of some redundant command line opts
removal of some np2's YANG modules, they are loaded via ln2's schema dir
the SSH and TLS options have been merged into one, that is SSH_TLS

Figured there is no need for the files netconf_server.c and netconf_server.h if there's only one function definition (the libnetconf2 callback) in them, so removed them.


CircleCI fails during Chrome install

So many questions:

why am I installing browsers in an image with browsers?
can this test just work with the existing browser? should we switch to chromium?
what's this error and why now? did something change?

#!/bin/bash -eo pipefail
sudo apt-get update
sudo apt-get install python-pip tcpdump

# Have to update firefox, default is ESR.
sudo pip install --upgrade pip
sudo pip install mozdownload mozinstall
mozdownload --version latest --destination firefox.tar.bz2
mozinstall firefox.tar.bz2
sudo cp -R firefox/* /opt/firefox/

# Latest chrome is already installed in the default container.
# curl -L -o google-chrome.deb https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
# sudo dpkg -i google-chrome.deb
# sudo sed -i 's|HERE/chrome\"|HERE/chrome\" --disable-setuid-sandbox|g' /opt/google/chrome/google-chrome
# rm google-chrome.deb
Ign http://http.us.debian.org jessie-backports InRelease

Ign http://http.us.debian.org jessie-backports Release.gpg

Ign http://http.us.debian.org jessie-backports Release

Err http://http.us.debian.org jessie-backports/main Sources
  404  Not Found [IP: <IP_ADDRESS> 80]

Err http://http.us.debian.org jessie-backports/main amd64 Packages
  404  Not Found [IP: <IP_ADDRESS> 80]

Get:1 http://security.debian.org jessie/updates InRelease [44.9 kB]

Ign http://deb.debian.org jessie InRelease

Ign http://deb.debian.org jessie-updates InRelease

100% [Waiting for headers] [Waiting for headers]Get:2 http://security.debian.org jessie/updates/main amd64 Packages [822 kB]

Hit http://deb.debian.org jessie Release.gpg

Ign http://deb.debian.org jessie-updates Release.gpg

Hit http://deb.debian.org jessie Release

Ign http://deb.debian.org jessie-updates Release

Get:3 http://deb.debian.org jessie/main amd64 Packages [9098 kB]

9% [3 Packages 12.1 kB/9098 kB 0%] [Waiting for headers]Err http://deb.debian.org jessie-updates/main amd64 Packages

Err http://deb.debian.org jessie-updates/main amd64 Packages

Err http://deb.debian.org jessie-updates/main amd64 Packages

Err http://deb.debian.org jessie-updates/main amd64 Packages

Err http://deb.debian.org jessie-updates/main amd64 Packages
  404  Not Found

100% [3 Packages 9098 kB]Fetched 9965 kB in 1s (6687 kB/s)
W: Failed to fetch http://http.us.debian.org/debian/dists/jessie-backports/main/source/Sources  404  Not Found [IP: <IP_ADDRESS> 80]

W: Failed to fetch http://http.us.debian.org/debian/dists/jessie-backports/main/binary-amd64/Packages  404  Not Found [IP: <IP_ADDRESS> 80]

W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages  404  Not Found

E: Some index files failed to download. They have been ignored, or old ones used instead.
Exited with code 100

After investigation, we are doing a sudo apt-get update to install firefox. This isn't needed since we are using an image with browsers. Removing it appears to work.

The 404s are because Debian Jessie was achieved and some repositories were removed. See this thread for more details. Probably not very useful information given the solution, but just in case 😄

Neat! The internet has all the answers! Anyway, it looks like the fix is to just delete that part of the config.


Error while webscraping multiple websites

Error:  Article download() failed with 404 Client Error: Not Found for url: https://www.nytimes.com/reuters/2017/08/05/business/05reuters-britain-eu-king.html on URL https://www.nytimes.com/reuters/2017/08/05/business/05reuters-britain-eu-king.html
content = []
for i in test.url:
    article = Article(str(i))
    try:
        article.download()
        article.parse()
        article.download()
        article.html
        article.parse()
        text = article.text
        content.append(text)
    except:
        content.append('error')
    continue

Error:

Code:
content = []
for i in test.url:
article = Article(str(i))
try:
article.download()
article.parse()
article.download()
article.html
article.parse()
text = article.text
content.append(text)
except:
content.append('error')
continue

How can I use exception handling in the loop to ignore this?

First off, you don't have to download/parse the article twice. Check the documentation for the proper use.
(...)
except:
    pass

This would ignore the error and would continue the loop without handling the exception.
(...)
except yourError as e:
    content.append(e)

This would catch the error (see error msg for exact one) in a variable and append it to content. Continue is not necessary because you properly handle the exception (and would have to be properly intended anyways).


Using picked in a QuickPickItem does not pre-select item in QuickPick

VSCode Version: 1.47.2
OS Version: Mac OS 10.15 Catalina

Steps to Reproduce:

Write an extension for vscode
Include this code

const quickpick = await vscode.window.createQuickPick();
quickpick.canSelectMany = true;

const items: vscode.QuickPickItem[] = [
         { label: 'Item 1', picked: false },
         { label: 'Item 2', picked: true },
        ];

quickpick.items = items;
quickpick.show()

Item 2 does not look pre-selected during the quick pick

Does this issue occur when all extensions are disabled?: Yes

Does your example work if you use the simpler showQuickPick API and set canPickMany: true in your QuickPickOptions?
Something like this (untested):
const picks = await vscode.window.showQuickPick([{ label: 'Item 1', picked: false }, { label: 'Item 2', picked: true }], { canPickMany: true });

Thank you @gjsjohnmurray this is working.


New version: OpenMedia.4KVideoDownloaderPlus version <IP_ADDRESS>0

Pull request has been created with komac v2.0.2 :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

2024-02-02T02:14:48.8334938Z ##[error] Manifest Error: Duplicate installer entry found.

(Automated response - build 694.)

@wingetbot run

Manual Validation ended with:

Is the 64-bit version packaged with an installer that cannot run on 64-bit OSes?

@stephengillie, please rerun the pipeline.
(for future reference, do only the moderators have the permission to restart the pipeline?)

@wingetbot run

/AzurePipelines run

Hi @fancybody,

(for future reference, do only the moderators have the permission to restart the pipeline?)

Yes - but your commit should also have triggered a run. We're working through a bit of an issue currently.

/AzurePipelines run

Automatic Validation ended with:

[1BE0:1984][2024-02-08T18:52:36]w363: Could not create system restore point, error: 0x80070422. Continuing...

(Automated response - build 723.)

Manual Validation ended with:


Issue with Unavailable Methods in ent

I encountered the following issues while using ent for database operations:
Methods OnConflict, OnConflictColumns, and UpdateNewValues Are Unavailable
Despite referencing ent official documentation and examples, I am unable to find these methods in my code.
Methods Not Found in Generated Code
I attempted to verify the presence of these methods in the generated code (under the ent directory), but I could not locate them.
ent Version Issue
The version of ent I am using is v0.14.1, but the functionality seems to be unavailable in this version.
Dependency Not Updated
I tried updating ent and its related dependencies, but the issue persists.
Steps to Reproduce:
Attempt to execute an insert operation with conflict handling using the following code:
err := client.User.
Create().
SetName("Ariel").
OnConflictColumns(user.FieldName).  // Method used to handle conflict
UpdateNewValues().                  // Method used to update values
Exec(ctx)
Check the generated code files to verify if these methods are present.
Refer to the ent version release notes and documentation to understand supported features.
Expected Behavior:
The methods OnConflict, OnConflictColumns, and UpdateNewValues should be available to handle database conflicts.
These methods should be present in the ent generated client code and function as expected.
Actual Behavior:
The methods OnConflict, OnConflictColumns, and UpdateNewValues are not found in the code.
These methods are not present in the generated code files.
Version v0.14.1 of ent does not seem to support these functionalities.
Additional Context:
Ensure that ent and its related tools are up to date, and that code generation has been completed successfully.
Provided an official documentation example to confirm the usage of these methods.
Suggested Fix:
Verify whether the ent version in use supports these methods and review the documentation for the relevant version.
If these methods are not supported in the current version, consider upgrading to a version that supports these features.
Ensure that the code generation step is error-free and that the generated code files are complete.

Hi, did you specify the --feature sql/upsert feature flag? Please see the documentation. I use v.0.14.0 (there is no v0.14.1).

Thanks @krakowski for supporting @call-81192 🙏
Closing, but please feel free to join our Discord server in case you need more help with this.


Portuguese Brazil Translations

The title explains itself

Looks good! We'll leave it open for a few days to see if anyone will review it before merging.
Thanks!


feat: show progress bar on router.back() optionally

#9

I made your addition by modifying the operation of showProgressBar that I prefer to activate as a base.
That's why I didn't directly accept your commit.
You can now install version 2.1.0.
Thank you for your work.


🐞 : Adding feedback section at relevant position

:red_circle: Title :
:red_circle: Bug :
:red_circle: Changes :
Screenshots 📷

@iamrahulmahato

✅ Details to Include When Taking the Issue:
Name :
Participant Role (Specify the Open Source Program name, e.g., GSSOC, Hacktoberfest, etc.):

Happy Contributing! 🚀
Wishing you all the best on your open source journey. Enjoy! 😎

gssoc,hacktoberfest both

And also improving the ui/ux design of feddback section @iamrahulmahato

it is fixed


[Feature] Integrate Test Reporting reporter

A preliminary test of this worked out so it would be nice to integrate our @web/test-runner report directly into the framework.
https://github.com/Brightspace/test-reporting-node?tab=readme-ov-file#webtest-runner
Config used to make it work with core.
import { defaultReporter } from '@web/test-runner';
import { reporter } from 'd2l-test-reporting/reporters/web-test-runner.js';

export default {
	pattern: type => `**/test/*.${type}.js`,
	reporters: [
		defaultReporter(),
		reporter()
	]
};

Resolved by #437


Amplify never spins up Next server when using Nx monorepo

Please describe which feature you have a question about?
Deploying a Next.js 11 app with a Nx monorepo
Provide additional details
It appears that using the monorepo feature (checkbox while creating an app) in Amplify Console makes it so that it doesn't recognize there being a Next.js app inside. This results in the build running fine but it never actually spins up the next server. It seems to consider it to be a static web app now.
When trying to create an app without the monorepo feature it does recognize the Next.js app being there but it will give me errors due to it not being on the root level, which makes sense.
I was hoping you could change the framework in Amplify Console manually but there doesn't seem to be a way to do this. It currently shows "Web" as framework, rather than Next.js.
What AWS Services are you utilizing?
Amplify
AppId
d28pbmqulo3anx
Region
eu-west-1
Provide additional details e.g. code snippets
My amplify.yml currently looks like this:
version: 1
applications:
  - frontend:
      phases:
        preBuild:
          commands:
            - npm install
        build:
          commands:
            - npm run build:prod
      artifacts:
        baseDirectory: ../../dist/apps/orderpicker/.next
        files:
          - '**/*'
      cache:
        paths:
          - node_modules/**/*
    appRoot: apps/orderpicker

I have looked through the other issues in regards to Nx and monorepo's in general, but those all seem to have specific errors come up, where as for us it will build and "deploy" fine, except that it doesn't consider it a Next app, so it doesn't actually start the server.

Hi 👋🏻 @iDavidB, can you try updating the application type using https://github.com/aws-amplify/amplify-console/blob/master/FAQ.md#convert-an-ssr-app-to-ssg.
Hope that helps!

Hi @siegerts, I appreciate your help. I ran both commands, these, to be exact.
aws amplify update-app --app-id d28pbmqulo3anx --platform WEB --region eu-west-1
aws amplify update-branch --app-id d28pbmqulo3anx --branch-name main --framework 'Next.js - SSR' --region eu-west-1

While it did change the framework to Next.js - SSR, it seems to have no impact on the deployment process. I forgot to mention that it is an SSR based app, if that makes any difference?
When running it without it being a monorepo, it starts a process saying [INFO]: Starting SSR Build.. after the build process. This is what i'm trying to achieve here too.

Is it along the lines of https://github.com/aws-amplify/amplify-console/issues/1866? If possible, it'd help to see a same app structure or repo to help the team repro.

I don't think so, as that issue seems to run into a specific error, ours just builds but never runs the next steps.

Hi again, @siegerts! I created a reproduction repo, you can find it HERE. I deployed it in the same way I have with my original repo and I can confirm I have the same issue.
AppId: d3s2lbk203au2l
Region: eu-west-1
amplify.yml of this app:
version: 1
applications:
  - frontend:
      phases:
        preBuild:
          commands:
            - npm install
        build:
          commands:
            - npm run build:prod
      artifacts:
        baseDirectory: ../../dist/apps/mono-repro/.next
        files:
          - '**/*'
      cache:
        paths:
            - node_modules/**/*
    appRoot: apps/mono-repro

Let me know if you can work with this or if you need any additional info.

@iDavidB I ran into something similar earlier and I believe it has to do with framework detection. It's done by looking at the package.json in monorepo root (which there is none in your case being nx) and looking at the build commands https://docs.aws.amazon.com/amplify/latest/userguide/server-side-rendering-amplify.html#package.json-settings.
See if you can create a stub package.json with the listed build scripts in it. It might also be worthwhile to try deploying without monorepo mode

Hi @jtmthf, I linked to a reproduction repo in my previous reply. Our Nx setup does use a single package.json at the root, but you would be right to say that it probably doesn't recognize the Next commands due to there not being any on that level. However, I did change the framework to Next.js - SSR manually with the commands shown in one of my earlier replies.
The final build ends up in dist/apps/mono-repro/ where there will also be a next start command in the package.json.
I did also try to run it without monorepo mode, which made it fail due to other reasons, which were logical reasons.

Hi, are you trying to deploy a Next.js Custom Server?
Amplify does not support Next.js Custom Servers at this time.

Hi @Athena96,
No custom server. Just basic Nx with a Next app in it generated through the Nx CLI.
This reproduction repo has the exact setup we use in it except cleared of our actual code ofcourse.
https://github.com/iDavidB/mono-repro

Hi @siegerts, any updates on this? Were you able to reproduce the issue with my repo?

Hi @iDavidB, thanks for providing that repo and the build commands. I was able to reproduce the issue and get the same behaviors. I'll follow up with the team and provide an update once I get more information.
Reproduction steps:

Select New app -> Host web app
Select the GitHub repo username/mono-repro
Check monorepo box
Specify file path for the next app apps/mono-repro
Edit build settings and replace with:

version: 1
applications:
  - frontend:
      phases:
        preBuild:
          commands:
            - npm install
        build:
          commands:
            - npm run build:prod
      artifacts:
        baseDirectory: ../../dist/apps/mono-repro/.next
        files:
          - '**/*'
      cache:
        paths:
            - node_modules/**/*
    appRoot: apps/mono-repro

Click Save and then Next.
Notice the detected framework is Web and not Next.js - SSR. Deployment will succeed but the website will result in HTTP ERROR 404

Hello @iDavidB, Sorry for the inconvenience. According to https://docs.aws.amazon.com/amplify/latest/userguide/server-side-rendering-amplify.html#deploy-nextjs-app, we detect your app as a SSR by inspecting your package.json file in your monorepo app root folder (apps/mono-repro/package.json).  However, I notice that you are using Nx monorepo framework which is little a different (package.json in root folder).  Can you please follow my step to resolve this issue?

Create a package.json file inside of your app root folder & add following content :

{
    "version": "0.1.0",
    "scripts": {
      "dev": "next dev",
      "build": "next build",
      "start": "next start"
    },
    "dependencies": {
      "next": "^11.1.2"
    }
}

Create a new App and it will be detected as SSR app, Choose correct SSR App service role, Edit build settings as below:

version: 1
applications:
  - frontend:
      phases:
        build:
          commands:
            # This step will build app with Nx framework
            - cd ../../
            - npm install
            - npm run build:prod
            # This step will build/update SSR resources(S3, Cloudfront, Lambda@Edge)
            - cd apps/mono-repro
            - npm install
      artifacts:
        baseDirectory: ../../dist/apps/mono-repro/.next
        files:
          - '**/*'
      cache:
        paths:
            - node_modules/**/*
    appRoot: apps/mono-repro

Hi @victorccccc, we decided against using Amplify for our deployments in the end. Partly due to the troubles deploying but we also needed more flexibility after all. I hope this issue may help someone in the future.
Either way, thank you all for your help!


I fixed a missing closing brackets

Fixing  #![forbid(unsafe_code)] from #![forbid(unsafe_code) to #![forbid(unsafe_code)]
Apologies, I could not not unsee it

Thank you so much!


File hash check for local fs and https

Not sure if this is the place for asking questions, but I see that for network robustness, when transferring a file, the hash is checked to make sure the destination matches the source for GCS and S3. Is there a reason why this check isn't also done for local file system and https transfers?

Yes that answers my question and makes sense for local file systems. I am not sure if there is a standard that most web servers follow, so I think sounds like not checking for now is the way to go

Yea, I'm also happy to build in some special handling for important systems, but I think they need to be identified to me first.


After first install of iOS App, SignalR (Websockets, long polling) is failing

Hey,
me and my team had a bug, that each time after we freshly installed our cordova iOS App, our server connection (using SignalR, logn polling) was failing with 400 Bad Request.
Stopping, starting, reestablishing of this connection didn't help, but closing and reopening the App did.
We had a really tough time to locate this bug to this plugin. (same behaviour with cordova-plugin-wkwebview-engine). We are now using the default UIWebview and everything works fine.
Any clue why this is happening? Maybe there is some startup proble with the webserver code?
Would be great if we can use this plugin since the UIWebview is slow and buggy on it's own way.

Are you using cookies for authentication?

yes we do

There is a problem with cookies on first lunch. That's why you have this problem.

Where is the problem? In the plugin?
And is it reported or is anybody working on it?


Comments written by post author should have a special class on CommentItem

reported by @adcpm

We should be able to highlight comments written by the current article author


dll loading error (randomly)

Hi, we're randomly experiencing the following error:
Unable to load DLL 'PgCPP.DLL.9.x.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E) -    at Npgsql.BulkCopy.Native.Versions.PQ9xNativeApi.openRemoteConn(Char hostaddr, Int32 port, Char dbname, Char user, Char password)    at Enerj.CDV.Data.DataManagerBase1.InsertBulk(DataTable DT_Tabella)
at Enerj.CDV.Data.DataManager.IndicizzaDocumentInstance(List1 ListID, Int64 IDInstance)    at Enerj.CDV.ControlsService.Manager.StartProcess()
The library is used in a Windows Service and the error shows after deploy and installation, while everything works fine in Visual Studio. On the server where we deploy the service, we've installed the Visual C++ Redistributable.
We hope you can give us a hint or a solution for this problem.
Thank you.

Hi!
Okay I'll tomorrow  see

which version your PG ? 9.5 or 9.4?
Need to update from C:\Program Files\PostgreSQL\9.5 folder lib & dll's

Sorry but I don't understand.
When I download the Nuget package, a folder named lipqdll with the following structure is downloaded and what I do is to copy the whole folder structure and contents to the service deployed root folder.

Am I wrong?
What am I supposed to do exactly?

I have the same problem. My postgres instance is on linux server.

How we can get past this error?
I've tried to compile the .DLL but it gives me countless errors ...

Same issue, note im running under Net Core

Ok, looking today.End of this week I pushed a new version.

I have the exact same error. I am using PG 9.5. It all works fine for my unit test project.
I get the Unable to load DLL 'PgCPP.DLL.9.x.dll': The specified module could not be found. error for my MVC web project. Same computer, same database.
I tried adding the lipqDLL folder to the bin folder which worked for my Unit Test project. Did not work still.
I wish the error said the expected directory too so I know where to put the dlls: Unable to load DLL 'C:/Project Folder/bin/PgCPP.DLL.9.x.dll': The specified module could not be found.

Hi!
Thank you for your replying.
Last 2 week I have many works because I don't have nay time.
This week I can be looked.
Thanks & regards,
Elyor Latipov.
Mobile phone:  <+998977111770>+998(97)711-17-70 <+998977111770>
Job profile:

http://www.linkedin.com/in/levdeo/
https://github.com/elyor0529/
https://bitbucket.org/levdeo/

E-mail:

<EMAIL_ADDRESS><EMAIL_ADDRESS>
IM:

*Skype *- live:elyor
*Hangouts *- elyor.blog

On Wed, May 31, 2017 at 3:30 AM, Steven-FlexTechs<EMAIL_ADDRESS>wrote:

I have the exact same error. I am using PG 9.5. It all works fine for my
unit test project.
I get the Unable to load DLL 'PgCPP.DLL.9.x.dll': The specified module
could not be found. error for my MVC web project. Same computer, same
database.
I tried adding the lipqDLL folder to the bin folder which worked for my
Unit Test project. Did not work still.
I wish the error said the expected directory too so I know where to put
the dlls: Unable to load DLL 'C:/Project Folder/bin/PgCPP.DLL.9.x.dll':
The specified module could not be found.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/elyor0529/NpgsqlBulkCopy/issues/1#issuecomment-305027374,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEUjL-CvexTXjqQqrLgpVZ1Th9A201Hnks5r_JiJgaJpZM4IaPo1
.

Same problem here. +1

I fixed it, I will make a pull request today to merge
I also then want to go on and use costura to embedded the C++ dlls in the Net assembly

@screig waiting for it, thanks

Ok I have reworked the code base quite a bit
forked version
The C++ projects had hard-coded links to specific installed versions of Postgres. I have made all the C++ projects use relative paths.  I also went and tried to go and find the required references, namely the lib and include files for the following versions:

9.x x86
9.x x64
8.x x86
8.x x64 (this one I could not find)

I included this data in the code base (bar 8.x x64). I rebuilt the C++ projects which regenerated the missing dlls and copied them over to the C# folder.

@screig could you please point out where you did the changes?

sorry it is still uploading...

Let me check I enable now

Thank you!

Ok its in

If anybody can fix the x64 version of the postgres binaries I can add them in

thanks🤗
Thanks & regards,
Elyor Latipov.
Mobile phone:  <+998977111770>+998(97)711-17-70 <+998977111770>
Job profile:

http://www.linkedin.com/in/levdeo/
https://github.com/elyor0529/
https://bitbucket.org/levdeo/

E-mail:

<EMAIL_ADDRESS><EMAIL_ADDRESS>
IM:

*Skype *- live:elyor
*Hangouts *- elyor.blog

On Wed, May 31, 2017 at 4:39 PM, Sean<EMAIL_ADDRESS>wrote:

If anybody can fix the x64 version of the postgres binaries I can add them
in
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/elyor0529/NpgsqlBulkCopy/issues/1#issuecomment-305165050,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEUjL9tAzOGh6CmxQutsZuwXD0WgL57Nks5r_VFwgaJpZM4IaPo1
.


Ability to get Database instance from JNDI

How about this one?
It's nessesary to have an ability to share AsyncExecutor and other Database settings with plugin.

Thanks! I have created a v2.2.19 release with the fixes


added example of stanfordnlp lemmatiser for hindi sentences

Modified the lemmatisation example with stanza code, and added translations

Need to review this.


Configurable Preview Size

          Similar for me

What I mostly use this plugin for is:
go into a zip file , copy a piece of code using "preview"
I'd like to have a lot bigger preview
I'd like to have a button near "get preview",  "open temporary" in a new tab
Thanks
Originally posted by @giac-fab in https://github.com/AdamRaichu/vscode-zip-viewer/issues/101#issuecomment-2035633390

API to use for open temp: https://code.visualstudio.com/api/references/vscode-api#workspace.openTextDocument

Would be nice to add some more CSS markup to
var t = document.createElement("textarea");

Simple additions like adding class names, then bake in additional the CSS in /media/ZipEditor.css
t.className = "NewStyledTextarea";

I do like the
resize: vertical;

Would be nice to add real VSCode extension settings block for custom markup.

Would be nice to add some more CSS markup to
var t = document.createElement("textarea");

Simple additions like adding class names, then bake in additional the CSS in /media/ZipEditor.css
t.className = "NewStyledTextarea";

I do like the
resize: vertical;

Would be nice to add real VSCode extension settings block for custom markup.

https://github.com/AdamRaichu/vscode-zip-viewer/blob/b857177cead1a32b972c8442bf762c9b0bdbbc4d/media/ZipEditor.css#L20-L26
The textarea is already set to resize: vertical, but I do think that custom CSS would probably be the easiest way to implement this. I'll take a look.


Adopt the library to HTML changes of GitHub

Hey, it seems there are changes in the HTML of GitHub and the library doesn't return any trending now. It would be nice to get an updated version aligned to the changes.
What I changed to fix it on my side:

Repository containers: $('li', 'ol.repo-list') => $('article')
Title: $(repo).find('h3') => $(repo).find('h1.h3 a')
Description: $(repo).find('.py-1 > p') => $(repo).find('p')

With these changes all data are filled except the amount of forks which is not anymore available.
Care about maybe there are different layouts, so it's maybe needed to support multiple ones and the selectors are relative general and it's maybe worth to exchange them with more precise ones.

Thanks for letting me know 👏


npm install --save react-native failed

I am using Mac OS X EI Capitan
node --version && npm --version
v4.2.1
2.14.7
Every step I followed with Getting Started. when I run command: react-native init AwesomeProject
it will throw this:
npm info postinstall<EMAIL_ADDRESS>npm info preinstall<EMAIL_ADDRESS>npm info install<EMAIL_ADDRESS>into /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/yeoman-generator/node_modules/through2/node_modules/readable-stream
npm info install
npm install --save react-native failed
Then i cd to my project and run npm install
npm install
npm info it worked if it ends with ok
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm info preinstall<EMAIL_ADDRESS>npm info build /Users/Shadowlong/Works/react-native/shadowlong
npm info linkStuff<EMAIL_ADDRESS>npm info build /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native
npm info preinstall<EMAIL_ADDRESS>npm info linkStuff<EMAIL_ADDRESS>npm info install<EMAIL_ADDRESS>npm info postinstall<EMAIL_ADDRESS>npm info install<EMAIL_ADDRESS>npm info postinstall<EMAIL_ADDRESS>npm info prepublish<EMAIL_ADDRESS>npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/babel requires<EMAIL_ADDRESS>but will load
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/source-map,
npm WARN unmet dependency which is version 0.4.4
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/babel-core requires<EMAIL_ADDRESS>but will load
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/regenerator,
npm WARN unmet dependency which is version 0.8.41
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/babel-core requires<EMAIL_ADDRESS>but will load
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/source-map,
npm WARN unmet dependency which is version 0.4.4
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/regenerator/node_modules/commoner requires<EMAIL_ADDRESS>but will load
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/graceful-fs,
npm WARN unmet dependency which is version 4.1.2
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/regenerator/node_modules/defs requires<EMAIL_ADDRESS>but will load
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/yargs,
npm WARN unmet dependency which is version 3.29.0
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/connect/node_modules/body-parser/node_modules/raw-body requires<EMAIL_ADDRESS>but will load
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/connect/node_modules/body-parser/node_modules/iconv-lite,
npm WARN unmet dependency which is version 0.4.11
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/fbjs-scripts/node_modules/gulp-util/node_modules/dateformat/node_modules/meow requires<EMAIL_ADDRESS>but will load
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/fbjs-scripts/node_modules/gulp-util/node_modules/object-assign,
npm WARN unmet dependency which is version 3.0.0
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/jstransform/node_modules/commoner requires<EMAIL_ADDRESS>but will load
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/graceful-fs,
npm WARN unmet dependency which is version 4.1.2
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/yeoman-generator/node_modules/download/node_modules/caw requires<EMAIL_ADDRESS>but will load
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/yeoman-generator/node_modules/download/node_modules/object-assign,
npm WARN unmet dependency which is version 4.0.1
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/yeoman-generator/node_modules/download/node_modules/gulp-decompress/node_modules/gulp-util requires<EMAIL_ADDRESS>but will load
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/yeoman-generator/node_modules/download/node_modules/object-assign,
npm WARN unmet dependency which is version 4.0.1
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/yeoman-generator/node_modules/download/node_modules/gulp-decompress/node_modules/gulp-util requires<EMAIL_ADDRESS>but will load
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/yeoman-generator/node_modules/download/node_modules/vinyl,
npm WARN unmet dependency which is version 1.1.0
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/yeoman-generator/node_modules/github-username/node_modules/gh-got/node_modules/got requires<EMAIL_ADDRESS>but will load
npm WARN unmet dependency /Users/Shadowlong/Works/react-native/shadowlong/node_modules/react-native/node_modules/yeoman-generator/node_modules/github-username/node_modules/gh-got/node_modules/object-assign,
npm WARN unmet dependency which is version 2.1.1
npm info ok
But I can not find ios/AwesomeProject.xcodeproj and index.ios.js in my folder ...
Please help !!!!  but I can run npm start and I also can create an android app from react-native command.

I got this error too on Windows, then I wanna see more information of this error, so I set the npm loglevel to debug...
“What the F*ck!? Why loglevel makes it works!"
yes, it's works for me. :ghost:
set npm log level to debug

Please use Stack Overflow and tag your question with react-native for asking these kinds of questions: http://stackoverflow.com/questions/tagged/react-native
Many people from the community hang out on Stack Overflow and will be able to see and likely also answer your question. Using Stack Overflow for questions also helps us use Github issues to keep track of bugs that need to be fixed.

@charmingzuo thanks dude ~  It is unbelievable... But I tried your solution... It still doesn't work for me... Do you use VPN or something ? I think the problem is Fuckin' Chinese GFW...

@Shadowlong YES,the problem is Fuckin' Chinese GFW...，I use VPN and is OK.


does the lpips work on grey images?

Is this safe to use lpips for gray images? The code does not work for 1 channel images. The hack would be to use 3 identical channels yet I am not sure what would be the effect within the end-to-end calibrated solution on color images.

I didn't test specifically on grayscale images, but it should still give some notion of distance.

thank you for the update

Facing the same issue myself. Need to use LPIPS (averaged over the number of frames) as a metric of Perceptual Similarity for the KTH Action Video Dataset (which is grayscale). Is replicating the single channels to 3 identical channels an acceptable way to obtain a similarity measure? Does there exist a better alternative?

The most proper (but perhaps time-consuming) thing would be to retrain AlexNet to do ImageNet classification on grayscale images. This would be a 1-line change to this codebase (add a line in the data loader to force images to be grayscale). Then do a linear calibration steps with our perceptual judgments from the BAPPS dataset.
Replicating to 3 identical channels is a reasonable alternative.


HTML formatting is a mess

VSCode Version: Code 1.9.0 (27240e71ef390bf2d66307e677c2a333cebf75af, 2017-02-02T08:31:00.827Z)
OS Version: Windows_NT ia32 6.3.9600
Extensions:

Extension
Author
Version

Steps to Reproduce:

Open the attached HTML file in VS Code.
Format the file using keyboard shortcut <SHIFT>+<ALT>+<F>.
Look at the JavaScript code inside the html file ...

settings.json.zip

I believe this is a duplicate of  #19813
A fix is checked into master and we plan on releasing a 1.9.1 recovery build with the fix as well


[WIP/RFC] A simple logit-style discrete choice model

Names, directories, style violations and more are very much up for critique. (it's referenced as DARK or dark in some places, but that should be changed to match the agent type's name once that is settled).
I created this tiny example of solving Rust's (1987) model of capital replacement. I did so because it's the baby version / precursor on the discrete side of things for stuff like G2EGM, DCEGM, and whatever models out there use extreme value type I taste shocks to either smooth out the problem or to get non-degenerate policies for maximum likelihood estimation purposes.
I'm attempting to use the HARK features such as distance_criteria etc, but please tell me more places where I can use the features HARK has to offer.
As it stands, it's quite bare. It's just solving the model. If @llorracc / @mnwhite / others agree that such a model should be here, it would make sense to expand with simulation of data and estimation (will be very straight forward to do).
The model is very simple, but that has the added value that the example will be quite easy to follow for new-comers to Econ-ARK. This is why I am requesting suggestions above for incorporating HARK features where possible/advantageous.
As an added bonus, this made me realize that there were some bugs in the discreteUpperEnvelope function that is also in the G2EGM PR (#200), so if this PR is shot down, we'll at least have that :)
Todo

[ ] add doc strings
[ ] add coments
[ ] add simulate method
[ ] add estimate method
[ ] small description of the model, assumptions, etc... it's all in Rust (1987)

Tried the Jupytext plugin to Jupyter as suggested by Chris. It is super easy to set up, and quite nice to work with in practice. So far I've not run into any annoyances. Certainly, it's better than adding .ipynb files to the repo.

I'm going to archive this. We can do such a model at a later point, but all relevant code that carries actual functionality has been further developed elsewhere.
In the future, I will re-implement this specific model with the discrete choice solver being written.


feat: update eslint and add rules

update eslint packages to latest version
separate prettier from eslint (best practice: formatter and linter should be separated for performance)
add rules to prevent unused imports and variables
migrate existing code to be aligned with new rules

Note: in scripts/database.ts a lot of rules are ignored because it's actually pretty difficult to strictly-type it. In future we should consider rewriting it in a smarter way.
Also closes #112 with 317170c10da98f205b116b59733334f0d790c37f

note: forced pushed from c6084767b92fbb2d732520dbd0c58a97345c9bf6 to 4b752f4655581664691b2f40d05dbf9f303828cf for wrong commit message

I think that all the review comments have been addressed, so we can proceed to merge.
@toto04 @toto04 all right?

@lorenzocorallo I haven't been able to test this locally yet, that's why the review is not approved yet. Sorry :/


Doesn't compile with mingw32 gcc on windows with -std=c99

On windows, when using gcc with the ming32 toolchain, it doesn't compile:
make
[  6%] Built target flatccrt
[  7%] Building C object src/compiler/CMakeFiles/flatcc.dir/__/__/external/hash/cmetrohash64.c.obj
[  8%] Building C object src/compiler/CMakeFiles/flatcc.dir/__/__/external/hash/str_set.c.obj
[  9%] Building C object src/compiler/CMakeFiles/flatcc.dir/__/__/external/hash/ptr_set.c.obj
[ 10%] Building C object src/compiler/CMakeFiles/flatcc.dir/hash_tables/symbol_table.c.obj
In file included from D:\Projects\flatcc\src\compiler\hash_tables\symbol_table.c:2:0:
D:/Projects/flatcc/src/compiler/symbols.h:156:6: error: ISO C99 doesn't support unnamed structs/unions [-Werror=pedantic]
     };
      ^
cc1.exe: all warnings being treated as errors
make[2]: *** [src/compiler/CMakeFiles/flatcc.dir/hash_tables/symbol_table.c.obj] Erreur 1
make[1]: *** [src/compiler/CMakeFiles/flatcc.dir/all] Erreur 2
make: *** [all] Erreur 2

Have you looked at:
https://github.com/dvidelabs/flatcc/pull/171
There is ongoing work on updating the CMake system and also add GitHub actions compilation which includes a new mingw build cross and native.
I'm not claiming this solves your issue, since I don't recall fixing any unnamed unions. Maybe the mingw build only builds the runtime target?
FlatCC attempts to avoid unnamed unions because of portability issues so this likely needs to be fixed in the symbol table.

Thanks for the link, I'll try by going on the branch of the PR to test if that fix the issue. Actually yeah, I guess the real fix should be to rewrite the structs which contain nested struct or unions ;)

You can see the mingw build here:
https://github.com/madebr/flatcc/runs/1596243638?check_suite_focus=true
Note that I had to make a few changes to flatcc before it would compile, but these are on the master branch now.

Also note the following comment in the pstdaligh.h header:
 * If stdalign.h is supported but heuristics in this file are
 * insufficient to detect this, try including <stdaligh.h> manually
 * or define HAVE_STDALIGN_H.

https://bellard.org/tcc/tcc-doc.html

The keyword __attribute__ is handled to specify variable or function attributes. The following attributes are supported:
aligned(n): align a variable or a structure field to n bytes (must be a power of two).

...

The __alignof__ keyword can be used as sizeof to get the alignment of a type or an expression.

Also note that there is a printf formatting issue that must be fixed in the CMakeList.txt file or whatever you use to build. A warning must be disabled. This has not been merged to master. You can find it in the PR discussion.

This union type fb_value_t is used everywhere, and the number of named indirections is already long when accessing values in the symbol table. So this is not an easy fix.
I suggest either removing -Wpedantic from the MinGW build, which should also fix MS formatting warnings, or use -std=gnuc99, or -std=c11, noting that c11 officially supports anonymous unions. If you do keep -Wpedantic, you need to add -Wno-pedantic-ms-format specifically for MinGW targets.
While I do want to support -Wpendantic wherever practically possible, it has also been disabled in FlatCC for the latest GCC versions because it became nearly impossible to silence an increasing flood of new warnings while maintaining portable code.
There is currently no MinGW detection in the CMakeList.txt but there is in a PR as mentioned earlier. Here -std-c11 and -Wno-pedantic-ms-format is configured for MinGW.

Alternatively you can choose o build with FLATCC_RTONLY to limit the build to the runtime library. It should not depend on anonymous unions (hopefully).

Closing as won't fix. It is not practical to change the root cause, the anonymous union in fb_value and generally flatcc does not support pedantic warnings from gcc (as they work against portability). Following next release there will be some updates to the build system, and if there is explicit interest in mingw support, please add a PR for that with suitable flags.


chore: upgrade yarn to 3.5

Test Plan
Try running yarn install

Hm, I mean we are already on yarn 3 but this sounds weird:
https://vercel.com/guides/does-vercel-support-yarn-2

I created a new lock, lets see

Ok, it passed now


Multilanguage Spanish: Reviewed all text strings

Description
I've reviewed all the text strings in Spanish and rewritten some of them to fit the width of the screen and make them properly understood.    Two python files have also been modified to add strings not contemplated by Babel

I've temporarily altered a total of 4 lines very similar to the code comment above.
As well, if you are making i18n changes to code, you can also submit the master ./babel/messages.pot if you'd like... since it has likely been done at your end during development, that way I won't mess with comments and can update all langs once merged.
I'm still writing up what I have to do as "iteration" work whenever i18n/l10n additions are made, so I'll have a better idea and be sure myself once I've been thru this process once.
If you like, feel free to add more commits, else I'll comment below here as I figure this out and make sure all is working... before merging.

I've made a commit to my clone of seedsigner-screenshots here.  I believe it to be representative of your changes, but please let me know.

I have to check some screens with the emulator, because I am seeing in your screenshots that although the translations are in the .po file, they are not being reflected on the screens

and I'm still organizing at my end.  I have not run this through my development seedsigner... because it's still "building wheel for numpy" which takes ages.  I generated the screenshots "blind", so I really have no clue what I may have broken or forgotten to do.

This seems to be mostly working for me.  Exceptions are:

green toast for "sdcard" messages are not being localized because they're in a thread that isn't locale aware... needs a fix.
I believe that "Misc Error Views" would be localized too, except that when the settings screenshots run, the locale got changed... needs a fix.
Otherwise, random translation changes that I check on my pi0 dev system are showing translated... while some phrases still over-run screen size (which is a known issue since Keith's early work -- "needs scrolling!").


Offline mode

Cherry Tree currently relies on the Internet to connect with authentication servers.
When the servers are down, however, the ENTIRE system is inaccessible. This ruins the point of a "local" media oriented system if it requires an Internet connection to run. It's just a worse Xbox One at this point. 🤷

Cherry Tree TV is based on the old Cherry Tree Console which is why it depends on the websocket connection. The connection failing and causing a softlock seems to be a bug as it could absolutely continue on normally without a connection. (e.g. when you hit Skip from the initial OOBE menu)


[BitcoinCoreProject.BitcoinCore version 0.21.1] 0x80190194 : Not found (404)

I think I should check for installer hashes while checking response codes for download URLs.

https://bitcoincore.org/bin/bitcoin-core-0.21.1/

Looks like the URL changed - the manifest has the bad one: https://github.com/microsoft/winget-pkgs/blob/master/manifests/b/BitcoinCoreProject/BitcoinCore/0.21.1/BitcoinCoreProject.BitcoinCore.installer.yaml#L8
https://bitcoin.org/bin/bitcoin-core-0.21.1/bitcoin-0.21.1-win64-setup-unsigned.exe doesn't work
https://bitcoincore.org/bin/bitcoin-core-0.21.1/bitcoin-0.21.1-win64-setup-unsigned.exe works

Looks like the URL changed - the manifest for 0.21.1 has the bad one: https://github.com/microsoft/winget-pkgs/blob/master/manifests/b/BitcoinCoreProject/BitcoinCore/0.21.1/BitcoinCoreProject.BitcoinCore.installer.yaml#L8
(old) https://bitcoin.org/bin/bitcoin-core-0.21.1/bitcoin-0.21.1-win64-setup-unsigned.exe doesn't work
(new) https://bitcoincore.org/bin/bitcoin-core-0.21.1/bitcoin-0.21.1-win64-setup-unsigned.exe works

Weeeeell you see, both of the URLs work for me, in Edge and Firefox and in Sandbox 🤷♂
Decided to replace the manifest because the installer is unsigned and a big leap in version anyways

(old) https://bitcoin.org/bin/bitcoin-core-0.21.1/bitcoin-0.21.1-win64-setup-unsigned.exe doesn't work:

(new) https://bitcoincore.org/bin/bitcoin-core-0.21.1/bitcoin-0.21.1-win64-setup-unsigned.exe works:

The new URL is using the correct domain.
https://bitcoin.org is maintained by @Cobra-Bitcoin
Neither it's an official website for Bitcoin nor associated with Bitcoin Core project.
https://bitcoincore.org is the website maintained by Bitcoin Core contributors and should be preferred for downloading Bitcoin Core.


Changing forcing_code to external submodule

Changes to be committed:
deleted:    forcing_code/include/aorc.h
deleted:    forcing_code/include/aorc_tools.h
deleted:    forcing_code/include/bmi_aorc.h
deleted:    forcing_code/src/aorc.c
deleted:    forcing_code/src/bmi_aorc.c
modified:   make_and_run_pass_forcings.sh
modified:   src/main_pass_forcing.c
[Short description explaining the high-level reason for the pull request]
Additions

Removals

Changes

Testing

Screenshots
Notes

Todos

Checklist

[ ] PR has an informative and human-readable title
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows project standards (link if applicable)
[ ] Passes all existing automated tests
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future todos are captured in comments
[ ] Visually tested in supported browsers and devices (see checklist below :point_down:)
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
[ ] Reviewers requested with the Reviewers tool :arrow_right:

Testing checklist
Target Environment support

[ ] Windows
[ ] Linux
[ ] Browser

Accessibility

[ ] Keyboard friendly
[ ] Screen reader friendly

Other

[ ] Is useable without CSS
[ ] Is useable without JS
[ ] Flexible from small to large screens
[ ] No linting errors or warnings
[ ] JavaScript tests are passing

@WanruWu-NOAA I don't see the /extern directory here, nor an updated .gitmodules. Maybe you didn't push all of your commits. Can you also give your PRs and commits more illustrative titles and messages? This will allow us to better track changes over time. Also, please edit your top-level comment with the necessary info in the noted locations. Thanks!

Thanks for the review, Keith. I will close this one and start a new PR.


Add route name to config

Route name is now customizable in config/airlock.php for easier testing.

No need to customize this very often IMO.


GH-34138: [C++][Parquet] Fix parsing stats from min_value/max_value

Rationale for this change
The code below does not read from stats.min_value/max_value at all.
// Extracts encoded statistics from V1 and V2 data page headers
template <typename H>
EncodedStatistics ExtractStatsFromHeader(const H& header) {
  EncodedStatistics page_statistics;
  if (!header.__isset.statistics) {
    return page_statistics;
  }
  const format::Statistics& stats = header.statistics;
  if (stats.__isset.max) {
    page_statistics.set_max(stats.max);
  }
  if (stats.__isset.min) {
    page_statistics.set_min(stats.min);
  }
  if (stats.__isset.null_count) {
    page_statistics.set_null_count(stats.null_count);
  }
  if (stats.__isset.distinct_count) {
    page_statistics.set_distinct_count(stats.distinct_count);
  }
  return page_statistics;
}

What changes are included in this PR?
Do similar thing from parquet-mr to check and read min_value/max_value from thrift stats.
Are these changes tested?
Some test cases fail after the fix. Fixed them to make sure it is covered.
Are there any user-facing changes?
No.

Closes: #14870
Closes: #34138

@pitrou @wjones127 @westonpace Could you please take a look?

Does this mean the following (testing my understanding)?
If min is set but max is not set then we should ignore both min and max

Does this mean the following (testing my understanding)?
If min is set but max is not set then we should ignore both min and max

Yes, it does mean we will. Do you foresee that as an issue? It sounds like Java implementation takes the same approach.

Does this mean the following (testing my understanding)?
If min is set but max is not set then we should ignore both min and max

When only one of min and max exists, it usually happens when a binary value has an extreme length or a floating value has NaN. In this case, the stats provide little value and make it tricker to use.

This looks good. @wgtmac before we merge, could you create a new issue for this bug fix? Also, if you could create issues for the TODOs as well, that would be appreciated.

I have created a new issue for this PR and updated the title.
A separate issue has been created for the TODO items: https://github.com/apache/arrow/issues/34139
Thanks for the review! @wjones127

Gentle ping @wjones127 @pitrou
Once this gets merged, I will rebase https://github.com/apache/arrow/pull/34107 which is blocked by it.

CC @fatemehp

Yes, it does mean we will. Do you foresee that as an issue? It sounds like Java implementation takes the same approach.

In datasets, for row group statistics, we recently added a check that was roughly...
if (is_nan(min) && is_nan(max)) {
  // Ignore statistics
} else if (is_nan(min)) {
  // Assume x <= max
} else if(is_nan(max)) {
  // Assume x >= min
} else {
  // Assume min <= x <= max
}

In other words, if one of min or max is NaN then we still use the other side of the equality.  I think my primary concern is to validate that is a safe assumption.  In other words, I want to make sure we aren't using garbage data in our handling of row groups.

@westonpace that makes sense.

When only one of min and max exists, it usually happens when a binary value has an extreme length or a floating value has NaN. In this case, the stats provide little value and make it tricker to use.

It seems like we do have handling for these two cases. See Weston's message for NaN handling and max_statistics_size on WriterProperties. Based on that, I'd actually prefer we keep the ability to parse just the min or max if only one is available.

It seems like we do have handling for these two cases.

Just for clarity, the PR I linked (and my thoughts) were about how we currently handle row group statistics.  I'm not sure if the rules are identical for page statistics.  I mainly wanted to make sure my understanding of the row group statistics wasn't invalid.

It seems like we do have handling for these two cases.

Just for clarity, the PR I linked (and my thoughts) were about how we currently handle row group statistics. I'm not sure if the rules are identical for page statistics. I mainly wanted to make sure my understanding of the row group statistics wasn't invalid.

IIUC, row group statistics are aggregated from page statistics so they should share the same rules. The parquet thrift message definition does allow only one side of min or max exist:
/**
 * Statistics per row group and per page
 * All fields are optional.
 */
struct Statistics {
   /**
    * DEPRECATED: min and max value of the column. Use min_value and max_value.
    *
    * Values are encoded using PLAIN encoding, except that variable-length byte
    * arrays do not include a length prefix.
    *
    * These fields encode min and max values determined by signed comparison
    * only. New files should use the correct order for a column's logical type
    * and store the values in the min_value and max_value fields.
    *
    * To support older readers, these may be set when the column order is
    * signed.
    */
   1: optional binary max;
   2: optional binary min;
   /** count of null value in the column */
   3: optional i64 null_count;
   /** count of distinct values occurring */
   4: optional i64 distinct_count;
   /**
    * Min and max values for the column, determined by its ColumnOrder.
    *
    * Values are encoded using PLAIN encoding, except that variable-length byte
    * arrays do not include a length prefix.
    */
   5: optional binary max_value;
   6: optional binary min_value;
}

On the other side, the story of page index is different. The column index definition does require existence of both min and max values if it is not a null page:
/**
 * Description for ColumnIndex.
 * Each <array-field>[i] refers to the page at OffsetIndex.page_locations[i]
 */
struct ColumnIndex {
  /**
   * A list of Boolean values to determine the validity of the corresponding
   * min and max values. If true, a page contains only null values, and writers
   * have to set the corresponding entries in min_values and max_values to
   * byte[0], so that all lists have the same length. If false, the
   * corresponding entries in min_values and max_values must be valid.
   */
  1: required list<bool> null_pages

  /**
   * Two lists containing lower and upper bounds for the values of each page
   * determined by the ColumnOrder of the column. These may be the actual
   * minimum and maximum values found on a page, but can also be (more compact)
   * values that do not exist on a page. For example, instead of storing ""Blart
   * Versenwald III", a writer may set min_values[i]="B", max_values[i]="C".
   * Such more compact values must still be valid values within the column's
   * logical type. Readers must make sure that list entries are populated before
   * using them by inspecting null_pages.
   */
  2: required list<binary> min_values
  3: required list<binary> max_values

  /**
   * Stores whether both min_values and max_values are ordered and if so, in
   * which direction. This allows readers to perform binary searches in both
   * lists. Readers cannot assume that max_values[i] <= min_values[i+1], even
   * if the lists are ordered.
   */
  4: required BoundaryOrder boundary_order

  /** A list containing the number of null values for each page **/
  5: optional list<i64> null_counts
}

So I am fine with parsing only one side min or max values from page/row group statistics. @westonpace @wjones127

The CI build is failed due to a recent branch rename and will be fixed by https://github.com/apache/arrow/pull/34233

@westonpace Could you please take another pass?


[Destination] Generic HTTP API Endpoint

Name of the service: Generic HTTP Endpoint (To be able to send to Elasticsearch or any other databases and destinations)
Example from Upstash HTTP HTTP Sink Connector:

It would be great to have a generic HTTP Endpoint destination, for example to send to Elasticsearch over REST HTTP with the possibility to add authorization (username / API key) headers, body, and parameters.

Thanks for the suggestion @dijkstrajesse! I agree, this would be super useful & something for us to look into


Missing functions __OSValidateAddressSpaceRange, DisassemblePPCOpcode, OSIsAddressValid and AVMGetDRCScanMode

I've been needing a few functions which are not available in wut. Can those be added by any chance? I also ran into a problem with __OSValidateAddressSpaceRange where it wouldn't link successfully even though the name is correct:
#ifdef __cplusplus
extern "C" {
#endif
// TODO: Prepend __ but then linker error?
int (*OSValidateAddressSpaceRange)(int dummy_true, void *address, size_t size);
#ifdef __cplusplus
}
#endif

typedef uint32_t (*DisasmGetSym)(uint32_t addr, char *symbolName, uint32_t nameBufSize);

#ifdef __cplusplus
extern "C" {
#endif
bool DisassemblePPCOpcode(uint32_t *address, char *opCodeBuffer,
						  uint32_t buffer_size, DisasmGetSym disasmGetSym,
						  uint32_t disassembler_options);
#ifdef __cplusplus
}
#endif

#ifdef __cplusplus
extern "C" {
#endif
BOOL OSIsAddressValid(const void *address);
#ifdef __cplusplus
}
#endif

#ifdef __cplusplus
extern "C" {
#endif
int (*AVMGetDRCScanMode)(int);
#ifdef __cplusplus
}
#endif

@exjam
I just realized that the signature of DisassemblePPCOpcode is wrong. The return value should be bool. I can prove it by running the code and seeing how I get 0 on disassemble failure and 1 on success:
typedef void *(*DisasmGetSym_t)(uint32_t address, uint8_t *symbol_name, uint32_t buffer_size);

typedef bool (*DisassembleOpcode_t)(uint32_t *opcode, char *buffer, uint32_t buffer_size,
								DisasmGetSym_t get_symbol_function, uint32_t flags);

bool disassemble_op_code(char *current_address, char *op_code_buffer, int disassembler_output_buffer_size,
					 int disassembler_options) {
OSDynLoad_Module core_init_handle;
const auto acquire_module_error = OSDynLoad_Acquire("coreinit.rpl", &core_init_handle);
if (acquire_module_error != OS_DYNLOAD_OK) {
	DEBUG_FUNCTION_LINE("OSDynLoad_Acquire() failed: 0x%x\n", acquire_module_error);
}
void *disassemble_op_code_pointer;
const auto find_export_error = OSDynLoad_FindExport(core_init_handle, false, "DisassemblePPCOpcode", &disassemble_op_code_pointer);
if (find_export_error != OS_DYNLOAD_OK) {
	DEBUG_FUNCTION_LINE("OSDynLoad_FindExport() failed: 0x%x\n", find_export_error);
}

return reinterpret_cast<DisassembleOpcode_t>(disassemble_op_code_pointer)
		((uint32_t *) current_address,
		 op_code_buffer, disassembler_output_buffer_size,
		 reinterpret_cast<DisasmGetSym_t>(OSGetSymbolName),
		 disassembler_options);
}

Simply looking at the assembly or the decompiled code to not spot an explicit return value isn't enough.


Defunk the API

The goal of this PR is to simplify Microstates and remove concepts that make it weird in JavaScript ecosystem. These changes make Microstates more boring but this is a good thing. Here are all of the changes that this PR introduces.

Removes this() context in transitions
Removes MS.* namespace
Renames microstates factory to create and moves it to static method on Microstate class
Eliminates current as first argument in transitions

Removes this() context in transitions
this() was cool because it provided an interesting API for type shifting in transitions, unfortunately it was not welcomed by people who we respect. Our friends raised concerns about support by languages like TypeScript and typeflow. We decided to remove this() in favour of this() being a microstate for current type and value. For all intents and purposes this() and this are now equivalent because context is actually result of this().
Removes MS.* namespace
We've been asked MS.Number and not just Number. Good point we said, so there is no more namespace. We're mapping JavaScript types internal types that have transitions. It makes the API surface much smaller and more ergonomic.
Renames microstates factory to create and moves it to static method on Microstate class
We've been asked why can't I just do new Microstate. This won't work because Microstate constructor expects a tree. To the lay the foundation for the hopeful future where microstates will work like a class, we'll making the microstates factory similar to Object.create. The factory now lives on Microstate class and is appropriately called Microstate.class.
To create  microstate, the developer has to,
import Microstate from 'microstates';

Microstate.create(Number, 42);

In the future, we'll be able to create a babel plugin that will transpile something like,
import Microstate from 'microstates';

state Modal {
  isOpen = Boolean;
}

let modal = new Modal({ isOpen: true });

to something that'll be equivalent of

class Modal {
}

let modal = new Microstate.create(Modal, { isOpen: true });

Something of that nature, but likely somewhat different.
Eliminates current as first argument in transitions
Originally, we designed transitions like Redux reducers because we thought that reducers provided a good point of reference for how transitions work. As we added comparability and batched transitions, it no longer made sense. In addition, some respected friends suggested to change this because it's weird that a method that they define receives different arguments than they specified.
The first argument was not being used and it was not helpful to make these functions without context. Now that transition context is a microstate, it's very easy to make the state accessible off the this.state property.

This PR is created against the tree-structure-and-lenses branch. After that branch is merged, this PR should be changed to master before merging.

Coverage increased (+0.04%) to 96.324% when pulling bc97607e965088de781a1b77c943412e2613ee2e on simplify-api into 31f4cc0adb749d6be4dba28b36724d77e42636db on tree-structure-and-lenses.


Add the MIT license in the repo

In your deno.json you specified that your license is MIT, but you don't have a LICENSE file. Which means that technically your code is private and licensed for use by you only and no one can use it and contribute on it. You should add that.

Totally, thanks for pointing that out!


TLS with openssl (Issue #43)

Implements https://github.com/scylladb/scylla-rust-driver/issues/43
Ssl can be turned on by setting ssl_contex in SessionBuilder.
ssl_context is Option where user can set certificate path, if tls, sslv23 or any diffrent method is used or if we want to verify responses from scylla.
For our case I set method to tls, set a path to self signed certificate that I generated and decided not to verify responses.
Some functions needed to be changed into more generic version in order them to work (router, writer, reader) and splitting streams had to be used with tokio's split function that would work on both TCP and SSL streams.
Tls example works on scylla instance with ssl turned on.

[x] I have split my patch into logically separate commits.
[x] All commit messages clearly explain what they change and why.
[x] I added relevant tests for new features and bug fixes.
[x] All commits compile, pass static checks and pass test.
[x] PR description sums up the changes and reasons why they should be introduced.
[x] I added appropriate Fixes: annotations to PR description.

@psarna @piodul it is done, waiting for review

Previous certificates couldn't be verified by local CA files. I've found this guide very helpful for generating verifiable self-signed certificates and a CA file: https://gist.github.com/kyledrake/d7457a46a03d7408da31.
I've asked @havaker for sanity check if it will work on his machine.


getFile returning "invalid file_id" on local server, but works on api.telegram.org

This problem started about 1 week ago, and I can't figure out what is happening.
The exactly same botToken and file_id works fine using api.telegram.org, but gives me "invalid file_id" on my local bot server.

https://api.telegram.org/{token}/getFile { file_id: "xxxx" } --> Works fine
http://localhost/{token}/getFile { file_id: "xxxx" } --> Bad Request: invalid file_id

Ps: Literally the exactly same request, the only difference in the requests is the hostname (https://api.telegram.org/ vs http://localhost/ [or others]).
I already redeployed the server in other locations (including my localhost), but it just doesn't work anymore.
I tried with different bots, but the issue still persists.
I also found nothing other than "invalid file_id" in the verbose=4 logs.
Strangely enough, using file_ids older than one week (before the issue started) still works fine, and I can getFile on them.
Any clues what I'm missing here?

You need to update the local Bot API server to the latest version. Old Bot API servers can't use file identifiers received from newer Bot API versions.
Also, ensure that you use exactly one Bot API server. You can't use simultaneously api.telegram.org and a local Bot API server.

@levlam you were right! I updated the bot server, and getFile started working again, thanks!
But this raised me another question: How may I know when I must update the bot server, or when the "file_id" is actually invalid.
Also, about your "You can't use simultaneously api.telegram.org and a local API server" statement..

I made a lot of tests and found no issues doing it.
Updates (messages, events, etc.) arrive at both server as usual.
I'm relying on "api.telegram.org" to dispatch webhook and events, and I use my local API server just for downloading files.

Are there any risks if I keep doing this way?
In Telegram's documentation, they tell me to disconnect/logout from api.telegram.org and unsetting the webhook before moving to local server to avoid losing any updates/webhooks. However, I though that this was only to protect me against losing updates.
Anyway, thanks for your time and pacience!

How may I know when I must update the bot server

You don't need to know this, if only one Bot API server is used.

I made a lot of tests and found no issues doing it.

This proves nothing.

Updates (messages, events, etc.) arrive at both server as usual.

This is not guaranteed and there are a lot of cases for which this isn't true for any bot.

I'm relying on "api.telegram.org" to dispatch webhook and events, and I use my local API server just for downloading files.

This is not supposed to work.

I though that this was only to protect me against losing updates

This is mandated to protect the bot from losing updates in the future and to avoid a lot of other issues.


Cache prefix

If I am not mistaking this package also works with the Cache of Laravel, but it seems the Prefix isn't being used (CACHE_PREFIX)?

sorry it works correct :-)

Since v1.1.0 you can specify the Redis prefix in your connection settings.


[Feature Request]: Use SVG WordPress logo

Is your feature request related to a problem? Please describe.
PNG icons can look blurry. To prevent this, you include 5 different PNG resolutions of the logo twice (for Chrome and Firefox separately). If you add a Safari extension, it will be 15 logo files.
Describe the desired solution
Use the SVG version of the WordPress logo instead.
Describe the alternatives that you have considered
Keep things as-is.
Additional context
Please find the logo here: https://upload.wikimedia.org/wikipedia/commons/0/09/Wordpress-Logo.svg. According to https://commons.wikimedia.org/wiki/File:Wordpress-Logo.svg, it is from https://wordpress.org/about/logos/.

To prevent this, you include 5 different PNG resolutions of the logo twice (for Chrome and Firefox separately)

Actually, those are included as they are required in the extension manifest, see https://developer.chrome.com/docs/extensions/reference/manifest/icons. Those don't support SVGs.
For the content injection, only 1 file (wp-logo.png) is used. Seems reasonable to use an svg for that though :)