Instructions missed implicit operands info

popa, popad pop 8 generals
pusha, pushad push 8 generals
Maybe need a new registers flag string?
seems "all" not an option, because call instruction and others maybe redefine the semantics of "all"
xx/yx/zx like series for cases?

There are many ins like the following in X64 which operand modifier is dx:zsi and like
    ["movsd"            , "X:<es:zdi>, X:<ds:zsi>"                      , "NONE"    , "A5"                               , "ANY REP REPNE    DF=R"],
    ["movsq"            , "X:<es:zdi>, X:<ds:zsi>"                      , "NONE"    , "REX.W A5"                         , "X64 REP REPNE    DF=R"],

I guess, since REX.W limit the instruction, so the z- prefix is not necessary, it's fine that to just use r- prefix.
And ecds-segment ignored in bits64 mode, it should be ignored.
["movsq"            , "X:<rdi>, X:<rsi>"                      , "NONE"    , "REX.W A5"                         , "X64 REP REPNE    DF=R"],

?

["syscall"          , "w:<rcx>,w:<r11>"                                            , "NONE"    , "0F 05"                            , "X64              Volatile"],

Hey good ideas, however, I think asmdb needs the concept of "hidden" registers, that's how it's called in other tools - hidden is everything that is not mentioned in operands and is accessed by the instruction. The only question is how to add it to the database.
Maybe something like to the metadata?
HIDDEN=W:rcx,W:r11 or HIDDEN=W:zmm0..15[63:32]
Undecided, thinking about it, but yeah I think this is necessary for tooling.

one point, prefix?
[RWwXx-~:]operand
- for implicit, instead of <>
~ for commutative instead of ↔


RFC: Disallow interleaving commas after result blocks in match exprs

 Issue by bjz
Saturday Dec 21, 2013 at 00:19 GMT
For earlier discussion, see https://github.com/rust-lang/rust/issues/11090
This issue was labelled with: A-grammar, B-RFC in the Rust repository

Currently you can do:
match x {
    A => (),  // exprs must end in a comma
    B => {}   // no comma needed after blocks
    C => {},  // a comma can still be added because `{}` is also an expr
    D => (),  // the comma is optional here, good for playing nice with diffs
}

Perhaps we could simplify the grammar so that each pattern/result pair is a form of :
<match-arm>  ::= <pattern> "=>" <expr>
<match-expr> ::= "match" <expr> "{" (<match-arm> ",")* <match-arm> [","] }

To illustrate what it might look like with bigger blocks, here is what is currently possible:
match x {
    A => (),
    B => {
        // some block stuff here
    }
    C => {
        // some more block stuff here
        // ...and here
    }
    D => blah_blah(),
}

Subjectively, I find the mixing of comma terminated exprs and non-comma terminated blocks distracting and a little ad-hoc. Compare to what would be required with the simpler grammar:
match x {
    A => (),
    B => {
        // some block stuff here
    },
    C => {
        // some more block stuff here
        // ...and here
    },
    D => blah_blah(),
}

I think this would be great. Still there's no official RFC for this.. is there more prediscussion needed?
Discussion in the [forum]http://internals.rust-lang.org/t/clarify-the-syntax-of-match-expressions/451) and in the original issue seemed good.

Since the language is now stable I don't think we can particularly change this, so closing.


Update authenticate-azure-cli.md

Removed "Contact your Microsoft or tenant administrator to change this value." from line 21.
As of January 30, 2021, lifetime of refresh token cannot be changed.
https://learn.microsoft.com/en-us/azure/active-directory/develop/configurable-token-lifetimes#refresh-and-session-token-lifetime-policy-properties

As of January 30, 2021, lifetime of refresh token cannot be changed.

I don't think this is what https://learn.microsoft.com/en-us/azure/active-directory/develop/configurable-token-lifetimes#refresh-and-session-token-lifetime-policy-properties is trying to say.

If you decide not to use Conditional Access to manage sign-in frequency, your refresh and session tokens will be set to the default configuration on that date and you'll no longer be able to change their lifetimes.

My understanding is that now you need to use Conditional Access to manage Refresh Token Max Inactive Time.
This refresh token expiration information was initially added by https://github.com/MicrosoftDocs/azure-docs-cli/pull/546 as 14 days and was later changed to 90 days in https://github.com/MicrosoftDocs/azure-docs-cli/pull/980. Actually, I don't think it is a good idea to mention the refresh token expiration time, as it is an AAD setting and not controlled by Azure CLI. We can link to the AAD doc, but is not a good idea to "vendor" its content as this will make our doc hard to maintain.

@shwetamathur7, Thank you for your contribution to Microsoft Docs.  I'm closing this PR as your comments prompted us to put in a link to Refresh and session token lifetime policy properties.
Please see PR 3822 as a replacement PR.


Remove unneeded permissions

I added these permissions back when I thought we were going to be asking identity questions. Since we aren't, the permissions are no longer needed.

meacer ptal

Very LGTM


Add new Firestore events supported by Eventarc.

@minyu19 Waiting for your go-ahead before merging.

Thank you, Mete. Looks like it will take some more time. I will let you know when it is ready.


fix: publish button and botStatus item should be disabled to click when some bot is publishing

Description
Bugfix: publish button and botStatus item should be disabled to click when some bot is publishing status
Task Item
#minor
Screenshots

Coverage decreased (-0.05%) to 55.726% when pulling 3d0a4b077c6c26d5fa7f6dfbc410b2096c072827 on julong/publish-disabled into d15d465e91f5d490fc25f1604c007bee898ac14a on main.


File tree encapsulation

Change Summary

Encapsulated fileTree component [resolves #35 ]

file tree now acts as independent component which get folder path as input and returns folder/file path as output

folder selection is now fixed [resolves #62]

More info

fileTree component get folder path as input, use the FolderService to load it's content and update the fileTree view.
when selecting a folder or a file, it's path is returned by the fileTree component.
codeEditor component now gets file path as input, uses the FileService to load it's content and update the code editor view

:warning: MAKE SURE TO GO THROUGH THIS LIST :warning:
(reviewers shouldn't approve a PR without the next three checkboxs checked)
Before you submit a PR, make sure you did the following things:

[ ] did you link this PR to an issue?

Make sure there's an issue open about the change you did (open one if there isn't). link this PR to that issue by writing resolves #{{issue_number}}. If this PR had several mission, link each issue in its parallel mission.

[ ] did you lint your changes to both javascript and scss?

hound can be pretty rough at keeping our code clean and readable! make sure you format your code by running either gulp format or gulp lint and cleaning out all the lint errors. If you won't, you'll have a long conversation with hound :-)

[ ] "I'm pretty sure I'll be able to read and understand this PR, even if I wasn't the author." - said the PR author

This change is

This PR was replaced to #91 for branch naming style guide


[mono][tests] Fix SolutionGenerator test on mono/osx

Under Mono/osx, even when using in-tree msbuild, solution before/after
files (eg. NuGet) get picked up from the installed mono. So, only count
targets coming from .sln.metaproj files, which would be the ones
generated by the SolutionGenerator.
The change should be safe for all platforms.
Fixes
Microsoft.Build.UnitTests.Construction.SolutionProjectGenerator_Tests.IllegalUserTargetNamesDoNotThrow

There might be an alternative implementation. Apparently setting the global property ImportByWildcardBeforeSolution to false will skip those imports. Second arg in the SolutionProjectGenerator.Generate appears to take in global properties.
Though I do not know what's cleaner, setting that global property or making the t.FullPath.Contains(".sln.metaproj") assumption.

Though I do not know what's cleaner, ...

Setting the global property, IMHO :)

BTW, we use $(ImportByWildcardBeforeSolution) for controlling both Before and After target imports, is that deliberate?

BTW, we use $(ImportByWildcardBeforeSolution) for controlling both Before and After target imports, is that deliberate?

Apparently it is deliberate: http://sedodream.com/2010/10/22/MSBuildExtendingTheSolutionBuild.aspx


New syntax for create sink

Is your feature request related to a problem? Please describe.
Similar to RFC: New Source DDL #64, we hope to  make the syntax of create sink clearer and more consistent with source.
Take Kafka sink for example:
CREATE SINK sink1 FROM mv1
WITH (
   connector='kafka',
   type='append-only'
   properties.bootstrap.server='localhost:9092',
   topic='test'
);

(Currently, Kafka sink only supports JSON format.)
If we adapt the new source syntax here, it will be like
CREATE SINK sink1 FROM mv1
FORMAT append-only ENCODE json
WITH (
   connector='kafka',
   properties.bootstrap.server='localhost:9092',
   topic='test'
);

This syntax is also applicable to any other sources with multiple format/encode options, such as S3 or Iceberg.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

It seems to be a prerequisite of supporting other formats than JSON for Kafka Source. So let me assign to @xiangjinwu for now.

Minor concern: append only is spelled as two words when used on table. #7965, although they do mean slightly different things:

On table, it is more like a constraint on what a table is allowed to do.
On sink, it is a type/format about how input would be transformed into output.


Add support for more complex shapes

https://de.wikipedia.org/wiki/U-Bahn_München#Linie_U7
https://de.wikipedia.org/wiki/U-Bahn_München#Linie_U8

🥲

So.. if you have an idea, feel free to contribute :D but I guess, these Munich lines are like an edge-case. would be nice if those could be displayed, but I actually dont know how..

I enjoy suffering

Found a way

Yeah, I get what this is doing, but I guess we need to find a way for non-Webapplications to render this correctly and convenient without having parsing issues...

I don't feel like writing my own format for representing gradients

How about SVG? Could represent all the weird and wonderful shapes and colors that some designers dream up

