FEZ-FNA fails with FNADroid at GetLocalSaveFolder

Should be patchable via FEZMod.
E/mono    (24093):
E/mono    (24093): Unhandled Exception:
E/mono    (24093): System.TypeInitializationException: An exception was thrown by the type initializer for FezGame.Program ---> System.TypeInitializationException: An exception was thrown by the type initializer for Common.Util ---> System.NotImplementedException: Unhandled SDL2 platform!
E/mono    (24093):   at Common.Util.GetLocalSaveFolder () [0x00000] in <filename unknown>:0
E/mono    (24093):   at Common.Util..cctor () [0x00000] in <filename unknown>:0
E/mono    (24093):   --- End of inner exception stack trace ---
E/mono    (24093):   --- End of inner exception stack trace ---
E/mono-rt (24093): [ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: An exception was thrown by the type initializer for FezGame.Program ---> System.TypeInitializationException: An exception was thrown by the type initializer for Common.Util ---> System.NotImplementedException: Unhandled SDL2 platform!
E/mono-rt (24093):   at Common.Util.GetLocalSaveFolder () [0x00000] in <filename unknown>:0
E/mono-rt (24093):   at Common.Util..cctor () [0x00000] in <filename unknown>:0
E/mono-rt (24093):   --- End of inner exception stack trace ---
E/mono-rt (24093):   --- End of inner exception stack trace ---
I/Zygote  (  311): Process 24093 exited cleanly (1)
I/ActivityManager( 1243): Process com.angelde.fnadroid (pid 24093) has died

After trying to patch it, it crashes somewhere else: EasyStorage.dll.
I doubted that I'd ever need to patch that dll, but well, time to prepare Travis CI for it...
(12:49:12.753) [FEZMod] JustAnotherFEZMod (FEZMod) 0.3a8
(12:49:13.021) [FEZDroid] Checking if running in Android
(12:49:13.024) [FEZDroid] Android mode engaged!
(12:49:13.069) [FEZMod] Handling FEZMod PreInitialize crash...
(12:49:13.213) [FEZMod] System.TypeInitializationException: An exception was thrown by the type initializer for EasyStorage.PCSaveDevice
  at (wrapper managed-to-native) System.Reflection.MonoField:SetValueInternal (System.Reflection.FieldInfo,object,object)
  at System.Reflection.MonoField.SetValue (System.Object obj, System.Object val, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0
  at System.Reflection.FieldInfo.SetValue (System.Object obj, System.Object value) [0x00000] in <filename unknown>:0
  at FezGame.Mod.FEZMod.PreInitialize () [0x00000] in <filename unknown>:0
  at FezGame.Mod.FEZMod.PreInitialize (System.String[] args) [0x00000] in <filename unknown>:0
  at FezGame.Program.Main (System.String[] ) [0x00000] in <filename unknown>:0
(12:49:13.219) [FEZMod] System.NotImplementedException: Unhandled SDL2 platform!
  at EasyStorage.PCSaveDevice.GetLocalSaveFolder () [0x00000] in <filename unknown>:0
  at EasyStorage.PCSaveDevice..cctor () [0x00000] in <filename unknown>:0


⚠ Bofrost.be has degraded performance

In c4ab76e, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1553 ms

Resolved: Bofrost.be performance has improved in f09491a after 40 minutes.


New release to fix build of reagents?

Now that multicore is closer to becoming reality (https://github.com/ocaml/ocaml/pull/10831) it'd be good to be able to easily install/use the rest of the libraries around it.
https://github.com/ocaml-multicore/reagents/issues/25 says a new kcas is needed to build, and I confirm that is still the case with latest OCaml 4.12.0+domains+effects and the multicore opam repo.
opam remote -v
[NOTE] These are the repositories in use by the current switch. Use '--all' to see all configured repositories.

<><> Repository configuration for switch 4.12.0+domains+effects <><><><><><><><>
 1 multicore git+https://github.com/ocaml-multicore/multicore-opam.git
 2 default   https://opam.ocaml.org

By default you get a compile error like this (if you install the missing jbuilder dependency):
#=== ERROR while compiling reagents.0.3.0 =====================================#
# context     2.1.1 | linux/x86_64 | ocaml-variants.4.12.0+domains+effects | git+https://github.com/ocaml-multicore/multicore-opam.git
# path        /var/tmp/edwin-caches/.opam/4.12.0+domains+effects/.opam-switch/build/reagents.0.3.0
# command     /var/tmp/edwin-caches/.opam/opam-init/hooks/sandbox.sh build jbuilder build -p reagents -j 8
# exit-code   1
# env-file    /var/tmp/edwin-caches/.opam/log/reagents-112796-f96fc6.env
# output-file /var/tmp/edwin-caches/.opam/log/reagents-112796-f96fc6.out
### output ###
# [...]
#       ocamlc reagents/.reagents.objs/reagents__Offer.{cmo,cmt} (exit 2)
# (cd _build/default && /var/tmp/edwin-caches/.opam/4.12.0+domains+effects/bin/ocamlc.opt -w -40 -g -bin-annot -I reagents/.reagents.objs -I /var/tmp/edwin-caches/.opam/4.12.0+domains+effects/lib/kcas -I /var/tmp/edwin-caches/.opam/4.12.0+domains+effects/lib/lockfree -no-alias-deps -open Reagents__ -o reagents/.reagents.objs/reagents__Offer.cmo -c -impl reagents/offer.ml)
# File "reagents/offer.ml", line 42, characters 17-28:
# 42 |   let get_id r = Kcas.get_id r
#                       ^^^^^^^^^^^
# Error: Unbound value Kcas.get_id
#     ocamlopt reagents/.reagents.objs/reagents__Offer.{cmx,o} (exit 2)
# (cd _build/default && /var/tmp/edwin-caches/.opam/4.12.0+domains+effects/bin/ocamlopt.opt -w -40 -g -I reagents/.reagents.objs -I /var/tmp/edwin-caches/.opam/4.12.0+domains+effects/lib/kcas -I /var/tmp/edwin-caches/.opam/4.12.0+domains+effects/lib/lockfree -no-alias-deps -open Reagents__ -o reagents/.reagents.objs/reagents__Offer.cmx -c -impl reagents/offer.ml)
# File "reagents/offer.ml", line 42, characters 17-28:
# 42 |   let get_id r = Kcas.get_id r
#                       ^^^^^^^^^^^
# Error: Unbound value Kcas.get_id

The workaround mentioned in the above issue still works:
opam pin add kcas --dev-repo

Could you make a new release to allow these to be able to installed/built together?

Thanks for the bug report. kcas and reagents are not actively maintained now as the multicore team does not have the resources to do so. We will have to come back to this after the 5.00 release.

I believe this is now resolved with 0.1.5 release in opam.


Working with EIA data in parquet

I am trying to load eia data (such as the eia 923 boiler fuel data) into a dask dataframe after running epacems_to_parquet, but it looks like the only data in my parquet directory is the hourly epacems data.
I downloaded the pudl-eia860-eia923-epacems.tgz file from zenodo and successfully ran epacems_to_parquet datapkg/pudl-data-release/pudl-eia860-eia923-epacems/datapackage.json to create a parquet db of the epacems data.
Do I need to run a separate process on the epacems datapkg to convert the eia data to sqlite and then load it into a dataframe from sqlite? e.g.
datapkg_to_sqlite datapkg/pudl-data-release/pudl-eia860-eia923-epacems/datapackage.json
Do I need to separately download pudl-eia860-eia923.tgz and then run the datapkg_to_sqlite on that datapackage?

Sorry, we clearly need to document all this better.
The epacems_to_parquet script only converts the one big table: hourly_emissions_epacems which has nearly a billion records in it into the Parquet format. The other data (EIA 860/923) will need to be loaded into the SQLite database using datapkg_to_sqlite, using the data package that does no contain EPA CEMS data.
For the sake of simplicity, even though it's a lot of data, I would recommend just downloading the whole archive from Zenodo and running the load-pudl.sh script, which will load absolutely everything for you.

Thank you!


Not working with jsPDF (after build)

Steps to reproduce
i transfer project from vite to farm, it working nicely under vite.
Create new farm project
yarn create farm // vue program
yarn add jspdf // version<EMAIL_ADDRESS>npm link https://www.npmjs.com/package/jspdf
code like this:
import { jsPDF } from "jspdf"; const doc = new jsPDF();
put at any page, it runs no problems under dev mode.
but if you yarn build,  the page can't open.
web browser err code:
Uncaught TypeError: Cannot read properties of undefined (reading 'prototype')     at oe (index_1d3b.aecb47d5.js:18700:32)     at index_1d3b.aecb47d5.js:18706:16     at e17eb7d5 (index_1d3b.aecb47d5.js:18712:6)     at _.require (index.html:5:37090)     at 87817ef5 (index_ec41.a0d71309.js:1:905)     at _.require (index.html:5:37090)     at badfa50a (index_ec41.a0d71309.js:1:3550)     at _.require (index.html:5:37090)     at 89380c7c (index_ec41.a0d71309.js:1:2267)     at _.require (index.html:5:37090)
my testing page like this:

What is expected?
work normally
What is actually happening?
the page down.
System Info
System:
    OS: macOS 14.3
    CPU: (8) arm64 Apple M1 Pro
    Memory: 109.25 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.9.0 - /usr/local/bin/node
    Yarn: 1.22.22 - /usr/local/bin/yarn
    npm: 10.5.0 - /usr/local/bin/npm
    bun: 1.0.20 - ~/.bun/bin/bun
  Browsers:
    Edge: 123.0.2420.53
    Safari: 17.3

Any additional comments?
No response

I'll take a look


Cannot run sea-orm-cli with feature codegen without sqlite as a dependency

Description
I cannot run sea-orm-cli with feature codegen without sqlite as a dependency. I do not want to pull in sqlite, I am using codegen with postgres. There is no way to remove the dependency.
Steps to Reproduce
Add sea-orm-cli to any crate with feature codegen.
Look at cargo.lock
Expected Behavior
I want to be able to deselect the sqlx-sqlite dependency.
It stems from the feature dependency on sea-schema:
codegen (default)
sea-orm-codegen (default)
sea-schema/sqlx-all (default)

Yeah, I've already encountered this same issue: #2225


merge: dev to master

I will correct the readme.

We'll address the Node version issue causing errors during the GitHub build shortly.
CI / Build, lint, and test on Node 10.x and ubuntu-latest
CI / Build, lint, and test on Node 12.x and ubuntu-latest
CI / Build, lint, and test on Node 14.x and ubuntu-latest


Fix: CVE-2020-26235 for the library

Fixes #57 for the rustube library.

Hey @gokberkkocak, thanks for the PR!


touching up the wording on the main page

Monero is secure
Do we really want the first sentence about the security of Monero to include "extremely difficult to hack and steal your funds. "  To me that doesn't sound safe for large amounts if it's only "extremely difficult"... and why mention "hack" and "steal" at all?  Further, if you are trying to define "decentralized cryptocurrency" the definition is absolutely NOT "extremely difficult to hack and steal your funds.".  You could say the same of cash in a bank vault, an ATM machine, a centralized currency, or the safe in my basement...  Those are all "extremely difficult to hack and steal" from.  It seems to me we should be explaining what decentralized cryptocurrency is and perhaps state it's the safest method known to mankind to store value, outside of Fort Knox.  Not that its just hard to hack and steal.
Monero is fungible - if we're going to say it's untraceable above, we may as well remove the whole "In its current state, it is extremely unlikely that Monero will ever be..." and just bluntly state that it will never be blacklisted due to previous association.  Also, very few people know what fungible even means, so I have added the definition so people know what they're reading.

I made the suggested changes.
I also took out the part referencing "mnemonic seeds" as I understand now the intention is to keep things as easy to understand as possible on the main page.  So that edit just replaces a comma with the word "to", which is more grammatically correct.

Monero is a decentralized cryptocurrency meaning **it is** secure digital cash powered by a network operated by its users.
You are the bank - no one knows how much you have or how you spend it.
We already have a statement about this in the top paragraph. I don't believe using the same wording is ideal.
This means no one can tell one Monero from another Monero and therefore your funds can't be blacklisted by exchanges or vendors.
I would argue that due to its association in previous transactions is a key message of the original statement and that removing it would make the intended message less obvious.

Removed some of my proposed changes.  Now this commit basically just changes the part about hacking and stealing into a useful description of decentralized crypto.


Improved error handling

For now, without unit tests. These will be added later.

Added unit tests

Thanks for the fixes @zivnevo ! I will give them a try by trying to integrate directly with this branch. I will let you know if there are any issues with anything that would be blocking. I am not sure I finish this today (Tuesday), but tomorrow the latest I should be back with success report or with a list of required corrections.

I was able to partially integrate with this branch and I see the library working correctly in simple scenarios (I haven't checked anything more complex yet).
As this PR is really big and almost impossible to review, I propose the following:
* merge it as it is,

* address potential issues in separate, smaller PRs if needed.

Does it sound ok?

Yes, this sounds good. I opened issues to address most of the comments. If you think I missed something, feel free to open a new issue.


Cannot read property 'injectionFactories' of undefined

I upgrade to 1.3.10 and I started getting this error when I start my application
TypeError: Cannot read property 'injectionFactories' of undefined
at Object.initialize (flash-messages.js:22)
at ember.debug.js:4820
at ember.debug.js:4849
at Object.visit [as default] (ember.debug.js:55496)
at DAG.topsort (ember.debug.js:2513)
at _emberRuntimeSystemNamespace.default.extend._runInitializer (ember.debug.js:4848)
at _emberRuntimeSystemNamespace.default.extend.runInitializers (ember.debug.js:4809)
at _emberRuntimeSystemNamespace.default.extend._bootSync (ember.debug.js:4710)
at _emberRuntimeSystemNamespace.default.extend.domReady (ember.debug.js:4611)
at Object.Backburner.run (ember.debug.js:688)onerrorDefault @ ember.debug.js:31563exports.default.trigger @ ember.debug.js:53628(anonymous function) @ ember.debug.js:54877Queue.invoke @ ember.debug.js:327Queue.flush @ ember.debug.js:391DeferredActionQueues.flush @ ember.debug.js:192Backburner.end @ ember.debug.js:570Backburner.run @ ember.debug.js:692Backburner.join @ ember.debug.js:712run.join @ ember.debug.js:20709(anonymous function) @ ember.debug.js:20772fire @ jquery.js:3099self.fireWith @ jquery.js:3211jQuery.extend.ready @ jquery.js:3417completed @ jquery.js:3433
ember.debug.js:4719Uncaught TypeError: Cannot read property 'injectionFactories' of undefined

I'm getting the same error. Fixed when downgrading to 1.3.9

Fix coming, thanks for reporting!

Please use 1.13.11, sorry for the trouble!

No problem, thanks for the quick turnaround on the fix!

I'm getting this on 1.13.11 too?

I still got this error with 1.13.11, I needed to modify my environment.js with flashMessageDefaults: {} otherwise it crashes in the initializer.

Sorry about that @Padchi and @visoft, I have another PR up – https://github.com/poteto/ember-cli-flash/pull/145

Can you give 45b89f8 a try?


Feature Request - Display Multiple sensors on one button

Hi there,
thank you for your incredible work.
I am primarily using this Plugin to display sensor states from my home-office on my streamdeck.
What I absolutely love the this plugin so far is the fact that I can display a sensor value and can call different actions with the short and long press buttons, all on the same streamdeck key.
However I would love the possibility to display more than just one sensor value (entity) per key.
In my specific example, I have a temp, TVOC, CO2, and PM2.5 sensor in my home-office.
I also have an air-purifier and HVAC, both integrated in homeassistant.
I would love to display both the TVOC and PM2.5 values on a button where I can then toggle my air-purifier. And on a second button I'd love to display my Temp and CO2 and toggle the HVAC.
One possible implementation for this could be by leveraging the existing "Custom labels" section, or adding a new "Advanced labels" section to display multiple sensors value.
For example In my current setup I use it like this:

But I could imagine a configuration that looks like this:

Which would look like this on the button:

What do you think about this?
Would you be open to a PR adding this or should I fork?
Thanks a mil in advance

Hi cedi,
that sounds like a nice feature. I thought of something similar, but never managed to implement it. Of course, i would very much appreciate your help and a pull request.
Thanks in advance :)


Homepage updates

Added helptext on submission tabs
Empty-argument checks
Link to CISA best-practices doc

Discussed and merged


[network] added NetworkContext for logging

Motivation
Consistent logging across all networking logs to keep track of a tuple
of NetworkId, RoleType, PeerId.  This will also consolidate having to
pass 3 different types all around.
Caveats

This currently doesn't do anything at the noise / protocol / wire / transport level logging, and handles logging at mostly the (Fill-in)Manager level.

Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
RUST_LOG=info cargo x test -p network e.g.->
INFO 2020-06-09 19:54:57 network/src/connectivity_manager/mod.rs:328 [Validator,validator,1d0901de] Create dial future: peer: 4be09508, at address: /ip4/<IP_ADDRESS>/tcp/9090, after delay: 100ms
INFO 2020-06-09 19:54:57 network/src/connectivity_manager/mod.rs:340 [Validator,validator,1d0901de] Dial future: dialing peer: 4be09508, at address: /ip4/<IP_ADDRESS>/tcp/9090, after delay: 100.000611ms
INFO 2020-06-09 19:54:57 network/src/connectivity_manager/mod.rs:351 [Validator,validator,1d0901de] Dialing peer: 4be09508, at addr: /ip4/<IP_ADDRESS>/tcp/9090
INFO 2020-06-09 19:54:57 network/src/connectivity_manager/mod.rs:493 [Validator,validator,1d0901de] Failed to connect to peer: 4be09508 at address: /ip4/<IP_ADDRESS>/tcp/9090; error: IO error: connection refused

Related PRs
Adding networkId in the first place: https://github.com/libra/libra/pull/4088

:umbrella: The latest upstream changes (presumably 0b969e533d0be00be7e8065656df2c2df03ca48e) made this pull request unmergeable. Please resolve the merge conflicts.

the rest of the logging and context propagation looks good! at some point (probably not now) we should investigate better logging macros for structured logging but this is about as good as we're gonna get : )

the rest of the logging and context propagation looks good! at some point (probably not now) we should investigate better logging macros for structured logging but this is about as good as we're gonna get : )

Yeah, figured this is just round one, some day we'll come back and make it better

:hourglass: Testing commit 1fb9ad0089d91d05e5455f1b5db4cb54814ff620 with merge 0d3d7bffaacc70ae855129e3626e73d6200f8d62...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: phlip9
Pushing 0d3d7bffaacc70ae855129e3626e73d6200f8d62 to master...


Bug: v12.0.0 Relaychain node (Kusama node) uses the default path for db also if --base-path flag is used

Hello Basilisk Team,
it seems that with v12.0.0 the relaychain node uses the default path for db instead of the path in --base-path flag. This is causing the relaychain node syncing from scratch.
I tried to put --base-path flag also for relaychain node (instead of only for parachain node) but the result is the same
Waiting for your kind reply

Solved
For some reason the relaychain database migrated from /database/polkadot/chains/ksmcc3 to /database/chains/ksmcc3


[Task]: Remove BeamSummit Banner from Website

What needs to happen?
There is a "BeamSummit" Banner on beam.apache.org which announced the Beam Summit which has passed.
Please remove this banner.
Looks like was created in this PR:  https://github.com/apache/beam/commit/4fa5c43fa89c6c6be4cbaca94f851c56f77335c0 ...  Looks like that might be just the Playground.  So, more to look at for the 'regular' website.
I aim to 'fix' this on the workshop on contributing to OSS on 24 July 2022.  If this is not fixed/closed by then, then anyone please address.
Issue Priority
Priority: 2
Issue Component
Component: website

thanks for filing this. I don't know, but I don't see the banner anymore...

agreed that banner is gone ... but how?  Since we'll want a banner in the future, I'd like to know where/how that was changed, to make it easy for whoever might address in the future.  Let's track that down.

The website banner was removed in 33dc35fd553a02c0be8b9ad183889ee0cf9e620f

Addressed by https://github.com/apache/beam/commit/33dc35fd553a02c0be8b9ad183889ee0cf9e620f

thanks, @alexeyinkin !


As a Project Coordinator, I want to see project revision diffs, so that I can understand what was changed in past revisions

Description:
A component to visualize diffs between project (or form_change) revisions
Acceptance Criteria:
Given I am a CIF project coordinator
When I view a project details
Then I can see a list of revisions for that project
Given I am a CIF project coordinator
When I view the list of revisions on the project details page
Then I can see summary data on each revision
Given I am a CIF project coordinator
When I select a project revision
Then I can see the details of the changes from the previous revision
Development Checklist:

[ ] a cif.get_project_revision_diff(a,b) method that returns an array of changes, organized by form_change
[ ] we can use the same diff toolkit as in CIIP (unless results of UX research point at something else)
[ ] a ProjectRevisionDiff component that fetches the output of that function and displays it

Notes:

For each revision, get the associated form-changes and compute a diff from the JSON
If there is no json field in the previous revision/form_change, we'll need to go back to the previous revision/form_change where it was set to retrieve the previous value

This needs to be split in two issues

@dleard - is this ticket complete with your most recent diff work? Or is this something different?

This is different, the work I did shows the diff when editing a project. This cards is about being able to view diffs between one revision to another

Do we still need this ticket or has it been replaced with the existing tickets that have been created for revisions and amendments?

Hi @pbastia and @nanyangpro - is this ticket still required or has it been replaced by any of the new amendment/revision user stories? If it is still required, I'd like to change it to be captured under amendments/revisions EPIC - thoughts?

I think #920 and #994 cover this ticket, @pbastia?

@nanyangpro not quite, this feature is about showing the diff between 2 arbitrary versions, as an analytics tool. It would be in addition to the 2 cards you linked

Gotcha, thanks for clarifying @pbastia. Since this ticket was created in Jan, and wasn't specifically brought up by the CIF team during my discovering for amendments/revisions, I'm wondering if you still see the need for keeping it?

@LindsayMacfarlane  flagging this card for your review, as per Nan's comment above.

@Dianadec - I feel we can icebox this ticket for now. This was a very early ticket in our development and would be better to validate with CIF if it is required. The functionality currently being built will most likely meet CIFs immediate needs and this may be more of a future need (if at all).

I'm going to remove this ticket from the amendments EPIC as it is not a priority to get this feature working and in the hands of CIF.


Support string in DataChannel.SendMessage

I've tested to implement this somewhat in this draft PR: https://github.com/microsoft/MixedReality-WebRTC/pull/675
Describe the problem
I'm not 100% sure about this, but, once a DataChannel is setup there is these two methods to send raw bytes over the data channel:
SendMessage(IntPtr message, ulong size)
SendMessage(byte[] message)

The only way to send messages right now is using raw bytes, but there should be another alternative according to the RFC (https://tools.ietf.org/html/rfc8831). The RFC states that the Payload Protocol Identifier (PPID) used in the data channel can be used to indicate raw bytes or UTF8 encoded data.
It would be great to have this available in the package as well, and might not be much trouble if the underlying support in the library is already there (hopefully).
Describe the solution you'd like
Overload the SendMessage method with another alternative:
DataChannel.SendMessage(string message)

This would UTF8 encode the message and send it by with the PPID flag.
Describe alternatives you've considered
I see no other way to make this happen, there is no way to send the raw bytes as a UTF8 message since it is set by the underlying protocol, I think?

I've checked the C++ code and found the following in data_channel.cpp

I don't have Visual Studio 2017 (yet) and am not that familiar with C++, but it seems this boolean is what I'm looking for!

Closed issue since the library now supports the flag using the SendMessageEx method and the MessageReceivedEx event.

@torepaulsson would you mind to publish mrwebrtc.dll with that fix ?
I have the same problem you described - the peer I am connecting to doesn't accept blob DataChannel messages from MixedReality-WebRTC 2.0.2 and expects text only
It looks like there is only win32-x64-Debug version published https://dev.azure.com/aipmr/MixedReality-WebRTC-CI/_build/results?buildId=19141&view=artifacts&pathAsName=false&type=publishedArtifacts
Very interested in win32-x64-Release build and failed to build it myself

@mikhaylo1, I'm sorry but I'm not the owner of this repository and unsure how it is published. I've built mine locally instead, it would be great if we could get a official release though. Maybe @djee-ms can help with that, if the release pipeline still functions.

I am looking for Win32 Release build, as far as I see there is only a Release artifact for UWP build generated with that change in DataChannels
@djee-ms Is there any chance to run the pipeline and generate artifacts for the current master repository ?


RT#803875 - Updating section numbers after deletion

More details here: https://github.com/sanger/stan-client/issues/689

Hi @KatyTudor , thank you for testing it,  the recent changes shouldn't be impacting the store functionality.
Also, I just conducted a test on UAT using STAN-1C2ED to create 3 new tubes through the section confirmation operation, and I was able to store them successfully.
From the screenshot provided, it appears that the system it is failing to store one specific labware. Could you confirm if this is the labware you just created within the section confirmation process? Additionally, I noticed that its details are missing from the table.

@sabrine33 sorry for the delay. the screenshot is from testing the deleting of labware, I created the labware on the planning then at confirmation I deleted 1 tube, the section numbering was adjusted after deleting, but when I can to store the labware the deleted/discarded labware was in the list to be stored

@KatyTudor, Should discarded sections or deleted labware in the section confirmation page be present on the print labels page?

@sabrine33 no they shouldn't

@sabrine33 the error is still occuring, deleted tubes are still available to print (first image), and then appear on the "awaiting storage" (second image) and then when I try to store i get the error (last image):

@KatyTudor apologies for the confusion, this is does not seem to be deployed yet on UAT.

@sabrine33 no worries let me know once its updated and I can test


Filter broke get_payments on extensions

added **kwargs to the function params

where and how does it break? @jackstar12

where and how does it break? @jackstar12

Here for example: https://github.com/lnbits/lndhub/blob/47ca0ac1b952dde6e4304264df1d680bd025f693/views_api.py#L121
limit and offset are not parameters of get_payment

ok so we should probably, introduce a /v2/ of the api, use that in frontend, and revert the code to the original /v1/
@jackstar12

ok so we should probably, introduce a /v2/ of the api, use that in frontend, and revert the code to the original /v1/ @jackstar12

I could include that in https://github.com/lnbits/lnbits/pull/1613

V2 for entire api? Sounds dramatic, surely this can be fixed without?

Disagree, we should not make a new endpoint but fix the old one can keep it 100% backwards compatible. That was the goal of the Filter PR but seems like it didn't work. Lets fix it.

Adding **kwargs to the params, doesn't change anything at all, it just makes the error go away. The bug is actually in the lndhub extension that needs to use Filters.

Here is the issue we need to fix: https://github.com/lnbits/lndhub/issues/7

Disagree, we should not make a new endpoint but fix the old one can keep it 100% backwards compatible. That was the goal of the Filter PR but seems like it didn't work. Lets fix it.

@callebtc 100% backwords compatibility wont really be possible for https://github.com/lnbits/lnbits/pull/1613 because it changes the response model so I think keeping the new stuff on a seperate endpoint for now should be the easisest and safest (there might be more stuff that depends on the current api). At some point the old one can be removed / deprecated

A vote for new api endpoint, then when people complain we point to the pagination endpoint

A vote for new api endpoint, then when people complain we point to the pagination endpoint

Agreed, I assumed the response remains the same. The endpoint should either not change or be 100% backwards compatible. So let's do a separate endpoint for paginated payments and restore the functionality of the old endpoint to exactly the same as it was before.


content: ESP-NOW reliability in indoor and outdoor environment

Added two articles:

Data transmission reliability over ESP-NOW protocol in indoor environment (blog/reliability-esp-now)
Exploring wireless communication protocols on ESP32 platform for outdoor applications (blog/esp-now-for-outdoor-applications)

Added three autors:

Michal Kubaščík (kubascik-michal)
Ján Šumský (sumsky-jan)
Samuel Gancarčík (gancarcik-samuel)

Thank you very much, @kubascikmichal for your contribution!
We will review your article and suggest changes if needed.


flow check prints lots of /tmp/flow/flowlib_* output

Executing flow check (v0.20.1) produces the following unwanted output. Valid Flow warnings and errors are printed afterwards but it's a lot of clutter to have to parse.
(node:13717) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
/tmp/flow/flowlib_2fd4e8d8/dom.js { dev: 64513,
  mode: 33188,
  nlink: 1,
  uid: 1000,
  gid: 1000,
  rdev: 0,
  blksize: 4096,
  ino: 50856059,
  size: 36261,
  blocks: 72,
  atime: 2016-06-12T02:27:47.000Z,
  mtime: 2016-06-12T02:27:47.000Z,
  ctime: 2016-06-12T02:27:47.217Z,
  birthtime: 2016-06-12T02:27:47.217Z }
/tmp/flow/flowlib_2fd4e8d8/node.js { dev: 64513,
  mode: 33188,
  nlink: 1,
  uid: 1000,
  gid: 1000,
  rdev: 0,
  blksize: 4096,
  ino: 50856060,
  size: 40743,
  blocks: 80,
  atime: 2016-06-12T02:27:47.000Z,
  mtime: 2016-06-12T02:27:47.000Z,
  ctime: 2016-06-12T02:27:47.277Z,
  birthtime: 2016-06-12T02:27:47.277Z }
/tmp/flow/flowlib_2fd4e8d8/cssom.js { dev: 64513,
  mode: 33188,
  nlink: 1,
  uid: 1000,
  gid: 1000,
  rdev: 0,
  blksize: 4096,
  ino: 50856058,
  size: 8947,
  blocks: 24,
  atime: 2016-06-12T02:27:47.000Z,
  mtime: 2016-06-12T02:27:47.000Z,
  ctime: 2016-06-12T02:27:47.341Z,
  birthtime: 2016-06-12T02:27:47.341Z }
/tmp/flow/flowlib_2fd4e8d8/bom.js { dev: 64513,
  mode: 33188,
  nlink: 1,
  uid: 1000,
  gid: 1000,
  rdev: 0,
  blksize: 4096,
  ino: 50856049,
  size: 8938,
  blocks: 24,
  atime: 2016-06-12T02:27:47.000Z,
  mtime: 2016-06-12T02:27:47.000Z,
  ctime: 2016-06-12T02:27:47.401Z,
  birthtime: 2016-06-12T02:27:47.401Z }
/tmp/flow/flowlib_2fd4e8d8/react.js { dev: 64513,
  mode: 33188,
  nlink: 1,
  uid: 1000,
  gid: 1000,
  rdev: 0,
  blksize: 4096,
  ino: 50856061,
  size: 9835,
  blocks: 24,
  atime: 2016-06-12T02:27:47.000Z,
  mtime: 2016-06-12T02:27:47.000Z,
  ctime: 2016-06-12T02:27:47.465Z,
  birthtime: 2016-06-12T02:27:47.465Z }
/tmp/flow/flowlib_2fd4e8d8/core.js { dev: 64513,
  mode: 33188,
  nlink: 1,
  uid: 1000,
  gid: 1000,
  rdev: 0,
  blksize: 4096,
  ino: 50856057,
  size: 21679,
  blocks: 48,
  atime: 2016-06-12T02:27:47.000Z,
  mtime: 2016-06-12T02:27:47.000Z,
  ctime: 2016-06-12T02:27:47.529Z,
  birthtime: 2016-06-12T02:27:47.529Z }

that's odd, this is a Node error. how are you running flow check?

Sorry for the hassle. My path includes node_modules/.bin. This appears to be the redonk output of the NPM touch package which is a dependency of something else in the project. Not a Flow issue.


New hygiene test - incomplete modeling indicator

https://github.com/edmcouncil/fibo/blob/master/ONTOLOGY_GUIDE.md#t6-partial-modeling suggests that a class with a single subclass MAY indicate unfinished modeling.
The following query finds all such cases:
prefix rdfs:  <http://www.w3.org/2000/01/rdf-schema#>

##
# banner Class with a single subclass may indicate incomplete modeling.

SELECT DISTINCT ?warning ?class2
WHERE
{

  ?class1 rdfs:subClassOf ?class2 .
  FILTER (ISIRI(?class2))
  FILTER (CONTAINS(str(?class2), "edmcouncil"))
  BIND (concat ("WARN: Class ", str(?class2), " has just one subclass.") AS ?warning)
}
GROUP BY ?warning ?class2
HAVING (COUNT(?class1)=1)

See also: https://github.com/edmcouncil/ontology-publisher/issues/20.

Can we find a way to put the output from each test in a separate file, aside from those that we say are ERROR in prod?  This will clutter the results to the degree that I can't sift through them.  I'm sure there are a number of these concepts where we think that FIBO users may extend a given class, but that we have not incorporated.  I would say that the same should be done for the ambiguous definitions, for example.

This doesn't make sense to me at all. Even based on the section in the ontology guide, but I could think about lots of other cases.
BTW that misuses "singleton" which means a class with a single instance not with a single subclass.
BTBTW I made lots of comments on the Ontology Guide - why don't we firm that up before hardcoding hygiene tests based on it?

As for:

Can we find a way to put the output from each test in a separate file, aside from those that we say are ERROR in prod? This will clutter the results to the degree that I can't sift through them. I'm sure there are a number of these concepts where we think that FIBO users may extend a given class, but that we have not incorporated. I would say that the same should be done for the ambiguous definitions, for example.

I think this request should go to @przemekgradzki and perhaps be handled  in https://github.com/edmcouncil/ontology-publisher where the issues with our DevOps process are discussed.

As for:

BTBTW I made lots of comments on the Ontology Guide - why don't we firm that up before hardcoding hygiene tests based on it?

@rivettp, where can I find these comments?
I've just searched for them using github search and was not able to find a single issue there that reports any of them - but I might have missed something.

Shall I then modify the ontology guide so that this test be no longer recommended as a hygiene test candidate?

IMO, a class with a single subclass indicates either unfinished modelling or is a sign of more serious problems. @mereolog, please add this test as WARN.

I disagree @trypuz - to take a real example from a real project - we have class LegalEntity with a single subclass RegulatedEntity which has additional restrictions and properties 9e.g. to regualtions). Are you saying that's unfinished? Has serious problems? Would you also force an additional subclass UnregulatedEntity? IMO that would be wrong from Open World perspective - just because you're not aware of an applicable regulation doesn't mean the entity is unregulated?

FWIW there are over 50 classes in the schema.org class hierarchy with only one subclass.

Further, with FIBO we're trying to be use-case-driven not to provide a complete taxonomic model of the universe. Hence it's quite legitimate not to expand out all possible subclasses. An example of where we went for over-completeness in the past was to model criminal organization (or similar) as part of a complete set of subclasses of organization.

Since this is a rather stale issue now, I going to follow @rivettp view and drop the suggestion of this test from the ontology guide.


Allow importing unquoted strings from JSON

This would be really handy to have, especially in a project I'm working on involving live theme customization, where colors are loaded from JSON generated from the server utilizing a hosted Sass build system.

Implemented in 1.2.


Want to change the UI of the Dinosaur Game!!

Hey @Vishal-raj-1 I would love to change the UI of the dinosaur game along with some background music when the dinosaur hits the obstacle. Could you please assign me this under LGM-SOC'21so that I can enhance its look?

Hey @Vishal-raj-1 I want to work on this issue please assign me if possible under Lgm-soc '21


Strange behavior when returning from CTRL-Z - 5.24.0

I pressed CTRL-Z to drop to shell. Using fg I went back to gdu. I pressed CTRL-Z to drop to shell again, then the following happened:
Just dropping to the shell with CTRL-Z and returning the gdu I can not use the arrows to scroll the tree.
**

**

Moving the mouse keeps appending to the shell:

This happened on Centos 7 inside bash.

entered reset:

gdu  did a rescan but terminal still was not happy.

this situation seems to happen occasionally ?
sometimes i have also encountered https://github.com/dundee/gdu/issues/249#issuecomment-1559684903

tview.Application.Suspend seems not safe (when work with signal SIGTSTP?)

handle screen state by screen.Fini and re-create new screen seems more safer (but it need lots of re-setup;
gocui has a logic layer handle that and user don't have to , but tview seems lack of it )

@yurenchen000 I can replicate it each time. I must just not touch the mouse then it should be fine.

I try it on windows,
didn't encounter the same situation,
but encountered a similar one.

client \ server
ubuntu22 local
ubuntu22/20/18 via ssh
centos7 via ssh

ubuntu22 terminator
Rare
Frequent
❌

win10 cmd
Rare
Frequent
❌

win10 powershell
Rare
Frequent
❌

win10 windows terminal
Rare
Frequent
❌

Client :
OS: win10 22H2 (10.0.19045.2006)
windows terminal: 1.17.11461.0
A temporary workaround here:
// I haven't dig the deep (timing) reason yet
https://github.com/yurenchen000/gdu/tree/feat_ctrl_z_3
can you try if it solved the problem?
// it works on my tests

@yurenchen000 I compiled your test branch. I was not able to trigger the problem anymore.

I just noticed that Windows Terminal updated to 1.17 from last week, and now it is much harder to trigger the issue.

I just noticed that Windows Terminal updated to 1.17 from last week, and now it is much harder to trigger the issue.

It seems that:

terminal via ssh is easier to trigger than in local terminal
open large folder is easier to trigger than small folder
centos is easier to trigger than ubuntu
after fg press ↑ quickly may easier to trigger

I can confirm that after fg press ↑ quickly may easier to trigger

and,
did the workaround avoid it?

Not avoid. Just harder to trigger.

Not avoid. Just harder to trigger.

I didn't trigger again after this temp patch:

A temporary workaround here: // I haven't dig the deep (timing) reason yet https://github.com/yurenchen000/gdu/tree/feat_ctrl_z_3

can you explain how to trigger it (and the environment) ?

I think it's about race condition of

kill (it's async
terminal resume

(so sleep can improve the situation
(I'll try a better way..


Using within typescript project

Thank you for this awesome package, which I'm sure it'll become an important part in every graphql server written in Javascript.
I have a graphql server based on Apollo Server and the whole project is written in TypeScript. For running the server I use ts-node.
The problem I have is when I make a query, I always get 'Query Complexity of 0'. Then I made a custom Typescript module to where I copied the graph-query-complexity code with small modifications regarding only the type definitions. With this module, the Query Complexity is calculated as it should.
I'm not sure if this is a problem of the package or the fact that I'm using Typescript with ts-node.
Any help would be more than welcome.

After doing some more investigation, I found that the problem isn't in using Apollo Server nor in ts-node, but how graphql module is included in the project.
In your module package.json, the graphql module is defined as dependency. My project also has graphql module as dependency and creators of graphql stated that there should be only one graphql module per project. After removing graphql module from your package's node_modules, everything works.
So I recommend that you change graphql moduledependency to peerDependency.

Thanks for reporting and investigating the issue. I just released a new version with that change. Could you check if that solved the problem?

Yes it is solved. Thank you!


How do we get the live-stream video URL Flutter?

Version
v1.2.0
Which operating systems have you used?

[X] Android
[X] iOS

Environment that reproduces the issue
How to get the live stream video URL.
Is it reproducible in the example application?
Yes
RTMP Server
How to get the live stream video URL.
Reproduction steps
How do we get the live-stream video URL?
Expected result
Video URL
Actual result
Video Link
Additional context
No response
Relevant logs output
No response

This package is for publishing a RTMP live stream, not for playing a video.
All you need is a URL and a Stream key. These info are provided by your video server.

How can we test it locally?


Documentation: how it works

There should be a documentation page talking about how Dagger works under the hood. An architecture diagram, core technology, etc.
For example this diagram is from https://sigstore.dev/how-it-works:

I'm imagining a high-level approach where we split this into 3 sections:

What is BuildKit

the BuildKit Crash Course section of my blog post here may be a good reference for how to explain it quickly (though probably don't use Dockerfile as a central example to avoid confusion)
Include a diagram of an LLB DAGs

What is cue/flow

This will reference our current What is CUE? page, but focus more on how cue/flow enables us to create DAGs of tasks that are defined with CUE but implemented using Go
Include a diagram of CUE task DAGs

How do we bridge from the cue/flow DAG -> BuildKit LLB DAG

Include diagram showing the bridge from the cue/flow DAG of the previous example to the LLB DAG from the earlier example.

Basically, the approach here is to progressively introduce concepts and then conclude with how they all connect together. It should be something like a peek under the hood but also doesn't require going into too low-level of detail.
I'll start with creating a skeleton of this approach and placeholder diagrams/explanations.

Moved this back from in progress for now as there are some emergent high priorities (which may also impact what we write in these docs). Will reschedule once there is bandwidth again.

removing @sipsma as assignee since he is working on a few other things right now. @jpadams, Erik offered to help answer questions around buildkit (if needed) whenever we get someone else to work on this.


Fix formatting error in README.md

Came across a rendering issue when reading the README. It seems like a codeblock wasn't closed properly.

I have signed the CLA!


Add dynamic route generation for the js api implementation

In our customer project we need to prefix all sulu api calls with sulu.
This is easily done in the yaml configuration e.g.:
    tailr_failed_queue:
        resource: '@SuluMessengerFailedQueueBundle/Presentation/Controller/Admin'
        type: attribute
        prefix: /sulu/admin/api

Unfortunately the javascript implementation was hardcoded to the specific route.
This MR uses the symfonyRouting service from the fos-jsrouting/router to resolve the given symfony route.

Thanks for the PR.
It indeed makes sense to do so, but I don't seem to get it working:

(same for retry - the fetch one does work)
Even though the routes are available from admin console (after my change):
  tailr.messenger_failed_queue_fetch                   GET        ANY      ANY    /admin/customprefixedroute/api/messenger-failed-queue/{id}
  tailr.messenger_failed_queue_list                    GET        ANY      ANY    /admin/customprefixedroute/api/messenger-failed-queue
  tailr.messenger_failed_queue_requeue                 PUT        ANY      ANY    /admin/customprefixedroute/api/messenger-failed-queue/requeue
  tailr.messenger_failed_queue_retry                   PUT        ANY      ANY    /admin/customprefixedroute/api/messenger-failed-queue/retry

Thanks for the PR.
It indeed makes sense to do so, but I don't seem to get it working:

(same for retry - the fetch one does work)
Even though the routes are available from admin console (after my change):
  tailr.messenger_failed_queue_fetch                   GET        ANY      ANY    /admin/customprefixedroute/api/messenger-failed-queue/{id}
  tailr.messenger_failed_queue_list                    GET        ANY      ANY    /admin/customprefixedroute/api/messenger-failed-queue
  tailr.messenger_failed_queue_requeue                 PUT        ANY      ANY    /admin/customprefixedroute/api/messenger-failed-queue/requeue
  tailr.messenger_failed_queue_retry                   PUT        ANY      ANY    /admin/customprefixedroute/api/messenger-failed-queue/retry

Thanks for the quick response!
Sorry my bad, tbh I only tested it with the fetch route and thought it will work 😂
The issue was that the other route had not set the exposed option in the route configuration.
I hope it will work now 🤞

Oh yeah, looked over that :)
Thanks!


[suggestion] Store chunk list in entry point instead

Chunk names are currently hard-coded into each emitted chunk. With hashed chunk names this means that whenever a chunk updates the parents of that chunk must reference the new chunk name, and then the parents of those parents must do the same, etc. Effectively, all ancestors of a changed chunk must change too.
What if instead the entry point stored a master list of all chunk names, then only the changed chunk + entry point would have to be updated. Faster incremental updates and much more cache friendly.
So instead of the current approach:
// someParentChunk.js
loadScript('someChildChunk.js')

It could be:
// entryPoint.js
var chunkNames = ['someChildChunk.js'];

// someParentChunk.js
loadScript(chunkNames[0])`

Wups, my mistake, this is already done.


update PMP exception handlers to 'fix' config CSRs

This PR adds new functionality to the PMP configuration object to enable generation of a custom PMP fault handling routine, that will loop through each pmpaddr/pmpcfg CSR pair, match up the correct CSRs to the faulting address, then "fix" the configuration settings by enabling the appropriate access permissions.
For example, say pmpaddr0 is set to 0x80002000, and its corresponding 8-bit access configuration fields are set such that the address matching scheme is TOR and all instruction fetches are disabled. If an instruction fetch to 0x80001FFC is made, a PMP fault will occur, and the core will jump to the generated instruction fetch exception handler. Assuming mepc is not modified, after executing the handler the core will jump back to the same address that caused the trap, which means that we will infinitely loop on this instruction fetch until any timeouts.
This approach was chosen to allow forward progress as simply updating mepc within the handler itself is not desirable as there is no good way of knowing if the faulting instruction is compressed or not (which directly translates into whether we add 2 or 4 to mepc), and disabling compressed instructions altogether is not a good strategy either.
There are a few TODO items associated with this PR, mainly that it doesn't quite work with NA4/NAPOT modes yet due to an inconsistency in how addresses are passed in from the command line, this will be addressed in a separate PR.

Please run this change with incisive to make sure the regression is passing
Sun, 26 Apr 2020 20:08:39 INFO parse_pmp_config(pmp_region, pmp_cfg[i]);
|
ncvlog: *E,UNSRFA (xxx/riscv_pmp_cfg.sv,174|43): unsupported ref argument usage because actual argument is not a supported element reference for ref arg.

That is actually an issue with IUS not having support for passing array elements by reference, though it is perfectly valid as per the LRM (we actually removed IUS support from Ibex environment for lack of support of many RTL/DV language features like this).
Should I restructure this to avoid this error?

Please run this change with incisive to make sure the regression is passing
Sun, 26 Apr 2020 20:08:39 INFO parse_pmp_config(pmp_region, pmp_cfg[i]);
|
ncvlog: *E,UNSRFA (xxx/riscv_pmp_cfg.sv,174|43): unsupported ref argument usage because actual argument is not a supported element reference for ref arg.

That is actually an issue with IUS not having support for passing array elements by reference, though it is perfectly valid as per the LRM (we actually removed IUS support from Ibex environment for lack of support of many RTL/DV language features like this).
Should I restructure this to avoid this error?

Yes, I think we should make it work for the mainstream simulators

Yes, I think we should make it work for the mainstream simulators

Got it, will prepare a workaround.

This latest force push contains a workaround to the issue of accessing structs in an array with the ref keyword.
@taoliug - I'm unable to reproduce the error you're seeing, could you see if this workaround is successful with IUS now?

This force push takes into consideration a guideline in the spec that the combination of [W:1,R:0] is reserved for future use and should not be enabled.

Latest force push fixes some merge conflicts introduced by #554.


Parsing "months since ..." dates

Hi,
Following on from #68, it turns out that you can't now parse dates of "months since ..." in the Gregorian calendar:
>>> import cftime
>>> cftime.__version__
'1.6.2'
>>> cftime._dateparse('months since 2000-1-1', 'gregorian')
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
Cell In[17], line 1
----> 1 cftime._dateparse('months since 2000-1-1', 'gregorian')

File src/cftime/_cftime.pyx:98, in cftime._cftime._dateparse()

ValueError: 'months since' units only allowed for '360_day' calendar

Was this intended?
This makes it hard to read datasets like:
	float32 T(T) ;
		T:standard_name = "time" ;
		T:calendar = "standard" ;
		T:units = "months since 1960-01-01" ;

       data:
             T = 0, 1, 2, 3

which exist, even if the creators probably didn't really mean what they encoded (although they might have!).
The lines https://github.com/Unidata/cftime/blob/master/src/cftime/_cftime.pyx#L97-L100 seem to restrictive to me. I'm fine with raising an exception when you try do something in these units (like date2num), but I think that it might be too restrictive to prevent these units from being stored in the first place.
Thanks,
David

cftime._dateparse is not part of the public api, it's used internally in num2date and date2num.  So, unless I'm missing something, you shouldn't ever see this error unless you try to do something with these units.

Having said that, if you are using cftime._dateparse and don't want it to fail on invalid units I see no harm in removing that error - it will be triggered later in date2num and num2date anyway.

Thanks - that would certainly help me! I appreciate that it's an underscore method, but it is very useful  - converting CF-netCDF units attributes to datetime objects is something I do frequently, and I don't know of another method for doing it.


Installation

Running (F5) from IDE works great.  Any tips on installation?
Tried:
installutil FileService\bin\Debug\DocumentExport.FileService.exe
Got:
No public installers with the RunInstallerAttribute.Yes attribute could be found.
Remove InstallState file because there are no installers.
The Commit phase completed successfully.
The transacted install has completed.
How to add the service process installer and service installer? From the looks of Program.cs, I was expecting service installation when I ran the project. But I'd also want to be able to script the install from command line, as it's going on remote machine.

Please look at the TopShelf documentation for additional information:
http://docs.topshelf-project.com/en/latest/overview/commandline.html#examples
Basically you can use the command line to install, uninstall and configure the service.


Add support for custom vendor.js paths

Adds support for custom vendor.js output paths specified in ember-cli-build.js (outputPaths). Fixes ebryn/ember-component-css#159

New beta version fixes this, my bad for not checking. Disregard!


Redirection to support KB redirect to the Developer page

Example URL(s)
https://developers.cloudflare.com/support/ssl-tls/troubleshooting/troubleshooting-ssl-errors/
Actual Behavior
All links below redirect to self:
https://developers.cloudflare.com/support/ssl-tls/troubleshooting/troubleshooting-ssl-errors/

Redirect loop errors or HTTP 525 or 526 errors
Only some of your subdomains return SSL errors
Your Cloudflare Universal SSL certificate is not active
OCSP response error
SSL expired or SSL mismatch errors

Expected Behavior
Load the actual support KB articles or have they now been integrated into Developer doc ?
Additional information
No response

The KB article those link to became that dev docs article, those links are trying to link to anchors on the same page and can be updated to anchor links accordingly.

Hi @wolruf ,
I've raised a PR fixing the links on this page:
https://github.com/cloudflare/cloudflare-docs/pull/9411


croc-hunter-jenkinsx to 0.0.53

Promote croc-hunter-jenkinsx to version 0.0.53

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


mkcert -install keeps telling me that "keytool is not available", when it is?

I keep getting:
Warning: "keytool" is not available, so the CA can't be automatically installed in Java's trust store! ⚠

When it plainly is available, I can just type "keytool" and it works. JAVA_HOME is set just fine. I'm really at a loss because everything else can access it just fine.

Weird! Can you give us the output of which keytool and echo $PATH? Are you running mkcert with sudo, maybe?

Timing out in "waiting for info", feel free to open a new issue with the debug info!

Weird! Can you give us the output of which keytool and echo $PATH? Are you running mkcert with sudo, maybe?

Observed same issue due to wrong path in JAVA_HOME, once correct path is present, issue wasn't observed. Thanks for the tip 'which keytoolandecho $PATH', helped me to resolve it.


[Event Request] - Codeunit 5752 - ShowResult

We are using BC 14.0.35570.
We would like to be able to suppress the ShowResult messages/dialog in codeunit 5752.
Suggested new code:
LOCAL ShowResult(WhseShipmentCreated : Boolean)
OnBeforeShowResult(WhseShipmentCreated, Handled); // New
IF Handled then // New
  EXIT; // New
IF WhseShipmentCreated THEN BEGIN
  GetSourceDocuments.ShowShipmentDialog;
  OpenWarehouseShipmentPage;
END ELSE
  MESSAGE(Text004,WarehouseRequest.TABLECAPTION);

With the event definition:
LOCAL [IntegrationEvent] OnBeforeShowResult(WhseShipmentCreated: Boolean; VAR Handled: Boolean)

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


On_best callback function in GeneticAlgorithm

GeneticAlgorithm currently uses the local search intensification procedure whenever a new best solution is found.  #98 will implement intensification at each iteration (with some probability) making the current on best implementation somewhat redundant.
We should implement a more general on_best method to the genetic algorithm, similar to how it's done in ALNS.

Before we do this particular callback function, I think we should have a more general idea of what kind of events a user can register custom code for/what we want to support.

From https://github.com/N-Wouda/PyVRP/issues/164#issue-1608261274:

Now I think it's great if a ready to use GeneticAlgorithm is part of PyVRP, but I don't think it needs to support a lot of customization (like #111 which are hard to get right for every use case), as for those users can just implement their own algorithm inspired by the examples.

I agree with Wouter that we shouldn't support customizations such as on_best. Users can simply create their own algorithms if they really want to have it. Unless we find a good reason to have things like on_best, I propose to benchmark this feature (with and without intensify_on_best) and if there's no meaningful performance difference, then we should just drop it.

@leonlan should we close this? I'm not sure. I personally don't feel the need to support this right now, but that might change later when we have an actual use case. Based on the comments above it seems to me that this issue is quite stale, with no work being planned. We might just as well close it if that's the case.

Let's close it. This is an old idea that I don't need or see myself using in the near future.


Add support user_tags field in library to append volume labels

:red_circle: Coverage decreased from [90.3926%] to [87.7868%]

:red_circle: Coverage decreased from [90.3926%] to [87.7868%]

:red_circle: Coverage decreased from [90.3926%] to [87.7868%]

:red_circle: Coverage decreased from [90.3926%] to [87.7868%]


[Pulsar] Add way to calculate end-to-end operation latency from event time or message property

When testing Pulsar Functions end-to-end latency, it is necessary to be able to calculate the end-to-end latency metrics for the complete end-to-end operation.
This PR adds support for calculating the end-to-end operation latency from either

message publish time (default when using optype of ec2-msg-proc-consume)
message event time
message property called "e2e_starting_time" (milliseconds since epoch)

The calculation method should be specified in the e2e_starting_time_source document level parameter.
When e2e_starting_time_source is set, it configures the end-to-end starting time source. The supported values:

message_publish_time
message_event_time
message_property_e2e_starting_time

Pulsar Functions copy the properties from the incoming message by default. This makes message_property_e2e_starting_time suitable for calculating end-to-end operation latency for chained Pulsar Functions where one incoming message maps exactly to one output message.

@lhotari LGTM.  Can you please update README? In particular, section 3.2 and chapter 8? Thank you!

@lhotari LGTM. Can you please update README? In particular, section 3.2 and chapter 8? Thank you!

@yabinmeng I've added docs to section 3.2.

@lhotari please review the previous changes which added payloadRttFieldFunc to see if these are doing practically the same thing. If so, adding this change would mean we have three different ways to calculate some form of end-to-end RTT. I'd prefer we not duplicate functionality on this if it is the same intent.

payloadRttFieldFunc is different. It takes the time source for calculating the end-to-end latency from the payload.
I don't see three different ways for calculating some form of end-to-end RTT. I think there's only two: the one in this PR that uses the e2e_msg_latency histogram and the payloadRttFieldFunc feature which added the payload_rtt histogram. I agree that it's not optimal that there are multiple ways for calculating end-to-end RTT. Perhaps some further unification could be made in the future.
This PR improves the existing e2e_msg_latency histogram solution so that it is no more tied to using optype of ec2-msg-proc-consume . This PR introduces a concept of "end-to-end operation starting time source" so that various use cases can be supported while continuing to use the e2e_msg_latency histogram.
/cc @mfleming @kijanowski


Fix the import of the pascalToKebab function for icons generation

Current dependencies on/for this PR:

main

PR #43

PR #45

PR #46   👈

This comment was auto-generated by Graphite.


[Metadata] Copy fields

When displaying the metadata of any data (right-click, metadata), it would be nice to be able to copy any field of the metadata.

I just tested @mjuhoor and you can copy / paste a selected line with Ctrl-C / Ctrl-V


1.0

You want to make a PR to Talos
Thanks so much :) First, please take a moment to carefully check through
the below items:
Sanity

[ ] I'm aware of the implications of the proposed changes
[ ] Code is PEP8
[ ] I'm making the PR to master

Docs

[ ] Docs are updated
[ ] Docs version is correct (index.html and _coverpage.md)

Tests

[ ] Changes have gone through actual use testing
[ ] All local tests have passed (run ./test.sh in /talos)
[ ] Tests have been updated to reflect the changes

Hello @mikkokotila! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file examples/version-check.py:

Line 4:1: E402 module level import not at top of file
Line 7:1: E402 module level import not at top of file
Line 8:44: W292 no newline at end of file

In the file setup.py:

Line 11:58: W291 trailing whitespace

In the file talos/autom8/automodel.py:

Line 63:80: E501 line too long (89 > 79 characters)

In the file talos/metrics/keras_metrics.py:

Line 89:5: E265 block comment should start with '# '

In the file talos/model/normalizers.py:

Line 14:80: E501 line too long (89 > 79 characters)

In the file talos/scan/scan_finish.py:

Line 71:80: E501 line too long (84 > 79 characters)

In the file talos/utils/experiment_log_callback.py:

Line 28:80: E501 line too long (93 > 79 characters)

In the file test-ci.py:

Line 16:1: W293 blank line contains whitespace

In the file tests/commands/recover_best_model.py:

Line 9:57: W291 trailing whitespace
Line 24:80: E501 line too long (94 > 79 characters)
Line 29:80: E501 line too long (92 > 79 characters)

In the file tests/commands/test_latest.py:

Line 36:80: E501 line too long (93 > 79 characters)

In the file tests/commands/test_predict.py:

Line 4:1: W293 blank line contains whitespace

In the file tests/commands/test_scan.py:

Line 52:28: E231 missing whitespace after ':'
Line 57:31: E231 missing whitespace after ':'
Line 129:80: E501 line too long (83 > 79 characters)


[Fluent] Porting LoadBalancer fixes and unit test enhancements from the Java SDK beta4.1 side

(tests passing)
based on Java SDK commits:

https://github.com/Azure/azure-sdk-for-java/commit/0f94f9a65c47a5a7cdb73f5f6feb259ce2d3128d
https://github.com/Azure/azure-sdk-for-java/commit/b6c20bf4ffe3e24f67039d871aa703aab1380de6
https://github.com/Azure/azure-sdk-for-java/commit/596290b7beb5263921edd73600ff3f4fee9a6e5a
https://github.com/Azure/azure-sdk-for-java/commit/88ae72dd2fd8fa12a466e1d16d53a7982982b468

Hi @martinsawicki, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (marcins). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@martinsawicki please reset your branch


Ground Truth for Benchmark / Semi-Supervised

Orion version: 0.2.7
Python version: 3.11
Operating System: Windows

Question 1:
I want to make a Benchmark for some Pipelines, but how to set the ground truth in den input?
In this quickstart, we can use the evaluation function wiht ground_truth, but how to use in the benchmark-function?
Question 2:
As far as i understand, all these models work only in a unsupervised way, since all models are used in a regression-based way since they try to predict values from the time-series input which are part of the input. For models like auto-encoder, they can also wokr in a semi-supervised way, where they use some labeled data (Anomaly or not) to  define/find a better threshhold to separate the distribution of normal data and anaomaly data.
Are all models limited to use them in a unsupervised way? And do i have access to the threshold value you use in https://sintel.dev/Orion/api_reference/api/orion.primitives.timeseries_anomalies.find_anomalies.html.
Since there is not exactly explained what this Threshiold is and how it will be computed. Can u explain or give me a reference where is is stated?
Best Lukas

Hi @LuSchnitt!
Q1: To use the benchmark, there is a load_anomalies function where it takes the name of the signal as input and returns a dataframe of the start and end timestamps of the ground truth anomalies. To use our benchmark on your custom dataset, please provide an anomalies.csv file in your data path that looks something similar to the labels dataframe provided in this notebook.
Q2: all pipelines in Orion are unsupervised and do not use anomalies in any part of the detection process, they are only used for evaluation in the benchmark. Even the autoencoders we support work on reconstructing the signal and are completely unsupervised.
The find_anomalies primitives works in two approaches: fixed threshold or dynamic threshold.

The fixed threshold approach is a simple moving window where any value that exceeds 4 standard deviations away from the mean is considered an anomalous value.
The dynamic threshold is the algorithm proposed by NASA, you can read their approach here.

Hope this clarifies your questions!

Hi @sarahmish,
Thank you for answering my questions so quickly. I have read a lot in the python code of the primitives and the paper you mentioned.
I think I understand everything now, thanks for your help!
You all did a great job documenting the python code! Could be that I missed it, but there is no option to return the dynamic threshold for each window of find_anomalies?
Best Lukas

We don't currently keep track of the threshold values that was used for each window.
Though there is a simple modification to the function https://github.com/sintel-dev/Orion/blob/47c13538257d72fbdcb18f8f2d81b9c03f3c28b9/orion/primitives/timeseries_anomalies.py#L364
where we can return the threshold that was found for that window
return window_sequences, threshold

then you can store a list in find_anomalies function of all the threshold values that were used.
I believe that would make it possible for you to retrieve the threshold values.
Let me know if you have any further questions!

Hello @sarahmish,
thanks for the help, i thougth about this too but wasn sure if i jinx some of the following functionality with it. I did it by saving the threshold to a file instead of adapting the return values.
In regar to Q1: Evaluation, i did like you said but unfortunately i got the same error again and again. I will add a picture with the structure of my anomalies and the error message.

The resulting anomalies dataframe should have two main columns:

signal: which contains the name of the signal
events: which is a list of tuples containing two elements.

for example, in the following screenshot, we have S-1 with only one anomaly (the list contains only one tuple). While P-1 has more than one.

then when you reference load_anomalies('S-1') you will get a dataframe containing the anomalies of S-1 as follows:

You raise an important issue though, load_anomalies should take a source file as argument to load your data's anomalies. As a workaround, you will need to have anomalies.csv in the expected path of the function which is /path/to/orion/data/anomalies.csv.
I will open an issue to mark the need for this functionality!

Thanks for replying!
So if i understand correctly, the signal coloumn contains information about specific anomalie-events. Since i only have infomation if a timestamp is anomalous or not this approach is unnecessary complex for my case.
But i found a way to use the <model>.evaluate method which fits perfect to my case!
I just got one more question.
The evaluate function takes an data arguemnt as well as as an train_data argument.
I understand the workaround in the following way: The model gets trained with train_data and afterwards tested with data, the found anomalies from data are then comapred with the ground_truth anomalies which only correspond to the data anomalies.
Am i correct?
Anyway much thanks to you for your support, i really like your framework and will cite it in my master-thesis which is about finding anomalies in building energy meter-data.

Yes that is correct @LuSchnitt, the orion.evaluate function is only evaluating contextual anomalies. Moreover, the train_data argument is only if you want to train your model on the training data prior to evaluating!
Thank you so much, best of like with your master thesis!


ETA for the official release of svelte-datepicker

I am running into issues with https://github.com/6eDesign/svelte-calendar and was hoping that this rewrite would fix that ;)

That would be really interesting to know.
I think this is the first easy to use range picker for svelte that looks like something

That would be really interesting to know.
I think this is the first easy to use range picker for svelte that looks like something

We use this in prod :) so... Already!
Is there something specific you want in order to make it an official release?

We use this in prod :) so... Already!
Is there something specific you want in order to make it an official release?

Ok, all public now. Sorry! https://www.npmjs.com/package/@beyonk/svelte-datepicker

Ok, all public now. Sorry! https://www.npmjs.com/package/@beyonk/svelte-datepicker


[Bug]: can't drag mod to activite window

recording-2023-08-05-12-29-11.webm
BG3 Mod Manager Version
<IP_ADDRESS>
BG3 Game Version
Hotfix#1
Bug Summary
I am unable to drag inactive mods into the activation area, which is preventing the desired mod functionalities from being enabled in my game.
Links
No response

Imgur

mine completely crashes when attempting to drag a mod

are you on GOG?
I am, and have the same issues
**Screenshots:
https://imgur.com/a/95EgnhD**
I also think i fixed the order but it didnt help

Reddit ask for help post with photos:
BG3 mod manger not working
Mods / Modding
Hey guys, every time i used bg3 mod manager first i get this missing mod pop up
and even if i don't, I also can't drag inactive mods to active?
Any idea? I really just want to mod the game and not use nexus.
Also my profile is automatically public. I'm using GOG.
**Screenshots:
https://imgur.com/a/95EgnhD**

你在GOG嗎？（在頂上）
我也是，也有同樣的問題
**截圖：
https://imgur.com/a/95EgnhD **
我還認為我修復了順序，但沒有幫助，我還添加了所有點網注入的照片，我無法獲得 4.7.2 運行時，因為我有 6 和 7，可能就是這樣。
Reddit 請求幫助發布照片：
BG3 mod 管理器無法工作 Mods / Modding 嘿伙計們，每次我首先使用 bg3 mod 管理器時，我都會彈出這個缺失的 mod
即使我不這樣做，我也無法將不活動的模組拖到活動狀態？
任何想法？我真的只是想修改遊戲而不是使用 Nexus。
我的個人資料也自動公開。我用的是GOG
**截圖：
https://imgur.com/a/95EgnhD **

Mine is the steam version, I won't jump out any missing errors, I can't drag the mod to the activate window, it will always be in the inactivate window, so the game can't read the mod all the time

go into setting, keyboard shortcuts, moved selected nods to opposite list. thats how i got mine to work

CHANGED "Public" PROFILE FOLDER NAME
it used to be
C:\Users\bouta\AppData\Local\Larian Studios\Baldur's Gate 3\PlayerProfiles\Public
then i changed the name to my character in game and they started activating.
thanks mod author for the note in the documentation.

The "mortemus" folder used to be "Public"
so change that to the character name, and then make sure the drop down at the top left matches it

go into setting, keyboard shortcuts, moved selected nods to opposite list. thats how i got mine to work

OK this solved my problem but still don't know why the mouse dragging doesn't work


Automate (some) Testing

It would be highly helpful to have automated testing on a skeleton project.
My current inclination is to use maven-verifier.
If that route were taken, we could inject environment properties to set the git branch during execution, assert logs contain appropriate messages, and assert that artifacts are named appropriately and published to the correct place (file-based destination repositories).

Thanks to @jacobharris919 for the help on this in #90


refactor: Allow user to inject multiple outbound transport

closes #859
Signed-off-by: Firas Qutishat<EMAIL_ADDRESS>

@rolsonquadras


docker: disable LVM backup

By default, LVM tools will create a "metadata backup" every time a pool
is modified. Since the backup location only exists while the container
exists, this wasn't very useful in the container context.
In the interest of making our images ready to be read-only, disable the
creation of LVM backups.
Signed-off-by: Moritz "WanzenBug" Wanzenböck<EMAIL_ADDRESS>

@kvaps I'd be interested to hear if you ever used these LVM metadata backups. If you have, we might instead try to make them actually persistent.

What is driving this effort actually? Not against it, just trying to understand why we would like to have a "RO label".

I'm currently working on operator v2, and would like to tighten the SecurityContext of our containers. One of the recommended options is readOnlyRootFS, which I enabled temporarily, which then caused all LVM commands to fail. If nothing else, it ensures we don't accidentally miss the creation of files in the container that should really be persistent.
In this case, I guess I'll just map the hosts directory through.

However it make sense only for LVM backend, LVM_THIN has it's own metadata volume.

For me, it was also required for lvcreate -T ... operations.

Yes LVM_THIN writes metadata into /etc/lvm/backup the same way as traditional LVM, but since it uses chunks, the information about these chunks is stored in specific metadata volume. Thus if you lose this information, you'll be never successful to recover thin-volumes from /etc/lvm/backup


Fix bug with column names in SklearnTransform

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Before submitting (must do checklist)

[x] Did you read the contribution guide?
[x] Did you update the docs? We use Numpy format for all the methods and classes.
[x] Did you write any new necessary tests?
[ ] Did you update the CHANGELOG?

Type of Change

[ ] Examples / docs / tutorials / contributors update
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Improvement (non-breaking change which improves an existing feature)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Proposed Changes

Fix bug #377
Refactor code
Add tests on these transforms

Related Issue
#377
Closing issues
Closes #377

Codecov Report

Merging #398 (571013e) into master (e884f8a) will decrease coverage by 35.38%.
The diff coverage is 57.14%.

:exclamation: Current head 571013e differs from pull request most recent head 40ec4a2. Consider uploading reports for the commit 40ec4a2 to get more accurate results

@@             Coverage Diff             @@
##           master     #398       +/-   ##
===========================================
- Coverage   87.02%   51.64%   -35.39%
===========================================
  Files          98       98
  Lines        4964     4961        -3
===========================================
- Hits         4320     2562     -1758
- Misses        644     2399     +1755

Impacted Files
Coverage Δ

etna/transforms/power.py
52.38% <ø> (-40.48%)
:arrow_down:

etna/transforms/scalers.py
100.00% <ø> (+7.14%)
:arrow_up:

etna/transforms/sklearn.py
36.14% <50.00%> (-59.64%)
:arrow_down:

etna/core/mixins.py
73.91% <75.00%> (-20.83%)
:arrow_down:

etna/core/__init__.py
100.00% <100.00%> (ø)

etna/commands/__init__.py
0.00% <0.00%> (-100.00%)
:arrow_down:

etna/commands/backtest_command.py
0.00% <0.00%> (-96.43%)
:arrow_down:

etna/commands/forecast_command.py
0.00% <0.00%> (-92.00%)
:arrow_down:

etna/commands/__main__.py
0.00% <0.00%> (-87.50%)
:arrow_down:

etna/commands/resolvers.py
0.00% <0.00%> (-80.00%)
:arrow_down:

... and 65 more

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 e884f8a...40ec4a2. Read the comment docs.


Consider replacing abandoned dependencies

Following dependencies identified to have low amount of recent commits and might be abandoned at one point:

[x] https://github.com/CyCraft/blitzar/issues/160 -> https://dev.to/maceto2016/data-driven-ui-with-vuejs-and-quasar-2ccb or https://formkit.com/
[ ] keyboard -> no replacement yet (just a very reduced set implement without dep?)
[x] dependency-injector
[x] v4l2py -> https://github.com/tiagocoutinho/linuxpy

blitzar replaced by jsonforms.


Issue #317 Fixed the footer from scratch

ISSUE #317
I complete this.
Please don't forget to add this label --> gssoc24-exted, hacktoberfest-accepted, label-2 as per added in the issue #317
merge it.

@Luson045


Appstudio update test-component-pac-jrvw

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-jrvw-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
19 seconds
clone-repository

✅ Succeeded
23 seconds
build-container

✅ Succeeded
8 seconds
sast-snyk-check

✅ Succeeded
11 seconds
inspect-image

✅ Succeeded
10 seconds
sbom-json-check

✅ Succeeded
10 seconds
deprecated-base-image-check

✅ Succeeded
11 seconds
clair-scan

✅ Succeeded
40 seconds
clamav-scan

✅ Succeeded
6 seconds
show-summary

✅ Succeeded
6 seconds
show-sbom

Pipelines as Code CI/test-component-pac-jrvw-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
19 seconds
clone-repository

✅ Succeeded
23 seconds
build-container

✅ Succeeded
8 seconds
sast-snyk-check

✅ Succeeded
10 seconds
sbom-json-check

✅ Succeeded
40 seconds
clamav-scan

✅ Succeeded
11 seconds
inspect-image

✅ Succeeded
10 seconds
deprecated-base-image-check

✅ Succeeded
11 seconds
clair-scan

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
6 seconds
show-summary


lwcCompilerOutput options for Production not respected

I know it is best practice to minify and compact JS resource for a production environment. But I wanted to see the source-map in my Chrome console. However, when I set my lwcCompilerOutput to this:
production: {
            compat: false,
            minify: false,
            env: {
                NODE_ENV: 'production'
            },
            format: 'amd'
        }

It seems that this line
will ignore the compat and minify options.

The LWC compiler output is not affected by that line. It's passed as you configure it to the transform.
If you want more granular control I recommend to either use a custom webpack config, or a boilerplate webpack project and the lwc-webpack-plugin.

I guess what I am trying to say is when I run npm run build which in turn runs lwc-services build -m production and I have compat and minify false as specified above, it never produces a source map. Only when I run npm run build:development which in turn runs lwc-services build  will it only produce a source-map. So that's why I am pointing to that line referenced in my original post

Yeah, that's something that's unlikely to change in lwc-services. The dedicated webpack plugin is a viable alternative for that.

@muenzpraeger understood I just wanted to confirm that it wasn't an issue with the parsing of the lwc-services.config.json


Error on start mat theme

Software version
quasar-nuxt:
OS:
Node:
NPM:
Browsers:
Any other software related to your bug:
JsFiddle (for Quasar v0.15+ only)

What did you get as the error?
nuxt:render Rendering url / +12s
{ TypeError: Cannot set property 'screen' of undefined
at Object.install (node_modules/quasar-framework/dist/quasar.mat.esm.js:19632:0)
at server-bundle.js:4509:11
at Array.forEach ()
at Object.install (node_modules/quasar-framework/dist/quasar.mat.esm.js:835:0)
at Function.Vue.use (d:\Projects_Workplace\schooling\nuxt\node_modules\vue\dist\vue.runtime.common.js:4749:22)
at module.exports.webpack_exports.a (.nuxt/quasar-nuxt.js:15:0)
at createApp (.nuxt/index.js:135:0)
at
at process._tickCallback (internal/process/next_tick.js:188:7) statusCode: 500, name: 'TypeError' }

install: function install (ref) {
var this$1 = this;
var $q = ref.$q;
var Vue = ref.Vue;
if (this.__installed) { return }
this.__installed = true;

if (isSSR) {
  **this.$q.screen = this;** => **$q.screen = this**
  this.setSizes = this.setDebounce = function () {};
  return
}

{
"dependencies": {
"nuxt": "^1.0.0",
"quasar-nuxt": "^0.16.0-alpha.2"
},
"devDependencies": {
"babel-eslint": "^8.2.1",
"eslint": "^4.15.0",
"eslint-friendly-formatter": "^3.0.0",
"eslint-loader": "^1.7.1",
"eslint-plugin-vue": "^4.0.0"
}
}
What were you expecting?
What steps did you take, to get the error?

Hi,
Thanks for your interest in Quasar and this Nuxt module. Unfortunately, it is still work in progress here (indicated on this repo), as you need the bleeding edge version of Quasar: v0.16.1, which I haven't released yet. Please stay tuned to our Discord/Forum/Twitter account for announcements ;)

On discord I was told to use quasar's solution: https://quasar.dev/quasar-cli/developing-ssr/introduction


Update events

Adding 3 upcoming events

Karolinska LCI workshop
GBI seminars
TiM 2023

cc @jburel

Built at https://snoopycrimecop.github.io/www.openmicroscopy.org/events/

I remembered us using a different icon for event in the future. Did we decide to stop using it?

I remembered us using a different icon for event in the future. Did we decide to stop using it?

Fixed in https://github.com/ome/www.openmicroscopy.org/pull/631/commits/af0c6026eb9156c5271b52c908bb52af2b68e7ed

fixes pushed


Feat: Enable Copying Data from AG Grid to Excel - 620

This PR enables copying data directly from AG Grid cells to an Excel file.
Closes #620

This is an interesting feature, but I wonder if its better just to use the backend download data feature. Let's ask our product owner if he thinks this has additional value.

Thank you for reviewing my PR. I agree with you. Using backend download to provide a full list of records makes more sense. Front-end download is useful for short lists that fit on one page with different filters applied.


Implement nested run deep linking

Provide the ability to identify individual runs in the UI based on separate URLs, not just to identify individual resolutions as currently.

The current nested run and open tab should be reflected in the UI.

Can you help provide more context ? Maybe give an example of nested runs?

@chance-an Here is the concept explained: https://docs.sematic.dev/diving-deeper/functions#nested-sematic-functions

For clarity, the ask for this issue is to implement deep links for pipeline pages in a form similar to
/pipelines/[pipeline_name]/[run_id]?deeplink=params
So when a user launches a deep link URL of this kind, he or she will see the previously selected nested run or open tab chosen and highlighted.
Is this understanding correct?

@chance-an  Exactly. The URL needs to individually identify every panel. Currently it only identifies the resolution, with the panel being inherited by the browsing of any previously-opened resolution on the same pipeline:


Misc kotlin cleanup

renamed kotline.go (!?!) to kotlin.go
deleted a useless function call in the boilerplate function

Thanks!


SIGINT is sent twice when pressing Ctrl-C, causing dirty shutdown

I have a package.json with the following scripts:
…
"startemulators": "firebase emulators:start --import seed",
"listen": "onchange 'source_files/*.js' -- touch functions/index.js",
"emulate": "concurrently \"npm run startemulators\" \"npm run listen\""
…

Running the emulate script works as expected, but pressing Ctrl-C to shut the processes down gives me this:
[0] i  emulators: Received SIGINT (Ctrl-C) for the first time. Starting a clean shutdown.
[0] i  emulators: Please wait for a clean shutdown or send the SIGINT (Ctrl-C) signal again to stop right now.
[0] i  emulators: Shutting down emulators.
[0] i  ui: Stopping Emulator UI
[0] ⚠  Emulator UI has exited upon receiving signal: SIGINT
[0] i  functions: Stopping Functions Emulator
[0] i  hosting: Stopping Hosting Emulator
[0] i  database: Stopping Database Emulator
[1] npm run listen exited with code 0
[0]
[0] ⚠  emulators: Received SIGINT (Ctrl-C) 2 times. You have forced the Emulator Suite to exit without waiting for 3 subprocesses to finish.

So for some reason, a second SIGINT is sent to the firebase command specified in the first script. How come?

Any ideas on this?

@alimony I have seen this, but wasn't considering concurrently would be causing the double Ctrl-C's.
It may well be. In that case, debugging it means having a project with Firebase JS SDK and concurrently both in the mix. Maybe we should create a minimal project that showcases this?

I'll create a minimal test case.

I can provide a reproducible, negative test case.
$ git clone https://github.com/akauppi/firebase-jest-testing.git
$ cd firebase-jest-testing
$ npm install

$ npm run //start:pipeless
...
<once services are up, press Ctrl-C>

Tried ~6 times, not a single time there is Received SIGINT (Ctrl-C) 2 times.

I'll try to compare with my other project, where I do see these, and try to spot the difference.

The weird "//start:pipeless" is because if I pipe Firebase Emulator output, another concurrently issue is raised, and it disturbs in checking this one. :)

macOS 11.4

The positive case comes here.
If I launch: concurrently -> Docker -> Firebase CLI (which I do in a web app project, all the time), the double Ctrl-C occurs.

It's always connected to using Docker
diving into the container and launching it manually from there (no concurrently involved) doesn't recreate the error

Detailed log
> concurrently --kill-others "$(docker-run-cmd) firebase emulators:start --project=demo-2"

Launching Docker... 🐳

[0] ⚠  emulators: You are not currently authenticated so some features may not work correctly. Please run firebase login to authenticate the CLI.
[0] i  emulators: Starting emulators: auth, functions, firestore
[0] i  emulators: Detected demo project ID "demo-2", emulated services will use a demo configuration and attempts to access non-emulated services for this project will fail.
[0] ⚠  Your requested "node" version "14 || ^16" doesn't match your global version "16"
[0] ⚠  functions: You are not signed in to the Firebase CLI. If you have authorized this machine using gcloud application-default credentials those may be discovered and used to access production services.
[0] i  firestore: Firestore Emulator logging to firestore-debug.log
[0] i  ui: Emulator UI logging to ui-debug.log
[0] i  functions: Watching "/work/functions" for Cloud Functions...
[0] ✔  functions[us-central1-cloudLoggingProxy_v0]: http function initialized (http://<IP_ADDRESS>:5002/demo-2/us-central1/cloudLoggingProxy_v0).
[0] ✔  functions[us-central1-userInfoShadow_2]: firestore function initialized.
[0]
[0] ┌─────────────────────────────────────────────────────────────┐
[0] │ ✔  All emulators ready! It is now safe to connect your app. │
[0] │ i  View Emulator UI at http://<IP_ADDRESS>:4000                  │
[0] └─────────────────────────────────────────────────────────────┘
[0]
[0] ┌────────────────┬──────────────┬───────────────────────────────┐
[0] │ Emulator       │ Host:Port    │ View in Emulator UI           │
[0] ├────────────────┼──────────────┼───────────────────────────────┤
[0] │ Authentication │ <IP_ADDRESS>:9100 │ http://<IP_ADDRESS>:4000/auth      │
[0] ├────────────────┼──────────────┼───────────────────────────────┤
[0] │ Functions      │ <IP_ADDRESS>:5002 │ http://<IP_ADDRESS>:4000/functions │
[0] ├────────────────┼──────────────┼───────────────────────────────┤
[0] │ Firestore      │ <IP_ADDRESS>:6767 │ http://<IP_ADDRESS>:4000/firestore │
[0] └────────────────┴──────────────┴───────────────────────────────┘
[0]   Emulator Hub running at localhost:4400
[0]   Other reserved ports: 4500
[0]
[0] Issues? Report them at https://github.com/firebase/firebase-tools/issues and attach the *-debug.log files.
[0]
^C[0]
[0] i  emulators: Received SIGINT (Ctrl-C) for the first time. Starting a clean shutdown.
[0] i  emulators: Please wait for a clean shutdown or send the SIGINT (Ctrl-C) signal again to stop right now.
[0] i  emulators: Shutting down emulators.
[0] i  ui: Stopping Emulator UI
[0] ⚠  Emulator UI has exited upon receiving signal: SIGINT
[0] i  functions: Stopping Functions Emulator
[0] i  firestore: Stopping Firestore Emulator
[0]
[0] ⚠  emulators: Received SIGINT (Ctrl-C) 2 times. You have forced the Emulator Suite to exit without waiting for 1 subprocess to finish. These processes may still be running on your machine:
[0]
[0] ┌────────────────────┬──────────────┬─────┐
[0] │ Emulator           │ Host:Port    │ PID │
[0] ├────────────────────┼──────────────┼─────┤
[0] │ Firestore Emulator │ <IP_ADDRESS>:6767 │ 30  │
[0] └────────────────────┴──────────────┴─────┘
[0]
[0] To force them to exit run:
[0]
[0] kill 30
[0]
[0] docker run --rm --sig-proxy=true -v /Users/asko/Git/GroundLevel-firebase-es/packages/backend:/work -w /work -p 6767:6767 -p 5002:5002 -p 9100:9100 -p 4000:4000 firebase-ci-builder:9.12.1-node16-npm7 firebase emulators:start --project=demo-2 exited with code 0

Note: This is just my 2c. I am not really troubled by this error message, since if running things under Docker, things get cleaned up, anyhow.

I have not been able to create a small test case, but I have discovered that skipping the pubsub emulator makes the error go away. For example, using this:
firebase emulators:start --only firestore,database,functions,hosting,pubsub
will send SIGINT twice when quitting concurrently, while this:
firebase emulators:start --only firestore,database,functions,hosting
will not.

Hi,
I have the same problem and investigated a little bit.
By commenting out that line, I ended up with something working correctly, no double SIGINT, everything is cool.
It looks like spawn-command does not spawn the subprocess in detached mode, and it seems the defaults in concurrently are not setting detached options neither. Because if not, it's perfectly normal to have the SIGINT sent twice, because it's received by the subprocess, and then resent with command.kill(signal) a second time.

hi there!
I'm experiencing this issue too if I try to run firebase directly as concurrently command.
However, if my firebase command is wrapped with yarn script command in package.json, the issue is not reproduced. Looks like yarn already does some protection of double sent signals.
I can't use full command in scripts since I construct firebase command args on the fly.
So I did an alias like that:
// package.json

"scripts": {
  "firebase:emulators": "firebase emulators:start",
}

and then call the command via concurrently like that:
yarn firebase:emulators --only ... <here are my dynamic args>

for me this is a legit workaround, hope it helps someone else

Running into this problem myself, here's a bit from my package.json:
  "scripts": {
    "build": "tsc",
    "build:watch": "tsc -w",
    "format": "prettier --write src/**/*.ts",
    "emulate": "firebase emulators:start --import=./emulator-data --export-on-exit",
    "serve": "concurrently 'npm run build:watch' 'npm run emulate'"
  },

If I run npm run serve and then press Ctrl+C the Firebase emulators see double SIGINT signals and shutdown without exporting data.

Hey all. I've briefly looked at this today, it seems that firebase-tools@9 causes the issue, but firebase-tools@10 doesn't.
@akauppi it seems you did a fair amount of research in https://github.com/firebase/firebase-tools/issues/3578.
Is there much that should be done here?
I see people mentioned the removal of things like passing SIGINT down to the command or spawning subprocesses in detached mode, but I'm afraid this would worsen issues around hanging processes.

@gustavohenke I moved from concurrently to Docker Containers last year, and that removed the dirty shutdown issue for me.

A solution i came up with is like this:
{
    "emulator-start": "./node_modules/.bin/firebase emulators:start --import=emulatorData/localEmulatorData --export-on-exit=emulatorData/localEmulatorData",
    "start": "npm run emulator-start & npm run start-servers",
    "start-servers": "concurrently -c gray.dim --kill-others \"npm run api\" \"npm run scheduler\""
}

@jakeleventhal So you just replaced concurrently with the & approach for the npm script which combines the emulators with another command?
My understanding is that the & approach will not work on Windows machines.  Is that still true?(I'm on Mac and don't have a Windows machine handy to test it with).

@jasonkylefrank kind of - i am running the emulators outside of concurrently but my servers are still running via concurrently
as for windows - i don't use windows so idk lol

I noticed this today as now I can't exit the shell with pressing ctrl+c again (on macbook pro).
running "concurrently \"yarn:firebase:emulators\"" and pressing ctrl+c gives exit code 1. Running the same without concurrently gives exit code 0.
Adding docker to mix with "concurrently \"yarn:firebase:emulators\" \"docker compose up\" and pressing ctrl+c I get
^C[1] Gracefully stopping... (press Ctrl+C again to force)
[firebase:emulators]
[firebase:emulators] i  emulators: Received SIGINT (Ctrl-C) for the first time. Starting a clean shutdown.
[firebase:emulators] i  emulators: Please wait for a clean shutdown or send the SIGINT (Ctrl-C) signal again to stop right now.
[firebase:emulators] i  emulators: Shutting down emulators.
[firebase:emulators] i  ui: Stopping Emulator UI
[firebase:emulators] ⚠  Emulator UI has exited upon receiving signal: SIGINT
[firebase:emulators] i  auth: Stopping Authentication Emulator
[firebase:emulators] i  hub: Stopping emulator hub
[1] Container gql-1  Stopping
[firebase:emulators] i  logging: Stopping Logging Emulator
[1] time="2022-05-03T08:09:27+03:00" level=error msg="got 3 SIGTERM/SIGINTs, forcing shutdown"
[1] Container db-1  Killing
[1] Container gql-1  Killing
[firebase:emulators] yarn run firebase:emulators exited with code 1
[1] Container db-1  Killed
[1] Container gql-1  Killed
[1] Container gql-1  Stopped
[1] Container db-1  Stopping
[1] Container db-1  Stopped

concurrently process seems to be stuck itself so I cant exit the shell anymore

@gustavohenke

I see people mentioned the removal of things like passing SIGINT down to the command or spawning subprocesses in detached mode, but I'm afraid this would worsen issues around hanging processes.

windows 10
firebase-tool 11.2.2
<EMAIL_ADDRESS>I'm also have this problem that double SIGINT cause emulator unable to export the exit gracefully.
I remove and patched the line that @ghivert mentioned,and its really solve the problem on windows.  Double SIGINT seems really not a right way to exit all process, maybe consider use the timeout timer to deal with hanging process in any case?

Same issue over here, any updates ?

I think this may be due to Concurrently's use of tree-kill to terminate individual processes. For example, if you send a SIGINT signal to a Docker Compose, it will handle terminating its subprocesses on its own; there's no need for Concurrently to know or care that the process has subprocesses (although I'm sure that's not always the case). But I think having the option to override this behaviour with simply sending the signal to each of the original processes might solve this issue.
I wanted to verify this by writing a minimal wrapper for the Concurrently API and passing (pid, signal) => process.kill(pid, signal) as the kill option; but it doesn't quite seem to work as it should - there's no output at all (even when I pass outputStream: process.stdout in the options), and the script seems to terminate immediately when I hit Ctrl+C, as opposed to waiting for the child processes to exit, like the CLI does; so I don't really know how to verify this.


[tls] libvirt service to use dedicated libvirt ca

Depends-On: https://github.com/openstack-k8s-operators/openstack-operator/pull/779
Jira: OSPRH-6174

/hold

recheck

recheck

recheck


minepkg-lock.toml doesn't update

When commenting out a dependency in the minepkg.toml, the game will still start with whatever was commented out.
To make it work, the user has to delete the minepkg-lock.toml first.
So it appears the minepkg-lock.toml doesn't update when launching.
How to reproduce

Make a modpack or mod
add for example modmenu as a dependency
enter minepkg launch and exit
comment something out (in this case modmenu)
enter minepkg launch again

Expected behavior: minepkg does not include mods that are commented out.
Actual behavior: The game starts with mods even when they were removed in the toml.

should be fixed


Container image

It would be great if we had a container image, hosted on ghcr.io and not docker hub due to the limits.

PR for the base Docker image at #30 .

I’m going to update the PR #30 and we will publish a docker image.

For those who want a published docker image, I made my own available with cyb3rjak3/unbound-exporter or ghcr.io/cyb3r-jak3/unbound-exporter.
Source also happy to make a PR for publishing images in this repo.

Couple of reasons I have my own docker file.

Using busybox as the release image means that healthchecks can be supported as wget is already in the image
By cloning the repo, instead of using COPY, I can easily change the version of the unbound exporter used.