[SPARK-9301] [SQL] Add collect_set aggregate function

Can one of the admins verify this patch?

@nburoojy I think when @yhuai filed the ticket, he wanted to implement this for the new aggregate interface, not the old one (since it already exists on the old one).

That makes sense. To be clear, the new interface is AlgebraicAggregate or, if a lower-level interface is needed AggregateFunction2, right?

@yhuai and @rxin I have updated the collect_list and collect_set fn's to use the new aggregate interface. Please take another look. Thanks!

@nburoojy This will work, but the performance will be pretty bad, and very prone to GC.
I think to properly fix this, we might want to rewrite the query under the hood to implement it using an operator that gives a list of items, instead of an aggregate function.

@rxin I bet you're right about the performance and gc issue. Is there a performance test suite to quantify this issue? I always hesitate to optimize prematurely :-)

rewrite the query under the hood to implement it using an operator that gives a list of items

Are you suggesting to create a List equivalent of OpenHashSetUDT? Mutating a single buffer on updateExpressions and mergeExpressions would certainly cut down on the number of Object instantiations.

This is not premature optimization. Just run collect_set on a large set and Spark JVM processes will OOM.
What I'm suggesting is to implement this not as an aggregate function, but rather an operator that does the function of collect_set (e.g. the operator can sort all the data by grouping key and set key to compute the set for each group).
Anyway - maybe it'd make sense also have the aggregate function version of this, with the caveat written correctly that this would OOM if running on large amount of data.

@rxin the OOM concern is valid, but I see it as a distinct from the performance concerns I have.
In theory, a collect_list over an ungrouped dataset with 10M nonnull rows will return a single row containing an array of 10M elements. In practice, the array of 10M elements may require more memory than heap available on a single node and the process will OOM. This is a fundamental limitation of the collect_list and collect_set interface, I think; just like the RDD functions collect and CollectByKey, we can't return bulk data through a single node. Based on this, I think the right solution (as you mentioned) is to write the caveat that the resulting arrays should be limited in size. Where should I document these functions?
The performance issue I see is that we allocate new arrays for each element in updateExpressions. This could produce bulky garbage and the resulting GC could significantly slow things down. This is the performance issue I wanted to measure before writing a ArrayListODT to reuse lists. I think this would be a good next step once the core collect_set and collect_list functionality is merged.
I'm certainly not a Spark SQL expert, so I'm not sure I fully understand your concerns or ideas for performance improvement. Could the operator-based collect_* produce the same array in a single row results as the aggregation-based collect_* functions while preventing OOM issues on the worker nodes?

@rxin What are the next steps with this?

@rxin I would really like to see this merged in as well. I agree with @nburoojy that collect_as_list and collect_as_set will always have issues if the size of one list/set gets too big, but that doesn't mean that this isn't useful. I didn't quite follow the other parts about the API refactor, but if that isn't a huge issue, it would be nice to merge something like this in soon.
If people are careful, this can be extremely useful, especially when it's impossible to write a UDAF that has a mergeValue and mergeCombiner function, or when you just want to restructure how the table is layed-out. In addition, until pyspark gets UDAFs, this will be a good substitute for most cases. Right now, to get around this in pyspark, I'm using hive's collect_list, but it's annoying because I have to register a temp table and use a SQL query instead of the dataframe API.

I agree that this could be useful in this form.
Maybe we can merge this into 1.6.0 ?

Thanks for working on this!  I would like to include this, but I'm worried about the performance.  Unfortunately, I think that in order to get something that is not n^2 we are going to have to make major changes to aggregation (and its after code freeze already).
Fortunately, we already have a hive UDF that does this in O(n).  I'd propose that we just add a wrapper so that people can find this in the functions list for DataFrames.  You can just make the function call: callUDF("collect_set", ...), etc.
If you can make a PR in the next day or two we can still include it in Spark 1.6.

Thanks for the review @marmbrus !
I've sent https://github.com/apache/spark/pull/9526 with your suggestion to alias the Hive UDAFs. And I'd like to include it in the 1.6 release.
Longer-term (beyond 1.6) I'd like to solve the core issue.
For my particular use case I would like the ability to aggregate compound types (struct and array), and it appears Hive 0.13.0 does not support this.
What kind of major changes would we have to make to support O(1) array insertion? I was thinking that a strategy like CollectHashSet uses would also work here; that is, I would implement a CompactBufferUDT (backed by CompactBuffer), and updateExpressions would append to the buffer in amortized O(1).
Would this strategy break assumptions in the new aggregation framework? Do you think this change is larger than I expect?

The problem is we are deleting the old non-memory managed aggregation codepath.  Its simpler but leave the user open to OOMs.  We would need to add some way to append to array in tungsten encoded rows or something?

@nburoojy
I have the same issues like you - aggregating compound types.
What we can do with this PR ?


replace 'github.com/chainer/pfio' with 'github.com/pfnet/pfio'

I noticed that github.com/chainer/pfio remains in several places while the repository has moved to github.com/pfnet/pfio.

Thank you for the PR! I am sorry the current master fails on the style with the latest flake8. Can you please merge into the master after #127 get merged?

Can you please merge to the latest master for #127 ?

Do you mean that merging the latest master into this PR and see the CI result?
Because I cannot merge without passing CI.
By the way, I intended to make the pull request from github.com/msakai/pfio but I realized that I made it from github.com/pfnet/pfio/ by mistake.
Sorry about that.


OS.execute doesn't run all the programs

Operating system or device - Godot version:
Godot 3.0 Alpha 1
Issue description:

Using something like this works:
OS.execute("notepad", StringArray([]), false)
OS.execute("calc", StringArray([]), false)
but something like this doesn't:
OS.execute("regedit", StringArray([]), false)
OS.execute("cmd", StringArray([]), false)
OS.execute("powershell", StringArray([]), false)
Steps to reproduce:
Link to minimal example project:

I figure out the problem, I had to run Godot using administrator rights. You can close this ticket.

I tried to run cmd.exe or powershell.exe using Godot as admin and I couldn't make it work. Regedit works fine.

So when launching Godot on MS Windows you will have a two windows pop up the command prompt and the Godot editor, so when you do OS.execute("cmd", StringArray([]), false) or OS.execute("powershell", StringArray([]), false) it creates another cmd/powershell within the currently existing command prompt:

You might have searched online for solutions.
Here is a Stack overflow question, which seems related to what you ask.
Basically, you should do something like this, in order to pass cmd.exe the /K flag, which would cause it to start up a new window.
OS.execute("cmd", StringArray(["/K"]), false)

Additionally, to start powershell, you might have to do this:
OS.execute("cmd", StringArray(["/K", "powershell"]), false)