SVG representations would basically treat these not as pictograms that are part of the displaying app’s design system but as icons that are ultimately defined by the operator (slightly different definitions for “pill” included).
But that’s fine, because their purpose is making what users encounter on screen resemble offline equivalents as closely as possible.
SVGs are also infinitely scalable and not limited to Web-based rendering.

I think another new shape which would represent a lot of bus lines is the regular hexagon. Examples can be found in Stuttgarts bus map.

I think hexagon already is on the specs (see readme down below) but I think nothing can render it atm (so please dont add it for the moment)

A hexagon is on the specs indeed, but not a regular hexagon. I won't add corresponding lines until the shape is officially supported.

I think hexagon already is on the specs (see readme down below) but I think nothing can render it atm (so please dont add it for the moment)

In my opinion we shouldn't disapprove adding data to the spec, just because it can't be rendered. Applications should ideally fallback to methods they support if they encounter unrecognized/non-implemented shapes.
Besides, there might be other use cases apart from rendering, that could benefit from this data nonetheless.


[Feature] Decouple view categories from fetching of images

New Issue Checklist

[x] I have read and understood the CONTRIBUTING guide
[x] I have read the Documentation
[x] I have searched for a similar issue in the project and found none

Issue Info
n/a (Current)
Issue Description and Steps
For all sorts of reasons (testability, Single Responsibility Principle, I have strong opinions about MVC), I would like to decouple the downloading and caching part of SDWebImage from the category on UIImageView part of SDWebImage.
This feature request would manifest as the domain logic for the -sd_setImage:[...] category methods on UIView/UIImageView/UIButton/etc being moved to a separate object (Maybe an SDWebImageFetcher?), which I can then new up and use wherever I want. Then, the various -sd_setImage:[...] calls would just use an SDWebImageFetcher to do their duties, while I feel nice knowing that my views are dumb and my controllers can handle actually fetching the data.
Note that most of the work involved is handled by SDWebImageManager, with the exception of the correct thread handling, error handling, basically, the entire implementation of -sd_internalSetImageWithURL:placeholderImage:options:operationKey:setImageBlock:progress:completed:, and the methods called from it.
Essentially:
I want an object NOT UIImageView/UIButton/MKAnnotationView/UIView that I can call something like -fetchImage:completionHandler: with a NSURL and a completion block that'll handle downloading/caching as well as threading translation and such so that I can handle placing the image on the desired view.

@younata I see. I recently moved all that logic inside the UIView category so it's not duplicated with every UIView. But we can take one step further and separate it into a new component and some leftover UI code that will remain in UIView category.
Are you interested in making a PR?

So....Actually I think current design is correct. Most of the property using in View Category is tied to UIView. So if your custom instance even is not a UIView subclass, most logic for this is really useless. (You don't need image indicator, image transition and many other feature we add).
So, why don't use just use SDWebImageManager loadImageWithURL: ? In 5.x we also provide the same context arg acrossing the View Category to Manager. You can build you logic without not much code.


Module build failed: SyntaxError: Unexpected token { on fresh install

ERROR in ./~/css-loader?sourceMap!./~/vue-loader/lib/style-compiler?{"id":"data-v-44de71e8","scoped":false,"hasInlineConfig":false}!./~/vue-loader/lib/selector.js?type=styles&index=0!./src/App.vue
Module build failed: SyntaxError: Unexpected token {
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:373:25)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at loadLoader (/Users/zhopeng/UI/simple1/node_modules/loader-runner/lib/load

Same here.

same with me

try to  change package.json:
"vue-loader": "^11.1.4"
to
"vue-loader": "11.1.4"
for temporary solution

I met the same issue, but report to the  https://github.com/vuejs/vue-cli/issues/414

Ref to https://github.com/vuejs-templates/webpack/issues/619

It still does not work

Thanks keeping "vue-loader": "11.1.4", worked for me on this fresh install :)

Using Node 6 instead of 4 helped me.

Same here.


fix(eslint-plugin): allow query key factory style

fixes https://github.com/TanStack/query/issues/4700

Codecov Report
Base: 96.36% // Head: 92.30% // Decreases project coverage by -4.05% :warning:

Coverage data is based on head (ed585bb) compared to base (eab6e2c).
Patch has no changes to coverable lines.

:exclamation: Current head ed585bb differs from pull request most recent head 21c64ca. Consider uploading reports for the commit 21c64ca to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4704      +/-   ##
==========================================
- Coverage   96.36%   92.30%   -4.06%
==========================================
  Files          45       89      +44
  Lines        2281     3758    +1477
  Branches      640      982     +342
==========================================
+ Hits         2198     3469    +1271
- Misses         80      273     +193
- Partials        3       16      +13

Impacted Files
Coverage Δ

src/core/focusManager.ts

src/core/logger.ts

src/react/utils.ts

src/core/mutationObserver.ts

src/core/queryObserver.ts

src/core/retryer.ts

...rc/createWebStoragePersistor-experimental/index.ts

src/core/utils.ts

src/devtools/devtools.tsx

src/react/useMutation.ts

... and 124 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

ah, this conflicts now with the other PR I just merged 😅

yea, it happens since because I add tests for each PR in the same file at the end 😅


Build failing

I'm trying to set up, and the build of my tests is failing with lacking packages.
nuget package restore is failing with

Dependency '"Newtonsoft.Json": ""' has invalid version specification.

Fixed.


Make the comment easier to read

By using the comment symbol you can not only separate the value pairs remarkably, but also simplify them by removing extra comas and using well known comment symbols which can't be used in any way other than to separate stuff.
UX texts, baby!

I think that in this scenario adding those extra // is actually incorrect, since it (to me) would mean //comment A // comment B // comment C while the comment is instead just trying to say how the output value will change based on the entry value.

I agree with kelset, the comment represents the interpolation result.
Would you have a better representation? I'd think of an object, but this could be biased 🤔.

Seems like we don't agree that this is the right change to make so I'm going to close this PR.


context on dark theme blends in

Reading the contexts on the dark theme is hard:

Oops, sorry! This is fixed in 6ddd8c8e3abf1321277a07ecd2a5b1c857163ee1.

@nedbat can we get a release with this? The current state makes the code almost iimpossible to view.

This is available in coverage 5.2.1.  Glad to know someone is using contexts! :)


Wallet.toJson is slow on web

Hi
Wallet wallet = Wallet.createNew(EthPrivateKey.fromHex("1122"), "123456", Random.secure());
debugPrint(DateTime.now().toString());
var json = wallet.toJson(); //20 seconds
debugPrint(DateTime.now().toString());
this part take 20 second. is it normal or a bug ?

İts only slow on debugging , on release its fast enough 👍


Is there a way to add multiple tables (the entire database)?

In connector options it asks for table name, is it possible to add more tables? If not, could you please give me a hint of what should I do to add this functionality? Thanks!

Sorry, I just saw that I need to create a new data source (table) in google data studio using the same connector, i.e, I can't connect a entire database at time.


Fix cross fs migration

What happens when migrating from say LXD 2.2 to a LXD version that supports the snapshots information? Do we get a proper fallback to just not having the snapshot config data and re-using the container data in that case or do things blow up?
I'm assuming the other way around (LXD git to LXD 2.2) will work as it does now given that the receiving end will just discard the extra protobuf fields.

https://github.com/lxc/lxd/pull/2384/commits/7e9cabb0dcf8d37790db723eb18be8c30f74451e#diff-1ba281187d55ff97223c66dcde00a84cR636

@tych0 cool, that looks good. Though that makes me ask another question.
When reading through the diff very quickly, I assumed that snapshotNames was still being set, but this part of the diff would indicate that it's not (since it assumes that snapshotNames being > 0 indicates a legacy source).
So what happens when migrating from a new LXD to an old one? Does that mean that snapshotNames won't be set and the target will be confused as to why it's received data streams on something which apparently doesn't have snapshots?

Looks like you forgot the go tests :)

Yeah, just noticed. I'm hitting another issue too.
Anyway, r.e. your question about what happens when going backwards, yes, it's currently broken. I'll push a fix shortly though.

jenkins: test this please

Looks like this needs some rebasing. Also, the review comments still apply.


Fix bad byte code when block-scoped function is called from with.

Yesterday's fix was incomplete, because it failed to address the case in which the nested function called from a with statement is declared in a lexical scope. The concept we're conservatively using, of a scope containing a with statement as well as closure-captured data, has to be tracked on individual scopes rather than functions.

@aneeshdk This is a variant on the one you looked at last week.

LGTM


Crashing after update for VSCode v1.31.1

I've been using Dashboard for a while now and love it's simplicity. However, after the latest update of VSCode, it appears to crash.
Opening VSCode:
Extension host terminated unexpectedly.

Running Dashboard from the command pallet gives me this error:
command 'dashboard.open' not found

Here's what Dev tools is giving me:
dyld: lazy symbol binding failed: Symbol not found: __ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE
  Referenced from: /Users/levi/.vscode/extensions/ritwickdey.liveserver-5.3.1/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node
  Expected in: flat namespace

dyld: Symbol not found: __ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE
  Referenced from: /Users/levi/.vscode/extensions/ritwickdey.liveserver-5.3.1/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node
  Expected in: flat namespace

extensionService.ts:457 Extension host terminated unexpectedly. Code:  null  Signal:  SIGABRT
t._onExtensionHostCrashed @ extensionService.ts:457
notificationsAlerts.ts:40 Extension host terminated unexpectedly.
t.onDidNotificationChange @ notificationsAlerts.ts:40
log.ts:161  INFO no standard startup: not the explorer viewlet

I hope you find it useful and can push an update to this wonderful extension. Please let me know if you need more debugging info.

Thanks for reporting, I'll have a look on this as soon as i can!

