local.settings.json to override input binding

is it possible to override input bindings declared in function.json with values from local.settings.json?
as i would like to override the queue input binding via local.settings.json for local development, without modifying function.json and accidentally checking in changes to that file.
i have tried this locally without success, it just looks for a queue with the key of the item in local.settings.json, rather than the value.

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

ID: b2646ad4-34b7-fc5e-dcc9-d53a061df394
Version Independent ID: bbff4fda-24e4-2b62-24b9-94cda5f53bed
Content: Work with Azure Functions Core Tools
Content Source: articles/azure-functions/functions-run-local.md
Service: functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

Thanks for the question! We are investigating and will update you shortly.

@GuyHarwood no you cannot. The function will use local.settings.json when developing on prem by design
You can use the --publish-local-settings switch described in this doc to have your function pull the info from local.settings.json though

@MicahMcKittrick-MSFT This is only for local development.  let me explain our situation a little more, to see if it helps...

there are 4 developers on our team
we have one storage account in azure for our development team (limitation imposed by client)
we have 4 queues in our application, each developer has their own set, prefixed with their name (so my prepare-check queue is called guy-prepare-check)
in function.json we declare an input binding to the queue prepare-check
however, when developing locally i want to bind to guy-prepare-check to isolate queue messages created locally by my own environment.
rather than manually edit function.json temporarily to switch the binding to guy-prepare-check i would like to use my local.settings.json to override this.

Does that make sense?
It is possible to override storage connection strings via local.settings.json so would it possible to add this feature if it is not already possible?
we are all nix based, so prefer not to use the windows based storage emulator
azurite (cross platform emulator) appears to be broken, and does not work with azure functions

@ggailey777 do you have any thoughts on this one?

@GuyHarwood, @MicahMcKittrick-MSFT local.settings.json is designed to mock project-level settings for local development, such as application settings and CORS. It has no impact on individual function bindings.
If you are using C# class library functions, you can set binding properties at runtime. You could then have an app setting in local.settings.json that evaluates locally to guy-prepare-check at runtime, but in Azure the app setting is prepare-check. To be honest, I haven't worked with imperative C# bindings, but if you have questions, I would try Stack Overflow or the Functions Forum.
I don't know that there is a way to do this for JavaScript, but you can always ask on Stack or the Forum.

Thanks @ggailey777!
@GuyHarwood does that help?

@MicahMcKittrick-MSFT Sadly not - we are using Javascript.

@GuyHarwood Got it.
I would suggest you ask the functions team directly on this issue
https://github.com/Azure/Azure-Functions/issues
Many of them should have more experience using JS and have a better idea of if this is possible and how to achieve this.
Once you open that issue you can reference this one as well so we can track it. I will close this out for now as there is no update needed on this specific doc. Let me know if you have issues opening the issue on the Functions GitHub page


Empty params in url cause Uncaught SyntaxError

Hi there,
Just noticed today that this library doesn't seem to play nicely with empty url search query params.
For example, for the url:
http://localhost:5000/something?event=

I'm getting the following error:
Uncaught SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at toParams (es.es5.js:37)
    at Object.../../node_modules/react-easy-params/dist/es.es5.js (es.es5.js:47)
    at __webpack_require__ (bootstrap:709)

I'm actually not even using the params part of this library at the moment, just the storage part - but it seems to run some kind of setup for the params side of things in any case (I assume the backing stores). Looks like its running into some kind of JSON parsing error when a query param is empty in the url.
In this case I believe the params object should look like so:
{
   event: "",
}

Using the popular query-string library, I get an object like that when I parse the query param part of the url.

Thanks for the crystal clear issue, it will be an  simple fix.
I would rather have ?event= result in params.event === undefined instead of params.event === ''. The reason is that easy-params is preserving type information of query params and 'nothing' pairs best with undefined from all the types. Are you okay with this?

Hmm I'm not too sure, and I've been thinking about this in my use case lately as well. I'm personally leaning towards it being an empty string, because then we can deliberately check on length if we want to deal with it like that in an "undefined" manner. And then it also allows the passing of empty strings deliberately... otherwise how would we deal with that?
Also if event was never passed in as a param, then params.event === undefined would be true.. which seems truer than if it was deliberately defined in the url.

You are right about this. So this is my current proposal in a (url -> object -> url) format

?page=12&filter="apple" -> { page: 12, filter: 'apple' } -> ?page=12&filter="apple"
?page=12&filter=apple -> { page: 12, filter: 'apple' } -> ?page=12&filter="apple"

invalid type info in url for apple falls back to string

?page=12&filter= -> { page: 12, filter: '' } -> ?page=12

empty query params fall back to empty string, empty object props are not reflected in the url

?page=12&filter -> { page: 12 } -> ?page=12

Totally empty (no = sign) query params are not reflected in the params object.

It might seem a bit complex, but from a practical point this would be the best I think. Having empty strings in the params object is pretty common, since most values come from HTML input values. I would not reflect those in the query to keep things clean.
What is your opinion?

In my use case, I think I might prefer:
?page=12&filter= -> { page: 12, filter: '' }-> ?page=12&filter=
Feel like behaviour should work both ways, as that might be the most expected outcome?
And also because I am using url params to represent inputs on the page which can be set to completely undefined (with a checkbox), or they can be deliberately kept empty to represent an empty string.
But that said, I understand where you're coming from too. I guess they're both correct in their own ways.
I'm only noticing now that you're trying to keep type information in the url structure as well- which I'm unsure about because of the established way that url params have worked in the past. I do see the value in it though.
But using that, my preference would then be:
?page=12&filter= -> { page: 12, filter: '' }-> ?page=12&filter=""

Agreed, functionality is more important than nice query strings. So in the end I have this one implemented:

