Centroid of invalid MultiPolygon is defined and not within coverage of shape

Expected behavior and actual behavior.
The centroid of an invalid MultiPolygon is defined, but is not within the coverage of the shape. I would expect the centroid to be undefined (None) for an invalid geometry.
Steps to reproduce the problem.
My use case is calculating the centroid of antimeridian-spanning images. I split the antimeridian-spanning Polygon into a MultiPolygon and get the centroid of this shape. Initially, I did not realize that my initial Polygon was invalid according to the is_valid method because of a line along the antimeridian (self-intersection). If the geometry is not valid, I would not expect a centroid value to be available -- I would expect it to be None, as it has no meaning in the context of an invalid geometry.
The shape looks like:

In my case, the centroid value and what i would expect for the centroid are shown below:

The code to do this computation is:
import shapely

geometry = {
  "type": "MultiPolygon",
  "coordinates": [
    [
      [
        [
          180.0,
          66.6956303
        ],
        [
          180.0,
          66.685634
        ],
        [
          178.474107,
          66.653756
        ],
        [
<PHONE_NUMBER>0000004,
          65.67165
        ],
        [
          180.0,
          65.699713
        ],
        [
          180.0,
          65.7104459
        ],
        [
          180.0,
          66.6956303
        ]
      ]
    ],
    [
      [
        [
          180.0,
          65.7104459
        ],
        [
          181.03381,
          65.721148
        ],
        [
          180.9557,
          66.7056
        ],
        [
          180.0,
          66.6956303
        ],
        [
          180.0,
          65.7104459
        ]
      ]
    ]
  ]
}

sg = shapely.geometry.shape(geometry)

print(f"centroid: {sg.centroid}")
print(f"convex hull: {sg.convex_hull}")
print(f"convex hull centroid: {sg.convex_hull.centroid}")

And gives output:
centroid: POINT<PHONE_NUMBER>6504603 66.15570510691623)
convex hull: POLYGON ((178.64650700000004 65.67165, 178.474107 66.653756, 180 66.6956303, 180.9557 66.7056, 181.03381 65.721148, 180 65.699713,<PHONE_NUMBER>0000004 65.67165))
convex hull centroid: POINT<PHONE_NUMBER>9779035 66.19375407103354)

Operating system
MacOS 13.x
Shapely version and provenance
shapely 2.0.1
geos 3.11.1

Hi @gadomski, thanks for your report and sorry for the late response.

I would expect the centroid to be undefined (None) for an invalid geometry.

I understand why you expect this, but GEOS (and also shapely) has the policy to “fail in exciting ways” on invalid geometries. This is for performance reasons: we don’t check preemptively on geometry validity. The only guarantee you get is that it doesn’t crash your interpreter; the returned could be anything.
So if you are unsure about the validity of your geometry, please check it explicitly!

I love that policy. Now that we know this, we're checking the validity and correcting it before getting the centroid, and that has worked fine. Thanks!


Use Intune to turn on cloud protection - guidance no longer accurate

Use Intune to turn on cloud protection
The guidance in this section is no longer accurate and appears to relate to an older version of endpoint.microsoft.com

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

ID: 77bcfc10-a6b2-04a9-180e-7e0ffa230c36
Version Independent ID: 8ed5bf92-9816-fb44-ca16-8d6fd8b1e37f
Content: Turn on cloud protection in Microsoft Defender Antivirus
Content Source: microsoft-365/security/defender-endpoint/enable-cloud-protection-microsoft-defender-antivirus.md
Service: microsoft-365-security
Sub-service: mde
GitHub Login: @denisebmsft
Microsoft Alias: deniseb

@dpshutts Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/10205
Once the author approves, the changes will be live.
Thanks
Sri


docs: add html documenation

Codecov Report

Merging #5 (bfe1d5c) into main (5c59fff) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main       #5   +/-   ##
=======================================
  Coverage   98.63%   98.63%
=======================================
  Files           2        2
  Lines          73       73
=======================================
  Hits           72       72
  Misses          1        1

Impacted Files
Coverage Δ

src/bip39.cr
98.14% <100.00%> (ø)

src/util.cr
100.00% <100.00%> (ø)

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 5c59fff...bfe1d5c. Read the comment docs.


Support getting TOP N rows from table

Hi Paulo,
I'm working with very large tables (100K+ rows) and just need to process all records in the table. Getting all rows at once is not practical, and I don't know content of the table, so limiting by custom filter or querying by partition key is not option here.
So I updated the module to be able to specify # of records to return from query, and call into table iteratively until all rows are processed.
I guess this may get handy to other people as well, so I'm proposing this to get included into your version
Regards,
Jiri

hi @donghexu, this one we need to investigate since the proposed code limits all queries to<PHONE_NUMBER> maximum and I'm not sure that if we limit it we may be blocking someone. So this should be made optional.


Fixed #5562 -- Show welcome screen regardless of DEBUG value

Fixed #5562

Changed signature of internal _handle_no_page function

Coverage remained the same at 82.519% when pulling a6bb19f7de301c7b1ed572da74c15c4e0c735877 on czpython:fixes/3.4.x/5562 into 9c79fae2f86076603ef9c2d2364f3bbb04027920 on divio:release/3.4.x.

Coverage remained the same at 82.519% when pulling f8ad362b8b2c3b0a5794f4520ce425e554ba2662 on czpython:fixes/3.4.x/5562 into 9c79fae2f86076603ef9c2d2364f3bbb04027920 on divio:release/3.4.x.

Coverage remained the same at 82.519% when pulling b17151f3ad3dcb05dd53acdfb2175ed530149e86 on czpython:fixes/3.4.x/5562 into 9c79fae2f86076603ef9c2d2364f3bbb04027920 on divio:release/3.4.x.

@vxsx would you mind having a look? Seems like one of the FE tests is legitimately failing.

Coverage remained the same at 82.622% when pulling 0ad762b4deb4968c162210e75fab07944d159683 on czpython:fixes/3.4.x/5562 into 7e2e4995740d9e8cf3c6061c3bea9a12cfbbface on divio:release/3.4.x.

Coverage remained the same at 82.489% when pulling ebb06009590ad161c29505463247ea3ce46a24cd on czpython:fixes/3.4.x/5562 into 4b8089b8b6861f09f904aeb4ec2432d74efcee12 on divio:release/3.4.x.

Coverage increased (+0.1%) to 82.598% when pulling b6848b0e9b3a139f2e78a320e6cbdc7720126f9f on czpython:fixes/3.4.x/5562 into 4b8089b8b6861f09f904aeb4ec2432d74efcee12 on divio:release/3.4.x.

This will land on 3.4.3

Coverage remained the same at 82.604% when pulling d74838b4da5719276d3848af0430845ddb35d283 on czpython:fixes/3.4.x/5562 into 63e51f37eabf08623e14e07d4d920d17640839ba on divio:release/3.4.x.

Because this is a change in behavior, I'm pushing this to 3.5.0

Changes Unknown when pulling 6da095e61a95a37ec16e92a733799061f1fac5da on czpython:fixes/3.4.x/5562 into ** on divio:develop**.


yeelight 皓石吊灯氛围灯无法控制

yeelight 皓石吊灯 有主灯和氛围灯，添加后在HA里只有显示和控制主灯，无法控制氛围灯。
可以通过添加自定义实体解决吗？

请更新至master分支后再试。

我是直接从HACS市场下载的，可以切换分支吗？

切换到masterwvfc分支也还是没有氛围灯的控制选项。

https://github.com/al-one/hass-xiaomi-miot/blob/373a8f11a969dd1e295f29e9847a97b3e792dc9e/custom_components/xiaomi_miot/core/miio2miot_specs.py#L1522-L1530
请检查你的本地文件以确保更新成功。

重新下载了master分支，也检查了miio2miot_specs.py这段代码，手动添加上这段，都还是不行。

请下载完整的插件代码。

更新到了Master，也重新添加了设备，还是没有氛围灯属性，是少做了什么吗？

尝试最新版本