I just tried to reproduce this problem on two computers running Win10 (build 1803), but everything worked fine. Also nobody from my company reported any errors - a bunch of my colleagues are using vscode-dashboard and most likely have the newest vscode update installed automatically.
Reading from your log, it looks like ritwickdey.liveserver-5.3.1 https://github.com/ritwickdey/vscode-live-server is causing some problems. I found this issue describing your exact problem.
Looks like that extension is somehow breaking the extension startup, so vscode-dashboard does not get initialized. I suggest you follow the solution in the linked issue. :)
I'm closing this, but will gladly reopen if the error persists.

Thanks so much for investigating this issue! I must apologize because I had assumed it was this extension, as it appeared it was the only one that wasn't working. I have confirmed that was the issue. Disabling Live Server extension fixed the problem. Again, I really appreciate your help and apologize for the inconvenience.


Error message in homebridge log

Running homebridge on Synology NAS in a docker container.
The UPS connected to the NAS  (<IP_ADDRESS>) is a PowerWalker VI STL 1500.
Currently using other nut plugin (Homebridge NUT (Network UPS Tools) )and that one works OK.
Upgraded node.js to latest version, 16.17.1.
Message popping up in log every 5 sec or so:
[9/25/2022, 11:12:00 PM] [UPS] <IP_ADDRESS>: error: TypeError: constants.device.mfr.trim is not a function
at UpsHost.init (/homebridge/node_modules/homebridge-ups/lib/UpsHost.js:70:51)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at UpsPlatform.init (/homebridge/node_modules/homebridge-ups/lib/UpsPlatform.js:104:7)

What UPS device do you have?  Please list the output of ups info.  It looks like it doesn’t carry the device.mfr variable.

Hi Erik,
it is a Powerwalker.com http://powerwalker.com/ ups, model VI STL 1500 and connected to a Synology NAS.
Don’t know how to do the ups info on Synology, in Control Panel it shows manufacturer 1 and Model 1500. That’s also what the other Homebridge plugin shows.
Erik

On 25 Sep 2022, at 23:31, Erik Baauw @.***> wrote:
What UPS device do you have? Please list the output of ups info. It looks like it doesn’t carry the device.mfr variable.
—
Reply to this email directly, view it on GitHub https://github.com/ebaauw/homebridge-ups/issues/1#issuecomment-1257293113, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKNF22JTTKE3Q3XD67TACJTWADHEVANCNFSM6AAAAAAQVICCQA.
You are receiving this because you authored the thread.

SSH into the Synology and run ups info.  At least that works for me, using the standard Homebridge package on DSM 7.2.
Alternatively, install Homebridge UPS on another system, and run ups -H x.x.x.x info from that system.  Make sure to list that system's IP address under Permitted Synology NAS devices..

Run Homebridge in docker, so ran ups info from docker shell. Output attached below.
{
"version": "Network UPS Tools upsd DSM7-1-42464-211216 - http://www.networkupstools.org/",
"apiVersion": "1.2",
"devices": {
"ups": {
"description": "Unavailable",
"nCients": "1",
"clients": [
"<IP_ADDRESS>"
],
"commands": [
"beeper.disable",
"beeper.enable",
"beeper.mute",
"beeper.off",
"beeper.on",
"load.off",
"load.off.delay",
"load.on",
"load.on.delay",
"shutdown.return",
"shutdown.stayoff",
"shutdown.stop",
"test.battery.start.deep",
"test.battery.start.quick",
"test.battery.stop"
],
"constants": {
"battery.charge": 100,
"battery.charge.low": 10,
"battery.charge.warning": 20,
"battery.mfr.date": 1,
"battery.runtime": 7200,
"battery.runtime.low": 300,
"battery.type": "PbAcid",
"battery.voltage": "27.1",
"battery.voltage.nominal": 24,
"device.mfr": 1,
"device.model": 1500,
"device.serial": "",
"device.type": "ups",
"driver.name": "usbhid-ups",
"driver.parameter.pollfreq": 30,
"driver.parameter.pollinterval": 5,
"driver.parameter.port": "auto",
"driver.parameter.synchronous": "no",
"driver.version": "DSM7-1-42464-211216",
"driver.version.data": "CyberPower HID 0.4",
"driver.version.internal": "0.41",
"input.transfer.high": 290,
"input.transfer.low": 162,
"input.voltage": "237.6",
"input.voltage.nominal": 230,
"output.voltage": "237.6",
"ups.beeper.status": "enabled",
"ups.delay.shutdown": 20,
"ups.delay.start": 30,
"ups.load": 0,
"ups.mfr": 1,
"ups.model": 1500,
"ups.productid": 601,
"ups.realpower.nominal": 900,
"ups.serial": "",
"ups.status": "OL",
"ups.timer.shutdown": -60,
"ups.timer.start": -60,
"ups.vendorid": 764
},
"variables": {
"battery.charge.low": 10,
"battery.runtime.low": 300,
"input.transfer.high": 290,
"input.transfer.low": 162,
"ups.delay.shutdown": 20,
"ups.delay.start": 30
}
}
}
}

Hm, it does carry ups.mfr, but it contains only digits, so Homebridge UPS incorrectly treats the value as an integer, but I can fix that.  Same for ups.model.  More worrying, it does report an empty ups.serialnumber, which I use as ID for the accessory.  Need to think what to do about that.

Could you try v1.0.1?  I should handle the number manufacturer name and model, as well as the empty serial number.  From what I can see from the output, Homebridge UPS should support it otherwise.

Thanks for the quick update.Unfortunately it’s not working. I get the below message (sorry could only do screenshot from remote vpn session on Iphone)On 30 Sep 2022, at 11:12, Erik Baauw @.***> wrote:
Could you try v1.0.1?  I should handle the number manufacturer name and model, as well as the empty serial number.  From what I can see from the output, Homebridge UPS should support it otherwise.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

No message?

[9/30/2022, 5:12:14 PM] [UPS] <IP_ADDRESS>: error: TypeError: Cannot read properties of undefined (reading 'trim')    at UpsHost.init (/homebridge/node_modules/homebridge-ups/lib/UpsHost.js:74:49)    at processTicksAndRejections (node:internal/process/task_queues:96:5)    at UpsPlatform.init (/homebridge/node_modules/homebridge-ups/lib/UpsPlatform.js:104:7)On 30 Sep 2022, at 17:06, Erik Baauw @.***> wrote:
No message?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Missing device.firmware.  Could you try beta v1.0.2-0?

That looks much better :-)9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS>: Network UPS Tools upsd DSM7-1-42464-211216 - http://www.networkupstools.org/, API v1.2[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS>: set Serial Number to "ups"[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS>: set Manufacturer to "1"[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS>: set Model to "1500"[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS>: set Firmware Revision to "1.0.2-0"[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS>: ups: 1 1500 230V UPS with 24V PbAcid battery from 1[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS>: set Outlet In Use to 1[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS>: set Total Consumption to 0 kWh[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS>: set Log Level to 2[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS>: set Last Event to ""[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS>: set On to true[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS>: set Current Consumption to 0 W[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS>: set Voltage to 237.6 V[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS>: set Mute to false[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS>: set Status Fault to 0[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS>: set Last Event from "" to "undefined"[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS> Battery: set Battery Level to 100%[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS> Battery: set Charging State to 2[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS> Battery: set Status Low Battery to 0[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS> Battery: set Low Battery Threshold to 20%[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS> Battery: set Charging State from 2 to 0[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS> Battery: set Low Battery Threshold from 20% to 10%[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS> Battery: set Voltage to 27.1V[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS> Battery: set Remaining Duration to 0 seconds[9/30/2022, 6:57:45 PM] [UPS] <IP_ADDRESS> History: remove stale characteristic Name[9/30/2022, 6:57:45 PM] [UPS] warning: latest version: homebridge-ups v1.0.1[9/30/2022, 6:57:46 PM] [UPS] <IP_ADDRESS>: set Outlet In Use from 1 to trueOn 30 Sep 2022, at 17:49, Erik Baauw @.***> wrote:
Missing device.firmware.  Could you try beta v1.0.2-0?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Released v1.0.2.

Run Homebridge in docker, so ran ups info from docker shell. Output attached below.
{
"version": "Network UPS Tools upsd DSM7-1-42464-211216 - http://www.networkupstools.org/",
"apiVersion": "1.2",
"devices": {
"ups": {
"description": "Unavailable",
"nCients": "1",
"clients": [
"<IP_ADDRESS>"
],
"commands": [
"beeper.disable",
"beeper.enable",
"beeper.mute",
"beeper.off",
"beeper.on",
"load.off",
"load.off.delay",
"load.on",
"load.on.delay",
"shutdown.return",
"shutdown.stayoff",
"shutdown.stop",
"test.battery.start.deep",
"test.battery.start.quick",
"test.battery.stop"
],
"constants": {
"battery.charge": 100,
"battery.charge.low": 10,
"battery.charge.warning": 20,
"battery.mfr.date": 1,
"battery.runtime": 7200,
"battery.runtime.low": 300,
"battery.type": "PbAcid",
"battery.voltage": "27.1",
"battery.voltage.nominal": 24,
"device.mfr": 1,
"device.model": 1500,
"device.serial": "",
"device.type": "ups",
"driver.name": "usbhid-ups",
"driver.parameter.pollfreq": 30,
"driver.parameter.pollinterval": 5,
"driver.parameter.port": "auto",
"driver.parameter.synchronous": "no",
"driver.version": "DSM7-1-42464-211216",
"driver.version.data": "CyberPower HID 0.4",
"driver.version.internal": "0.41",
"input.transfer.high": 290,
"input.transfer.low": 162,
"input.voltage": "237.6",
"input.voltage.nominal": 230,
"output.voltage": "237.6",
"ups.beeper.status": "enabled",
"ups.delay.shutdown": 20,
"ups.delay.start": 30,
"ups.load": 0,
"ups.mfr": 1,
"ups.model": 1500,
"ups.productid": 601,
"ups.realpower.nominal": 900,
"ups.serial": "",
"ups.status": "OL",
"ups.timer.shutdown": -60,
"ups.timer.start": -60,
"ups.vendorid": 764
},
"variables": {
"battery.charge.low": 10,
"battery.runtime.low": 300,
"input.transfer.high": 290,
"input.transfer.low": 162,
"ups.delay.shutdown": 20,
"ups.delay.start": 30
}
}
}
}