?page=12&filter="apple" -> { page: 12, filter: 'apple' } -> ?page=12&filter="apple" -> { page: 12, filter: 'apple' } -> ?page=12&filter="apple"
?page=12&filter=apple -> { page: 12, filter: 'apple' } -> ?page=12&filter="apple" ->  { page: 12, filter: 'apple' } -> ?page=12&filter="apple"
?page=12&filter= -> { page: 12, filter: '' } -> ?page=12&filter="" -> { page: 12, filter: '' } -> ?page=12&filter=""
?page=12&filter -> { page: 12 } -> ?page=12 -> { page: 12 } -> `?page=12

Let me know if you agree and I will merge and release it.
Another note: I am pretty sure about including the type info. I know it is a bit unorthodox, but it is really valuable in practice and I see no huge drawbacks because of it.

v2.0.2 is out with the changes. Thanks for the tips, I think we found the best solution in the end 🙂


header: Add links to symbiflow website and documentation

Any documentation that uses this theme will have these 2 links in the header by default. The option 'hide_symbiflow_links' in html_theme_options can be set to True in conf.py to disable this feature.

Should resolve SymbiFlow/fasm#26
Signed-off-by: Daniel Lim Wee Soong<EMAIL_ADDRESS>

@mithro ping

@daniellimws I wonder if there are better icons we could use?

Otherwise LGTM!

Is there any there you would suggest? I can't think of any particular one.

Maybe for the documentation link;

https://material.io/resources/icons/?icon=chrome_reader_mode&style=baseline
https://material.io/resources/icons/?icon=book&style=baseline
https://material.io/resources/icons/?icon=description&style=baseline
https://material.io/resources/icons/?icon=library_books&style=baseline
https://material.io/resources/icons/?icon=menu_book&style=baseline

For the website you might already have the right icon, but maybe https://material.io/resources/icons/?icon=web&style=baseline ?

BTW - I think for the GitHub link we should probably use the "code" icon shown at https://material.io/resources/icons/?icon=code&style=baseline icon?

I also wonder if we should have a help / contact link?

A link to the IRC channel?

Ok I changed the icons. But currently the icon for GitHub is set inside conf.py for each repository so the change has to be made inside each repository.

@daniellimws -- That looks good!


Add Nong Song

Song Name
KERO
Artist Name
Someone
Source
Youtube
Youtube Link
Rhttps://youtu.be/GYE9H4SMq5E?si=hMfG9xay-UFgVtdA
Direct File Link
No response
Song ID
1
Start Offset [ms]
No response
Extra
No response

reject


Not able to pull docker-images/OracleWebLogic/dockerfiles/12.1.3/

Hi Team,
How can i download/pull these weblogic data.

@aivl2018 You need to clone this repository git clone https://github.com/oracle/docker-images.git to your machine.  Once cloned then follow the README.md to build the image.
Thanks
Monica

Thanks Monica for your reply.
I have cloned it to my local machine. but how can i build docker image for weblogic 12.1.3.
Can you pls provide commands for that.

Thanks Monica for your response.
Can we create domain for Weblogic :<IP_ADDRESS>. for Generic distribution. As i can see there is only steps for Developer distribution is docker container registry.
In sample dockerfile, there is also mention (FROM  oracle/weblogic:<IP_ADDRESS>-developer ) not a generic distribution .
Thanks in advance

@aivl2018 We have prebuilt images of WebLogic <IP_ADDRESS> both dev and generic (no label) in Docker Store: https://hub.docker.com/_/oracle-weblogic-server-12c  and in the Oracle Container Registry https://container-registry.oracle.com under middleware.
If you want to build the image manually then in the FROM instead of extending oracle/weblogic:<IP_ADDRESS>-developer do oracle/weblogic:<IP_ADDRESS>.  The README should have the step by step instructions how to build images.  Lety me know if you have any other questions.
Thanks
Monica

@aivl2018 The FROM clause can always change to point to the image you want to build on top of, e.g. if you are building the domain on top of the WLS <IP_ADDRESS> image you pulled from Docker Store then your clause would be something like "FROM store/oracle/weblogic:<IP_ADDRESS>".

Thanks Monica for instant reply.
Issue got solved.
Now i am stuck while creating container . Below error occurred.
domain_name     : [base_domain]
admin name      : [AdminServer]
admin_port      : [7001]
cluster_name    : [DockerCluster]
domain_path     : [/u01/oracle/user_projects/domains/base_domain]
production_mode : [prod]
com.oracle.cie.domain.script.ScriptException: 60308: Domain location not writable.
60308: The domain location does not have write permission.
60308: Correct permissions or select different domain location.
    at com.oracle.cie.domain.script.ScriptExecutor.writeDomain(ScriptExecutor.java:2035)
    at com.oracle.cie.domain.script.jython.WLScriptContext.writeDomain(WLScriptContext.java:1793)

If you are using 12213-domain sample the domain home gets mapped to a host volume on your machine.  This would be the -v clause in the docker run command.  That host volume myst have write priviledges so that the domain home is persisted there.
Thanks
Monica

Could you please elaborate it.
I have not mentioned -v clause in my docker run command.
Command used :
docker run -d --name wlsadmin --hostname wlsadmin -p 7001:7001 --env-file ./container-scripts/domain.properties -e ADMIN_PASSWORD=w3bl0g1c 12213-domain
& where is " host volume myst" present. Can you pls mention command over here where to go & check it.
Thanks In Advance !!!!

Thanks Monica for your response.
Admin Server is in running state after giving 777 permission to my local domain.
Now my container is created.
But i am not able to access weblogic console in browser.
I have enabled All traffic in aws still not opening.
http://ec2-3-56-444-20.compute-1.amazonaws.com:7001/console


Decrease minSdkVersion to API 14

Related to #36 .

Sorry about this, but I am afraid I will have to close this PR as well, as it is going to be impossible to merge it after the massive refactoring that the library has undergone recently. Luckily, this request is quite old and what this PR implements, in my opinion, is not necessary anymore.
In any case, thank you very much for your collaboration and apologies for the delay in my response!


Make health bars show rough percentage of max hp

From my quick testing this works fine, and fixes things like an hp_max of 10 and hp of 10 showing players at half health

FWIW, Minetest uses the following code to adjust the health bar to a fixed width (or max value): https://github.com/minetest/minetest/blob/master/builtin/game/statbars.lua#L30-L37


struct.error: unpack requires a buffer of 12 bytes

Hello!
When I follow the readme to use RViz visualization, an error occurs.

I find the function deserialize(str) and print out the input, and find that the input is empty("").
Also, the code has a note on it :"raise genpy. DeserializationError(e) # most likely buffer underfill".
This problem causes the bug that the env couldn't step.
How can I solve this problem?

I think..
Some third-party packages  have been taken from https://github.com/srl-freiburg/pedsim_ros/tree/melodic-dev (which only supports ros-melodic). I think this part might be the problem. I would recommend testing in the ROS melodic environment.


Conform height of bounding box across logo variants

Differently sized bounding box heights for different logos are causing issues for NRK Radio.
A possible fix could be to conform the height of the logo bounding box for the different layout-variants. The height would have to accommodate for the maximum logo height. This would mean:

title right: 20px 1)
title below: 34px 2)
with-bg: 24px

This would accommodate for ascenders/descenders and most diacritics. A notable exception would the uppercase Å – this would have to be tweaked to fit the bounding box.
This would not accommodate for two-line titles (such as "NRK Kringkastingsorkestret"), which would need title-below: 51px. I would assume that it is better to operate with two heights – for one-line and for two-line titles, but this can be discussed further. The obvious case for these (besides "NRK Kringkastingsorkestret") would be NRKs districts, for example "NRK Vestfold og Telemark".

If we decide to implement this change, it should probably be done so that it is part of PR #210, which moves new logos from nrk-logo-preview to nrk-logo.

Added a codepen with examples to try and illustrate the issues with different bounding-box/viewbox sizes across same logo group types. https://codepen.io/skjalgepalg/full/rNqgpyv

After some discussion we propose to change the height of the bounding box to 24px for title-right logos. This corresponds to the safe zone of logo composition, and is also equal to the with-bg logos, thus simplifying the structure a bit more. It will also address any potential issues with extra high/low ascenders/descenders, such as an uppercase Å.

One further question – if we include the safe zone of the logos for the title-right logos, should we not also do that for the title-below logos, so that that different variants behave in a internally predictable way?
This is the design guidelines for logo lockups and safe zones:

This is the adjusted Figma assets for title-right, and with-bg:

This is the current Figma asset for a title-below logo:

This would be an adjusted Figma asset (including vertical safe zone) for a title-below logo:

Closing this issue as resolved.
In v13 all title-right/with-bg variants have the same height (24 px) while title-below logos that follow the standard logo lockup have a height of 41 px.
Expceptions include: "NRK" logo (h: 14 px), title-below logos connected to P3/MP3. Title-below logo for "NRK Kringkastingsorkestret" (58px) where sub-brand is split into two lines. "NRK Yr", "NRK Nyheter", "NRK Sport", "NRK 1", "NRK 2" and "NRK 3", where logos have not yet been updated to new design (new versions are available in the ´preview´context).


Fix missing reverse_adaptor constraints

Fixes #143

Woo, ICEs in two different compilers at once, this must be a good commit...


Update mui-icon-builder folder with latest code

Describe the desired behavior
Update mui-icon-builder folder with latest code (https://github.com/mui/material-ui/tree/master/packages/mui-icons-material)
Describe the current behavior
Currently  mui-icon-builder folder is not as per https://github.com/mui/material-ui/tree/master/packages/mui-icons-material
Is this request related to a current issue?
Additional Context
No

The MUI folder structure and icon names have changed due to misspelled icon names and updates for MUIv5. Rebase when we are ready.

We no longer use the MUI icon builder, we use SVGR directly


Fix format string in error message.

[ ] Tests added / passed
[ ] Passes black dask / flake8 dask / isort dask

Without str call the format operator will raise a type error.

Thanks for opening this @trivialfis - it's a nice fix!


In the section Build app

File: get-started/part2.md, CC @johndmulhausen
IN the section Build app, just before command "docker build -t friendlyhello .", please mention that user MUST NOT omit the dot at the end. It is easily to be overlooked, so user will be saved from unnecessary dilema. I have not included dot at the end of command, so I was 1 minute thinking what is wrong on the site...  Dot (local dir) can be placed also right after "build" word, so it is not omitted when copy-pasting.

Hi, @gopa810 , I totally agree and have that covered in my upcoming rewrite. Thanks for bringing it up. This is how the step will look when I'm done:

Build the image with the files in this directory (.) and tag it with a meaningful name such as ...


Fix active Todos service behaviour

Description

Franz 5.6.0 came with a new behaviour related to Franz Todos. If a user adds Franz Todos as a service and uses Franz Todos simultaneously, the TodosWebView gets expended when the user switches to the Franz Todos service.
Motivation and Context

For https://github.com/getferdi/ferdi/issues/1017#issuecomment-775014033.
Ferdi offering multiple alternatives to Franz Todos, this pull request aim at maintaining this behaviour for the supported alternatives.
Screenshots

https://user-images.githubusercontent.com/412895/120563873-8af11980-c401-11eb-86aa-1e97dac00f03.mp4
Checklist:

[x] My pull request is properly named
[x] The changes respect the code style of the project ($ npm run lint)
[x] I tested/previewed my changes locally

I took my stab at refactoring this to move the common logic into mobx stores. Feel free to edit or force-push the previous version if something's off.

Assuming @kytwb is ok with the direction/changes, I'm 👍

Actually, there's a _migrate method on SettingsStore which may help with the settings migration.

so, in which case, we can use that to migrate and not incur tech-debt here?

I'm looking into it, but so far, it seems we can't because the migrations don't have access to the previous contents of settings.yaml.

@kytwb @vraravam Can we go ahead and merge this?


Minor fixes

I'm working on packaging xrdp for Amazon Linux. The hard stuff is still in the works. I'm pushing the trivial things first to get them out of the way.

:+1:

+1
looks good


Headers fields must be case insensitive

Bug Report
Description
From the spec:

Each header field consists of a case-insensitive field name followed
by a colon (":"), optional leading whitespace, the field value, and
optional trailing whitespace.

 header-field   = field-name ":" OWS field-value OWS

 field-name     = token
 field-value    = *( field-content / obs-fold )
 field-content  = field-vchar [ 1*( SP / HTAB ) field-vchar ]
 field-vchar    = VCHAR / obs-text

 obs-fold       = CRLF 1*( SP / HTAB )
                ; obsolete line folding
                ; see Section 3.2.4

The field-name token labels the corresponding field-value as having
the semantics defined by that header field.  For example, the Date
header field is defined in Section <IP_ADDRESS> of [RFC7231] as containing
the origination timestamp for the message in which it appears.

To Reproduce

add a header: "Cache-Control": "no-cache"
add the same header with different casing: "cache-control": "max-age: 600"
inspect the request and see the header twice.

Expected behavior
The last assignment survives or if the method allows for appending, the headers are combined.
Additional context
https://tools.ietf.org/html/rfc7230#section-3.2
Leads to bugs such as #474 #472 #413

Taking this!


how disable autoplay in youtube videos

how disable autoplay in youtube videos
i try to modify de js file, but doesn't work

Edit this line: https://github.com/ashleydw/lightbox/blob/master/ekko-lightbox.js#L417

autoplay=1 is not working right?


Switch back to service CA for testing certificate re-creation

For X.509 certificates we are using the manually created certificates
for the HTTP protocol adapter now. However, that will not create
the expected certificate, and also will not automatically re-create it.
So in this test, we explicitly switch back to the service CA for HTTP.
Type of change

Bugfix

Description

Checklist

[ ] Update/write design documentation in ./documentation/design
[ ] Write tests and make sure they pass
[ ] Update documentation
[ ] Check RBAC rights for Kubernetes / OpenShift roles
[ ] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
[ ] Reference relevant issue(s) and close them after merging
[ ] Update CHANGELOG.md

@enmasse-ci run tests ocp4 profile=iot testcase=io.enmasse.systemtest.iot.isolated.tls.ReloadCertificatesTest

:x: Test Summary :x:
TEST_PROFILE: iot
TEST_CASE: io.enmasse.systemtest.iot.isolated.tls.ReloadCertificatesTest
TOTAL: 25
PASS: 24
FAIL: 1
SKIP: 0
BUILD_NUMBER: 1041
BUILD_ENV: crc
:heavy_exclamation_mark: Test Failures :heavy_exclamation_mark:

testRecreateCertificate in io.enmasse.systemtest.iot.isolated.tls.ReloadCertificatesTest

@enmasse-ci run tests ocp4 profile=iot testcase=io.enmasse.systemtest.iot.isolated.tls.ReloadCertificatesTest

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: iot
TEST_CASE: io.enmasse.systemtest.iot.isolated.tls.ReloadCertificatesTest
TOTAL: 25
PASS: 25
FAIL: 0
SKIP: 0
BUILD_NUMBER: 1044
BUILD_ENV: crc


Working with an async RTM client

Description
Hi, I'm trying to use an async RTM client in the following manner -
RTM_CLIENT = slack.RTMClient(token=TOKEN, run_async=True)
RTM_CLIENT.start()
while True:
     ...

And I defined the following function to listen to events:
@slack.RTMClient.run_on(event='message')
def listen(**payload):
...

It looks like I'm doing something wrong here as I'm not getting any events from slack. It works normally with the sync client. Any help would be appreciated.
What type of issue is this?

[ ] bug
[ ] enhancement (feature request)
[X] question
[ ] documentation related
[ ] testing related
[ ] discussion

Requirements

[X] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[X] I've read and agree to the Code of Conduct.
[X] I've searched for any related issues and avoided creating a duplicate issue.

Hey @liorblob ,
First looks, I don't see anything off that may cause this to go wrong. We have run_async=True in the tutorial so may be worth having a look at https://github.com/slackapi/python-slackclient/blob/master/tutorial/PythOnBoardingBot/async_app.py . Can you give us an example of the rest of your code? I'm curious about your while True but you may also need to wrap your RTM_CLIENT.start() as loop.run_until_complete(rtm_client.start()).

@splinterific Thanks for the quick response. I've tried working according to the tutorial in this example:
@slack.RTMClient.run_on(event='message')
async def say_hello(**payload):
    data = payload['data']
    print(data.get('text'))

if __name__ == "__main__":
    loop = asyncio.new_event_loop()
    asyncio.set_event_loop(loop)
    rtm_client = slack.RTMClient(token='xoxb-337101411617-ECxUiSOnHQP1lYZnmXq3Wtzc', run_async=True, loop=loop)
    loop.run_until_complete(rtm_client.start())

    while True:
        print('Hi')
        time.sleep(5)

The process gets stuck on loop.run_until_complete and the while loop isn't running. I'm quite new to async coding in Python so I might be approaching this wrong.

Looks like this solved it:
import re
import slack
import time
import asyncio
import concurrent
from datetime import datetime

@slack.RTMClient.run_on(event='message')
async def say_hello(**payload):
    data = payload['data']
    print(data.get('text'))

def sync_loop():
    while True:
        print("Hi there: ", datetime.now())
        time.sleep(5)

async def slack_main():
    loop = asyncio.get_event_loop()
    rtm_client = slack.RTMClient(token='x', run_async=True, loop=loop)
    executor = concurrent.futures.ThreadPoolExecutor(max_workers=1)
    await asyncio.gather(
        loop.run_in_executor(executor, sync_loop),
        rtm_client.start()
    )

if __name__ == "__main__":
    asyncio.run(slack_main())

@liorblob Still they are not asynchronous. All messages are serving in serial. Could you please check?

It's not about the messages, rather the client itself being non-blocking (rtm_client.start()).

Ok, is there be any possibility of responding in parallel, currently, it's responding one by one.
Thanks in advance for the help.

I think you should try to open a different issue for this.

@rcsrao Probably, the issue you mentioned is this one: https://github.com/slackapi/python-slackclient/issues/558 I wanted to resolve this in v2.6 but haven't managed to address it yet.

@liorblob I have posted here https://github.com/slackapi/python-slackclient/issues/777 Please check.

@seratch Thank you, I will check and let you know.


Updates Heading, Image, Label & Text docs to use Example

Partial fix for #5.
Screenshots:

@chrislloyd could you add some screenshots?

@christianvuerings good call - updated the description. Going to merge anyway because I think it's better than before (even if there are still small errors pending review). If any, would rather fix those in follow up PRs because of some of the other work I'm doing.
Also, can't wait for the per-PR docs!


CSV Export use new async jobs

As a Nautobot User, I want the ability to export data in CSV and have those CSV exports run asynchronously and provide me a means to download a file once it is complete, so that I am not annoyed and confused by timeouts or long running foreground requests to export CSV data today.
For now we will do this as a system job but make no provisions for any changes to the permissions model for jobs. Users will need to have permission to run this new csv export job.
This story also does not have any special provisions for any UI enhancements/changes related to CSV export. Upon clicking the existing Export button, the user should be redirected to the Job result which will generate their export and from which they will be able to download the file. A later story will deal with UI/UX enhancements in this area.
This story also needs to account for custom Export Templates. They should work exactly the same way as CSV export.
The job should still honor the CSV export filtering logic.

Implemented in #4746 for 2.1.


Getting Original Schema of a DataFile in a FileScanTask?

Question
Is there a recommended way to getting the base / original schema or schema-id of a data file in a FileScanTask returned during FileTableScan.plan_files? This is useful to determine what kind of schema evolution occurred with the subset of files we are reading, and group files together with the same schemas for reads.
I had a hard time accomplishing this in the Java library, but found it much easier to do in Python. In plan_files, we can get the snapshot id a data file was created by looking at the snapshot_id of the associated manifest entry (or added_snapshot_id of the manifest list if the previous is null). From there, we can get the associated schema per snapshot.
Is this a logical approach, or is there a better way to get the original schema? Happy to open a PR to integrate this into FileTableScan if it would be useful!

@Fokko any thoughts?

Hey @srilman sorry for not replying earlier. It slipped somewhere through the cracks, thanks for pinging me!

Is there a recommended way to getting the base / original schema or schema-id of a data file in a FileScanTask returned during FileTableScan.plan_files? This is useful to determine what kind of schema evolution occurred with the subset of files we are reading, and group files together with the same schemas for reads.

Unfortunately, no :(

From there, we can get the associated schema per snapshot.

A snapshot can have files with multiple schemas. See the example in https://github.com/duckdb/duckdb_iceberg/issues/40

Is this a logical approach, or is there a better way to get the original schema? Happy to open a PR to integrate this into FileTableScan if it would be useful!

The only source of truth is in the Parquet file. The crux is that you don't want to do name-based projection, but field-id-based projection. Names can change over time, but field-id won't. So if you filter on a specific field-id, that will always work correctly. The same goes when reading parquet files, it can be that the names change over time, and you don't want to rewrite petabytes of data, so you can leave them as is. When reading, you want to make the field-ids to the current schema.


Update frontend dependencies

In the JS world I do not want to fall too far behind and some of the dependabot alerts actually refer to frontend parts that make it into the final bundle.
This PR does explicitly not update axios as it changed the default value of the response from any to unknown and to properly migrate we'd need to finally create type decls for backend JSON responses. They can probably be generated from our openapi specification but that's a bit out of scope right now.
I'll have a look at this tomorrow and make sure nothing too obvious breaks.

Maybe problematic upgrades
I updated vue-echarts (which has no typescript types. Yay!) to the next major version which included some breaking changes. I think I tracked them down but as the chart component is used quite a lot there might be subtile changes that weren't documented.
Ignored updates
This is the current status of the dependency updates I will not perform:

The axios update would require us to properly type responses which would take some time.
The vuex-persist update is just fundamentally incompatible with (de)serializing rich objects. I doubt this is worth looking at currently.
The eslint and sass loader upgrades depend on vue-cli 5 which does not yet have a stable release

It's "tomorrow" for a very loose definition of the word but I finally got around to this. I will leave this open for a day and then merge it, though the change will be deployed to the lean instance right away. I will stick around for a bit after the merge and my E-Mail notifications are enabled in general, if all hell should break loose for some unforeseen reason not found during my tests.


Possibility to rename operators ?

Hi,
is there a way to rename operators ?
If not, I was thinking about omitting built in operators and then adding custom ones that would be the default one but with other names,
would it be doable ?
Thanks

Yep, this is doable:
import { createQueryTester, $eq, $in } from "sift";
const filter = createQueryTester({ $eq: 5 }, { operations: { $eq, $in } });

Let me know if this answers your question!

Thanks,
I tried something like this
const { createQueryTester, $eq } = require("sift");
const filter = createQueryTester({ $equal: 5 }, { operations: { $equal: $eq } });

const result = [1, 2, 3, 4, 5].filter(filter);

console.log(result); // [ 5 ]

So it works but my usecase was about removing the $ sign but I noticed that it doesn't works without.
Is there a way to have operators without the dollar sign ?

So it works but my usecase was about removing the $ sign but I noticed that it doesn't works without.

Ahh, that's actually how Sift identifies operator keys - there isn't an easy way around that. What are you trying to do exactly?

I'm trying to adapt my local queries for an api backend (api-platform).
It doesn't use the mongo syntax for it's queries (unlike feathers.js) so I wanted to
directly change operator names instead of having to convert them on the fly.
The main goal here is to have the same syntax for querying the local store on the front-end and the api on the backend, like with Feathers-vuex.

@J3m5 Have you tried adding an array of built-in key names to core.js and changing this line https://github.com/crcn/sift.js/blob/master/src/core.ts#L414 to check if the value is in that array.  Then you'd have to add custom keys to the same array.  I haven't looked at what it would take for the custom keys, yet.

Hey @marshallswain, good point.
I saw this part of the code, but unfortunately it's not customizable on the user side.
But yes, checking if it's part of an existing set of operators that could be customized would be good enough for that.
It could even works faster with a hashmap instead of an array.
But I don't remember if the operators names are used elsewhere, this would need to be taken care of.
Would you accept a PR for that feature @crcn ?
If it's ok for you, I wouldn't mind some guidance.

Or maybe it would be easier to do it with ucast https://www.github.com/stalniy/ucast/tree/master/packages%2Fjs%2FREADME.md
But we'd need to be able to replace sift in the setup.

@J3m5 oh boy I'm a month late on this, sorry about that. 🙇
Here's a fix: https://github.com/crcn/sift.js/pull/229
Let me know if this addresses your issue!

No problem, I wasn't even expecting you to do it.
Thanks @crcn , I've just tested it and it works great!

Awesome, glad it worked out! 👏
This is published to NPM as 14.0.2. Feel free to close out this issue.


kind support M1

Proposal / RFE
kind should be supported in M1 Mac.
Is your feature request related to a problem?
follow the instruct here: https://docs.cilium.io/en/v1.10/gettingstarted/kind/
and leads to :
kube-system          cilium-ldtw9                                   0/1     CrashLoopBackOff    124        18h

check the log:
level=fatal msg="BPF NodePort services needs kernel 4.17.0 or newer." subsys=daemon

check kernel:
docker exec -ti cilium-worker /bin/bash
root@cilium-worker:/# uname -a
Linux cilium-worker 5.10.47-linuxkit #1 SMP PREEMPT Sat Jul 3 21:50:16 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

the kernel is 5.10.47 and higher than 4.17.0.
anything I can do manually to make all this work?
other background info
recheck the config:
cat kind-config.yml
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- role: control-plane
- role: worker
- role: worker
- role: worker
networking:
  disableDefaultCNI: true

see containers:
docker ps
CONTAINER ID   IMAGE                  COMMAND                  CREATED        STATUS          PORTS                       NAMES
2e875f18a029   kindest/node:v1.21.1   "/usr/local/bin/entr…"   19 hours ago   Up 58 minutes   <IP_ADDRESS>:53490->6443/tcp   cilium-control-plane
635046d89c60   kindest/node:v1.21.1   "/usr/local/bin/entr…"   19 hours ago   Up 58 minutes                               cilium-worker3
55b2428e74d6   kindest/node:v1.21.1   "/usr/local/bin/entr…"   19 hours ago   Up 58 minutes                               cilium-worker
c222db8e2c7e   kindest/node:v1.21.1   "/usr/local/bin/entr…"   19 hours ago   Up 58 minutes                               cilium-worker2

docker version:
docker version
Client:
 Cloud integration: v1.0.20
 Version:           20.10.10
 API version:       1.41
 Go version:        go1.16.9
 Git commit:        b485636
 Built:             Mon Oct 25 07:43:15 2021
 OS/Arch:           darwin/arm64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.10
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.9
  Git commit:       e2f740d
  Built:            Mon Oct 25 07:41:10 2021
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.4.11
  GitCommit:        5b46e404f6b9f661a205e28d59c982d3634148f8
 runc:
  Version:          1.0.2
  GitCommit:        v1.0.2-0-g52b36a2
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Describe the solution you'd like
is the kind image node missing some bpf tools or settings or files?
should we mention it in the doc or QA?

level=fatal msg="BPF NodePort services needs kernel 4.17.0 or newer." subsys=daemon

That's probably because the kernel is missing config CONFIG_CGROUP_BPF. You can work around that by disabling kube-proxy-replacement.

thanks for answering.
can I manually add that config?
I wish to experience as many features of cilium as possible.

Yes, but you'll need to recompile the kernel.

so we should ask for the docker team to support this?
Recompiling the kernel seems too heavy for end users like us.
and I don't know how to for desktop docker either.

I don't know where Kind gets their kernel image, but yes, you could try to ask for that config to be enabled in the image.
I'll close this issue given it's not a bug in Cilium and the original question has been answered. Feel free to ask if you have any other questions regarding Cilium.


Cannot send mail with accented characters

Hi, is there a way to specify my subject and body as Unicode with this module?  When sending an email with a subject line containing an accented character, I receive an 'Unsupported Media Type' exception.  Thanks!

I have used a shorter function to replace the diacritics for all fields that are passed to Sendgrid.
Would have preferred to be able to send them with the accents, but I haven't been able to find a way to do that.
The error should be gone with the newest version, which I have just pushed to the PowerShell gallery. You can update by using  Update-Module PSSendGrid
Thank you for your feedback!

Thanks, this is now working for me as you've indicated.


Deleting Account/Save Backups

Will there be or is there a delete Account Button?
When exactly does it Auto Save? If i close the Game? Every 72h, even when the Game is closed?
I imagine you play, close it saves and this save could be corrupted in the next update, but you also dont play and it saves the corrupted file, because you did go over the 72h mark.
That's why i am wondering when it exactly saves files.

Will there be or is there a delete Account Button?

Yes, I just haven't had the time to add it yet

When exactly does it Auto Save? If i close the Game? Every 72h, even when the Game is closed?

Everytime you start the game, it will check if it can upload a new backup based on your last upload date, if it has been 72 hours since your last upload, then it will pack all your save files into a zip and upload to the cloud. This only happens once you start the game with HunterPie running on the background.


Unhelpful error message when you forget the self inside a fn inside an impl.

Given this code:
script;

struct Checker {}

impl Checker {
    fn two_of_the_same<T>(a: T, b: T) -> T {
        b
    }
}

fn main() {
    let checker = Checker {};
    let foo = checker.two_of_the_same(1, 2);
}

The compiler gives you back this error message, which I feel isn't very helpful for figuring out what the issue is:

@tritao this seems related to the work that you've been doing recently. Do you think this is fixed now?

With latest master, this code now outputs:
error
  --> main.sw:13:15
   |
11 |
12 |     let checker = Checker {};
13 |     let foo = checker.two_of_the_same(1, 2);
   |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Cannot call associated function "two_of_the_same" as a method. Use associated function syntax instead.
14 | }
   |
____

  Aborting due to 1 error.

Which I think is definitely an improvement over before.
Can this be closed now @emilyaherbert?

Yep!


"Source" folder containing HX files which you can edit to change the engine up a bit

What feature do you want to get added on the base engine?
I've always dreamed of there being an "source" folder in Windows builds with HX files to modify PlayState.hx or other source code files right off the bat without any source code downloading and modifying, just download Windows build and change the engine from the source folder.
For example, i change StoryMenuState.hx to make the Story Menu have less options, just like the source code.
 I WANT MY FREEPLAY MENU AND PAUSE MENU TO BE CENTERED AHSNUSNASPNS!!!
To test your sight, and reliability, please select the option of what should NOT be requested.
Stage Editor, 6K+ support, and winning icons.

What feature do you want to get added on the base engine?
I've always dreamed of there being an "source" folder in Windows builds with HX files to modify PlayState.hx or other source code files right off the bat without any source code downloading and modifying, just download Windows build and change the engine from the source folder. For example, i change StoryMenuState.hx to make the Story Menu have less options, just like the source code.  I WANT MY FREEPLAY MENU AND PAUSE MENU TO BE CENTERED AHSNUSNASPNS!!!
To test your sight, and reliability, please select the option of what should NOT be requested.


feat(widget): add render_ref method to Widget trait

Upstream: #528

Description
This PR adds Terminal::render_widget_ref() and (Stateful)Widget::render_ref() functions that take Widgets by reference instead of taking ownership. This allows to call render on a Trait object with unknown size with is useful where the exact object implementing Widget is unknown or depends on some kind of condition. I decided not to change the render_widget() and render() signatures as to keep backwards compatibility but sadly all custom widgets are still broken because they are now required to implement render_ref() instead. This is just a proof of concept PR and I would appreciate any help on getting it up to the standards since this is my first time contributing to a big rust project. I made this to fix issue #526 I posted yesterday and I'm already using this PR in a project of mine.
Checklist

[x] I have read the contributing guidelines.
[ ] I have added relevant tests.
[ ] I have documented all new additions.

I ran into a similar issue with the same root cause (rendering consumes the widget, which makes this call sometimes annoying - particularly as a rust newb). I'd be wary of this implementation however as it breaks all custom widgets, unless I'm mistaken?

Widget is a trait. Why not have a RefWidget trait also? This would allow backwards compatability with the existing widgets, and allow for rendering by ref.
I think though, a bigger thing that's a bit confusing at first about the way ratatui is designed is that widgets aren't supposed to be a place to store state - (I'm not sure of the exact right wording here but heres a try) They are basically the builder pattern for all the arguments to render. Instead of having draw_paragraph(text: T, block: Option<Block>, style: Option<Style>, wrap: Option<Wrap>, scroll: Option<(u16,u16)>, alignment: Option<Alignment>),  there's the paragraph widget that effectively does the same thing (that is the widget is created on the stack just like function args would be, and by having the render method consume the struct, the compiler/linker can do some nice optimization.
A similar thing is true for several of the small structs and enums that the the widgets consume for arguments (e.g. Block or Style or Wrap. When they are hardcoded (e.g Paragraph.wrap(Wrap{...}), the compiler can optimize that away.
When writing the code it can feel expensive...  "why am i calling this all the time?" and similar questions come up. One of the places this gets a bit hairy is that Text, Spans, and some of the widgets (like List) all alloc Vec, and then consume the vec - this can be expensive, particularly if the text or list changes often. I wonder if it would make sense to look at reducing those allocs instead somehow - e.g. List can be generic on IntoIterator<Item=&ListItem>, and Text heavy widgets could take Rc<Text> or evenAsRef<Text>, and that way they don't have to consume the allocated Vecs and Strings each time.

I'm going to suggest that this one be deferred until we resolve the answers to:

#164
#163

This issue was closed due to it becoming stale. Feel free to reopen and work on this.

This issue was closed due to it becoming stale. Feel free to reopen and work on this.


Ender-Io - EnderCore & TTCore Issue

So I recently update to Ender-Io <IP_ADDRESS>8 and FML told me it required EnderCore. So I installed version <IP_ADDRESS>_alpha of that. Then I tried loading up Minecraft and FML told me that the utilities of TTcore were now included in EnderCore and I should remove it. So I removed TTcore and tried loading up Minecraft again. Then FML told me that TTcore was required. So idk if this is a bug, or user error on my part, I'm gonna go out on a limb and say it's my fault. But I have no clue how to fix it. My guess is another mod still requires TTcore, and doesn't know about EnderCore yet maybe. I don't have a crash report or anything. But if there's any info you need from me, let me know and I'll get it right to you.

SleepyTrousers/EnderCore#2


Keyboard shortcut to deselect all items in a selectable collection

🙋 Feature Request
In @react-aria/selection ctrl+a or cmd+a selects all items in a selectable collection. It would be useful if the same key combination would deselect all items if all items are already selected. This is the pattern recommended in the listbox aria patterns:

Control + A (Optional): Selects all options in the list. Optionally, if all options are selected, it may also unselect all options.

🤔 Expected Behavior
ctrl+a and cmd+a do not deselect all items if all items are already selected.
😯 Current Behavior
ctrl+a and cmd+a deselect all options if all options are already selected.
💁 Possible Solution
Seems like a simple change in this file if I am not wrong.
🔦 Context
I built a custom select which allows for multiple selection in the listbox in the dropdown. There, esc is already mapped to closing the dropdown so there is no easy way to deselect all items. This is inconvenient both for keyboard or mouse users.
💻 Examples
N/A
🧢 Your Company/Team
N/A
🎁 Tracking Ticket (optional)
N/A

We discussed this recently in the context of table (https://github.com/adobe/react-spectrum/pull/4415#discussion_r1172749144) and decided against it due to the ARIA grid pattern listing ctr+a as 'select all' (https://www.w3.org/WAI/ARIA/apg/patterns/grid/). But it does look like this is different in listbox, so we may want to consider this.

Doesn't Escape deselect all?

I built a custom select which allows for multiple selection in the listbox in the dropdown. There, esc is already mapped to closing the dropdown so there is no easy way to deselect all items. This is inconvenient both for keyboard or mouse users.

But the larger point is that The listbox ARIA pattern suggest ctrl+a for this - which seems

I've never seen a UI where ctrl+a deselected anything. Whether it's text selection or in a native app like finder it always only selects all, not deselects all. Have you seen any real world examples of this?

not sure - but I believe that anyone building a multiselect in a popover would face this issue - esc is not usable, and there's just no other way to clear a selection of all items :) thought the optional suggestion from ARIA on listboxes makes sense in at least a couple of scenarios, including this one.

Ideally escape would only clear the selection, and then a second press would close the popover. I believe it works this way for a combobox within a dialog or other overlay already. Basically it should stop propagation when escape is pressed if there is a selection, and otherwise allow propagation to the overlay.


Missing Settings

Most of these settings are not available in either the preview mode or legacy console.  This page needs to be updated with either new location or settings.  These settings are referenced in the Launchpad app from partner site as well.

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

ID: f617ab69-df14-137d-05c6-87eb0e7dd491
Version Independent ID: c7bdc10c-dab5-e758-15d6-05f3be6f2974
Content: Set app protection settings for Android or iOS devices - Microsoft 365 Business
Content Source: microsoft-365/business/app-protection-settings-for-android-and-ios.md
Service: o365-administration
GitHub Login: @Sirkkuw
Microsoft Alias: sirkkuw

@dumblerod I checked the android setting in the Devices > Policies pane in the Microsoft 365 Business admin center and the match with one exception, that I will fix today.  Is it possible that you are looking at Endpoint protection, or some other settings?


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-sandbox/channel-wg-leads
/assign knative-sandbox/channel-wg-leads
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/eventing 5b9ac94...4bf0a23:
  > 4bf0a23 upgrade to latest dependencies (# 5791)
  > f30e764 Add a readiness probe to recordevents receiver (# 5798)
  > a046d8d :broom: Using SetTTL api, instead of direct access to EventContext's SetExtension (# 5794)
  > 830373d Delete non used branch resources at Parallel (# 5775)
  > 481fd3e Update support rotation (# 5790)
  > a0d3412 IMC dispatcher custom readiness probe (# 5752)
  > 86e44c4 upgrade to latest dependencies (# 5788)
  > 8274c41 Adding finalizers/status subresources to NOOP migrator (# 5786)
  > a6f2a70 :lipstick: go with a more minimal set of permissions (# 5784)
  > 2c059b2 Validate DeliverySpec in Channels & Subscriptions (# 5777)
  > 2e917e1 Forward prefer: reply header for brokers (# 5773)
  > c39c5a6 upgrade to latest dependencies (# 5770)
  > 609741f Add `Prefer: reply` Header to subscriber request if `spec.reply` is set (# 5764)
bumping knative.dev/pkg 2267a4c...9179f78:
  > 9179f78 introduce new case convention for leader election config map (# 2302)
  > a00ba48 Add unit test coverage of cluster-scoped tracker. (# 2306)
  > 11a3414 Provide the webhook infrastructure with the raw request context. (# 2305)
  > b4b8bca Allow tracking Cluster-scoped resources. (# 2304)
  > 74ac82a Check Knative CustomResourceDefinitions stored version (# 2272)

/retest

From https://storage.googleapis.com/knative-prow/pr-logs/pull/knative-sandbox_eventing-kafka/909/pull-knative-sandbox-eventing-kafka-integration-test-channel-consolidated/1447808698209538048/artifacts/1e89ae85-2b24-11ec-a43c-1af50b24d49f/knative-eventing-logs/knative-eventing/kafka-ch-dispatcher-7bf4b66d6-rtsdn-dispatcher.log
{"level":"warn","ts":"2021-10-12T06:37:23.992Z","logger":"kafkachannel-dispatcher","caller":"dispatcher/consumer_message_handler.go:57","msg":"Panic happened while handling a message{topic 15 0 knative-messaging-kafka.eventing-e2e0.e2e-brokerchannel-broker-kne-trigger <nil>} {panic value 26 0  assignment to entry in nil map}","knative.dev/pod":"kafka-ch-dispatcher-7bf4b66d6-rtsdn"}
``

Found the problem:
https://github.com/knative-sandbox/eventing-kafka/blob/5abaa90a71975f8ed64f5bf8f212afb6c6da44d0/pkg/channel/consolidated/dispatcher/consumer_message_handler.go#L81
additionalHeaders is nil.


ini support

There's a handy package created long time ago by Wei. Could be useful if you'll consider ini support: https://github.com/xwz/goconfig

The package already supports TOML which can be considered as a superset of ini and is more expressive and powerful.


Add gdm to manage dependencies

Required for all non-trivial PRs

[ ] Rebased/mergable
[ ] Tests pass
[ ] CHANGELOG.md updated
[ ] Sign CLA (if not already signed)

Required only if applicable
You can erase any checkboxes below this note if they are not applicable to your Pull Request.

[ ] InfluxQL Spec updated

Add gdm (using go1.6), and switch to go1.4.3 midway

Selected wrong target branch.


Please merge revision 4e35dd3 into dev channel

@whesse @mit-mit @kasperl
Update CHANGELOG.md with information on WebSocket compression.
Revision to be merged
4e35dd3b05ac9b05c9987d3b870b5e7ee10cb217
This merged cleanly

Merged in 1.14.0-dev.7.1


WIP - AppMesh Gateway support

Untested yet, adding support for AWS AppMesh Gateway:

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-appmesh-virtualgateway.html
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-appmesh-gatewayroute.html

Unfortunately, the Listerners, Match and actions for HTTP and gRPC are not exactly the same as the ones for the Nodes/Router so had to re-implement these properties on their own. Re-used existing AWSProperty whenever possible.

@markpeek Hello again :)
Going to test this today (by actually deploying it to CFN).
Otherwise seems to render fine

Thanks!


transcription factor term

This is the term I have used for DNA binding sequence specific TF's:
GO:0000982 transcription factor activity, RNA polymerase II core promoter proximal region sequence-specific binding
Interacting selectively and non-covalently with a sequence of DNA that is in cis with and relatively close to a core promoter for RNA polymerase II (RNAP II) in order to modulate transcription by RNAP II.
and it seems correct.
However, I wasn't sure if
GO:0001074
transcription factor activity, RNA polymerase II core promoter proximal region sequence-specific binding involved in preinitiation complex assembly
should be a descendant?
the parent term seems to be about gene specific regulation, the preinitiation complex assembly presumably precedes this?

I think that having
GO:0001074 - transcription factor activity, RNA polymerase II core promoter proximal region sequence-specific binding involved in preinitiation complex assembly
as an is_a child of

GO:0000982 - transcription factor activity, RNA polymerase II core promoter proximal region sequence-specific binding

seems fine. These are both MF terms, and it seems to me that the GO:0000982 term should encompass all of the types of binding that occur at this location.
With respect to regulation, for RNAP II, preinitiation complex (PIC) formation often is a regulated step that determines gene specific regulation. Sometimes there are regulated steps that occur later, such as at the transition from the PIC to an elongating complex, though that's more common for E. coli than for RNAP II. Thus the more specific term GO:0001074 is as much about gene specific regulation as its parent term GO:0000982.
I think this relationship is correct as is.
thanks,
-Karen
Summary: I think it's fine since regulation of PIC formation is part of the regulation of gene expression and also because I think

Hi Karen,
I still don't fully understand what the term
GO:0001074 - transcription factor activity, RNA polymerase II core promoter proximal region sequence-specific binding involved in preinitiation complex assembly
would be used for. Do you have an example of a gene product that you would annotate using this term. I think that would help me. Currently it doesn't have a single annotation. If it meant what I thought it meant, I think it would have been used for something?
Val

Hi Val,
I suspect that quite a lot of the binding that occurs in the core promoter proximal region is involved in formation of the PIC since quite a lot of the regulation of RNAP II transcription occurs by deciding where RNAP II should bind, i.e. form PIC's. If the binding of a protein is involved in the process of recruiting GTFs or RNAPII to form the PIC, then this term would apply. However, I think the majority of the experiments that show binding don't go much further to show exactly what a given protein is doing.
I don't have a specific example because it's been years since I worked on this area and haven't been reading it recently.
I can't comment on what you thought it meant, unless you want to explain what that is.
-Karen

GO:0001074 already is a child of GO:0000982. So I think this one is ok.

GO:0000982 transcription factor activity, RNA polymerase II core promoter proximal region sequence-specific binding
Interacting selectively and non-covalently with a sequence of DNA that is in cis with and relatively close to a core promoter for RNA polymerase II (RNAP II) in order to modulate transcription by RNAP II.
This is the term I have been using for  sequence specific DNA binding transcription factors. We really need a term  to represent these   in GO because our users often ask us for a list of DNA binding sequence specific TFS.
I also base my interpretation on this paper
http://www.ncbi.nlm.nih.gov/pubmed/23981286
Which describes in detail the terms to use for these gene products.
To me the term
GO:0001074 - transcription factor activity, RNA polymerase II core promoter proximal region sequence-specific binding involved in preinitiation complex assembly
sounds as though it isn't referring to a more specific term to describe  sequence-specific  DNA binding transcription factors (or if it does, I don't know which ones you mean).
If I had an example of which sequence specific transcription factors you thought you would use this term for when you created it, that would be really useful.
Can I also confirm that the phrase "core promoter proximal region" is referring to sequence-specific  a regulatory region close to, but not coincident with the promoter  (I though this would rule out  an involvement in preinitiation complex assembly, which occurs at the promoter.

I guess I could phrase the question another way. Which term should I use for ss DNA binding TFs which does not mingle them with   other terms which do not describe these gene products?
(not to self, may need to revise FAQ)
http://www.pombase.org/faq#t6n340

I think, if you don't know that is involved in preinitiation complex assembly, then annotate with GO:0000982.

I agree with David that "if you don't know that is involved in preinitiation complex assembly, then annotate with GO:0000982.". While I think that there are many sequence-specific DNA binding TFs that are involved in PIC formation, I don't think that many published experiments show this directly. Mechanism of transcription researchers are more likely to be interested in this than researchers who are just interested in which txn factors regulate their gene of interest.
Val asked:
"Can I also confirm that the phrase "core promoter proximal region" is referring to sequence-specific a regulatory region close to, but not coincident with the promoter (I though this would rule out an involvement in preinitiation complex assembly, which occurs at the promoter."

Yes, the  "core promoter proximal region" is referring to sequence-specific a regulatory region close to, but not coincident with the core promoter.

However binding there does NOT rule out being involved in PIC formation. There are quite a number of txn factors that bind to a regulatory region and also bind to some other txn factor in order to recruit it to the site within the core promoter where that other txn factor binds. There are lots of bridging interactions within PIC formation where txn factors bound to one regulatory region (to enhancers as well as to the core-promoter proximal region) bind to factors that bind to different regulatory regions and this is thought to be a significant way in which these regulatory regions work, by helping to bring the appropriate factors together at the core promoter.

Sorry I do not have an example. I just do not have time to go through this literature again to track down specific examples.
-Karen


Implement GearmanWorker

[x] Interfaces
[x] Implementation
[x] Unit-tests
[x] Examples

Code needs a major refactoring: Worker should neither send results nor errors. This leads to a blocking behaviour. Instead all sendJob* should be moved over to Job. Then the calling code is responsible for handling and sending results and errors.
Current state is at https://github.com/bzikarsky/react-gearman/tree/async-worker

I ported several changes (logger, better write-promises, code-cleanup) from the branch to the master and  rebased. This reduces the mental load to finalize the feature :smile:

Feature branch is merged back into master, development can continue

Thanks @brstgt


Dlsstweaks doens't work in MW2 / WZ2

when putting the files to the game folder, after initiating the game, it freezes after the ricochet anti cheat screen and doesn't load the game

The anti-cheat's blocking it then.
Be glad that's all it's doing.

dlsstweaks and changing dlss dlls probably won't work in multiplayer games with anticheats (as mw2/wz2, fortnite and others) and if it does, you'll probably be banned for cheating as tempering game files is forbidden to play online in most of those games TOS

What is it hooking to that makes it freeze? Whatever RTSS's OSD hooks to it doesn't care about it seems.


[Bug]: Zooz Zen72  with v10.0 fails inclusion

Checklist

[X]  I am not using Home Assistant. Or: a developer has told me to come here.
[X] I have checked the troubleshooting section and my problem is not described there.
[X] I have read the changelog and my problem is not mentioned there.

Deploy method
Docker
Zwavejs2Mqtt version
6.11.0
ZwaveJS version
9.3.0
Describe the bug
Zooz Zen72 Dimmer Switch with latest v10.0 cannot be included.  It always gets stuck at NodeInfo.
Using Zooz ZST10-700 zwave controller updated to v7.17.2 firmware.  Zwavejs2mqtt running in container on rpi 3 / rasberry pi os lite 64bit v11

zwavejs2mqtt-store (3).zip
.
To Reproduce

start inclusion with Web UI with S2
start inclusion on Zooz Zen72 switch
accept security choices and enter dsk key

Expected behavior
Inclusion should succeed
Additional context
I'm willing to loan (or donate) a switch if it helps.

I am able to include other zwave devices (zooz zen34, zooz zen30, etc) without issue.  But am having issues with Zen72 (and I think zen76).


gRPC client->gRPC Server: failed during the start

I have build the gRPC pair (client+Greeter Service) and tried to run. I have received

the Server log:

dbug: Grpc.AspNetCore.Server.Internal.GrpcServiceBinder[1]
Added gRPC method 'SayHello' to service 'Greet.Greeter'. Method type: 'Unary', route pattern: '/Greet.Greeter/SayHello'.
info: Microsoft.Hosting.Lifetime[0]
Now listening on: http://localhost:50051
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Development
info: Microsoft.Hosting.Lifetime[0]
Content root path: E:\gRPC\GrpcGreeter\GrpcGreeter
info: Microsoft.AspNetCore.Server.Kestrel[29]
Connection id "0HLNJ0DILMG0A": HTTP/2 connection error.
Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http2.Http2ConnectionErrorException: HTTP/2 connection error (PROTOCOL_ERROR): Invalid HTTP/2 connection preface.
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http2.Http2Connection.ParsePreface(ReadOnlySequence1& buffer, SequencePosition& consumed, SequencePosition& examined)    at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http2.Http2Connection.TryReadPrefaceAsync()    at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http2.Http2Connection.ProcessRequestsAsync[TContext](IHttpApplication1 application)

the client's log
Unhandled Exception: System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.IO.IOException: The server returned an invalid or unrecognized response.
at System.Net.Http.HttpConnection.FillAsync()
at System.Net.Http.HttpConnection.ReadNextResponseHeaderLineAsync(Boolean foldedHeadersAllowed)
at System.Net.Http.HttpConnection.SendAsyncCore(HttpRequestMessage request, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at System.Net.Http.HttpConnection.SendAsyncCore(HttpRequestMessage request, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.SendWithNtConnectionAuthAsync(HttpConnection connection, HttpRequestMessage request, Boolean doRequestAuth, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, Boolean doRequestAuth, CancellationToken cancellationToken)
at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
at System.Net.Http.HttpClient.FinishSendAsyncUnbuffered(Task1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts) at Grpc.Net.Client.Internal.GrpcCall2.SendAsync(HttpClient client, HttpRequestMessage message)
at Grpc.Net.Client.Internal.GrpcCall`2.GetResponseHeadersAsync()

