Add test case for AbstractShenyuWasmPlugin

#5427

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

@loongs-zhang I am getting a null pointer exception here could you please take a look?

WARNING: If a serviceability tool is not in use, please run with -Djdk.instrument.traceUsage for more information
WARNING: Dynamic loading of agents will be disallowed by default in a future release
Java HotSpot(TM) 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended
18:03:17.704 [main] DEBUG io.github.kawamuray.wasmtime.NativeLibraryLoader - Loading Wasmtime JNI library from C:\Users\Divyansh\AppData\Local\Temp\wasmtime_jni_0.19.0_windows_x86_648134173620995520118.dll
18:03:17.760 [main] DEBUG io.github.kawamuray.wasmtime.Func - New trampoline 0 of type FuncType(params=[I64, I64, I32], results=[I32])
18:03:17.763 [main] DEBUG io.github.kawamuray.wasmtime.Func - New trampoline 1 of type FuncType(params=[I64, I64, I32], results=[I32])
18:03:18.280 [main] DEBUG reactor.util.Loggers - Using Slf4j logging framework
rust side-> buffer base address: 1048496
18:03:19.532 [main] DEBUG io.github.kawamuray.wasmtime.Func - Trampoline 0 invoked with params=[Val(type=I64, value=0), Val(type=I64, value=1048496), Val(type=I32, value=32)], results=[null]
18:03:19.533 [main] INFO org.apache.shenyu.plugin.wasm.base.AbstractShenyuWasmPlugin - java side->hello from java 0
rust side-> recv:hello from java 0
18:03:19.539 [main] DEBUG io.github.kawamuray.wasmtime.Func - Trampoline 1 invoked with params=[Val(type=I64, value=0), Val(type=I64, value=1048780), Val(type=I32, value=11)], results=[null]
18:03:19.539 [main] INFO org.apache.shenyu.plugin.wasm.base.AbstractShenyuWasmPlugin - java side->rust result
18:03:19.544 [main] ERROR org.apache.shenyu.plugin.wasm.base.AbstractShenyuWasmPlugin - doExecute function not found in org.apache.shenyu.plugin.wasm.base.AbstractShenyuWasmPluginTest$RustShenyuWasmPlugin.wasm

java.lang.NullPointerException: Cannot invoke "org.apache.shenyu.plugin.api.result.ShenyuResult.error(org.springframework.web.server.ServerWebExchange, int, String, Object)" because the return value of "org.apache.shenyu.plugin.api.result.ShenyuResultWrap.shenyuResult()" is null

It seems that you did not regenerate the wasm file, please refer to https://github.com/apache/shenyu/blob/master/shenyu-plugin/shenyu-plugin-wasm-api/src/test/README.md

It seems that you did not regenerate the wasm file, please refer to https://github.com/apache/shenyu/blob/master/shenyu-plugin/shenyu-plugin-wasm-api/src/test/README.md

I actually did generate the wasm file and according to the documentation I put it in the resources folder

see https://github.com/apache/shenyu/pull/5450


EXT-FSS2 Added support for React Native 0.73

Update build.gradle to set sourceCompatibility and targetCompatibility to JavaVersion.VERSION_11 for AGP versions below 8

Added support for React Native 0.73

The build fails on React Native 0.73 for Android due to a Kotlin version inconsistency. This can be resolved by adhering to the expo commit standard for Kotlin versioning

Self Review:

[ ] Appropriate test coverage
[ ] Relevant Documentation updated

Smoke Tests:

[ ] ...

Hi @ball-hayden one more


fix: typing

For #23 , #24
Add geostyler type :tada:  and references issue related to types (see newly created issues).
Complete "by hand" esri types.

:tada: This PR is included in version 1.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