On 26 Sep 2022, at 09:25, Erik Baauw @.***> wrote:
SSH into the Synology and run ups info. At least that works for me, using the standard Homebridge package on DSM 7.2.
Alternatively, install Homebridge UPS on another system, and run ups -H x.x.x.x info from that system. Make sure to list that system's IP address under Permitted Synology NAS devices..
—
Reply to this email directly, view it on GitHub https://github.com/ebaauw/homebridge-ups/issues/1#issuecomment-1257675270, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKNF22LYSVWQZNLOAQRWTFTWAFMXFANCNFSM6AAAAAAQVICCQA.
You are receiving this because you authored the thread.


Primary alignment filtering

Hi,
I've found a way to reduce background repeat counts.
In line 333 of https://github.com/unique379r/strspy/blob/main/scripts/STRspy_v1.0.sh reads are filtered so that only unmapped are eliminated from repeat counting.
If swapped to keep only primary alignments (-F 2308) instead of -F 4 which also keeps secondary and supplementary alignments,  this leads to much tidier repeat counting and reduced background repeat counts.
I propose changing filtering from -F 4 to -F 2308.
Thank you.

Thanks Heather thats a great suggestion!


Releases - Performance release e

Release branch for performance release e
Contains PRs:
https://github.com/Civil-Service-Human-Resources/lpg-services/pull/609
https://github.com/Civil-Service-Human-Resources/lpg-services/pull/615
https://github.com/Civil-Service-Human-Resources/lpg-services/pull/639

Closing as branch name contains forward slash char which causes issues in jenkins builds. Replaced by https://github.com/Civil-Service-Human-Resources/lpg-services/pull/640


Span IDs and Span context propagation is missing

@danyelf and I noticed that Honeycomb doesn't detect events from this library as traces, most likely because trace.span_id and trace.parent_id aren't generated and sent along

Perhaps this is a docs fix? A little more documentation or an exemplar of how to set up tracing data would be lovely.

The idea of this library is not traces.  It's a communication library that simply manages the communication with honeycomb.  It will not emit any events itself.  There is the AspNetCore implementation that wraps the HttpRequest, but this is not for tracing, just normal events.
The opentelemetry implementation is separate, in https://github.com/martinjt/Honeycomb.OpenTelemetry.
If OpenTelemetry, and it's Collectors retrieve traces from the Http calls this library makes, then OpenTelemetry would add all the relevant data to the events.


fix: Harvester ManagedChart is modified after an upgrade

Ignore the status fields in some post-modified CRDs in the upgrade path.
IMPORTANT: Please do not create a Pull Request without creating an issue first.
Problem:

Solution:

Related Issue:
Test plan:

A question here: the ComparePatches is defined as an array. The multi run of current code will expand the array. Should we check if the target value is not in the array and then append it?
type DiffOptions struct {
	ComparePatches []ComparePatch `json:"comparePatches,omitempty"`
}

type ComparePatch struct {
	Kind         string      `json:"kind,omitempty"`
	APIVersion   string      `json:"apiVersion,omitempty"`
	Namespace    string      `json:"namespace,omitempty"`
	Name         string      `json:"name,omitempty"`
	Operations   []Operation `json:"operations,omitempty"`
	JsonPointers []string    `json:"jsonPointers,omitempty"`
}

A question here: the ComparePatches is defined as an array. The multi run of current code will expand the array. Should we check if the target value is not in the array and then append it?

Good point, updated. The script is now idempotent. I'd keep the v1.2.1 one since it's already shipped.

@mergifyio backport v1.3


Add config to disable firstline matching lastline regex

I'm trying to concatenate java logs and the only way to know to stop matching is to get a 'normal' line again, which also happens to match exactly a first line.
My best scenario would be to start accumulating lines when matching the multiline_start_regexp and end excluding the multiline_end_regexp.
Idea?
My current config:
<filter docker.**>
  @type concat
  key log
  multiline_start_regexp /^\d{4}-\d{1,2}-\d{1,2} \d{2}:\d{2}:\d{2}.\d{1,3}/
  multiline_end_regexp /^\d{4}-\d{1,2}-\d{1,2} \d{2}:\d{2}:\d{2}.\d{1,3}/
  stream_identity_key container_id
  use_first_timestamp true
  flush_interval 1s
</filter>

example log (simplified, actual log is from docker fluentd logger):
2016-09-07 13:17:40.848  WARN 23 --- [nfoReplicator-0] c.n.discovery.InstanceInfoReplicator     : There was a problem with the instance info replicator

com.netflix.discovery.shared.transport.TransportException: Cannot execute request on any known server
     at com.netflix.discovery.shared.execute(RetryableEurekaHttpClient.java:111) ~[eureka-client-1.4.10.jar:1.4.10]
     at com.netflix.discovery.shared.register(EurekaHttpClientDecorator.java:56) ~[eureka-client-1.4.10.jar:1.4.10]
     at java.lang.Thread.run(Thread.java:745) [na:1.8.0_92-internal]

2016-09-07 13:17:40.726  INFO 23 --- [nfoReplicator-0] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_SERVICE-AUTH/c500a64ed52c:service-auth:9000: registering service...
2016-09-07 13:17:40.801  INFO 23 --- [  restartedMain] o.s.c.support.DefaultLifecycleProcessor  : Starting beans in phase<PHONE_NUMBER>
2016-09-07 13:17:40.827 ERROR 23 --- [nfoReplicator-0] c.n.d.s.t.d.RedirectingEurekaHttpClient  : Request execution error

com.sun.jersey.api.client.ClientHandlerException: java.net.UnknownHostException: service-registry
     at com.sun.jersey.client.handle(ApacheHttpClient4Handler.java:187) ~[jersey-apache-client4-1.19.1.jar:1.19.1]
     at com.sun.jersey.api.client.handle(GZIPContentEncodingFilter.java:123) ~[jersey-client-1.19.1.jar:1.19.1]
     at com.netflix.discovery.EurekaIdentityHeaderFilter.handle(EurekaIdentityHeaderFilter.java:27) ~[eureka-client-1.4.10.jar:1.4.10]

And...... it work by simply NOT using a multiline_end_regexp. Works marvelously too, thanks for this plugin!


Ability to mimic a zip file created by a Linux file-system.

Use Case
Create a zip archive with specific permissions, such as the executable flag, using the ExternalAttributes property. The Linux unzip command only applies such permissions if the zip entry indicates the file was added by a Linux host-system.
Solution
Expose the more specific ZipEntry constructors that allow controlling the version number and host-system information. Ensure this information is used when creating the zip archive.
Changes:

Changed access level from internal to public on constructors for ZipEntry. This allows setting the madeByInfo value.
Changed VersionMadeBy property to return the entire ushort. This is required by ZipFile and ZipOutputStream to write the correct value.
Fixed HostSystem property to clear out the upper byte where the host system information is stored.
Changed ZipFile and ZipOutputStream to respect the VersionMadeBy value of the ZipEntry instance instead of hard-coding it.

Agreement
I certify that I own, and have sufficient rights to contribute, all source code and related material intended to be compiled or integrated with the source code for the SharpZipLib open source product (the "Contribution"). My Contribution is licensed under the MIT License.

I would prefer to add this by having a "host OS override" that can be set and which in turn sets the top version byte.

There is a HostSystem property that might fit the bill. It had a bug where it cleared out the high-byte instead of the low-byte (see diff).
The big problem, IMO, is the VersionMadeBy property. As implemented, it always truncates the highg-bytes (see diff). Fixing that could potentially be a breaking change since dependent code may not expect the high-byte to have a value.
If VersionMadeBy cannot be fixed, then another property needs to be added that holds both the OS and zip version information. This information is later needed by ZipFile.WriteCentralDirectoryHeader(...) (see diff) and by ZipOutputStream.Finish(...) (see diff).
Let me know how you would like me to proceed and I'll update the pull-request. Thanks!

So, wouldn't just fixing the HostSystem property be enough then?
And using HostSystem + VersionMadeBy in ZipFile and ZipOutputStream?

I think so, yes. That would probably work. Let me give it a shot and update the pull-request.

@piksel
I updated the code. It now just fixes the HostSystem property bug and then ORs it with VersionMadeBy property in-lieu of the ZipConstants.VersionMadeBy constant.

As it turns out, it's not possible to set the HostSystem property of an entry using ZipFile (unless the file is empty).
I made some tests and added this functionality in a new PR.


Feat(packages): new optimizer package - [WIP]

This PR introduces a new package/executable: publicomp optimizer.
The goal is to centralize scripts used in the nosgestesclimat and nosgestesclimat-site into a cli tool being able to compile Publicodes model into a single JSON file.
Moreover, it will allows to optimize the generated file by removing constant rules -- see https://github.com/datagir/nosgestesclimat-site/issues/746.

Thanks for the early PR ! Some remarks on naming:

I initially thought that publicomp stood for “compiler” not “compression”
I would use the term constant folding for this operation as it's well established in computer science