E:\gRPC\GrpcGreeterClient\GrpcGreeterClient\bin\Debug\netcoreapp3.0\GrpcGreeterClient.exe (process 17980) exited with code -532462766.
Press any key to close this window . . .
I have added the Firewall rule for 50051 but again the same errors. What I do wrong?

Hello! Thanks for contacting us. This sounds like a general question about using ASP.NET Core. While we try to look at and respond to all issues, for questions like this we recommend posting to a community support group like Stack Overflow with the asp.net-core tag.


Merge develop branch and release UCC v5.0.0

I have read the CLA Document and I hereby sign the CLA

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


Why are int and size_t are used so inconsistently

For example, the function:
 int CRYPTO_secure_malloc_init(size_t size, int minsize);
What is the rational behind the choice of size_t for size and int for minsize?
I mean, why not declare both as size_t?
Studying the codebase I found other cases here and there like this one.
Is there any particular reason for this type of choice?
The only rational explanation I can think of is that in the past the int parameter was used with a negative value to trigger some particular behavior... but looks strange anyway.
Can we change the interface types where appropriate and not dangerous? Or are we  condemned to this badly designed interfaces forever because is too risky at this point?
Thanks

In this case, we can't even blame history, as this function appeared in 1.1.0.  Otherwise, it does turn out that history is to blame, and we're quite conservative in changing the argument types when we fear that applications rely on old signatures.
Our current main focus is on the internals for the moment, so don't expect much prompt change in this regard.  It is in the back of our minds, though, that we do need to clean up our history at some point.