(Note that the above code is untested, as I'm on linux)

@deltasquad451 Thanks, now I understand why I couldn't see any result on screen. I though it was a bug or a limitation on Godot. I will close this ticket. Thanks again.


Provide prebuilt releases for older versions

Hi,
at our organization we're using an older version of Sharp (specifically 0.17.3) due to using Debian in production, which has an older version of libvips.
How hard would it be to backport the prebuilt releases functionality and publish that as 0.17.4 version?

Pre-built binaries for libvips and its dependencies are downloaded by sharp at install time should any globally-installed version of libvips not be recent enough. Do these meet your needs?

But there aren't any prebuilt binaries for 0.17.3 version of sharp (for MacOS specifically). It always tries to compile sharp during yarn install.
Are you saying that there's already prebuilt binaries for older releases?

Prebuilt binaries for sharp and prebuilt binaries for libvips are independent.
Have you tried upgrading sharp to the latest version and seeing what happens?

By way of example, sharp v0.20.5 requires libvips v8.6.1+. At npm install time, if this version of sharp finds a globally-installed libvips v8.4.5, it will be ignored and sharp will download v8.6.1 instead.
You'll see all the install-time decisions relating to detection/download/compilation being logged via npmlog.

Ok, so in order for us to use in production the globally-installed libvips v8.4.5, we need to set sharp v.0.17.3 in our project.
When using sharp v.0.17.3 on local machines for development (on MacOS), yarn tries to compile sharp because there aren't any prebuilt binaries for v0.17.3. We're trying to avoid this (because of time, problems during compiling etc).
My original question was: Can we backport and provide prebuilt releases on older versions (specifically 0.17.3)?

Using a globally-installed version of libvips means sharp will always compile itself from source as shared libraries can have slightly different APIs and therefore ABIs between versions and can be in different locations. This is true even if a prebuilt sharp is available, so sadly the solution you propose won't help.

"Sharp will be built from source at install time when... a globally-installed libvips is detected"
http://sharp.pixelplumbing.com/en/stable/install/#building-from-source

Is there a specific reason you need to use the globally-installed, Debian-packaged libvips v8.4.5?


Invalid Projection CRSError

I'm trying out the sample code from the official page
osm = pyrosm.OSM(get_data('Helsinki')) drive_net = osm.get_network(network_type="driving") drive_net.plot()
and get the error
CRSError: Invalid projection: epsg:4326: (Internal Proj Error: proj_create: no database context specified)
what are the possible courses of action?

Hmm, this sounds like a problem with the pyproj library. Perhaps an installation issue.
Have you tried plotting some other data with geopandas? Does it work?

geopandas works fine with other projects, and can plot too. Can you suggest possible solutions to fix it if it's a problem with the pyproj library? Sorry if this seems like a beginner question.

Hmm, okay interesting. Have you used conda for installing the packages?
Could you provide a list of packages and their versions in your environment? Eg conda list command from terminal will provide you the list

@khelzor31415 : Any update on this one? Are you still having this issue?


fix: database patch fix to cleanup old fap_assignments and fap_reviews that are not related to any fap_proposal

Description
This PR introduces a database patch to clean up stale fap_assignments and fap_reviews that are not linked to any fap_proposal.
Motivation and Context
This change is required to maintain data integrity and avoid orphan records in fap_assignments and fap_reviews tables, which can lead to confusion and potential errors in future data operations.
Changes

The fap_assignments table is updated to set fap_proposal_id for existing records. Any records that do not have a corresponding fap_proposal are deleted.
The fap_reviews table is updated similarly, setting fap_proposal_id for existing records and deleting any records that do not have a corresponding fap_proposal.
The fap_proposal_id column in both tables is then set to NOT NULL to enforce data integrity moving forward.

How Has This Been Tested?

Fixes Jira Issue
https://jira.esss.lu.se/browse/
Depends On

Tests included/Docs Updated?

[ ] I have added tests to cover my changes.
[ ] All relevant doc has been updated

If the db patch has already run how will this be applied?


Reduce log level of Removing inventory cache

i’m looking at some Agent logs on the kubernetes integration and I see the logs flooded by this kind of info logs
time="2022-05-12T11:19:12Z" level=info msg="Removing inventory cache" agentEntityIDChanged=true component=PatchSender
entityKey="k8s:cluster:foo" offlineTime=24h0m0s

Not sure what is the meaning of it but looks like the entry is being deleted because of a TTL expiration.
I think reducing the level to debug or trace would make troubleshooting easier.

This log entry is shown when the agent has been offline for more than 24 hours or its entity ID has changed. From the log line it seems that the agent was offline more than 24 hours.
As this message will be shown every time the agent is going to send the inventory, it seems reasonable to move it to Debug.
@gsanchezgavier Thanks for reporting this!


How to remap the insert mode 'jk' to ''

Thanks your blog, but there is a question that you do not mention the insert mode how to remap in keymaps.lua. In your blog tag the 'disuse' but not talk about it, if you give me the solution about it, I would be grateful.

Thanks your blog, but there is a question that you do not mention the insert mode how to remap in keymaps.lua. In your blog tag the 'disuse' but not talk about it, if you give me the solution about it, I would be grateful.

Do you mean map jk to '' in insert mode?
Just like follow:
local keymap = vim.keymap

keymap.set("i", "jk", "<ESC>")

Thanks your blog, but there is a question that you do not mention the insert mode how to remap in keymaps.lua. In your blog tag the 'disuse' but not talk about it, if you give me the solution about it, I would be grateful.

Do you mean map jk to <ESC> in insert mode?
Just like follow:
local keymap = vim.keymap

keymap.set("i", "jk", "<ESC>")

thanks your reply! But it did not worked in my vscode😨

Thanks your blog, but there is a question that you do not mention the insert mode how to remap in keymaps.lua. In your blog tag the 'disuse' but not talk about it, if you give me the solution about it, I would be grateful.

Do you mean map jk to <ESC> in insert mode?
Just like follow:
local keymap = vim.keymap

keymap.set("i", "jk", "<ESC>")

thanks your reply! But it did not worked in my vscode😨

It depends on the vscode plugin, I use vscode.neovim. The method is as follow:

I don't know how vim plugin works.


Changes based on feedback

Changes based on feedback from @AmandaBirmingham (See https://github.com/biocore/metagenomics_pooling_notebook/pull/225)

Closing w/out merge as this work has been superseded.


Move config file to config folder

I propose to move the configuration file to the ~/.config folder. This one has a lot of config files for many programs, it has become "common" for several years.
Also this will make it less likely that users will accidentally delete the file by wonder what is it.
Since the file is located in a dedicated "origami" folder, I also renamed the file "applications" to be more precise on what it contains.

Hey, thanks for these changes!
I agree it would be more coherent, but could you add a small test case to cover this new behaviour? Also, do not silent the errors with @ please. 😉

Should I also remove the @ for existing code? (in the FilesystemException condition) ?
I wonder though why that class don't use the symfony filesystem component, maybe a forgotten update?

Should I also remove the @ for existing code? (in the FilesystemException condition) ? I wonder though why that class don't use the symfony filesystem component, maybe a forgotten update?

Sorry for the delay!

When I was saying could you add a small test case, it was about adding a unit case to cover this scenario. 😉
About Symfony Filesystem component, feel free to use it if you consider it a nice addition.

Or just few hours... Seems ok for me.
Tested on my local several times.


toHaveColumnValuesInSet can accept a column header that does not exist

column_1

a

b

c

const set: Set<string> = new Set(["a", "b", "c");
await expect(myTableLocator).toHaveColumnValuesInSet("no_column", set);

This passes when called from playwright-tables because the column no_column does not exist, therefore this should fail and print out the available headers.

I've had a go at this and raised a PR. It's the simplest fix, so nothing smart like collecting all the different rows that don't contain the expected header. See what you think...


Implementing OtelJMX metrics exporter for JMX metrics insights

Issue #, if available:
Description of changes:

Implemented custom provider for OtelJMX metrics insights
Is enabled when AWS_JMX_ENABLED is set to true
Sets up a metrics exporter over 4314 port only over HTTP protocol

Testing
Tested as part of amazon-cloudwatch-observability helm-chart

Annotate a pod deploying a sprint boot project with     instrumentation.opentelemetry.io/inject-java: "true" cloudwatch.aws.amazon.com/inject-jmx-jvm: "true" and deploy on the cluster
Deploy the helm-chart with a custom amazon-cloudwatch-operator build to inject the following environment vars

OTEL_EXPORTER_OTLP_PROTOCOL
OTEL_METRICS_EXPORTER
OTEL_LOGS_EXPORTER
AWS_JMX_EXPORTER_METRICS_ENDPOINT
OTEL_JMX_TARGET_SYSTEM

Verified AwsJMX exporter is enabled in pod logs

 INFO software.amazon.opentelemetry.javaagent.providers.AwsJMXMetricsCustomizerProvider - AWS JMX metric collection enabled

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Please update the PR with the verification result of the following test cases as there's no UT added for those changes:

OTEL_METRICS_EXPORTER is none, OTEL_AWS_JMX_EXPORTER_METRICS_ENDPOINT is not set -> no metrics are exported.
OTEL_METRICS_EXPORTER is none, OTEL_AWS_JMX_EXPORTER_METRICS_ENDPOINT is set, OTEL_JMX_TARGET_SYSTEM is jvm -> only JMX JVM metrics are exported to AWS JMX EP, no other metrics are exported.
OTEL_METRICS_EXPORTER is not none (e.g. logging), OTEL_AWS_JMX_EXPORTER_METRICS_ENDPOINT is set, OTEL_JMX_TARGET_SYSTEM is jvm -> only JMX JVM metrics are exported to AWS JMX EP, all metrics are exported to the default exporter, JMX JVM is dual published.
OTEL_METRICS_EXPORTER is not none (e.g. logging), OTEL_AWS_JMX_EXPORTER_METRICS_ENDPOINT is not set -> no metrics are exported to AWS JMX EP, all metrics are exported to the default exporter.
OTEL_METRICS_EXPORTER is not none (e.g. logging), otel.jmx.enabled is disabled, OTEL_AWS_JMX_EXPORTER_METRICS_ENDPOINT is set, OTEL_JMX_TARGET_SYSTEM is jvm -> same as 4, except JMX JVM metrics are not exported to the default exporter.

Tested and it didn't emit any metrics as expected.

- env:
        - name: OTEL_METRICS_EXPORTER
          value: none

JVM metrics received:

- env:
        - name: OTEL_METRICS_EXPORTER
          value: none
        - name: OTEL_AWS_JMX_EXPORTER_METRICS_ENDPOINT
          value: http://cloudwatch-agent.amazon-cloudwatch:4314/v1/metrics
        - name: OTEL_JMX_TARGET_SYSTEM
          value: jvm

JVM metrics received:
Same as above.

We got errors in the logging to show it was trying to send metrics to the default OTLP exporter endpoint.

- env:
        - name: OTEL_METRICS_EXPORTER
          value: otlp
        - name: OTEL_AWS_JMX_EXPORTER_METRICS_ENDPOINT
          value: http://cloudwatch-agent.amazon-cloudwatch:4314/v1/metrics
        - name: OTEL_JMX_TARGET_SYSTEM
          value: jvm

Same error and no metrics.

- env:
        - name: OTEL_METRICS_EXPORTER
          value: otlp
        - name: OTEL_JMX_TARGET_SYSTEM
          value: jvm

Same error and no metrics like above.

- env:
        - name: OTEL_METRICS_EXPORTER
          value: otlp
        - name: OTEL_JMX_ENABLED
          value: "false"
        - name: OTEL_AWS_JMX_EXPORTER_METRICS_ENDPOINT
          value: http://cloudwatch-agent.amazon-cloudwatch:4314/v1/metrics
        - name: OTEL_JMX_TARGET_SYSTEM
          value: jvm


Driver for the sensirion sht85 sensor

Adds a driver for the sensirion sht85 sensor and a sensirion sensor bridge. It uses official drivers of sensirion to communicate with the sensor bridge.

Pretty nice first commit into basil!

I do not know the Sensirion box etc. so it is tough for me to judge this. From what I read, it works as the following:

there is a sensirion box that allows to have up to 2 ic2 devices connected to it. This is the TL SensirionSensorBridge
the i2 devices can be connected to it. A generic i2c device is SensirionBridgeI2CDevice
a specific i2c device are the temperature devices sensirionSHT85

I mean that is (as I can quickly judge) a very clean and generic implementation to support hardware we have and to support hardware we don't have ;-)
If we are only going to use the bridge with the temperature sensors, one could maybe just make one driver and skip the extra TL.
For lab devices I originally used the TL to specify the means of communication (RS232, TCP/IP, GPIB, USB and the library NI VISA, python.socket, ...). This makes a lot of sense for lab devices that have multiple interfaces (e.g. TTi, Keithleys, ...). I am not sure what we gain for having such generic TL/HL pattern, when the TL is not interchangeable, not configurable and fixed (@michaeldaas an me discussed that recently, too).

I recommend to configure your editor in a way that it takes care of the code style. Good editors (pydev, VStudio Code, ...) can do that. When you clean up the formatting issues https://travis-ci.org/github/SiLab-Bonn/basil/jobs/741928925#L5989 it is fine to be merged. You can check for code flaws by typing:
flake8-diff origin/development

Also, you see that the CI failed due to code flaws

Coverage decreased (-1.1%) to 32.447% when pulling 72e09d34c412ea8a2d562a46501e67a5e8df826c on sensirion_sht85 into 968842a120f8699963ff7ec967b5d427a1551818 on development.


test(theme): <ThemeProvider/>

Can we also test body class?

Assert that body got specific class name? We cant guarantee anything with this test

Can we also test body class?

Assert that body got specific class name? We cant guarantee anything with this test

Why not? We expect a specific class to be set for the body.


Feature/diagnostics system port

XRTK - Mixed Reality Toolkit Change Request
Overview
Ported the latest implementation of the MRTK DiagnosticsSystem over and made necessary Adjustments. There is some open TODOs:

[x] OnDiagnosticsChanged() in MixedRealityDiagnosticsSystem.cs is never executed and the event does not fire respectively. Implementing this will allow to do runtime changes to settings of the diagnostics system, since the Visual Profiler implements IMixedRealityDiagnosticsSystemHandler.

[x] Support for all XRTK platforms Needs to be verified. E.g. while it works on Android mobile AR it actually Displays in 3D space. Probably for mobile s screen space overlay solution would be more appropriate. Also I could not verify Lumin support.

[X] Supports UWP
[X] Supports Android
[X] Supports iOS
[x] Supports Lumin

Target of the change:

Core (core framework, interfaces and definitions)

Changes:

Added new visual profiler component to visualize diagnostics data
Updated inspector
Updated profile settings

XRTK/SDK PR 28 is part of this: https://github.com/XRTK/SDK/pull/28

Can we review and update the outstanding tasks prior to merging?
Platforms must be tested prior to merge

Stephen can take care of ML
I can do HL (when my device returns this week)
Can you test iOS or do we need help with that?

Upi also need to refresh your submodules as they are showing out of date and could cause issue.

Thanks1 I can test iOS later today and check the submodules.

Just a note, make sure the Submodule checkouts are always the latest development checkout sha.

/azp run

Tested on iOS. Behaves the same as on Android.

I'll test it on Lumin soon.

Getting this warning when building to device and running in the editor:
A shader supporting instancing could not be found for the VisualProfiler, falling back to traditional rendering. This may impact performance.

https://github.com/FejZa/XRTK-Core/pull/1

@StephenHodgson thank you. I'll look into the shader warning. Pretty sure I know what's up.

@StephenHodgson Added missing shader to XRTK.Core/StandardAssets/Shaders. The warning is gone now.

@FejZa just need to resolve the conflicts and we should be good to go.


content/local: don't open file with sync

After running into performance issues when sending in certain kinds of
content, synchronous writes for content have been removed. Content is
still synced on commit, so this shouldn't be necessary.
Signed-off-by: Stephen J Day<EMAIL_ADDRESS>cc @tonistiigi

LGTM

Codecov Report

Merging #1784 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master    #1784   +/-   ##
=======================================
  Coverage   49.06%   49.06%
=======================================
  Files          77       77
  Lines        7719     7719
=======================================
  Hits         3787     3787
  Misses       3289     3289
  Partials      643      643

Flag
Coverage Δ

#linux
49.13% <100%> (ø)
:arrow_up:

#windows
44.85% <100%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

content/local/store.go
50.66% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 67232e9...5113299. Read the comment docs.


[release-1.22] Bump Go to 1.16.14

From https://github.com/kubernetes-sigs/descheduler/pull/744
Affects go 1.16 and 1.17

/lgtm


Ashtech GPS driver conversion

This piece of code for coordinate conversion looks wrong and needs inspection.
_gps_position->lat = (int(lat * 0.01) + (lat * 0.01 - int(lat * 0.01)) * 100.0 / 60.0) * 10000000;
_gps_position->lon = (int(lon * 0.01) + (lon * 0.01 - int(lon * 0.01)) * 100.0 / 60.0) * 10000000;

According to this page: http://www.gpsinformation.org/dale/nmea.htm#position
It starts to make sense, as it is a degree / minute / second conversion.


Remove Usage Tracking

For commercial products, tracking user data may be an understandable and acceptable thing. But for an open source software... well, I think this will become a very controversial behavior (even if you just collects seemingly harmless data).  I don't think people would want the JuiceFS process they run to send any data to endpoints that aren't part of their project.
Therefore, please consider removing any “tracking” behavior. ❤

@aofei Very good point. You can disable it with a command line argument.
So we'd like to keep it for now, to better understand how the community is using it.

@aofei Very good point. You can disable it with a command line argument.
So we'd like to keep it for now, to better understand how the community is using it.


[tcgc] update crossLanguageDefinitionId to correspond to apiview

fixes https://github.com/Azure/typespec-azure/issues/849

:x: There is undocummented changes. Run chronus add to add a changeset or click here.
The following packages have changes but are not documented.

:x:@azure-tools/typespec-client-generator-core

Show changes

You can try these changes at https://cadlplayground.z22.web.core.windows.net/typespec-azure/prs/936/
Check the website changes at https://tspwebsitepr.z22.web.core.windows.net/typespec-azure/prs/936/


Destructuring assignment not working when downloading PDF

Version info:

Node 10.16.0
Puppeteer 4.0.0
Laravel 6.18.20

I am trying to download a PDF using the following:
return PDF::loadHtml($html)->download($filename);

When I do this, I get the following error:
[2020-06-19 17:52:02] local.ERROR: The command "PATH=$PATH:/usr/local/bin NODE_PATH=`npm root -g` node '/home/code/laravel/vendor/spatie/browsershot/src/../bin/browser.js' '{"url":"file:\/\/\/tmp\/1176757848-0907304001592589121\/index.html","action":"pdf","options":{"path":"\/tmp\/594410754-0907194001592589121\/BrowsershotOutput1592589121G9jfs.pdf","args":[],"viewport":{"width":800,"height":600},"displayHeaderFooter":false}}'" failed.

Exit Code: 8(Unknown error)

Working directory: /home/code/laravel/public

Output:
================

Error Output:
================

/home/code/laravel/vendor/spatie/browsershot/bin/browser.js:6
const [, , ...args] = process.argv;
      ^
SyntaxError: Unexpected token [
    at Module._compile (module.js:439:25)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)
    at node.js:929:3
 {"userId":39767,"exception":"[object] (Symfony\\Component\\Process\\Exception\\ProcessFailedException(code: 0): The command \"PATH=$PATH:/usr/local/bin NODE_PATH=`npm root -g` node '/home/code/laravel/vendor/spatie/browsershot/src/../bin/browser.js' '{\"url\":\"file:\\/\\/\\/tmp\\/1176757848-0907304001592589121\\/index.html\",\"action\":\"pdf\",\"options\":{\"path\":\"\\/tmp\\/594410754-0907194001592589121\\/BrowsershotOutput1592589121G9jfs.pdf\",\"args\":[],\"viewport\":{\"width\":800,\"height\":600},\"displayHeaderFooter\":false}}'\" failed.

Exit Code: 8(Unknown error)

This seems to indicate that destructuring assignment is not supported (which I think is new with ES6), but I have the minimum requirements and don't see what else I could be doing wrong. Any help with this?

Hi @sschilli, the only way I was able to reproduce your error was using Node <6.0.0, my best guess is that you have multiple versions of node installed on your system.
Try specifying NODE_BINARY_PATH  on you're .env file to make sure you are using the right binary


[Fixes: #7462] Orchard.OutputCache - Possible NRE in DefaultTagCache ctor when accessing the WorkContext

Fixes #7462

Hi @Xceno, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

My bad, I just fixed them. Thanks!


Couldn't find a way to convert tflite to tensorflow graph

Hello all,
I am new to this world so hopefully my question will be as clear as possible and related to this forum.
I want to be able to convert tflite file to tensorflow graph.
I have tried several ways:
tflite --> onnx : I used
tflite2onnx.convert(tflite_path, onnx_path)
Result:
NotImplementedError: Unsupported TFLite OP: 41
It seems there is an unsupported operations (maybe more) and I was unable to convert
tflite --> pb
I looked on the net and found that it is possible only up to tf 1.9 so I downgraded my tf to 1.9
and tried following the instructions (which included using bazel, couldn't even install bazel)
Anyway Is there a known way (either one of the above or any other you can think of)
that I can use and hopefully works?
Thanks in advance
Chen

There is no way to do this currently. Do you not have access to the original source TensorFlow graph?


chore: use bundle packaging format

@ricardomaraschini I'll do you suggested changes on https://github.com/quay/quay-operator/pull/538


Installed on a clean 7.4.1 (on UAAS)

Installed Umbraco 7.4.1 (pull from UAAS)
Installed FormEditor via nuget
Started website
This happens:

Hi @jesperordrup,
I haven't had time to implement UaaS support in FormEditor yet. What you're seeing is pretty much what I'd expect to see on UaaS :)
It's on my TODO list.

It seems to work on UAAS if you just install as an umbraco package .. both locally and on Azure

Oooh.... right. Then I think I know what the problem is; FormEditor has a dependency on Umbraco core binaries v7.3, because it's compatible with 7.3+.
I've actually made a note of it in the "extending FormEditor" docs here (although that was not meant as a comment specifically for UaaS).
All the same, UaaS support is on the drawing board - including finding the best way to actually support UaaS, be it nuget or package installs or whatnot. But thanks a lot for reporting and making me aware of the problem.

Hey Jesper, did you solve the issue by installing the package by hand?

Yup - downloaded the Umbraco Package and installed it via Developer section

Closing this for now. I might have to revisit UaaS stuff later on.


F504: Carriage return prevents expression extraction

In Python, a standalone carriage return character (0xd or \r) is considered whitespace. One could easily argue that this is quite problematic, given that carriage returns can potentially be used to hide parts of source code. That said, it does trigger a failure in F504 (\r replaced literally):
"" % {
  'test1': '',\r  'test2': '',
}

And a downloadable version to test against.
I would simply mark F504 as sometimes fixable, but this solution doesn't feel right. Instead, this feels indicative of incorrect handling of carriage returns as plain whitespace. At the same time, standalone carriage returns should probably be marked as invalid anyways.
I leave this to the discretion of the developers of Ruff :slightly_smiling_face: We should find a fix one way or another to avoid future issues with this being marked as a failure case in the fuzzer.
Discovered by #4822.

Perhaps a bug in LibCST, which is failing to parse it?

I'm not so clear on that. Is this because libCST is used to parse the expression for repair?

Yeah

The LibCST parse call throws an error, but it could be our fault, not theirs. We may need to wrap the expression in parentheses before parsing.

We may need to wrap the expression in parentheses before parsing.

I did a quick experiment and this doesn't help either, it still throws an error:
libcst_native::parse_expression(&format!("({})", &contents))

Failed to parse file: Internal error while parsing whitespace: Found newline at (2, 15) but it's not EOL

This is a bug in LibCST. It seems they don't support mixed newlines:
https://github.com/Instagram/LibCST/blob/c91655fbba7c27db05423673609f10203316b9c0/native/libcst/src/tokenizer/whitespace_parser.rs#L67-L88

Upstream fix in LibCST https://github.com/Instagram/LibCST/pull/1007/files

The upstream fix is merged. All that we need to do now is to update libcst 🫣


typescript module not found error while running "npx shadcn-ui@latest init"

while initializing shadcn-ui using the command "npx shadcn-ui@latest init" in nextjs using typescript an error is generated
which says
cons err= new Error(message);
Error: cannot find module '@ts-morph/common'
Installed ts-morph using yarn ("yarn global add ts-morph) but the error still persists

To expedite the triage process, we need everyone to follow the issue template and instructions.
When you clicked "Create New Issue", the issue form was pre-populated with a template and some instructions. We need you to read those instructions completely, follow them, and then fill in all the fields in that template.
We are not able to assist with issues that don't follow the template instructions as they represent a significantly larger amount of work compared to issues which are correctly specified. Thank you for understanding.

Please use npm instead of yarn to install or initialize shadcn-ui ⚡🧑💻


Alias db:migrate:down and db:migrate:up

The up/down migration tasks should also be aliased, for deploy tools such as capistrano, mina, etc.

Yep, thanks


Docker container: Error during analysis task

Hi,
I was trying to execute the Regression in Machine Learning hands-on by using the docker container.
After uploading data and setting parameters according to the hands-on instructions I run the analysis but after a while, I got this error:
Fatal error: Exit code 1 (Error occurred. Please check Tool Standard Error)
Using TensorFlow backend.
/export/tool_deps/_conda/envs/mulled-v1-26f90eb9c8055941081cb6eaef4d0dffb23aadd383641e5d6e58562e0bb08f59/lib/python3.6/site-packages/sklearn/externals/joblib/__init__.py:15:
DeprecationWarning: sklearn.externals.joblib is deprecated in 0.21 and
will be removed in 0.23. Please import this functionality directly from
joblib, which can be installed with: pip install joblib. If this warning
is raised when loading pickled models, you may need to re-serialize
those models with scikit-learn 0.21+.
   warnings.warn(msg, category=DeprecationWarning)
Traceback (most recent call last):
   File
"/export/galaxy-central/database/job_working_directory/000/2/tmp6OCskg",
line 11, in <module>
     from galaxy_ml.utils import load_model, get_X_y
   File
"/export/tool_deps/_conda/envs/mulled-v1-26f90eb9c8055941081cb6eaef4d0dffb23aadd383641e5d6e58562e0bb08f59/lib/python3.6/site-packages/galaxy_ml/utils.py",
line 15, in <module>
     import xgboost
   File
"/export/tool_deps/_conda/envs/mulled-v1-26f90eb9c8055941081cb6eaef4d0dffb23aadd383641e5d6e58562e0bb08f59/lib/python3.6/site-packages/xgboost/__init__.py",
line 11, in <module>
     from .core import DMatrix, Booster
   File
"/export/tool_deps/_conda/envs/mulled-v1-26f90eb9c8055941081cb6eaef4d0dffb23aadd383641e5d6e58562e0bb08f59/lib/python3.6/site-packages/xgboost/core.py",
line 136, in <module>
     _LIB = _load_lib()
   File
"/export/tool_deps/_conda/envs/mulled-v1-26f90eb9c8055941081cb6eaef4d0dffb23aadd383641e5d6e58562e0bb08f59/lib/python3.6/site-packages/xgboost/core.py",
line 128, in _load_lib
     lib.XGBGetLastError.restype = ctypes.c_char_p
UnboundLocalError: local variable 'lib' referenced before assignment

The same occurred trying to run the classification example.
Running the same examples on an external Galaxy instance (for example https://usegalaxy.eu/) everything works fine.
Do I need to do something special using the docker container or is it an issue of the docker image?
Thank you in advance
Giovanni

@Strato75 can you check if the tool version is the container is the same as in usegalaxy.eu? I suspect we need to update the container.

@bgruening the Galaxy tool version of the container is <IP_ADDRESS> whereas in usegalaxy.eu is <IP_ADDRESS>.
The tool version row, for the docker container, shows "None" but I imagine that it is because the process is stopped due to the error. If it is useful I can attach a screenshot.

If you need to container now, go to the admin panel and try updating the tool. We should rebuild the container I think to get the latest version of the tool.

It is my first time using Galaxy so I can try to update the tool version but I don't know if I am able to manage that. How much time do you think it takes to make a new version of the docker image?

We just need to find time, its not a big deal. But we are this week very busy. Is usegalaxy.eu good enough for you for the moment?

I managed to update all the tools. Now they are at version <IP_ADDRESS>. I deactivate the older ones but I still get the same error message. Maybe I did not make the update process properly, I don't know. I am not in a hurry I was just trying examples so, if you do not have any other suggestions,  I can surely use the usegalaxy.ue instance waiting for the docker container update. Thank you.

I don't know if it can be useful, but I managed to perform the linear regression analysis by making a minor change in the file:
/tool_deps/_conda/envs/mulled-v1-26f90eb9c8055941081cb6eaef4d0dffb23aadd383641e5d6e58562e0bb08f59/lib/python3.6/site-packages/galaxy_ml/utils.py

I put the import of the xgboost module at the top of the file and the error disappeared.
Tomorrow I'll check if some of the other analysis work as well.


messaging issues on latest android client

Summary
messages missing or not getting updated or not getting sent after latest android client update, whereas previously never any such issue
Environment Information

Device Name: Google Pixel 4a
OS Version: 13
Mattermost App Version: 2.0.0 Updated 13 Jan 2023
Mattermost Server Version: Mattermost Version: 7.1.3, Database Schema Version: 89, Database: postgres

Steps to reproduce
Just use the app normally to navigate channels and chat with people. Happens randomly.
Expected behavior

when opening a channel, it shows all the messages in there, adding any new messages as they come
when sending a message, it gets sent and delivered
when reacting to messages, the reaction is swiftly applied

Observed behavior (that appears unintentional)

when opening a channel, sometimes but too often it has no messages, or it has only some but not all messages, or it has the messages from some time ago but not the very latest ones
when sending a message, sometimes but too often it immediately fails, and I have to click the little red circle, then then click "try again"
when reacting to messages, sometimes but too often nothing seems to happen. Just now when re-trying I got stuck in the reaction GUI, and had to force kill and restart the client to be able to return to messages.

Possible fixes
No code fixes to suggest. What works for me is:

exit and reopen the channel until messages show up. Might take a few tries. Sometimes have to force kill and restart the client.
manual "try again" flow always works immediately with the first try.
force kill and restart, then it works.

d'oh fixed typo on client version; 2023 of course, not 2013 (facepalm)

WRT Elias' comment; I don't know the codebase or architecture all, but my first guess would also be connectivity related. Adding a couple details:

very rarely any issues previously. The client update is the only known change here, and issues started immediately after updating the client.
when message sending fails as described here, it fails instantly. As soon as I finish typing and press send, it's an immediate failure, without any visible attempt to send the message. When using the retry flow, it generally works immediately and on the first try.
which ever way my personal device, my personal networks, the other networks and the server itself if set up, these all used to work perfectly on the previous client.
If there was a network failure, I would usually expect to first see an attempt to communicate, and then failure only after a timeout, and retry should not help until only after connectivity is restored.

Hope this helps! Happy to answer questions.

Our users report similar behaviour after updating the mobile app.

here's a case from today:
I was moving away from a wifi, but the phone had not quite yet given up on it. Trying to a send a message, the client GUI indicates that delivery is being attempted by promptly adding my message to the chat but rendering it in gray instead of black. Some seconds later the message turns from gray to black to indicate successful delivery, whether because the wifi still had a bit of kick left or the device shifted to cellular net and auto-retried delivery. Normal and expected behaviour.
A couple minutes later, by now far from the wifi and firmly on the cellular network, I sent two messages in quick succession, just a couple seconds between messages. The first one was instantly delivered (turned instantly black), the second one instantly failed, i.e. remains gray and has the red error circle next to it, which apparently indicates permanent failure until manual retry. There was no hint of any attempt to deliver the message, like in the case two minutes earlier. And again, pressing the red error circle to use the manual try again -feature, now instant successful delivery.

Same issue #2 for me - randomly messages do not send and you need to press try again. Server/app details attached.

I can also report having a similar problem.
Out of nowhere i get an instant and unexpected message that failed to get sent. Network is fine with no intermittent issues what so ever. The common denominator is that the message fails immediately without trying to get sent.

I might have fixed my issues by disabling Settings -> Advanced -> Allow message drafts to sync with the server.
Please give it a try.

@c0deright Just tried it, and it still happens on my mobile client even after turning it off.  Happens every 20 or so messages.

Opened https://mattermost.atlassian.net/browse/MM-49968.

There doesn't seem to have been any updates to that issue since January 30th.
@amyblais is there actually work being done on this?  These issues have made the mobile app completely useless for myself, and likely others.

@Willyfrog Should this ticket be moved to the Core 1 team? https://mattermost.atlassian.net/browse/MM-49968

@amyblais Any updates on this?  I still see the MM issue as "unassigned" with no updates on it.

@larkox @Willyfrog I've moved the ticket to the Mobile team, but let me know if that's not the correct team

@larkox In the Beta the chat history issue seems to be resolved but the immediate fail on send is still present.  Though instead of having to retry the send multiple times it now seems to succeed on the first retry.

Can you send me the logs? If you go to your profile, and click settings, you should see a report a problem link. You can DM me in Mattermost Community and I can give you my email if needed<EMAIL_ADDRESS>

Sorry, I missed the first mention, but yes, mobile is fine right now

Is anyone still experiencing this issue? If so, can you send me the logs on community? If not, I will close this ticket in the following days.

Hi @larkox thanks for asking!
Quick test right now:

I selected a channel. It was showing old content. Waited a few seconds. No change, and no visually apparent attempt to do anything.
Dragged to refresh. Spinner appears. Spinner quickly disappears. Channel is not refreshed.
Dragged to refresh again. Spinner appears. Spinner remains on screen. After a second, channel is refreshed and spinner disappears.
Sent a private message. It was immediately delivered.
Without delay sent another message. Message remains gray, and red (i) circle appears immediately.
Pressed the red (i) circle in order to try again. The try again popup did not appear. App is unresponsive. After waiting a few minutes, force killed app.
Restarted app. Red (i) circle is still next to grayed out message draft. Pressed it. Getting Try Again prompt. Pressed Try Again. Message was delivered.

All except the last point was with a good high bandwidth 4G connection with full bars, and this is consistent with the MatterMost issues which first started upon upgrading to v2.0.0.
Should I be testing a beta version? This is the normal one.
Current versions:
App 2.4.0 (Build 6000471)
Server 7.1.3
Database Postgres
Schema 89

hola @larkox
I will send you a sample log via PM in a moment, once I figure out how to do that. The log includes the server URL so I hope it can be kept private?
I have redacted some channel/person names, I imagine this does not reduce the usefulness of the log. Not sure how useful the log is in general, mainly it seems to say "unexpected end of stream" where issues occur.
Not knowing anything about MatterMost's architecture, I will make myself ridiculous by analyzing the logs regardless; seems that WebSockets are being used, and are assumed to be good, but in fact the WS is often unusable. The fact that failure is instant could hint that the WS was already closed, but the MatterMost application did not receive notification that it was closed. In other situations in the log there is a different kind of message when the WS is closed and then reconnected.
FYI in our setup the MatterMost server is being proxied by Apache from an intranet IP. Would not surprise me at all if Apache just kills the underlying TCP socket without doing a WebSocket disconnect notification.
Would it be possible to make MatterMost just silently automatically reconnect and retry when unexpected end of stream occurs? Without requiring the user to click on retry. We did not have this issue in the pre-2.0.0 client, so I imagine it must have done something like that. Our server setup has not changed, it was exactly like this already before 2.0.0 shipped.
On a gut feeling, I would say that channel switching is working much better on this beta version. It does not always immediately refresh the channel, and it does not show a spinner, but if I just wait a few seconds, usually the channel will refresh without action. Nice work, thank you!

Hi @skmakine,
That is almost exactly what is going on in my case as well.  We have
Mattermost fronted by an HAProxy load balancer instead though.  No issues
with v1.x of the app, but the minute someone got the v2.x app it was
basically too broken to use.  The beta is a bit better however it still
isn't as functional as the v1.x app was.
I hope that the issue can be determined soon so that the app will once
again work reliably.
On Fri, Jun 16, 2023 at 8:45 AM skmakine @.***> wrote:

hola @larkox https://github.com/larkox
I will send you a sample log via PM in a moment, once I figure out how to
do that. The log includes the server URL so I hope it can be kept private?
I have redacted some channel/person names, I imagine this does not reduce
the usefulness of the log. Not sure how useful the log is in general,
mainly it seems to say "unexpected end of stream" where issues occur.
Not knowing anything about MatterMost's architecture, I will make myself
ridiculous by analyzing the logs regardless; seems that WebSockets are
being used, and are assumed to be good, but in fact the WS is often
unusable. The fact that failure is instant could hint that the WS was
already closed, but the MatterMost application did not receive notification
that it was closed. In other situations in the log there is a different
kind of message when the WS is closed and then reconnected.
FYI in our setup the MatterMost server is being proxied by Apache from an
intranet IP. Would not surprise me at all if Apache just kills the
underlying TCP socket without doing a WebSocket disconnect notification.
Would it be possible to make MatterMost just silently automatically
reconnect and retry when unexpected end of stream occurs? Without requiring
the user to click on retry. We did not have this issue in the pre-2.0.0
client, so I imagine it must have done something like that. Our server
setup has not changed, it was exactly like this already before 2.0.0
shipped.
On a gut feeling, I would say that channel switching is working much
better on this beta version. It does not always immediately refresh the
channel, and it does not show a spinner, but if I just wait a few seconds,
usually the channel will refresh without action. Nice work, thank you!
—
Reply to this email directly, view it on GitHub
https://github.com/mattermost/mattermost-mobile/issues/7021#issuecomment-1594701286,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABCAJHCBTXB2WY33AY7QYRLXLRPOFANCNFSM6AAAAAAUGQSSQY
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Justin Paulsen
IT Professional
"The world is open, are you?"

@Petaris thanks to some awesome debugging by @larkox I changed the Apache proxy config to disable connection KeepAlive, and for me this works perfectly!

Has this improved in any way since the linked pr was merged?

I still encounter this issue (messages instantly failing to send) multiple times per day, on the latest non-beta Android version.

@lexelby Any chance you can share the app logs with me at the community server?
<EMAIL_ADDRESS>

I'm sorry, I haven't found the time to gather the logs.  I do have some hints though.  I had mattermost running in docker, and I was forwarding http to it using Apache as a reverse proxy.  I had a mod_rewrite setup that forwarded normal requests and websockets.
I solved the problem by exposing mattermost's port directly and pointing android clients at it.  ios never had the problem.  For reasons that don't matter, I ended up fronting mattermost's port with stunnel and that works too.  No more send failures.

I still have the issue as well, though not as often.  I'm using the release
version on Android.  I have HAProxy in front of Mattermost, so maybe that
is a consideration.  I am not using any rewrites though.
Mine is on Docker as well, though I build my own Docker container which
uses OpenSUSE Leap as the base.  I don't think this has anything to do with
the issues though.
On Fri, Feb 2, 2024 at 8:21 PM Lex Neva @.***> wrote:

I'm sorry, I haven't found the time to gather the logs. I do have some
hints though. I had mattermost running in docker, and I was forwarding http
to it using Apache as a reverse proxy. I had a mod_rewrite setup that
forwarded normal requests and websockets.
I solved the problem by exposing mattermost's port directly and pointing
android clients at it. ios never had the problem. For reasons that don't
matter, I ended up fronting mattermost's port with stunnel and that works
too. No more send failures.
—
Reply to this email directly, view it on GitHub
https://github.com/mattermost/mattermost-mobile/issues/7021#issuecomment-1925024098,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABCAJHBCZRPVCEVU22ZIPBTYRWNJHAVCNFSM6AAAAAAUGQSSQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRVGAZDIMBZHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Justin Paulsen
IT Professional
"The world is open, are you?"


nannou crate build failed

Crate name: nannou
Build failure link: https://docs.rs/crate/nannou/0.12.0/builds/196525
Additional details:
The build seems to fail on the xcb dependency version 0.8.2, however this build has succeeded in the past and is currently available on docs.rs. This leads me to wonder if the cause is a bug in the latest rustdoc nightly. Is it possible to get the documentation re-built with stable?

Related: https://github.com/rust-lang/docs.rs/pull/229, https://github.com/rust-lang/docs.rs/issues/228

Your build error doesn't seem to be related to the version of rust, though. cc @pietroalbini, do you intentionally make /opt/rustwide/cargo-home read-only?

It looks like xcb is a new dependency in nannou 0.12, I wonder if it's trying to write to part of the filesystem it's not supposed to. I know we changed the sandboxing pretty significantly about a month ago in the switch to rustwide: https://github.com/rust-lang/docs.rs/pull/407, maybe xcb hasn't been rebuilt since then?

Your build error doesn't seem to be related to the version of rust, though. cc @pietroalbini, do you intentionally make /opt/rustwide/cargo-home read-only?

Yeah, otherwise a malicious crate could've messed up the state for other crates.

It looks like xcb is a new dependency in nannou 0.12, I wonder if it's trying to write to part of the filesystem it's not supposed to. I know we changed the sandboxing pretty significantly about a month ago in the switch to rustwide: #407, xcb hasn't been rebuilt since 2018: https://docs.rs/crate/xcb/0.8.2/builds/87332

I just tried building xcb 0.8.2 myself using docker-compose run web build crate xcb 0.8.2, and this appears to be what caused the problem.
The crate has a python script rs_client.py which it uses to create some FFI files. The exact line it fails at is rs_client.py:114.
The good news is, xcb 0.9.0 works fine, so I think if x11-clipboard (the dependency of copypasta, the dependency of conrod_core, the dependency of nannou) upgrades to 0.9.0, this should be fixed.

Looks like this isn't a bug in docs.rs, going to close this.

Thanks for digging into this @alberdingk-thijm!

Looks like this isn't a bug in docs.rs, going to close this.

@jyn514, do you happen to know when docs.rs will try to build nannou (and the other crates related to this error in xcb) again?

Rebuilding automagically is #464 . Currently someone has to schedule a manual build.

This particular crate won't be helped by rebuilding however because it tries to write to a read only filesystem.

We tracked down the dependency (x11-clipboard) that caused the error and sent a PR https://github.com/quininer/x11-clipboard/pull/17 through, which has been bubbled up to the other dependency copypasta in a minor patch https://github.com/jwilm/alacritty/pull/3024. conrod_core (the dependency which pulls in copypasta) just requests 0.6, so I would think building with copypasta 0.6.1 would get rid of this issue, although admittedly I can't seem to figure out how to tell the docker container to do that on my own machine.

@alberdingk-thijm Could you make these updates in a different repo, such as https://github.com/nannou-org/nannou/issues/429? This is not a docs.rs bug.

Oh hold on I think I misunderstood your comment. You're asking us to build with a different version of a minor dependency? We don't control dependency management, that's done by cargo. If you've fixed the bug you can publish a new version and docs.rs will build that version.

Oh hold on I think I misunderstood your comment. You're asking us to build with a different version of a minor dependency? We don't control dependency management, that's done by cargo. If you've fixed the bug you can publish a new version and docs.rs will build that version.

Gotcha, that's what I was asking. Thanks for your help!


Unable to build docker image

Steps to reproduce:

git clone https://github.com/druid-io/docker-druid.git
docker build -t druid/cluster docker-druid

Error message:
Oct 28, 2015 8:44:59 AM org.hibernate.validator.internal.util.Version <clinit>
INFO: HV000001: Hibernate Validator 5.1.3.Final
2015-10-28T08:45:00,153 INFO [main] io.druid.guice.JsonConfigurator - Loaded class[class io.druid.guice.ExtensionsConfig] from props[druid.extensions.] as [ExtensionsConfig{searchCurrentClassloader=true, directory='druid_extensions', hadoopDependenciesDir='hadoop_druid_dependencies', loadList=null}]
2015-10-28T08:45:01,402 INFO [main] io.druid.guice.JsonConfigurator - Loaded class[class io.druid.server.metrics.DruidMonitorSchedulerConfig] from props[druid.monitoring.] as [io.druid.server.metrics.DruidMonitorSchedulerConfig@2ca47471]
2015-10-28T08:45:01,408 INFO [main] io.druid.guice.JsonConfigurator - Loaded class[class io.druid.server.metrics.MonitorsConfig] from props[druid.monitoring.] as [MonitorsConfig{monitors=[]}]
Exception in thread "main" com.google.inject.ProvisionException: Guice provision errors:

1) Unknown provider[mysql] of Key[type=io.druid.metadata.MetadataStorageConnector, annotation=[none]], known options[[derby]]
  at io.druid.guice.PolyBind.createChoiceWithDefault(PolyBind.java:86)
  while locating io.druid.metadata.MetadataStorageConnector

1 error
	at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1014)
	at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1040)
	at io.druid.cli.CreateTables.run(CreateTables.java:108)
	at io.druid.cli.Main.main(Main.java:91)
The command '/bin/sh -c /etc/init.d/mysql start && java -cp /usr/local/druid/lib/druid-services-*-selfcontained.jar -Ddruid.extensions.coordinates=[\"io.druid.extensions:mysql-metadata-storage\"] -Ddruid.metadata.storage.type=mysql io.druid.cli.Main tools metadata-init --connectURI="jdbc:mysql://localhost:3306/druid" --user=druid --password=diurd && /etc/init.d/mysql stop' returned a non-zero code: 1

Hi @dzer6 I think this might be due to the fact that the extensions loading mechanism has changed in the current master branch, so we will probably have to make some adjustments. Can you try the 0.8.2 branch to see if it works with the current release candidate?

Hi Xavier!
It works for 0.8.2 and 0.8.1 branches but fails for master.
Best Regards,
Andrew

Thanks that's good to know. @guobingkun would you mind having a look at this, and see what tweaks need to be done to get the image to work after merging #1638 ? Ideally if we could make minimal adjustments, this would be a good real-work test to see if pull-deps works as expected to create a deployable directory structure.

@xvrl Sure, I will take a look at this.

@dzer6 Thanks for reporting the issue! Do you mind trying https://github.com/druid-io/docker-druid/pull/14 out?

@guobingkun Sure, will try this soon.

@guobingkun checked, works for me, thanks!

@dzer6 Awesome! Thank you!


Fingerprint sensors

@r-vdp does this work for you?
nix-repl> :p nixosConfigurations.turingmachine.config.facter.detected.fingerprint
{ enable = true; }

I tested this now on two different laptops. I thing this is good to go for the first iteration.

@mergify queue

@mergify refresh

@r-vdp we have too many frameworks. Not enough diversity.

@r-vdp we have too many frameworks. Not enough diversity.

Are you saying I need to expense some hardware? :thinking:

@brianmcgee you probably have to travel to thailand some time.


Send trace origin

Description
See https://github.com/getsentry/team-sdks/issues/14.

Then, I would close this for now cause it doesn't make any sense to keep this open until we add performance. You only have to ensure to add it once you add performance.


commented most of the units. These can be reactivated in case of need.

@ArndGerns habe ich korrigiert


Fix Ansible Linting Errors

This fixes these two linting errors:

fqcn-builtins: Use FQCN for builtin actions.
name: All names should start with an uppercase letter. (name[casing])

This will have to wait to land until travis tests are fixed, unfortunately.


Issue 96

I updated the welcome screen to have hyperlinks that perform actions to open a new library, or an existing library from a file - as they suggested from the issue thread.
Brief demo as follows:

@u7663394 Hi Guochen - I made some changes from the other PR. Please double check and let me know if you notice any issues, then i'll raise the PR with the main repo


Expiration date

1- It would be possible to add in the USERS part, when adding new user an expiration date. Give access to the USER with a predefined access time. after the end of the date access will be revoked
2 - within the user limit the maximum number of connections for the user. If I pass the list to someone only 1 user will have access. I can define the number of connections
thank you

xTeVe is not intended to be used as a Media Server

If you want to start a business this is the wrong software ;)

it is not to earn money, from time to time I send the list to some friends to use to watch different channels like soccer, I want to limit my list to only one, they can pass this list to other users of the family for example. my intention is not to make money, it never was. just limit access to those who pass a list of my VU + UNO 4K.

See my Comment....

i have a VU + uno 4k with support for 8 demodulators, ie 8 list (m3u8) i share with friends and family, i use xteve as m3u8 manager and program for my plex. I would like to know if they are sharing my m3u8 to others, as there are only 8 channels that my device supports. As much as I trust my friends and family I want to be sure heheh
If it were possible to identify it would be of great help, or even in the option users to have an option of how many connections per users.


add more rules - Drupal

Fixes #83
@MattIPv4 new PR :)

Hey @saidatom,
We are no longer maintaining the do branch, instead, you'll want to make a PR against the master branch and update the new drupal config generator there.


Use ruby's default bundler version

Hi,
In ruby 2.7, bundler version is 2.1
https://www.ruby-lang.org/en/news/2019/12/25/ruby-2-7-0-released/
With this line
https://github.com/dependabot/dependabot-core/blob/f6acb90326f54ad7b19d6045ad9d8f9960248855/bundler/lib/dependabot/bundler/helpers.rb#L21
dependabot use version 2.2 of bundler when reading Gemfile.lock made by the default bundler version in ruby 2.7
Any rationales behind this ?
Regards,

Hi @brrygrdn,
Seems reasonable not to support all 337 versions of https://rubygems.org/gems/bundler/versions.
How about supporting minor version (last patch) for each current version of ruby, I mean :

2.7
3.0
3.1

ℹ  2.6 support stops at this end of this month
This will make only 3 minors version :

2.1 for  ruby 2.7
2.2 for  ruby 3.0
2.3 for  ruby 3.1

Regards,

Also, why supporting bundler 1.17.3. Is their still users of this version ?

We generally don't factor in bundler/ruby version pairing since the version of Ruby in use is ultimately determined by Dependabot Core itself. We use variant bundler versions alongside our Ruby version as generally there isn't significant enough variance between Ruby and Bundler pairings to result in any difference in outcomes when generating diffs on Gemfiles.
The rationale for supporting Bundler 1.x vs Bundler 2.x is that there are significant breaking changes in the internal bundler code dependabot-core uses and at present we do actually have enough projects using Bundler v1.x versions it is worth supporting, but it's something we'd like to deprecate.


Hotfix + log

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 6 (66.67%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 54.31%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/cron/init.go
4
6
66.67%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
126

Relevant Lines:
232

💛  - Coveralls


Are the documented initializations correct?

I'm not positive that the readme or the demo application are initializing the Mixpanel instance safely.
For example, in the readme, this is the intended approach for initializing the Mixpanel instance:
import { Mixpanel } from 'mixpanel-react-native';
...
class YourClass extends React.Component {
    constructor(props) {
        super(props);
        this.configMixpanel();
    }

    configMixpanel = async () => {
        this.mixpanel = await Mixpanel.init("Your mixpanel token");
    }
...

I think that async initialization is generally frowned upon in constructors because you can't reasonably make predictions about the behavior.  In this case, it's possible that someone could try to access this.mixpanel before it has been assigned, right?
Often, if something has to be done asynchronously in React, it'll be handled in componentDidMount rather than in the constructor.  I know this isn't "loading" or "initializing" really, but it smells kind of funny.
I think that's probably partially why the MixpanelManager class was created in the demo project.  But, this also has async work in the constructor:
export default class MixpanelManager {
    static sharedInstance = MixpanelManager.sharedInstance || new MixpanelManager();

    constructor() {
        this.configMixpanel();
    }

    configMixpanel = async () => {
        this.mixpanel = await Mixpanel.init(MixpanelToken);
    }
}

It seems like there are two potential issues with this.  One of them is that it hides the fact that there's async work being done from the consumer.  The other is that there's not a good way for the consumer to wait for initialization before continuing.
Indeed, this code results in an error:
import { MixpanelManager } from './MixpanelManager';

MixpanelManager.sharedInstance.mixpanel.track("Race lost. :(");  // undefined is not an object

It totally makes sense that this kind of thing would pop up.  A lot of analytics libraries manage their own singletons.  They have an async init method you can await, but the singleton is always accessible.  In this case, we manage our own Mixpanel instance and we have to get it asynchronously because it constructs and initializes at the same time.
I guess, all of this is to say, are these examples appropriate as the canonical examples of how to consume this library?

Any progress on above issue? I am facing same error for initialization.
TypeError: this.mixpanel.track is not a function. (In 'this.mixpanel.track('my message')', 'this.mixpanel.track' is undefined)

@tncbbthositg Thanks for bringing it up. We will fix this.

@dipalinjawale, there are a few ways I considered handling this.  Typically, with an async init, you'll get a promise you can await, but that's kind of hidden in the docs.  With stateless functional components and hooks, maybe you could use state with a lazy initializer?  Something like this would probably work:
const mixpanel = useState(() => Mixpanel.init("Your mixpanel token"));

// ...

const onSomeEvent = async () => {
  // do important things
  (await mixpanel).logEvent("my event");
}

I have an analytics "service" to abstract the logging (so I can easily switch logging services . . . which I did recently to adopt mixpanel).
So, I have a lazy function that effectively memoizes a promise.  Memoization libraries do this really well . . . but I didn't feel like adding an entire library for this problem so here's what I did (in retrospect, I probably should've used lodash's once, but I didn't know about that at the time):
export function lazy<T>(init: () => Promise<T>): () => Promise<T> {
  let result: Promise<T>;

  return () => {
    if (!result) { result = init(); }
    return result;
  };
}

Then, in my service, I can use it like this:
const getMixpanel = lazy(async () => Mixpanel.init('my key'));

And I can await that promise before calling the logEvent function.
const instance = await getMixpanel();
instance.logEvent('my event');

I like having the service as an abstraction to isolate the init logic.  You could also use a hook like useMixpanel and have it return a Promise<Mixpanel>.
I have both the service and a hook.  I call useLogEvent('my event') and it returns a logEvent function and a logHandler function.  The logHandler function wraps another function with logging.
Something like this:
const { logHandler, logEvent } = useLogEvent('User Did Something Important');

// ...

const onPress = () => {
  // do important stuff

  // I can log like this
  logEvent({ customData: 'go here' });
}

// or, if I have a component that takes a handler as a prop, I can log like this
const { onSomeEvent } = props;
const loggedHandler = logHandler(onSomeEvent, { customData: 'go here' });

return (
  <>
    <button onPress={loggedHandler} />
    <button onPress={onSavePressed} />
  </>
);

The Mixpanel class method init() is potentially causing issues and we are now deprecating it.
Please try our latest version 1.3.1 and use the instance method init() instead.
import { Mixpanel } from 'mixpanel-react-native';

const mixpanel = new Mixpanel("Your Project Token");
mixpanel.init();

More examples: https://github.com/mixpanel/mixpanel-react-native/tree/master/Samples.
This folder contains 3 sample applications demonstrating how you can use Mixpanel in your React Native app.
SimpleMixpanel: Integrate Mixpanel with a minimalist approach
MixpanelDemo: A full Mixpanel API demo app
ContextAPIMixpanel: Integrate Mixpanel with Context API
I'm closing this one now. Please feel free to reopen if you have any issues. Again, thanks so much for bringing it up.

I just installed the latest. "mixpanel-react-native": "^1.3.1". And I'm getting this back...
[TypeError: mixpanel.init is not a function. (In 'mixpanel.init()', 'mixpanel.init' is undefined)]

hi @jamesdunay , sorry for the inconvenience. This is a known issue and we will address this shortly. For the time being, you can follow the workaround in here: https://github.com/mixpanel/mixpanel-react-native/issues/83

Hi @zihejia, despite the API change, you still provide a method named init which returns a promise. Can you please confirm whether it's necessary to await the result of mixpanel.init() in order for the mixpanel instance to function properly?
Both your ios and android implementations synchronously initialize Mixpanel, and immediately resolve the promise. So is initialization not actually asynchronous, or is Mixpanel perhaps buffering events internally so that callers don't need to deal with that detail?
So anyways, just looking for clarity on whether we need to wait on that init promise or not.
Thanks!


Suggestion about project settings

I think it would be good to have project settings for Qodot, so users can set default settings per project. For example:

Default directories for map files and textures
Default locations of brush clip and skip textures
Default inverse scale factor
PBR properties to use in automatic texturing (for example I personally added transmission to the texture loader)

Adding project settings entries for these should be fairly easy, but I'll have to think on actually making QodotMap respect them - default values in the inspector are driven by class-scope values that get baked into the definition at compile-time, so getting it to work in an elegant fashion will require some setter-driven trickery.
Ideally I'd want to be able to offer overridable defaults for every property in QodotMap, so a more generalized solution is probably in order.
On the PBR properties, that extends beyond the scope of default values and into the realm of the texture loader, so I've opened a separate issue for that: #101

I actually think default directories could be better implemented using EditorSettings.
Currently, all paths are absolute, and they match your (@Shfty 's) hard drive, but not mine. For example: P:/Personal/Godot/Qodot/qodot-example/addons/qodot/example_scenes/1-interactivity/4-advanced-signal-wiring/4-advanced-signal-wiring.map
So to re-build any example maps, I have to use Godot's file picker to choose the same file but with an absolute path that fits my hard drive.
If file path settings are saved with the Editor and NOT with the project, users on multiple computers can download the files and edit them wherever they want on their hard drive, without having to manually change every file path (which is, AFAIK, what you have to do now; not workable for teams).
I also think you can skirt past the class-scope values issue by making all paths RELATIVE to the editor setting. That way, it's okay if the "path" string variable in, say, a QodotMap object is set in stone. The full file path will be added together like this...
# inside a QodotMap
path = "maps/bobomb_battlefield/luigi_land.map"
actual_path_to_load = str(EditorSettings.get_setting("Qodot_asset_directory"), /, path)
# example result: C:/Users/foofoocuddlyfoops/my_supercalifragilisticexpialidocious_godot_thing/maps/bobomb_battlefield/luigi_land.map

To accommodate multiple projects on one computer, perhaps EditorSettings could contain a dictionary that matches each a project directory with an "assets" directory (where Qodot looks for assets). By default, the assets directory and the project directory could be one and the same, encouraging users to store their maps and textures in res://.
Alternatively, just make all of this super simple and make all asset paths relative to res://.
If this is change implemented in an update, it could cause some issues upgrading a Qodot project (like if someone has their files scattered across their hard drive). However, these can be solved by finding all the used .maps and textures and automatically copying them all into organized locations within the res:// folder during the upgrade process.
One final note, I think Trenchbroom's location should also be stored as a separate Editor Setting (rather than baked into the definition of an FGD asset) for similar usability reasons.


Autorefresh for tx so that pure and new msigs apprear without a manual refresh

After implementing polling, unlike subscriptions, we now have to poll (for 1min) the new multisigs and proxies, after certain transactions to make sure the UI auto-refreshes.

Somehow the even extrinsic success isn't fired.. I'll ask the chopsticks team.
Transaction status: Ready
useSigningCallback.tsx:22 Transaction status: Broadcast
useSigningCallback.tsx:22 Transaction status: Finalized
useSigningCallback.tsx:87 Finalized block hash 0xdfd2e17fe46defa98bfc6b6e438de0530b241075593bbfa5fe8fe69b48e9a26f

This ias What happens in tests as well that I can't reproduce. I'll manage

Thanks @asnaith it should be fixed now.

Ah thanks, there's still quite some cleanup to do in this PR, I left some log and comments.


Added recipientfilter limit (2048 characters)

SEE working on Premier support ticket

Docs Build status updates of commit e0bb579:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/New-DynamicDistributionGroup.md
:white_check_mark:Succeeded
View (exchange-ps)

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

Docs Build status updates of commit 1959ef1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/New-DynamicDistributionGroup.md
:white_check_mark:Succeeded
View (exchange-ps)

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


Build twenty-twenty for GLTF

We use the 20/20 crate to do visual regression testing on our frontend, our CLI, and our backend. 20/20 works by comparing two PNGs or two h264 frames, and checking their visual similarity is above some configurable threshold (e.g. 99% similar).
This crate works very well, especially because when it detects a change, it's easy for a programmer to visually compare the images and see what's gone wrong. But it has some problems:

False positives (e.g. the anti-aliasing settings of the grid change, causing every pixel along the grid to be slightly different, dropping the similarity threshold below 99%)
False negatives (e.g. a shape has lots of complicated internal geometry which is hidden from the camera by an occluding face, and when it changes, the camera cannot see it)

We have many concrete examples of the former (everyone has a story about "oh the engine changed rendering slightly, someone needs to update all the frontend snapshots"). An example of the latter just happened, where @benjamaan476 wants to test an engine change which adds internal edges to a model. Because the edges are internal, they can't be seen by the camera and 20/20 is useless. But the edges matter for future applications, and their existence should be tested.
Proposed solution
20/20 checks our model geometry, rendered visually. I think we need a second library for checking model geometry, rendered textually. We could export the model in some text format (e.g. our GLTF) and check it against the expected GLTF.
This approach has a few problems:

There might be many possible ways to describe the same geometry with different GLTFs

A trivial example is outputting a degree of either 0 or -0, this is a change in text with no actual meaningful difference in geometry
Other trivial example: unordered maps/sets being output to text in different orders
There might be many ways to describe the same geometry, e.g. whether to represent a straight line as Curve::Polynomial{degree: 1} or Curve::StraightLine
We should design the assert_gltf function to understand these equivalences and not worry about them, just like doing assert_eq on two HashMaps in Rust doesn't care about the ordering of items.

It's not really clear how to understand the difference between two complicated GLTF files, they're not as intuitive as looking at two pictures.

So I think this would be a complement to 20/20, not a replacement.

We could call the library "xray_specs" because they let you see internal geometry that not even 20/20 vision can :)

100%. I've always asserted that any visual check of our models should be of the actual rendered geometry due to various factors.
Unfortunately I don't believe this is a task to focus on at the moment. We have higher priority items like making modeling-app able to pump KCL to the backend even faster than we do now.
A short term solution would be to use better computer vision techniques, such as not basing our comparisons on raw pixel colors, but instead their "color distance"  https://en.wikipedia.org/wiki/Color_difference (preferably something from the CIE color space), and downscaling to reduce comparing minute details (which is what neural networks do).

Yeah, not saying we need to do it now, clearly 20/20 works well enough for most cases. But I wanted to write it down for the future.


Refactor Application To Include Redux!

We want to refactor the entire application to include redux, this is a big task but we should be able to make this work!

We will use the Redux Toolkit not the normal redux core (https://redux-toolkit.js.org/)
We won't be using hooks because this will take longer

More issues may be posted but this issue thread will be the main location to talk about the refactor. Documentation is linked above.

This was finished and merged into master.


Error on run : Absent Code attribute in method that is not native or abstract in class file javax/ws/rs/core/Application

Hi,
in one of my projects I have this error :
[INFO] --- jaxrs-analyzer-maven-plugin:0.12:analyze-jaxrs (default) @ test ---
[INFO] analyzing JAX-RS resources, using Swagger backend
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.477 s
[INFO] Finished at: 2017-02-01T12:53:44+01:00
[INFO] Final Memory: 23M/206M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.sebastian-daschner:jaxrs-analyzer-maven-plugin:0.12:analyze-jaxrs (default) on project test: Execution default of goal com.sebastian-daschner:jaxrs-analyzer-maven-plugin:0.12:analyze-jaxrs failed: An API incompatibility was encountered while executing com.sebastian-daschner:jaxrs-analyzer-maven-plugin:0.12:analyze-jaxrs: java.lang.ClassFormatError: Absent Code attribute in method that is not native or abstract in class file javax/ws/rs/core/Application
[ERROR] -----------------------------------------------------
[ERROR] realm =    plugin>com.sebastian-daschner:jaxrs-analyzer-maven-plugin:0.12
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/C:/Users/mat/.m2/repository/com/sebastian-daschner/jaxrs-analyzer-maven-plugin/0.12/jaxrs-analyzer-maven-plugin-0.12.jar
[ERROR] urls[1] = file:/C:/Users/mat/.m2/repository/com/sebastian-daschner/jaxrs-analyzer/0.12/jaxrs-analyzer-0.12.jar
[ERROR] urls[2] = file:/C:/Users/mat/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import  from realm ClassRealm[maven.api, parent: null]]
[ERROR]
[ERROR] -----------------------------------------------------
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException
My pom.xml import that dependencies :

I'm doing something wrong?
Thanks a lot in advance!

The problem is in the pom.xml
<dependency>
      <groupId>javax</groupId>
      <artifactId>javaee-web-api</artifactId>
      <version>6.0</version>
      <scope>provided</scope>
</dependency>

I replaced javaee-web-api with javaee-api:
<dependency>
      <groupId>javax</groupId>
      <artifactId>javaee-api</artifactId>
      <version>6.0</version>
      <scope>provided</scope>
</dependency>

Now the build is working!

Great you figured it out! Thanks for sharing, yes the Analyzer assumes that the Java EE 7 API is being used.


Jailbreak software in Emulator?

So I was gonna install Orbital to try to jailbreak, but it was complicated, so I wonder if I can jailbreak the PS4 in the emulator, so is it possible to jailbreak in the Emulator? Thanks.

Yes, Orbital runs the entire PS4 CPU software stack. Any vulnerability there that is exploitable in physical PS4 machines can be exploited in Orbital's virtual PS4 machines.


Agent not recognized when running evaluate

Hi, I could run the trainnning of ma2c on large grid (for 5 days of trainning). But now, I want to evaluate it.
When I run this command:
python main.py --base-dir test_dir evaluate --agents ma2c --evaluate-seeds 3
I got the following error:

[ERROR] Evaluation: ma2c does not exist!

Of course, the folder ma2c really not exists in test_dir.
What have I done wrong? could you help please?

The evaluation path should match your training path. Say if base-dir=/xx/test_dir in your training (and the trained model is stored under /xx/test_dir/model), please rename test_dir as ma2c and pass base-dir=/xx, agents=ma2c in your evaluation. Alternatively, you can modify main.evaluate_fn to import an arbitrary path.

Thank you. But I will add some tip to your answer. The checkpoints files should be directly put inside ma2c  but not in ma2c/model and we need to add the configuration file .ini inside ma2c to.

Sorry for the confusion. Now you can pass ma2c as it is, i.e., .ini under ma2c/data and model files under ma2c/model.


Unread/alert badge showing erroneously

Describe the bug
Some apps in the dock have unread/alert badges showing when there are no messages/alerts/unreads in the app. A screenshot of what I'm seeing is shown below.
What did you expect to happen?
Badges should only be shown when the app has something to report.
Output of rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: last run 16h ago
Deployments:
  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:gts
                   Digest: sha256:37982919f241d6b3882e1d4b2c03df5f8b4102040c92e0288ffee60292cfdaf8
                  Version: 39.20240627.0 (2024-06-27T15:18:35Z)
                     Diff: 58 upgraded

● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:gts
                   Digest: sha256:c192a8306619c0b83daf9bb7d03168bfc2c506c0005f5cd6ea7c8db7e6383c50
                  Version: 39.20240624.0 (2024-06-25T03:10:58Z)

Output of groups
fonnesbeck wheel

Extra information or context
Here is what I'm seeing:

Yet, for both Slack and Spotify there are no messages, unread items, direct messages, etc. Restarting the app has no effect on this behavior.

After restarting the system, the badge for Slack has cleared but the Spotify badge persists.

I've seen this a few times, not sure what causes it.

Even logging out of Spotify does not clear it, so definitely not associated with an alert.

Looks like this is a long-standing issue: https://www.reddit.com/r/gnome/comments/11s6pej/how_to_disable_notification_dotsbadges_in_the_dock/?rdt=45894
Is there a setting for simply turning them off globally?


small fixes

-remove double viewDidLoad
-disable cameraSwitchButton until the transition between cameras is
finished to avoid crash if the user spams the button

Thanks for this! By the way, with git and GitHub, you don't have to close PR's & create new PRs in a new branch to make a change. If you make new commits to the existing branch and push those up, the PR will automatically consider those. You can even squash/rebase multiple commits if your intention is to keep history clean :smile:

Oh I didn't know that!
Thanks for the tips, I appreciate!  :)


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 1172 ms

Resolved: Bofrost.de performance has improved in f71efb6 after 8 minutes.


Bring nostrify to npm also

I would like to suggest to include @nostrify/nostrifyin npm repository.
Always I try to update @nostrify/nostrify using npm install @nostrify/nostrify@latest --save it brokes.
When I try to auto update angular and it dependencies by using ng update it brokes when trying to update @nostrify/nostrify, so I must remove the package always I need to update the frameworks libraries and then reinstall.
File .npmrc is included and configured, but these errors keep happening.

The problem with npm is that I need to add a build step. With jsr I can push my TypeScript code directly to jsr and it "just works". I'm using jsr specifically because I don't want that extra complexity.
I would encourage you to give Deno a try. It's made by the creator of Node, and as of the recent 2.0 release I would say it's finally "better" than Node: https://deno.com/blog/v2.0 I think Deno and jsr are the future of JavaScript, so I am wanting to move forwards not backwards.

You look decided into this.
I believe a in retrocompatible way  to move, ng update of angular does not make a good work in auto update projects with cross repository, or maybe I have missed something.
I believe most people and enterprises will migrate from node/npm slowly to jsr/deno, to keep my retrocompatible way  to move, I ask you: is no problem for you if I fork this project and publish in npm with my custom library contexts (@belomonte) so I can point this as my dependency and not something in jsr?

I ask you: is no problem for you if I fork this project and publish in npm with my custom library contexts

Sure, that's no problem.

I believe a in retrocompatible way to move, ng update of angular does not make a good work in auto update projects with cross repository, or maybe I have missed something.

I was thinking we should create an issue in Angular or Deno to see if they can solve the problem.
But then I looked at ng update and I'm simply trying to understand it... if I understand correctly, this is not a package manager? However, it uses a package manager? So it must detect whether you are using npm or yarn etc automatically. Then it needs to support an infinite number of package managers like pnpm, bun, etc. This is cursed.
It seems like somebody caused themselves pain writing this script instead of letting the package manager do it. And by depending on it you are "locked in" to it. Free your chains. :joy:

You're right. I'll see if there is no issue in angular about it and open it, I believe they are using npm to install the packages but for some reason they don't read .npmrc configs.
About ng update:
It update the new angular packages, update libraries and change your code to keep it compatible. It also recommend migrations to new angular content. Angular have a update checklist to help update things that ng update can't do: https://update.angular.dev/
Thank you for your time.