What is the underlined motivation behind https://github.com/datagir/nosgestesclimat-site/issues/746 ?
At this point I'm not convinced that this package should be merged in this repository. Generally I think it is better if teams can independently implement features on top of the core API, and only merge them back into core if it's useful to multiple independent teams (I assume that constant folding is doable with the current core API but if not, then a PR that modify it would be welcome).

The reason of this PR, is that we (@betagouv/datagir) initiated a design phase to improve the management of models written in Publicodes. In particular, we would like to add lazy loading and a module/package system -- see the related pad.

What is the underlined motivation behind datagir/nosgestesclimat-site#746 ?

We defined a first step in this direction: adding a pass of constant folding optimization (thanks for term by the way :)) in our rulesToJSON.js script. This will allow to reduce both the size and the parsing time of the NGC's model, indeed, the waste model doesn't depend on user inputs, for example. Therefore, it can be precomputed in the server side.
More generally, several scripts have been developed for NGC that could be beneficial to other projects. They could become cli tools, such as: an optimized JSON transpiler, an automatic translation manager, build system/package manager, etc...
The main reason to develop them directly in the Publicodes repository is to reduce future refactoring, and to enforce a certain standard to the tool.

I assume that constant folding is doable with the current core API

By adding an argument to the Engine constructor and letting users writing wrappers around  it? Why not, I'm personally in favor of the unix philosophy. What do you think @laem @johangirod and @Clemog?

Regarding the name, it was intentional that comp refers both to compiler and compression, as it compresses a representation of the AST but what do you prefer?

Le projet a été déplacé dans un dépôt séparé : https://github.com/datagir/publiopti


What to do with Redis modules (RedisBloom, RediSearch etc)

redis-py has support for many modules that Valkey doesn't support and are not present in Valkey's Docker container.
Specifically:

RediSearch
RedisBloom
RedisGraph (EOL)
RedisTimeseries
ReJSON
RedisGears

A decision is needed about what to do with them. Should we completely drop all the code and tests (they are currently disabled) from valkey-py or delay the first release and wait to see if some of these get support?

https://github.com/valkey-io/valkey-rfc/pull/4
https://github.com/valkey-io/valkey-rfc/pull/2
https://github.com/valkey-io/valkey-rfc/pull/8


About client.cfg

"All configuration can be done by adding a configuration file named client.cfg to your current working directory or /etc/luigi (although this is further configurable)"
I got two problems:
(1) "your current working directory" is not clear enough, how can luigid find the client.cfg in "my current working directory"?
(2)"although this is further configurable",  how to configure the configure file path for luigid ?
Thanks everyone in advance.

The doc link:  http://luigi.readthedocs.org/en/stable/configuration.html

Does it look better here @leafjungle? https://github.com/spotify/luigi/pull/1010,
As for luigid, it's quite unfortunate that it uses the same logic for configuration as the client (it couples them for no good reason).

@Tarrasch ，Thank you very much.
I set the config file path by environment variable.
But I still puzzled  by "the current work space directory", is it the same directory with my python program (such as OneTask.py) ?

@leafjungle are you confused over "current working directory"? I mean, try running man pwd in a terminal.


feat: add support to ANY AND EVERY expression.

Adding support to create ANY AND EVERY expression.

@uribro hi, thanks for your contribution! We are actually using gerrit, and everything is detailed in here: https://github.com/couchbase/couchbase-java-client/blob/master/CONTRIBUTING.md
let me know if you have any questions, happy to help out if you get stuck

@uribro heyo, see my comment above - how do you want to tackle it? thanks!

Hi Michael,
I really want to contribute this code.
I don't know how to work with gerrit, so I tried to follow the manual and
stack a bit on (associated it with a SSH key).
Do you have some more info of how to do it?
On Mon, Mar 6, 2017 at 2:50 PM, Michael Nitschinger <
<EMAIL_ADDRESS>wrote:

@uribro https://github.com/uribro heyo, see my comment above - how do
you want to tackle it? thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/couchbase/couchbase-java-client/pull/19#issuecomment-284387575,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APjKWd9V9yiVkJ0TZzEzhak1sKOmzBj-ks5rjAEpgaJpZM4L_sjR
.

Hi @uribro,
I suppose you were able to register and sign the CLA  http://review.couchbase.org/#/settings/agreements. You can generate ssh key and add the public key here http://review.couchbase.org/#/settings/ssh-keys. On your .ssh config, you can add the host specific declarations like following
Host review.couchbase.org
Port            29418
User            userid
IdentityFile    ~/.ssh/id_rsa
PreferredAuthentications publickey

@uribro does that help you further?

@uribro can you sign the CLA here http://review.couchbase.org/#/settings/new-agreement with the email used in the patch<EMAIL_ADDRESS>Once you have signed it, we can upload the patch on your behalf to gerrit and get this merged. Thanks!

Hi @uribro, since we didn't hear back from you. I went ahead and created the patch on gerrit with the changes. It is here http://review.couchbase.org/#/c/76437/. Thanks much for the contribution.


Not an issue, but a question.

It is possible to patch the installation CD of Windows 98 SE with all of those patches including patches for RAM  high capacity disks and AHCI? Or the patches you may have in one line with patcher9x. To modify the installation CD-ROM instead of install windows 98 se to patch. Is a question only

AFAIK you can apply all the patches simultaneously if you want.


Updates to support InstanceYearSpecific ApiMode

Adding Support for External Cache Hash Code
Adding Support for Bulk Console
Adding Support to Smoke Test project

@AxelMarquez  I have signed and squashed commits as requested.


Make fault injection be DEBUG only

Currently cxplat/src/cxplat_winuser/cxplat_winuser.cpp always enables fault injection and leak detection.
For performance, these should only be enabled on DEBUG builds.

I think it makes more sense to move leak detection and fault injection out of cxplat and into usersim.

The cxplat kernal and user should behave the same, whereas currently one has explicit leak detection and fault injection, but the other does not.
The cxplat library is intended for production use, whereas usersim is currently a testing tool. Leak detection and fault injeciton are test only scenarios.

I would still like to have leak detection and fault injection (better than AppVerifier currently provides) available in cxplat CI/CD test runs.  Will see if we can factor logic out of the main path while leaving it accessible to tests.

I would also prefer it in cxplat, so projects that only need cross-platform API support can still benefit.

The cxplat kernal and user should behave the same, whereas currently one has explicit leak detection and fault injection, but the other does not.

I agree, and we should fill those gaps.

The cxplat library is intended for production use, whereas usersim is currently a testing tool. Leak detection and fault injeciton are test only scenarios.

Debug mode of cxplat is not intended for production use, so it is a great place to put this kind of stuff.


CrmServiceClient Error accessing_ws_metadata_exchange_failed: Accessing WS metadata exchange failed

Hi,
I am using oauth to connect to dataverse from azure function.
var connectionString = $"RequireNewInstance=true;AuthType=OAuth;Username={userName};Password={password};Url={crmOrgUrl};AppId=51f81489-12ee-4a9e-aaae-a2591f45987d;RedirectUri=app://58145B91-0C36-4500-8554-080854F2AC97;LoginPrompt=Never"; CrmServiceClient service = new CrmServiceClient(connectionString); return service;
I am seeing below error in application insights log
Error in connecting to Central CRM Instance : 5/28/2021 7:55:30 AM : ERROR REQUESTING Token FROM THE Authentication context

General ADAL Error accessing_ws_metadata_exchange_failed:
Accessing WS metadata exchange failed => A task was canceled.Unable to connect to CRM: A task was canceled.
accessing_ws_metadata_exchange_failed: Accessing WS metadata exchange failed =>
A task was canceled.Unable to Login to Dynamics CRM Unable to Login to Dynamics CRM System.Exception: Unable to Login to Dynamics CRM

.Net Framework - 4.6.2
Microsoft.CrmSdk.XrmTooling.CoreAssembly <IP_ADDRESS>
Please let me know if you need any other details.
@MattB-msft Please help.

Hi,
Can you please look into this.
Thanks!

@bipinshan @MattB-msft
Thanks for contacting us. Unfortunately, we're unable to handle Support requests for the product here. To contact Support, visit https://powerapps.microsoft.com/support/.
You can also try posting your issue to one of the developer forums.
We accept incorrect or missing documentation and sample code issues.
Closing this issue.


can't copy folder into subdirectory

   gap: {
                files: [
                    {src: ['../dist/**'], dest: '../Explore/www/'}
                ]
            }

I tried this with expand and cwd... same result. always copies into ../Explore/dist  not ../Explore/www/dist this is on OSX.  this is with grunt 0.4.5, could that be the issue?
"name": "grunt-contrib-copy",
"description": "Copy files and folders",
"version": "1.0.0",
Also tried downgrading to 0.5 get the same result.
with other deps:
"devDependencies": {
"tsd":"latest",
"angular-modal": "latest",
"bower": "latest",
"grunt": "0.4.5",
"grunt-cli":"latest",
"grunt-angular-templates":"latest",
"grunt-contrib-connect": "latest",
"grunt-contrib-copy": "latest",
"grunt-contrib-jasmine": "latest",
"grunt-contrib-jshint": "latest",
"grunt-contrib-uglify": "latest",
"grunt-contrib-watch": "latest",
"grunt-html-build": "latest",
"grunt-ngmin": "latest",
"grunt-template-jasmine-requirejs": "latest",
"grunt-text-replace": "~0.3.12",
"grunt-serve": "latest",
"grunt-typescript":"latest",
"grunt-curl":"latest"
}

Ah, if I put Explore/www/dist it works, but how would I copy the contents of dist into www directly?


Add 'λ' glyph

Adds a lambda 'λ' glyph!
This is from my Comic Shanns fork, Serious Shanns, which I started before I was aware of yours.
 Unfortunately I don't have time to add the styles for the extended charset at the moment, but if you would like to use some or all of my extended styles as a base for additional styles for Comic Shanns Mono I'd be happy to share! Of course, once I get around to adding the extended charset to my fork I'll open a PR for the added styles at that time 😸