Hi, I have just tried the latest version. The ambient light is still not showing up for me. Just the main light and off_delay_time like @rickycm. Is there anything I can run or do to help you figure out why it is not working?

@crgnclsn  Show me the entity attributes.

 Here you are!

It is integrated via account. I have tried both manual and account.
On Thu, 1 Sept 2022, 14:00 Alone, @.***> wrote:

Make sure this device is integrated by account (automatic mode), or by
token.
—
Reply to this email directly, view it on GitHub
https://github.com/al-one/hass-xiaomi-miot/issues/721#issuecomment-1234246590,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFVA5KJCPMED7QFVSRGO2VDV4CSG3ANCNFSM54UHZBAQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Error -704030013 Property is not readable comes from the cloud.
Ambient light of the device is only available in local mode.

Forced refresh in local mode.
Still only showing a single light entity with one setting.
min_mireds: 154
max_mireds: 370
effect_list: Day, Night
supported_color_modes: brightness, color_temp, onoff
color_mode: color_temp
brightness: 51
color_temp: 357
hs_color: 28.185, 62.588
rgb_color: 255, 170, 95
xy_color: 0.516, 0.386
effect: Day
model: yeelink.light.ceiling10
lan_ip: <IP_ADDRESS>
mac_address: 50:EC:50:89:77:20
entity_class: MiotLightEntity
miot_type: urn:miot-spec-v2:device:light:0000A001:yeelink-ceiling10:1
light.on: true
light.brightness: 20
light.color_temperature: 2801
light.mode: 1
light.off_delay_time: 0
state_updater: lan
sub_entities: light-2.off_delay_time-102
friendly_name: Ceiling Bar Light
supported_features: 39

Try master branch.

Working!  Many thanks.


Add build step example to README

close #26

CI fails at peter-evans/create-or-update-comment@v4 step 🤔
It appears related to GITHUB_TOKEN permission for external contributors?
https://github.com/exoego/esbuild-bundle-analyzer/actions/runs/9219330816/job/25364750063?pr=28


Canonical URL isn't updating on page change

Describe the bug
When using the Nuxt  this will automatically change on page change.
However, when using Nuxt-seo-kit this doesn't update unless the page is refreshed.
The og:URL will update on page change but the canonical URL will stay the same.
Reproduction
No response
System Info
System:
    OS: macOS 13.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 96.31 MB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.9.1 - /opt/homebrew/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 8.19.1 - /opt/homebrew/bin/npm
  Browsers:
    Firefox Developer Edition: 109.0
    Safari: 16.2

Used Package Manager
yarn
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

Hey @Ben-VP
Thanks for the issue. The canonical URL was set not to be reactive due to robots only needing it on the initial server response. I've updated it to be reactive just in case something needs it dynamically though
The change is available in 0.4.7

Thanks @harlan-zw, seems to work but after a few page navigations it disappears.

I can't seem to replicate it disappearing, any chance of a reproduction repo or some more details?
Again wouldn't cause any issues as only the initial load is considered by robots.


[vcpkg] Fix name clash (e.g. "all" build for triplet x64-windows-release and "release" build for triplet x64-windows).

Describe the pull request
This fixes name clash still left after 7534d24
•	What does your PR fix?
•	Which triplets are supported/not supported? Have you updated the CI baseline?
all
•	Does your PR follow the maintainer guide?
Yes
•	If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?
N/A
If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

This is re-open of #22501
.combined name change does not make sense to me as the filenames that conflict here are:

${CURRENT_BUILDTREES_DIR}/cmake-vars-${TARGET_TRIPLET}.${VCPKG_BUILD_TYPE}.cmake.log (line 43), when building for TARGET_TRIPLET=x64-windows, VCPKG_BUILD_TYPE=release
${CURRENT_BUILDTREES_DIR}/cmake-vars-${TARGET_TRIPLET}.cmake.log (line 46), when building for TARGET_TRIPLET=x64-windows-release

.combined name change does not make sense to me as the filenames that conflict here are:

${CURRENT_BUILDTREES_DIR}/cmake-vars-${TARGET_TRIPLET}.${VCPKG_BUILD_TYPE}.cmake.log (line 43), when building for TARGET_TRIPLET=x64-windows, VCPKG_BUILD_TYPE=release
${CURRENT_BUILDTREES_DIR}/cmake-vars-${TARGET_TRIPLET}.cmake.log (line 46), when building for TARGET_TRIPLET=x64-windows-release

I think the idea was to always set(cmake_vars_file "${CURRENT_BUILDTREES_DIR}/cmake-vars-${TARGET_TRIPLET}-combined.cmake.log"). So for each suffix in combined, rel, dbg, it is clear that triplet ends before the suffix.

As I said back in https://github.com/microsoft/vcpkg/pull/22501/ , I don't like whether something is a "-" vs "." to be "load bearing" like this. If the names are conflicting we should pick one or the other to "own" the pattern and add actual name text to distinguish the other rather than only punctuation.

I think the idea was to always set(cmake_vars_file "${CURRENT_BUILDTREES_DIR}/cmake-vars-${TARGET_TRIPLET}-combined.cmake.log"). So for each suffix in combined, rel, dbg, it is clear that triplet ends before the suffix.

That would work!

.combined name change does not make sense to me as the filenames that conflict here are:

${CURRENT_BUILDTREES_DIR}/cmake-vars-${TARGET_TRIPLET}.${VCPKG_BUILD_TYPE}.cmake.log (line 43), when building for TARGET_TRIPLET=x64-windows, VCPKG_BUILD_TYPE=release
${CURRENT_BUILDTREES_DIR}/cmake-vars-${TARGET_TRIPLET}.cmake.log (line 46), when building for TARGET_TRIPLET=x64-windows-release

I think the idea was to always set(cmake_vars_file "${CURRENT_BUILDTREES_DIR}/cmake-vars-${TARGET_TRIPLET}-combined.cmake.log"). So for each suffix in combined, rel, dbg, it is clear that triplet ends before the suffix.

I am not sure I understand. cmake-vars do not conflict with -rel or -dbg (because VCPKG_BUILD_TYPE is "release" or "debug", not "rel" or "dbg"). They conflict with each other in case TARGET_TRIPLET=windows-x64-release (no VCPKG_BUILD_TYPE) and TARGET_TRIPLET=windows-x64, VCPKG_BUILD_TYPE=release

Again, unconditionally
set(cmake_vars_file "${CURRENT_BUILDTREES_DIR}/cmake-vars-${TARGET_TRIPLET}-combined.cmake.log")

i.e. replace the if-else-endif from https://github.com/microsoft/vcpkg/commit/7534d241b08dc0c80d14c09f955c161e7cf5f92f.

triplet
file / build type
filename

x64-windows
combined
cmake-vars-x64-windows-combined.cmake

included for release
cmake-vars-x64-windows-rel.cmake

included for debug
cmake-vars-x64-windows-dbg.cmake

x64-windows-rel
combined
cmake-vars-x64-windows-rel-combined.cmake

included for release
cmake-vars-x64-windows-rel-rel.cmake

(not) included for debug
cmake-vars-x64-windows-rel-dbg.cmake

x64-windows-release
combined
cmake-vars-x64-windows-release-combined.cmake

included for release
cmake-vars-x64-windows-release-rel.cmake

(not) included for debug
cmake-vars-x64-windows-release-dbg.cmake

Looking again at the problem which https://github.com/microsoft/vcpkg/commit/7534d241b08dc0c80d14c09f955c161e7cf5f92f:
I assume you wanted to use a different combined file name because the content varies with VCPKG_BUILD_TYPE changes in the portfile. Let's remove this variation: always write both include lines, and do one of the following:

use the OPTIONAL keyword for include.
when VCPKG_BUILDT_TYPE is set, set the cache file variable to the actual file for that build type.

Convert this PR to draft since there is no progress.


OpenKeychain: Easy PGP

What went wrong?
OpenKeyChain doesn't accept the NFC key from WearAuthn: Error: Initialization failed! My first question is: Should it be able to tho? It doesn't seem locked to a specific brand security token.
Steps to reproduce