parser, ast: add ColumnOptionCollate for all column types (#260)

What problem does this PR solve?
Cherry-pick https://github.com/pingcap/parser/pull/260

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

PTAL @crazycs520 @winkyao

/run-all-test  tidb-test=pr/786


Formatting Preference for Contributions with Series Content

I was curious if there is any preferred formatting for content that is part of a series.
Some articles that come to mind are A Trip Through The Graphics Pipeline (which could have a general tag of GPU hardware and pipelining) or Carnegie Mellon's Computer Graphics Course (which could include everything from mesh processing to path tracing, to just a general tag "course").
Each section has has an area of focus, so the tags would be more specific, but at the same time submitting each segment individually could be undesirable for organizational reasons.

That's an interesting point! I wonder if it would make sense to have a "master" entry that can then link out to the individual entries, which could then have their own tags.

I thought some more about this and I could see different situations where different behaviors are preferable. Using the above content as example pieces:

If I wanted to search for courses in general, seeing ~25 entries for a single course might be undesirable
If I wanted to search for primitive assembly, I would mainly only care about part 5 of a trip through the graphics pipeline

I'm not sure which case is more common or preferable, but I think @TheRealMJP's point about "master" entries lines up with how, for instance, ACM's digital library entries for journals work.


Feature: Docs, component, package updates

Closes #5846

Does this really need a second review? Otherwise let's just merge it :)


Contact emails should be validated client and server side

At the very least, they need to have an @ sign...

Can we create an error message on the page if they input something that's
missing the @ sign?
On Wed, Dec 18, 2019 at 4:42 PM Razzi Abuissa<EMAIL_ADDRESS>wrote:

At the very least, they need to have an @ sign...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/razzius/hms-weave/issues/145?email_source=notifications&email_token=AKOFUUJL6OQFHZC7IM42VJLQZK7ORA5CNFSM4J4WIGQKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IBP2APA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKOFUUIVWW56TTLJL2GBCI3QZK7ORANCNFSM4J4WIGQA
.

Yeah, I'll explore some ways to inform the user


Fix compute in HammingDistance object

Hamming distance via bit sampling LSH is size of symmetric difference set.

The failed test is irrelevant to this pr.

That failing test may be flaky; agreed that it's irrelevant.
Could you add a test that demonstrates the difference between the current behavior and the new behavior, though? See [https://github.com/karlhigley/spark-neighbors/blob/master/src/test/scala/com/github/karlhigley/spark/neighbors/DistanceMeasureSuite.scala#L40](this test) as a starting point.

Closing and re-opening to trigger a new build.

No worries! Thanks for reviewing the distance computations. I learned about diff from your PR.

I appreciate your kind words :)


Packaging external node_modules

Is your feature request related to a problem? Please describe.
I have a use case where an npm module I depend on uses readFileSync to pull in a file. This results in my bundle failing when executing in a cloudwatch synthetics context.

ERROR: Canary error:
Error: ENOENT: no such file or directory, open '/opt/nodejs/dom-testing-library.js'

Describe the solution you'd like
Is there a way to configure the esbuild through this module to copy the node_modules, and have the bundle resolve the node_modules?
Describe alternatives you've considered
Rewriting the dependency so it does not do this...
Additional context
The dependency is https://github.com/testing-library/pptr-testing-library/blob/main/lib/index.ts#L8-L11

It looks like the copyDir prop might be what I want.
But using it say with ./node_modules/pptr-testing-library will copy the contents into the root directory of the asset bundle ignoring the outDir: nodejs/node_modules that i'm using to bundle for Synthetics
I changed this line
https://github.com/mrgrain/cdk-esbuild/blob/163b38c3940bdf4d796520dab5a2817dbc810161/src/bundler.ts#L121
to:
path.join(outputDir, 'nodejs/node_modules')

Thinking that by getting the assets in the same location of the bundle the intent would be to package it and send it to s3.
However the error I get when I use the changes looks like:
Bundling asset FooBar0/TypeScriptCode/Stage...
Error: Failed to bundle asset FooBar0/TypeScriptCode/Stage, bundle output is located at /Users/azaharakis/FooBar/cdk.out/bundling-temp-48a6bfb0079015bedd2abb1e6747dd6ea88fcf0d4e38044a5e19506e68766d7b-error: TypeError: messages is not iterable

Not entirely familiar with es-build and synthetics packaging requirements. So still poking around the logs of the output

Apologies, I've been travelling. Will look at this asap.
I think the issue is that esbuild is bundling all dependencies into a single file and pptr-testing-library then gets confused about where the files should be. There should be a way to tell esbuild how to do this. The easiest thing to do might be to just NOT bundle.

Hi @mrgrain, no apologies needed, wasn't even expecting a response tbh :)

I think the issue is that esbuild is bundling all dependencies into a single file and pptr-testing-library then gets confused about where the files should be

Yep thats right. pptr-testing-library is unable to resolve the dependency because readFileSync isn't evaluated by esbuild or any bundler for that matter the same way as import/require is.

The easiest thing to do might be to just NOT bundle.

I would have thought so as well. But i've had difficult finding good examples of synthetics asset implementations that take this approach on anything non trivial. From what I understand i'd need to:
Upload my asset as a zip to s3 in the directory structure that looks something like this:
nodejs/
├─ node_modules/
│  ├─ pptr-testing-library
│  ...
│  ├─ canary-handler.js

But there are a couple of issues i've found so far going down this approach.

This construct allows you to statically define what you want to be uploaded to s3 (Ideally I wanted to avoid writing anything custom or any procedural scripts to do this), but it unzips the contents in the bucket instead of keeping it zipped e.g https://github.com/aws/aws-cdk/issues/8065. This is incompatible with Synthetics, Synthetics wants your asset zipped in the bucket.

If you do manage to upload a zip to s3. To make changes to the canary seems to at least require changing the object key e.g my-bucket/canary.asset{timestamp}.zip in order to trigger an update to the stack so synthetics can rebuild the layer from a new zip. If the file name stays the same, but the zip contents change the layer is not updated.

These were the 2 issues prevented me from going down this path further and was hopeful that this library was abstracting the upload to s3 functionality as part of its implementation that would handle all cases for asset publishing to synthetics.

Good questions. This package is using S3Asset to upload the zip to S3. I just have a tiny wrapper around it.
https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_s3_assets-readme.html
Initially I thought it would be enough to do
buildOptions {
  bundle: false
}

but I recall now that Synthetics has some odd requirements with the file system.

Upload my asset as a zip to s3 in the directory structure that looks something like this:

Agreed, that should be the goal and it should be possible with the right combination of outdir, copydir and external.
We also might need an extra node_modules in the tree structure, but that should be easy enough if needed.
PS: I'm aware you probably know all this already. I'm really just writing down my own thought process so I can come back to it later.

tl;Dr This is currentlynot easily possibly with this package or any esbuild features.
I've played around with this on a separate branch. This is the best I came up with. It's untested, but creates the files in the right place:
https://github.com/mrgrain/cdk-esbuild/blob/pptr-testing-library/examples/website/infrastructure/stack.ts#L46
The current implementation of Copydir isn't clever enough to copy the dependency to the correct dir. It's a nice feature idea though and should be easy enough to add support for a map of multiple things to copy into various locations. I don't just want to change it to copy to the outdir, because I originally added the feature to be able to copy files NOT to the outdir.

@mrgrain thank you so much for pointing me in the direction to un-block myself with your provided branch! This particular issue was outside of the scope of this package imo so I really appreciate your help on this!!

The current implementation of Copydir isn't clever enough to copy the dependency to the correct dir. It's a nice feature idea though and should be easy enough to add support for a map of multiple things to copy into various locations. I don't just want to change it to copy to the outdir, because I originally added the feature to be able to copy files NOT to the outdir.

So I understand you are suggesting:
type copyDir: string

extended to say:
type copyDir: string | Record<string,string>

Where in the case of a map the id represents the srcDir and the value representing the destinationDir relative to projects src, not the outDir or if provided from the relative path of absWorkingDir ?

extended to say:
type copyDir: string | Record<string,string>

Yes, that's right. We could also add a string array for even more options:
type copyDir: string | string[] | Record<string,string>

Where in the case of a map the id represents the srcDir and the value representing the destinationDir relative to projects src, not the outDir or if provided from the relative path of absWorkingDir?

We need to be a bit careful here to not mix up the various things. copyDir is a feature added by cdk-esbuild (this package) and has nothing to do with esbuild. I did suggest to add it to esbuild directly, but they understandably didn't want to implement it.
For CDK we need to copy the files into an asset staging area. That's one of the cdk.out/asset.1234hash directories you can see. Let's call this assetDir.
I've also noticed that esbuild uses the id of the map as target, and the valuer as source. It would probably be a good idea to follow that pattern for consistency.
Putting all things together, in the case of a map the id represents the destinationDir relative to the assetDir and the value represents the srcDir relative to the current working dir (same logic as currently done for the string).
These would then all be equivalent:
copyDir: "path/to/files"
copyDir: ["path/to/files"]
copyDir: {
  ".": "path/to/files"
}

PS: I can't remember why I called it copyDir. Pretty sure it can also copy a single file. 😅

Hi @mrgrain, nice one! The implementation looks great! i'll need a bit of time to test it for my use case. Will try to get to it before Monday

@azaharakis I'm probably going to release this on the weekend. No worries if you don't get the testing it. We can always iterate afterwards!

@mrgrain so sorry mgrain, i've been super swamped and I agree and think you should move forward, the implementation looks solid to me

@azaharakis v3.4.0 has been released. I've updated the example branch as well:
https://github.com/mrgrain/cdk-esbuild/blob/a6ce259134419f2858a749bc60131b226ee9affe/examples/website/infrastructure/stack.ts#L46-L59
Please feel free to comment/re-open/open a new issue if this doesn't get you all the way. =D


Don't create virtualizer before panel.

In Itemspresenter:

Don't create virtualizer before panel. Otherwise, an ItemVirtualizerNone is created which can materialize all items, even if ItemVirtualizationMode.Simple is set.
Use weak subscriptions. This not only prevents memory leaks, but also accidental double-subscribes as we have an IDisposable to represent the subscription state.

@danwalmsley : hopefully fixes #1707.
@RayyanTahir: should also fix the problem you were seeing with two listboxes.

I'm still getting an exception, System.ArgumentException: 'An item with the same key has already been added. Key: 1'
StackTrace:
   at System.ThrowHelper.ThrowAddingDuplicateWithKeyArgumentException(Object key)
   at System.Collections.Generic.Dictionary`2.TryInsert(TKey key, TValue value, InsertionBehavior behavior)
   at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
   at Avalonia.Controls.Generators.ItemContainerGenerator.Materialize(Int32 index, Object item, IMemberSelector selector) in C:\Projects\Avalonia\src\Avalonia.Controls\Generators\ItemContainerGenerator.cs:line 65
   at Avalonia.Controls.Presenters.ItemVirtualizerSimple.CreateAndRemoveContainers() in C:\Projects\Avalonia\src\Avalonia.Controls\Presenters\ItemVirtualizerSimple.cs:line 324
   at Avalonia.Controls.Presenters.ItemVirtualizerSimple.ItemsChanged(IEnumerable items, NotifyCollectionChangedEventArgs e) in C:\Projects\Avalonia\src\Avalonia.Controls\Presenters\ItemVirtualizerSimple.cs:line 164
   at Avalonia.Controls.Presenters.ItemsPresenter.ItemsChanged(NotifyCollectionChangedEventArgs e) in C:\Projects\Avalonia\src\Avalonia.Controls\Presenters\ItemsPresenter.cs:line 160
   at Avalonia.Controls.Presenters.ItemsPresenterBase.ItemsCollectionChanged(Object sender, NotifyCollectionChangedEventArgs e) in C:\Projects\Avalonia\src\Avalonia.Controls\Presenters\ItemsPresenterBase.cs:line 257

Please use the repro provided in: https://github.com/AvaloniaUI/Avalonia/issues/1709
The steps to repro are almost similar to https://github.com/AvaloniaUI/Avalonia/issues/1709 as well:

add up to 5 items to listbox.
select first item and remove till the listbox is empty.
add a couple of items
app crashes with the above exception.

@RayyanTahir i've pushed another fix that hopefully will fix what you were seeing!

@RayyanTahir this may also now fix #1723 - could you check?

@grokys Apologies for being late. I've checked, it works great now. Great work and thanks.


Impl: ALU cleanup with enum package

create a package with the instruction, funct3, funct7, alu_ops enums

Enhancement of functional units within the ALU hardware unit to be done. (Multiplier, Adder)


Release 0.1

Hello, Thanks for your pull request. I'd rather not land anything more on the 0.1 branch, we have an 0.2 branch which represents the current release which you should be using instead.

@msorvillo2234 as discussed in https://github.com/heptio/contour/pull/83#issuecomment-349480722 I plan to close this PR without merging it. Please comment if you disagree.

K sounds good.
On Sun, Dec 10, 2017, 8:11 PM Dave Cheney<EMAIL_ADDRESS>wrote:

@msorvillo2234 https://github.com/msorvillo2234 as discussed in #83
(comment)
https://github.com/heptio/contour/pull/83#issuecomment-349480722 I plan
to close this PR without merging it. Please comment if you disagree.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/heptio/contour/pull/83#issuecomment-350599052, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAQuAnFYL9yYBjqQ0KEsoADs8lAZ-Uk9ks5s_IFIgaJpZM4Q2f0G
.


CODE RUB: InvalidCompletionException Class Update v2.10.1

Updated InvalidCompletionException class by removing constructors in which the error message was hard coded in. Updated all relevant service files to include message.

Closed Pull Request. Resolved in PR #557.


When will chromium be available?

I tried using chromium but it was unsupported. Or am I doing something wrong?

+1


Enable the application to use the Checkbox field type instead of Text fields for checkboxes

We use text fields for checkboxes and print a text character to indicate that the checkbox has been ticked or not.  This design makes it harder for case workers to click on checkboxes in Adobe Acrobat to toggle the value.  Instead of clicking once to toggle, they must click into a text field and then remove or add a text value.

Checkboxes should work, when properly labeled: https://districthousing.org/dictionary#tickboxes
In your example image, you should create checkboxes with the following labels:
"Hispanic or Latino" -> EthnicityHispanicTickYes
"Not Hispanic or Latino" -> EthnicityHispanicTickNo
"Male" -> GenderMaleTickYes
"Female" -> GenderFemaleTickYes


Each user in your organization must have a Teams license before they can use Teams.

Article mentioned "Each user in your organization must have a Teams license before they can use Teams". However for joining Teams meetings, no licenses are required Refer: https://docs.microsoft.com/en-us/MicrosoftTeams/quick-start-meetings-live-events#get-licenses-for-meetings-and-live-events.
We should have an * marked next to this mentioning "for meetings refer the meetings article."

@jaspreetjolly  Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.

Hi Manuela, the issue with document is still there. Here is the latest screenshot which still shows "Each user in your organization must have a Teams license before they can use Teams"


Tab Buttons still tappable when alert is shown

I use tab bar controller in my application and when the alert is displayed these remain tappable. Would it be possible to make the alert cover the entire screen?
Great library btw!

Well this is not actually hadeled very well right now, I can create workaround for this usecase in couple of days.... I plan on rewriting most of it in close future tho...

On 30 Apr 2016, at 21:52, Gerard Kelly<EMAIL_ADDRESS>wrote:
I use tab bar controller in my application and when the alert is displayed these remain tappable. Would it be possible to make the alert cover the entire screen?
Great library btw!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

Any updates about this?

Hi, just informing you that I have not forgotten about this, I plan on fixing this with some kind of hotfix, later this week...
Thanks.

@syky27 I've modified JSSAlertView to be presented as a view controller, which I think is the correct approach. I can send a PR if you're interested :)

Go for it I'll check it out!

On 23 May 2016, at 16:36, Mario Cecchi<EMAIL_ADDRESS>wrote:
@syky27 I've modified JSSAlertView to be presented as a view controller, which I think is the correct approach. I can send a PR if you're interested :)
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@gearoidoceallaigh please update to 1.1.5 version
Thanks goes to @macecchi for #42


Autorest Regen Preview to 3.0.0-alpha.20231204.5 by Dapeng Zhang from refs/pull/3838/merge

Triggered from https://github.com/Azure/autorest.csharp/pull/3838

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Data.AppConfiguration


series_premiere and series do not work properly in conjunction

Series_premiere is parsing over series plugin, reproducible by placing series_premier in a task with an entry, example Big Brother US
DEBUG parser_internal tv Parsing series: Big Brother US S04E13 kwargs: {'identified_by': u'auto', u'date_regexps': [], 'strict_name': False, 'name': u'Big Brother US', 'prefer_specials': None, 'special_ids': [], 'alternate_names': [], u'sequence_regexps': [], 'date_dayfirst': None, u'id_regexps': [], 'assume_special': None, 'name_regexps': [], 'date_yearfirst': None, 'allow_groups': [], u'ep_regexps': []}

example config:
template:
  tv:
    thetvdb_lookup: yes
    series_premiere: yes
    exists_series: /TV Shows/{{ tvdb_series_name }}
    series:
      - Big Brother US

tasks:
 tv:
  rss:
  template:
    -tv

some name matching works but some doesnt about 31 days ago. (aug 7th,2017)

To add to this:
This commit https://github.com/Flexget/Flexget/commit/3334586e5a7c257b3795600b5a511e083f9f79c5, introduced a Force flag, which causes metainfo_series to re-parse a show and normalize its series name. Thus "Big Brother US" becomes "Big Brother Us", which breaks series here https://github.com/Flexget/Flexget/blob/develop/flexget/plugins/filter/series.py#L1554-L1555 because "Big Brother US" != "Big Brother Us"


The video completion tick-mark does not persist when the week section is re-opened

When I update the mark as complete check box, it doesn't persist when I close and reopen the week section.

To Reproduce
Steps to reproduce the behavior:

Open the website and log in
Open a video and follow what the video does

Expected behavior
The tick-mark should persist even if I close the week section.
Screenshots or GIFs
https://github.com/code100x/cms/assets/69739582/8093f50a-49ba-4ca8-948e-0250aebf7be3
Info (please complete the following information):

Browser Brave
Version: 1.65.132 Chromium: 124.0.6367.202 (Official Build) (64-bit)

Additional context

I checked the network tab and found ki request for updating the course is running and it's successful. But when I close and open the section, there's no network request that's going to load the data, or I'm not sure how the state is being saved. Maybe the state goes back to default values once the request is being sent.

In this issue when refresh the website then it persiting the mark

Can I get assigned to do this?

I was thinking of using local storage to keep track of each checkbox's state.

Sorry, but the above solution isn't working and I figured out why we are facing this in the first place. The check component is being re-rendered when the accordion is opened or closed, causing the check state to be reset.
We can solve this by moving the check box state management to the parent Sidebar component,
then we will pass the checkbox state and a function to update the checkbox state as a prop to the Check component.

https://www.loom.com/share/8fd99e679c7d4bf9b56612389e04e17e?t=10&sid=f908802e-e4f9-4755-b028-56b5ffafa7c0
And it's working!!!

When I update the mark as complete check box, it doesn't persist when I close and reopen the week section.

To Reproduce Steps to reproduce the behavior:

Open the website and log in
Open a video and follow what the video does

Expected behavior The tick-mark should persist even if I close the week section.
Screenshots or GIFs
out.4.mp4
Info (please complete the following information):

Browser Brave
Version: 1.65.132 Chromium: 124.0.6367.202 (Official Build) (64-bit)

Additional context

I checked the network tab and found ki request for updating the course is running and it's successful. But when I close and open the section, there's no network request that's going to load the data, or I'm not sure how the state is being saved. Maybe the state goes back to default values once the request is being sent.

Hey i'm also facing this issue, also after refreshing its is not getting checked.
I'm using chrome


zigbee2mqtt: 1.37.1 -> zigbee2mqtt-1.37.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for zigbee2mqtt is: Zigbee to MQTT bridge using zigbee-shepherd
meta.homepage for zigbee2mqtt is: https://github.com/Koenkk/zigbee2mqtt
meta.changelog for zigbee2mqtt is: https://github.com/Koenkk/zigbee2mqtt/releases/tag/zigbee2mqtt-1.37.1
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found zigbee2mqtt-1.37.1 with grep in /nix/store/aiq970k9s87ck9sw5fwjnqgwii6l99hi-zigbee2mqtt-zigbee2mqtt-1.37.1
found zigbee2mqtt-1.37.1 in filename of file in /nix/store/aiq970k9s87ck9sw5fwjnqgwii6l99hi-zigbee2mqtt-zigbee2mqtt-1.37.1

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

zigbee2mqtt

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/cd1d1310660ecea341bba2f9b929cc311bb586fc#zigbee2mqtt

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

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

1 package built:

zigbee2mqtt

Maintainer pings
cc @sweber83 @mweinelt for testing.

Closed by #316747.


Says Private Link only available on Dedicated, other page says standard and dedicated.

[Enter feedback here]
This page says private link is only available on EH dedicated, linked page says is available on standard and dedicated.
jolammer

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9aa6a799-cfb1-4cf3-c25d-2bf19a8f6560
Version Independent ID: bd9db425-45ee-7edb-c2b7-bc7b69268835
Content: Network security for Azure Event Hubs - Azure Event Hubs
Content Source: articles/event-hubs/network-security.md
Service: event-hubs
GitHub Login: @spelluru
Microsoft Alias: spelluru

@jonlammers - Thanks for reporting the issue.
This page needs to be updated to indicate that the feature is supported for both standard and dedicated. We will fix it immediately.
The linked page was updated in this commit:
https://github.com/MicrosoftDocs/azure-docs/commit/b363be4d72ee74b8462d3c9205a59bfca736c794#diff-e5c2c9199935f808e80e305eadd4fce95df640f2be15bbd2ea98d561e4f2159e

#assign: spelluru

I have fixed the issue. The updated article should go live a few minutes after 10 AM PST tomorrow.

Thanks, I'm an employee and EventHubs Dev (jolammer).  Just github didn't
let me say that anywhere.  Updates aren't necessary.
jon
On Tue, Oct 20, 2020 at 8:10 PM Sreedhar Pelluru<EMAIL_ADDRESS>wrote:

I have fixed the issue. The updated article should go live a few minutes
after 10 AM PST tomorrow.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/64702#issuecomment-713210700,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADSBNPUJKE3B4KLBMGYJGODSLYRGRANCNFSM4SY4VBQA
.

#please-close


Add functionality to load files as DataFrames

Goals

Add functionality to load .csv, .xls, and .xlsx files.
Add special functionality for EAB enrollment reports
Add utilities for combining enrollment reports into a time series

[x] Add functionality to load .csv, .xls, and .xlsx files.
[ ] Add special functionality for EAB enrollment reports
[ ] Add utilities for combining enrollment reports into a time series

[x] Add functionality to load .csv, .xls, and .xlsx files.
[x] Add special functionality for EAB enrollment reports
[ ] Add utilities for combining enrollment reports into a time series

[x] Add functionality to load .csv, .xls, and .xlsx files.
[x] Add special functionality for EAB enrollment reports
[x] Add utilities for combining enrollment reports into a time series

just waiting for CI to pass 🎉


Manual notes for context

scenario:
you are reading book which requires context from previous chapters.
You stop reading suddenly.
Next time you are back at the book you need to retrieve context somehow.
Some simple system to add manual context (notes) to certain point or words in the text.

Simple side panel note taking would suffice


GitHub Pages

Hey @Ravin-Oli, can you please enable GitHub pages on the gh-pages branch? I can't access the repo settings. Thanks!

Ok sorry for delay.

Ok it's published.


Store Restriction still applicable?

Does use of these APIs still preclude submitting the app to the Windows Store? It looks like it's been lifted in some circumstances - https://wpdev.uservoice.com/forums/110705-universal-windows-platform/suggestions/9950598-exclude-suspending-in-desktop

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9f08a1cd-54da-9647-5f88-12ff5dcd9bab
Version Independent ID: 1de44f88-2e90-cc63-9707-b415be120237
Content: Run in the background indefinitely - Windows UWP applications
Content Source: windows-apps-src/launch-resume/run-in-the-background-indefinetly.md
Product: uwp
GitHub Login: @eliotcowley
Microsoft Alias: elcowle

Thanks for the comment, and sorry for the delay in addressing it.
The official guidance is that this API is a restricted capability, and can only be used in very few Store apps under specially vetted circumstances.
https://docs.microsoft.com/en-us/windows/uwp/packaging/app-capability-declarations#restricted-capabilities
Thanks for taking the time to leave feedback, and again, sorry for the delay. We do read bugs as they come in, but may not add comments immediately, which gives a poor impression. As this wasn't really a documentation bug, it fell through some cracks. I apologize. -John


can a feature disable?

I wish you we can turn off some feature like source control so space complexity will improve for low end user.
we can manage source control on CLI if we want I think it's a great idea. even though I hide it's still running on background while im coding.

@Babailan, the source control functionality in VS Code is being powered by the vscode.git extension. If you switch to the "Extensions" viewlet, and you search for "@builtin" you will get a list of the built-in extensions. You can manually disable the "Git Base" and "Git" extensions to essentially turn off the source control functionality in VS Code.


The WebSheet dataset

It seems that the websheet dataset used in the Cell Type Classification cannot be accessed.  Could you also share the dataset?

Thanks for you attention.
Please find SAUS, DeEx, and CIUS at
https://github.com/majidghgol/TabularCellTypeClassification.
We will upload TUTA's code at
https://github.com/microsoft/TUTA_table_understanding/ soon.
We will upload WebSheet at https://github.com/microsoft/TableSense after we
have prepared well (the internal dataset publication process is quite
strict and complex). Please stay tuned.
Best,
Haoyu
buptxiaofeng @.***> 于2021年9月3日周五 下午7:29写道：

It seems that the websheet dataset used in the Cell Type Classification
cannot be accessed. Could you also share the dataset?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/TUTA_table_understanding/issues/1, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACO6YQAUPK5D3K664ZJBK3DUACWSVANCNFSM5DLRZMIQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Hi @HaoAreYuDong, I don't see the WebSheet dataset in the TableSense repo, is that expected ?


[FULL@RACe!]]HDBritish GP 2023 LIVE STREAM@FREE ON TV 9 July 2023

Check out how to watch British Grand Prix v British GP in the F1, 2023,including TV channel, radio coverage and kick-off time.and British Grand Prix v British GP battle at Hampden Park on Sunday as the hosts look to end their Old Firm rivals' chances of a historic eighth domestic treble.
🔴Watch🔴📺🥊👉 British Grand Prix Live

Both Glasgow clubs have achieved the feat seven times – widely recognised as the most among any clubs in the men's professional game – and the Bhoys have another in their sights in 5055/55. Ange Postecoglou's side beat in the final of the  F1 2023 in June and can clinch the SPFL title early next month due to their 55-point lead at the top, which means the F1 2023 is the only bit of domestic silverware not yet in their grasp. With Falkirk and Livingstone facing off in this weekend's other final, whoever triumphs in the latest Old F1, 2023 will head into June's final as significant favourites. That fact and the looming prospect of a record eighth domestic treble for should mean the stakes are even higher than usual in Sunday's F1, 2023 . RadioTimes has rounded up everything you need to know about how to watch v on TV and online. When is British Grand Prix v British GP ?British Grand Prix v British GP will take place on Saturday 09th July 2023. Check out our live Game on TV guide for the latest times and information.British Grand Prix v British GP kick-off time British Grand Prix v British GP will kick off at 5:50pm. There are plenty of matches on the F1, 2023  TV schedule this week. What TV channel is British Grand Prix v British GP on? You can watch the game live on Viaplay Sports 5, formerly Premier Sports, from 55:50pm. Viaplay Sports can be added to new and existed Virgin Media and Sky TV packages with a monthly or annual subscription.

British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023
British Grand Prix 2023 Live Coverage ON 9 July 2023


kernel: fix smp build on esp32

set_kernel_idle_time_in_ticks is not used in non SMP code.

Codecov Report

Merging #13042 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #13042   +/-   ##
=======================================
  Coverage   48.71%   48.71%
=======================================
  Files         316      316
  Lines       47178    47178
  Branches    10906    10906
=======================================
  Hits        22982    22982
  Misses      19637    19637
  Partials     4559     4559

Impacted Files
Coverage Δ

kernel/idle.c
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Allow inline lists

Hi! I saw https://github.com/awslabs/smithy/blob/idl-2.0-rc-1/designs/inline-io.md and wondered if something similar could happen for lists:
instead of
structure User {
  names: Names
}

list Names { member: Name }

it would be possible to do
structure User {
  names: [Name]
}

(or similar) and a shape like Names could be implicitly assumed to exist without the spec author having to write it.
This is not only a syntactic convenience, it would also aid refactoring (fewer symbols to rename).
Thanks :)

For inline operation input/output, we saw that teams were almost always creating dedicated input and output shapes in their models, naming them consistently (e.g., PutFooInput, PutFooOutput), and rarely ever applying traits to them. Despite synthesizing these shapes, the end result is that the name is still deterministic so you could do stuff like add traits to the synthesized I/O shapes.
We thought inline lists as less of a slam dunk (and sets and maps), but I'm curious about your thoughts on this.
Teams often need to apply traits to lists (like @length, @documentation, @sparse) and traits to the member of the list (docs, other constraints). If we accounted for this in syntax, then sure it could work, but it won't look as nice and succinct. Like:
// This could support adding a trait to the member, but oof!
// We'd probably just not support member traits with an inline syntax.
structure User {
    names := @sparse Name[@length(min: 1)]
}

We think this would reduce the amount of shape sharing across a model. Let's say you have a list that needs a to be limited to contain no more than 10 elements, and that list is used throughout the model any time you refer to, say, "widgets". With inline syntax, most people would inline the list in multiple places and repeat the constraint trait rather than share the common definition. The problem there is that if you ever need to change from 10 to something else, you have to update multiple places in the model.
So this is great:
structure User {
    names: UserNames
}

structure UserNameSummary {
    names: UserNames
}

@length(max: 10)
list UserNames {
    member: Name
}

Whereas this isn't great because it creates multiple places that need to be updated if constraints on UserNames ever changes:
structure User {
    @length(max: 10)
    names := [UserNames]
}

structure UserNameSummary {
    @length(max: 10)
    names := [UserNames]
}

As for naming, all shapes in Smithy have to have a name, so we'd have to synthesize one (inline I/O is just syntactic sugar that is exactly equivalent to writing it out long-form). It would have to be based on the container shape name + the member name to avoid conflicts with other similarly named structure members with divergent target shapes, documentation, etc (e.g., Usernames? or UserNames).
So for example:
structure User {
    names: [Name]
}

Changing to:
structure User {
    names: UserNames
}

list UserNames {
    member: Name
}

Would be considered identical models. Breaking the shape out would be something a team could do if they ever needed to add traits to the previously synthetic shape.

I have to admit I didn't consider naming conflicts when used in multiple shapes. Prefixing sounds good though, we don't see these shapes in our generated code anyway (list shapes are omitted in smithy4s-generated interfaces).
I think it's fair to assume these lists would mostly be used when there's just one of these lists: things like
structure User {
    @length(max: 10)
    names := [Name]
}

structure UserNameSummary {
    @length(max: 10)
    names := [Name]
}

wouldn't be the norm - at that point it'd definitely be worth extracting into a proper list shape. The main usecase is really the simple lists with zero or few traits.
Maybe it's not so much of an improvement but it'd help a lot for people using Smithy syntax for domain modelling :)

If the synthetic list didn't support traits on the synthetic list or the member of the list, then we could use the target shape as the synthetic list's name (e.g., NameList or similar), cutting down on the number of duplicated synthetic lists. We could also automatically mark the synthetic list as @private to prevent any other consumer of your model from another namespace from referring to the synthetic list, and it makes it usable for defining traits (a typical practice for traits is to mark all shapes used by a trait @private).
To mitigate stuff like repeating the same constraint traits over and over on synthetic lists, we could probably add some kind of validation that looks at members that target lists and repeat the same trait.

Seems like quite a lot of work. Maybe it's better to just bite the bullet and type the extra characters 😅
In the future it could be made easier with an editor code action (e.g. "create missing type" which would default to a list type based on some naming heuristics)

Yeah :). The Smithy core team is pretty divided on whether this would be a net positive too. Inline lists look great in docs and examples, but in practice we'd probably discourage their use at AWS since we want to add constraints to basically every list/set/map/string to make them bounded in some way, and we really don't want teams to fall into the trap of repeating themselves.
If we do add something for inline list definitions, it would be in 2.1 or later since we're working on wrapping up Smithy IDL 2.0.

Since we don't currently have plans for inline lists, I'll close this issue.


bridge plugin: Document the macspoofchk field argument

Ref: https://github.com/containernetworking/plugins/pull/639

@dcbw , could you please look into this?


Correction for raw affiliation Department of Intensive Care Medicine, Narbonne Hospital, Narbonne F-11100, France

Correction needed for raw affiliation Department of Intensive Care Medicine, Narbonne Hospital, Narbonne F-11100, France
raw_affiliation_name: Department of Intensive Care Medicine, Narbonne Hospital, Narbonne F-11100, France
new_rors:
previous_rors: 022m8c549
works_examples: W2755736162
contact: 6b48fb6b7b8146514ccb92d262e0f8b6:e0c3ad727e5fe3bc77a9f8013bd220725a94 @ inrae.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-09. The new affiliations should be visible within the next 7 days.


Rename runtime docker_version

Renaming runtime docker_version to prevent setting that
value on the command line from breaking the play run.
This fixes #2081

ci check this

Looks like the build failed for:
"User does not have permissions to start CI run"
I'm assuming that's something someone else needs to handle.

Looks like the gitlab-ci/pipeline was re-run and passed?

@podnov thanks for the excellent fix!


fix travis

manual install of wheel to avoid "error: invalid command 'bdist_wheel'"

Anything needed here?
would be really nice to have it merge so it can re-validate other PRs.

Anything needed here?
would be really nice to have it merge so it can re-validate other PRs.

any feedback?
there are non-travis config related fixes that I would prefer committed before working on the github action equivalent.

@juju4 thanks a lot for working on this.
This PR should be merged as it is very important to have CI tests to this role.

PR Stale and not ready for bbb 2.3
Closing for now.
Also I was told some issues with the new plans around travis and @davidmehren wanted to take a look at this to do this via github actions.


[FEATURE REQUEST] Show blacklist button to edit blacklist

Before submitting the issue

[x] I have checked that the requested feature is not a duplicate or, if it is, it needs to be reopened
[x] I have checked that I am running the latest version of WingetUI
[x] I have checked the FAQ section

Is your feature request related to a problem? Please describe.
It's currently not possible to edit the blacklist.
You can't remove one program from the blacklist, you have to reset it completely.
Describe the solution you'd like
An extra button to show the blacklist where you can remove programs from it would be nice.

Duplicate of #284


Add eula_acceptance to key as it is required by Tower

Currently, the trial licenses do not have the eula_accepted: true key and as of Tower 2.1, is it required

hope you tested this :)

Hello, it's not working for me. Looks like this new part:
- name: Ensure eula is accepted if posting license
  lineinfile:
    path: "{{playbook_dir}}/tower_license.json"
    line: '    "eula_accepted": true,'
    insertbefore: '"company_name"'
    state: present
  when:
    - ansible_os_family == 'RedHat'
    - autolicense

Is checking the file on the remote system, and we never upload it, as it's posted via API. In my case, the error (with a tower_license.json that doesn't include the Eula_accepted line) (log attached)
error.log

I have a fix I’ll push tomorrow! Sorry about this!
On Thu, Sep 27, 2018 at 4:31 PM Ignacio Verona<EMAIL_ADDRESS>wrote:

Hello, it's not working for me. Looks like this new part:

name: Ensure eula is accepted if posting license
lineinfile:
path: "{{playbook_dir}}/tower_license.json"
line: '    "eula_accepted": true,'
insertbefore: '"company_name"'
state: present
when:

ansible_os_family == 'RedHat'
autolicense

Is checking the file on the remote system, and we never upload it, as it's
posted via API. In my case, the error (with a tower_license.json that
doesn't include the Eula_accepted line) (log attached)
error.log
https://github.com/network-automation/linklight/files/2425819/error.log
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/network-automation/linklight/pull/94#issuecomment-425232468,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGPB0JH2mWT9JqXOBsNeSqmeGSE600hrks5ufTWmgaJpZM4WEIqZ
.


WebsiteDeployHelper Lambda uses unsupported python runtime version

Describe the bug
In the nested stack "EFSFileWebApplication" the WebsiteDeployHelper can not be created because it tries to use a no longer supported runtime version for lambda.
Full error:

2022-08-18 12:15:36 UTC+0200
WebsiteDeployHelper
CREATE_FAILED
Resource handler returned message: "The runtime parameter of python3.6 is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (python3.9) while creating or updating functions. (Service: Lambda, Status Code: 400, Request ID: dadadadada)" (RequestToken: dadadadadadada, HandlerErrorCode: InvalidRequest)

To Reproduce
Deploy the stack with CloudFormation
Expected behavior
It runs through without errors

Version: (SO0145) Simple File Manager for Amazon EFS Solution Main v1.4.0

Mappings:
  SourceCode:
    General:
      S3Bucket: "solutions"
      KeyPrefix: "simple-file-manager-for-amazon-efs/v1.0.4"

[ ] Region: [e.g. eu-central-1]
[ ] Was the solution modified from the version published on this repository? NO
[ ] If the answer to the previous question was yes, are the changes available on GitHub?
[ ] Have you checked your service quotas for the sevices this solution uses? NO
[ ] Were there any errors in the CloudWatch Logs?

This was fixed.
Version 1.4.1
Released: 08/2022


out of memory error

Hi, @qian-qi
I run your codes with default settings on a single Tesla-v100 card, but an error occurred
"RuntimeError: CUDA out of memory. Tried to allocate 10.52 GiB (GPU 0; 31.72 GiB total capacity; 22.42 GiB already allocated; 8.18 GiB free; 15.33 MiB cached)"
Why the softtriple loss costs such many memory? Or can you share your experimental settings in details? Thank you.

Hi,
It costs less than 3GB memories with default settings in my environment, which is a single P100.

Hi,
I just change the "self.weight = torch.zeros(cLass_numK, cLass_numK, dtype=torch.bool).cuda()" to "self.weight = torch.zeros(cLass_numK, cLass_numK, dtype=torch.long).cuda()", as torch.bool is not supported in torch 1.0.1, it that matters?

Pls try torch.uint8 instead.

Hi,
It works, thx!


CustomizableCalendarDay meant to be exported?

I'm working on updating the typescript definition file for react-dates, which were last updated for 16.0.0. Since then it looks like CustomizableCalendarDay was added (#894), but I don't see it exported in the generated lib/index.js file. Is this intentional?

Yes, it’s intentional. Both because it’s not intended for casual use, and because deep imports are the better way to import things :-)


Add run id to response header in action server

That should be useful to query info on the run after the run.

Fixed in https://github.com/robocorp/robocorp/commit/5a468fc1d7a543a146982214c750871ad1ac437c


Feature: Support "keyless" verification non-Fulcio certificate authorities

Description
Currently we have some support for signing with x509 certificates using haven't come from a Fulcio CA and and don't chain up to a TUF root. For example
cosign sign --certificate cert.pem --key key.pem --certificate-chain bundle.pem example.com/foo@sha256:.....

Aside: the key format needs to be cosign's format to make this work so you often need to run e.g cosign import-key-pair to make that the case

The current invocation to verify this kind of signature is a little inconvenient as you need to specify the leaf certificate like so:
cosign verify --certificate cert.pem --certificate-chain bundle.pem example.com/foo@sha256:....

This means grabbing that leaf certificate off the OCI manifest or from the Rekor bundle or something.  Would be great to be able to do the same kind of invocation as Fulcio's verification like
cosign verify --certificate-chain bundle.pem --certificate-identity<EMAIL_ADDRESS>--certificate-oidc-issuer https://id.example.com example.com/foo@sha256:.....

This convenient keyless verification would be awesome for folks using a custom CA, provided they're using certificates in a similar shape that Fulcio does (Efforts to standardize these extensions like https://github.com/sigstore/fulcio/pull/945 would make it easy for folks to create a CA that does this)

cc @znewman01 since we were chatting about this recently
We definitely need a cohesive story around BYO PKI UX, since issues like this have popped up a few times. This seems like a reasonable approach, though I personally would prefer we encourage TUF usage over passing roots by flag.

Yeah I agree that passing roots by file is less secure and we should encourage folks to set up a TUF root for distribution if possible, but I think its would be nice to keep the option there even if its got the usual discouraging name like --insecure-certificate-chain with a little pointer to how folks can do better with TUF.   Also, I think its reasonable that folks might have some other secure mechanism to deliver a CA bundle without requiring cosign to do that bit.

One thing that Zack proposed that I liked was namespacing verification with self hosted PKI. This would let us be opinionated about TUF for some verification, but allow for other verification for the BYO case. This lets us avoid calling parts of verification insecure since there’s an assumption that you know what you’re doing with self hosted.
This would be a ways out obviously so adding this flag seems reasonable.

A different set of CLI commands with their own flags. The verification API should be designed to support any use case (it shouldn’t be TUF aware for example, the CLI layer should just parse the input and pass it to the verifiers).
Main concern with this approach is creating even more verify functions, we already have a lot!

Yeah agreed that the verify functions are kind of a lot, but I will say that the user experience might be better if BYO PKI has its own subcommand. I've been playing around with this BYO PKI using a step-ca configured to look kinda like Fulcio that respects OIDC tokens from my Gitea instance and I found it really tricky to understand which flags on the existing verify function worked together as there are so many ones you'd think might combine or might not you know?

Flag bloat is definitely an issue. Tangential, I’m curious what the verify command looked like and how we can simplify.

So the flow right now looks like this
# Build example image with ko
KO_DOCKER_REPO=code.nfsmith.ca/nsmith/seccon ko build --bare > image

# Get a code signing cert from my step-ca
step ca certificate<EMAIL_ADDRESS>cert.pem key.pem

# Import the private key to the cosign format. (Lets get rid of this odd step in the BYO PKI experience? I'm going to delete the key right after this anyways..)
COSIGN_PASSWORD=derp cosign import-key-pair --key key.pem

# Signing
COSIGN_PASSWORD=derp cosign sign --key import-cosign.key --certificate cert.pem \
    --certificate-chain bundle.pem $(cat image)

# Delete private key
rm import-cosign.key key.pem

# Verification
cosign verify --certificate cert.pem --certificate-chain bundle.pem --certificate-identity<EMAIL_ADDRESS>--certificate-oidc-issuer https://code.nfsmith.ca/ --insecure-ignore-sct $(cat image)

The last bit works because of the structure of my step-ca configuration. Its adding the right Fulcio extension so that --certificate-oidc-issuer flag works correctly.
I think ideally I'd like to smooth out the experience to by

Removing the need to change the private key format
Removing the need to specify the certificate when verifying
Make the verification logic more extensible if its a custom CA?

On that last note, it was easy to make step-ca kind of Fulcio-like to fit the need here, but it would be nice if cosign verify-with-pki (or whatever) could read something like a Rego policy and I could write down the checks I wanted there so that a user could check any number of custom extensions etc

Removing the need to specify the certificate when verifying

To confirm, does your OCI image have the certificate and chain in its annotations? If you pass them on sign, they should get attached to the image so you don't need to provide --certificate (you still need --certificate-chain, though technically you only need the root since the intermediates get pulled from the image annotations if not specified by flag).

Yup! Sign totally works as expected and I can see the cert and chain
correctly added to the  OCI signature when I run e.g crane manifest derp:sha256-blah.sig
On Sun, Jan 15, 2023, 8:25 PM Hayden B @.***> wrote:

Removing the need to specify the certificate when verifying
To confirm, does your OCI image have the certificate and chain in its
annotations? If you pass them on sign, they should get attached to the
image so you don't need to provide --certificate (you still need
--certificate-chain, though technically you only need the root since the
intermediates get pulled from the image annotations if not specified by
flag).
—
Reply to this email directly, view it on GitHub
https://github.com/sigstore/cosign/issues/2630#issuecomment-1383472885,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC4X2GMYGK2YK2VYIJ6M2MLWSTESPANCNFSM6AAAAAAT4E4GLI
.
You are receiving this because you authored the thread.Message ID:
@.***>

Should is the key word I guess. It doesn't work in practice because if you
don't specify a cert then the current cosign implementation loads the
Fulcio root, ignores the cert chain you specify and then fails verification
because it didn't load the CA chain correctly
On Sun, Jan 15, 2023, 8:25 PM Hayden B @.***> wrote:

Removing the need to specify the certificate when verifying
To confirm, does your OCI image have the certificate and chain in its
annotations? If you pass them on sign, they should get attached to the
image so you don't need to provide --certificate (you still need
--certificate-chain, though technically you only need the root since the
intermediates get pulled from the image annotations if not specified by
flag).
—
Reply to this email directly, view it on GitHub
https://github.com/sigstore/cosign/issues/2630#issuecomment-1383472885,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC4X2GMYGK2YK2VYIJ6M2MLWSTESPANCNFSM6AAAAAAT4E4GLI
.
You are receiving this because you authored the thread.Message ID:
@.***>


OS opening more connections than specified in pools config?

Hello,
I'm testing this library using the following configuration:
# MyApp.Application

{Finch, name: MyApp.Finch, pools: %{
    :default => [size: 3, count: 1],
    "https://host.sample-videos.com" => [size: 3, count: 1],
}}

And then doing a bunch of requests with:
Enum.map(1..20, fn n ->
  Task.start(fn ->
    Finch.build(:get, "https://www.sample-videos.com/video123/mp4/720/big_buck_bunny_720p_30mb.mp4")
    |> Finch.request(MyApp.Finch)
  end)
end)

However the connections in iftop show 20 connections open:
 * :39881                    <=> host.sample-videos.com-:https  416b    479Kb   219Kb
 * :58309                    <=> host.sample-videos.com-:https  344Kb   479Kb   197Kb
 * :39449                    <=> host.sample-videos.com-:https  624b    477Kb   219Kb
 * :56327                    <=> host.sample-videos.com-:https  302Kb   470Kb   156Kb
 * :33007                    <=> host.sample-videos.com-:https  515Kb   440Kb   212Kb
 * :39955                    <=> host.sample-videos.com-:https  316Kb   439Kb   198Kb
 * :45601                    <=> host.sample-videos.com-:https  353Kb   437Kb   146Kb
 * :59039                    <=> host.sample-videos.com-:https  216Kb   399Kb   129Kb
 * :42899                    <=> host.sample-videos.com-:https  341Kb   372Kb   114Kb
 * :36477                    <=> host.sample-videos.com-:https  522Kb   368Kb   118Kb
 * :36269                    <=> host.sample-videos.com-:https  318Kb   341Kb   178Kb
 * :39667                    <=> host.sample-videos.com-:https  114Kb   341Kb   155Kb
 * :40727                    <=> host.sample-videos.com-:https  275Kb   314Kb   128Kb
 * :37057                    <=> host.sample-videos.com-:https  302Kb   305Kb   109Kb
 * :36993                    <=> host.sample-videos.com-:https  158Kb   215Kb  75,3Kb
 * :51285                    <=> host.sample-videos.com-:https  170Kb   213Kb  82,6Kb
 * :40895                    <=> host.sample-videos.com-:https  193Kb   192Kb  65,2Kb
 * :38113                    <=> host.sample-videos.com-:https  159Kb   189Kb  91,1Kb
 * :51565                    <=> host.sample-videos.com-:https    0b    162Kb   219Kb
 * :44515                    <=> host.sample-videos.com-:https    0b   1,26Kb   219Kb
 * :49556                    <=> lb-140-82-112-3-iad.git:https    0b    187b     47b
 ...
 ... etc

What am I missing? Shouldn't it open 3 connections at a time only?

Yes, the number of open connections should be based on the pool size. Finch will use the default settings to open that many connections for each unique host. So, in your example, https://www.sample-videos.com would have its own connections separate from https://host.sample-videos.com. But, based on your config it should only be opening 3 connections per host. I feel like we saw an issue with this early on and fixed it in nimble pool. But I can't recall the details off the top of my head. I'll need to go look through PRs to remember.

@imricardoramos just in case please paste your finch and nimble_pool versions from your mix.lock.


Mark collected/downloaded gallerys

When a gallery was collected/downloaded, then show heart/download Icon in thumbnail to remind users.

An "This is already downloaded. Do you want to download again?" prompt with a marker on the thumbnail wouldn't be bad

An "This is already downloaded. Do you want to download again?" prompt with a marker on the thumbnail wouldn't be bad


[NOC] Fix for accented chars in sheet.json & minor CSS/HTML updates

Changes / Comments
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[ ] Does the pull request title have the sheet name(s)? Include each sheet name.
[ ] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.


submitting project to BH school website

Hi I'm submitting my project folder /rs-fMRI-music-rct-autism to the school/en/content/project folder.

sorry for the delay reviewing this PR.
LGTM! could you please just update the date as suggested?

LGTM, merging!


Deploy & Build error when install Ignite

Hi Paul, I'm deploying my website on Netlify, but it gave me below compiling error when installing dependency Ignite. Is this Swift version specific issue? My build is OK in my local machine with Swift 5.10
➜  IgniteStarter git:(MyDevSpace) swift --version
swift-driver version: <IP_ADDRESS> Apple Swift version 5.10 (swiftlang-<IP_ADDRESS> clang-15<IP_ADDRESS>)
Target: arm64-apple-macosx14.0

1:58:45 PM: build-image version: ecdc8b770f4a0193fd3f258c1bc6029e681813a4 (focal)
1:58:45 PM: buildbot version: 22552e71c3c7b6a5ebfd780eb1c9b2f42fe63aa7
1:58:46 PM: Building without cache
1:58:46 PM: Starting to prepare the repo for build
1:58:46 PM: No cached dependencies found. Cloning fresh repo
1:58:46 PM: git clone --filter=blob:none https://github.com/Haibo-Zhou/my-new-website
1:58:46 PM: Preparing Git Reference refs/heads/MyDevSpace
1:58:48 PM: Starting to install dependencies
1:58:49 PM: Python version set to 3.8
1:58:49 PM: Attempting Ruby version 2.7.2, read from environment
1:58:49 PM: Using Ruby version 2.7.2
1:58:50 PM: Started restoring cached go cache
1:58:50 PM: Finished restoring cached go cache
1:58:51 PM: go version go1.19.13 linux/amd64
1:58:52 PM: Downloading https://download.swift.org/swift-5.10.1-release/ubuntu2004/swift-5.10.1-RELEASE/swift-5.10.1-RELEASE-ubuntu20.04.tar.gz
1:58:52 PM: /tmp/swiftenv-5.10.1- /opt/build/repo
1:58:52 PM:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
1:58:52 PM:                                  Dload  Upload   Total   Spent    Left  Speed
1:58:52 PM:   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
1:58:53 PM:  10  576M   10 61.0M    0     0   163M      0  0:00:03 --:--:--  0:00:03  162M
1:58:54 PM:  59  576M   59  344M    0     0   250M      0  0:00:02  0:00:01  0:00:01  250M
1:58:54 PM: 100  576M  100  576M    0     0   265M      0  0:00:02  0:00:02 --:--:--  265M
1:59:06 PM: /opt/build/repo
1:59:06 PM: 5.10.1 has been installed.
1:59:06 PM: Using Swift version 5.10.1
1:59:06 PM: Building Swift package
1:59:06 PM: Started restoring cached swift build
1:59:06 PM: Finished restoring cached swift build
1:59:07 PM: Fetching https://github.com/twostraws/Ignite.git
1:59:07 PM: [1/1466] Fetching ignite
1:59:07 PM: Fetched https://github.com/twostraws/Ignite.git from cache (0.24s)
1:59:07 PM: Fetching https://github.com/apple/swift-markdown.git
1:59:07 PM: [1/6045] Fetching swift-markdown
1:59:07 PM: Fetched https://github.com/apple/swift-markdown.git from cache (0.41s)
1:59:08 PM: Fetching https://github.com/swiftlang/swift-cmark.git
1:59:09 PM: [1/17821] Fetching swift-cmark
1:59:09 PM: Fetched https://github.com/swiftlang/swift-cmark.git from cache (0.71s)
1:59:09 PM: Fetching https://github.com/apple/swift-argument-parser.git
1:59:09 PM: [1/12089] Fetching swift-argument-parser
1:59:10 PM: Fetched https://github.com/apple/swift-argument-parser.git from cache (0.73s)
1:59:10 PM: Computing version for https://github.com/apple/swift-argument-parser.git
1:59:10 PM: Computed https://github.com/apple/swift-argument-parser.git at 1.5.0 (0.21s)
1:59:10 PM: Creating working copy for https://github.com/swiftlang/swift-cmark.git
1:59:10 PM: Working copy of https://github.com/swiftlang/swift-cmark.git resolved at gfm (fc07ab5)
1:59:10 PM: Creating working copy for https://github.com/apple/swift-markdown.git
1:59:10 PM: Working copy of https://github.com/apple/swift-markdown.git resolved at main (d217140)
1:59:10 PM: Creating working copy for https://github.com/apple/swift-argument-parser.git
1:59:10 PM: Working copy of https://github.com/apple/swift-argument-parser.git resolved at 1.5.0
1:59:10 PM: Creating working copy for https://github.com/twostraws/Ignite.git
1:59:10 PM: Working copy of https://github.com/twostraws/Ignite.git resolved at main (d101d2b)
1:59:12 PM: [1/1] Compiling plugin GenerateManual
1:59:12 PM: Building for debugging...
1:59:12 PM: [1/46] Compiling cmark-gfm syntax_extension.c
1:59:12 PM: [2/46] Compiling cmark-gfm arena.c
1:59:12 PM: [3/46] Compiling cmark-gfm houdini_html_u.c
1:59:12 PM: [4/46] Compiling cmark-gfm blocks.c
1:59:12 PM: [5/46] Compiling cmark-gfm-extensions tasklist.c
1:59:12 PM: [6/46] Compiling cmark-gfm-extensions tagfilter.c
1:59:12 PM: [7/46] Compiling cmark-gfm-extensions strikethrough.c
1:59:12 PM: [8/46] Compiling cmark-gfm-extensions ext_scanners.c
1:59:12 PM: [9/46] Write swift-version-19E6B5D239350F1E.txt
1:59:12 PM: [10/46] Compiling cmark-gfm-extensions core-extensions.c
1:59:12 PM: [11/46] Compiling cmark-gfm-extensions table.c
1:59:12 PM: [12/46] Compiling cmark-gfm-extensions autolink.c
1:59:12 PM: [13/46] Compiling cmark-gfm xml.c
1:59:12 PM: [14/46] Compiling cmark-gfm render.c
1:59:12 PM: [15/46] Compiling cmark-gfm registry.c
1:59:12 PM: [16/46] Compiling cmark-gfm plugin.c
1:59:12 PM: [17/46] Compiling cmark-gfm references.c
1:59:12 PM: [18/46] Compiling cmark-gfm plaintext.c
1:59:12 PM: [19/46] Compiling cmark-gfm utf8.c
1:59:12 PM: [20/46] Compiling cmark-gfm map.c
1:59:12 PM: [21/46] Compiling cmark-gfm man.c
1:59:12 PM: [22/46] Compiling cmark-gfm node.c
1:59:12 PM: [23/46] Compiling cmark-gfm linked_list.c
1:59:12 PM: [24/46] Compiling cmark-gfm iterator.c
1:59:12 PM: [25/46] Compiling cmark-gfm latex.c
1:59:12 PM: [26/46] Compiling cmark-gfm scanners.c
1:59:12 PM: [27/46] Compiling cmark-gfm houdini_html_e.c
1:59:12 PM: [28/46] Compiling cmark-gfm html.c
1:59:12 PM: [29/46] Compiling cmark-gfm houdini_href_e.c
1:59:12 PM: [30/46] Compiling cmark-gfm footnotes.c
1:59:12 PM: [31/46] Compiling cmark-gfm cmark_ctype.c
1:59:12 PM: [32/46] Compiling cmark-gfm inlines.c
1:59:12 PM: [33/46] Write sources
1:59:12 PM: [34/46] Copying Resources
1:59:12 PM: [35/46] Write sources
1:59:12 PM: [37/46] Compiling cmark-gfm commonmark.c
1:59:12 PM: [38/46] Compiling cmark-gfm cmark.c
1:59:12 PM: [39/46] Compiling CAtomic CAtomic.c
1:59:12 PM: [40/46] Compiling cmark-gfm buffer.c
1:59:13 PM: [42/98] Emitting module Markdown
1:59:15 PM: [43/115] Compiling Markdown RangerTracker.swift
1:59:15 PM: [44/115] Compiling Markdown MarkupRewriter.swift
1:59:15 PM: [45/115] Compiling Markdown BasicBlockContainer.swift
1:59:15 PM: [46/115] Compiling Markdown BasicInlineContainer.swift
1:59:15 PM: [47/115] Compiling Markdown BlockContainer.swift
1:59:15 PM: [48/115] Compiling Markdown BlockMarkup.swift
1:59:15 PM: [49/115] Compiling Markdown InlineContainer.swift
1:59:15 PM: [50/115] Compiling Markdown InlineMarkup.swift
1:59:15 PM: [51/115] Compiling Markdown ListItemContainer.swift
1:59:15 PM: [52/115] Compiling Markdown AtomicCounter.swift
1:59:15 PM: [53/115] Compiling Markdown CharacterExtensions.swift
1:59:15 PM: [54/115] Compiling Markdown CollectionExtensions.swift
1:59:15 PM: [55/115] Compiling Markdown StringExtensions.swift
1:59:15 PM: [56/115] Compiling Markdown MarkupVisitor.swift
1:59:15 PM: [57/115] Compiling Markdown MarkupWalker.swift
1:59:15 PM: [58/115] Compiling Markdown MarkupFormatter.swift
1:59:15 PM: [59/115] Compiling Markdown MarkupTreeDumper.swift
1:59:15 PM: [60/115] Compiling Markdown OrderedList.swift
1:59:15 PM: [61/115] Compiling Markdown UnorderedList.swift
1:59:15 PM: [62/115] Compiling Markdown Paragraph.swift
1:59:15 PM: [63/115] Compiling Markdown CodeBlock.swift
1:59:15 PM: [64/115] Compiling Markdown HTMLBlock.swift
1:59:15 PM: [65/115] Compiling Markdown Heading.swift
1:59:15 PM: [66/115] Compiling Markdown ThematicBreak.swift
1:59:15 PM: [67/115] Compiling Markdown Table.swift
1:59:15 PM: [68/115] Compiling Markdown TableBody.swift
1:59:15 PM: [69/115] Compiling Markdown TableCell.swift
1:59:15 PM: [70/115] Compiling Markdown TableCellContainer.swift
1:59:15 PM: [71/115] Compiling Markdown TableHead.swift
1:59:15 PM: [72/115] Compiling Markdown TableRow.swift
1:59:15 PM: [73/115] Compiling Markdown Replacement.swift
1:59:15 PM: [74/115] Compiling Markdown SourceLocation.swift
1:59:15 PM: [75/115] Compiling Markdown Emphasis.swift
1:59:15 PM: [76/115] Compiling Markdown Image.swift
1:59:15 PM: [77/115] Compiling Markdown InlineAttributes.swift
1:59:15 PM: [78/115] Compiling Markdown Link.swift
1:59:15 PM: [79/115] Compiling Markdown Strikethrough.swift
1:59:15 PM: [80/115] Compiling Markdown Strong.swift
1:59:15 PM: [81/115] Compiling Markdown CustomInline.swift
1:59:15 PM: [82/115] Compiling Markdown InlineCode.swift
1:59:15 PM: [83/115] Compiling Markdown InlineHTML.swift
1:59:15 PM: [84/115] Compiling Markdown LineBreak.swift
1:59:15 PM: [85/115] Compiling Markdown SoftBreak.swift
1:59:15 PM: [86/115] Compiling Markdown SymbolLink.swift
1:59:15 PM: [87/115] Compiling Markdown Text.swift
1:59:15 PM: [88/115] Compiling Markdown Aside.swift
1:59:15 PM: [89/115] Compiling Markdown BlockDirectiveParser.swift
1:59:15 PM: [90/115] Compiling Markdown CommonMarkConverter.swift
1:59:15 PM: [91/115] Compiling Markdown LazySplitLines.swift
1:59:15 PM: [92/115] Compiling Markdown ParseOptions.swift
1:59:15 PM: [93/115] Compiling Markdown RangeAdjuster.swift
1:59:15 PM: [94/115] Compiling Markdown ChildIndexPath.swift
1:59:15 PM: [95/115] Compiling Markdown DirectiveArgument.swift
1:59:15 PM: [96/115] Compiling Markdown Document.swift
1:59:15 PM: [97/115] Compiling Markdown LiteralMarkup.swift
1:59:15 PM: [98/115] Compiling Markdown Markup.swift
1:59:15 PM: [99/115] Compiling Markdown MarkupChildren.swift
1:59:15 PM: [100/115] Compiling Markdown MarkupData.swift
1:59:15 PM: [101/115] Compiling Markdown PlainTextConvertibleMarkup.swift
1:59:15 PM: [102/115] Compiling Markdown RawMarkup.swift
1:59:15 PM: [103/115] Compiling Markdown BlockDirective.swift
1:59:15 PM: [104/115] Compiling Markdown BlockQuote.swift
1:59:15 PM: [105/115] Compiling Markdown CustomBlock.swift
1:59:15 PM: [106/115] Compiling Markdown DoxygenDiscussion.swift
1:59:15 PM: [107/115] Compiling Markdown DoxygenNote.swift
1:59:15 PM: [108/115] Compiling Markdown DoxygenParameter.swift
1:59:15 PM: [109/115] Compiling Markdown DoxygenReturns.swift
1:59:15 PM: [110/115] Compiling Markdown ListItem.swift
1:59:16 PM: [111/116] Wrapping AST for Markdown for debugging
1:59:16 PM: [113/190] Compiling Ignite Dropdown.swift
1:59:16 PM: /opt/build/repo/.build/checkouts/Ignite/Sources/Ignite/Elements/Include.swift:33:49: error: value of type 'URL' has no member 'appending'
1:59:16 PM:         let fileURL = context.includesDirectory.appending(path: filename)
1:59:16 PM:                       ~~~~~~~~~~~~~~~~~~~~~~~~~ ^~~~~~~~~
1:59:16 PM: [114/190] Compiling Ignite Embed.swift
1:59:16 PM: /opt/build/repo/.build/checkouts/Ignite/Sources/Ignite/Elements/Include.swift:33:49: error: value of type 'URL' has no member 'appending'
1:59:16 PM:         let fileURL = context.includesDirectory.appending(path: filename)
1:59:16 PM:                       ~~~~~~~~~~~~~~~~~~~~~~~~~ ^~~~~~~~~
1:59:16 PM: [115/190] Compiling Ignite Emphasis.swift
1:59:16 PM: /opt/build/repo/.build/checkouts/Ignite/Sources/Ignite/Elements/Include.swift:33:49: error: value of type 'URL' has no member 'appending'
1:59:16 PM:         let fileURL = context.includesDirectory.appending(path: filename)
1:59:16 PM:                       ~~~~~~~~~~~~~~~~~~~~~~~~~ ^~~~~~~~~
1:59:16 PM: [116/190] Compiling Ignite Group.swift
1:59:16 PM: /opt/build/repo/.build/checkouts/Ignite/Sources/Ignite/Elements/Include.swift:33:49: error: value of type 'URL' has no member 'appending'
1:59:16 PM:         let fileURL = context.includesDirectory.appending(path: filename)
1:59:16 PM:                       ~~~~~~~~~~~~~~~~~~~~~~~~~ ^~~~~~~~~
1:59:16 PM: [117/190] Compiling Ignite HTML.swift
1:59:16 PM: /opt/build/repo/.build/checkouts/Ignite/Sources/Ignite/Elements/Include.swift:33:49: error: value of type 'URL' has no member 'appending'
1:59:16 PM:         let fileURL = context.includesDirectory.appending(path: filename)
1:59:16 PM:                       ~~~~~~~~~~~~~~~~~~~~~~~~~ ^~~~~~~~~
1:59:16 PM: [118/190] Compiling Ignite Head.swift
1:59:16 PM: /opt/build/repo/.build/checkouts/Ignite/Sources/Ignite/Elements/Include.swift:33:49: error: value of type 'URL' has no member 'appending'
1:59:16 PM:         let fileURL = context.includesDirectory.appending(path: filename)
1:59:16 PM:                       ~~~~~~~~~~~~~~~~~~~~~~~~~ ^~~~~~~~~
1:59:16 PM: [119/190] Compiling Ignite Image.swift
1:59:16 PM: /opt/build/repo/.build/checkouts/Ignite/Sources/Ignite/Elements/Include.swift:33:49: error: value of type 'URL' has no member 'appending'
1:59:16 PM:         let fileURL = context.includesDirectory.appending(path: filename)
1:59:16 PM:                       ~~~~~~~~~~~~~~~~~~~~~~~~~ ^~~~~~~~~

Nice, I have manually deployed my website on Netlify with Netlify CLI. Wait for the Swift 6 shipping though for auto-deploy from github :)

Wait for the Swift 6 shipping though for auto-deploy from github :)

@Haibo-Zhou could you share what you mean by this?

It appears this issue has been resolved. Feel free to open another one if you encounter further problems.


Programming Exercise Domain Commands

Checklist

[x] I run yarn run webpack:build:main: the project builds without errors.
[x] I run yarn lint: the project builds without code style warnings.
[x] I updated the documentation and models.
[x] I tested the changes and all related features on the test server https://artemistest.ase.in.tum.de.
[x] ~I added (end-to-end) test cases for the new functionality.~

Motivation and Context
It would help the tas/instructors to insert tasks and testCases from domain commands from the markdown editor.
Description
The list of test cases is taken from template participation, if there is no template participation due to an error, the test case list is empty.
To make the test case list work, I had to define a new domainCommand type "MultiOptionCommand", this class can be used to construct dropdowns in the editor.
In the markdown-editor html template a class type check is done to differentiate between domainTagCommands and multiOptionCommands.
This PR also fixes the issue with the header dropdown submitting the programming-exercise forms.
Steps for Testing

Log in to ArTEMiS
Navigate to Course Administration
Select course with a programming exercise
Open the exercise via edit, or create/link a new programming exercise -> commands should work as expected

Screenshots

I merged another PR on programming exercises first and now we have conflicts here. Could you please resolve them? Thanks!

Develop was merged and I did some smaller cleanup, but this somehow broke the bamboo build. I'll find out what causes the issue.

Bamboo build works again so we can merge this, right?

@thilo-behnke After merging your other PR, we again have merge conflicts 😔
Could you please fix them again? Also in case everything is done from your side, please change remove the tag work-in-progress and add the tag ready for review

@krusche All is merged and up-to-date now :)


Fix cd can't work cross drives in Windows

Changes
In #189, somebody (and I) got a error like this when building Android.
Cannot operate on packages inside the cache.
Compiling bin/build_tool_runner.dart to kernel file bin/build_tool_runner.dill.
Error: Couldn't resolve the package 'build_tool' in 'package:build_tool/build_tool.dart'.
bin/build_tool_runner.dart:1:8: Error: Not found: 'package:build_tool/build_tool.dart'
import 'package:build_tool/build_tool.dart' as build_tool;
       ^
bin/build_tool_runner.dart:3:15: Error: Method not found: 'runMain'.
   build_tool.runMain(args);
              ^^^^^^^
Could not find a command named "bin\build_tool_runner.dill".

Usage: dart <command|dart-file> [arguments]

Global options:
-v, --verbose               Show additional command output.
    --version               Print the Dart SDK version.
    --enable-analytics      Enable analytics.
    --disable-analytics     Disable analytics.
    --suppress-analytics    Disallow analytics for this `dart *` run without changing the analytics configuration.
-h, --help                  Print this usage information.

Available commands:
  analyze    Analyze Dart code in a directory.
  compile    Compile Dart to various formats.
  create     Create a new Dart project.
  devtools   Open DevTools (optionally connecting to an existing application).
  doc        Generate API documentation for Dart projects.
  fix        Apply automated fixes to Dart source code.
  format     Idiomatically format Dart source code.
  info       Show diagnostic information about the installed tooling.
  pub        Work with packages.
  run        Run a Dart program.
  test       Run tests for a project.

Run "dart help <command>" for more information about a command.
See https://dart.dev/tools/dart-tool for detailed documentation.

FAILURE: Build failed with an exception.

I inspect the reason and find this command not work at all. run_build_tool.cmd#L11
This error was causing by the different drive of pub cache and project dir.
https://stackoverflow.com/questions/11065421/command-Prompt-wont-change-directory-to-another-drive
After I add the /d argument to cd, it works successfully now.
Before Committing
Please make sure that you've analyzed and formatted the files.
dart analyze flutter_ffi_plugin --fatal-infos
dart format .
cargo fmt
cargo clippy --fix --allow-dirty

Thanks for the PR! I will publish a new version very soon.
@knopp It looks like it would be nice to share this fix for Windows, please excusing me for tagging you.

This has been fixed in cargokit for a while now
https://github.com/irondash/cargokit/commit/c6d46d47ce6384f2b0edf92d35c36dd496bdbc5c
Maybe you need to update?


⚠ Auth has degraded performance

In 405f8d0, Auth (https://auth.k2lin.com) experienced degraded performance:

HTTP code: 200
Response time: 20957 ms

Resolved: Auth performance has improved in 379b8e9.


Add support for multiline string literals

Attempt to fix https://github.com/ConsenSys/solidity-parser-antlr/issues/4
See commit message for details on my competence level though :-)

Hey @forshtat! Thank you so much for the submission! 🙏  However the file you're changing, as stated on top is automatically generated by the ANTLR grammar housed here: https://github.com/ConsenSys/solidity-antlr4
If you want to direct a PR there, help will be very welcomed! If not, I'll take a look at this soon. 😄

I'll close this PR here for the time being.

@GNSPS oops, ok, got it. 🤦♂
By the way, judging by the test.sol:712 the grammar does support multiline strings.


Sometimes test.name is a symbol.

This means that Builder won't escape it, which allows invalid symbols to sneak into the JUnit output.

I might be wrong but looking at Builder's code it looks like it handles symbols correctly (https://github.com/jimweirich/builder/blob/master/lib/builder/xmlmarkup.rb#L323)  Am I missing something?  Perhaps it is a bug in some version of Builder?

@craigw I'm closing the PR since there is no response, feel free to reopen it with additional information.


Add TypeScript typings (revisited)

This is a continuation of #541 which seems to have stalled. Fixed the merge conflict and upgraded @types/react.

Ugh, used the wrong branch.


tuf: move INFO logs to DEBUG or WARNING

This should reduce some default logging noise when TUF's ngclient is used as a library in other applications (in particular, sigstore-python).
See: https://github.com/sigstore/sigstore-python/pull/351
cc @jku
Signed-off-by: William Woodruff<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

8 of 8 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.194%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1349

Relevant Lines:
1365

💛  - Coveralls

a) sigstore-python is the one setting a non-default log level (WARNING is default IIRC)

Oh, you're completely right. I'm not sure why we set INFO as our default level; that might be an artifact of me originally intending to use the logger for more regular outputs.

Yeah, agreed -- I need to re-think how sigstore-python does loglevels more generally (it probably makes sense for INFO to be the default for first-party code, DEBUG for third-party, etc.)
I'm going to file an issue for that.


How to prevent row selection when dropdown is clicked inside a table ?

I'm creating a table with selectable rows (using the select listener) that also has an actions dropdown in the last column.
The problem I have is that clicking the dropdown button also selects the row, which should not be the case. It seems to only do that when using the example @select listener from the documentation:
function select (row) {
  const index = selected.value.findIndex((item) => item.id === row.id)
  if (index === -1) {
    selected.value.push(row)
  } else {
    selected.value.splice(index, 1)
  }
}

I only use the select listener to make the select all checkbox work (i.e. the one in the table header). Is this a bug with the default selectable behavior or am I missing something?

An easy fix would be to add a @click.stop on the <UDropdown> component.
It won't work on the <UButton> as it will prevent dropdown menu opening.

This works like a charm, thanks !


Bugfix 443 master v3.0 mtd use cases

Removed 1 use case, updated values in 2 cases to produce better results.

On kiowa, I checked out this bugfix branch, merged it into master_v3.0, and ran 2 use cases:
/d1/projects/METplus/METplus_pull_requests/METplus-3.1-beta2/feature_443/METplus/ush/master_metplus.py /d1/projects/METplus/METplus_pull_requests/METplus-3.1-beta2/feature_443/METplus/parm/use_cases/model_applications/precipitation/MTD_fcstHRRR-TLE_obsMRMS.conf -c ~/mccabe.kiowa.conf
/d1/projects/METplus/METplus_pull_requests/METplus-3.1-beta2/feature_443/METplus/ush/master_metplus.py /d1/projects/METplus/METplus_pull_requests/METplus-3.1-beta2/feature_443/METplus/parm/use_cases/met_tool_wrapper/MTD/MTD.conf -c ~/mccabe.kiowa.conf
The output from these runs are found in:
/d1/projects/METplus/METplus_pull_requests/METplus-3.1-beta2/feature_443/output


Adds alpha support for R5

Description
Adds alpha support for R5
Related issues
Addresses [issue #862].
Testing
All existing tests updated to run against R5.

Also add the new R5 project in
https://github.com/microsoft/fhir-server/blob/master/build/package.yml#L8


.NET Core HelloWorld does not work non-ASCII Path

Original issues: https://github.com/awslabs/aws-sam-cli/issues/2031 and https://github.com/aws/aws-toolkit-vscode/issues/1144
aws_lambda_builders.exceptions.WorkflowUnknownError: DotnetCliPackageBuilder:RunPackageAction - 'utf-8' codec can't decode byte 0x94 in position 308: invalid start byte

Cause:
aws_lambda_builders\workflows\dotnet_clipackage\dotnetcli.py
LOG.info(out.decode("utf8").strip())
out (output from dotnet.exe) is not utf8 encoded


Better bomb revealing on game ended

Ideally when the bombs are revealed, the flags of the player should be kept there even if they were on a bomb, and if the flag was not on a bomb we should have a marker for that, like an "X" over the flag or something. Also the bomb which the player clicked on should be made visible, for example by making its background red.

fixed by this commit


Adds missing variadic bindings for string methods

JsString::from_code_point - allows to create JS strings using slice of codes in WASM memory.
JsString::from_char_code - same as above, but also uses updated signature with u16 instead of u32 (partially helps with #1460 at least for the new binding).

127 | #[wasm_bindgen]
    | ^^^^^^^^^^^^^^^ the trait `wasm_bindgen::convert::traits::IntoWasmAbi` is not implemented for `&[wasm_bindgen::JsValue]`

Ah hmm... I should have checked these.
Is there any particular reason these slices are not allowed? (while Box<[JsValue]> is)

I've added support for [JsValue] slices since it seemed easy to do so (resulting in removing more code than added), but let me know if that's not desired for some reason.

Oh, hmm, currently bindings assume that they can drop every item of the slice. I see, it's not as easy as seemed initially.

Removed the problematic bindings for now, and kept just String::fromCharCode and String::fromCodePoint instead.

👍


refactor: simplify services

Description
At the moment every service is a static service. That PR creates singleton services which we can retrieve using global React context.
It's a part of refactoring which prepares the Studio for multiple files support.
Next will be:

simplify state management - move to the zustand library.
simplify modal management.

@fmvilas I had to fix git conflicts. Could you check again?

/rtm


drogon or rather Trantor Resolver should be able to return multiple IP addresses

Right now, AresResolver only uses the first IP address rather than exposing the entire list of IP addresses. The list can be very useful for load balancing purposes.

Would u like to make a PR for this?


Set JupyterHub version as a Build Arg

The version of JupyterHub in use inside the container must match the version of JupyterHub outside the container. We should enforce this by setting a build arg that must be consumed by the Dockerfile.
Note that this is only an issue for people who make their own Dockerfiles.

We do this now, but we also no longer require JupyterHub to be installed inside binder, so that makes everything easier!


mark no @@species support for Rows/Columns classes

Rows/Columns classes extends built-in Array but do not support @@species.
They'll run into problems when @@species implementation available in node.
Fixed by declaring these classes not supporting @@species.

thank you :+1:
although, when i get time, i plan to move this project away from extending built-in classes because they are not backward compatible..
currently, i'm using babel 5 to compile es5 for old node users.. however, babel 6 does not offer support for extending base classes, so i am stuck on babel 5 until i stop extending Array.

@75lb Thanks for accepting this PR! Would be fine if you move away from extending built-in classes. I ran into this problem when running on https://github.com/nodejs/node-chakracore which has @@species support. With this change it runs fine, except that one unit test baseline does match on Windows (line ending issue). Thanks for this great module.

just fixed the failing test on Windows, thanks.
glad you like the module! i will keep my eye on @@species support..

Awesome!


Disable taps while swiping between feeds

I've been encountering this behavior on mobile, where sometimes (a lot of the times!) swiping horizontally to go from feed A to feed B registers a tap on feed A. So it would move to the next feed and after a small delay it would unexpectedly expand a post or an image from the previous feed, which makes for a very annoying experience:
https://github.com/user-attachments/assets/ede1d500-1831-4c69-a2ed-6ae0d05722cb
This is most likely a bug with react-native-pager-view, callstack/react-native-pager-view#776.
As a workaround, I made it so that while the page is being dragged, touch events are captured by the corresponding view, so hopefully no presses are triggered further down. It seems to work, and I cannot reproduce the behavior anymore, except in the case where one is at the first/last page and swipes away from the edge, like so:
https://github.com/user-attachments/assets/3fe75717-9c02-4446-a581-2e0e2c19b588

Thanks for looking into this. I agree it’s very annoying and we need to get some fix in.
Would you be open to looking into the underlying cause? We really should fix it at the pager level. If we know what the fix is, patching it in would be fine.

I tried, but I don't really know enough about gesture stuff to make a proper fix, sorry. I'll look into it some more but I'm not very confident


ServerlessPipeline Failure to create S3 bucket: Bucket name should not contain uppercase characters

Hi,
I am trying to follow Step 3 and deploy the Serverless Pipeline, but got this error.
The repo I am using is: https://github.com/sysout/aws-serverless-samfarm
I moved the files in api folder to the root folder.
See the screenshots:

Hi there,
I had a quite similar issue. The solution was to get rid of the camelCase in the service name.
So in your case I'd suggest making mystack-serverless-pipeline out of mystack-ServerlessPipeline.
Hope that helps!


Require Cycle Warning

Describe the bug
Require cycle warning in terminal:

Require cycle: node_modules/react-native-track-player/lib/index.js -> node_modules/react-native-track-player/lib/hooks.js -> node_modules/react-native-track-player/lib/index.js

To Reproduce
After yarn start I have a warning

Environment:
react-native - 0.63.4
react-native-track-player - 2.0.1

I am also running into this warning, but with a slightly different environment. It happens right on app launch. I'm using the library on iOS, not sure if the issue exists on other platforms though.
react-native - 0.65.1
react-native-track-player - 2.0.3

I see this warning as well, something we'll have to look into! Contributions are welcome :)

@redbluenat or @burdisal is this something you could help us with? Love to see a PR! thank you :) 😊

I think we may have actually fixed this issue with this commit: https://github.com/DoubleSymmetry/react-native-track-player/commit/4ee2cac155f9f1767cb79bbafe4cd0b78bea2843

The require cycle warning is back again, now on version v4.0.1:


using !ENV always gives a string

Having yml with ENV tag and default values:
...
mongodb:
  host: !ENV ${MONGO_HOST:<IP_ADDRESS>}
  port: !ENV ${MONGO_PORT:27017}
  serverSelectionTimeoutMS: 1000
...

and loading it with:
from pyaml_env import parse_config
appSettings = parse_config('./app/settings/app.yml')

gives me:

a string for host and port (no matter if the ENV variable exists or not)
a number for serverSelectionTimeoutMS

I would expect that "port" is interpreted as a number too (cause the default value is a number). Otherwise I have to convert every time I use it.
Is there a way to accomplish that?

How are you converting it now?

YAML can autodetect data types. However, it is often necessary to explicitly specify the type using a tag. To force a type, we can prefix the type with a !! symbol, for instance example: !!float 23.
However example: !!float !ENV ${EXAMPLE} returns an error, making impossible to use such tool. Any thoughts on that?

@m3mayllon A great idea! I tried several ways to have this done, but the only way I could do it was via the tag:yaml.org,2002: tag which is the translation of !! (see here )
Can you all take a look at the PR and let me know if this resolves your issue so that I can merge please? :)

@m3mayllon thanks for testing this :)
Yeah, not happy with the aesthetic part too, but I didn't want to introduce a completely new way of doing !!float 😬 I mean we could do !TAG float!! ${...} !TAG :float ${...} or any other variation that is not an existing yaml tag denotation to avoid getting exceptions but... Let me know if you have any other ideas, I'll wait a bit before merging this.