To me, the biggest changes in my fork are edits to disambiguate certain glyphs (currently 'a'/'o', 'l'/'1', and 'Y'/'y'). In my mind it seems sensible to keep Comic Shanns Mono close to the original without messing with these glyphs, but if you think differently and would like to use them then as above I'd be happy to share!
Thanks for maintaining this awesome font!

Thank you! I will indeed take a look at your fork. Feel free to submit the changes when you can, sounds like a good addition.


ci(actions): update renovatebot/github-action action to v40.2.0

This PR contains the following updates:

Package
Type
Update
Change

renovatebot/github-action
action
minor
v40.1.12 -> v40.2.0

Release Notes

renovatebot/github-action (renovatebot/github-action)
v40.2.0
Compare Source
Features

Add docker-network input param (#853) (c928c7f)

Documentation

update references to actions/checkout to v4.1.7 (4ff182b)
update references to ghcr.io/renovatebot/renovate to v37.399.10 (d9f7b19)
update references to ghcr.io/renovatebot/renovate to v37.409.1 (b1a2cdc)
update references to ghcr.io/renovatebot/renovate to v37.414.1 (ed5f0a1)
update references to ghcr.io/renovatebot/renovate to v37.421.3 (9f6242a)
update references to renovatebot/github-action to v40.1.12 (1d7e888)

Miscellaneous Chores

deps: update commitlint monorepo to v19 (major) (#844) (34e6b8d)
deps: update dependency @semantic-release/github to v10.0.6 (847b012)
deps: update dependency @types/node to v20.12.13 (1e8ce71)
deps: update dependency @types/node to v20.13.0 (359b038)
deps: update dependency @types/node to v20.14.0 (6cc1def)
deps: update dependency @types/node to v20.14.1 (d9cd851)
deps: update dependency @types/node to v20.14.2 (c7042bf)
deps: update dependency @types/node to v20.14.4 (49567cf)
deps: update dependency @types/node to v20.14.5 (f3cb0cb)
deps: update dependency @types/node to v20.14.6 (9d5ef66)
deps: update dependency @types/node to v20.14.7 (26228c5)
deps: update dependency @types/node to v20.14.8 (bbad4ca)
deps: update dependency conventional-changelog-conventionalcommits to v8 (#845) (baa196d)
deps: update dependency lint-staged to v15.2.6 (86e740b)
deps: update dependency lint-staged to v15.2.7 (f3a7571)
deps: update dependency prettier to v3.3.0 (9677d0a)
deps: update dependency prettier to v3.3.1 (0559cdb)
deps: update dependency prettier to v3.3.2 (a78922f)
deps: update dependency semantic-release to v24 (#854) (38db792)
deps: update pnpm to v9 (#847) (642ac77)
deps: update pnpm to v9.1.4 (6ecec78)
deps: update pnpm to v9.2.0 (749814c)
deps: update pnpm to v9.3.0 (1c2bc6d)
deps: update pnpm to v9.4.0 (4e8557f)
deps: update semantic-release monorepo (major) (#848) (bfe0ea9)

Build System

deps: lock file maintenance (f9e5140)
deps: lock file maintenance (859f2d0)
deps: lock file maintenance (f0aa6a9)
deps: update dependency typescript to v5.5.2 (eeae706)

Continuous Integration

deps: update actions/checkout action to v4.1.7 (d92d1c6)
deps: update renovate docker tag to v37.388.0 (e58e07a)
deps: update renovate docker tag to v37.388.1 (b969215)
deps: update renovate docker tag to v37.390.0 (6537120)
deps: update renovate docker tag to v37.390.1 (b39ccad)
deps: update renovate docker tag to v37.391.0 (b390760)
deps: update renovate docker tag to v37.392.0 (b62d5e0)
deps: update renovate docker tag to v37.393.0 (2616b2e)
deps: update renovate docker tag to v37.395.0 (bed7655)
deps: update renovate docker tag to v37.399.0 (2040c48)
deps: update renovate docker tag to v37.399.10 (225db92)
deps: update renovate docker tag to v37.399.3 (88330a2)
deps: update renovate docker tag to v37.399.8 (cac78b1)
deps: update renovate docker tag to v37.401.1 (b45d221)
deps: update renovate docker tag to v37.401.2 (7a3b5f2)
deps: update renovate docker tag to v37.401.4 (d73e4b3)
deps: update renovate docker tag to v37.401.5 (a97d457)
deps: update renovate docker tag to v37.402.1 (203a2e1)
deps: update renovate docker tag to v37.404.1 (b7493c5)
deps: update renovate docker tag to v37.406.1 (9844fc5)
deps: update renovate docker tag to v37.406.2 (6b1676d)
deps: update renovate docker tag to v37.407.1 (5428f14)
deps: update renovate docker tag to v37.407.2 (0f6ba96)
deps: update renovate docker tag to v37.407.3 (186a106)
deps: update renovate docker tag to v37.408.0 (d0274f1)
deps: update renovate docker tag to v37.408.1 (56ab7c8)
deps: update renovate docker tag to v37.408.2 (23ad392)
deps: update renovate docker tag to v37.409.0 (d00fdff)
deps: update renovate docker tag to v37.409.1 (9936cc1)
deps: update renovate docker tag to v37.410.1 (07c293a)
deps: update renovate docker tag to v37.410.2 (8501ada)
deps: update renovate docker tag to v37.412.1 (a91a675)
deps: update renovate docker tag to v37.412.2 (91a706b)
deps: update renovate docker tag to v37.413.1 (4bc2e47)
deps: update renovate docker tag to v37.413.2 (82cd1a4)
deps: update renovate docker tag to v37.413.3 (c183ec8)
deps: update renovate docker tag to v37.413.4 (195bea4)
deps: update renovate docker tag to v37.414.0 (3c2f890)
deps: update renovate docker tag to v37.414.1 (8efba2f)
deps: update renovate docker tag to v37.415.0 (221a5ff)
deps: update renovate docker tag to v37.417.1 (7850b39)
deps: update renovate docker tag to v37.419.0 (b297b93)
deps: update renovate docker tag to v37.419.1 (b4f97bb)
deps: update renovate docker tag to v37.420.1 (6a8705c)
deps: update renovate docker tag to v37.421.0 (b79224e)
deps: update renovate docker tag to v37.421.1 (d210104)
deps: update renovate docker tag to v37.421.2 (1b88eda)
deps: update renovate docker tag to v37.421.3 (3172258)
deps: update renovate docker tag to v37.421.5 (5a127d9)
deps: update renovate docker tag to v37.421.6 (031bba2)
deps: update renovate docker tag to v37.421.7 (c9067a7)
deps: update renovate docker tag to v37.421.9 (59545c6)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.

:tada: This issue has been resolved in version 1.4.7 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


onChange gets called with an empty array

I've set up a TagInput pretty similar to the way it's set up in the example. When I type a new tag, the previous tag gets removed.
I suspect it's because of this line: https://github.com/jwohlfert23/react-native-tag-input/blob/90e8a50d187a807b58ff3454eb25ce31c478b78f/index.js#L219
What's the purpose of this line?

Even i am facing the same issue.

Which version of RN? >= 0.54?
Dupe of this? https://github.com/jwohlfert23/react-native-tag-input/issues/55

0.55 on iOS.

There is a bug in recent versions of RN where Backspace gets called incorrectly when the TextInput is cleared, so it doesn't return in the 'if' check below and then gets pop'd. And I think another bug where the value wasn't getting set right.
if (this.props.text !== '' || event.nativeEvent.key !== 'Backspace') {
      return;
}
const tags = [...this.props.value];
tags.pop();

There are PR's up that fix it, but who knows when it'll make it out to release. Have a branch off of 0.55.4 with the 2 patches applied that fixed the issues for me, if useful to anyone.
https://github.com/nol13/react-native/tree/TextInput-Patch-0.55.4

Ya two issues, need both patches to get normal behavior. Not really sure of/qualified to speak about the relative merit of 19087 vs. 18456, as far as I can tell both work, just need one or the other.
The backspace patch is needed to fix the issue where you can only add one tag. The other fixes a bunch of weird behavior where the js and native values can get out of sync or something after adding a few tags, and events stop firing, backspace will delete tags even if there is still text, etc.

@nol13 any workaround for expo users?

i think downgrading to expo 25 would do it, if that's a possibility.
(and saw backspace fix merged, thanks for moving that along!)

Expo 25 is deprecated. Still getting this issue in the latest version of expo.


Adding 'fixed geometries' before executing tool on thematic and referencelayer

The brdr -library makes all geometries valied (make_valid) when loading them.
But in brdrQ there are steps before, where the thematic and referencelayers are used (adding ID etc).
When input geometries are invalid the brdrQ stops working on these steps.
It would be a good step to add 'fix geometries' in the preparation step of the thematic and local referencelayer.
(when using the downloads (adp adpf2024 etc) this will give no problems for the referencelayers because geometries are downloaded and made valid inside the brdr logic)

Fixed geometries already used in code, but not as i first step.
In the thematic layer we could place it as a first step? But in the referencelayer (fe. all parcels of flanders) it will slow down the script. At the moment we first make a selection of the relevent parcels and we execute a 'fix geometries' only on these parcels

"Object (23198) van “Adp12041B500” heeft een ongeldige geometrie. Repareer de geometrie of wijzig de optie “Ongeldige invoerobjecten filteren“ voor deze invoer of globaal in de instellingen van Processing.
Execution failed after 2.21 seconden"

fixed by setting context:
context.setInvalidGeometryCheck(QgsFeatureRequest.GeometryNoCheck)


Reverse conversion: HFS+ to HFS

It would also be useful to convert HFS+ volumes to HFS, or “zip up” real-world folders into HFS volumes. (The latter might end up similar, UI-wise, to hdiutil create.)
Subcommands I thought of for these, as recorded in NOTES.md, are downgrade for reverse-conversion (though it could just be under convert, if that's given an HFS+ volume as its first argument), and archive for zipping-up.
archive might be sufficient to start with. As long as it's possible to mount HFS+, you can archive a mounted volume and it'll solve pretty much the same needs as downgrade. The main benefits of downgrade are that (1) it would be one step instead of two, and (2) it would continue to work if support for HFS+ is pulled entirely someday.
Some things that would need to be handled:

(from NOTES) Extended attributes can be silently dropped because they can't reasonably be persisted
(from NOTES) Long filenames will be tricky. Could fail hard, or silently truncate, or borrow the Windows 95 solution of “Blah Blah Blah~1”.
Then there's encodings. HFS+ is Unicode; HFS… is not. I would probably need to make this an argument, and even then, it could fail.
(from NOTES) Files without type and creator codes would need them added (Launch Services might be able to help with at least some of that, though some translation to common Classic Mac creator codes might still be needed).
(from NOTES) Also, we'll need to fail hard for files too large or numerous to be encoded in an HFS volume.

I think Apple implemented support for large files even on HFS at one point. I should look into how those get represented by Mac OS 9. Particularly the logical length, which is represented as an int32_t…

(from NOTES) Hardest part might be needing to build a reasonable B*-tree from scratch, not having an existing one to copy off of.

I don't actually think building a B*-tree is that hard at this point, given how I ended up implementing the tree builder. The foundation of the tree is the leaf row, which can easily be built from a flat list of items. The rest of the work is building zero or more index rows over that row. I don't think I'm even using the depth field from the original tree, so it could work basically as-is.

Coming from that discussion: Apparently fdScript/frScript isn't really used, as far as I can tell.
I wonder what would happen if the reverse converter set it.


Use MySQL in a container instead of CloudSQL?

Using MySQL in a container instead of CloudSQL may increase performance.  Investigation is required to assert this.

Thanks for the idea, putting into our planning backlog.

Just a stream of thoughts....

Installation times will be faster if not dependent on a CloudSQL instance
Decreased cost
Less network traversal

https://github.com/forseti-security/helm-charts/issues/28


[GHSA-h574-6646-vfxx] Apache Airflow: Ignored Airflow Permission

Updates

Affected products
References

Comments
Add patch links related to CVE-2024-28746 which fixed in multi-branches.

Hi @sunSUNQ, I'm not accepting these links because they're all cherry picked from https://github.com/apache/airflow/commit/89e7f3e7bdf2126bbbcd959dc10d65ef92773cca, which is already present in the advisory's reference links. Thank you for your interest in GHSA-h574-6646-vfxx!


Crash on adding more than one scene instance with an OmniLight3D

Godot version
4.2.beta5
System information
Godot v4.2.beta5 - macOS 10.14.6 - Vulkan (Forward+) - dedicated NVIDIA GeForce GT 750M - Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz (8 Threads)
Issue description
For some reason, including more than one scene instance with an OmniLight3D crashes Godot. Sometimes it's forced my computer to reboot, other times it just freezes the engine. I noticed this when I wanted to make a glowing collectable. It doesn't seem to be a problem when the scene that the instances are put into is completely blank save for a root Node, it seems to happen when light is being cast on a mesh.
Steps to reproduce
Create a scene with a root Node and a MeshInstance3D plane, and a scene with a root Node3D and an OmniLight3D. Drag out two of the latter into the former.
Minimal reproduction project
N/A

Vulkan (Forward+) - dedicated NVIDIA GeForce GT 750M

Vulkan-based renderers are not supported on NVIDIA GPUs on macOS, so please switch to the Compatibility rendering method. I'm surprised Forward+ even started on your machine…

Dang, I didn't know. That's wild, I've had no issues other than this! Switching renderer resolved the issue, but now my shader doesn't work anymore... I'll have to figure that one out on my own, I guess. Mobile renderer seems to work too, btw, and gets the lighting looking a lot nicer


dependency management

Use maven or gradle to import the needed dependencies. It is easier for an end-user to start your editor :D

Or just provide a built release ;)

I am using Maven now ;)


TCP connection timeout, SO_KEEPLIVE, etc cannot be configured in HTTP Client connector

Description:
$subject.

Closing this as this is already fixed.


Sounds great!

I was looking for a way to develop minecraft plugins or mods in python, I found your repository and this seems like a great idea!
Can you do a little more ? Like basic events would be neat, and addon support might be an excellent thing to do 👍

I am working on an update that includes events, but I don't know what is addon support is.

just a qustion bc im slow
will this make it so im able to make a mod with python that works with fabric mods????

I am working on an update that includes events, but I don't know what is addon support is.

addon is the bedrock verion of a "modding api" kinda like java minecraft has datapacks but more closer to modding then datapacks are


Eliminate unreachable statement

The statement is unreachable which will be detected by dmd when compiling with dub build --build=profile.

Duplicate of https://github.com/dlang/phobos/pull/6621?

True. So, I close this PR.


Default value makes optional, nullish, nullable as required

As soon as i add a default value to optional, nullish, nullable,
these all become required.
To reproduce the error:
No default value, everything works as expected:
const schema = object({
  key: string([minLength(1), toTrimmed()]),
  type: optional(string()),
  reserved: optional(boolean()),
})
type SchemaTypes = Output<typeof schema>

With default value, now type and reserved are required:
const schema = object({
  key: string([minLength(1), toTrimmed()]),
  type: optional(string(), ''),
  reserved: optional(boolean(), false),
})
type SchemaTypes = Output<typeof schema>

Here you have to distinguish between input and output. As you noticed, the output type can no longer be undefined when using a default value. Therefore the output type can only be string. But it is different for the input. There type and reserved are still optional:
// Create schema
const Schema = object({
  key: string([minLength(1), toTrimmed()]),
  type: optional(string(), ''),
  reserved: optional(boolean(), false),
})

// Get input type
type SchemaInput = Input<typeof schema>;

// Get output type
type SchemaOutput = Output<typeof schema>;

You can find more info here: https://valibot.dev/guides/infer-types/

Thanks for the explanation, it totally makes sense now


PSP deletion issues.

Rancher server - Build from master
Steps to reproduce the problem:
Created PSP - psp1, psp3
Create a cluster with default PSP set to psp1.
Create a project under this  cluster with psp3.
Deleted the project.
This should have resulted in PSP being created from the cluster when queried using kubectl.
The PSP is still present in the cluster.
LaviniapleWatch:bin sangeethahariharan$  kubectl get podsecuritypolicies
NAME          DATA      CAPS      SELINUX    RUNASUSER   FSGROUP    SUPGROUP   READONLYROOTFS   VOLUMES
default-psp   true      [*]       RunAsAny   RunAsAny    RunAsAny   RunAsAny   false            [*]
psp1-psp      false     []        RunAsAny   RunAsAny    RunAsAny   RunAsAny   false            [*]
psp3-psp      false     []        RunAsAny   RunAsAny    RunAsAny   RunAsAny   false            []

Following errors seen in logs:
E0420 21:25:15.105748       1 generic_controller.go:204] ProjectController c-p65kq/p-jbj5c [mgmt-project-rbac-remove] failed with : failed to remove finalizer on c-p65kq:p-jbj5c
E0420 21:25:15.121516       1 generic_controller.go:204] ProjectController c-p65kq/p-jbj5c [mgmt-project-rbac-remove] failed with : failed to remove finalizer on c-p65kq:p-jbj5c
E0420 21:25:15.141208       1 generic_controller.go:204] ProjectController c-p65kq/p-jbj5c [project-namespace-auth] failed with : failed to remove finalizer on c-p65kq:p-jbj5c
E0420 21:25:20.230235       1 tokens_controller.go:259] error synchronizing serviceaccount p-jbj5c/default: secrets "default-token-8wn76" is forbidden: unable to create new content in namespace p-jbj5c because it is being terminated.
E0420 21:25:20.243914       1 tokens_controller.go:259] error synchronizing serviceaccount p-jbj5c/default: secrets "default-token-58nhm" is forbidden: unable to create new content in namespace p-jbj5c because it is being terminated.
E0420 21:25:20.258507       1 tokens_controller.go:259] error synchronizing serviceaccount p-jbj5c/default: serviceaccounts "default" not found
E0420 21:25:20.321362       1 generic_controller.go:204] ProjectRoleTemplateBindingController p-jbj5c/creator [cluster-prtb-sync] failed with : failed to remove finalizer on p-jbj5c:creator

