Telemetry, output, and bug fixes

Description
This PR includes a number of small changes intended to correct reported issues and implement the latest telemetry updates.
Fixes #74
Fixes #88
Closes #74
Closes #88
Type of Change

[x] Non-module change (e.g. CI/CD, documentation, etc.)
[x] Azure Verified Module updates:

[x] Bugfix containing backwards compatible bug fixes

[x] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[x] Feature update backwards compatible feature updates.
[ ] Breaking changes.
[x] Update to documentation

Checklist

[x] I'm sure there are no other open Pull Requests for the same update/change
[ ] My corresponding pipelines / checks run clean and green without any errors or warnings
[ ] I did run all  pre-commit checks

@khushal08 or @jaredfholgate - Can you please approve the e2e tests and review this PR?  It addresses some of the longer running issues and adds the new telemetry (modtm) provider updates.  The TFlint tests are failing due to the new WAF rule for VNet VPN gateways to be active/active on one of the examples.  I can try setting it to active/active if you concur.


Supporting heredoc

Hey @drowzy,
I am trying to parse a config with heredoc like this:
action "transform_data" {
  js = <<-EOT
    const output = { ...input, x: 1 };
    return output;
  EOT
}

But it is failing with the following error:
** (FunctionClauseError) no function clause matching in HXL.Error.upcase_first/1

    The following arguments were given to HXL.Error.upcase_first/1:

        # 1
        'syntax error before: '

    Attempted function clauses (showing 1 out of 1):

        defp upcase_first(<<char::utf8, rest::binary>>)

    (hxl 0.1.2) lib/hxl/error.ex:37: HXL.Error.upcase_first/1
    (hxl 0.1.2) lib/hxl/error.ex:24: HXL.Error.format_reason/1
    (hxl 0.1.2) lib/hxl/parser.ex:21: HXL.Parser.parse/1
    (hxl 0.1.2) lib/hxl.ex:95: HXL.decode/2
    (hxl 0.1.2) lib/hxl.ex:25: HXL.decode_file/2
    iex:3: (file)

Is parsing HCL that contains heredoc supported?
If not, are there any potential workarounds?
BTW, this is a great library, excellent work!

Found out that it is supported.
https://github.com/drowzy/hxl/blob/2f9295c10c8d3d4a2f6090683e9aa62d5d903705/src/hcl_parser.yrl#L196
So, fixed my code by adding a missing space like below.
action "transform_data" {
  js = <<- EOT
    const output = { ...input, x: 1 };
    return output;
  EOT
}

However, it seems that the library is trying to parse string inside heredoc as well since now I am getting this error:
{:error, "Unrecognized input: ';\n    return output;\n  EOT\n}\n' at 19:238"}

Thanks for the issue! You are correct that it should treat the lines in the heredoc as text. Seems to be a bug. I’ll look into it!

Thanks Simon :)

I tried with the following:
hcl = """
action "transform_data" {
  js = <<-EOT
    const output = { ...input, x: 1 };
    return output;
  EOT
}
"""

iex(8)> HXL.Lexer.tokenize(hcl)
{:ok,
 [
   {:identifier, {1, 6}, ["action"]},
   {:string_part, {1, 23}, ["transform_data"]},
   {:"{", {1, 25}},
   {:identifier, {2, 4}, ["js"]},
   {:=, {2, 6}},
   {:heredoc, {0, 0}},
   {:identifier, {2, 13}, ["EOT"]},
   {:text, {4, 0}, ["    const output = { ...input, x: 1 };"]},
   {:text, {5, 0}, ["    return output;"]},
   {:identifier, {5, 5}, ["EOT"]},
   {:"}", {6, 1}}
 ], "", %{}, {7, 106}, 106}

and
HXL.Parser.parse(hcl)

{:ok,
 %HXL.Ast.Body{
   statements: [
     %HXL.Ast.Block{
       type: "action",
       labels: ["transform_data"],
       body: %HXL.Ast.Body{
         statements: [
           %HXL.Ast.Attr{
             name: "js",
             expr: %HXL.Ast.TemplateExpr{
               delimiter: "EOT",
               lines: ["    const output = { ...input, x: 1 };",
                "    return output;"]
             }
           }
         ]
       }
     }
   ]
 }}

Which seems to be correct. Can you post a complete example? Might be something else that is wrong.
Or atleast the output from HXL.Lexer.tokenize/1.

Oh and both <<-EOT and <<- EOT is allowed now, in the second example that you posted it skipped tokenize as a heredoc due to the space, which it should do now :).

The only difference is that you used tokenized while I am using devode_file
test.hcl
action "transform_data" {
  js = <<- EOT
    const output = { ...input, x: 1 };
    return output;
  EOT
}

hcl_parser.ex
defmodule HclParser do
  def parse do
    HXL.decode_file("test.hcl")
  end
end


Fix getAll repository use pagination

Hi,
I notice the $URL_registry/v2/_catalog only return the 100 first repositories.
So the purpose of this change is to extend the repository array until the pagination link is available.
test passed :)
Thanks

thanks!


Library is not indexed on klibs.io

https://klibs.io/faq states:

Libraries are added automatically within 24 hours if they meet the following criteria:

The library is open source and is available on GitHub.
At least one artifact is published to Maven Central.
At least one artifact is multiplatform must have kotlin-tooling-metadata.json.
At least one artifact's POM contains a valid link to the GitHub repository, either under "url" or "scm.url" example.

If you believe your library satisfies all criteria, yet it's still not available, please submit an issue.

From v0.2.0:

kotlin-tooling-metadata.json: https://repo1.maven.org/maven2/dev/sargunv/maplibre-compose/maplibre-compose/0.2.0/maplibre-compose-0.2.0-kotlin-tooling-metadata.json
POM: https://repo1.maven.org/maven2/dev/sargunv/maplibre-compose/maplibre-compose/0.2.0/maplibre-compose-0.2.0.pom

This project should already meet those criteria, so I'm not sure why it's not there: https://klibs.io/?query=maplibre
The issue might be some extra quotes in our POM, scm.url, fixed in https://github.com/sargunv/maplibre-compose/commit/cafae40f9ac04329a49b5b6b946b4e520fc734b2. Next release, we should verify if the library got indexed or not, and file an issue with klibs.io if not.

v0.3.0 fixed the extra quotes in the pom, but it's still not indexed. Filed issue here: https://github.com/klibs-io/issue-management/issues/32


fix: 1. fix component/table can not change pageSize

fix(ui): 1. fix component/table can not change pageSize,affect system/query profile/session page etc.
2. add antd Table Component missing rowKey property to fit react specification
2. fix system/query profile/session/configuration page maybe lead memory leak when switch these pages fast
3.other grammar fix to fit typescript and react specification
Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ - ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ - ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ - ] No
[ ] No Need

Does it need to update dependencies:

[ - ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ - ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

it mainly fix the pageSize can't be changed


WaterBulter problem

Hi
Would you please help me about this error, we are facing on WaterBulter
Raven is not configured (logging is disabled). Please see the documentation for more information.
[2016-08-30 10:33:36,548][INFO][raven.contrib.tornado.AsyncSentryClient]: Raven is not configured (logging is disabled). Please see the documentation for more information.
[2016-08-30 10:34:11,981][ERROR][tornado.application]: Uncaught exception GET /data?path=%2F&provider=osfstorage&nid=7wrgv&=1472578451945 (<IP_ADDRESS>)
HTTPServerRequest(protocol='http', host='localhost:7777', method='GET', uri='/data?path=%2F&provider=osfstorage&nid=7wrgv&=1472578451945', version='HTTP/1.1', remote_ip='<IP_ADDRESS>', headers={'Accept-Language': 'en-US,en;q=0.5', 'Host': 'localhost:7777', 'Origin': 'http://localhost:5000', 'Accept-Encoding': 'gzip, deflate', 'Connection': 'keep-alive', 'Accept': 'application/json, text/*', 'Cookie': 'osf=57c5bc03e1382318501bd337.dDn9bbzaaDZf7xkC3TpyWr1v7ZE', 'User-Agent': 'Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:48.0) Gecko/20100101 Firefox/48.0', 'Referer': 'http://localhost:5000/7wrgv/'})
Traceback (most recent call last):
File "/home/steve/git/waterbutler/lib/python3.5/site-packages/tornado/web.py", line 1424, in _execute
result = yield result
File "/home/steve/git/waterbutler/lib/python3.5/site-packages/tornado/gen.py", line 1008, in run
value = future.result()
File "/home/steve/git/waterbutler/lib/python3.5/site-packages/tornado/concurrent.py", line 232, in result
raise_exc_info(self._exc_info)
File "", line 3, in raise_exc_info
File "/home/steve/git/waterbutler/lib/python3.5/site-packages/tornado/gen.py", line 1014, in run
yielded = self.gen.throw(*exc_info)
File "", line 6, in _wrap_awaitable
TypeError: throw() takes 2 positional arguments but 4 were given

Hey @umardraz,
There's a bug in core python that makes WaterButler (and MFR) not work when Tornado server debugging is turned on.  See this page for instructions on how to disable it.
Also, if you run into issues with WaterButler or MFR please report it in their issue trackers.  I'm much more likely to see it if you post there.
Cheers,
@felliott


Refactor this issuer to use issuer-lib

This is the first open-source issuer that will start using this library.
This change greatly simplifies this issuer.

/retest

@SgtCoDFish I just had to add the ok-to-test label (see https://github.com/jetstack/google-cas-issuer?tab=readme-ov-file#continuous-integration).
In the future, we probably want to move this repo to the cert-manager org and use prow.


Make Client and Service decorator always override as() or serviceAdded()

Motivation:
If a user writes a decorator with curried lambda style,
the given decorator will not override as() or serviceAdded(). #1958
sb.service("/svc", myService.decorate(delegate -> (ctx, req) -> {
    ...
    return delegate.serve(ctx, req);
}));

The decorated service will not call ServiceCallbackInvoker.invokeServiceAdded() properly.
Modifications:

Add DecoratorUtil for validating decorators using reflection.
Add the validation logic to {Http,Rpc}Service.decorate(), ClientDecoration.*decorate(), RouteDecoratingService().

Result:
You can now get IllegalArgumentException when the specified decorator does not override as() or serviceAdded()
Fixes #1958

Is it not possible to define an interface with as to catch at compile time?

Is it not possible to define an interface with as to catch at compile time?

That sounds good. I'm not sure, but let me try whether it is possible. 😀

I've just realized this stops a user from using Function.identity() or other creative use of functions, like returning a completely different Client or Service which is not a decorator.
That means, I think we can't validate anything this way. :sob:

other creative use of functions, like returning a completely different Client or Service which is not a decorator.

Ah... I don’t think of that. That is important point.
I will close this PR. If we have another idea on this, will make a PR. 😀

Is it not possible to define an interface with as to catch at compile time?

Then a user can't write a service using a lambda expression.

@trustin Yeah I thought if the return value of the decorator lambda was an interface with as (which SimpleDecoratingService would implement) it'd be checked and allow the syntax in the attached issue. But anyways, sounds like there are other issues 😅


Handle title element in HtmlToWmlConverter

Put the title element value in the Title property in core props.

Closing all issues as this repo is being archived and will no longer be maintained by Microsoft. The project is licensed for continued use and development by forking to your own repo.


Redirect old docs links

See https://github.com/api3dao/api3-docs/issues/1244#issuecomment-2308980311

Closing since the upcoming docs reorg renders this moot


[BEAM-10681] Set metrics supported in Spark portable runner.

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Java Spark PortableValidatesRunner Batch

R: @annaqin418

LGTM


[Automation]  Code update update status check

There is a bug pointed out by @geissonator .
To JSON using : content={
"data": null,
"message": "200 OK",
"status": "ok"
}
The Response is part of the Get update attribute.. so this needs to be fixed.

Test in progress and code pushed for review


After the update, I opened ComfyUI and encountered this error code

File "E:\comonAI\ComfyUI_windows_portable\ComfyUI_windows_portable\ComfyUI\main.py", line 165, in
server.add_routes()
File "E:\comonAI\ComfyUI_windows_portable\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI_NestedNodeBuilder_init_.py", line 124, in add_routes_wrapper
add_routes(self)
File "E:\comonAI\ComfyUI_windows_portable\ComfyUI_windows_portable\ComfyUI\server.py", line 516, in add_routes
self.app.add_routes(self.routes)
File "E:\comonAI\ComfyUI_windows_portable\ComfyUI_windows_portable\python_embeded\lib\site-packages\aiohttp\web_app.py", line 334, in add_routes
return self.router.add_routes(routes)
File "E:\comonAI\ComfyUI_windows_portable\ComfyUI_windows_portable\python_embeded\lib\site-packages\aiohttp\web_urldispatcher.py", line 1200, in add_routes
registered_routes.extend(route_def.register(self))
File "E:\comonAI\ComfyUI_windows_portable\ComfyUI_windows_portable\python_embeded\lib\site-packages\aiohttp\web_routedef.py", line 76, in register
return [reg(self.path, self.handler, **self.kwargs)]
File "E:\comonAI\ComfyUI_windows_portable\ComfyUI_windows_portable\python_embeded\lib\site-packages\aiohttp\web_urldispatcher.py", line 1161, in add_get
resource.add_route(hdrs.METH_HEAD, handler, **kwargs)
File "E:\comonAI\ComfyUI_windows_portable\ComfyUI_windows_portable\python_embeded\lib\site-packages\aiohttp\web_urldispatcher.py", line 348, in add_route
raise RuntimeError(
RuntimeError: Added route will never be executed, method HEAD is already registered
E:\comonAI\ComfyUI_windows_portable\ComfyUI_windows_portable>pause
But After I removed your plugin, it opened normally,What is the problem？

Your error seems to be from: https://github.com/ssitu/ComfyUI_NestedNodeBuilder
And you look to be running an old version of that extension


feat(backing image): support backing image in spdk engine

ref: https://github.com/longhorn/longhorn/issues/6341

Implement BackingImage related API

BackingImageCreate
BackingImageGet
BackingImageDelete
BackingImageList
BackingImageWatch
BackingImageExpose
BackingImageUnexpose

We create BackingImage only in two ways

download from backing-image-manager URL with the HTTP request
sync from other spdk server

expose the src backing image
connect the src backing image and create a device
directly copy the content from the device to the temp head lvol device

Add backing image handling in verify() function

if there is record in the server already (Ready or Failed), we check if the lvol exists
If there is no record in the server, we reconstruct the record with the info stored in the lvol xattr

Add BackingImage *Lvol to the replica

When prepareHead, we add the BackingImage to the r.ActiveChain[0] and r.BackingImage
When node reboot, we add the BackingImage to the r.ActiveChain[0] and r.BackingImage in construct() function
This will be used when

backup: we check if r.BackingImage is nil to decide the compare snapshot range
engine: checkAndUpdateInfoFromReplicaNoLock() we check if replica contains the BackingImage to decide which  replica we are getting the info from

When RebuildingDstSnapshotRevert(),

if the snapshot is a BackingImage, the  backing image snapshot lvol name is from src node.
we need to reconstruct the backing image snapshot lvol name to the current disk

Fix replicaLvolFilter to allow getting the backing image lvol, because we would need it when building the newChain when validating or reconstructing. here

	// Check if the root snap/head lvol has a parent. If YES, it means that this replica contains a backing image
	var biSvcLvol *Lvol
	rootLvol := newChain[len(newChain)-1]
	if rootLvol.Parent != "" {
		// Here we won't maintain the complete children map for the backing image Lvol since it may contain root lvols of other replicas
		biBdevLvol := bdevLvolMap[rootLvol.Parent]
		if biBdevLvol == nil {
			return nil, fmt.Errorf("cannot find backing image lvol %v for the current bdev lvol map for replica %s", rootLvol.Parent, replicaName)
		}
		biSvcLvol = BdevLvolInfoToServiceLvol(biBdevLvol)
		biSvcLvol.Children[rootLvol.Name] = rootLvol
	}
	newChain = append(newChain, biSvcLvol)

cc @shuo-wu

@coderabbitai pause

Hi @derekbit
I temporarily add a snippet of code in verify() to check the head before deleting the record.
And as you can see, the unit test has passed.
		if bdevLvolMap[r.Name] == nil {
			logrus.Infof("[DEBUG] r.Name: %v lvol is nill", r.Name)

			r.RLock()
			head := r.Head
			r.RUnlock()

			if head != nil {
				continue
			}
....

Please take a look, and if there is no other comment
I can remove the debug and extra code to merge the PR first.
Thanks

This pull request is now in conflict. Could you fix it @ChanYiLin? 🙏

Fixed.

Hi @derekbit
Fixed the error handling in BackingImageExpose() and BackingImageUnexpose()
and also fixed the conflicts
PTAL, thanks

Hi @derekbit
I have fixed the comments, PTAL, thanks


Update tx with missing fields.

Tx lacks metadata/withdrawals/certificates fields #471.
Together with adding these I refactored script and datum witnesses out of inputs/etc into seperate maps [see #459 ].
Pre-submit checklist:

Branch

[ ] Tests are provided (if possible)
[ ] Commit sequence broadly makes sense
[ ] Key commits have useful messages
[x] Relevant tickets are mentioned in commit messages
[x] Formatting, materialized Nix files, PNG optimization, etc. are updated

PR

[x] Self-reviewed the diff
[x] Useful pull request description
[ ] Reviewer requested

This pr introduces these changes:
Changes
Redefines Tx type

Tx gets withdrawals, certificates(1), metadata(1) fields
script and datum witnesses get put into maps and refered to by hashes (related comment and issue )
redeemers get put together with the MintingPolicy/Certificate/Input (^ same links)
defines TxInput and TxInputType simmilar to TxIn and TxInType.
defines Withdrawal type
defines Certificate type
splits Ledger.Tx.Internal module

Updates pab accordingly

TxIn remains used by some functions only in auxiliary way
most changes are automatic: imports and minor updates that don't change logic only update the Tx
toCardanoTxBodyContent from Ledger.Tx.CardanoAPI gets updated with withdrawal translation (based on plutus-simple-model).

Updates purescript accordingly

code generation generates added types: Certificate, Withdrawal, TxInput, TxIn
minor tweak in purescript source code

Shortcomings
Certificate and Metadata is wrong for now (1)

DCert in Certificate has some data like StakePoolParameters in registration certificate digested. Best would be to reproduce cardano-api/Certificate but using plutus-friendly types.
Metadata is more like Map Word64 JSONLikeValue, definitely not bytestring. Best would be cardano-api/TxMetadata, but we can't use for example Word64 onchain, correct? We could reproduce cardano-api type using plutus-friendly types. Or leave metadata as bytestring, to be decoded by users (I don't like this).

What about plutus V2? i.e Should scripts in txScripts be annotated with versions?

EDIT: I see that script version was added to TxInType

Can you rebase from next-node branch? There are a lot of commits in here that are unrelated to the work done.

^ Yes, that was my mistake. I was baited by Tx moved inside plutus-ledger in next-node.
I rebased it on main. Still need to fix CI etc.

@zmrocze Just noticed a huge mistake on my part... It was actually okay and desirable for you to work on next-node. I had forgotten that the Tx is available in main branch, and was migrate only in next-node. So this PR is the right one. Really sorry about getting mixed up...

oh damn..
@koslambrou  I'll go about resolving conflicts here, hopefully not many. I'm close to resolving them as well in the main targeting branch, if thats relevant.
I would still need advice on:

what to use for DCert and Metadata types? Should we define in Ledger analogues of Cardano.Api types, just using Plutus friendly type analogues? Or use Cardano.Api types itself (not plutus friendly).

Maybe I could correct Metadata already in this pr, as I've seen someone having to use a fork with metadata added. But leave DCert for next pr already, not to leave this hanging for longer?
I've edited slightly the pr description above but it mainly remains up to date.

No, don't waste time on the main  branch. Let's stay on next-node unless you have a compelling reason why you would want it also on main.
For the types, let's use the ones from Cardano.Api. We're moving towards using that more and more.
And yeah, I would agree to add Metadata only in this PR, and add DCert in a separate one.

@koslambrou  I think its ready for review.
I had to reset back to commit without TxMetadata used in Tx as I need help fixing:
[1/1 ModuleNotFound] generated/Ledger/Tx/Internal.purs:6:1

  6  import Cardano.Api.TxMetadata (TxMetadata)
     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  Module Cardano.Api.TxMetadata was not found.
  Make sure the source file exists, and that it has been provided as an input to the compiler.

that is plutus-playground-cllient/default.nix:generate-purescript needs Cardano.Api as input and I am not fluent with nix enough to fix it.
What is left after that pr:

Add constraints in plutus-ledger-constraints concerning Withdrawals, Certificate, Metadata (functional constraint)
Swap DCert in the txCertificates field of Tx for i.e. cardano-api/Certificate.
Use cardano-api TxMetadata in txMetadata field of Tx
TODO: Implement ToSchema TxMetadataValue
TODO: Parse certifying redeemer., TODO: Parse rewarding redeemer., TODO: ToJSON rewarding/certifying Redeemer.

Though I think its right to review it already as by its nature it modifies code all over the place and at merges there is a flood of nontrivial merge conflicts.
Initial pr description applies. I tried keeping stuff in Ledger/Tx/Internal.hs this time.

Your PR includes commits that shouldn't be there. Did you do git pull --rebase origin next-node?

I started from next-node when it was WIP pr. Then merged next-node to stay updated. Can git squash in the end

Hey @koslambrou @ak3n, what is the plan with this pr?
I've fixed requested bits and can update it again if you are ready. Is there something more fundamentally wrong in the changes? If so let's discuss it as well (there's some suitable issues linked at the top).
As to splitting it into smaller pr's - to me this seems like unnecessary work, I'd prefer not to do it. I'll summarize changes in squashed commit, is it alright?

Conflicts need to be fixed first, then CI needs to pass.
And yes, please summarize the changes in the squash commit.

given how long lived this branch is I can't reasonably squash the commits. Doing so results in conflicts with next-node which were resolved already. I know it took long, sorry

Here's a description of changes if that's needed:
Add missing fields to Tx.

  * Add certificates and withdrawals to Tx.

  * Move script witnesses to txScripts.

  * Modify TxIn type, rename to TxInput.

  * Put redeemers together with minting scripts.

  * Translate withdrawals in toCardanoTxBody.

  * Export redeemers for signing with wallet.


Allow memberOf attribute on OpenLDAP

Currently, the memberOf attribute is only used on AD.
OpenLDAP has also support for this attribute.

Hello,
This request is stale for too long. Regarding our policy to cleanup this project, we're closing it. Feel free to open a new issue later.
Also, note that there is a filter field in the latest versions that allow you to write any LDAP filter, including memberOf.
Regards
PowerDNS Admin Team
See https://github.com/PowerDNS-Admin/PowerDNS-Admin/issues/1153 for the policy


Unable to read modbus on V3

I've installed the latest V3 yesterday and the hardware is working great.
Only problem I currently have is to read the modbus registers.
Regardless if what register I try to read, I always get the exact same response:
21:04:19:482 > 00 49 00 00 00 06 01 03 00 02 00 01  21:04:20:509 < 00 49 00 00 00 06 0A 04 00 00 00 14  21:10:18:578 > 00 4A 00 00 00 06 01 03 00 04 00 01  21:10:20:513 < 00 4A 00 00 00 06 0A 04 00 00 00 14  21:10:47:492 > 00 4B 00 00 00 06 01 03 00 0A 00 01  21:10:48:516 < 00 4B 00 00 00 06 0A 04 00 00 00 14  21:10:52:844 > 00 4C 00 00 00 06 00 03 00 02 00 01  21:10:54:510 < 00 4C 00 00 00 06 0A 04 00 00 00 14
Besides the response always being exactly the same, the value '0A 04 00 00 00 14' can be found on the Sensorbox documentation (see the example below the page):
https://github.com/SmartEVSE/Sensorbox-2
So am I doing something wrong? Or is the modbus implementation changed in V3?
Additional info:

tried both modbus and modbus rtu
sensorbox is connected with the P1 of my digital meter
no kWh meter
I use a waveshare device to read modbus over tcp

@mstegen  I was also trying to get modbus to work to no avail, glad I found this issue in time. I'm in need to control the evse to work together with other devices consuming power, the evse without this feature to control it via any form of external api is a step backward for me.
This feature was in v2 right? Can we perhaps flash v2 on the v3 device in the meantime?
Also, any other option of more high level communication than raw modbus (like a TCP or MQTT bridge) would be a huge step forward. If that is easier to implement than fix the modbus support than that would also be OK !
Would it be possible to give an ETA on this please as I'm really blocked atm wit this. Thanks!

I have ported v2 software to v3 hardware, but the ESP32 is completely different from the PIC which was used on v2.
The modbus code on v2 was written from scratch, on v3 i'm using a library, mainly because low level access to the uarts on the ESP32 (while running RTOS) is difficult.
Until a few weeks ago it was for example not (?) possible to get a callback when new data was received by the uart.
You had to check for new data continuously in a loop. This is how the eModbus library determines there is new data.
10 days ago they added support for a callback (https://github.com/espressif/arduino-esp32/pull/6364)
Hopefully it will get added to a stable arduino core release soon.
But in the mean time, i'll see if i can run the modbus master and node/slave processes at the same time.
That would most likely fix this issue.

Ok that would be great!
Another idea maybe, if running both processes would not be possible, is to have some kind of minimalistic firmware just driving the cp pwm and offer a modbus master for comms (or if possible a higher level tcp/mqtt bridge, who needs modbus anyways). This firmware could then be used by people controlling loadbalancing and/or power management themselves instead of relying on the evse/sensorbox.

I tested to run both the master and node processes, but that did not work.
So for now the only way to get it to work with a external master controller, is to configure the controller(s) as a Node, and send the required commands.
In order to keep each node happy, and not timeout with a comm-error you will have to send the chargecurrent for each node in a broadcast message to all nodes (address 09):
09 10 00 20 00 08 10 00 A0 00 00 00 3C 00 00 00 00 00 00 00 00 00 00 99 24
Node 0 00 A0 = 160 = 16.0A
Node 1 00 00 = 0 = 0.0A
Node 2 00 3C = 60 = 6.0A
etc.

Each time this message is received on each node, the timeout timer is reset to 10 seconds.
The master will usually send this message every two seconds.
This is all what is required to prevent the communication error.
To have full control over the nodes, you will have to read each node's status registers, and see if it requests to charge.
for example for node 2:
Received packet (21 bytes) 03 04 10 00 01 00 00 00 3c 00 01 00 00 00 01 00 01 00 20 4d 8c
00 01 = state B
00 00 = no errors
00 3c = charge current 6.0 A
00 01 = Smart mode
etc.

Here the state changes to STATE_COMM_C (00 06)
Received packet (21 bytes) 03 04 10 00 06 00 00 00 3c 00 01 00 00 00 01 00 01 00 20 0a 8e
So the ESVE request to charge.
You can respond to this request by changing the state of the node to State_C
03 10 00 00 00 02 04 00 07 00 00 49 D6
Here it will write 00 07 (STATE_COMM_C_OK) to register 0x0000, and reset the error register 0x0001
The node will respond to this by switching to STATE_C (Charging).

As I am now able to add an API endpoint to read and control the data I need, this feel like the better way to move forward.
So for me need anymore to access the EVSE through the modbus interface, not sure what the others their opinion is on this.


Update app.py to show sgv via workaround

As per @renegadeandy pull request https://github.com/renegadeandy/oref0/pull/1
just tested it and it works nicely, so making PR for Dev.

I don’t use the enlite and haven’t been closely following this issue. Can someone fill me in on what testing has been done to confirm this fixes the issue and doesn’t cause any issues for non-enlite users?

I don’t use the enlite and haven’t been closely following this issue. Can someone fill me in on what testing has been done to confirm this fixes the issue and doesn’t cause any issues for non-enlite users?

Hi, i wasn't aware this was enlite related, or at least it isn't for me.
We're using Dexcom G6, Edison and a Medtronic 715 pump.
I've got two rigs running, one using xdrip+ (overnight) and the other xdrip-js (daytime). And neither local webpages have shown sgv data from nightscout since I've been using OpenAPS. The xdrip-js one does work via Logger if the rig is in range/carried around.
I added the line to both rigs last night and the xdrip+ one has worked, but i see the xdrip-js one hasn't.
I've not done any further testing, perhaps this should be an issue?
Screenshots from this morning, left picture is xdrip-js:

Hi, i wasn't aware this was enlite related, or at least it isn't for me.
We're using Dexcom G6, Edison and a Medtronic 715 pump.
I've got two rigs running, one using xdrip+ (overnight) and the other xdrip-js (daytime). And neither local webpages have shown sgv data from nightscout since I've been using OpenAPS. The xdrip-js one does work via Logger if the rig is in range/carried around.
I added the line to both rigs last night and the xdrip+ one has worked, but i see the xdrip-js one hasn't.
I've not done any further testing, perhaps this should be an issue?
Screenshots from this morning, left picture is xdrip-js:

Sorry, I confused it with another issue. So this only affects the “offline” web page display on the rig?

Sorry, I confused it with another issue. So this only affects the “offline” web page display on the rig?

to confirm, yes only affects the offline webpage.

to confirm, yes only affects the offline webpage.


iPhone strange css bug

On the iPhone, the numbers are temporarily displayed mirror-inverted when rotating. I suspect here a css property is not supported.

I have found the problem. In the .css file the animation of the rotating digits is defined in keyframes. There is an anination for the upper part (hide old digit) and an aniation for the lower part (show new digit). The visibility is controlled by z-index, which leads to problems with animations in Safari.
My solution is certainly not pretty, but seems to work (tested also on Android and Windows Chrome/Firefox). Instead of z-index I used opacity to control the visibility:
@keyframes countDown_flip_1{
	0%{transform:rotateX(0);opacity:100;}
	50%{transform:rotateX(-90deg);opacity:100;}
	51%{transform:rotateX(-90deg);opacity:0;}
	100%{transform:rotateX(-180deg);opacity:0;}
}
@keyframes countDown_flip_2{
	0%{transform:rotateX(0);opacity:0;}
	50%{transform:rotateX(-90deg);opacity:0;}
	51%{transform:rotateX(-90deg);opacity:100;}
	100%{transform:rotateX(-180deg);opacity:100;}
}


Rewrite the view rendering

Maybe use urwid. At least do something to avoid redrawing the entire view.

Started trying this out with Urwid. Needs some work, but prob won't happen for a while since I just started a new job.

What's the status on this?


Button Shows Logging In or register although it fails in Validation

Hi, this issues will be set to public and available on v0.1.4 - Alpha. Thanks!


Resizable handlers incorrectly resizing

As you can see in the gif above, resizing with handles on the top or right do not work as expected. They should also edit the x and y properties of the item, not just the width and height.
See the new example (17, resizable handles). Seems like the following link (https://strml.github.io/react-grid-layout/examples/17-resizable-handles.html) is not working, I believe you have to upload the built examples.

I'm experiencing the same issue as @LorenzHenk . I've set the resizeHandles to "sw" and "se" and in my case "sw" is not behaving like I expect it to. I would expect it to 'expand' to the left when I move my mouse to the left. Also, the mouse cursor on Mac isn't correct (and different from what @LorenzHenk shows in his animation). On Mac it's the same arrow pointing to bottom right as with the SE handle.

Another thing that would be nice, but maybe this is more of a feature request, is that handles only appear if expanding is possible in that direction. So "SE" would only appear if the item isn't already 'docked' to the far right, and "SW" would only appear if the item isn't docked to the far left.

Also, the mouse cursor on Mac isn't correct (and different from what @LorenzHenk shows in his animation). On Mac it's the same arrow pointing to bottom right as with the SE handle.

I do have this problem as well. It doesn't appear in my recording, because for the recording I modified an official example. The examples have different styles applied. In the example styles, the cursor is set correctly.
In the actual styles, the other cursors are not styled differently.
I'll create a PR for the cursor styles problem.

Another thing that would be nice, but maybe this is more of a feature request, is that handles only appear if expanding is possible in that direction. So "SE" would only appear if the item isn't already 'docked' to the far right, and "SW" would only appear if the item isn't docked to the far left.

Don't forget about shrinking. This would only make sense if the item size was the minimum allowed size. Else you could still use the handle to shrink the item.
Excerpt from the issue template:

Please only submit bugs to this tracker. If you have a feature request, please implement it. This is free software and the author is busy with other projects.

So let's please keep the focus of this issue on the original bug I've reported :grin:

Also, the mouse cursor on Mac isn't correct (and different from what @LorenzHenk shows in his animation). On Mac it's the same arrow pointing to bottom right as with the SE handle.

I do have this problem as well. It doesn't appear in my recording, because for the recording I modified an official example. The examples have different styles applied. In the example styles, the cursor is set correctly.
In the actual styles, the other cursors are not styled differently.
I'll create a PR for the cursor styles problem.

That's awesome!

Another thing that would be nice, but maybe this is more of a feature request, is that handles only appear if expanding is possible in that direction. So "SE" would only appear if the item isn't already 'docked' to the far right, and "SW" would only appear if the item isn't docked to the far left.

Don't forget about shrinking. This would only make sense if the item size was the minimum allowed size. Else you could still use the handle to shrink the item.

You're absolutely right. It's more than just looking at growing, it's also about shrinking which probably makes it more complex to solve this.

Excerpt from the issue template:

Please only submit bugs to this tracker. If you have a feature request, please implement it. This is free software and the author is busy with other projects.

So let's please keep the focus of this issue on the original bug I've reported 😁

Thanks for pointing that out. To be honest, I wasn't exactly sure if this could be part of the bug. I was hoping that maybe this was already implemented but somehow failed due to the issue you described.
Thanks for your reply! And by the way to all the devs: awesome library...

Hi everyone. This is going to be a difficult bug to tackle, as resizing was never meant to change the position of an item, which is always determined by top-left grid units. Fixing this requires a rework of resizing entirely. Perhaps there is an elegant way to do so, perhaps there is good impetus here to refactor resizing and dragging and compacting into Interfaces that can then be pluggable as in #346.

As the plugin system you mentioned does not yet exist (correct me if I'm wrong), I guess focusing on fixing the bug has priority over creating said plugin system.

Can anyone tell if there is any update on this issue ? I am experiencing the same thing.

I'm having the same issue. Was this never taken care of?

Is there a solution for this problem? 🤔
Thank you in advanced!

lol it's december 27 and I just got a ticket open for this exact same bug 😅

Top and left resizing was fixed in #1917


Permission denied in devenv ci

Describe the bug
I've created a custom pre-commit hook that uses poetry:
entry = "${pkgs.poetry}/bin/poetry run pytest .";

When running pre-commit run --all-files this works, but when I try to run devenv ci I get the following exception:
[Errno 13] Permission denied: '/private/tmp/nix-build-pre-commit-run.drv-0/src/.venv/bin/pytest'

Solution as mentioned on discord

oh yeah, we should wire up venv for devenv ci

The issue here is that we run devenv ci in a Nix derivation that doesn't have access to networking.
We'll need to design it differently to work with features like venv and poetry.

1.0 ships https://devenv.sh/tests/, which goal is exactly to fix this.
devenv ci is now deprecated.


Multi Account Support

I would like to configure more than one Spotify account at the same time. This was possible using the original Spotify plugin for Squeezebox but seems to be impossible using spotty.
Do you have any plans to support more than one account in the future?

Multi-account management has been part of the Spotty plugin from very early on. Just go to the settings screen and add another account.

Thanks for pointing out! Awesome news. :) Maybe it is worth having an "Add Account" menu item in the device UI that points out how to add another account (e.g. "Go to web config and add an account there")?

I'm not planning to enhance the player menu, as most users in multi-user environments seem to prefer the Connect mode anyway.

What's the connect mode?

You can have Spotty announce your SB players as Spotify Connect endpoints. They will then show up in the Spotify apps and desktop applications as devices you can play on. This means you'd control your SB from the Spotify app, rather then the LMS environment.

https://www.spotify.com/connect/

Thanks for your explanation! Now I enabled this feature as well. Did not see it before.


segfault when launching LimeSuiteGUI

Version: limesuite17.12.0-myriadrf~artful, liblimesuite17.12.0-myriadrf~artful)
the problem occurs, when launching LimeSuiteGUI or any application that uses gr-osmosdr + soapy
LimeSuiteGUI crashes with the following error:
traps: LimeSuiteGUI[23171] trap invalid opcode ip:55b59092a78f sp:7fff70dd8fd0 error:0 in LimeSuiteGUI[55b590803000+2f3000]
LimeUtil can perform an FPGA update without problems
CPU: Intel i5-7400. works perfectly on a i5-5300U though
OS: Ubuntu 17.10
kernel: 4.13.0-21-generic

I can confirm, I upgraded to 17.12.0-myriadrf~artful myself yesterday and everything that tries to use the radio crashes with an illegal instruction error. An easy reproducer is "LimeUtil --timing".
andrew@goron:~$ gdb LimeUtil
GNU gdb (Ubuntu 8.0.1-0ubuntu1) 8.0.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from LimeUtil...(no debugging symbols found)...done.
(gdb) set args --timing
(gdb) run
Starting program: /usr/bin/LimeUtil --timing
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff62e2700 (LWP 27446)]
[New Thread 0x7ffff5ae1700 (LWP 27447)]
[New Thread 0x7ffff52e0700 (LWP 27448)]
Connected to [LimeSDR-USB, media=USB 3.0, module=STREAM, addr=1d50:6108, serial=0009060B00471F18]
Estimated reference clock 30.7198 MHz
Reference clock 30.720 MHz
Creating instance of LMS7002M:

Timing basic operations:
  >>> SPI write register:       137.237 us
  >>> SPI read register:        138.752 us

Thread 1 "LimeUtil" received signal SIGILL, Illegal instruction.
0x00007ffff7b500d5 in lime::LMS7002M::GetFrequencyCGEN() () from /usr/lib/x86_64-linux-gnu/libLimeSuite.so.17.12-1
(gdb) bt
#0  0x00007ffff7b500d5 in lime::LMS7002M::GetFrequencyCGEN() () from /usr/lib/x86_64-linux-gnu/libLimeSuite.so.17.12-1
#1  0x00007ffff7b50100 in lime::LMS7002M::GetReferenceClk_TSP(bool) () from /usr/lib/x86_64-linux-gnu/libLimeSuite.so.17.12-1
#2  0x00007ffff7b5033e in lime::LMS7002M::SetNCOFrequency(bool, unsigned char, double) () from /usr/lib/x86_64-linux-gnu/libLimeSuite.so.17.12-1
#3  0x0000555555559bb7 in ?? ()
#4  0x0000555555558815 in ?? ()
#5  0x00007ffff6f9b1c1 in __libc_start_main (main=0x555555557170, argc=2, argv=0x7fffffffda98, init=<optimized out>, fini=<optimized out>,
    rtld_fini=<optimized out>, stack_end=0x7fffffffda88) at ../csu/libc-start.c:308
#6  0x0000555555558d7a in _start ()
(gdb)

Given the location of the crash, I have some suspicion of https://github.com/myriadrf/LimeSuite/commit/12108cf5af6274e938e9a78597a459258dd4496a being involved, but also maybe compiler flags? It's an odd one.

I'm seeing this too, definitely odd. But its not happening when I build the same debs manually on artful. It may be a flags issue or something odd in the PPA build environment. I will probably try rebuilding just in case it was an accident on a particular PPA build machine.

So -march=native can be issue when packaging for x86 when you want the binaries to work across many SIMD architectures. This commit should address this issue: https://github.com/myriadrf/LimeSuite/commit/305ac5d3aed5f0f280d73860dcbbc40d63b3d6ee and I have uploaded a new build for artful. Happy new year!

Thank you and happy 2018! I upgraded using apt to <IP_ADDRESS>.305ac5d-myriadrf1~artful and I can confirm everything working fine.

Yea, it was a tricky bug, but we should be good going forward.


Get the id from new seeAlso format

closes pulibrary/figgy#6329

deployed this to staging and it successfully indexed the performances collection (held 4 items before this PR; matches production after this pr with 762) https://dpul-staging.princeton.edu/performances/catalog?utf8=✓&exhibit_id=performances&search_field=all_fields&q=


Update sql-server-linux-performance-best-practices.md

@krishnamsft20 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks @krishnamsft20! I'll approve this.
#sign-off

@VanMSFT: I'm sorry - only the author of this article, @tejasaks, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


How about making a library out of it?

Hello,
Thanks for your valuable extension. I copy-pasted the code in my project.
I was wondering why you didn't make a library out of it?
Cheers

Regarding the ones here, those were prototypes for inclusion in JUnit Jupiter, but we (the JUnit 5 team) decided not to include them.
If you're referring to the @CaptureSystemOutput support, that has recently been implemented in Spring Boot 2.2.
I am therefore closing this issue; however, if the above does not answer your question, feel free to provide further input here.
Thanks

Thanks @sbrannen, I was talking about the CaptureSystemOutput. So I'll wait for Spring Boot 2.2 to be released, then I can use the OutputCapture rule.


Update chart grafana to 7.3.2

This PR contains the following updates:

Package
Update
Change

grafana (source)
patch
7.3.1 -> 7.3.2

Release Notes

grafana/helm-charts (grafana)
v7.3.2
Compare Source
The leading tool for querying and visualizing time series and metrics.
What's Changed

[grafana] autoMount set to false in values.yaml by @Sheikh-Abubaker in https://github.com/grafana/helm-charts/pull/2977

Full Changelog: https://github.com/grafana/helm-charts/compare/grafana-7.3.1...grafana-7.3.2

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


fix(AutoControlledComponent): replace startsWith call

Fixes #733
There was a ''.startsWith() call in AutoControlledComponent.  We use _.startsWith instead for browser support.  This PR replaces the native string method with the lodash util.

Current coverage is 99.48% (diff: 100%)

Merging #745 into master will not change coverage

@@             master       #745   diff @@
==========================================
  Files           132        132
  Lines          2122       2122
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           2111       2111
  Misses           11         11
  Partials          0          0

Powered by Codecov. Last update cb7fffa...d14953e


Multiline Text Field

Hello, I would like to use the library however I did not see an attribute or definition for textarea or htmleditor type fields, could you please let me know if there is any or how we can implement?
Thank you.

Hi,
It is not supported yet, but I think we can add it in the nearest update

Hello, we have published version 1.3.3 PR #55.
You can enable multiline text editor in such a way:

 endpoints.MapEasyData((options) => {
    .     .      .     .    .
    options.UseModelTuner(model =>
    {
        // Find attribute by id (EntityType.PropertyName pattern)
        var categoryDesc = model.FindEntityAttr("Category.Description");
        // set default editor for its attribute
        categoryDesc.DefaultEditor = new TextValueEditor($"TVE_MULTI_{categoryDesc.Id}")
        {
            Multiline = true
        };
    });
});

P.s. There is a small problem with styles for the textarea. We will resolve it in the next update


Class decorator doesn't work for models created in setUpTestData

Thanks for a very useful library, it fits what I need perfectly. I'm trying to run some tests on a model instance that is created and has a file added in setUpTestData(). The whole test class is decorated with @override_settings().  If I drop into PDB during one of the test methods, the FieldFile object has the original name and it's storage attribute is a LocMemStorage object but the storage doesn't contain the file, ie, my_file.storage.exists(my_file.name) returns False.
If I shift all the file saving from setUpTestData() to the test method then it works as I expect: the storage contains the file.
Is this a supported pattern for building test data?

I've never tried to create any files in the setUpTestData() method but there are probably two problems I can see. The first is the underlying machinery. override_storage uses django's TestContextDecorator (https://github.com/django/django/blob/master/django/test/utils.py#L323) to get similar behaviour to override_settings. Unfortunately, TestContextDecorator wraps setUp() which is called after setUpTestData().
The second is test case isolation. In LocMemStorage and StorageTestMixin there is no notion of a 'snapshot' of what files were around before the test or the ability to roll back to that state at the end of the test. You can create storages which persist files across all tests so you may be able to combine a modified LocMemStorage and StorageTestMixin to make something that is created before setUpTestData() and gives you snapshot behaviour in setUp and tearDown.

Thanks for speedy response. I think I will just accept that's the way it works and use setUp() as necessary.


Translation Issue: "Caixxa".

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[x] Correction or update

Details

Hi guys!
In the image below shows the word "Caixxa", written with double "x". On Brazilian grammar the correct must be "Caixa".

URL: https://developer.mozilla.org/pt-BR/docs/Tools/Network_Monitor

Apologies, but we are not accepting changes to this locale right now; see https://github.com/mdn/translated-content#tier-1-locales for an explanation of which locales are currently active, and why. https://github.com/mdn/translated-content#promoting-an-inactive-locale-to-tier-1 is also useful.


Fixes ingress support for Google Container Engine

The latest 1.0.0 commit broke ingress support on GKE. In short, GKE requires the container to export the port it uses for readinessProbe in order for the ingress's healthcheck to properly create.
Previous versions of this Chart exposed port 3000 on the container but the latest commit changed to only export  {{ .Values.service.port }}
This PR fixes the problem exposing port 3000 too.
See more details here:
https://stackoverflow.com/questions/44584270/how-to-get-a-custom-healthcheck-path-in-a-gce-l7-balancer-serving-a-kubernetes-i

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:

@rjkernick done

/assign

/ok-to-test

/lgtm

/lgtm


GH-34509: [C++][Parquet][Docs] Fix comment for ArrowReaderProperties::batch_size

Rationale for this change

Fixing document for ArrowReaderProperties::batch_size.
What changes are included in this PR?

Update document in ArrowReaderProperties::batch_size
Are these changes tested?

no
Are there any user-facing changes?
no

Closes: #34509

@XinyuZeng @wgtmac Mind take a look?

@pitrou would you mind take a look at this? Just a document update, because ArrowReaderProperties::batch_size just works on interfaces about RecordBatch, like async generate record batch, or RecordBatchReader


Support setting ImagePullPolicy for session images

Would be great to have.
Currently this is not possible in
https://github.com/rstudio/helm/blob/dd607de994a5810d662e1a1d7287feeeddc9e0c6/charts/rstudio-workbench/values.yaml#L9-L18
Would be great for rolling tags when using custom images.

I have improved documentation here: https://github.com/rstudio/helm/tree/main/charts/rstudio-workbench#rstudio-profiles

Thanks, I'll try again soon! So far I couldn't get it working but happy to give it another try 👍  Thanks for the new descriptive examples.

Seems to work now 🥳
(Actually I don't know why, I haven't changed this code part since I last checked but I've deployed multiple versions of the same tag today and each time the newest session image was downloaded).

Good to hear things are working for you! Let us know if you run into this again - we are working on a way to make it a bit easier to set config settings like this for session images, so hopefully that will make life easier in the future!


npm start error

Since my comments were locked on a previous issue #458, I will post my reply here.
Well obviously I am reading that page as it is the next step in your tutorial unless you have a different page than the entire world wide web. What part of I followed every step of the tutorial do you not understand.
First you go to this page to install the puffer panel:
http://www.pufferpanel.com/v0.7.6/docs/how-to-install
Then the next obvious step would be to go to the node instillation page here:
http://www.pufferpanel.com/v0.7.6/docs/adding-a-new-node
Oh wait that is the same page that you posted.  There is something wrong with your tutorial and or your program. I am asking for help in installing this program and that is it.  If this tutorial is so easy please install a fresh version of Ubuntu 14.04lts and install pufferpanel exactly how the tutorial says and not use your knowledge of the dependencies that are required. Just follow the tutorial and type everything out just like I did.
By the way the next "DEV" version is v.0.8.0 and it does not have any documentation as you said in a previous post.

Your first issue was because you installed v.0.1.5 of GSD, which is not PufferPanel. I pointed you to the documentation for installing the correct version of GSD (v0.1.4) for PufferPanel v<IP_ADDRESS>, as is mentioned in the documentation.
The documentation above is correct and we have installed it ourselves following that documentation, as well as countless others. There is no documentation out for v0.8.0 of PufferPanel because it is not released, and we want to avoid any confusion. Additionally, since it isn't even done, we don't know what all we even need to be documenting for it yet.

 I don't know what it is going to take to make you understand that there is something wrong with either your tutorial or your program. Time to take it all down and check your code. Somewhere you or your devs made a mistake and its the public's fault because we followed your tutorial. Good luck with your broken program and or tutorial.

Thank you for letting us know where you think the error is so that we can fix it...
You keep saying the documentation is wrong and that we are shorty devs without providing any context for what the problem is.

Thank you for the response, I assumed that when I stated in every post I made that I followed your tutorial that something might clicked. If I have installed GSD v. 0.1.5 then it is obviously wrong with your tag as I typed in the git command exactly as it is on your tutorial. I apologize if I was rude but you made it seem like I did sometging wrong when I followed your tutorial to the letter, instead of saying hey can you check this or hey maybe we linked the wrong file to that tag. I like the looks of this panel and my company may be interested in using this panel or at least beta testing it. Again all I am asking for is a little help in installing the program and getting it working to test it.

I'd be happy to help, can you go ahead and tell me what error you are currently getting? Thanks!

The error I am getting is in the very first post of issue 458. You said I have installed the wrong GSD, now I am not sure where to get the correct GSD as I typed in this command.
cd /srv && git clone https://github.com/PufferPanel/gsd.git
git checkout tags/0.1.4
That is the command taken form the install node page of the tutorial and the command I typed in. I don't know if your tag links to the newer version of GSD or not, that is why I am asking you for help.

git rev-parse HEAD
Run that. Give us the code it prints out.

Thank you for the trouble shooting tip. I ran the command you gave me and the output is as follows:
1004e232516553166879f9b9ea68d0866e513baa
Also I can test the install tutorial again now that it has been updated. Would it be better if i reinstalled the server with a fresh copy of Ubuntu to test?

You should be fine to just run cd /srv/gsd && git checkout tags/0.1.4 which should get you running with the correct stuff.

Thank you I will run those command in a moment

Well by using the commands you provided did not work. What I wound up doing was rm -rf /srv/gsd to remove the entire gsd folder and started over. The new tutorial worked and it started up and the panel found the node. Well done on the solution.
One last question, can the gsd be run as a service and or under /etc/init.d? If not are there plans to create a script for either  methods?

Glad you got things working. I don't believe anyone has written an init script for GSD yet, but with Scales replacing GSD soon I'll make sure we have one for Scales when it's ready.

You could also look into using forever for now.

That looks like a good alternative than using screen. I see that there is a monitor for it as well. Thanks for the suggestion, I look forward to seeing what you guys come up with in the next version.


Skip deleting non existent file

On shared filesystems like NFS some file operations may create .nfsXXX cache files. This files are visible to the opencast process but should be managed by NFS subsystem itself. The WorkingFileRepository put-operation tries to delete these files as shown in the exception trace below. The delete operation return false as the file was moved/removed at this point. This is fine and not an error.
Exception:
2023-08-17T13:17:55,680 | WARN  | (SchedulerRestService:967) - Error updating event with id 'c04165a6-2f72-408c-a671-4edbd0bda5ce'
org.opencastproject.scheduler.api.SchedulerException: java.lang.IllegalStateException: Unable to delete file: /srv/opencast/files/mediapackage/c04165a6-2f72-408c-a671-4edbd0bda5ce/d0c7fcfe-5a4b-4a2b-ab26-b26c1c2b9f4e/.nfs000000002a1a014f00000008
	at org.opencastproject.scheduler.impl.SchedulerServiceImpl.updateEventInternal(SchedulerServiceImpl.java:844) ~[!/:?]
	at org.opencastproject.scheduler.impl.SchedulerServiceImpl.updateEvent(SchedulerServiceImpl.java:659) ~[!/:?]
	at org.opencastproject.scheduler.endpoint.SchedulerRestService.updateEvent(SchedulerRestService.java:961) [!/:?]
	...
Caused by: java.lang.IllegalStateException: Unable to delete file: /srv/opencast/files/mediapackage/c04165a6-2f72-408c-a671-4edbd0bda5ce/d0c7fcfe-5a4b-4a2b-ab26-b26c1c2b9f4e/.nfs000000002a1a014f00000008
	at org.opencastproject.workingfilerepository.impl.WorkingFileRepositoryImpl.put(WorkingFileRepositoryImpl.java:438) ~[?:?]
	at org.opencastproject.workspace.impl.WorkspaceImpl.put(WorkspaceImpl.java:682) ~[?:?]
	at org.opencastproject.scheduler.impl.SchedulerServiceImpl.updateDublincCoreCatalog(SchedulerServiceImpl.java:1663) ~[!/:?]
	at org.opencastproject.scheduler.impl.SchedulerServiceImpl.updateEventInternal(SchedulerServiceImpl.java:799) ~[!/:?]
	... 130 more

Your pull request should…

[ ] have a concise title
[ ] close an accompanying issue if one exists
[ ] be against the correct branch
[ ] include migration scripts and documentation, if appropriate
[ ] pass automated tests
[ ] have a clean commit history
[ ] have proper commit messages (title and body) for all commits

Tested successfully on an affected system.


Feature request to remove old version PRs amongst newer version PRs

Apologies if this issue is a duplicate. It's not the most simplistic thing to search for without spending a helluva lotta time eyeballing, but:
I tend to have some long intervals before checking greenkeeper prs in my repos. By that time, I may have a PR open for Package A version 1.0.2, and another PR for Package A version 1.0.3. It would be nice if greenkeeper was able to close out the older version PR automatically.

The new integration method continuously updates a single PR instead of creating a new PR for each version.


Additional parameters for GET queries and documentation of use vs. POST/schemas

As per various discussions, using GET request seems a rather widely used concept with implementers (rapid UI integration w/o need of using specific frameworks; easier documentation, examples, testing etc.). In fact, while we also implement POST in parallel, for Progenetix so far we rely on GET.
I would propose that we provide an extended matrix for parameters in GET queries. Examples here are

includeDescendantTerms - this can in POST be provided per filter but works for "medium complex use cases" as a global parameter
requestedGranularity, includeResultsetResponses - simple globals, but need to be documented that they can be used in GET
requestedSchemas - could be supported as resolving to entityType?
...

IMO it would be much easier for many implementers to see such parameters as simple query parameters, and then the comparable documentation of the POST schemas.
Also see https://github.com/ga4gh-beacon/beacon-framework-v2/issues/43

Is your suggestion about adding these parameters to the endpoints.yaml files?


Determinate Nix installer

Is your feature request related to a problem? Please describe.
When I started fiddling with Nix on macOS, my initial experience was quite horrible. I quickly made my setup barely usable and wanted to start over, only to be met with a plethora of problems when I tried to perform a complete uninstall.
It's way too easy to unwittingly enter a hellscape of your own creation. Here's what NOT to do, as evidenced by my struggles:

Install nix using the official installer.
Install nix-darwin, fiddle with random flakes and break stuff until you don't even know how to get out of the mess you've created.
Uninstall nix using the official guide, hoping that you'll be able to start over. There are quite a few steps, and one of them involves editing fstab, so you better be careful. At this point I was sweating bullets, not fun.
Try to reinstall nix, only for the installer to fail, because you didn't uninstall nix-darwin first.
Nix-darwin cannot be uninstalled using the script they provided, because nix-build is no longer available. Good luck, you'll need it.

Once I managed to piece my OS back together, I reinstalled Nix using the Determinate Systems installer:

It provided me with an uninstall script, so I wouldn't have to jump through multiple hoops in case I wanted to start over.
It's also aware of existing nix-darwin installations and refuses to proceed if it detects one, so a beginner will have a much harder time bricking their setup.
Oh, and the installer enables flakes by default, which is neat.

Describe the solution you'd like
My experience with Nix on macOS would've been much smoother if I'd used the DS installer right off the bat. I think it deserves a mention alongside nix-darwin-kickstarter, since I can easily imagine a beginner running into the same footguns I did and deciding never to use Nix again.
Describe alternatives you've considered
I considered creating an appendix for macOS users, but I feel that just guiding them towards an alternative installer should be enough to alleviate most of the potential pain points.

Install nix using the official installer.

3. Uninstall nix using the official guide, hoping that you'll be able to start over. There are quite a few steps, and one of them involves editing fstab, so you better be careful. At this point I was sweating bullets, not fun.

That's indeed my feelings when I first started using Nix on macOS, that's why I recommended using the Determinate Nix Installer before: https://github.com/ryan4yin/nix-darwin-kickstarter/commit/29a4c81924afbc0f9e0f7b002c2452540ecbf65a
But a few months ago I found the Determinate Nix Installer works not will with nix-darwin, I tried to fix that by submit a PR to nix-darwin: https://github.com/LnL7/nix-darwin/pull/834.
But I did not figure out what exactly the problem is, and finally I closed the PR, and replace the Determinate Nix Installer by the official one(https://github.com/ryan4yin/nix-darwin-kickstarter/commit/29a4c81924afbc0f9e0f7b002c2452540ecbf65a), I never encountered this kind of issue again after the replacement.
Another problem I met is, the Determinate Nix Installer provides no docs for how to uninstall itself manually.
This will be a big issue when you use it with nix-darwin and try to manage nix itself via nix-darwin - /nix/nix-installer uninstall will not work properly, and you will have to dig into nix-installer's source code and state file to figure out how to uninstall it manually, which is painful.

2. Install nix-darwin, fiddle with random flakes and break stuff until you don't even know how to get out of the mess you've created.

Try to reinstall nix, only for the installer to fail, because you didn't uninstall nix-darwin first.

Nix-darwin cannot be uninstalled using the script they provided, because nix-build is no longer available. Good luck, you'll need it.

Yeah, nix-darwin modifies some of the core configurations of the macOS system, which is unnecessary and troublesome for people who only want to use nix for development environment management.
Nix-darwin should indeed be an option rather than a default, and I will find time to add relevant tips.

It's also aware of existing nix-darwin installations and refuses to proceed if it detects one, so a beginner will have a much harder time bricking their setup.

This feature was added by https://github.com/DeterminateSystems/nix-installer/pull/561, and docs for nix-darwin was added by https://github.com/DeterminateSystems/nix-installer/pull/687.
These are good features or documentation additions, but they didn't exist when I first used nix-darwin & nix-installer last year.

This issue saved my life.
I tried to follow the instructions in the document, but got stuck at the Nix installer step. It failed without a clear reason.
Then I found this issue and tried using the DS installer instead. Everything went smoothly! I would strongly recommend using the DS installer by default to prevent more people from encountering similar problems.


[macos] update XCode 15 to Beta 8

Description
update XCode 15 to Beta 8
Related issue:
Check list

[ ] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

/azp run macos11, macos12


[JUnit] Basic test suite for task-commands

Up till now Task-related classes had no tests. This PR aims to address this issue by introducing a basic test suite, which largely follow existing tests.
More focused and complex tests will be added eventually.

Coverage increased (+0.6%) to 77.316% when pulling 115e734d2bf0a949e6fc3165dbb38d090cf2e09e on Esilocke:inheritedCommands into dc28e8dc6cad5821d67694ebcc61ac2c63a42898 on CS2103AUG2017-W09-B2:master.

Coverage increased (+1.2%) to 77.835% when pulling 2587d879d8a21db3b6fae0f7ba5bba0a5526dcfa on Esilocke:inheritedCommands into dc28e8dc6cad5821d67694ebcc61ac2c63a42898 on CS2103AUG2017-W09-B2:master.

Coverage increased (+1.2%) to 77.835% when pulling 7bdc6596de0cdfa37f1c5240e89f76fcf8543906 on Esilocke:inheritedCommands into dc28e8dc6cad5821d67694ebcc61ac2c63a42898 on CS2103AUG2017-W09-B2:master.

Coverage increased (+2.3%) to 78.74% when pulling c0c42ab7ae823be5602200d286f9fed6707f9d96 on Esilocke:inheritedCommands into d43bfdd28401334f17001cdc3b51986fc380b1b0 on CS2103AUG2017-W09-B2:master.

Coverage increased (+2.3%) to 78.74% when pulling c0c42ab7ae823be5602200d286f9fed6707f9d96 on Esilocke:inheritedCommands into d43bfdd28401334f17001cdc3b51986fc380b1b0 on CS2103AUG2017-W09-B2:master.

Cleaned up some outdated comments from coveralls

Coverage increased (+2.5%) to 78.946% when pulling 845471313df3567a5efd087a7c2b90a1d90f9dc5 on Esilocke:inheritedCommands into d43bfdd28401334f17001cdc3b51986fc380b1b0 on CS2103AUG2017-W09-B2:master.

Coverage increased (+2.5%) to 78.944% when pulling c2ec8a6932666d472adc9c68d84505ad6f6d5249 on Esilocke:inheritedCommands into d43bfdd28401334f17001cdc3b51986fc380b1b0 on CS2103AUG2017-W09-B2:master.

Coverage increased (+2.5%) to 79.014% when pulling c66e212d6ca2aef9e0031f708f37cfc4650c8f20 on Esilocke:inheritedCommands into d43bfdd28401334f17001cdc3b51986fc380b1b0 on CS2103AUG2017-W09-B2:master.

Coverage increased (+2.7%) to 79.201% when pulling fc3dbf545eb6d3874fa526ba2a79559ace453345 on Esilocke:inheritedCommands into d43bfdd28401334f17001cdc3b51986fc380b1b0 on CS2103AUG2017-W09-B2:master.

Coverage increased (+2.7%) to 80.197% when pulling ec61f7546fa0d5b1f329e1df001ad9a4ae1548e7 on Esilocke:inheritedCommands into 2eedbb5a0877aec62c6d0981a3d575e14ff029c4 on CS2103AUG2017-W09-B2:master.


Don't work?

Hi, I installed the extention and launched the console but nothing happens, the console remains empty and the extention returns these errors on chrome:

Error handling response : TypeError : Cannot read properties of undefined (reading 'length') at chrome-extension://cajbjpmjnojnbfgnmlhgmccahhbnbona/background.23452572.js:1:557 at chrome-extension://cajbjpmjnojnbgnmlhgmccahhbnbona/background.23452572.js:1:778

Runtime.lastError unchecked: Unable to establish connection. Recipient does not exist.

Unchecked runtime.lastError : Message port closed before a response was received.

After reboot my PC i get this in console but nothing on Discord :

<IP_ADDRESS> - - [07/Aug/2023 14:24:40] "DELETE / HTTP/1.1" 200 -
<IP_ADDRESS> - - [07/Aug/2023 14:24:46] "PUT / HTTP/1.1" 200 -

Error handling response : TypeError : Cannot read properties of > undefined (reading 'length') at chrome-extension://cajbjpmjnojnbfgnmlhgmccahhbnbona/background.23452572.js:1:557 at chrome-extension://cajbjpmjnojnbgnmlhgmccahhbnbona/background.23452572.js:1:778

Runtime.lastError unchecked: Unable to establish connection. Recipient does not exist.

Unchecked runtime.lastError : Message port closed before a response was received.

I will make sure to handle those exception from your first comment in the next release. These exceptions can be ignored for now.

After reboot my PC i get this in console but nothing on Discord :

<IP_ADDRESS> - - [07/Aug/2023 14:24:40] "DELETE / HTTP/1.1" 200 -
<IP_ADDRESS> - - [07/Aug/2023 14:24:46] "PUT / HTTP/1.1" 200 -

The extension and client is working. But there might be something off with the rich presence. I will release an executable for debugging later.
Thank you for pointing out the issue!

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
Ethnical, @anthonyoliai, @aliihsancengiz, @drgomesp, @QiangL, @oxlime, @Chriscbr, @saucepoint, @cuongquangnam, @rameight, @touhonoob, @lostsnow, @dmmulroy, @taishi8117, @hamidra, @jgannonjr, @modulareum, @martinezjorge, @Bruce1115, @joachimneu


[Obsidian] Copy "Code" option

Extension – Obsidian
Author: @marcjulianschwarz

Describe the feature and the current behavior/state.
This may be too specific of a feature request, but I wonder if others do things like this and could be helpful. A stretch ask for sure, feel free to deny this.
I keep a lot of snippets of small, or larger code blocks in Obsidian that are not necessarily part of a specific project, or are specific to deployment servers for different projects, or what have you. I copy paste those from Obsidian into my shell or whatever environment I'm working in a lot.
Now, the issue is I have those wrapped in backticks to get the code block rendering in Obsidian, but if I copy the note contents directly through the RayCast Obsidian extension, I get those backticks. I could remove the backticks, but then I don't have code block rendering in Obsidian.
Who will benefit with this feature?
Anyone who wants to copy code blocks from Obsidian without having to reformat or remove markdown.
Any Other info.

Let me know if this is something you're okay with adding, or may as a configurable option? And maybe I can try to work it if it's not too hard.

Would something like this work for your?

Enable Copy Code action in settings

The Copy Code action will search through the entire note and retrieve all code snippets. It then either displays a list of all code snippets to select one from or if there is only one code snippet copy it directly.
The same could work for a Paste Code action or combine them both into one.

https://user-images.githubusercontent.com/67844154/182040320-abded943-94e2-4b47-affd-fdefd5ff31db.mov
Any feedback on this?

hey thanks for working on this so quick! For some reason I can’t load the video on my phone so I’ll let you know when I’m back at my computer before EOD!
Regards,
Damian Mastylo

On Jul 31, 2022, at 11:32, Marc Julian Schwarz @.***> wrote:

https://user-images.githubusercontent.com/67844154/182040320-abded943-94e2-4b47-affd-fdefd5ff31db.mov
Any feedback on this?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

@marcjulianschwarz this is sick!!! Can't wait to use it

Hi @dmastylo,
thank you, I like it too.
I dont know if I will be able to release it with the next version as there are already lots of changes happening with the update which is currently under review.
If you want you can clone the repo, run npm install, run npm run dev and use it that way until it will be released officially.

I'm happy to wait until the official release! Do you know when that may happen?

This pull request (for the release of 1.8.0) has been under review for nearly two weeks now and there doesnt seem to be any progress. I don't know why it takes so long. Usually updates will be released way faster.
The copy code feature will be released with version 1.9.0 as there are already quite a lot of changes in 1.8.0.
So maybe two weeks after 1.8.0 has been released which depends on the time it takes for the review.

Hey @marcjulianschwarz wanted to follow up on this and see if there was n update on v1.9? Thanks!

Hey @dmastylo,
sorry for not being active here. I am quite busy with preparations for university exams right now.
I will try to get the pull request for 1.9 ready today.

Hi @dmastylo,
new version (with copy code action) is now under review, see https://github.com/raycast/extensions/pull/2887

Awesome, thanks a bunch for this Marc it has been very helpful @marcjulianschwarz! Hope your exams are going well.


tslint rules don't overvrite pritter settings

I setup newest version of tslint-config-prettier in tslint.json. In vscode I have instaled prettier with settings   "editor.formatOnSave": true but after save I get " instead of '. So somethings wrong, I should put something more in settings to load tsconfig to prettier?

I have the same issue. It's not working.

I saw that tslint is deprecated so try to move to eslint (in pain) 😞

It sounds like you're using the Prettier VSCode extension instead of using TSLint directly, please refer to the Linter Integration section in the Prettier VSCode extension docs.


[Phase Four] prop damage

The problem of how to remove the purple color when prop takes damage?
How to remove damage?
Prop

That's like trying to remove crafting or mining from vanilla Minecraft.

Russian players like all break. Props no exception

It was in sv_hooks but now... there External... thx

I'll be marking this Issue as Solved. A user (murray-elijah) pointed out a lot of Issues that are solved or expired, so I'm working on that to tidy up Clockwork's Issues.


Not working with tslint 6.0.0

Updated tslint to latest version: 6.0.0. Plugin stopped working. Have tried reinstalling node modules, the plugin and vscode (using insiders build).
If I revert to 5.20.1 and restart vscode, it starts working again.

After updating to prettier@2 and<EMAIL_ADDRESS>I'm getting these on every line

Moved to eslint with typescript plugin (for which there is an extension that works fine).
"eslint": "^7.1.0",
"eslint-plugin-security": "^1.4.0",
"@typescript-eslint/eslint-plugin": "^3.1.0",
"@typescript-eslint/parser": "^3.1.0",

Closing this because I want to get rid of it from my open issues list :)


[Task]: Support Python 3.12

What needs to happen?
Add support for Python 3.12
Issue Priority
Priority: 2 (default / most normal work should be filed as P2)
Issue Components

[X] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam YAML
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

Hey. Friendly question here.
After Datastax fixed their libev support for cassandra-driver (testing it in https://github.com/apache/airflow/pull/38314) , Papermill and Apache Beam are two last community Airflow Providers that have no Python 3.12 support.
We are just about to release Airflow 2.9.0 where Python 3.12 support is enabled and also default airflow image is going to by Python 3.12, so Apache Beam will be uninstallable there and unusable - due to conflicting dependencies that have no Python 3.12 support (it will still work on Python 3.8 - 3.11).
I looked at the 2.55.0rc3 just uploaded - and it does not seem to come with Python 3.12 support, so I'd love to know if Python 3.12 support is planned any time soon.

This will be worked on in Q2. Thanks.

TODO:
Update all tests definitions, see:
grep -rn . --include="*.yml" -e "python_version:"
grep -rn . --include="*.yml" -e "python_version: \['3.8','3.9','3.10','3.11'\]"

./.github/workflows/beam_PreCommit_Python_Transforms.yml:67:        python_version: ['3.8','3.9','3.10','3.11']
./.github/workflows/beam_PostCommit_Python_ValidatesContainer_Dataflow.yml:68:        python_version: ['3.8','3.9','3.10','3.11']
./.github/workflows/beam_PreCommit_Python_Examples.yml:67:        python_version: ['3.8','3.9','3.10','3.11']
./.github/workflows/beam_PostCommit_Python_Examples_Direct.yml:66:        python_version: ['3.8','3.9','3.10','3.11']
./.github/workflows/beam_PostCommit_Python_ValidatesContainer_Dataflow_With_RC.yml:66:        python_version: ['3.8','3.9','3.10','3.11']
./.github/workflows/beam_Python_ValidatesContainer_Dataflow_ARM.yml:57:        python_version: ['3.8','3.9','3.10','3.11']
./.github/workflows/beam_PreCommit_Python.yml:67:        python_version: ['3.8','3.9','3.10','3.11']
./.github/workflows/beam_PreCommit_Python_Dataframes.yml:67:        python_version: ['3.8','3.9','3.10','3.11']
./.github/workflows/beam_PreCommit_Python_Runners.yml:67:        python_version: ['3.8','3.9','3.10','3.11']
./.github/workflows/beam_PreCommit_PythonDocker.yml:67:        python_version: ['3.8','3.9','3.10','3.11']

Looking forward to enabling apache-beam provider for Airflow to 3.12 finally !


From private repo

@v-alje : Thanks for your contribution to the Azure documentation! The author, @j-martens, has been notified to review your proposed change.


fix: Show ads on all pages

Prerequisites checklist

[x] I have read the contributing guidelines.

What is the purpose of this pull request?

What changes did you make? (Give an overview)
Added with context when importing the hero macro. That allows ad.html to access global data.
Related Issues
fixes #520
Is there anything you'd like reviewers to focus on?

Good catch!


VCF output runs into assertion if ref().size() > 1

The problem is that record.ref() only accepts a single nucleotide, although its type is dna5_vector. If I set multiple nucleotides, the program dies with a segmentation fault (release build) or Assertion failed: (buffer_space > 0) in function write_range (debug build).
This is my minimal code example:
#include <seqan3/alphabet/nucleotide/dna5.hpp>
#include <bio/var_io/writer.hpp>

int main()
{
    using namespace seqan3::literals;
    bio::var_io::header hdr{};
    hdr.file_format = "VCFv4.3";
    hdr.column_labels = {"CHROM", "POS", "ID", "REF", "ALT", "QUAL", "FILTER", "INFO", "FORMAT", "x"};

    bio::var_io::writer writer{std::cout, bio::vcf{}};
    writer.set_header(hdr);
    bio::var_io::default_record<> record{};
    record.chrom() = "chr1";
    record.pos() = 11111;
    record.id() = "test";
    record.ref() = "ATC"_dna5; // <- problem here: "A"_dna5 works
    record.alt() = {"AGC", "A"};
    record.qual() = 1.F;
    record.filter() = {"PASS"};
    record.genotypes() = {};
    record.info() = {};
    writer.push_back(record);

    return 0;
}

My current work-around is changing the type of ref() to std::vector<char>, which works as expected.

Yeah, this took me quite a while to figure out. The problem is that by default, std::cout does not do any buffering. This is horrible for performance and something you never want unless you are mixing calls to std::cout and printf() (which you also shouldn't be doing!).
The correct workaround is to call this somewhere at the beginning of your program
std::ios::sync_with_stdio(false);

This will make std::cout do regular buffering, which improves performance and will silence the assertion.
I will think about adding a buffering step when I see this situation.

I have now also added better handling of the situation to the library, so you will no longer get the assertion.


Possible Unhandled Promise Rejection (id: 3): Error: Zendesk failed to initialize.

Possible Unhandled Promise Rejection (id: 3):
Error: Zendesk failed to initialize.

当我在react-native0.69.12  安卓上使用得时候   初始化失败
Possible Unhandled Promise Rejection (id: 3):
Error: Zendesk failed to initialize.

@jyear Can you share your code?
You should handle initialize() and check error reason.
Zendesk.initialize(...).catch((error) => {
  console.log(error); // << error reason here!
});

Can you add this configuration on native and check crash logs? @jyear
Android: https://developer.zendesk.com/documentation/zendesk-web-widget-sdks/sdks/android/getting_started/#logging
iOS: https://developer.zendesk.com/documentation/zendesk-web-widget-sdks/sdks/ios/getting_started/#troubleshooting

I tried enabling the debug log but no help, same javascript logs  showing up in xcode.
Question - will the same channelid that is used in the script tag appended after snippet.js?key=XXXXXX work or do we need to create another ?


Fix update-version.sh

Fixes the script to correctly update the existing version references. Also updates some existing version references.

Yep, will fix this in a separate PR.


⚠ Boutique - Ascentia has degraded performance

In fa4d6f0, Boutique - Ascentia (https://store.ascentia.fr/) experienced degraded performance:

HTTP code: 200
Response time: 5706 ms

Resolved: Boutique - Ascentia performance has improved in 1c32a0a after 219 days, 9 hours, 11 minutes.


Setting SystemTrigger or ApplicationTrigger as background task triggers throws exception when registering

Describe the bug
I'm looking to create Win32 COM background task with Time, System and Application Triggers. Time works, but when System or Application triggers are set, calling BackgroundTaskBuilder.Register throws the following exception
System.Runtime.InteropServices.COMException: "Incompatible request (0x80070032)"

Steps to reproduce the bug
In BackgroundTaskWinMainComSample/CS project from DesktopBridgeToUWP-Sample repository I'm able to replicate the issue.
Only thing needed to update is at MainWindow.xaml.cs:172, change the Time trigger by any of the others mentioned:
RegisterBackgroundTaskWithSystem(new SystemTrigger(SystemTriggerType.SessionConnected, false), typeof(TimeTriggeredTask).GUID, typeof(TimeTriggeredTask).Name);

RegisterBackgroundTaskWithSystem(new ApplicationTrigger(), typeof(TimeTriggeredTask).GUID, typeof(TimeTriggeredTask).Name);

Expected behavior
It should be able to register the task and triggers should work.
Screenshots
No response
NuGet package version
Windows App SDK 1.4.0: 1.4.230822000
Packaging type
Packaged (MSIX)
Windows version
Insider Build (xxxxx)
IDE
Visual Studio 2022
Additional context
No response

@bpulliam what's the status here?

Same issue here, I am trying to use new SystemTrigger(SystemTriggerType.TimeZoneChange, false)

Currently we support SystemTrigger or ApplicationTrigger with the newly added BackgroundTaskBuilder API in WinAppSDK 1.7 exp1 release, Sample : https://github.com/microsoft/WindowsAppSDK-Samples/pull/392

Thank you a lot for the info and for the sample, it works perfectly!
However, I'm trying to use these triggers on my app that uses C#, but I still get the same exception type (but this time the exception message is empty) with those triggers.
Would you mind to include a C# sample? that would help a lot

Currently we support SystemTrigger or ApplicationTrigger with the newly added BackgroundTaskBuilder API in WinAppSDK 1.7 exp1 release, Sample : microsoft/WindowsAppSDK-Samples#392

Can you provide a C# sample？Thanks！

@Diegorro98 @Osirisoo0O
I have added C# sample here: https://github.com/microsoft/WindowsAppSDK-Samples/pull/392/commits/e123eae14bec61a1b47b1128a7322bbcc23a5ff3
Please let me know whether it helps, Thanks

Hey! I was finally able to make it work at my app :) Thank you!
It has been a little bit difficult because I was adapting the code that you uploaded to the code from my app, I was having exceptions all the time, but I finally discovered because I was using Windows.ApplicationModel.Background.BackgroundTaskBuilder (BackgroundTaskBuilder was imported with using) and I didn't saw that you were using `Microsoft.Windows.ApplicationModel.Background.BackgroundTaskBuilder``.
I hope this can be useful for someone encountering the same problem I was having.
Btw, is LaunchAndActivationPermission="O:PSG:BUD:(A;;11;;;IU)(A;;11;;;S-1-15-2-1)S:(ML;;NX;;;LW)" at Package.appxmanifest's com:ExeServer something important? I saw that you used but it also works without it and I would like to know what is and why are you adding it to your example

Thanks a lot @Diegorro98 for trying it out and the feedback. Microsoft.* is the newly added WinAppSDK API. I will update sample to highlight that usage as well with a comment.
LaunchAndActivationPermission is ideally required for giving the privilege for OOP Background Task to launch the COM component in your package, without which it may throw access denied issues during COM activation.

I just have been testing more, and yesterday in fact I was only able to register the task. Although the task is registered it does not launch the Run method from the class that inherits from IBackgroundTask. It launches the backgroundTaskHost.exe but does not do anything else, and after some time, it dies.
I have created a patch for the example at microsoft/DesktopBridgeToUWP-Samples/tree/master/Samples/BackgroundTaskWinMainComSample/CS were I tried to set everything similar to the provided example and the mentioned issue happens: new_bg_task.patch

I also discovered that the CS version, when the background task is triggered, it opens the app, and once you click the register button (which it was already clicked before, because if not the task wouldn't have been triggered) it does run the background task. The only thing that I have changed from your version is the Microsoft.Windows.SDK.BuildTools version because 10.0.26100.2454 is not available and I used the latest available (10.0.26100.1742).

@Diegorro98 I see that your sample is not setting LaunchAndActivationPermission. As I mentioned above, this is required for the backgroundtaskhost.exe to activate your COM component

If you apply the patch I have provided to the repository, you will find that LaunchAndActivationPermission is set.
But let me do it easily, I have created a fork with the changes from that patch: Diegorro98/DesktopBridgeToUWP-Samples/Samples/BackgroundTaskWinMainComSample/CS

I see, my bad I deleted it for no reason.
I did the change but it happens the same issue: https://github.com/Diegorro98/DesktopBridgeToUWP-Samples/commit/4ef17a52210090f63be54c473a396cc0f27409e2

@Diegorro98 I checked your sample, Even though the sample is mentioning PublishProfile in csproj, It seems the profiles are missing.
In that case to declare the activatable class in your manifest, you may have to give the real paths like below
<Path>runtimes\win-x64\native\Microsoft.Windows.ApplicationModel.Background.UniversalBGTask.dll</Path>
Alternatively you can add the pubxml files required for each architecture and that should solve the issue, You can copy the PublishProfile from here
It seems .gitignore of the DesktopBridgeToUWP-Samples repo restricts checking-in the pubxml files

I added the publish profile files and I finally got it working 🎉🎉
Thank you so much for you help and patience!

Another question that I have, if you don't mind.
How do I launch the task if I have defined the DISABLE_XAML_GENERATED_MAIN constant at .csproj?
Maybe it is related to the issue I mentioned the other day about the sample you provided where the main app is opened when the background app is triggered, and maybe the reason is because the system is launching the app with the RegisterForBGTaskServer argument, but because there is no logic with the arguments, both the app and the background task are launched.

@godlytalias were you able to check how to launch the task if DISABLE_XAML_GENERATED_MAIN is defined as a constant at .csproj so that Program.cs has to be created and the arguments have to be checked?

I didn't understand the question quite clearly, You want to define DISABLE_XAML_GENERATED_MAIN or not?
In my sample as well I have defined this at here
Normally we don't need XAML to be initiated when a background trigger happens (as background trigger can occur at a point the UI application is not running), Background task just require to do some works in the background and exit, So we implement the condition checks at a point even before xaml initialize (in Program.cs by doing DISABLE_XAML_GENERATED_MAIN).

Woah! It's true that is defined. I'm sorry, I was using https://github.com/microsoft/WindowsAppSDK-Samples/commit/e123eae14bec61a1b47b1128a7322bbcc23a5ff3 and I didn't update the branch in any moment, so I was pretty sure that DISABLE_XAML_GENERATED_MAIN wasn't defined, but there it is, right in the next commit.
So cool, problem solved!
Thank you!


Include "back_matter" section when parsing from json to csv

When parsing json to csv, in json2csv,include parsing of "back_matter" field in pdf_json data
back_matter_data = pdf_json_data["back_matter"]
back_matter_df = extract_sentences(input_filename, back_matter_data)

Instead of this try to filter out the sections that are not needed.

"back_matter" field is there in all Grobid json outputs. Filtering out method is not applied.


The kernel crashes occasionally in the service handler with a hard fault

Update: the problem does not lie in the service handler execption or handler. The problem is that the second time the SVC is called the PSP points to a non valid address; 0x000001F4. I tried removing the naked attribute from SVC caller thus verifiing that the SVC exeption returns to the right place, but in this setup the Thread A does not continue. I suspect the error is in the scheduler(s).

Solution: The problem was with the naked SVC handlers which did not branch to lr. Therefore the fix was to either remove NAKED or add asm volatile ("bx lr)


Create AthenaX Backend Core component with flexible DB storage / Instance Management / Cluster Management APIs

Split out athenax-backend into more flexible component groups to enable

APIs for replacing LevelDB with any database system

APIs for replacing YARN with any cluster management and Flink deployment models (remove dependencies with YARN / Hadoop)

APIs for replacing built-in watchdog policies with any instance management strategies.

Higher Lever Server Context APIs for enabling or extending future functionalities

Attached design Doc:
https://docs.google.com/document/d/1oWcYKz2knrRUVhnh6Xl53qD1sA88qSFBtBkPvX6KPM0/edit?usp=sharing

close, change of plan


Fix modal

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #60
Test URLs:

Before: https://main--bitdefender--hlxsites.hlx.page/solutions/
After: https://60-modal-button-in-hero-overwritten--bitdefender--hlxsites.hlx.page/solutions/


Broker interceptor

Passing in session instead of peer into broker/dealer calls
Cleaned up the defaultBroker maps
introduced BrokerInterceptor

This change is

Leaving this PR opened for now for feedback, however, I realized that the broker_interceptor approach does not scale as the number of organizations increases.  Will need to consider a different approach
Previously, mourad (Danilo Moura) wrote…
> #### Broker interceptor
>
> - Passing in `session` instead of `peer` into broker/dealer calls
>
> - Cleaned up the defaultBroker maps
>
> - introduced BrokerInterceptor
>
>
>

Review status: 0 of 8 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

After thinking about it further,  scaling will be handled by the library user (library has no knowledge of what an organization is -- nor should it).
Previously, mourad (Danilo Moura) wrote…
> Leaving this PR opened for now for feedback, however, I realized that the broker_interceptor approach does not scale as the number of organizations increases.  Will need to consider a different approach

Review status: 0 of 8 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 8 of 8 files at r1.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

broker.go, line 20 [r1] (raw file):

// A super simple broker that matches URIs to Subscribers.
type defaultBroker struct {
	routes        map[URI]map[ID]route

The way this type is defined, as the inner map grows and shrinks the individual route elements are going to have to be copied.  Consider map[URI]map[ID]*route instead.

broker_interceptor.go, line 4 [r1] (raw file):

// BrokerInterceptor is the interface that intercepts broker events
type BrokerInterceptor interface {

No issues with the actual implementation but the name is slightly confusing, only because of the clash with the Interceptor interface that already exists.  In that interface messages are truly being intercepted and possibly modified.  It doesn't seem like that's what's happening here.  Some alternatives that I can think of:
BrokerDistributor
BrokerPublisher

Comments from Reviewable

bump
Previously, mourad (Danilo Moura) wrote…
> After thinking about it further,  scaling will be handled by the library user (library has no knowledge of what an organization is -- nor should it).

Review status: 6 of 8 files reviewed at latest revision, 2 unresolved discussions.

broker.go, line 20 [r1] (raw file):
Previously, djoyner (David Joyner) wrote…
> The way this type is defined, as the inner map grows and shrinks the individual `route` elements are going to have to be copied.  Consider `map[URI]map[ID]*route` instead.

hmm .. I should've caught this, thx.

broker_distributor.go, line 4 [r1] (raw file):
Previously, djoyner (David Joyner) wrote…
> No issues with the actual implementation but the name is slightly confusing, only because of the clash with the `Interceptor` interface that already exists.  In that interface messages are truly being intercepted and possibly modified.  It doesn't seem like that's what's happening here.  Some alternatives that I can think of:
>
>     BrokerDistributor
>     BrokerPublisher
>

Went with `BrokerDistributor` as I might use it for things other than Publish in the future.

Comments from Reviewable

Reviewed 3 of 3 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Localisation: Import Account Dialog

Upon clicking on "Import Account" while a language other than English is chosen the dialog for passphrase entry contains English text instead of a translation, the same goes for "QR CODE" link, both emphasized in red in the attached screencap.

thanks for pointing this out.
Reason is that we made a last minute change in this warning and did not update the transalation files for this.

we can thank hylex for this - if it weren't for his passphrase guessing games I probably wouldn't have noticed

Fixed.


A question about Coregionalization case using Gpflow

I am trying to run the Coregionalization case
http://gpflow.readthedocs.io/en/latest/notebooks/coreg_demo.html，
but when i run to the code "gpflow.train.ScipyOptimizer().minimize(m)", it raises en error below

Could someone help me how to solve it? Thanks a lot!

Are you running the notebook as is, or changing it? If you're changing it, please provide some more details to help fix the problem.