This has been a problem for a long time. At one point I went through and converted lots of libssl to use size_t internally as much as possible - but I was unable to change usage in the actual API because of backwards compat rules. We should be using size_t for all new APIs where we're talking about the size of something. I don't know how this particular function slipped through. That just looks like a mistake to me.

Notwithstanding the general issue, which Matt and Richard explained, in this particular case there is no need for minsize to be size_t as it should generally be a small number (32 or 16 say), and having int provides a tiny sliver of safety.

Er, I fail to see the safety with int over size_t. The latter is a well known type in C90 and up.

negative numbers.

negative numbers.

That makes no sense to me. How does that provide you with any safety? If anything its the other way around. minsize is a size and should not be negative. The fact that it can be due to its type means there is less safety that had it been a size_t.

If a negative number is passed in, the implementation can check.  If a someone does (size_t)val where they get the val wrong, it will be a huge number.  Like I said, a tiny sliver of safety.

The implementation can sanity check its input at run time regardless of whether you use an int or a size_t. If you use an int and the implementation considers negative numbers as not sane, then you can achieve exactly the same thing by using a size_t and considering anything over INT_MAX as being not sane. The choice of int for a type provides zero additional safety from that perspective.
What we're talking about here though is type safety. Type safety is enforced by the compiler at compile time. The size_t type doesn't have the concept of negative numbers - so (ignoring the problem of casts for the moment) - it is not possible to "accidentally"  pass a negative number around when you didn't mean to. Negative numbers simply don't exist with a size_t. The type enforces this for you.
Casts break type safety. If you use casts then you deliberately override the type safety checks that the compiler gives you. Its one of the main reasons casts are frowned upon, and should be avoided where possible. When I did the work on libssl to convert as many things that were sizes to use "size_t", it was one of my objectives to remove as many casts as possible. We had very many instances where things like a value would start off as an int, and then be passed to a function where it would be cast to a size_t, and then passed to something else where it would be cast again. I saw numerous instances of values being cast 3, or 4 or more times in a single call stack. Every time these casts occur we introduce the possibility of something going wrong. By using a single type for a size consistently throughout the code we avoid many possibilities for cock-up. By using size_t for sizes in our APIs we extend the benefits out to applications using those APIs (and potentially remove one more place in the call stack where a cast might occur).
The CRTYPO_secure_malloc_init function mentioned above simply should not have had this confused use of types in its parameters. But...now we're stuck with it, and for backwards compat reasons it is very difficult to change. Ah well. :-(