Delete psp2.
After this delete , psp2 continues to be listed in rancher server.
But it is deleted from cluster when queried using kubectl.
Following errors seen in logs:
E0420 21:26:54.999224       1 generic_controller.go:204] PodSecurityPolicyTemplateController psp3 [mgmt-pspt-lfc-handler] failed with : error deleting psptpb: an empty namespace may not be set when a resource name is provided
E0420 21:26:55.010324       1 generic_controller.go:204] PodSecurityPolicyTemplateController psp3 [mgmt-pspt-lfc-handler] failed with : error deleting psptpb: an empty namespace may not be set when a resource name is provided
E0420 21:26:55.046863       1 generic_controller.go:204] PodSecurityPolicyTemplateController psp3 [pspt-sync] failed with : failed to remove finalizer on :psp3
E0420 21:26:55.050357       1 generic_controller.go:204] PodSecurityPolicyTemplateController psp3 [mgmt-pspt-lfc-handler] failed with : error deleting psptpb: an empty namespace may not be set when a resource name is provided
E0420 21:26:55.499694       1 generic_controller.go:204] PodSecurityPolicyTemplateController psp3 [mgmt-pspt-lfc-handler] failed with : error deleting psptpb: an empty namespace may not be set when a resource name is provided
E0420 21:26:59.500160       1 generic_controller.go:204] PodSecurityPolicyTemplateController psp3 [mgmt-pspt-lfc-handler] failed with : error deleting psptpb: an empty namespace may not be set when a resource name is provided
E0420 21:27:07.500629       1 generic_controller.go:204] PodSecurityPolicyTemplateController psp3 [mgmt-pspt-lfc-handler] failed with : error deleting psptpb: an empty namespace may not be set when a resource name is provided
E0420 21:27:23.501106       1 generic_controller.go:204] PodSecurityPolicyTemplateController psp3 [mgmt-pspt-lfc-handler] failed with : error deleting psptpb: an empty namespace may not be set when a resource name is provided
E0420 21:27:55.501584       1 generic_controller.go:204] PodSecurityPolicyTemplateController psp3 [mgmt-pspt-lfc-handler] failed with : error deleting psptpb: an empty namespace may not be set when a resource name is provided