Inside OpenKeyChain go to Use security token (if the app has a key setup, use the ⋮ (three dot) symbol and select "manage my keys")
Tap the Watch to the back of the phone as explained.
Receive error

Which model is your watch?
TicWatch Pro (OG) WF12096
Which Android version is running on your watch?
2.19 (H)
Which version of WearAuthn are you using?
0.9.16
Screenshots
n.a.

In the context of OpenKeychain, a "security token" is an OpenPGP hardware token with NFC support. WearAuthn is an implementation of FIDO2, which is an entirely different standard that is not related to OpenPGP in any way - for example, it can't do any kind of public key encryption.
The confusion probably arises because many popular hardware tokens (such as Yubikeys) support both FIDO2 and OpenPGP.


exp/services/recoverysigner: improve logs and alerts

Logs to add:

[ ] Any action the results in a db operation (insert, update, delete).
[ ] Each successful or unsuccessful authentication (the unsuccessful case might be something to remove if we see a lot of them)
[ ] Each successful transaction signed including the transaction hash in the log

Alerts to add:

[ ] Any error resulting in a 500 being returned to the client.

#2567 resolves this issue, and I've opened #2568 for a specific improvement.


Input scaling and datatype on version 1 RT_DETR pytorch model

Hello,
I wanted to use scaling and different input data type on rt-detrv2 but due to fixed TensorRT version, I can't use rt-detr v2. So, I put some tricks on the version 1 for dataloader to provide non-scaled int8(0-255) HWC format sample and cast the input of RT_DETR forward function to the float(0-255) CHW format to use the original implementation without extra changes. However, when I convert it into TensorRT engine, I got a lot of errors for the weights quantization.
These are the list of errors I got:
1 weights are affected by this issue: Detected FP32 infinity values and converted them to corresponding FP16 infinity.
271 weights are affected by this issue: Detected subnormal FP16 values.
67 weights are affected by this issue: Detected values less than smallest positive FP16 subnormal value and converted them to the FP16 minimum subnormalized value.
6 weights are affected by this issue: Detected finite FP32 values which would overflow in FP16 and converted them to the closest finite FP16 value.
Is it because of the structure of rt-detr version 1 or TensorRT problem? I'm wondering about if there is specific reason that scaling and dtype implementation is missing in the version 1 for pytorch.
Thank you

I don't think it's a model problem. The input is inconsistent with the training after you change it like this.


Freifunk/80211s defaults backport for 18.06

Add default values for freifunk and profile_berlin.
defaults are for /etc/config/freifunk are
config 'defaults' '80211s'
      option 'mode' 'mesh'
      option 'encryption' 'none'
      option 'mesh_id' 'Mesh-Freifunk'
      option 'mesh_fwding' '0'

the defaults for profile_berlin are
config 'defaults' '80211s'
      option 'mesh_id' 'Mesh-Freifunk-Berlin'

This was discussed in issue #2503
Since going forward the freifunk related packages will be removed from luci and put in it's own repo, the PR #2518 has been resubmitted in freifunk/openwrt-packages.
Signed-off-by: pmelange<EMAIL_ADDRESS>

The PR in freifunk/openwrt-packages is https://github.com/freifunk/openwrt-packages/pull/3

Could you elaborate? Why making changes here (and not remove it) when actually moving the package to freifunk repo?

The removed freifunk packages is new in the master branch, what will eventually become 19.x.  Even though we are getting ready to make the jump to 19.x, the Freifunk-Berlin Firmware is still basing it's development on the 18.x branch.
Sorry for any confusion.


[2024a] sync the 2024a release branch with the main branch

[2024a] sync the 2024a release branch with the main branch
Fixes: https://github.com/opendatahub-io/notebooks/pull/548

/approve
We are merging this to get the 2024a branch in place.


 I've found out that the right command would be yd eval instead of yd read, and now I fix it. I'll make a pull request to fix this issue now.

another related issue: after fixing yd read the same task outputs Flag --tojson has been deprecated, please use -o=json instead. I'll fix it as well.