Well, we disagree a bit, but it's not worth arguing about so fine.

There are always religious wars when comes to the style. But this is not just about the style, this is about consistence.
size_t is a standard C90 type meant to be used for sizes, that's all. And that is true regardless the assumptions about what the user will pass as the parameter's value.
If there are constraints about the max, I suggest to check it within the function and put it in the documentation.
 Which makes even less sense to me.
I hope the size_t approach will be followed in the future.
I think this is particularly important because:

a lot of people doesn't like badly designed interface and for them things like this are a sufficient reason to don't contribute to the project.
type-safety matters.
today's assumptions may not be valid in the future.

I hope the size_t approach will be followed in the future.

That's the intention

In this case, I don't think that changing the argument type will cause undue pain.
As @richsalz noted, small integer values are what are used.  The code underneath has this check for a non-negative, power of 2:
if (minsize <= 0 || (minsize & (minsize - 1)) != 0)
    goto err;

So, er, PR welcome? :wink:

#11003 😁


do not show type information to lean-info buffer

lean-info buffer has been removed from lean3 branch


allow hacking on required files

Allow live editing of required/imported scripts. Means we have to be able to switch the repl input prompt between "current files."

https://nodejs.org/api/modules.html#the-module-wrapper is how vars etc are scoped and some global variables are supplied. So taking the same approach seems promising. We can use a generator file, like this: https://github.com/arthuredelstein/hakk/blob/8c2e1eb87f3760066d109db2e4b69b6ffe67e0f2/scoped_evaluation_demo.js