I think this issue contains multiple separate issues

the titular issue - not deleting PSPs when a project is deleted
this error error synchronizing serviceaccount p-jbj5c/default: secrets "default-token-58nhm" is forbidden: unable to create new content in namespace p-jbj5c because it is being terminated.
this error E0420 21:27:55.501584       1 generic_controller.go:204] PodSecurityPolicyTemplateController psp3 [mgmt-pspt-lfc-handler] failed with : error deleting psptpb: an empty namespace may not be set when a resource name is provided

Regarding the first issue: this is behaving as intended. We are effectively lazy loading the PSP when it is referenced by a project or cluster. But, we intentionally do not delete it if a project stops using it. It will be deleted when and if the PSPT is deleted. Otherwise, it will remain in the cluster in case it is later referenced by another project or by the cluster default. Leaving it there has no ill effects.
Can we open up separate issues for 2 and 3?

@cjellick Logged 2 different issues to track the issues mentioned in the bug other than the   lazy loading of the PSP when it is referenced by a project or cluster which is the expected behavior.
Logged - https://github.com/rancher/rancher/issues/15727 to track
this error error synchronizing serviceaccount p-jbj5c/default: secrets "default-token-58nhm" is forbidden: unable to create new content in namespace p-jbj5c because it is being terminated.

Logged https://github.com/rancher/rancher/issues/15728 to track
E0420 21:27:55.501584 1 generic_controller.go:204] PodSecurityPolicyTemplateController psp3 [mgmt-pspt-lfc-handler] failed with : error deleting psptpb: an empty namespace may not be set when a resource name is provided

Closing this issue since we are tracking the 2 scenarios mentioned in 2 new issues.


Mismatched offset caused by duplicate part name with old file  use s3store.

Describe the bug
Preondition: s3store & specificed FileInfoChanges.ID from filename in PreUploadCreateCallback.
An old file named example.file.part, could be an object, could be the last failed upload remained. If it exists, client can't upload the file named example.file.
Error message is ERR_MISMATCHED_OFFSET: mismatched offset.
To Reproduce
Steps to reproduce the behavior:
Method 1:

Start a tusd server that use s3store & specificed FileInfoChanges.ID from filename in PreUploadCreateCallback.
Upload a file named example.file.part.
Upload a file named example.file Error.

Method 2:

Start a tusd server that use s3store & specificed FileInfoChanges.ID in PreUploadCreateCallback &  PreferredPartSize=10MB.
Upload(chunk_size=11MB) an object named example.file(size>50MB), and inertrupt upload when part file appear.
Upload a file named example.file Error.

Expected behavior
Upload example.file Success.
Setup details
Please provide following details, if applicable to your situation:

Operating System: macOS
Used tusd version: v2.4.0
Used tusd data storage: AWS S3
Used tusd configuration: see reproduce
Used tus client library: tuspy

First of all, apologies for my late response! My first thought here is that this is not directly what I consider a bug in tusd. When you are specifying a custom upload ID, its your task to ensure that this ID does not cause collisions with resources from other uploads. This can either achieved by deleting the resources belonging to the other uploads, or - what we usually recommend - by including a random part in the upload ID. If you really want to keep the original filename (which is already questionable), you can use IDs with the format {RANDOM UUID}/{FILENAME}.{EXTENSION}
That being said, I will see if we can improve the documentation for FileInfoChanges.ID to make these caveats clearer

Added documentation in https://github.com/tus/tusd/commit/57d06cf2901de3bdde208d40cb388adaeece6196.

You are correct, and the original file name may contain many special characters, leading to numerous exceptions if used as an UploadID. I ultimately resolved this issue through the PreFinishResponseCallback.


Add button toggle stats to enable/disable stats

A new toggle button has been added "Enable Stats" / "Disable Stats" to the UI
When enabled, stats are displayed in the console logs
Need to update sample with WatchRTC SDK > 1.38.beta5 in order to work

WatchRTC SDK > 1.38.beta5 fixes the build issue


lobmarib gwt2.8 improvements

Finally I could create the correct pull request.
Please feel free to comment

Hello Marco,
thanks for your contributions. One pull request with changes in 31 files is hard to merge. So please make pullrequests per feature next time.
Before I can merge this you have to remove your copyright entries in the classfile header because the project is licensed under the Apache License, Version 2.0. You can put the autor and the date in the class header.
You can remove the JSProperty names if they follow getter / setter syntax.
Regards
Tino

Hi Tino,
I did those changes to fulfill my needs in a project and then I decided to share them, that's why I have so many changes in just one go... Sorry about that. Next time I will do it by feature.
Yes, I just forgot to select the correct file headers.
Going to do that changes in a moment.
Regards
Marco

Hello Marco,
no problem! Let me know if I can help you.
Regards
Tino

Thanks!


Research into which condition(s) CDC will accept for OTC data

User Story
As a researcher on ReportStream, I want to figure out which condition(s) the CDC will accept regarding OTC data, so that I can inform the RADxMARS software requirements regarding the removal of unwanted conditions during translation.
Background
The RADxMARS SRD is currently being created to understand how ReportStream should receive OTC data from Senders in a RADxMARS profile, and appropriately send that data to Receivers in that same profile. For our pilot program, we are working solely with makemytestcount.org (MMTC) as a Sender of OTC data. There are a few hard requirements from our MMTC & NIH stakeholder:

ReportStream shall convert any unwanted conditions from OBX to NTE segments
ReportStream will remove all NTE segments to support the RADxMARS de-identification rules, except for converted OBX segments

For this ticket's purpose, we want to know, in this order:

If the CDC, as a receiver, wants all conditions sent
If the CDC wants only some conditions sent
If the CDC only wants, some conditions sent, do they care about receiving "unwanted conditions" as NTE

Ultimately, removing all NTE is easier and simpler for engineering. So it'll be good to know if we need to keep some NTE (the converted OBX segments) for CDC, or if we can just remove them all.
Risks/Impacts/Considerations

Delays or dependencies are possible if it turns out that CDC does want to see unwanted OBX segments as NTE (and therefore it's not an easy of a job as hoped for)
It remains to be seen which organization(s) and stakeholders are affected or should be included in this ticket between DEX, HHSProtect and DCIPHER

Open Questions

See above in Background

Links

#13799: Implement RADxMARS OTC De-Identification Support
SRD-RadxMars-OTC
RADxMARS Product Requirements

Acceptance Criteria

[ ] Find out which condition(s) CDC wants to accept for OTC data
[ ] Find out what the CDC would like to see with regards to unwanted conditions as NTE

Out of Scope

STLTs don't get a choice if they do or do not want to receive unwanted OBX as NTE (they will just receive them anyway), so this ticket is not for STLTs

Noting for future purposes; this ticket was created in a response to a discussion in Platform Stand-Up, but as Arnej noted, it will be de-prioritized for now because Product wants to approach this type work in a longer-term, more strategic manner. As such, this ticket will not be relevant until later in the quarter. Date: 3/26/24. cc @Andrey-Glazkv @jsutantio @jillian-hammer @arnejduranovic

##Ticket Housekeeping!
@arnejduranovic I think the main part of this potential ticket is solved...to my knowledge the logic is that c) CDC/STLTs may want only some conditions sent so they will receive "unwanted conditions" as NTE. If that's correct, then I will close out of this ticket. cc @Andrey-Glazkv.

@dylansmith-Nava Yes we have the ability to do this (via FHIR->HL7v2 transforms). I would talk to SME @GilmoreA6 to see if the condition actually matters in the context of removing unwanted conditions. I think the answer is "no" but we should verify with James before closing.

@arnejduranovic what do you mean exactly by the condition "mattering"?

@arnejduranovic what do you mean exactly by the condition "mattering"?

I am under the assumption that the logic for removing unwanted conditions is the same regardless of what the actual condition is. We should confirm this assumption with a SME.

As part of the eventual onboarding process with CDC DCIPHER, RS Product will figure out the answers to the primary questions and assumptions in this ticket, being that via the RadxMars topic:

What condition(s) does DCIPHER want?
Does DCIPHER want unwanted conditions dropped or as NTE? (Assumption is NTE as per the RadxMars spec)

As such, this ticket is not relevant and will eventually be solved by Product, not by Platform D/R. I will go ahead and close the ticket after chatting with @arnejduranovic. cc @Andrey-Glazkv


Action for Stale issues/PR(s)

This github action will mark stale (unattended) issues and PR(s).
In reference to #62

This is not needed and was never a part of the issues I created. However I will consider reopening this later. Thanks for your contributions.