Documentation Request: Using APIs not in the discovery service

It would be great if there was a bit of documentation on how to use API endpoints that are now exposed in the discovery mechanism like various maps services.
I just discovered https://github.com/google/google-api-php-client/issues/855 and I wonder if there is more I need to care about than just authorizing the client with the key and executing the call.

This has been added to the README! See Making HTTP Requests Directly

Great, thx!


Center hero image and adjust media query

Will need a higher res image here.

Totally agreed. We did have a suggestion in PR #313 but would rather we wait to hear a consensus before merging that one. Thanks for the fix in the meantime!

Yeah, I actually love the image... a bit more than the one from PR #313 even, just if we could find a higher res version of it.

K let's try this on staging. Thanks again, @likedaang!


ref(Dockerfile): remove WORKFLOW_RELEASE

This environment variable is not necessary any more.
refs deis/workflow#356

[Current coverage][cc-pull] is 41.71%

Merging [#378][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.09%

@@             master       #378   diff @@
==========================================
  Files            24         24
  Lines          1105       1105
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits            462        461     -1
- Misses          620        621     +1
  Partials         23         23

Powered by Codecov. Last updated by [a230d05...d9cc048][cc-compare]
[cc-base-branch]: https://codecov.io/gh/deis/builder/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/deis/builder/compare/a230d0513fe622c88aa6daf0ebe5ab695e955468...d9cc048c58fc62bfb967e86791b82058b503e2e2
[cc-pull]: https://codecov.io/gh/deis/builder/pull/378?src=pr


Fix ipykernel error in _plan_and_act of Role.

Fix ipykernel error in _plan_and_act of Role: If you create a lot of ExecuteNbCode instance objects without closing it, you will face the following error:
Traceback (most recent call last):
File "/anaconda3/lib/python3.9/runpy.py", line 197, in _run_module_as_main
File "/opt/anaconda3/lib/python3.9/runpy.py", line 87, in _run_code
File "/opt/anaconda3/lib/python3.9/site-packages/ipykernel_launcher.py", line 17, in
File "/opt/anaconda3/lib/python3.9/site-packages/traitlets/config/application.py", line 991, in launch_instance
File "/opt/anaconda3/lib/python3.9/site-packages/traitlets/config/application.py", line 113, in inner
File "/opt/anaconda3/lib/python3.9/site-packages/ipykernel/kernelapp.py", line 692, in initialize
File "/opt/anaconda3/lib/python3.9/site-packages/ipykernel/kernelapp.py", line 329, in init_sockets
File "/opt/anaconda3/lib/python3.9/site-packages/zmq/sugar/context.py", line 362, in socket
File "/opt/anaconda3/lib/python3.9/site-packages/zmq/sugar/socket.py", line 159, in init
File "zmq/backend/cython/socket.pyx", line 332, in zmq.backend.cython.socket.Socket.init
zmq.error.ZMQError: Too many open files in system
Finally, the error Fatal Python error: _Py_HashRandomization_Init: failed to get random numbers to initialize Python Python runtime state: preinitialized [IPKernelApp] WARNING | Parent appears to have exited, shutting down. may be found.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 81.19%. Comparing base (bcf5f05) to head (1e04e34).
Report is 16 commits behind head on code_interpreter.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@                 Coverage Diff                  @@
##           code_interpreter     #977      +/-   ##
====================================================
- Coverage             81.19%   81.19%   -0.01%
====================================================
  Files                   226      226
  Lines                 12478    12481       +3
====================================================
+ Hits                  10132    10134       +2
- Misses                 2346     2347       +1

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

LGTM


[iOS] [WebView] Error opening local video media (uri starting by file://)

Issue Description
I'm trying to open a local video media in WebView, it's working as i see the video with the play button but after 0,5s i get an error "WebKitErrorDomain , Plug-in handled load" . Seems that somehow webview doesn't allow to open things from file://.
Full error log:
{
  canGoBack:false,
  canGoForward:false,
  code:204,
  description:"Plug-in handled load",
  domain:"WebKitErrorDomain",
  loading:false,
  target:155,
  title:"",
  url:"file:///Users/tdurand/Library/Developer/CoreSimulator/Devices/E2D725EC-A972-4BAC-8309-2D8A13535FAA/data/Containers/Data/Application/54A5EDAB-F950-4D7D-8995-3BD5755AF52F/tmp/trim.CF765039-D257-4DB8-A9A7-3925D495942F.MOV"
}

You can see that it's successfully reading the file before throwing the error:

Steps to Reproduce / Code Snippets
Just try to open a local video file in webview:
<WebView source={{ uri: "file:///Users/tdurand/Library/Developer/CoreSimulator/Devices/E2D725EC-A972-4BAC-8309-2D8A13535FAA/data/Containers/Data/Application/54A5EDAB-F950-4D7D-8995-3BD5755AF52F/tmp/trim.CF765039-D257-4DB8-A9A7-3925D495942F.MOV" }}
                  style={{height: 150 ,width: 150}}
                />

Expected Results
Do not have the error thrown an being able to play the video.
Additional Information

React Native version: 0.34.1
Platform(s) (iOS, Android, or both?): iOS
Operating System (macOS, Linux, or Windows?): macOS

Did you make any progress on that issue?

@facebook-github-bot icebox

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with Canny! Check out its new home: https://react-native.canny.io/feature-requests/p/ios-webview-error-opening-local-video-media-uri-starting-by-file

I was experiencing this issue (yes, it is still an issue.) and solved it in a somewhat hack-y way.
I src the video in a html5 video tag within the WebView.
<WebView style={{height:200}} source={{html:"<video style=' height:180;width:500;' controls src='VIDEO_LINK_HERE.m3u8'></video>"}} allowsInlineMediaPlayback={true} mediaPlaybackRequiresUserAction={true}}/>

+1 here. Experiencing as well.

Here's a potential fix from another repo that ran into the issue with iOS' UIWebView. Perhaps RN needs this fix too?
https://github.com/brave/browser-ios/commit/e74eed9c11a408af5081477b827b5c05b669a60d


Gradle build fix

Codecov Report

Merging #6 (0a87568) into master (5958965) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #6   +/-   ##
=========================================
  Coverage     98.07%   98.07%
  Complexity       55       55
=========================================
  Files             5        5
  Lines           208      208
  Branches         10       10
=========================================
  Hits            204      204
  Misses            2        2
  Partials          2        2

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 5958965...0a87568. Read the comment docs.


Map UUID in GameMessageS2CPacket

Mojang, why?

Maybe it's for blocking users messages on the client for the future?


Neither CHANGELOG.md nor release notes are present

I'm currently using @wasmer/wasi 0.10 package and was thinking of upgrading to 0.11, but wasn't sure if the new release contained any breaking changes. I also wasn't able to find any changelog or release notes that clarify that. Would you mind adding those, so that it is more clear whether upgrading to the latest version makes sense for a given project?
Thanks.

Sure thing! We'll try to do it for next release

The @wasmer/sdk package now comes with a CHANGELOG.md file you can refer to. We re-implemented this package from scratch in order to support the newer Wasmer API and WASIX, so it won't contain any history from @wasmer/wasi.


Update GitHub landing page to look good!

This is just to make the GitHub page look good! A useful readme with update installation and running instructions, examples of using the tool, etc. Can also create a github site if that works better.

Added basic readme details


fix: navigation bottom sheet

:tada: This PR is included in version 1.14.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fix logback settings

As of right now, our tests are printing a ton of stuff (test and it:test).
These settings are logback related - see https://logback.qos.ch/manual/configuration.html
Right now we have logback files for the api and mysql/it, but not everywhere. If you put them everywhere though, you will get errors that it is finding multiple logback files on the classpath.
In general, need to figure out the right place for these files and put them there. For outcome, I think we want test logging off, and it:test mostly off (error at least, ideally suppress exception stack traces though)

closed with #303


CORS

Hi, i've been trying to run Cerberus with CORS activated. But seemingly there is nothing i can do to enable the Cross Domain. All the requests are being blocked.
Any Clue? =\

What errors are you getting? I've added a CORS filter enabled which should allow everything you would need.

It's working with the api/auth
But when i try to use the obtained token to api/protected, i get the following server error:
Browser:
Failed to load resource: the server responded with a status of 401 (Unauthorized)
(index):1 XMLHttpRequest cannot load http://<IP_ADDRESS>:8080/api/protected. Response for preflight has invalid HTTP status code 401
Server message:
2015-12-11 18:12:32.874 DEBUG 6934 --- [nio-8080-exec-1] o.s.web.servlet.DispatcherServlet        : DispatcherServlet with name 'dispatcherServlet' processing OPTIONS request for [/api/error]
2015-12-11 18:12:32.883 DEBUG 6934 --- [nio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Looking up handler method for path /error
2015-12-11 18:12:32.884 DEBUG 6934 --- [nio-8080-exec-1] s.w.s.m.m.a.RequestMappingHandlerMapping : Returning handler method [public void org.springframework.web.servlet.handler.AbstractHandlerMethodMapping$EmptyHandler.handle()]
2015-12-11 18:12:32.886 DEBUG 6934 --- [nio-8080-exec-1] o.s.web.servlet.DispatcherServlet        : Null ModelAndView returned to DispatcherServlet with name 'dispatcherServlet': assuming HandlerAdapter completed request handling
2015-12-11 18:12:32.886 DEBUG 6934 --- [nio-8080-exec-1] o.s.web.servlet.DispatcherServlet        : Successfully completed request

@SlySurfer This should be fixed now.


Business central Advanced settings UI

Summary by CodeRabbit

New Features

Introduced new configuration options for automation and customization in the Business Central advanced settings.
Enhanced the user interface for the Business Central advanced settings to reflect new features.

Improvements

Updated the loading behavior to improve user experience during data retrieval.
Improved the display of additional conditions in the Configuration Skip Export component.

Style Updates

Added new styles for .preview-text and .preview-box to enhance visual presentation.

Bug Fixes

Fixed an issue where the isLoading flag was incorrectly set, affecting the display of loading states.

@coderabbitai review


Added MasonryFlashList which adds support for rendering masonry layouts

Description
resolves #455
resolves #575
resolves #589
This PR adds support for Masonry layout rendering also referred to as Staggered Grid View layout.
It's implemented using core FlashList and I didn't plan to make it part of this repo (initially) because it's technically like a derivative. I changed my mind because at the end of the day masonry is a layout and how it's implemented shouldn't matter. Ideally, anything that can be built using FlashList can be kept out. Keeping it lean is a win and should keep the core quality high.
I took the liberty to fix two additional bugs I found while building this otherwise there's no change in core. I've added comments to those changes.
Why use this approach?
It can be implemented using nested lists without any drawbacks and also doesn't require a new layout algorithm on the native side. It's incredibly fast as well.
Performance
It's incredibly well performing. Compared to 2x2 non masonry this is just 2% slower which may very well be a measurement problem.
Known issue
There's a prop type warning being thrown by RLV which I'll address when we upgrade RLV the next time.
Reviewers’ hat-rack :tophat:

[ ] Open fixture and try the masonry sample

Screenshots or videos (if needed)

Checklist

[x] I have added a changelog entry following the Keep a Changelog guidelines.

This looks really good 👏
I have a couple of comments and questions but overall, I love the idea of having multiple FlashLists ❤
Additionally, I got this warning when running the Masonry example:

This requires a proptype fix in RLV. I'll get to it later

How are the odds this will be merged?

@fortmarek this is good to go IMO. Thoughts?

I have only a couple of minor comments, mostly about the documentation.
Additionally, as mentioned here, for now I'd mark this component as unstable or alpha before we are more confident in the stability of this feature.

@fortmarek Addressed the comments! Thanks for the review again.
Regarding stability, it's very stable and ready for prime time. I don't see a need for marking it alpha or beta. The warning that you see is a proptype warning and doesn't impact stability in any way.

This looks really good 👏
I have a couple of comments and questions but overall, I love the idea of having multiple FlashLists ❤
Additionally, I got this warning when running the Masonry example:

This requires a proptype fix in RLV. I'll get to it later

any update on this?
i am still getting this warning.

It should be fixed in v1.4.0

Does overrideItemLayout not work with Masonry layout? If so, is that documented anywhere? We can't get overrideItemLayout working at all.

Can you flag an issue for this, please? 🙏 I'm personally not aware that Masonry layout doesn't support overrideItemLayout.

Does overrideItemLayout not work with Masonry layout? If so, is that documented anywhere? We can't get overrideItemLayout working at all.

Can you flag an issue for this, please? 🙏 I'm personally not aware that Masonry layout doesn't support overrideItemLayout.

Yes, it's not possible to change spans in masonry. We'd appreciate a PR updating the docs!

That's terribly upsetting to hear! We just did hours of work to implement MasonryFlashList. Isn't there some way to allow overrideItemLayout - even if it's imperfect? I'd much rather that to having to roll back hours of work - considering FlashList appears to be the future and I'm confident a good/proper solution will exist in the future even if it doesn't today.
Any chance to simply patch masonry to accept overrideItemLayout?

@naqvitalha if this is treated as a docs-only issue - at minimum these pages need updating:

https://shopify.github.io/flash-list/docs/guides/section-list

"but all of them are replaceable with existing props."
renderSectionHeader doesn't seem to work with masonry
Surely other properties are misleadingly treated as though they would work with masonry

https://shopify.github.io/flash-list/docs/guides/masonry


Release Flatcar Container Linux Alpha 3745.0.0, Beta 3732.1.0, Stable 3602.2.0, LTS 3510.3.0

The release of the following Flatcar Container Linux version is planning October 4th, 2023.

Alpha 3745.0.0
Beta 3732.1.0
Stable 3602.2.0
LTS 3510.3.0

1. Preparation
Owner: @dongsupark

[x] A. Go/No-Go hackmd doc created from HackMD template for test tracking and release notes: (https://hackmd.io/XnuvS255RVyq0VgVboxxVw?view)
[x] B. All planned changes are merged & blocker bugs are fixed, last nightly reviewed for problems.
[x] C. Check that the kernel PR are merged for the channel(s) to be released.

2. Build
Owner: @dongsupark

[x] A. Branched off the main branch (only for new major).
[x] B. Tagged all the build branches.
[ ] C. Started the Jenkins builds, post the links into this issue as comment.

3. Release
i. The Go/No-Go Meeting
Owner:

[ ] A. Test status captured in the HackMD document.
[ ] B. All tests are Green.
[ ] C. Release notes / announcements added to Go/No Go doc from container/image_changes job by selecting Timestamps: None.
[ ] D. QA: Checked the diff for image file list, packages, and image size in the container/image_changes job output.
[ ] E. Conduct Matrix Go/No Go meeting (inc. release notes review).

ii. Artifacts goes public
Owner:

[ ] A. Created the Release Notes on the scripts repo for the respective tags on GitHub as GitHub Releases.
[ ] B. Ran the container/release Release job.
[ ] C. Images uploaded with copy-to-origin.sh.
[ ] D. Symlink to "current" updated with set-symlink.sh.
[ ] E. Website updated with ./update-flatcar-versions.sh and PR merged.

iii. Payload
Owner:

[ ] A. Update payload signed/uploaded.
[ ] B. Release package published in Nebraska (Prerequisite: 3.ii.E should marked done).

iv. Cloud Marketplace & Cluster API
Owner:

A. Azure

[ ] Offers updated and started publishing.
[ ] Sent the offers to publish to Live.

B. GCP

[ ] Offer deployment package uploaded to Google Bucket & submit for verification.
[ ] Offer Publish

C. Cluster API for new Stable

[ ] Azure: Manually run ./azure-sig.sh to create New Shared Community Gallery Images
[ ] OpenStack: documentation

4. Announcements
Owner:

[ ] A. Sent announcement to Mailing Lists
[ ] B. Sent Tweet out to Twitter, and Toot out to Mastodon
[ ] C. Brief version announcement in slack (k8s slack #flatcar) and the Flatcar Matrix channel

Alpha 3745.0.0 - http://jenkins.infra.kinvolk.io:8080/job/container/job/sdk/1090/cldsv/
Beta 3732.1.0 - http://jenkins.infra.kinvolk.io:8080/job/container/job/packages_all_arches/2647/cldsv/
Stable 3602.2.0 - http://jenkins.infra.kinvolk.io:8080/job/container/job/packages_all_arches/2646/cldsv/
LTS 3510.3.0 - http://jenkins.infra.kinvolk.io:8080/job/container/job/packages_all_arches/2645/cldsv/

@dongsupark
Looks like these versions are missing for Azure
Querying the image of 'kinvolk:flatcar-container-linux-free:stable-gen2:3602.2.0' failed for an error '(NotFound) Artifact: VMImage was not found.
Code: NotFound
Message: Artifact: VMImage was not found.'. Configuring plan settings will be skipped
Querying the image of 'kinvolk:flatcar-container-linux-free:stable-gen2:3602.2.0' failed for an error '(NotFound) Artifact: VMImage was not found.
Code: NotFound
Message: Artifact: VMImage was not found.'. Configuring plan settings will be skipped
(NotFound) Artifact: VMImage was not found.
Code: NotFound
Message: Artifact: VMImage was not found.


⚠ Carbubu has degraded performance

In 0f7c350, Carbubu (https://carbubu.fr) experienced degraded performance:

HTTP code: 200
Response time: 5674 ms

Resolved: Carbubu performance has improved in ce24018 after 6 minutes.


added select distinct entry to persist in flatedge tables.

This cater for persisting in flatedge tables when sess_flatedge have duplicate entry (see DSCS-2436, service ticket #2016111710000122 ).

@jrixon @scoen @ninhnguyen could you please review this change?  Thanks.

Looks good! Good solution 😄 😄 😄


plain_text_input in Messages, how to get content?

Hi there, I'm trying to use the plain_text_input block in messages (not a modal)
input_block = {
        "type": "input",
        "element": {
            "type": "plain_text_input",
            "multiline": True,
            "action_id": f"{fn_name}",
            "initial_value": f"{initial_value}",
        },
        "label": {"type": "plain_text", "text": f"{label_text}", "emoji": True},
    }

I'm able to get a text input box to appear. But I can't find any guides on how to handle that user input.
Any suggestions? Thank you.

Namely, after a user writes some input. How do I retrieve that input?

I found that the dispatch_action_config param, but upon pressing "enter," nothing happens

Hi @chengyjonathan, thanks for asking the question! Could you double-check if you've configured Request URL for Interactivity & Shortcuts section in the app configuration page? If you're using Socket Mode, just enabling the Interactivity feature should work for you.

Yes, I have. Other modes of interactivity work. (ie. buttons, etc)

I essentially have the following setup
input_block = {
        "type": "input",
        "element": {
            "type": "plain_text_input",
            "multiline": True,
            "max_length": 500,
            "action_id": f"{fn_name}",
            "placeholder": f"{initial_value}",
            "dispatch_action_config": {"trigger_actions_on": ["on_enter_pressed"]},
        },
        "label": {"type": "plain_text", "text": f"{label_text}", "emoji": True},
    }

@slack_app.action("fn_name")
def fn_name(ack, say, payload):
    ack()
    print(payload)

This produces the text box for input, but I can't find the documentation that would receive/handle any input text by the user.
Note: I'm not using a modal, just using Messages

I'm not sure if this is the right way to implement handling plain_text_input.
And I cannot find the right documentation anywhere. (Most of it pertains to Modals)
Any help is greatly appreciated

@chengyjonathan

@chengyjonathan Your code does not have "dispatch_action": True in the block, and that is the cause of its misbehavior. The following code works for me.
@app.event("app_mention")
def handle_app_mentions(say):
    say(
        {
            "text": "Testing dispatch_action_config",
            "blocks": [
                {
                    "type": "input",
                    "dispatch_action": True,
                    "label": {"type": "plain_text", "text": "Label"},
                    "element": {
                        "type": "plain_text_input",
                        "multiline": True,
                        "max_length": 500,
                        "action_id": "some_action_id",
                        "dispatch_action_config": {
                            "trigger_actions_on": [
                                "on_enter_pressed",
                            ]
                        },
                    },
                }
            ],
        }
    )

@app.action("some_action_id")
def handle_action(body, ack, logger):
    logger.info(body)
    ack()

Oh I see! Thank you.
I'll try that today and close this if it works.
One followup question. Is there a way to send additional metadata to the handle_action fn?
I've done this for buttons by packing stuff in the "value" field. But idk if there's a way to do this for plain_text_inputs as well.
Thank you, again!

Alternatively, is there a way to pair plain_text_inputs with a submit button where, I can pass that value field?


Update user-defined-function-mapping.md

solves #3729

relative comment: https://github.com/dotnet/efcore/issues/23408#issuecomment-1031877250
#23408


Referencing documents, parts of documents, bibliographic entries, etc.

This is related to #243
We are currently using a variety of reference systems. For instance:
<p n="3" corresp="#siksaguru_01.03"> (points to <p xml:id="siksaguru_01.03"> in another file)
<change who="part:axja" ...>
<persName ref="http://viaf.org/viaf/39382787">
<licence target="https://creativecommons.org/licenses/by/4.0/">
<ref>DHARMA_IdListMembers_v01.xml</ref>
<ref target="DHARMA_INSCIK00288.xml">
<idno type="filename">DHARMA_INSCIK00803</idno>
<rdg source="bib:Coedes1942_02">

The use of corresp="#siksaguru_01.03" for referencing an @xml:id in another
document is problematic. An @xml:id is supposed to be unique within a single
document, not at the scope of a full document collection. A typical address for
part of a document is DHARMA_INSHello#location, where DHARMA_INSHello is
the file name and location is an @xml:id. When referencing something in
the same document, the filename is not necessary, #location suffices.
We can choose not to follow XML conventions, but in any case, we
must have a referencing scheme that clearly distinguishes the file name and the
location of the target element within this file. Otherwise, I basically have to
process all the files in the collection to figure out where the @xml:id lies,
instead of processing a single file.
Secondly, we need to be careful to avoid name clashes in references. For
instance, we cannot have both DHARMA_INSHello_1.2.3 for referencing a
@n=1.2.3 and DHARMA_INSHello_location for referencing an
@xml:id=location, because it is not possible to tell from the reference
itself whether it refers to a @n or to an @xml:id.

I do not really understand what you are saying here. I have no knowledge of how @corresp is used in the project to point to specific locations in specific files, nor of how @xml:id is used for such a purpose, or of what considerations went into these practices. I do know that it was Axelle who insisted on making all of our @xml:id-s unique through the entire corpus by including the filename within those IDs; I never understood why this was important.
Now that you point out the problem of having always to process all files when looking for a specific ID, I understand why this is a problem, and understood all the less why Axelle thought it was a good idea. If the PIs agree that we should change to the regular convention and make IDs unique only within each document, then refer to them using #location for internal and filename#location for external references, then I think it should be possible to auto-update our existing IDs thanks to the rigorous file naming conventions in use. I may be wrong here, but I think it should be possible to do this:

In each file, in any instances of an @xml:id, occurrences of the current file's name plus a trailing underscore would be simply deleted. Thus, within the file DHARMA_INSHello, @xml:id="DHARMA_INSHello_1" would become @xml:id="1". At the same time, remaining instances of @xml:id containing an underscore might be flagged for human attention, but this may not be necessary.
Next, in all files, in instances of attributes referencing an xml:id (but not in @xml:id attributes themselves), any occurrences of any DHARMA filename (regex mask on the basis of the file naming conventions) plus a trailing underscore would be replaced to the same filename followed by a hash mark instead of the trailing underscore, so that within all files, @corresp="DHARMA_INSHello_1" would become @corresp="#1" and @corresp="DHARMA_INSBye_1" would become @corresp="DHARMA_INSBye#1".

If it is not possible to write failsafe regex masks for all DHARMA filenames, then this might also be done using a list of actual existing DHARMA filenames.
All this of course would have to be synchronised with a change in the practice of all encoders who use such references, which would not be easy.
And at any rate @arlogriffiths at least will certainly have to be involved more deeply in any problems related to encoding practices found only in the EGC and not in the EGD.
I'm not sure if you have any particular problem with the other kinds of reference you list. As far as I can see, the following
<persName ref="http://viaf.org/viaf/39382787">
<licence target="https://creativecommons.org/licenses/by/4.0/">
<ref>DHARMA_IdListMembers_v01.xml</ref>
<idno type="filename">DHARMA_INSCIK00803</idno>

should not be problematic, or if they are, then they should be straightforward to change to whatever arrangement you think is preferable.
Next, the following
<rdg source="bib:Coedes1942_02">
<change who="part:axja" ...>

have, I think, been implemented carefully and work as expected. If they cause any conflicts or problems, then (apart from problems with referring to the Zotero database) these should be possible to correct globally.
Finally, to <ref target="DHARMA_INSCIK00288.xml"> I should add the type <ref n="tfa-pallava-epigraphy" target="Pallava00001.xml"> where @n has been coopted to identify the repository for files located in a different repository than the one from which the reference is being made. If any of these referencing systems are problematic, then we'll need to know more about the problems and the proposed solutions.


allow permissive SA secret ref limitting

Allows the SA pod admission controller to limit secret references, but lets an individual service account carry an annotation that indicates that a pod using this service account should be able to reference any secret.  This also extends the SA controller to allow a managed SA to be created with annotations already present.
Related to https://github.com/GoogleCloudPlatform/kubernetes/issues/11070
@liggitt @erictune

@smarterclayton this affects the utility of secrets in generic Lists

Also needed to run e2es that use secrets against OpenShift
On Monday, July 27, 2015, David Eads<EMAIL_ADDRESS>wrote:

@smarterclayton https://github.com/smarterclayton this affects the
utility of secrets in generic Lists
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/11827#issuecomment-125275376
.

It's relevant to secrets in lists, but not sufficient for an author to confidently use them in lists (doing so assumes the service account is permissive, which probably isn't a great assumption)

David and I suggested making SAs permissive by default today.  Part of the
reason is that the primary use case for secrets is to enable offloading,
while the primary reason for SA strict checks was to enable isolation if
the author desires.
Right now, all users are getting the downsides of the latter, but only a
few users would benefit from the latter.  If users are disencetivized to
use secrets, that hurts both use cases (no way to make the check strict if
the user decided on ENV vars).
I think strict checks should be opt in for all SA.
On Jul 27, 2015, at 5:36 PM, Jordan Liggitt<EMAIL_ADDRESS>wrote:
It's relevant to secrets in lists, but not sufficient for an author to
confidently use them in lists (doing so assumes the service account is
permissive, which probably isn't a great assumption)
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/11827#issuecomment-125347461
.

Sure, I'm just leery of accumulating a large catalog of templates that assume permissive service accounts, which will not work if someone wants to isolate. I suppose if someone wants to do that, they're less likely to be running templates from the wild.

Trying to think of alternatives - an endpoint that takes a secret + an SA
name to bind the secret to the SA might be a little more secure.  Then you
at least guarantee the template doesn't get to see the secret with the
given name.  Proof of ownership.  But it does mean that you have to hard
code a service account name.
I admit, I worry some about a fishing image (mount all of these secrets and
send them to black hats!) but you can in theory fish for service account
tokens as well for any SA with a given name.
The trade off is convenience and security - what would client tools do to
ease the burden?  Ask you to confirm adding a secret?  As you to confirm
using a SA?  Force you to define your own SA if you want to use a secret?
Couldn't a user just add a role binding (in Openshift) to give the SA
permission to read secrets?
On Jul 27, 2015, at 6:14 PM, Jordan Liggitt<EMAIL_ADDRESS>wrote:
Sure, I'm just leery of accumulating a large catalog of templates that
assume permissive service accounts, which will not work if someone wants to
isolate. I suppose if someone wants to do that, they're less likely to be
running templates from the wild.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/11827#issuecomment-125362581
.

Check reversed.  Now an individual service account can indicate whether it wants to have the mountable secret references enforced even if the the default is non-enforcement.

Asked some questions on #11070.

I need to spend some more time parsing comments in #11070 before I can review this properly.

I'm on vacation this week (:house: :mouse:) and will take a look next week.

@deads2k ping, this patch is carried over in our Godeps, can you please move this forward, pretty, pretty please :)

LGTM.


Panic occured at runtime - Migration form CRA

System Info
System:
OS: Windows 10 10.0.19045
CPU: (16) x64 AMD Ryzen 7 PRO 6850U with Radeon Graphics
Memory: 12.01 GB / 31.31 GB
Binaries:
Node: 18.19.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
npm: 10.2.3 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: Chromium (120.0.2210.121)
Details
Following the guide on rsbuild.dev migrating from an existing MF CRA (not ejected) app to rsbuild. Got this error in the terminal when running rsbuild dev - It told me to create an issue here
Message:  should have dependency id, failed at C:\source\analytics\heat
Location: crates\rspack_plugin_javascript\src\dependency\context\common_js_require_context_dependency.rs:101

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 1: napi_register_module_v1
    at <unknown source file>
 2: napi_register_module_v1
    at <unknown source file>
 3: napi_register_module_v1
    at <unknown source file>
 4: napi_register_module_v1
    at <unknown source file>
 5: napi_register_module_v1
    at <unknown source file>
 6: napi_register_module_v1
    at <unknown source file>
 7: napi_register_module_v1
    at <unknown source file>
 8: BaseThreadInitThunk
    at <unknown source file>
 9: RtlUserThreadStart
    at <unknown source file>
error Command failed with exit code<PHONE_NUMBER>.

Using:
"@rsbuild/core": "^0.3.1",
"@rsbuild/plugin-react": "^0.3.1",
rsbuild.config.ts:
import { defineConfig, loadEnv } from "@rsbuild/core";
import { pluginReact } from "@rsbuild/plugin-react";
import rspack from "@rspack/core";
import mfConfig from "./modulefederation.config";

const { publicVars } = loadEnv({ prefixes: ["REACT_APP_"] });

export default defineConfig({
  html: {
    template: "./public/index.html"
  },
  source: {
    define: publicVars,
    entry: {
      index: "./src/index.js"
    }
  },
  dev: {
    assetPrefix: "/heat/",
    startUrl: "http://localhost:3000/heat"
  },
  server: {
    port: 3000
  },
  output: {
    distPath: {
      root: "build"
    },
    assetPrefix: "/heat/",
    sourceMap: {
      js:
        process.env.NODE_ENV === "production"
          ? // Use a high quality source map format for production
            "source-map"
          : // Use a more performant source map format for development
            "cheap-module-source-map"
    }
  },
  tools: {
    rspack: {
      plugins: [new rspack.container.ModuleFederationPlugin(mfConfig)],
      module: {
        rules: [
          {
            test: /\.pdf$/,
            // converts asset to a separate file and exports the URL address.
            type: "asset/resource"
          }
        ]
      }
    }
  },
  plugins: [pluginReact()]
});

modulefederation.config.js:
const env = process.env.NODE_ENV ? process.env.NODE_ENV : "development";
require("dotenv").config({ path: __dirname + `/.env.${env}` });
const { dependencies } = require("./package.json");

// Use the REMOTE_DOMAIN variable in urls to enable dev/test/prod deployment.
const REMOTE_DOMAIN =
  process.env.REMOTE_DOMAIN ||
  (() => {
    throw new Error("REACT_APP_REMOTE_DOMAIN environmental variable not set");
  })();

module.exports = {
  name: "heat",
  filename: "remoteEntry.js",
  remotes: {
    "@remotes/coreState": <EMAIL_ADDRESS>    "@remotes/coreAuth": <EMAIL_ADDRESS>    "@remotes/DLTA": <EMAIL_ADDRESS>  },
  exposes: {
    "./moduleIntegration": "./src/exposes/moduleIntegration"
  },
  shared: {
    ...dependencies,
    "@kamstrup/kfl": {
      singleton: true
    },
    "@emotion/react": {
      singleton: true,
      requiredVersion: "auto"
    },
    "react-router-dom": {
      singleton: true,
      requiredVersion: dependencies["react-router-dom"]
    },
    react: {
      eager: true,
      singleton: true,
      requiredVersion: dependencies["react"]
    },
    "react-dom": {
      eager: true,
      singleton: true,
      requiredVersion: dependencies["react-dom"]
    }
  }
};

Reproduce link
No response
Reproduce Steps
Install @rsbuild/core & @rsbuild/plugin-react
run yarn rsbuild dev

Could you provide a minimal reproduction?

I cannot create a repo to reproduce since it's happening in a prod app at my company but I did boil it down to the failure happening in an internal npm-package handling INTL.
When doing this inline require inside an NPM-package, so basically from node_modules in the failing application
return (
    <TranslationContext.Provider
      value={{
        translateText,
        translateDate,
        translateNumber,
        isLanguage,
        locale
      }}
    >
      <IntlProvider
        locale={lang}
        timeZone={timeZone}
        messages={require(`/src/i18n/${languagePath}/${translationsFileName}.json`)}
      >
        <IntlSetter setIntl={setIntl} />
        {intl ? children : null}
      </IntlProvider>
    </TranslationContext.Provider>
  );

Then it fails. We've later upgraded this package to handle this differently so the messages are passed as a prop to this npm-package component instead of letting the Provider handle it.
This is how it was used in the failing app
 <TranslationsProvider
      supportedLocales={supportedLanguages}
      ranslationsFileName="translations"
 >
     <AuthenticationProvider>
         <App />
      </AuthenticationProvider>
</TranslationsProvider>

Could you change require(/src/i18n/${languagePath}/${translationsFileName}.json) to a relative path and see whether the problem still exists?

If still exists then I can't help more without a minimal reproduction, I suggest try to extract this into a separate demo.

Good to hear


Cannot control smartir using Alexa

Please help me with turning this component on using Alexa:
I have set up an entity called climate.living_room_ac using the smartir component.
The entity works correctly and I can control it using the Home Assistant front end - turning it on, off, changing temperature etc.
I have exposed the entity climate.living_room_ac to Alexa using the emulated hue component.
I CAN change the temperature of the entity climate.living_room_ac using Alexa commands (either via the alexa app on my mobile or voice). The temperature indicator on the front end changes to the new value but the state remains “off”.
I CANNOT turn the entity on using Alexa.
I have used both the broadlink platform (using base64 codes) and the xiaomi platform (using raw codes).

I don't think it will work with that emulated hue component. Please try the cloud component.

Thanks.
I managed to connect using Node Red instead.


Add clock for synchronous circuits

We need to implement the clock that can be operated on the chosen frequency. This will be useful in many other modules.

Yes, this seems really useful. If you want I can assign this issue to you

I would have fixed it already instead of creating this issue 😅. I would need to understand more of your codebase to implement this I think.

Well, I won't pressure you xD
If you want to dig deeper and implement it, go ahead and ask me if you have any questions :)

Also, it would be nice if you could add some things to contributing.md about how your project simulates the components, like how the updating of circuit is handled or maybe some other things that should be known to change the project's core.


Add library guide for table provider and catalog providers

Which issue does this PR close?
~Closes #~ Related to #7014
This won't finish #7014, but adds the skeleton described in that issue as well as content for the custom table provider and catalog. I can also add some info on Scalar UDFs, but am not sure I know enough about the others to write something w/o a summary to expand on.
Hope this is what you'all are looking for, certainly open to feedback.
Finally, I'm getting some unrelated (I think) warnings, are these known?
/Users/thauck/personal/code/github.com/tshauck/arrow-datafusion/docs/temp/user-guide/example-usage.md:24: WARNING: 'myst' cross-reference target not found: '../../../datafusion-examples' [myst.xref_missing]
/Users/thauck/personal/code/github.com/tshauck/arrow-datafusion/docs/temp/user-guide/example-usage.md:211: WARNING: Pygments lexer name 'rust,ignore' is not known
/Users/thauck/personal/code/github.com/tshauck/arrow-datafusion/docs/temp/user-guide/sql/data_types.md:31: WARNING: Could not lex literal_block '❯ select arrow_typeof(interval \'1 month\');\n+-------------------------------------+\n| arrowtypeof(IntervalYearMonth("1")) |\n+-------------------------------------+\n| Interval(YearMonth)                 |\n+-------------------------------------+\n' as "sql". Highlighting skipped.
...

Rationale for this change
It was requested in #7014. I also would've found this useful for exon.
Are these changes tested?
I locally generated the docs, per the README. Ex..

Are there any user-facing changes?
Yes, this would update the docs users could read.

I think the current failure is related to https://github.com/apache/arrow-datafusion/pull/7286... I'll rebase and relook when it's merged.

Thank you @tshauck  -- I will review this later today

Thanks for all the feedback! I'll work through it later this evening and follow up on anything.

Thanks for the review, I think I got to the feedback. I can try to do the UDF page, but I don't have enough experience with the other areas to provide good info (though I'd like to read the one on using exprs 😄 ).

Great work -- thanks again @tshauck  -- I will file some additional tickets for the "Coming Soon" sections as well


Not setting threshold energy

When photon energy is changed in GDA the threshold is set to half this value. This doesn't seem to happen in Artemis

It would be good to find where this is being done in GDA, I couldn't work it out

EPICS logs show this is never set and we couldn't find anything in GDA for it so we think it's in the hardware. Test on the beamline that setting the photon energy sets threshold, could be that this is done on arm?

This does happen in the firmware, we don't need to worry about it


Override zinc compile analysis for source changes

Zinc records all of the compile source file hashes when compilation
completes. This is problematic because its possible that a source file
was changed while compilation was occurred. From the user perspective,
this may mean that their source change will not be recompiled even if a
build is triggered by the change.
To overcome this, I add logic in the sbt provided external hooks to
override the zinc analysis stamps. This is done by writing the source
file stamps to the previous cache after compilation completes. This
allows us to see the source differences from sbt's perspective, rather
than zinc's perspective. We then merge the combined differences in the
actual implementation of ExternalHooks. In some cases this may result in
over-compilation but generally over-compilation is preferred to under
compilation. Most of the time, the results should be the same.
The scripted test that I added modifies a file during compilation by
invoking a macro. It then effectively asserts that the file is
recompiled during the next test run by validating the compilation result
in the test. The test fails on the latest develop hash.

Works around https://github.com/sbt/zinc/issues/683.


Other Session Problem?

i fresh installation to test the new version...
and i cant register accout... and you can logging with an inexistent accounts.
(i cleared the browser.)
all database has been installed without problems.

Hi Katia. There is indeed an issue with session handler. I'm still working in a better solution.

@KatiaSishost , I just made a little change on auth logic. Can you give it a try and share your results?

@KatiaSishost , I just made a little change on auth logic. Can you give it a try and share your results?

Hello Canove! whats up!?
im trying with a fresh instalation... and when try login or register... it only refresh the page and not create user and no login... i will try to new fresh instalation again.

Do you mind sharing your chrome console when trying to create an account?

 You are able to login, logout and create users?

Entonces, ¿al final funciona? ¿Puede iniciar sesión, cerrar sesión y crear usuarios?

Yes... it work perfect.


Massive updates

All tested, working fine.
The only potential conflict that has not been tested is Ethornell/ImageBGI in feat: MAGES PS3/PSV Image Format decoding
One conflict with https://github.com/morkt/GARbro/pull/610 (Still not merged, I will close it after this pr completed)

Thank you very much ;D


use concurrent_queue generate cpu 100%

hi , I use concurrent_queue generate cpu 100% , and then I try to solve by add micro queue size from 8 to 32 ,then run well at online server , but yesterday we do stress Test , the problem happen again .
I want to try  reduce "push"  frequency  by thread local queue ,but the item order is error .
What can I do ,about this .
my machine have 16 core , launch 64 thread do push ,  and concurrent_queue`s  inner queue  change to 32
what can i do about this .
thanks
Looking forward to your reply.

Could you describe the desired behavior, please? As I understand, the algorithm performs multiple pushes from multiple threads. Since the queue has "unlimited" size, the threads will continue perform the push operation until they have something to push. Therefore, 100% utilization is expected in that case.

Could you describe the desired behavior, please? As I understand, the algorithm performs multiple pushes from multiple threads. Since the queue has "unlimited" size, the threads will continue perform the push operation until they have something to push. Therefore, 100% utilization is expected in that case.

Yes , has many thread do push operation , but too many thread block in spin lock, because they should wait theirs ticket , so when many thread trap in  the spin lock , cpu will 100% .
now I have to increase the micro queue count  , retard clash .

What type of elements stored inside the concurrent queue? Is it trivial (e.g. int) or something complex (e.g. std::vector)?

it is int*.


Set CanCollide to false for items

Related to https://github.com/space-wizards/RobustToolbox/pull/3259 but doesn't require it.

Maybe try re-running tests with a submodule dependency? I remember adding canCollide: false for #10274 but it shouldn't be there anymore with these changes.


docs: correct Prometheus port

The example monitoring deployment exposes Prometheus on port 9090, so that's what people should port-forward. Docs currently say 9962, but that's a port where prometheus can get metrics from Cilium.
Signed-off-by: Liz Rice<EMAIL_ADDRESS>

We have mutliple reviews covering this and tests are passing. Merging despite missing policy review.


[Feature request] Incorporate inplace parameter in drop() method

I'm a common user of PyRanges. Sometimes, when I work with GFF3 files, I need to discard some specific columns. To do so, I always use PyRanges.drop(drop='column') method.
However, I always need to save the output in a new variable since it doesn't offer a way to drop columns in place. It would be great to be able to drop columns mutating the actual PyRanges, without returning it.
As an example, I really like panda's inplace=True keyword, which modifies the data without returning anything.

You can do
gr = read_gtf(f).drop(col_names)
I'm not a fan of using the inplace argument myself. Less mutability is always better IMO.


Link to pages docs

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 0.00%.  Consider uploading reports for the commit 91a7b40 to get more accurate results

Additional details and impacted files
@@          Coverage Diff          @@
##            main     #13   +/-   ##
=====================================
  Coverage   0.00%   0.00%
=====================================
  Files         26      26
  Lines       1444    1444
=====================================
  Misses      1444    1444

Flag
Coverage Δ

unittests
0.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


MVP: addFriend()

Back end:
Make mutation to add friend
Make resolver to add friend
Front end:
Make mutation in mutation.js to add friend

Back End DONE

still need to do Front End


for asymmetric matrices csgraph laplacian uses in-degree to compute diagonal but documentation says out-degree

http://docs.scipy.org/doc/scipy/reference/generated/scipy.sparse.csgraph.laplacian.html
>>> import numpy as np
>>> from scipy.sparse import csgraph
>>> a = np.arange(4).reshape((2,2))
>>> csgraph.laplacian(a)
array([[ 2, -1],
       [-2,  1]])
>>> a
array([[0, 1],
       [2, 3]])

I think out-degree is more standard (i.e. make rows sum to zero), or at least this is the only way I've seen it written anywhere else.  For example the networkx directed laplacian implementation uses out-degree.  Scikit-learn seems to use laplacians only of symmetric matrices.
This doesn't really look tested in the unit tests.  I would be surprised if switching in/out degree laplacians would cause them to fail, not that I'm suggesting to do that right now.

@argriffing gh-3827 is merged, so can this be closed?


added Tenv.get_overriden_method

As suggested in the discussion https://github.com/facebook/infer/issues/326 this pull request implements
get_overriden_method : Tenv.t -> Procname.java -> Procname.t

to get the method of a superclass that is being overridden by a specific java pname.
I thought of unit test this, but unfortunately I wasn't able to figure out how to create the proper context with OUnit2. Perhaps the easiest way to test this will be integration tests.
Feel free to reject the pull request if unit tests are mandatory (or for any other reason, of course).

Thanks!


Implementation is vulnerable to side channel attacks

Since your implementation uses GF2^8 look up tables, it is vulnerable to side channel attacks on CPU cache.
See https://github.com/ECLab-ITU/Cache-Side-Channel-Attacks/blob/master/AES - HalfKey/Flush%2BReload/Readme.md

This is for some parts a joke but on the other hand, people actually wanting to implement AES should now, that this is a real vulnerability.

Hi @FlorianB-DE. Thanks for bringing the vulnerability to my attention. When I first wrote the GF look-up table I was oblivious that such attack would exist.
As you kinda suggested, I expect nobody to take this code for any serious project. However, as the respo stands, it might be better to add a comment on the code itself - or perhaps a message section in the README.md file - so that future readers are also made aware of the vulnerability introduced by the look-up table approach.
Are you open to do a PR? Otherwise I will add the comments myself on my spare time.
Cheers!


[Scheduled] dart pub upgrade --null-safety

Auto-generated by create-pull-request
See: https://github.com/peter-evans/create-pull-request/blob/master/docs/concepts-guidelines.md#triggering-further-workflow-runs

Codecov Report

Merging #115 (a858190) into main (7b6ea6c) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main     #115   +/-   ##
=======================================
  Coverage   70.35%   70.35%
=======================================
  Files          97       97
  Lines         958      958
=======================================
  Hits          674      674
  Misses        284      284

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Github -> GitHub in header

Just a very nit-picky pet peeve of mine. 😂

Important: Please read all instructions carefully.
Select the appropriate category for what this PR is about
This PR is:

[ ] Adding a new domain
[ ] Updating existing domain size
[ ] Changing domain name
[ ] Removing existing domain from list
[x] Website code changes (512kb.club site)
[ ] Other not listed

Thank you now clue how we missed that


[e2e]: delegator-generic workflow_dispatch main checkout slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/5844421650
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Sun Aug 13 01:01:43 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/5850592618
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Mon Aug 14 01:02:09 UTC 2023
Tests are passing now. Closing this issue.


Issue in blood glucose fluctuation code

https://github.com/clinicalml/gumbel-max-scm/blob/02d6ecebb7ccb306c9757d12555b74ba12e17c2e/sepsisSimDiabetes/MDP.py#L253
Should this be capped at 4 instead of 1? It seems like this randomly sets non-diabetics BG to 'low' sometimes. Is that intentional?

:+1: Collecting this (and any future improvements to the simulator) into the sim-v2 branch.


Support for non-asterisk lists

From @tlempart on July 8, 2015 7:51
Asterisk lists are used to define scenario steps, but sometimes there is a need to use lists for documentation purpose within scenario/specification. It would be great, if you can render non-asterisk lists (http://daringfireball.net/projects/markdown/syntax#list) properly.
Copied from original issue: getgauge/html-report#11

From @Thunderforge on September 22, 2015 19:38
I think that this should be moved to the general gauge project, since HTML is just reporting

Gauge will stick to asterisk for list for now and it wants to keep other symbols available for other implemetations for example https://github.com/getgauge/gauge/issues/805


Fix bugs causing posts to be pushed to Medium incorrectly

@majelbstoat Fixes #17 and #23
Adds a filter for allowed post types array, only allow post by default.
This will safely ignore all the other default post types.

@majelbstoat So, as it turns out, I believe just adding a $allowed_post_types array solves all the things.

I would like to finalise submission to the plugins db today, so I'm going to do up a quick patch that incorporates this change, and adds you to the contributor list, @fjarrett. Thanks!

Covered by #27.


Add an instructions argument to ConcreteBytecode, and validate its value

Also adds validation to Bytecode

I dislke the current code to validate instructions. The validation is delayed when you iterate on instructions. I would prefer to raise an error on .append(123) for example.
An option would be to modify InstrList to inherit from abc.MutableSequence instead of list, and implement the ABC using a private list. setitem() and insert() would validate that added items are instructions.

Ok, updated with those changes.

Aside from the abc.MutableSequence change, which would probably do better as a new PR building on this, is this good to merge?

Aside from the abc.MutableSequence change, which would probably do better as a new PR building on this, is this good to merge?


cmd/go: add better support for v0.YYYYMMDD.HHMMSS versions

What version of Go are you using (go version)?

go version go1.13.4 darwin/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
darwin/amd64
What did you do?
We recently switched to module versions of the form v0.YYYYMMDD.HHMMSS since we only care whether a module is more recent and we already had existing semver tags in the repo. So v0.0.YYYYMMDDHHMMSS would not work.
This works fine until the timestamp starts with a 0 since then the patch version is outside the semver spec. go build then fails but go mod tidy fetches the version but rewrites go.mod to  v0.20191115.124623-0.20191117071016-50581b53fb34. This does not happen after 10:00 obviously.
We can switch to something like v0.99.YYYYMMDD.HHMMSS or v1.0.YYYYMMDDHHMMSS but I'm wondering whether it would make sense to make the semver parser a bit more lenient to allow for this use-case.

I'd be concerned about deviating further from the semver spec. This would create ambiguity when comparing versions (does v1.2.03 come before or after v1.2.3?) and give room for bugs to hide.
Could you use a pre-release suffix for this instead? For example, v0.0.1-YYYYMMDDHHMMSS.

Ah, that's a good point and that would indeed create confusion. We're using v1.0.YYYYMMDDHHMMSS now since these are more recent than the other tags we've created so far and also does not have that problem.
Closing and thank you.


DOC 9065 PR #112644 - cli: add job traces for traceable jobs to the debug zip

Addresses DOC-9065
Updated cockroach debug zip page with --include-running-job-traces flag.

TFTRs!


[CELEBORN-817] PushMergedData should also check disk usage and trigger Split

What changes were proposed in this pull request?
While handling PushMergedData, PushMergedData should also check disk usage and trigger Split, which behavior is consistent with PushData.
Why are the changes needed?
While handling PushMergedData, PushMergedData also invokes checkDiskFullAndSplit to check disk usage and trigger Split.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Internal application tests.

If it's a disk issue, hard split maybe better?

If it's a disk issue, hard split maybe better? cc @waitinfuture

@waitinfuture, WDYT?

IMO we should separate partitionlocations that should trigger revive from those that should not based on their disks status.


Proposal: use renovate to keep dependencies up to date

It looks like many dependencies in this repository are out of date.  We're pretty happily using renovate to auto-submit PRs to help us keep things up to date in the googleapis org.
We'd be happy to help set up a config and get things rolling!

I was looking at an out of date branch 🤦♂


Failed to build installable wheels for some pyproject.toml based projects (gridencoder)

Hello, I had trouble installing gridcoder. When I run pip install. ,then I get the following error:

Did you check your nvcc version?
I had the same issue. My pytorch-cuda version was 11.7 while my nvcc version was 11.3. My fix was updating nvcc to 11.7.

嗯嗯，我后面在服务器上跑了，用的是Ubuntu环境，然后就解决了我的问题，可能是Windows不行？具体原因我没找到，但换了Ubuntu就好了
山岚浮生
@.***

------------------ 原始邮件 ------------------
发件人:                                                                                "ashawkey/torch-ngp"                                                                                @.>;
发送时间: 2024年7月12日(星期五) 晚上10:53
@.>;
<EMAIL_ADDRESS>主题: Re: [ashawkey/torch-ngp] Failed to build installable wheels for some pyproject.toml based projects (gridencoder) (Issue #201)
Did you check your nvcc version?
I had the same issue. My pytorch-cuda version was 11.7 while my nvcc version was 11.3. My fix was updating nvcc to 11.7.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Processing methods in Win10 environment:
Open setup. py
Modify the last set of parameters:
'build_ext': BuildExtension
Change to:
'build_ext': BuildExtension.with_options(use_ninja=False)
For more questions about 3D environment dependencies, please refer to [my blog](url https://blog.csdn.net/fuweipeng2012/article/details/136794036) post


Non-hardwired text style

This is a question of tastes, for sure, but I wouldn't hardwire the font color and size but would use what the platform provides instead, eg:
child: Text(_dialogMessage, style: Theme.of(context).textTheme.subhead),
child: Text("$_progress/100", style: Theme.of(context).textTheme.caption),
child: Text(message, textAlign: TextAlign.center, style: Theme.of(context).textTheme.subhead),

So, you suggest me to use these styles?

Yes. I do. Pick one that you consider nice but don't specify size and color manually. That's my suggestion.

Why not just let it be fully-extensible? The default theme is okay but some users would want to customize the dialog entirely...
Something like:
...

progressDialog.show(
   message,
   indicator: customIndicatorWidget,
   textStyle: Theme.of(context).primaryTextTheme.title,
   dialogTheme: DialogTheme(
    shape: RoundedRectangleBorder(
      side: BorderSide(
        color: Color(0xff000000),
        width: 0.0,
        style: BorderStyle.none,
      ),
    ),
  ),
);

...

That's a cool idea! @HakuFlou

Fixed in latest update pub v1.2.0, update will be published soon! Thank you!


Fix flaky JavaToolchainBuildOperationsIntegrationTest

JavaToolchainBuildOperationsIntegrationTest is pretty flaky because when there are multiple JDKs with same major version installed on the agent, toolchain will select a random one and fail the assertion. This PR fixes it by only searching for JDKs that are "unique" in its major version.
https://ge.gradle.org/scans/tests?search.timeZoneId=Asia%2FShanghai&tests.container=org.gradle.api.tasks.JavaToolchainBuildOperationsIntegrationTest&tests.test=emits toolchain usages for a build with java plugin configured toolchain for ':compileJava' task

The merge queue build has failed. Click here to see all failures.

I have cherry-picked to PR #30599.


Investigate hooks not working

Fixed @ https://github.com/Fizzadar/pyinfra/commit/fbd412a069a6f6741885fa12c264ea77e17bf2dc


Command line option to print full file paths

Sometimes it would be good to have full paths printed for filenames when building with Cargo. A typical example would be when building a large tree of code from an editor/IDE and when file paths only gets printed as src/filename.rs it makes it hard for the IDE to find it.
Cargo currently prints full names under certain conditions but there is no way to makes sure that always happen. Adding a command like option like --full-filename-paths or something better would allow editors/IDEs to easier navigate to compile errors/warnings etc.
See also

#5895
#9887

This issue is similar to #5895 and I wonder: by "full file path" do you mean an absolute path, or simply a more consistent path, such as consistently a path relative to the root of the workspace?

Absolute path would be best as it would work in all cases regardless of how your structure looks like.

@dwijnand  Any news about the implementation of this option?
It would really be very useful to me.
Thank :)

I took a look at this issue today and got it working with full paths. The diff looks like this.
diff --git a/src/cargo/core/compiler/mod.rs b/src/cargo/core/compiler/mod.rs
index 99fa98747..3e77dc871 100644
--- a/src/cargo/core/compiler/mod.rs
+++ b/src/cargo/core/compiler/mod.rs
@@ -633,8 +633,16 @@ fn path_args(bcx: &BuildContext<'_, '_>, unit: &Unit<'_>) -> (PathBuf, PathBuf)
     };
     assert!(src.is_absolute());
     if unit.pkg.package_id().source_id().is_path() {
-        if let Ok(path) = src.strip_prefix(ws_root) {
-            return (path.to_path_buf(), ws_root.to_path_buf());
+        // This setting allows us to print a full path to rustc as this is
+        // useful to print when getting errors of having the full filename printed
+        // as it makes it easier for editors/IDEs to find the file as the editor
+        // may not be have cwd relative to the file.
+        if true {
+            return (src, ws_root.to_path_buf());
+        } else {
+            if let Ok(path) = src.strip_prefix(ws_root) {
+                return (path.to_path_buf(), ws_root.to_path_buf());
+            }
         }
     }
     (src, unit.pkg.root().to_path_buf())

Now in order to have this fully working either:

Always use absolute paths here instead of relative ones. There is a reasoning in the comments for this function why relative paths are used.
Add a command line option (to replace the if true above) and pass it down to this code.

I'm not sure what the best option here would be.

Bump. It would be great to get this feature, I also rely on absolute paths to jump to the error in my environment.

Until this gets in cargo, my workaround is something like
abspath=`cargo metadata | jq -r '.workspace_root'`
export RUSTFLAGS="$RUSTFLAGS --remap-path-prefix src=$abspath/src"

This would be really nice to have. Currently it is very hard to navigate between errors in the Android Studio. It just doesn't highlight any file paths in the errors because they are all relative.

I found a workaround which is to put the workspace root in a sibling directory of the package, instead of a parent directory. For example:
a/
    Cargo.toml  // package manifest, with `workspace = "../b"`
b/
    Cargo.toml  // workspace manifest, with `members = ["../a"]`

Now, cargo build --manifest-path b will print diagnostics with absolute paths. :3


How to train SMPL-based model?

There are some problems in trying to reproduce the pw3d-spin-smpl experiment.

First, the key name in the ./data/poses/pw3d_spin_smpl/groundtruth is misspelled, and the “pose” is written as “psoe”.
In addition, I tried to run the ./train_smoothnet.py with default setting from pw3d_ spin_ 3d.yaml to train smpl-based model using oneeuro filter. It is found that although the train loss and acceleration errors have significantly decreased during the training stage, other metrics have become larger like MPJPE, MPVPE and PAMPJPE. I wonder if there is an error in my hyper-parameter setting.
Besides, does this repository consider adding the slerp filter function mentioned in the paper?

Hi, @Asakurayoho ! Thank you for your focus!

We have corrected the spelling mistakes of ./data/poses/pw3d_spin_smpl/groundtruth and thank you for pointing out the mistake.
For SMPL-based methods, we recommend using checkpoints trained with 3D poses. For example, you can use pw3d_ spin_ 3d checkpoint for 3DPW-SPIN-SMPL testing.
We will add the slerp filter into our repo as soon as possible.

Hi @Asakurayoho,
We use the slerp filter from this file (https://github.com/hongsukchoi/TCMR_RELEASE/blob/master/evaluate.py#L216). The definition can be found here (https://github.com/hongsukchoi/TCMR_RELEASE/blob/ade5ab5e2bd8b1a26338406c0b272d2a16f85070/lib/utils/slerp_filter_utils.py#L1446)

Thanks a lot. I'll do more experiments on it.

Hello author, I also found that based on smpl training, the loss can be reduced to a very low level, and the smoothing index acc also drops sharply, but in the end the index related to mpjpe increases instead. This is somewhat different from the training result of smpl-rot6d mentioned in the paper, which is slightly worse than that of 3D.
Is there anything that needs to be modified for smpl-based training, such as the loss function?


Plugin does not work with custom backoffice URL

The issue is that the resources JS file contains URLs that have umbraco hardcoded in them. This does not work if the backoffice has been moved to a different URL.
The URLs could be constructed using Umbraco.Sys.ServerVariables.umbracoSettings.umbracoPath instead to support custom backoffice URLs.

As a workaround add this to the backoffice JS files:
angular.module('umbraco.services').config([
    '$httpProvider',
    function ($httpProvider) {
        $httpProvider.interceptors.push(function ($q) {
            return {
                'request': function (config) {
                    //some plugins have hardcoded backoffice urls :(
                    //this will fix it without needing to modify their source
                    config.url = config.url.replace(/^\/umbraco\//, '/hax0rproofbackoffice/');
                    return config;
                }
            };
        });
    }
]);

Fixed in 7323c39


Support collaboration for webview tabs

Currently when using live share you don't seem to be able to open webviews collaboratively.  We have extensions that utilize webviews to edit json files.  It would be nice for the user to be able to  collaboratively view the same webview.

cc @lostintangent

By webview, are you referring to this: https://code.visualstudio.com/api/extension-guides/webview
I would assume it should work since running the WebView will be a local vscode command. And the required workspace resources will be got through liveshare rpc. Can you attach a gif of what you are seeing and what liveshare can do to improve the experience?

Yes that is what i'm referring to.  We have a VS Code extension that uses that API to create different webviews.  I don't have a gif, but i can say when we tried it, only text editor tabs show up for the person joining the session.  They don't see any of the tabs with webviews at all.
Behind the scenes in vscode, i believe the tabs containing webviews may be treated a little differently than normal editor tabs.  Maybe its just a matter of including that type of tab?  Not sure.

Hmm, the extension that creates the WebView can use the liveshare APIs to make it behave the way it expects.. The api can be found here: https://www.npmjs.com/package/vsls
The team-chat extension which also uses a WebView for chat, supports chatting in a liveshare session by using our APIs. Maybe this will work for you too.

We don’t currently have any plans to automatically synchronize WebViews, because the API is too low-level for us to know if/how it should be synchronized. As @Priya91 mentioned, we have an SDK that allows extensions to make custom web views fully collaborative. If you share the extension you’re building, we could chat through what it might look like to add Live Share support.
Additionally, you can check out this page to see all the extensions that already have Live Share integration. Many of them are open-source, so you can check out how they’re implemented as well.

Ok.  Thank you that is very helpful.  We will discuss next steps.
Get Outlook for Androidhttps://aka.ms/ghei36
On Sat, Jun 1, 2019 at 11:35 AM -0700, "Jonathan Carter" <notifications<EMAIL_ADDRESS>wrote:
We don’t currently have any plans to automatically synchronize WebViews, because the API is too low-level for us to know if/how it should be synchronized. As @Priya91https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Priya91&d=DwMFaQ&c=vy9bEki9XAFeNghGzbmTEA&r=jokHrZ6mDbxIDbvUI2OiTpaX3wcvbrm9RinRpuaxRH8&m=LIinfMepJN1IP3WY0n8dDG7F824YT_48prTJiGhDH34&s=Ya5jnIXuHBmx_jSE3WH7EA0g_nfcYZkgFwYXiPuPtXU&e= mentioned, we have an SDKhttps://urldefense.proofpoint.com/v2/url?u=https-3A__npmjs.com_vsls&d=DwMFaQ&c=vy9bEki9XAFeNghGzbmTEA&r=jokHrZ6mDbxIDbvUI2OiTpaX3wcvbrm9RinRpuaxRH8&m=LIinfMepJN1IP3WY0n8dDG7F824YT_48prTJiGhDH34&s=T0OOLN1qBr4nyNamwak4HAu-_oDswNASSa5MfKRC2Jw&e= that allows extensions to make custom web views fully collaborative. If you share the extension you’re building, we could chat through what it might look like to add Live Share support.
Additionally, you can check out this pagehttps://urldefense.proofpoint.com/v2/url?u=https-3A__aka.ms_vsls-2Dawesome&d=DwMFaQ&c=vy9bEki9XAFeNghGzbmTEA&r=jokHrZ6mDbxIDbvUI2OiTpaX3wcvbrm9RinRpuaxRH8&m=LIinfMepJN1IP3WY0n8dDG7F824YT_48prTJiGhDH34&s=q4nNFVbA4tLyxNby2OfiXEZNVLJhWJmXpkD1mE93ZCE&e= to see all the extensions that already have Live Share integration. Many of them are open-source, so you can check out how they’re implemented as well.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_MicrosoftDocs_live-2Dshare_issues_2184-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DAJ2BBZE3AMIKFZHZ4VD3ZADPYK6OLA5CNFSM4HR4SCKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWXGGHI-23issuecomment-2D497967901&d=DwMFaQ&c=vy9bEki9XAFeNghGzbmTEA&r=jokHrZ6mDbxIDbvUI2OiTpaX3wcvbrm9RinRpuaxRH8&m=LIinfMepJN1IP3WY0n8dDG7F824YT_48prTJiGhDH34&s=lU9D2-bpbTvNDZQg-Wh2R52EugBuqeTcEsWNM0dvWL0&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AJ2BBZGOWEWNAS3UWYQKVT3PYK6OLANCNFSM4HR4SCKA&d=DwMFaQ&c=vy9bEki9XAFeNghGzbmTEA&r=jokHrZ6mDbxIDbvUI2OiTpaX3wcvbrm9RinRpuaxRH8&m=LIinfMepJN1IP3WY0n8dDG7F824YT_48prTJiGhDH34&s=3QKj4HQm8AA2QLobrTLhp44V7IKGXhIMVSLzOOCfIZg&e=.

Closing this since we have no plans to generically remote WebView content, as opposed to enabling extension authors to make their experiences collaborative via our Live Share API.


Customise message on Altternative Options page

Don't tell people to do what we know they've already tried

Handled by simplified content


build: ngOnChanges property access rule not working

Follow-up to #21074. We have a lint rule that flags property accesses like changes.foo where changes is a SimpleChanges object, because they'll break under Closure compiler. The rule depends on the TS type checker to identify the objects, but it seems like somewhere along the way, tslint changed how they construct the Program which removed the necessary type information.
These changes add a less complicated fallback which looks at whether the name of the receiver of a property access is the same as the name of the first method parameter.

Blocked on #21074.

No longer blocked.

@crisbeto Can you force push to try and force CI to run? Something weird happened here and it's not running.

Done. Also rebased.


MSID: 95160 Version: 2 DOI: 10.1101/2<IP_ADDRESS>6396

MSID: 95160
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>6396
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=95160
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>6396

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/95160v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>6396
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/95160/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

(no schematron messages)


trezor: Remove support for external inputs

Trezor will be closing the loophole that we use to be able to sign external inputs. So we will need to tell users that they will not be able to sign such transactions if they are using those firmware versions.

I can confirm that the updated trezor and test code works well with the ScriptPubKey-checking Trezors.
All the tests passed when running this branch locally with new (unreleased) Trezor version.
Thanks for the cooperation!

Trezor will be closing the loophole that we use to be able to sign external inputs.

We decided to allow this loophole if the user disables "safety checks" on their Trezor. Then they will just need to confirm a warning that the scriptPubKey doesn't match the provided path.

For the record, as @matejcik already mentioned, Trezor T will accept all EXTERNAL inputs that already have a valid signature and EXTERNAL inputs that come with a SLIP-19 ownership proof. See also the documentation on signing external inputs. Trezor 1 doesn't support EXTERNAL inputs at all.
Note that I proposed a PSBT extension for SLIP-19 ownership proofs in https://github.com/satoshilabs/slips/blob/master/slip-0019.md#psbt-bip-174-extension, but we haven't implemented it anywhere yet.

For the record, as @matejcik already mentioned, Trezor T will accept all EXTERNAL inputs that already have a valid signature

Signature or scriptSig? AFAICT, there's only a scriptSig field. As HWI does not contain a finalizer, this is not necessarily useful for us.


migrate to go mod.

Please follow https://github.com/knative/sample-controller/pull/275#issuecomment-620177331 to fix the build-tests. Thanks!
@googlebot rescan

/hold
in case you want to address comment.

/unhold
PTAL


Automated cherry pick of #6686: fix: 避免锁超时

Cherry pick of #6686 on release/3.2.
#6686: fix: 避免锁超时

Codecov Report

Merging #6687 into release/3.2 will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           release/3.2    #6687      +/-   ##
===============================================
- Coverage         7.03%    7.03%   -0.01%
===============================================
  Files              650      650
  Lines           111812   111828      +16
===============================================
- Hits              7869     7865       -4
- Misses          103334   103354      +20
  Partials           609      609

Flag
Coverage Δ

#aFlag
7.03% <0.00%> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/baremetal/tasks/bm_register.go
0.00% <0.00%> (ø)

pkg/baremetal/tasks/ipmiprobe.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/namevalidator.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/opslog.go
1.50% <0.00%> (-0.01%)
:arrow_down:

pkg/cloudcommon/db/scoperesource.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/tenantcache.go
2.93% <0.00%> (-0.35%)
:arrow_down:

pkg/cloudcommon/policy/resources.go
0.00% <ø> (ø)

pkg/cloudprovider/cloudprovider.go
1.53% <0.00%> (ø)

pkg/cloudprovider/instance.go
0.00% <ø> (ø)

pkg/cloudprovider/objectstore.go
2.48% <0.00%> (-0.01%)
:arrow_down:

... and 29 more

Continue to review full report at Codecov.

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

/lgtm
/approve


Can't reset TCLink to zero loss and delay

This optimization prevents zeroing loss or delay link parameters after non-zero period because "not 0 = True" in Python:
https://github.com/mininet/mininet/blob/e203808a20e6eec9e4368757cdccce7010eab548/mininet/link.py#L352-L354
It should be compared to None or running value instead.

you are right

I believe the intent was to not add an unnecessary queuing discipline.
Is there a workaround if you set the loss to 0%?

addLink currently by default makes loss to 0%. This is not an issue in the current build at least @lantz .

@cheriimoya
Is setting the loss to 0% a reasonable workaround?


Searchbar is inconsistent

Searchbar in the courses tab is inconsistent

when trying to search for a course, you have to type the whole name of the course instead of being able to type any part of the course name

Package:  Course

Expected Behavior

If you type a part of the name of a course, it should find the course with the coresponding part in its name
Actual Behavior

You have to type the whole name of the course

Hey @KunzRobert,
I'm aware of this issue, and it's going to be improved by the time, since we're prioritising getting the most important functionality done and then further improving UX/UI 😉.


Add sigma, k1, k2, etc. as default parameters to tf.image.ssim_multiscale

I previously requested a feature on tf.image.ssim for window size and sigma on this link. https://github.com/tensorflow/tensorflow/issues/26929
Please read it for additional information.
I would like to request for variables of multiscale ssim (such as sigma, k1, k2, etc.) to be listed as defaults (instead of being fixed inside the script) as well.
System information

TensorFlow version (you are using): 1.13
Are you willing to contribute it (Yes/No): No. Sorry, I am not qualified to alter the code.

Describe the feature and the current behavior/state.
Currently, key parameters such as the sigma value are fixed when Tensorflow runs tf.image.ssim_multiscale.
It would be great if all the variables mentioned in the original paper proposing MS-SSIM could be altered by the user.
(See Z. Wang, E. P. Simoncelli and A. C. Bovik, “Multi-scale structural similarity for image quality assessment,” IEEE Asilomar Conference Signals, Systems and Computers, Nov. 2003.)
This is especially important for those who wish to use MS-SSIM as a loss function as those variables have a significant influence on the character of the outputs.
Will this change the current api? How?
There will be almost no change. If the parameters which are currently fixed are set as default values, most people will never notice the difference.
Who will benefit with this feature?
Those who wish to use MS-SSIM as a loss function or wish to fine tune it on a deep learning model.
Any Other info.
I do not understand all of the features of MS-SSIM perfectly. I understand that a minimum window size of 176x176 is fixed and that K1 and K2 parameters are usually not altered. Perhaps these values should be set as keyword arguments (**kwargs) to hide unnecessary complexity.

On second thoughts, I don't think that this is necessary for MS-SSIM as much as it is for SSIM.
Closing issue.

Also, I found that everything was already going on without a separate issue.


Chat Box only sends 1 message at a time

Describe
Running multiple sendMessage calls one after another only results in the first message being sent into the chat.
Steps to reproduce

Place computer with a chat box peripheral
Run code like below:

local chatBox = peripheral.find("chatBox")

chatbox.sendMessage("Hello world!")
chatbox.sendMessage("I am dave", "Dave")

See that only "Hello world!" appears in chat

Multiplayer?
No
Version
1.18.2-0.7.22r (Latest 1.18)
Minecraft, Forge and maybe other related mods versions
Forge 40.1.76 Minecraft 1.18.2
Screenshots or Videos
No response
Crashlog/log
No response

If you want to send a message to a player, you need to use sendMessageToPlayer

I know that, the issue is that 2 or more sendMessage one after another (like above) doesn't work. Only the first message is sent to chat, the second is ignored

Oh sorry, my fault. I thought Dave is a player

Does the second attempt return anything? The method returns either true or false with a error message

It should return cooldown notification, because AP have cooldowns for sending chat messages.

Thank you edvin
I completely forget that

Ah awesome! I'm actually in the middle of overhauling the AP docs for you so I'll make sure to add this to them.

That sounds interesting


mavlink_ulog: check_for_updates needs to be checked before acked_sub.…

check_for_updates state shall always be checked before update ulog_stream_acked uorb to avoid deadlocks

Verified in lmcloging-5 drone in PMK


update rack and sinatra

Update rack & sinatra as well as their dependencies. I've been running with these changes for over a year.

Sorry the first branch I made and 'git cherry-pick'ed a change into pulled in some extra updates into the Gemfile.

@dperson great! Thanks for this!


Add ComponentController

Add ComponentController & switch to definite assignment assertions

Can you confirm that this works well in VSCode? With perfect IDE support and everything described in the README working as it should?

Can you confirm that this works well in VSCode? With perfect IDE support and everything described in the README working as it should?

Yes, I can confirm

Okay, thanks!


Add gif and fix alignment

Replace bar chart icon with animated gif from designers.  Also fix alignment.
Before:

After:

@pelikhan @microsoftsam Ping for another review. I added alt text and offline caching.


Problems with using H5PyDataset after deserialization

The traceback is below. It seems that the first request that unpickled dataset gets is next_epoch, which calls reset, which calls close. close, however, requests the attribute external_file_handle bypassing the property. This way load is not called, property is not set, and AttributeError is raised.
Why are there so many places in H5PyDataset where _external_file_handle, not external_file_handle is used?
  File "/home/rizar/dist/fully-neural-lvsr/libs/blocks/bin/blocks-continue", line 15, in <module>
    continue_training(args.path)
  File "/home/rizar/dist/fully-neural-lvsr/libs/blocks/blocks/serialization.py", line 220, in continue_training
    main_loop.run()
  File "/home/rizar/dist/fully-neural-lvsr/libs/blocks/blocks/main_loop.py", line 196, in run
    reraise_as(e)
  File "/home/rizar/dist/fully-neural-lvsr/libs/blocks/blocks/utils/__init__.py", line 225, in reraise_as
    six.reraise(type(new_exc), new_exc, orig_exc_traceback)
  File "/home/rizar/dist/fully-neural-lvsr/libs/blocks/blocks/main_loop.py", line 182, in run
    while self._run_epoch():
  File "/home/rizar/dist/fully-neural-lvsr/libs/blocks/blocks/main_loop.py", line 225, in _run_epoch
    get_epoch_iterator(as_dict=True))
  File "/home/rizar/dist/fully-neural-lvsr/libs/fuel/fuel/transformers/__init__.py", line 64, in get_epoch_iterator
    self.child_epoch_iterator = self.data_stream.get_epoch_iterator()
  File "/home/rizar/dist/fully-neural-lvsr/libs/fuel/fuel/transformers/__init__.py", line 64, in get_epoch_iterator
    self.child_epoch_iterator = self.data_stream.get_epoch_iterator()
  File "/home/rizar/dist/fully-neural-lvsr/libs/fuel/fuel/transformers/__init__.py", line 64, in get_epoch_iterator
    self.child_epoch_iterator = self.data_stream.get_epoch_iterator()
  File "/home/rizar/dist/fully-neural-lvsr/libs/fuel/fuel/transformers/__init__.py", line 64, in get_epoch_iterator
    self.child_epoch_iterator = self.data_stream.get_epoch_iterator()
  File "/home/rizar/dist/fully-neural-lvsr/libs/fuel/fuel/transformers/__init__.py", line 246, in get_epoch_iterator
    super(Filter, self).get_epoch_iterator(**kwargs)
  File "/home/rizar/dist/fully-neural-lvsr/libs/fuel/fuel/transformers/__init__.py", line 64, in get_epoch_iterator
    self.child_epoch_iterator = self.data_stream.get_epoch_iterator()
  File "/home/rizar/dist/fully-neural-lvsr/libs/fuel/fuel/transformers/__init__.py", line 64, in get_epoch_iterator
    self.child_epoch_iterator = self.data_stream.get_epoch_iterator()
  File "/home/rizar/dist/fully-neural-lvsr/libs/fuel/fuel/transformers/__init__.py", line 64, in get_epoch_iterator
    self.child_epoch_iterator = self.data_stream.get_epoch_iterator()
  File "/home/rizar/dist/fully-neural-lvsr/libs/fuel/fuel/streams.py", line 137, in get_epoch_iterator
    self.next_epoch()
  File "/home/rizar/dist/fully-neural-lvsr/libs/fuel/fuel/streams.py", line 128, in next_epoch
    self.data_state = self.dataset.next_epoch(self.data_state)
  File "/home/rizar/dist/fully-neural-lvsr/libs/fuel/fuel/datasets/base.py", line 158, in next_epoch
    return self.reset(state)
  File "/home/rizar/dist/fully-neural-lvsr/libs/fuel/fuel/datasets/base.py", line 139, in reset
    self.close(state)
  File "/home/rizar/dist/fully-neural-lvsr/libs/fuel/fuel/datasets/hdf5.py", line 596, in close
    self._out_of_memory_close()
  File "/home/rizar/dist/fully-neural-lvsr/libs/fuel/fuel/datasets/hdf5.py", line 599, in _out_of_memory_close
    if not self._external_file_handle:
AttributeError: 'H5PYAudioDataset' object has no attribute '_external_file_handle'

@janchorowski , FYI, I created an issue.

Update: changed _external_file_handle to external_file_handle and blocks-continue works!


Remove some unused but set variables

There are a few unused but set variables when trying to build with Clang. So fix them accordingly... see individual commits for more details.
(There could probably more set but unused variables, so need to tackle them one by one when found.)

GCC doesn't because -Wunused-but-set-variable is explicitly disabled with -Wno-unused-but-set-variable in GCC's compiler_flags.cmake. But Clang and ARC MWDT are both set to warn.

Maybe we should consider removing -Wno-unused-but-set-variable then. cc @tejlmand


Set log level without trackerDiagnostic (close #441)

For issue #441.
During Tracker construction, setting of the logging level had mistakenly been put inside a conditional. The effect was that, since logging is OFF by default, no logs at all could been seen unless trackerDiagnostic had also been specified in the TrackerBuilder options.
This change allows logs to be set properly, and also adds tests for logging.

Thanks for your pull request. Is this your first contribution to a Snowplow open source project? Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://docs.snowplowanalytics.com/docs/contributing/contributor-license-agreement/ to learn more and sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.


Patch python-gnupg to fix tests on aarch64

Motivation for this change
For some reason /etc/foo is writable during the nix build on some
systems. I've observed it on an aarch64 Ubuntu 18.04 system.
This patch is also filed as an issues against the upstream package
so once it lands we can remove it here.
See https://bitbucket.org/vinay.sajip/python-gnupg/issues/143/pr-fix-tests-when-etc-foo-is-writable
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This patch just got merged https://bitbucket.org/vinay.sajip/python-gnupg/commits/443fc58ed3ce5ea928d90c16d6cfac25e40c05ba

Update commit message to pythonPackages.python-gnupg: Patch to fix tests on some systems

@jonringer @veprbl

@3noch Could you please rebase to resolve the merge conflict?

@3noch Could you please rebase to resolve the merge conflict?


Not Launching?

I tried setting this up in eclipse, but it doesn't seem to run with or without arguments.  I'm not even sure if this is something on your end or mine, but I thought I'd mention it just in case. Sorry if I'm wasting your time!

Sorry Again! Fixed it by replacing the one line of the main method with ```Java
new ExtractorGUI().start();


gRPC API requires serving and forward integrity key to activate LoRaWAN 1.0.3 ABP device

When activating a device through the gRPC API it is required to supply both s_nwk_s_int_key and f_nwk_s_int_key , though they should not be needed when using a device configured to use LoRaWAN 1.0.3 and ABP.
When activating through the interface these keys are internaly set to be the same as the nwk_s_enc_key (which can be verified with the GetDeviceActivationRequest), but this is not intuitive when calling the API:

If the provided keys do not match the activation will not work.
If no keys are supplied at all an "Invalid string length" error is raised.

If you think this can be better documented, them I'm happy to review a PR for this :-) However, I'm not planning to change how this is implemented in the API. While this might look strange, it makes it a lot easier to work with both LoRaWAN 1.0 and LoRaWAN 1.1 internally.

Got it. Sure I could do that, thanks!


Agent proxy that supports multiple input keys

At the moment, we have agent proxies that support only one input key. These don't support the case of multiple parts in the observation, for example both features and images.
I wrote a new agent proxy that iterates through the given keys and creates a dictionary where all parts of the observation are stored with their respective keys. The policy can then handle these as needed.
Is this a good way to approach this?

Very clean, but I'm wondering how a dictionary input for a policy works e.g. with ONNX exporters etc. I found it much easier to let the input_keys just represent argument ordering. So your policy can be def forward(self, a, b, c) and your input keys tell the proxy what data goes with a, b, c.

Wait Tom, just to make sure I understand what you're saying. You would like to see a
actions = self.policy(dict_tensor_obs)[0].detach().cpu().numpy()

changed to
actions = self.policy(**dict_tensor_obs)[0].detach().cpu().numpy()

but apart from that mostly things work fine?

Very clean, but I'm wondering how a dictionary input for a policy works e.g. with ONNX exporters etc. It would also require the policy to handle the names being able to be different. I found it much easier to let the input_keys just represent argument ordering. So your policy can be def forward(self, a, b, c) and your input keys tell the proxy what data goes with a, b, c.

That makes sense. It would also help with readability in the policy, as the function signature will explicitly show what it expects to receive.

@singhblom No, not even that. That requires the policy function to be defined using the keys of the agent proxy. That in turn makes the Python code determine the name of the inputs sent from the game. What I want to see is:
tensor_obs = []
for key in self._input_keys:
     inputs.append(...)

actions = self.policy(*tensor_obs)[0].detach().cpu().numpy()

Then, the function can be def forward(self, a, b, c), while the game sends {'foobar': [...], 'image': [ ... ], 'hidden': [ ... ] }. With input_keys being set to ('image', 'foobar', 'hidden',) we'd map a=image, b=foobar, c=hidden.

Yepp! And with the current setup; if I send feature_data instead of features it all goes up in flames everywhere. :-) No reason for it, and using positionals at the internal layer solves that - like the FeatureAgentProxy. You could put the same code I just posted in the feature agent proxy, actually, and it'd still work because we have 1 positional - 2 with epsilon - already. No need for dictionaries, unless we make sure no part has a hardcoded name when reading from it.
Another way of thinking it is that I'm remapping the names. Again, {'image': 'a', 'foobar': 'b', 'hidden': 'c'}. That's also fine. I could say 'feature_data': 'a' if that's what my data generator is generating. **tensor_dict_obs is a bug waiting to happen - input_names was added because some code assumed the features were called obs. That requires a separate policy and q network where that name is in the function signature. With **, you cannot use that network for any other input name at that point (without remapping explicitly!).


Build hugo from source

Env: WSL2 Ubuntu 20.04
faced issues (cannot be installed from snap):

internal error, please report: running "hugo" failed: cannot find installed snap "hugo" at revision 12665: missing file /snap/hugo/12665/meta/snap.yaml --> give up snap
cannot perform operation: mount --rbind /dev /tmp/snap.rootfs_Aaaf74//dev: No such file or directory --> give up snap
build github.com/gohugoio/hugo: cannot load embed: malformed module path "embed": missing dot in first path element --> install latest go

trials:

https://github.com/microsoft/WSL/issues/5126#issuecomment-653715201 --> not working for me
https://github.com/DamionGans/ubuntu-wsl2-systemd-script --> not working for me

uninstall: https://github.com/DamionGans/ubuntu-wsl2-systemd-script/blob/1d24d54714431a02658a0a5849dfd7a8c17c9d51/uninstall.sh

Steps

install latest go

$ sudo add-apt-repository ppa:longsleep/golang-backports
$ sudo apt update
$ sudo apt install golang-go
$ go version
go version go1.18.3 linux/amd64

clone and build hugo

$ mkdir $HOME/go/src
$ cd $HOME/go/src
$ git clone https://github.com/gohugoio/hugo.git
$ cd hugo
$ go install --tags extended
$ hugo version
hugo v0.99.0-DEV-89c1655ec88cd7286c2ed5f9b7eaed35af9cda52+extended linux/amd64 BuildDate=2022-04-28T11:02:45Z

If hugo version is failed, remember to add go path to PATH

Add export PATH=$PATH:$HOME/go/bin in ~/.bashrc

Related post: https://aben20807.github.io/posts/20230310-install-hugo-on-ubuntu-20-04/