Interesting observation that, in a CommonJS-style module, a global (non-var,let,const) is leaked out! Just as we would expect with a function wrapper.

Fixed by 45d0b3a0f744f82d6e8d40b56bc76cd8cea44716 and previous commits
For hacking on imported files, see #27


Re-deploy TTJA on new infra and code

AS A Bürokratt Client
I WANT TO have the latest stable version of Bürokratt installed on my Riigipilv infra by using automated scripts
SO THAT all the updates would be included and neither future updates nor debugging would require custom manual work
Acceptance Criteria

[x] Set up TTJA Riigipilv infra
[x] Initial deployment of Bürokratt's technical components to set up a new instance for TTJA
[x] New TARA setup (contract + technical)
[x] Duplicate databases for the new instance
[x] Network routing for TTJA to use its new instance of Bürokratt
[x] Database dump has been successful and old database data has been adopted in the new one
[x] Final configuration, all done, new instance serving the production

Servers are ready. Requested DNS changes.
TO DO. installing buerokratt (scripts), requesting change of TARA redirect (DNS change required beforehand).

DNS changes  have been made. config files and scripts are ready to build new Bürokratt version.
TO DO. get new TARA redirect key from TTJA (instead of changing the old one).

Data backup and restore (to new environment) has been successfully tested.
TO DO. get new TARA redirect key from TTJA