Here is described what happened with yq read command (in v3 it was a proper command, now in v4 it's substituted with eval or e: https://mikefarah.gitbook.io/yq/upgrading-from-v3


Returns client response from upload_file

Fixes #82
The only thing I'm not sure of here is the testing.  I'm not a fan of having multiple assert statements in the same test cases but I don't want to duplicate the existing test code unnecessarily.  Thoughts?

I really want this. Thanks for fix it

@aweidner I'm interested on this to be reviewed by upstream too. Would you mind to tag the issue with the label "needs-review" to bring better visibility over it?

@ricbartm Seems only those with write access to the repository are allowed to apply a label to a pull request.  I'd love to get this reviewed if possible though, it has been open for a while now.


test: add test for start studio

Description

Added test for start studio

Related issue(s)

Fixes #106

I just checked it in my machine and even though the test is passing the WebSocket server is not closing which leaves the test command running forever.

If you add tests you should change the prefix for PR from feat to chore, because you don't introduce new features :)

@Samridhi-98 do you plan to continue on this one, the PR test is failing

I tried fixing it but unable to do so. Need help for the same 🙂

@Samridhi-98
import { expect, test } from '@oclif/test';

describe('start', () => {
  test
    .stdout()
    .stderr()
    .command(['start:studio', '--file=./test/specification.yml', '--port=8080'])
    .it('runs studio', ctx => {
      expect(ctx.stdout).to.contain('Studio is running at http://localhost:8080?liveServer=8080');
      setTimeout(() => {
        process.exit();
      }, 5000);
    });
});

Just doing this the test cases pass but the studio also starts on the browser, which I don't know if it's ideal in gh runner, can't find any way to exit the process in a controlled manner.
One way could be to extract the server object https://github.com/asyncapi/cli/blob/5a51b5bd4bb2ec6a1b5dd0934b280b8073c142a1/src/models/Studio.ts#L94 test it and then kill the process, using oclif's testing library which is capturing the stdout messages, it's very hard to terminate the server after we are done testing.
@derberg do we absolutely need this test?

How about adding here https://github.com/asyncapi/cli/blob/master/src/models/Studio.ts#L53 listener for stop, and on stop terminate the server. Then in the test, after testing connect to the server and emit stop 🤔 some example here https://stackoverflow.com/questions/23258421/how-to-stop-app-that-node-js-express-npm-start

@Souvikns @Samridhi-98 did you have a chance to look at my proposal?

@Samridhi-98 hey, do you plan to continue with this one?

@Samridhi-98 hey, do you plan to continue with this one?

No, I'll open new one. Shall I close this PR?

@Samridhi-98 yup, that would be the best. Just open new one once you are ready


Add get_parse and get_parse_or generic over return T getters

Closes #26

@lweberk this is really great. can you also add tests please?
would love to see tests for various format types + errors.

Sure thing. Just let me figure out the codecov pipeline/machinery. I'm a little bewildered by it. It is showing things as new (numeric.rs, bulk.rs, ...) that are not. Not showing things it should (generic.rs) and showing things it should not (error.rs)

i don't care about coverage, just basic tests. so lets have generic_test.rs for that like in other modules.

Perhaps some docs under usage as well?

that would help. thanks

Ok, there we go

looks great. going to merge this in.
i'll probably update some examples and do minor cosmetic stuff..... there is another api i'm going to add (unreleated) and i'll release a new version.
thanks a lot!!!


speed up model construction

Bugfixes
Linting

Codecov Report

Merging #42 into master will increase coverage by 0.1%.
The diff coverage is 95.23%.

@@            Coverage Diff            @@
##           master      #42     +/-   ##
=========================================
+ Coverage   87.83%   87.94%   +0.1%
=========================================
  Files          14       14
  Lines         707      730     +23
=========================================
+ Hits          621      642     +21
- Misses         86       88      +2

Impacted Files
Coverage Δ

R/group_transcripts.R
96% <100%> (+0.16%)
:arrow_up:

R/create_transcript_models.R
95.65% <94.87%> (-4.35%)
:arrow_down:

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 bac6d27...3ca5389. Read the comment docs.


Fix filepath handling for a few types

What this PR does / why we need it:
This PR corrects a few unexpected results when generating a package
Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Fixes #265
Special notes for your reviewer:
55ff43e7480aadaafb09a3da77e49c47a97a2fae refactors a bit to create a new function that will use filepath.Base as default and replace it with cfg.Name if provided
507e531af5ff3c547b6c88e7643111cbbb81e634 changes how license and doc files are handled, because currently they need to be at the root of the buildroot unless a subpath was specified

Looks good after @adamperlin's comment is fixed.


Improve trailing comma situation

Codecov Report

Merging #779 into master will increase coverage by 0.1%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master     #779     +/-   ##
=========================================
+ Coverage   62.16%   62.26%   +0.1%
=========================================
  Files          82       82
  Lines       12944    12937      -7
  Branches     2665     2661      -4
=========================================
+ Hits         8046     8055      +9
+ Misses       3192     3178     -14
+ Partials     1706     1704      -2

Impacted Files
Coverage Δ

vm/src/stdlib/ast.rs
29.1% <0%> (+0.07%)
:arrow_up:

vm/src/compile.rs
75.63% <0%> (+0.25%)
:arrow_up:

parser/src/ast.rs
14.6% <0%> (ø)
:arrow_up:

vm/src/builtins.rs
64.16% <0%> (+0.38%)
:arrow_up:

vm/src/stdlib/platform.rs
47.36% <0%> (+47.36%)
: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 a59db05...29a137b. Read the comment docs.


Configuring Minimal theme's bold formatting to 'look like' the default Obsidian bold formatting.

Is your feature request related to a problem? Please describe.
I'm loving the Minimal theme and how easily customized it is, but I've noticed it's almost impossible for me to see bold formatting in the theme. Googling online I haven't found anyone else mentioning this, but the differences between Minimal and vanilla obsidian seem stark:

There may also be a way to do this that I haven't found. I tried messing with bold-text-weighting but that didn't really do anything to get it closer to the vanilla look.

You can change the bold weight by going to Style Settings > Minimal > Text
Try larger numbers like 700 or 800. It will also depend on the font you are using. Obsidian default font is Inter


[TB] Issues with Hotlinks color swatches

Problem/Concern
Steps to recreate:

Load "My Design" pre-defined design system
Go to Atoms->Hotlinks, select "No" for default underlining in light mode
Click on Components tab
Select Dark Mode
Click on Components->Colors->Hotlinks

You'll notice that in the Dark Hotlinks section that all three text samples are underlined, but not all samples under White Hotlinks are which seems inconsistent.  It also appears that the white styles in this section aren't synchronized with the black styles in this section (e.g. white text is underlined with hardcoding, black text is using var(-hotlinkOnBlack-decoration)).
Assigning to @lwnoble.  If Lise can give me the proper behavior, I'm happy to fix it.
For example, should black and white have pre-set rules here or are they adapting to design system atom and molecule settings?
Proposed Solution

Cannot be reproduced.  @aaronreed708 to verify if this is still a problem.

@brycecurtis @lwnoble We missed step #2 in the instructions when trying to recreate today.  You have to set default underlining to "no", then try to load the Components->Colors->Hotlinks in darkmode.  You'll see this, which I believe is incorrect:


Dashboard - Metabase

Hi,
Metabase is an open-source popular BI solution.
As Apache superset, integration Metabase would be a nice feature.

@haithem-souala Thanks a lot for opening this issue. Let us know if you are interested in contributing . We can help with the code base.

Api details https://www.metabase.com/docs/latest/api-documentation.html
Lets collect

Dashboard
Metric , it will be chart on OM side
what queries each Metric is using

You rock guys!!


Milestone 3: Add a Contact Form

Portfolio Milestone 3: Add a Contact Form
In this milestone I:
•	Created a new branch according to the GitHub flow rules
•	Added a .gitignore file
•	Set up the linters config
•	Used grid layout
•	Used flexbox
•	Created hover effect
•	Used button interactions
•	Created a UI
•	Used images and backgrounds to enhance the look of the website
•	Created forms with HTML5 validations
•	Used field validations
•	Collected data by using the Formspree service
•	Worked with my coding partner as a group

Thanks for your review @Shedrack-Sunday. I hope to be a code reviewer in the near future as well.

I wish you good luck bro 💯


Issues with dark mode

Framework/code-stack
React
Scope
Core application
Description

Unable to preserve dark mode between refresh
Select input options are not visible properly in dark mode

https://github.com/sadanandpai/frontend-mini-challenges/assets/44774504/02c191a0-f282-4605-8c61-409030ed8272
Expected behaviour

Should be able to preserve dark/light modes between refresh
Select input options should be visible properly in both modes

Suggested Solutions

Use local storage to preserve the selected mode
Update styles of Select options based on selected mode

Additional Context
No response

I can work on this, please assign to me.


fix travis build

fixes the travis build and uses the OOB providers along with travis encrypt for secrets on THIS repo

Don’t merge yet.. still has an issue... @liliankasem


feat(builder): Use builtin:swc-loader instead of Rspack's built-in translation behavior

Summary

🤖 Generated by Copilot at 1190c9c
This pull request introduces a new feature to use Rspack builtin:swc-loader and disableTransformByDefault options instead of Rspack's built-in transformation behavior, which improves the performance and compatibility of the code transformation. It also adds support for fast refresh for React components in Rspack mode, and maintains backward compatibility with the legacy transformation behavior through an environment variable. It updates the documentation, the tests, and the dependencies accordingly. It also fixes a circular dependency issue in hmr.ts. It temporarily adds rspress and @rspress/shared as overrides for testing purposes.
Details

🤖 Generated by Copilot at 1190c9c

Add new changeset files for @modern-js/builder-rspack-provider and @modern-js/app-tools packages to describe new features (link, link)
Add rspress and @rspress/shared as overrides for @modern-js/builder-rspack-provider package for testing purposes (link)
Add @rspack/plugin-react-refresh as a dependency for @modern-js/builder-rspack-provider package to enable fast refresh for React components in Rspack mode (link)
Remove polyfill property from outputConfigSchema as it is no longer needed in Rspack mode (link)
Modify builderPluginBabel function to use useLegacyTransform function to check the transformation mode, add builder-plugin-swc as a pre-requisite plugin, add a TODO comment for preset-typescript optimization, and use different logic for applying script condition and loader order (link, link, link, link)
Add swc-old.ts file that contains the old version of builderPluginSwc function for legacy transformation mode (link)
Modify react.ts file to use useLegacyTransform function to check the transformation mode (link)
Modify react.ts file to use pre property to indicate that builder-plugin-swc plugin is a pre-requisite (link)
Modify swc.ts file to import more types and functions from @modern-js/builder-shared, use getDefaultSwcConfig function to get the default options for builtin:swc-loader, apply the transformImport, decorator, and polyfill configurations to the swc-loader options, add the swc-loader to the bundler chain for both the JS rule and the JS data URI rule, and modify the Rspack config to set the disableTransformByDefault option to true (link, link)
Add constants.ts file that exports the useLegacyTransform function that checks the environment variable INTERNAL_USE_RSPACK_TRANSFORM_LEGACY (link)
Modify plugin.ts file to use useLegacyTransform function to conditionally apply different plugins, remove builder-plugin-babel from the default plugins, and use the old versions of builder-plugin-swc and builder-plugin-react plugins for legacy transformation mode (link, link, link)
Modify supportedRspackMinimumVersion constant to 0.3.6 as the minimum version of Rspack that supports the new transformation options (link)
Modify RspackConfig type to add more types and properties for the builtin:swc-loader options and add a comment to indicate that some of the Rspack built-in options are no longer supported (link)
Modify test case to use an invalid value for the output.polyfill option to reflect the change in the outputConfigSchema (link)
Add test case to check that the default plugins are applied correctly when the legacy transformation is enabled (link)
Modify test case to enable the test for the usage mode polyfill as it is now supported by the builtin:swc-loader in Rspack mode (link)
Modify isUsingHMR function to use a narrower type for the second argument to avoid a circular dependency issue (link)
Add a note in enableLatestDecorators.md file to indicate that this option is only supported by Webpack, not Rspack (link)
Remove the tip in polyfill.md file that says that the usage mode polyfill is not supported by Rspack as it is now supported by the builtin:swc-loader in Rspack mode (link)

Related Issue

Checklist

[ ] I have added changeset via pnpm run change.
[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.

use rsbuild directly
https://github.com/web-infra-dev/rsbuild/pull/170


Update Ind Language

Update language: Actions & Conditions

Get the world by world name
Create an ABB
Get an entities & players to the specified area
Set the world time
and more...

(this was taking about 40 minutes to do this. maybe..)

Thank you so much!


Colorpicker doesn't show up correctly when using a variable as a placeholder

Here's a Plunkr demo:
https://plnkr.co/edit/Ho9NBEogYkqrU0w6UpnV?p=preview
The placeholder shows just fine but everything else is messed up.
This code works:
    <color-picker ng-model="primary_color" options="{placeholder: '#123456'}" ></color-picker>

This doesn't:
    <color-picker ng-model="primary_color1" options="{placeholder: myColor}" ></color-picker>

(When $scope.myColor is defined)

Your Plunkr shows me good results, the placeholders are as intended...

Forgive me if I haven't described the issue correctly.
The placeholders are working just fine, but try to click on the colorpicker:
The second one works fine:

The first one though shows only red colorpicker and no bootstrap addon:

In your scenario on this line (https://github.com/ruhley/angular-color-picker/blob/master/src/scripts/controller.js#L402) it tries to merge the passed in options object with the default options object. Logging out the options object after the merge function results in the expected output. However outputting the options object in the html {{AngularColorPickerController.options}} only shows the provided options object, not the merged one. This only happens when using and inline options object -
<color-picker ng-model="color" options="{placeholder: myColor}" ></color-picker>

This does not happen if the options object is a defined variable and still using a variable in the placeholder.
$scope.options = {
    placeholder: myColor
};

<color-picker ng-model="color" options="options" ></color-picker>

It also works as expected if after the merge I assign the options object to another variable this.optionsClone = this.options; and then use that. I feel like this is some sort of weird AngularJS bug that two way binding doesn't work on inline objects with a variable.
If you absolutely have to pass in the options object inline then I put in the optionsClone hack for you. However I would rather fix the root cause of the problem.


fix(doc): update public readme

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

npm package (@latest dist-tag)
GitHub release
1.0.3

Your semantic-release bot :package::rocket:


feat: How can I run Dart frog with HTTPS support (SSL)?

Description
How can I configure dart frog to allow accessing the server via HTTPS? I know that I need to setup the certificate on my server accordingly. However, it seems that I'd also need to adjust how the server is started via shelf? Does dart frog so far support HTTPS connections?

Hi @zottel4242 👋
Thanks for opening an issue!
The easiest way to achieve this is by generating a production build via dart_frog build and deploying to a cloud provider which has a container registry. We currently have deployment guides for:

Google Cloud Run
AWS App Runner
Digital Ocean App Platform

We are planning to support custom entrypoints (#226) for cases where you need to manually configure the initialization of your app.
Hope that helps!

You can now use a custom entrypoint (#226) to configure the server 👍
https://dartfrog.vgv.dev/docs/advanced/custom_entrypoint

How can i run Dev Server with custom ssl cert?


One possibility would be to completeExceptionally if there was an exception

Thanks for the issue!  This should be resolved in this PR in this code.


<EMAIL_ADDRESS>

Johaness
[Enter feedback here]
####Get Rid of This Asshole
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 21ce6ac4-36b1-0520-6474-37a2bb2f78bd
Version Independent ID: a17cb98d-72db-1b3c-9d89-1af2773617ab
Content: Get started with Progressive Web Apps - Microsoft Edge Development
Content Source: microsoft-edge/progressive-web-apps-chromium/how-to/index.md
Product: microsoft-edge
Technology: pwa
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

This is whom I fell in love with. Please tell me she has nothing to do with this.


⚠ DDoS-Relay EU-C-fsn1-2 has degraded performance

In 907c1ec, DDoS-Relay EU-C-fsn1-2 (http://<IP_ADDRESS>:42069/;csv) experienced degraded performance:

HTTP code: 200
Response time: 320 ms

Resolved: DDoS-Relay EU-C-fsn1-2 performance has improved in 7a2b6f1 after 5 minutes.


Adding actions/checkout@v3 to github action docs

This step is necessary to successfully use the zed validate github action.

@josephschorr I forgot to request a reviewer before I submitted the PR, now I can't add one. Perhaps you have some admin abilities that will let you assign yourself as reviewer and review it?


Refactor Erlang AST and Parser to carry location information

In order to provide good error messages whenever there is a syntax error or a type error, we need to thread and carry this information on the AST.

This sounds incredibly useful and I would like to help. What files do you think I should start looking at?

Hej @banjomet this is a rather involved task but I'd be happy to help you get on board.
Right now I'm trying to move away from the Menhir parser an into the tree-sitter-erlang parser so the first thing we'd have to do is, well, redefine the Parsetree type 🙈 — worry not! I've got something in the works that I'll be merging sometime soon and we can have this chat again then.
In the meantime, if you want to help out with the tree-sitter-erlang parser that'd be great. The better that gets, the better Erlang parsing Caramel will have 😄
Check it out here: https://github.com/AbstractMachinesLab/tree-sitter-erlang/

I've merged a preliminary Parsetree in erl_parsetree.ml that we can start using. It is not currently in use, but we can start migrating to it.

I've merged a preliminary Parsetree in erl_parsetree.ml that we can start using. It is not currently in use, but we can start migrating to it.


enable prometheus configuration for remote write

As of right now prometheus configuration is very limited via istioctl
I have case where i need to configure prometheus to remote write to remote destination
this is done pretty well on prometheus helm package
it will be nice to have same capabilities to tune prometheus configuration via istioctl and use istio prometheus for monitoring
val-prom.yaml
server:
  remoteWrite:
  - url: http://remote_address
    queue_config:
      capacity: 100000
      max_shards: 1000
      max_samples_per_send: 1000
      batch_send_deadline: 5s
      min_backoff: 30ms
      max_backoff: 100ms
  basicAuth:
    username: user
    password: pass

helm upgrade --install prometheus -n prometheus stable/prometheus -f ./val-prom.yaml

We will not be adding configurability or supporting installation of Prometheus any longer - see https://istio.io/latest/blog/2020/addon-rework/ for details. Note we will still integrate with Prometheus but won't manage installation. Thanks!


Suggested problem solution that avoids awaiting in constructors

I believe the goal of this proposal is to be able to write code that looks something like this:
async class Base {
  constructor(fetcher) {
    this.data = await fetcher.getData();
  }

  /...
}

async class Sub extends Base {
  constructor(baseFetcher, subFetcher) {
    await super(baseFetcher);
    this.subData = await subFetcher.getData();
  }

  /...
}

It seems to me that we could get the desired subclassing behavior without having to do await inside the constructor.
Does the code pattern below solve the problem this proposal addresses?
class Base {
  constructor(data) {
    this.data = data;
  }

  static async fetchDataAndCreate(fetcher) {
    return new Base(await fetcher.getData());
  }
  /...
}

class Sub extends Base {
  constructor(baseData, subData) {
    super(baseData);
    this.subData = subData;
  }

  static async fetchDataAndCreate(baseFetcher, subFetcher) {
    return new Sub(await baseFetcher.getData(), await subFetcher.getData());
  }
  /...
}

Yes, static async methods are the proper solution, no async constructors are needed.

I believe the goal of this proposal is to be able to write code that looks something like this [...]

At stage 1 the goal of this proposal is to find out what problems there are with asynchronously initializing instances of fields. It does not tailor to a specific design direction until stage 2. The problems come from class features like class fields/accessors/etc. not having ergonomic integration with asynchronous creation of classes.

Does the code pattern below solve the problem this proposal addresses?

That uses an inversion of control to avoid asynchronous initialization entirely by relying on consumers to perform all asynchronous initialization. This investigation is partly about how to allow code to be written such that asynchronous resources do not require inversion of control. There are a variety of potential workflows we could pursue even if we do end up requiring such an inversion of control. The standardization of asynchronous initialization could be of any reasonable design and if you want to argue for inversion of control, perhaps explaining how to perform ergonomic integration with class fields and accessors such that the class author can ensure encapsulation and allow for asynchronous defaults etc. would help.

I'm not sure what you mean when you say "ergonomic integration".
Can you elaborate?
Maybe a code sample showing what you think should work but doesn't with my proposed solution?
Side note: I'm not sure "inversion of control" is what is happening with my solution.
https://en.wikipedia.org/wiki/Inversion_of_control
I'd say it's a separation of concerns.
Constructors expect to receive actual data to be stored. They are only responsible for storing it correctly in the object being constructed.

Does the code pattern below solve the problem this proposal addresses?

@brad4d
In other topic we discuss same
This example too easy: only one function - only one subclass
When your structure become complex - all become terrible.

@brad4d

I'm not sure what you mean when you say "ergonomic integration".
Can you elaborate?

A lot of JS language progression is in how usable certain workflows are and that is the core of lots of features being investigated such as this, previous features such as await, etc. The core here is that various features of JS do not work well with asynchronous initialization.

Constructors expect to receive actual data to be stored. They are only responsible for storing it correctly in the object being constructed.

This is not how JS works today so it doesn't seem really relevant as we cannot change that fact. JS has constructors that perform logic and can contain side effects. The Promise constructor is an example of JS builtin that is explicitly for that purpose of dealing with something with side effects and creating them when the Promise is initialized.
There is truth that this proposal does seek to address issues with workflows people use that do perform logic during construction, but JS the language does explicitly allow logic during construction and that cannot be changed. We should seek to understand the problems people have and serving them.
Authors of JS books even go into detail on how to perform logic and behaviors during initialization so it isn't a strange idea to perform logic, side effects, or async initialization. See https://2ality.com/2019/11/creating-class-instances.html for an example of a prevalent author doing so.


Updated Azure Cosmos DB branding.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/dotnet-tutorials-services-databases.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Empty assignments in exam

Is your feature request related to a problem?
I created a programming exercise and many students did not try the exercise at all. I am not aware of a method to grade all empty or more precisely all the students that have submitted an assignment with no difference to the given template with 0 points.
Describe the solution you'd like
I would like to have a method to directly grade all the empty assignments for an exercise with 0 points. Optionally, there could be a message that is put in the General Feedback text area for each of the assignments.

This is already possible for text, modeling and file upload exercises with the "Assess unsubmitted exams" button. We will also add this functionality for programming exercises with manual assessment. There is already a TODO in the code which was not yet implemented.

An easy solution could be a button Empty Submission instead of detecting the empty submissions.
This would also speed up the correction process.

This feature was recently implemented as part of the button access unsubmitted exams
Did it not work for you?￼￼


V2 sentinel 2 date search

Those changes allow the user to restrict the search by a date interval.
The start_date and end_date are optional. If no date is defined the function will search images between 2015 and now.

tests/timing.py was used during development to test the execution time. I removed it now.

Thank you for the changes. I did not know how to do the tests without a real call to AWS, It's a new trick and I'm grateful to learn. ;)

Yes mocking the multithreading calls is not a easy task, that's why at first I wasn't testing the sentinel2 search function :-)


Graphic for Why FlowFuse page

Related Issue
No response
Description
We need a graphic for the Why FlowFuse page so when we link to the page on social media we don't get the default FlowFuse - DevOps for Node-RED image.
I would suggest the image has somthing like:
Why FlowFuse? What FlowFuse adds to standard Node-RED.

Hi @iskerrett
Here's a version with only text
V1

And here's an alternative with a pseudo screenshot of the platform
V2

I like the second one. Can you add it to the page?


Add a Gitter chat badge to README.md

feroult/yawp now has a Chat Room on Gitter
@feroult has just created a chat room. You can visit it here: https://gitter.im/feroult/yawp.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

:+1:


fastlane deliver fails to generate html (XCode10)

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

I use fastlane deliver 2.104.0 along with Xcode 10. When deliver I get the following error during html generation. This deliver file worked in earlier versions with Xcode 9.4 perfectly.
Complete output when running fastlane, including the stack trace and command used

.....
[18:35:34]: Loading './metadata/review_information/phone_number.txt'...
[18:35:34]: Loading './metadata/review_information/email_address.txt'...
[18:35:34]: Loading './metadata/review_information/demo_user.txt'...
[18:35:34]: Loading './metadata/review_information/demo_password.txt'...
[18:35:34]: Loading './metadata/review_information/notes.txt'...
[18:35:35]: Detected languages: ["de-DE", "en-AU", "en-CA", "en-GB", "en-US", "es-ES", "es-MX", "fr-CA", "fr-FR", "ja", "ko", "pt-BR", "pt-PT", "ru", "zh-Hans", "default"]
[18:35:35]: #TypeError: no implicit conversion of nil into String
[18:35:35]: /Users/neu/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.104.0/deliver/lib/deliver/html_generator.rb:61:in `join'
/Users/neu/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.104.0/deliver/lib/deliver/html_generator.rb:61:in `render'
/Users/neu/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.104.0/deliver/lib/deliver/html_generator.rb:13:in `run'
/Users/neu/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.104.0/deliver/lib/deliver/runner.rb:180:in `validate_html'
/Users/neu/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.104.0/deliver/lib/deliver/runner.rb:117:in `upload_metadata'
/Users/neu/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.104.0/deliver/lib/deliver/runner.rb:38:in `run'
/Users/neu/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.104.0/deliver/lib/deliver/commands_generator.rb:79:in `block (2 levels) in run'
/Users/neu/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
/Users/neu/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
/Users/neu/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
/Users/neu/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
/Users/neu/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.104.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:74:in `run!'
/Users/neu/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
/Users/neu/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.104.0/deliver/lib/deliver/commands_generator.rb:182:in `run'
/Users/neu/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.104.0/deliver/lib/deliver/commands_generator.rb:17:in `start'
/Users/neu/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.104.0/fastlane/lib/fastlane/cli_tools_distributor.rb:100:in `take_off'
/Users/neu/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.104.0/bin/fastlane:20:in `'
/Users/neu/.fastlane/bin/bundle/bin/fastlane:22:in `load'
/Users/neu/.fastlane/bin/bundle/bin/fastlane:22:in `'
[18:35:35]: Could not render HTML preview. Do you still want to continue?

Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
10.13.6

Ruby
2.2.4

Bundler?
false

Git
git version 2.17.1 (Apple Git-112)

Installation Source
~/.fastlane/bin/bundle/bin/fastlane

Host
Mac OS X 10.13.6 (17G65)

Ruby Lib Dir
~/.fastlane/bin/bundle/lib

OpenSSL Version
OpenSSL 1.0.2g  1 Mar 2016

Is contained
false

Is homebrew
true

Is installed via Fabric.app
false

Xcode Path
/Library/Developer/CommandLineTools/

Xcode Version

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE
en_US.UTF-8
✅

fastlane files:
No Fastfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.104.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

slack-notifier
2.3.2

atomos
0.1.3

CFPropertyList
2.3.6

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.6.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
1.8.0

unicode-display_width
1.1.3

terminal-table
1.7.3

plist
3.4.0

public_suffix
2.0.5

addressable
2.5.2

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.6.4

tty-cursor
0.5.0

tty-spinner
0.8.0

babosa
1.0.2

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.60.0

faraday
0.14.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.1

gh_inspector
1.1.2

json
1.8.1

mini_magick
4.5.1

multi_json
1.13.1

multi_xml
0.6.0

rubyzip
1.2.2

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.2.1

bundler
1.14.6

faraday_middleware
<IP_ADDRESS>

naturally
2.1.0

simctl
1.6.3

uber
0.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.1

mime-types-data
3.2016.0521

mime-types
3.1

little-plugger
1.1.4

logging
2.2.2

jwt
1.5.6

memoist
0.16.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

google-api-client
0.21.2

emoji_regex
0.1.1

libxml-ruby
3.0.0

generated on: 2018-09-18

It seems like you have not included the output of fastlane env
To make it easier for us help you resolve this issue, please update the issue to include the output of fastlane env 👍

corrected ;-)

Anybody who experiences similar problems ?
In addition deliver seems to be extremely moody because currently  I need up to 10 attempts to upload metadata. 9 fails and then suddenly 1 successful upload.
Any help ?


AwesomeOpenSource

We are creating a github org for all awesome open source repos. I am working with a few individuals who are also managing their own awesome repos, and I think to gain more traction we need to work together. What are your thoughts about collectively moving your awesome repos to https://github.com/AwesomeOpenSource
The idea is that visibility for these repos would be increased due to more traffic to the org. What are your thoughts? Let me know if there is anything you'd like to discuss!

That's an interesting idea.
I think this is not a good fit for "awesome-rust" at this time, because Rust is a very young language. Quite some projects are started, but not always finished. This project started as a spin-off from a similar page in the Rust wiki. The main goal here is to have less entries and more quality of entries. I am not convinced that more contributors will support this goal.


Laravel Version Requirement

Installation of composer package failed for me. The error message seems to suggest that Laravel 8 is required and we're on Laravel 7. I don't see requirement information listed in the documentation and, after scanning the composer.json file, I'm not sure where it's coming from. If it is a requirement, would be handy to add it to the README.md
  Problem 1
    - Installation request for primitive/openapi-initializer ^1.1 -> satisfiable by primitive/openapi-initializer[1.1.0].
    - Can only install one of: laravel/framework[v7.30.4, 8.x-dev].
    - Can only install one of: laravel/framework[8.x-dev, v7.30.4].
    - Can only install one of: laravel/framework[8.x-dev, v7.30.4].
    - Conclusion: install laravel/framework 8.x-dev
    - Installation request for laravel/framework (locked at v7.30.4, required as ^7.0) -> satisfiable by laravel/framework[v7.30.4].

@Zaskoda thanks for the issue report. I will take a look hopefully this evening and get a fix pushed up.

@Zaskoda I have tagged a new release 1.3.0 that allows for installation on both 7.x and 6.x of Laravel. It also removes the hard dependency on php 7.4 as well.
I will update the docs with the requirements, but please let me know if you run into any more issues.


Could Lithuanian language be added?

I am a native speaker so I could help.
How hard is it to add another language?
And how exactly does one do that?

@DamaKubu i think you can look on this repo for adding language https://github.com/MihaiValentin/lunr-languages/blob/master/CONTRIBUTING.md


Online version from READ.ME show 404

I tried to use the online version of the extension as the extension is not not available on Firefox now but it shown 404 when I tried to access the link, is the online version no longer maintained or are there any replacement?
Thank you

@wasd0109, unfortunately, I am no longer maintaining for Firefox as they require some additional work to pass their security checks. But I keep updating for Chrome.


Compilation takes too long

Hi,
Currently trying to use SOAP for fine-tuning HF base model, but compilation takes too long. Is this expected?

Sample code
import jax
import jax.numpy as jnp
from transformers import FlaxBertForSequenceClassification, BertConfig
from transformers import BertTokenizer
from flax.training.train_state import TrainState
from transformers.models.bert.modeling_flax_bert import FlaxBertModel, FlaxBertModule
import optax
import soap

def create_train_state(model, learning_rate=1e-5):
    """Creates initial `TrainState` for the model."""
    learnin_rate_fn = optax.join_schedules(
        schedules=[
            optax.linear_schedule(0.0, 0.001, 1000),
            optax.linear_schedule(0.001, 0.0, 5000 - 1000),
        ],
        boundaries=[1000],
    )

    opt = soap.soap(learning_rate=learnin_rate_fn, b1=0.9, b2=0.999, eps=1e-8, weight_decay=0.01, precondition_frequency=5)
    module = FlaxBertModule(model.config)
    state = TrainState.create(
        apply_fn=module.apply,
        params=model.params,
        tx=opt
    )

    return state

@jax.jit
def train_step(state, batch):
    """Single training step."""
    def loss_fn(params):
        outputs = state.apply_fn(
            {'params': params},
            batch['input_ids'],
            attention_mask=batch['attention_mask'],
            deterministic=False,
            rngs={'dropout': jax.random.PRNGKey(0)}
        )
        logits = outputs.last_hidden_state
        loss = jnp.mean(logits)
        return loss

    grad_fn = jax.value_and_grad(loss_fn)
    loss, grads = grad_fn(state.params)

    # Update parameters
    new_state = state.apply_gradients(grads=grads)

    return new_state, loss

# Initialize model and tokenizer
config = BertConfig.from_pretrained(
    'bert-base-uncased'
)
model = FlaxBertModel.from_pretrained(
    'bert-base-uncased',
    config=config
)
tokenizer = BertTokenizer.from_pretrained('bert-base-uncased')

# Create dummy batch
text = ["This is a positive review!", "This is a negative review!", "This is a neutral review!", "This is a mixed review!", "This is a review!"]
labels = jnp.array([1, 0, 2, 3, 4])

# Tokenize
encoded = tokenizer(
    text,
    padding=True,
    truncation=True,
    max_length=128,
    return_tensors='np'
)

# Create batch
batch = {
    'input_ids': encoded['input_ids'],
    'attention_mask': encoded['attention_mask'],
    'labels': labels
}

# Initialize training state
state = create_train_state(model)

# Perform single training step
new_state, loss = train_step(state, batch)
print(f"Loss: {loss}")

Its expected that it takes a while to compile, each parameter update requires a loop over the preconditioners. It's possible that I can use https://jax.readthedocs.io/en/latest/_autosummary/jax.lax.scan.html to reduce the compilation time, I'll take a look at that.
Thanks for providing some example code.

The long compile time makes parameter sweeps very difficult. Please consider using scan to avoid the loop.


add API documents, update change log

@alexwwang @HaoyuHu I have re-organized the documents, added new API page. Remember to check it out~

@alexwwang @HaoyuHu I have re-organized the documents, added new API page. Remember to check it out~

Ok. I will.
Thank you for reminding me.
On Sun, Jul 14, 2019 at 15:37 Eliyar Eziz<EMAIL_ADDRESS>wrote:

@alexwwang https://github.com/alexwwang @HaoyuHu
https://github.com/HaoyuHu I have re-organized the documents, added new
API page. Remember to check it out~
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/BrikerMan/Kashgari/pull/150?email_source=notifications&email_token=AAGRFKRIPBEEIWMYIPVN4OLP7LJT3A5CNFSM4IDKNDA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ377RQ#issuecomment-511180742,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGRFKRUY2DUPM6M2OTL72TP7LJT3ANCNFSM4IDKNDAQ
.


config .env

Ensure that .env file is using proper variables

Looks like the issue is with the rpc public node.
The RPC node must expose the following EVM JSON RPC methods:
eth_getTransactionByHash (working)
eth_getBlockByNumber (working)
eth_getTransactionReceipt (working)
eth_getLogs (for indexing ERC20/721 transfers, not working)
eth_chainId (just called once and cached, not shown)
New task is to get both eth_getLogs & eth_chainId working


feat(frontend): deprecate CREATE MATERIALIZED SOURCE syntax

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What’s changed and what’s your intention?
From this PR on, users will use CREATE TABLE instead of CREATE MATERIALIZED SOURCE to create a table with a connector associated with it. The remaining part of the SQL command is the same as before.
Also, users will be able to perform INSERT, DELETE, and UPDATE operations on a table with a connector associated with it.
Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation
Types of user-facing changes

Connector (sources & sinks)
SQL commands, functions, and operators

Release note
Create a table with a connector associated with it:
CREATE TABLE t (
    v int
) WITH (
    connector = ‘datagen’
) ROW FORMAT json;

CREATE_TABLE

Insert into a table with a connector associated with it:
INSERT INTO t VALUES (99999999);

INSERT 0 1

Update a table with a connector associated with it:
UPDATE t SET v = 11111111 WHERE v = 99999999;

UPDATE 1

Delete from a table with a connector associated with it:
DELETE FROM t WHERE v = 11111111;

DELETE 1

Misuse old syntax:
CREATE MATERIALIZED SOURCE s (
    v int
) WITH (
    connector = ‘datagen’
) ROW FORMAT json;

ERROR:  QueryError: sql parser error: CREATE MATERIALIZED SOURCE has been deprecated, use CREATE TABLE instead

Refer to a related PR or issue link
Close #5949

Does this PR maintain backward compatibility? In other words, if a user has already created a materialized source with CREATE MATERIALIZED SOURCE and upgrades the codes to include this PR, will the existing materialized source still be usable?

Does this PR maintain backward compatibility? In other words, if a user has already created a materialized source with CREATE MATERIALIZED SOURCE and upgrades the codes to include this PR, will the existing materialized source still be usable?

Not tested yet, but I'll try to make it backward-compatible.

Does this PR maintain backward compatibility? In other words, if a user has already created a materialized source with CREATE MATERIALIZED SOURCE and upgrades the codes to include this PR, will the existing materialized source still be usable?

I prefer to not maintain the compatibility at all. IIUC, currently our catalog and other meta format does not provide any compatibility guarantee. :thinking:

Does this PR maintain backward compatibility? In other words, if a user has already created a materialized source with CREATE MATERIALIZED SOURCE and upgrades the codes to include this PR, will the existing materialized source still be usable?

Not tested yet, but I'll try to make it backward-compatible.

Per offline discussion with @st1page , backward capability is non-trivial and our system currently has no guarantee on it. We could find out a workaround if there are user requirements for this. So this PR might not include backward capability.

Does this PR maintain backward compatibility? In other words, if a user has already created a materialized source with CREATE MATERIALIZED SOURCE and upgrades the codes to include this PR, will the existing materialized source still be usable?

Not tested yet, but I'll try to make it backward-compatible.

Per offline discussion with @st1page , backward capability is non-trivial and our system currently has no guarantee on it. We could find out a workaround if there are user requirements for this. So this PR might not include backward capability.

Also discussed offline with @st1page. Maintaining compatibility is hard and may not worth it. If there is a need to upgrade version for the already deployed cases, we can write a simple tool to migrate old metadata to the new one on demand. @fuyufjh What do you think?

This PR is ready for review. PTAL @st1page @BugenZhao @tabVersion

better add an error to tell the users that we no longer support CREATE MATERIALIZED SOURCE and let them know to use create table with connector instead

@Mergifyio refresh


WIP: bump jdk8u hotspot builds to win2012

FYI @sxa555 this will allow us to destroy the 2008 machines and provision more 2012 build machines

test builds:
jdk8u-windows-x86-32 (https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-windows-x86-32-hotspot/529/)

If this gets merged, do we need to change the support statement on the website to "Windows Server 2012 or newer" instead of "Windows 2008r2 or later"?

@aahlenst we probably should even though we won't be breaking backwards compatibility because it's built on the same toolchain version

run tests

@aahlenst we probably should even though we won't be breaking backwards compatibility because it's built on the same toolchain version

I'd actually state the opposite.  We should probably make it clear what we build on vs what we can support on.

Execution error: No such property: versionInfo for class: Build

@karianna this PR checker has been broken by the recent Pipeline changes that allow the jobs to run in parallel, that particular failure has actually come from my other PR here: https://github.com/AdoptOpenJDK/openjdk-build/pull/1639
This PR is good to go (see the two test builds at the top)


Document using symbols in attributes

closes: #20
related: #19

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.83%. Comparing base (c8785ed) to head (c1ebe3a).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #21   +/-   ##
=======================================
  Coverage   93.83%   93.83%
=======================================
  Files          15       15
  Lines         454      454
  Branches       26       26
=======================================
  Hits          426      426
  Misses         26       26
  Partials        2        2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


deploy the database using helm

Closes #56

Some files on /database should be deleted, as they have been moved here.

A bit off topic from this PR, but I just realized that we could take advantage of a new field in the test_objects table. A flag called pruned or something similar to identify if the resource has been pruned after the archival or not. That way, the sink interactions with the database would be two:

Archive the object
Enable the flag after pruning the object from etcd

This could also be an advantage for the future CLI, when querying both etcd and kubearchive database and just showing the content in kubearchive that has been pruned from etcd.
What do you think @skoved?

I'm not sure about using the default instruction in the templates of the chart. I have the feeling that we are duplicating work there. I'm also thinking of the posibility of adding the required keyword instead to show in the linter where a mandatory value isn't provided.

The init_db.go creates a table. Modify the statement so it does not fail if the table already exists:
CREATE TABLE IF NOT EXISTS public.test_objects

I'm not sure about using the default instruction in the templates of the chart. I have the feeling that we are duplicating work there. I'm also thinking of the posibility of adding the required keyword instead to show in the linter where a mandatory value isn't provided.
I think is some cases a default value can be used and in others we can go with the required`. I will open an issue to check this.


Screen dumps incorrect for Sweden

Screen dumps of Sales tax report under Example, point no 6. are using norwegian/german sales tax codes and not the setup recommended on the page. Action: Update screen dumps to show Swedish VAT report with Swedish setup.

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

ID: 6892225e-76a8-be68-7fb6-1f41dd8d4c95
Version Independent ID: 6abeb12f-700e-1746-35c9-cc4a72d7166c
Content: Sales tax report for Sweden - Finance | Dynamics 365
Content Source: articles/finance/localizations/emea-swe-sales-tax-payment-report-sweden.md
Service: dynamics-365-finance
Product: ****
Technology: ****
GitHub Login: @AdamTrukawka
Microsoft Alias: atrukawk

This has been reported in bug 751251, so you may want to refer to that existing bug.


Key Binding erases file contents

I have installed the extension and it happens that when I use the KeyBinding, it erases all the file contents.

Well that's not supposed to happen.
Could you provide any details? Such as the OS you're using, the keybinding, your settings, the context of the problem. Also, if you could turn on the phpformatter.logging, try formatting again, and then posting the console log, we might be able to shed a little light on the problem at hand.
If you could post the results here, then we might be able to figure this out together.
Thanks for bringing this to my attention.

I running Visual Code 1.4 on Windows 10 64, with these user settings:
    "phpformatter.composer": true,
    "phpformatter.onSave": true,
    "phpformatter.level": "psr2",
    "phpformatter.logging": true

And this keybinding:
{
        "key": "ctrl+shift+l",
        "command": "phpformatter.fix",
        "when": "editorFocus"
    }

No output to console, by the way!

Exact same Problem here. In Addition when I activate the onSave Feature nothing happens.

This issue gave me huge headache, but I finally managed to fix it.
First, I tried checking whether this had anything to do with reading the file using NodeJS's fs library. According to the documentation, fs.readFileSync reads the entire file.
So, then I immediately assumed this had something to do with character encoding. After having spent several hours on that, I came to the conclusion that it could not be character encoding. I had completely isolated the issue from that.
So then I started fiddling around with reading files. Because I could positively confirm that the contents of the *.tmp files were properly written, the issue had to be with reading them. That's when I tried reading the file without using the file descriptor. Surprisingly, the entire file was read this time. Obviously, the file descriptor stored the wrong cursor position, which was used by fs.readFileSync.
The solution was to drop the fs.readFileSync method and use a read stream instead. This accepts an option to set the cursor position manually.
And that was that! Sorry for the long wait.


Trying to get transparent background

I try to get transparent background; that is the background shine through the pane it is added to. Let's say I want to switch themes in my app... can you tell me how I do it, if not - add support for it?

I can not set background color when terminal is active at least?

Sorry, close this, it worked!