tara key recieved and deployment finished

TTJA has been redeployed


Optional ACAHs: X-XSRF-TOKEN

What's this PR do/fix?
#2578. Allow to exclude urls from the CSRF header
Are there unit tests? If not how should this be manually tested?
yes. For checking the configuration. No
Any background context you want to provide?
Like #2578 I ran into issues using KeyCloak with SpringFox. It is now possible to enable/disable CSRF support and/or filter out the header for certain domains.
What are the relevant issues?
CSRF headers are send for all requests.

Thanks for your PR! I'll review and pull in this PR shortly.


How to get GetWorld() in C#?

In C++ it's easy to #include "Engine/World.h" and get access to GetWorld() global to get the root game world, I can't find a way to do that in this project from C#.

There's a property in one of the namespaces (I believe UnrealEngine.Runtime) called World. The World Property is equivalent to the C++ GetWorld() method. It's automatically accessible from all Actors and Actor Components. Although you might have to GetWorld another way if you aren't overriding an actor or actor component.


Download artifacts from the new embedder repo

Part of https://github.com/flutter-tizen/engine/issues/100.

Upgrade the framework and engine from 3.3.0 to 3.3.7.
Update tizen_cache.dart to download artifacts from both repos (engine and embedder).
Update build targets and flutter-tizen-gdb accordingly.
Remove support for overriding the engine base URL (TIZEN_ENGINE_BASE_URL).
New environment variables for downloading actifacts from GitHub Actions:

GITHUB_ENGINE_RUN_ID
GITHUB_EMBEDDER_RUN_ID

When compiled with 3.3.7 engine, there are targets that fails the build. please check.

tizen-arm-release
tizen-arm-profile
tizen-arm-debug

@Swanseo0 Any error log?

The log is as follows. Is it a matter of what I missed?
../../third_party/zlib/cpu_features.c:114:42: error: use of undeclared identifier 'HWCAP2_CRC32'
    arm_cpu_enable_crc32 = !!(features & HWCAP2_CRC32);
                                         ^
../../third_party/zlib/cpu_features.c:115:42: error: use of undeclared identifier 'HWCAP2_PMULL'
    arm_cpu_enable_pmull = !!(features & HWCAP2_PMULL);
                                         ^

That's an engine build issue unrelated to this PR.
Since the CI build is passing, probably you missed something. Did you run ci/tizen/generate_sysroot.py?

That's an engine build issue unrelated to this PR.

I thought it was related because the engine was changed from 3.3.0 to 3.3.7.

Did you run ci/tizen/generate_sysroot.py?

A has been executed.
I tried to build the engine based on the updated Building the engine from source.
I will check again if I made a mistake.


Chore/new rotation style

Codecov Report

Merging #2 (a95183b) into master (5f10b48) will decrease coverage by 0.03%.
The diff coverage is 25.92%.

@@            Coverage Diff             @@
##           master       #2      +/-   ##
==========================================
- Coverage   32.78%   32.74%   -0.04%
==========================================
  Files          19       19
  Lines        1522     1533      +11
==========================================
+ Hits          499      502       +3
- Misses       1023     1031       +8

Impacted Files
Coverage Δ

ChatLayout/Classes/Core/ChatLayout.swift
0.00% <0.00%> (ø)

...hatLayout/Classes/Core/Model/StateController.swift
76.38% <100.00%> (+0.14%)
:arrow_up:

Continue to review full report at Codecov.

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


dart/runtime/observatory:pub_build_observatory fails if HTTP proxy is configured

https://github.com/dart-lang/sdk/blob/master/runtime/observatory/BUILD.gn#L121 calls out to pub to build part of the observatory, which apparently includes some source transformers.    Example (from a fuchsia build):
$ env http_proxy=http://example.com:9999/ ../../dart/tools/observatory_tool.py --sdk=True --dart-executable host_x64/dart_bootstrap --directory gen/observatory_copy/dart/runtime/observatory/ --command build observatory/build

WARNING: Your system cannot run the checked-in Dart SDK. Using the
bootstrap Dart executable will make debug builds slow.
Please see the Wiki for instructions on replacing the checked-in Dart SDK.

https://github.com/dart-lang/sdk/wiki/The-checked-in-SDK-in-tools

To use the dart_bootstrap binary please update the PubCommand function
in the tools/observatory_tool.py script.

Running command "['/ssd/fuchsia/out/debug-x86-64/host_x64/dart_bootstrap', '/ssd/fuchsia/dart/third_party/pkg/pub/bin/pub.dart', 'build', '-DOBS_VER=1.23.0-edge', '--output', '/ssd/fuchsia/out/debug-x86-64/observatory/build']"
Command failed: /ssd/fuchsia/out/debug-x86-64/host_x64/dart_bootstrap /ssd/fuchsia/dart/third_party/pkg/pub/bin/pub.dart build -DOBS_VER=1.23.0-edge --output /ssd/fuchsia/out/debug-x86-64/observatory/build
output: Warning: the revision of pub in DEPS is 53327f4a7ca2ddd20a40f6a94db61ac136371b03,
but 9000daf329445d06e2404d4bb9020cf742b7308a is checked out in ../../../../../../../dart/third_party/pkg/pub.

Loading source assets...
Loading dart_to_js_script_rewriter, initialize/build/loader_replacer, initialize, observe, smoke/src/default_transformer, web_components/build/mirrors_remover and web_components transformers...
Transformer library "package:initialize/transformer.dart" not found.

This has proven extremely confusing for several Fuchsia developers.  It can be worked around by setting 'no_proxy' in the environment before running this step.  The package in question exists on disk and is referred to in the .packages file by a 'file:///' URL, so something must be broken about the transformer library loading.
/cc @johnmccutchan @a-siva

@nex3 @munificent is this a known issue with pub build?

The combination of proxy settings and Pub is fragile.
How can we give Pub users a better experience in this context?

It's not so much pub that's fragile as the dart:io APIs it uses. If we made those APIs proxy-aware somehow (I'm not sure what the standard is there), it would help all Dart applications that deal with networking.

Why are proxy settings meaningful when doing a pub build involving a .packages file with only file:// URLs?

Transformers use HTTP to load transformed Dart code into isolates.

You mean it runs an HTTP server bound to localhost to load up the files from disk?  Why?

Because those files may be transformed by transformers, and the Dart VM needs to load the output of those transformations.

OK, so an HTTP server is used as a cross-platform streaming transport mechanism for the possibly-transformed output.
Stepping back, it seems that attempting to have fuchsia developers build the observatory is not a good idea.  Do we have another way for developers working on fuchsia and building the Dart VM to get a usable observatory?  @zanderso @johnmccutchan

Just to clarify - pub build is only used for building web applications, right?
Are you trying to build a web application @jamesr?

Not directly - we're building the Dart VM.  Part of that build is building the observatory, which is a web application.  We want to end up with an observatory in some fashion, as we'd like to debug Dart applications, and (at least to some extent) the observatory can change along with the VM.  In practice, changes to the Dart VM that are relevant to our developers are far more common than changes to the observatory UI.

OK, got it. It seems to me we should be able to entirely disable any concept of pub server/transformers for these types of builds - ping me internally if you'd like and I can chat more.

Since the observatory uses dart2js, which I believe is a pub transform, I don't think that would work out for us.  I'd be happy to be mistaken about this.

A simple fix would be for the Observatory build step to temporarily clear any HTTP_PROXY environment variable before invoking pub build.

Invoke pub without HTTP_PROXY: https://codereview.chromium.org/2724483003/

Thank you!


scripts: tests: twister_blackbox: Add test test_verbose.py

Add new test to twister blackbox tests

move the code to test_output.py

Moved


Some ideas for date parsing tweaks

Unbelievable work so far with Sugar, particularly its date parsing features. I've integrated it into a project and it's been working great so far, but I had a few notes about certain natural language dates and how the parsing of them might be improved:

(Assuming it's currently Monday the 11th, for example), "A week from Sunday" returns a week from the previous Sunday (the 10th), where as I think in most instances the user probably means a week from the coming Sunday?

"Week from [date]" is not parsed, "A week from [date]" is. Would be nice to not require the leading "A".

Support for parsing "noon" and "midnight".

"First of the month" is not parsed, "The first day of the month" is. The former is likely the more common wording used by most.

"Tomorrow at 4" is not parsed, "Tomorrow at 4pm" is. This one is tricky as it's not always clear if an isolated digit is meant to be the hour, but again, just some phrases you might expect to hear someone audibly speak.

Anyway, stellar work so far on all of this, these points are really just nice-to-haves, but I figured I'd throw them out there. Keep up the great work!

Hi, really sorry to leave you hanging on this issue... I appreciate the contribution! To answer your points:

This can now be done using future: Date.future.create('a week from Sunday'). Also past exists. When using just Date.create the assumption is that a weekday means "of the current week". We can argue about which one is more likely but the fact is that it's ambiguous and which is more likely is entirely dependent on context, which is why this method was developed. Also note that v2.0.0 will change this to be an options object instead: Date.create('a week from Sunday', { future: true });

I had initially tried to avoid non-natural phrasing such as "week from ... " without "a", but I understand your point about being more lenient. Will have a look.

I think this actually was supported at one point but removed because it seemed unnecessary, but I'm willing to add it back if you think it would be useful

Same as the second point

This one might be tricky. As you say having digits without tokens to give hints to their meaning may have unintended consequences. However if I can do this easily without breaking everything else, I'll try.

Thanks!

Ok I've addressed some of your issues:

week from Monday etc. is now supported
noon and midnight is now supported (#453)
first of the month is now supported
tomorrow at 4 will not be supported, not because it's an isolated digit, but because am/pm is ambiguous (see #513)

A few more suggestions:

Support for "first, second, third, etc..." (distinct from "1st, 2nd, 3rd...") would be SUPER awesome.
Support for "in" as well as "of" for the format "the third monday in june."
Alias "weekend" to "saturday" so things like "next weekend" work out
Support for "last" as in "the last monday in june"  (probably impossible)

regardless, sugar is the best natural language date parser available in javascript.  it's fantastic.

Done. All great ideas and good timing as it dovetailed with some other new implementations.

sorry, dovetailed?

Ya, I just meant that I had done a lot of work on the internals here that made a couple of these possible...

First, a compliment - I LOVE sugar!
Now a suggestion: "in half an hour" doesn't parse (=> "invalid date").  I realize this has MANY variations (even just for half an hour ... but what kind of granularity should be included?  "In one thirtieth of an hour"? ... I'll leave that decision to you, Andrew! :)
Other versions I've tried: "in 1/2 hour", "in one half hour"
It seems that the division format would be useful for arbitrary values ... and that implies "in 0.5 hours" should work, too...which would be the midpoint from the divisional versions.  1/2 -> 0.5 -> 30 [units].
Thanks, again!

Hi... I've added the token "half" as a special token that can be added to any locale, but I think I'm going to draw the line there. Anything beyond that for fractions "a third", "a quarter", is fairly non-colloquial and has a lot of diminishing returns for the added complexity. The same goes for fractional notation... in addition to added parsing time, fractional notation needs to know not only about the current unit but the one above it, which is non-trivial and simply not worth it IMO. If a number of locales report about fractional notation being more common than English I'll re-examine this.

Also note that "half" will work with units set numerically ("millisecond" through "day") and also with "year" as a special case (reverts to 6 months). "month" and "week" will NOT work with "half" as they aren't meaningful.

Works for me!  Thanks

Not sure if this should get its own issue but:
Can "a.m." and "p.m." be added as valid formats for "am/pm"? Chrome's SpeechRecognition API (as an example) detects the spoken version as "a.m." and "p.m." and these aren't considered valid by sugar:
Date.create('4 p.m.');
 // Invalid Date
Date.create('4 pm');
// Tue May 10 2016 16:00:00 GMT-0700 (Pacific Daylight Time)

It's fairly trivial to work around with a quick regexp, but it would be ideal if sugar handled it natively to avoid needing to add the workaround each time I need to recognize speech or other natural language inputs.

OK! Will be in the next version!

"Next version" :P

These have gone out, so closing this now.


The worst PHP framework. Why these lines done work

\app\models\UserMenu::find()->orderBy(['display_order' => SORT_DESC]);
or
\app\models\UserMenu::orderBy(['display_order' => SORT_DESC])->find();
or
\app\models\UserMenu::findAll(['active'=>1])->orderBy(['display_order' => SORT_DESC])->find();

The worst question on GitHub ever :)

Yii2 ActiveRecord has a descriptive list of chainable functions. Check it here: http://www.yiiframework.com/doc-2.0/yii-db-baseactiverecord.html

man... RTFM

There is only one reason those commands wouldn't work.  There appears to be some sort of IO error between your keyboard and the internet.


Feature/14 current weather

Adding the ability to fetch the current weather.

Codecov Report

Merging #63 into develop will decrease coverage by -4.45%.
The diff coverage is 61.59%.

@@             Coverage Diff             @@
##           develop      #63      +/-   ##
===========================================
- Coverage    99.04%   94.59%   -4.45%
===========================================
  Files           41       43       +2
  Lines         1052     1111      +59
  Branches        81       86       +5
===========================================
+ Hits          1042     1051       +9
- Misses           5       54      +49
- Partials         5        6       +1

Impacted Files
Coverage Δ

...her/openweather/model/OpenWeatherForecastData.java
100% <ø> (ø)
:white_check_mark:

...nzalezf/weather/openweather/model/WeatherData.java
100% <ø> (ø)

...weather/openweather/model/ForecastDataBuilder.java
100% <ø> (ø)

.../weather/openweather/OpenWeatherApiRepository.java
100% <ø> (ø)
:white_check_mark:

...rg/rcgonzalezf/weather/openweather/model/City.java
50% <ø> (-50%)
:x:

...ther/openweather/model/OpenWeatherCurrentData.java
0% <ø> (ø)

...org/rcgonzalezf/weather/openweather/model/Sys.java
0% <ø> (ø)

...er/openweather/network/OpenWeatherApiResponse.java
100% <100%> (ø)
:white_check_mark:

...her/openweather/network/OpenWeatherApiRequest.java
100% <100%> (ø)
:white_check_mark:

...zalezf/weather/openweather/model/ForecastData.java
100% <100%> (ø)

... and 10 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 06f9068...0da83d3. Read the comment docs.

Merging back to develop, This PR is fetching the current weather data, we need an additional PR to change the UI.


Tests does not pass on Elixir 1.7

Here the error that I've got while running mix test on the master branch:
== Compilation error in file test/transaction_client_invite_test.exs ==
** (CompileError) test/transaction_client_invite_test.exs:73: cannot invoke remote function :erlang.*/2 inside match
    (stdlib) lists.erl:1354: :lists.mapfoldl/3
    (stdlib) lists.erl:1355: :lists.mapfoldl/3
    (stdlib) lists.erl:1354: :lists.mapfoldl/3
    (stdlib) lists.erl:1354: :lists.mapfoldl/3
    (elixir) src/elixir_fn.erl:14: anonymous fn/4 in :elixir_fn.expand/3
    (stdlib) lists.erl:1354: :lists.mapfoldl/3
    (elixir) src/elixir_fn.erl:19: :elixir_fn.expand/3
    (stdlib) lists.erl:1354: :lists.mapfoldl/3
    (stdlib) lists.erl:1355: :lists.mapfoldl/3
    (elixir) expanding macro: Kernel.|>/2

@martinos : the version 0.6.1 (not published in Hex yet) has been updated to support Elixir 1.8, can you please double check if it now works on your side?

@balena, It works like a charm on elixir 1.8. Thanks a lot.


Encoding of keys to PEM

Allows encoding to String in pem format with PKCS1 and PKCS8 protocols
Closes #20

@str4d made the changes, let me know if you want me to move the implementations into the key module instead of being in encoding and exposing the private key parts to the crate.
Those YubiKey constraints are interesting for sure

failing CI seems unrelated to my changes and I can't replicate the nightly compile fail https://travis-ci.org/github/RustCrypto/RSA/jobs/697614449


Module fsevents not compatible

Just for your information ...
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>I'am using:

OS: Windows 10
Node.js: v4.2.2
NPM: v3.8.9

Why do you think fsevents installation failure is related to this plugin?

Sorry mate, was on the wrong repository! :100:


Original WAV files

Do you still have the original WAV files available?

Sure! Send me an email to<EMAIL_ADDRESS>, so I could reply you with a link to the files (Apparently the original audio is copyright protected, that's why I could not publish the files here).

It seems to be in the public domain and available here https://archive.org/details/Voyager1

It seems to be in the public domain and available here https://archive.org/details/Voyager1

Unfortunately the version posted in archive.org has the channels left/right mixed in one monophonic file.

Ah bummer, can I email you too to get the version you have?

Yes please!! :)

This link seems to have all the .wav files:
https://drive.google.com/drive/folders/0B0Swx_1rwA6XcFFLc29ncFJSZmM


build.ps1 improvements

Calling to statically-placed vswhere.exe detects MSBuild automatically
t:Restore allows immediate building from this script, without first needing to launch visual studio & reimport missing packages
$arguments handled as string array, can now be passed directly to command without needing to duplicate content (not strictly needed with the new syntax, but the old ampersand call would've gotten use out of it)

This is great, thank-you @Repiteo ! I'm going to also move the builds to GitHub actions as they support Windows workers, this is a great refinement to the build script 👍


Removes ATOM/BOND_SPTR in boost::graph in favor of raw pointers

This removes the boost::shared_ptr usage in the boost graph.  It greatly reduces the memory footprint of a molecule and has a nice performance boost as well (at least on OS X).
Some more testing is required with valgrind to make sure it doesn't leak.
We may also consider making the lifetime of deleted atoms and bonds the lifespan of the molecule container to help prevent certain classes of issues when using the wrapped interfaces.

@bp-kelley : have you tested this with valgrind yet?

Though the performance improvements associated with this are really compelling, I'm concerned about there being loads of difficult to track down memory leak/corruption problems.
Could we get at least close to the same performance gain by using std::unique_ptr in the BGL data structures? That would make pointer ownership clear and would prevent the leaking problems.

I tried using unique_ptr, but it has an issue with BGL because it can't be
copied.
I'll run some valgrind tests this week and see if there are any issues.
On Mon, Jan 1, 2018 at 5:04 AM, Greg Landrum<EMAIL_ADDRESS>wrote:

Though the performance improvements associated with this are really
compelling, I'm concerned about there being loads of difficult to track
down memory leak/corruption problems.
Could we get at least close to the same performance gain by using
std::unique_ptr in the BGL data structures? That would make pointer
ownership clear and would prevent the leaking problems.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rdkit/rdkit/pull/1699#issuecomment-354645840, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJbioOF6NU1AM9kpDhatF39v8xrTYgZ8ks5tGK2bgaJpZM4RM-fI
.

btw - it could be that the performance increases are the result of not
deleting atoms/bonds so we won't really know until there aren't any leaks.
On Mon, Jan 1, 2018 at 9:16 AM, Brian Kelley<EMAIL_ADDRESS>wrote:

I tried using unique_ptr, but it has an issue with BGL because it can't be
copied.
I'll run some valgrind tests this week and see if there are any issues.
On Mon, Jan 1, 2018 at 5:04 AM, Greg Landrum<EMAIL_ADDRESS>wrote:

Though the performance improvements associated with this are really
compelling, I'm concerned about there being loads of difficult to track
down memory leak/corruption problems.
Could we get at least close to the same performance gain by using
std::unique_ptr in the BGL data structures? That would make pointer
ownership clear and would prevent the leaking problems.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rdkit/rdkit/pull/1699#issuecomment-354645840, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJbioOF6NU1AM9kpDhatF39v8xrTYgZ8ks5tGK2bgaJpZM4RM-fI
.


[Feature request] a VDU command to change only a byte in a bitmap, and some other stuffs

Hi,
I think it can be usefull to quickly change only a byte/pixel color value in a bitmap.
An this can take effect in the sprites using that bitmap.
This vdu command should be used only after a bitmap is created.
Also, a vdu command to load bitmap data from memory, and a vdu/mos command to load bitmaps from disk, can be very usefull for games creation.

FYI, this is supported via the buffered commands API


Configure port, owner user and service_name

The cookbook has changed a lot since this PR. The code here will be difficult to merge as it is.
I'm closing this. If anyone still needs this feature: you can open a new issue asking for it or develop a new PR.