MaoRoulette challenge not working if there are some rules set up for it

When you have some rules set up for the task it will not load, there are messages like "Oops! Unable to fetch map-bounded tasks" , "Failed to release task lock. Your lock or your session may have expired", "Unable to retrieve latest challenge data from server", "Unable to fetch a task to work on".

If you remove the rule, challenge works without errors. This started happening a week ago, since then everything was working with rules set up. Can you investigate what is the issue?

This doesn't appear to be reproducible locally and may be prod specific.  Can you provide a specific challenge/task?  Thanks.

This may have been due to the outages during that period of time.  If you do see this issue spring back up, feel free to re-open.  Thanks for reporting!


Live debugging

-d / --debug
This option will let you peek in the stash or run IPython on the current step.
Commands

s: prints stash
d: opens Interactive Python.
h: prints commands
In Python shell, context can be accessed via step.context.stash. Note that modifications to step object will carry over to the steps below.
It is usually a better idea to inspect the stash before the step being debugged.

Notes

I was hoping to have an interactive and colorful way of parsing the stash, but this was the solution I could come up with.
Curses can be added to run the commands with a single click instead of pressing enter afterwards. However, I would need help to prevent curses from clearing the screen. (Which I is probably not easy)

Pull Request Test Coverage Report for Build 1108

8 of 24 (33.33%)  changed or added relevant lines in 2 files are covered.
6 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.05%) to 59.358%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

terraform_compliance/main.py
2
3
66.67%

terraform_compliance/steps/terrain.py
6
21
28.57%

Files with Coverage Reduction
New Missed Lines
%

terraform_compliance/common/defaults.py
6
84.21%

Totals

Change from base Build 1101:
-0.05%

Covered Lines:
1294

Relevant Lines:
2180

💛  - Coveralls


DS-9323: update creativecommons.org links to use https

References

Fixes #9323

Description
This simple PR updates creativecommons.log links from http to https.
Instructions for Reviewers
Deploy the PR, choose a CC license during a submission, and observe that the CC license link in the item now starts with https.
Checklist

[X] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & integration tests). Exceptions may be made if previously agreed upon.
[X] My PR passes Checkstyle validation based on the Code Style Guide.
[X] My PR includes Javadoc for all new (or modified) public methods and classes. It also includes Javadoc for large or complex private methods.
[X] My PR passes all tests and includes new/updated Unit or Integration Tests based on the Code Testing Guide.
[X] If my PR includes new libraries/dependencies (in any pom.xml), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
[X] If my PR modifies REST API endpoints, I've opened a separate REST Contract PR related to this change.
[X] If my PR includes new configurations, I've provided basic technical documentation in the PR itself.
[X] If my PR fixes an issue ticket, I've linked them together.

Manual port to 7.x in #9634


RoutingService

Prepare forwards

Resolve mediators by DID in serviceEndpoint or DID URL in routingKeys

Reference implementation in didcomm-python. Striving for simplicity and readability.

__forward_if_needed
wrap_in_forward

Support for forwarding will come requirement that we know how to parse/work with DIDComm services (routingKeys, serviceEndpoint)
Discussion: Should we support the old did-communication style?
Conclusion: No. We should only accept the spec compliant DIDCommMessaging style to exert positive pressure on doing things the correct way/according to the spec. If people want to support DIDs with the old style, they should implement a layer in the resolver to translate from old to new.
{
  ...
  "service": [
    {
      "id": "did:example:123456789abcdefghi#didcomm-0",
      "type": "did-communication",
      "serviceEndpoint": "https://example.com/endpoint",
      "accept": ["didcomm..."],
      "routingKeys": ["...", ...],
    },
    {
      "id": "did:example:123456789abcdefghi#didcomm-1",
      "type": "DIDCommMessaging",
      "serviceEndpoint": [{
          "uri": "https://example.com/path",
          "accept": [
              "didcomm/v2",
              "didcomm/aip2;env=rfc587"
          ],
          "routingKeys": ["did:example:somemediator#somekey"]
      }]
    }
  ]
}


Compute external dependencies of protobuf APIs

Protocol Buffer-based API descriptions consist of potentially multiple .proto files that can use import statements to include other .proto files. Our current working definition of a protobuf spec is that it is a directory of .proto files that might refer to other files outside that directory. Many analysis tasks would require resolution of these references, and a first step to that would be to have a way to compute and store the internally-unresolved imports in a protobuf spec, i.e. the external dependencies.

Addressed in #105


Add ability to get public key from nip-05

Changelog notice
Add ability to get public key from nip-05
Checklists
All Submissions:

[x] I've signed all my commits
[x] I followed the contribution guidelines
[x] I ran cargo fmt and cargo clippy before committing

Thank you for your contribution!


Size limits

Building the image yields the following. We should set a higher limit, or figure out how to strip these files to be within the limit.
-  Building for production...
[BABEL] Note: The code generator has deoptimised the styling of /home/node/app/node_modules/monaco-editor/esm/vs/language/html/html.worker.js as it exceeds the max of 500KB.
[BABEL] Note: The code generator has deoptimised the styling of /home/node/app/node_modules/monaco-editor/esm/vs/language/css/css.worker.js as it exceeds the max of 500KB.
[BABEL] Note: The code generator has deoptimised the styling of /home/node/app/node_modules/monaco-editor/esm/vs/language/typescript/ts.worker.js as it exceeds the max of 500KB.
[BABEL] Note: The code generator has deoptimised the styling of /home/node/app/src/utils/CypherParser/CypherParser.ts as it exceeds the max of 500KB.
 WARNING  Compiled with 2 warnings12:44:17 PM

 warning

asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets:
  css.worker.js (1010 KiB)
  editor.worker.js (248 KiB)
  html.worker.js (677 KiB)
  json.worker.js (375 KiB)
  ts.worker.js (4.66 MiB)
  js/index.6358f0f7.js (389 KiB)
  css/chunk-vendors.ed48cc6e.css (328 KiB)
  js/chunk-vendors.d57c2224.js (5.26 MiB)
  img/kuzu-logo-inverse.png (493 KiB)
  third-party/fontawesome-free-6.4.2-web/webfonts/fa-solid-900.ttf (385 KiB)

 warning

entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
Entrypoints:
  index (5.97 MiB)
      css/chunk-vendors.ed48cc6e.css
      js/chunk-vendors.d57c2224.js
      css/index.90908399.css
      js/index.6358f0f7.js

The webpack configuration was generated by vue-cli. I will look into it.

It seems this can be safely ignored: https://stackoverflow.com/questions/35192796/babel-note-the-code-generator-has-deoptimised-the-styling-of-app-js-as-it-exc
I also tried to set the compact: true option and it did not seem to work with vue-cli, so I think I will leave it as-is for now.


Issue with chef user resource

Description
Chef-client is not working properly for User resource when used as an object of Chef::Resource::User class.
Chef Version
Chefc-client above > chef13
Platform Version
Centos 6.xx
Replication Case
I am running the following in loop with different values of username.
user= Chef::Resource::User.new('username', run_context)
				user.password 'hash'
				user.supports :manage_home => true
				user.home '/home/username'
				user.shell '/bin/bash'
              			user.action [:create, :modify]
 				user.run_action :create

Client Output

 ================================================================================
      Error executing action `create` on resource 'user_resource_abstract_base_class[root]'
      ================================================================================

      NotImplementedError
      -------------------
      NotImplementedError

      Cookbook Trace:
      ---------------
      /var/chef/cache/cookbooks/config_common/recipes/user_groups.rb:55:in `block (4 levels) in from_file'
      /var/chef/cache/cookbooks/config_common/recipes/user_groups.rb:28:in `foreach'
      /var/chef/cache/cookbooks/config_common/recipes/user_groups.rb:28:in `block (3 levels) in from_file'
      /var/chef/cache/cookbooks/config_common/recipes/user_groups.rb:27:in `each'
      /var/chef/cache/cookbooks/config_common/recipes/user_groups.rb:27:in `block (2 levels) in from_file'
      /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:78:in `run_action'
      /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in `block (2 levels) in converge'
      /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in `each'
      /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in `block in converge'
      /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:105:in `converge'

      Compiled Resource:
      ------------------
      # Declared in

      user_resource_abstract_base_class("root") do
        action [:create, :modify]
        supports {:manage_home=>true}
        retries 0
        retry_delay 2
        default_guard_interpreter :default
        username "root"
        home "/root"
        shell "/bin/bash"
        password "$6$VcvJ7Na8/.tYT2a8$I4kaEiEU/dHlfo5zyWad/.I/NT7dmF7xElYbyGv8UEKYx3DcAAUS4abwPHHzJieaDGvlxF.OqlA//R9O.xTDU0"
        iterations 27855
      end

      Platform:
      ---------
      x86_64-linux

    ================================================================================
    Error executing action `run` on resource 'ruby_block[Create user and groups]'
    ================================================================================

    NotImplementedError
    -------------------
    user_resource_abstract_base_class[root] (dynamically defined) had an error: NotImplementedError: NotImplementedError

    Cookbook Trace:
    ---------------
    /var/chef/cache/cookbooks/config_common/recipes/user_groups.rb:55:in `block (4 levels) in from_file'
    /var/chef/cache/cookbooks/config_common/recipes/user_groups.rb:28:in `foreach'
    /var/chef/cache/cookbooks/config_common/recipes/user_groups.rb:28:in `block (3 levels) in from_file'
    /var/chef/cache/cookbooks/config_common/recipes/user_groups.rb:27:in `each'
    /var/chef/cache/cookbooks/config_common/recipes/user_groups.rb:27:in `block (2 levels) in from_file'
    /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:78:in `run_action'
    /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in `block (2 levels) in converge'
    /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in `each'
    /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:106:in `block in converge'
    /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:105:in `converge'

This looks like you're doing something you really shouldn't. Can you explain why you'd ever want to instantiate objects of Chef::Resource::User manually, especially since it looks a lot like you're just doing:
users.each do |u|
  user u
end

inside a ruby block rather than in the recipe.

yeah that's broken 100% deliberately.
you can also use:
declare_resource(:users, 'foo') do
  supports manage_home:  true
end

although i don't see why you'd need to do that.

FWIW, supports manage_home:  true is deprecated and should be manage_home:  true

fixed.  i clearly need much more caffeine this morning...

My user database is in GIT and we are trying to process it from there. Git sync will be performed on converge phrase, so will not be able to enumerate user array or hash as the file will be present on server. To make sure, user creating activity is performed after the git fetch/checkout is completed, i need to run this block of code inside ruby_block.
I was not aware of @lamont-granquist 's declare_resource approach. Let me check it out.

i need to run this block of code inside ruby_block.

you probably don't, but you don't show exactly what you're doing, so i can only guess.   you should probably use a git resource that notifies a user resource.  if you need variables to be set for the username or whatever then you should pre-declare those in normal recipe code outside of the scope of the ruby_block you're using.

In that case I will have to notify all the users resources.
Idea here is to store the user/password data in GIT and be able to create and delete user from git itself so we can have an inbuilt audit. To achieve that we need to first download the file using git sync resource and then read all the lines from file to create users + groups.
If you have any other alternatives I am very open to those suggestions.
Shubham

On 06-Feb-2017, at 11:47 PM, Lamont Granquist<EMAIL_ADDRESS>wrote:
i need to run this block of code inside ruby_block.
you probably don't, but you don't show exactly what you're doing, so i can only guess. you should probably use a git resource that notifies a user resource. if you need variables to be set for the username or whatever then you should pre-declare those in normal recipe code outside of the scope of the ruby_block you're using.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/chef/chef/issues/5767#issuecomment-277766374, or mute the thread https://github.com/notifications/unsubscribe-auth/AK5HxUKDQo3G5Kg1gu_qAhSf9bKB-oYHks5rZ2OdgaJpZM4LxXBc.

you can move your logic to a resource and force the git resource to run at compile time:
resources/default.rb:
action :doit do
  git "stuff" do
    [ ... sync the git repo ... ]
  end.run_action(:sync)

  users = [ ... slurp into an array ... ]

  users.each do |user|
    user user.username do
      [ ... etc ... ]
    end
  end
end

by moving the git resource to compile time, you can avoid the ruby_block and can construct normal ruby variables and do typical looping constructs around creating users.
since the git resource might depend on prior recipes being completed, it most likely makes sense to move the logic into a resource so that the code still runs at converge time of the outer run context.

I'm going to close this out since it's been over a year and we haven't heard back with more information.


fix: disable occlusion tracker on windows

Fixes https://github.com/microsoft/vscode/issues/123257
Fixes https://github.com/microsoft/vscode/issues/130644
Fixes https://github.com/microsoft/vscode/issues/136396
Fixes https://github.com/microsoft/vscode/issues/148661

Will this flag be supported going forward? I wonder if Electron needs a solution that ensures occlusion tracking is not coming back, similar to what was suggested in the Google Groups thread.

The change suggested in the thread will be pushed to the chromium main branch soon, once the change is landed Electron does not need to make any changes unless it wants to enable the feature. So, we will not face any regressions moving forward.


ImportError: cannot import name 'mtls'

Environment details

OS type and version: Docker Image
Python version:  3.7
pip version: 20.0.2
google-api-python-client version: 1.9.1

Steps to reproduce

import google-api-python-client

Important this cannot be reproduced with version 1.9.0. We currently downgraded from 1.9.1 to 1.9.0 to solved this issue.
Code example

Stack trace

Hi @SaschaHeyer,
Would you mind doing a pip freeze and providing the exact stack trace?
The most likely cause is an old version of google-auth. See #933

@SaschaHeyer This is because you have an old google-auth installed, please update the google-auth library to the latest version (1.16.1). Please reopen the issue if it doesn't work. Thanks.


Ensure blessed Web UI is pinned

Context
We switched to loading Web UI from IPFS in https://github.com/ipfs-shipyard/ipfs-companion/pull/680.
Blessed CID is hardcoded in extension sources:
https://github.com/ipfs-shipyard/ipfs-companion/blob/1b81a4fac937fff36d8b88f2e48eb4ede6cfb58a/add-on/src/lib/state.js#L27
Problem
@Mikaela noted interesting  problem:

Should the webui get automatically pinned or something? I have gc enabled on go-ipfs
I am wondering what happens if I get disconnected for two hours or so, will I lose the webui?

Solution
ipfs-companion should:

keep current webuiCid pinned

check could happen every time remote API is connected to for the first time in browsing session

when webuiCid changes, unpin old version and pin new one

relevant API: browser.runtime.onInstalled with OnInstalledReason

https://github.com/ipfs-shipyard/ipfs-companion/pull/735 introduces small optimization that preloads the root of webui to speed up the first time it is opened.
Pinning is tricky, because don't want user to fetch entire webui right after extension is installed or when Web UI's Status page shows bandwidth chart with high load (here is why: https://github.com/ipfs-shipyard/ipfs-webui/issues/854, https://github.com/ipfs-shipyard/ipfs-webui/issues/848)
Ideas to explore:

IIRC files in MFS are implicitly pinned (won't be GC'd) but do not need to be recursively present in local repo. This means we could add Web UI root to MFS and keep it from being GC'd that way.

Where to keep it? {MFS}/.cache/ipfs-webui ?


triggering the js_eval resets the page

hello there,
I've run into an issue with the js_eval where it wouldn't properly render (or perhaps just reset the page?) when using it behind a button. It's the same whether or not I just put the code behind a if button("Button Name"): or when a callback method is used.
Clicking the button multiple times results in the result of js_eval being shown.
Streamlit version: 1.11.1 (I can't go beyond that unfortunately)
streamlit_js_eval version: 0.1.5
example code:
#!/usr/bin/env python

import streamlit as st
import streamlit_js_eval

if st.button("Test!"):
    test_function: str = """
    function return_some_data() {
        return "some data"
    }

    return_some_data()
    """

    output = streamlit_js_eval.streamlit_js_eval(
        js_expressions=test_function, key="test0"
    )
    print(f"output length: {len(output)}" if output else "output is None")
    st.write(f"output length: {len(output)}" if output else "output is None")
    st.write(f"output: {output}")

example video of behaviour:

Hi. I will work on it as soon as I find some time. I hope we can find a fix :)

Hi. Sorry for the delay. I'm failing to get your example to work, and I'm kin of blocked as I'm not an expert (or knowledgeable at all!) of Streamlit internals :(
Is it impossible/unfeasible to call streamlit_js_eval outside the condition branch and then just use the out value output? That "solves" the issue, although not in a good way really.

No I can't call it outside the condition branch. I went and upvoted the issue you linked here.

Hi, I am facing similar problem even outside the callback. The problem is when i do streamlit_js_eval(js_expression='window.innerwidth', key='WIDTH') it causes refresh. streamlit 1.30.0 and js_eval ver 1.5.

Hi.  It's js_expressions, not js_expression :) This works "outside a branch":
 x = streamlit_js_eval(js_expressions='window.innerWidth', key='WIDTH',  want_output = True,)
 st.write(f"Width is {x}")

Hi. I just noticed that your code actually works if you replace st.button with st.checkbox :-/
Streamlit 1.31.0, Python 3.10
@derfryday @DevDrake
Hello again,

Even more interesting, if you create simple HTML button using SJE itself and not the default streamlit button, it works!
There is a new version 0.1.7 now, with simple Bootstrap button bootstrapButton(), that does not have this branch issue. You may want to try that.
I know this is really a workaround and not a real solution, but I'm not sure what else I can do without collaboration from the Streamlit team.

Closing for now. Re-open if there is some other finding.

Hello! I didn't quite understand how to use bootstrapButton. Could you please provide a minimal example?

Just the exact same way you use normal Streamlit st.button
Dev-iL @.***> schrieb am Mo., 10. Juni 2024, 13:09:

Hello! I didn't quite understand how to use bootstrapButton. Could you
please provide a minimal example?
—
Reply to this email directly, view it on GitHub
https://github.com/aghasemi/streamlit_js_eval/issues/2#issuecomment-2158050796,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABYCZ37Y4ULTCU33GA7HR7DZGWCNNAVCNFSM6AAAAABJCCMW3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJYGA2TANZZGY
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

What do you mean? It doesn't look like bootstrapButton supports all the kwargs that st.button does... Specifically on_click.

BTW, what I'm trying to do is react to js events in python, by programmatically "pressing" an invisible Streamlit button. It looks like a race condition that's associated with the page refresh is interfering with my solution. Below is a demo of my "almost working" solution for reacting to mouse hover on a Streamlit dataframe:

Some things to note:

It can be seen in the browser console that the action is either enter or leave.
The python console is "lagging behind" the browser, it's unable to retrieve the latest object for some reason.


Incorrect Cassette Days remaining

See https://github.com/bdwilson/waterguru-api/issues/5#issue-2319978748
I just replaced the cartridge and the app is showing 2 for Cassette Days Remaining.  In the app, this is 2 months, not 2 days.  Not sure if this can be fixed in the integration or if this is an issue with the API which is why I opened an issue in both places.

Oh that's definitely a bug here. The response is free text and I assume it was always "x days left". If it returns "x months left" then I'm not going to be able to parse an accurate number of days. Hmm...

I just pushed a new version. Can you update and then run this integration in debug mode and share the log lines that have [custom_components.waterguru.waterguru] refillable: so I can see what the API is returning for you?

Sorry for the delay in responding, @dwradcliffe.  I updated to  6362f8a and here is the log info you requested:
2024-06-05 10:20:19.061 DEBUG (SyncWorker_9) [custom_components.waterguru.waterguru] refillable: {'viewType': 'RefillableView', 'status': 'GREEN', 'type': 'LAB', 'color': '#23B8DC', 'label': 'Cassette', 'maxAmount': '174', 'amountLeft': '144', 'unit': 'pad', 'timeLeftText': '7 weeks left', 'pctLeft': 83.0, 'pctLeftDec': '83', 'urgent': False, 'refillTime': '2024-05-27T02:54:05.723Z'}
2024-06-05 10:20:19.061 DEBUG (SyncWorker_9) [custom_components.waterguru.waterguru] refillable: {'viewType': 'RefillableView', 'status': 'GREEN', 'type': 'BATT', 'color': '#23B8DC', 'label': 'Battery', 'maxAmount': '6.40', 'amountLeft': '5.63', 'unit': 'volt', 'timeLeftText': '5 months left', 'pctLeft': 89.0, 'pctLeftDec': '89', 'urgent': False}

At the same time the WaterGuru app shows 7 weeks left and Home Assistant show 210 days.
For my unit, you can either calculate the number of days remaining using pctLeft * 60 (50 days) or simply use timeLeftText.
Thank you for looking into this for me.  I am more that happy to provide any additional information you need.

It seems that there's no way to determine if the cassette is a C2 or a C5 😞
So I can't calculate like you said, and the only option is to parse the text string and estimate when it returns "weeks" or "months".
I've updated the code to handle this. I'm going to close this for now; hopefully their API changes eventually.

Thanks for the update, David.  Today the data looks perfect.  The app says 6 weeks on the cassette and the app says 42 days and 72%.  I'll continue to monitor and let you know if I have any further questions.
Thank you for creating this integration and keeping it working.


[base] Integrate FormControl with input components

Motivation
To be able to easily compose different kinds of (higher level) form fields with consistent interaction states using Base components/hooks,
Currently, only the Input component is supported (doc).
<FormControlUnstyled defaultValue="" required>
  <Label>Name</Label>
  <Input />
  <HelperText />
</FormControlUnstyled>

But that <Input /> could just as well be an Autocomplete or a Switch.
Requirements
1. Consistent interface for getting a value from any form component

Currently FormControl accepts an onChange prop that gets an event as the sole argument
This works for getting the value from a basic Input using event.target.value, but doesn't work for cases like multi-select or Autocomplete with multiple options
It could updated to provide the latest value as a second argument like: onChange: (event: React.SyntheticEvent, newValue: any) => void

Some components already have this second argument:

useAutocomplete: onChange?: (event: React.SyntheticEvent, value: AutocompleteValue<T, Multiple, DisableClearable, FreeSolo>, reason: AutocompleteChangeReason, details?: AutocompleteChangeDetails<T>) => void
useSlider: onChange?: (event: Event, value: number | number[], activeThumb: number) => void
useSelect: onChange?: (   event: React.MouseEvent | React.KeyboardEvent | React.FocusEvent | null,   value: SelectValue<OptionValue, Multiple>, ) => void
useNumberInput

2. Additional metadata
Some components call onChange with "metadata" arguments:

Autocomplete: reason, details
Slider: activeThumb

Perhaps a general metadata object can be used as the third argument, e.g. onChange: (event, newValue, metadata).
Components

[ ] Input
[ ] Select https://github.com/mui/material-ui/issues/31011
[ ] Slider
[ ] Switch https://github.com/mui/material-ui/issues/32075
[ ] Autocomplete
[ ] TextareaAutosize
[ ] NumberInput

I made a sandbox that integrates a react-hook-form based form with all of Base's form components as a reference: https://codesandbox.io/s/baseui-react-hook-form-ycmlxz?file=/src/App.tsx


React.js and cache invalidation

Describe the bug
I created an app using create-react-app, connected my repo to amplify console and deployed. Then I did some changes and pushed to the master branch. Waited for deploy finish, went to amplify's url and nothings changes. I need to force cache reload (CTRL+SHIFT+R) to see new changes.
To Reproduce
Steps to reproduce the behavior:

Use create-react-app
Configure and deploy on amplify console
Make new changes on repo
Push
Wait for deploy
Check url

Expected behavior
I expected to see new changes without force reload cache.

@maiconcarraro. Could you provide your appId and region? It could be a bug for us.

@garyleefight Sure, it's us-east-1 and d3n05fd1eoav4x

@swaminator that's right, it was service worker. sorry about that.

Hi there, did you resolve the issue? I have the same :)

hey @akabynga yeah, there are 2 approaches:
1 - Unregister service worker, it will prevent caching. On your app.js:
import * as serviceWorker from "./serviceWorker";
serviceWorker.unregister();

2 - Manage to reload everytime has a new registration (automatically), during register you can send onUpdate logic
serviceWorker.register({
  onUpdate: registration => {
    registration.unregister().then(() => {
      window.location.reload();
    });
  }
});


Fix: New Usage Panel fragment instead of Dialogue box in navigation bar

Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Apply the AndroidStyle.xml style template to your code in Android Studio.

[x] Run the checks with ./gradlew check to make sure you didn't break anything

[x] If you have multiple commits please combine them into one commit by squashing them.

@Hiteshgautam01
Please first fix your build.
Show the usage section using activity in place of the fragment.
Please read the PR template before submitting any PR.

Okay @sagar15795  👍

okay @sagar15795 the build is passing now.
I will make activity insted of fragment and commit in this PR as soon as possible.


Add custom script for database creation

Thanks for looking into this @kvanover 🥳
I've made a few small comments above, but in general this looks very close to me!

All should be resolved

Sorry mate I don't think I explained my issue with the test very well.
I'm looking to see the test confirm that we ran the script file, rather than the default behaviour.  One way we could do that is by altering the script file to create a database with a different name to the one passed in on the config, but I'm open to any sort of check that confirms we ran the .sql, not the default create statement from ISyntax.

OK, go it. Will adapt the test 👌

Added a SupportCreateCustomScript for MariaDB, PostgreSQL and SqlServer.
on the test, I'm creating 2 databases so that you can see the custom script is used.

Why the sudden decision to drop Oracle support?

No drop, still in progress. Was a bit hesitant because Oracle was not with 'create database' syntax. That's why I first did the defaults and need to see what I can do for oracle. If you have ideas...

Oracle just uses different syntax, and shoudn't affect whether a suitably knowledgable user can pass in a custom script or not.
If you stayed with your original test that initialised the migrator with (say) FakeDb database name, but you populated the .sql file using the ISyntax create code like before, but with the dbase name DbaseItem253 as the token, then you could happily assert that FakeDb doesn't exist, while DbaseItem253 does.

The main problem here is that it crashes because it does not find 'FakeDb' with the custom script change.

Mmmmm, that makes sense, I didn't see that coming!
Maybe your two-database plan is best then, but just write the ISyntax twice with the different DB names?

Ok, did it a bit differently. catch the error but I verify that the database is created with the custom script.
Oracle is now also included.

Is there still something I need to do? Or do you not agree with the catch approach?

Sorry mate, I'm on holidays atm so internet access is limited.
I have pending reviews above to:

remove all the docco etc indicating this feature is only available on specific DBMS's, as by my thinking it should apply to any target database?
Remove the config flag about whether a DBMS supports a custom script file, as they all should?
As a nit we also have a warning from the build regarding the unused exception var in the catch block of the test.

no problem, just checking if it was ok.
For the config flag, the custom create script is very strange for Sqlite. You are creating a database file based on the connection string. I don't see how we can integrate the custom 'create database' script. So If I would remove the flag, I still need to do something different for the SQL lite version. The rest is set to true.

Hi, @kvanover !
Thank you very much for your contribution, I really appreciate it, and my apologies for not having the time to respond sooner to your PR.
I like the new feature, and I see the need for it. It's just something bugging me, that we get very, very many command-line options as we add features, and this makes the tool a bit confusing to use. How do you (and you, @wokket ), feel about generalising this concept, so that both create and drop, and possibly other of the "Syntax" commands can be customised, should the need be there?
Would it make sense to, instead of providing a command-line switch for just create, to be able to provide a --syntaxOverrides <folder> command-line switch, where we could create scripts for CreateDatabase, DropDatabase, and maybe others, should it be needed in the future?
Say I specify:
--syntaxOverrides ./scripts

and put a script, CreateDatabase.sql in that folder, we change grate so that if there is a specified folder, we use the scripts there instead of the hard-coded ones in the XXXSyntax  (e.g. SqlServerSyntax, OracleSyntax) classes?

also perfect for me.
Will update the code to reflect the requirements

Sorry guys, a little late to the party here.
Everything else in grate is "files called what you like in specially named folders". Could we add a "CreateDataabase" folder to go alonside "AlterDatabase" etc?  No new commandline settings, and consistency withe the rest of the process?

Sorry for the no-reply season here on my part, guys. Real work(TM) has occupied me a lot lately. I haven't had the time to look deeply into this, but, intuitively I'm really a fan of your suggestion with a custom folder, @wokket . This also takes even a bit more of the database-specific stuff out of grate.
I'll look closer into this when I have a bit more time :)

This is solved with #289 - available in release 1.5.0


Hydrawise broken since ver 105.5

The problem

After upgrading to 105.5 all my HYDRAwise entities cannot be found.
Environment

Home Assistant 0.105.5
Frontend version: 20200130.3 - latest

Home Assistant release with the issue: 105.5

Last working Home Assistant release (if known): 105.4

Operating environment (Hass.io/Docker/Windows/etc.):
Home assistant on PI4 with Docker

Integration causing this issue:  HYdrawise

Link to integration documentation on our website:
https://www.home-assistant.io/integrations/hydrawise/

Problem-relevant configuration.yaml

   - platform: hydrawise
     monitored_conditions:
         - watering_time
         - next_cycle

switch:
   - platform: hydrawise
     monitored_conditions:
       - auto_watering
       - manual_watering

binary_sensor:
- platform: hydrawise
      monitored_conditions:
        - is_watering
        - status

hydrawise:
    access_token: xxxxxxxxxxxxxxxxxxx

Traceback/Error logs

Unable to prepare setup for platform hydrawise.switch: Unable to set up component.
10:18 AM setup.py (ERROR)
Unable to prepare setup for platform hydrawise.sensor: Unable to set up component.
10:18 AM setup.py (ERROR)
Unable to prepare setup for platform hydrawise.binary_sensor: Unable to set up component.
10:18 AM setup.py (ERROR)
Error during setup of component hydrawise
10:18 AM components/hydrawise/__init__.py (ERROR)

Additional information
configuration checker doesn't find any errors but I get a notification telling me there is an invalid config:
The following integrations and platforms could not be set up:
hydrawise
hydrawise.sensor
hydrawise.binary_sensor
hydrawise.switch
wink

I'm having the same issue.

Could this be related to #31957?

Do you have any other logs/traceback in home-assistant.log that is related to this integration?

I turned on the log to debug and restarted. Here is what is in the log:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 174, in _async_setup_component
component.setup, hass, processed_config  # type: ignore
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/hydrawise/init.py", line 77, in setup
hydrawise = Hydrawiser(user_token=access_token)
File "/usr/local/lib/python3.7/site-packages/hydrawiser/core.py", line 42, in init
self.update_controller_info()
File "/usr/local/lib/python3.7/site-packages/hydrawiser/core.py", line 65, in update_controller_info
self.user_id = self.controller_status['user_id']
KeyError: 'user_id'
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=binary_sensor.ehct_06108_rain, old_state=None, new_state=<state binary_sensor.ehct_06108_rain=off; friendly_name=Rain, device_class=moisture @ 2020-02-21T10:12:05.392795-05:00>>
2020-02-21 10:12:05 DEBUG (MainThread) [async_upnp_client.traffic] Received packet from ('<IP_ADDRESS>', 47277):
b'HTTP/1.1 200 OK\r\nCACHE-CONTROL: max-age=1800\r\nDATE: Fri, 21 Feb 2020 10:12:04 GMT\r\nEXT:\r\nX-User-Agent: redsonic\r\nLOCATION: http://<IP_ADDRESS>:1080/upnp_device_desc.xml\r\nSERVER: Linux, UPnP/1.0, Private Upnp SDK\r\nST: upnp:rootdevice\r\nUSN: uuid:www.dahuatech.com.device_3_0-3J060C4PAG00030::upnp:rootdevice\r\n\r\n'
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=persistent_notification, service=create, service_data=title=Invalid config, message=The following integrations and platforms could not be set up:

hydrawise

Please check your config., notification_id=invalid_config>
2020-02-21 10:12:05 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform hydrawise.binary_sensor: Unable to set up component.
2020-02-21 10:12:05 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform hydrawise.sensor: Unable to set up component.
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.un60d7000_un60d7000, old_state=None, new_state=<state media_player.un60d7000_un60d7000=unknown; source_list=['TV', 'HDMI'], is_volume_muted=False, friendly_name=Family Room Samsung TV, supported_features=20281, device_class=tv @ 2020-02-21T10:12:05.408518-05:00>>
2020-02-21 10:12:05 INFO (MainThread) [homeassistant.components.camera] Setting up camera.bloomsky
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.components.person.storage_collection] added 8bbff82d3a714f2b8baf61a3f0531d47: {'device_trackers': ['device_tracker.lum_2586392f_6979_4b69_a8be_b22992d7990d_2'], 'id': '8bbff82d3a714f2b8baf61a3f0531d47', 'name': 'Lucille Miele', 'user_id': '15bffd888f7c4f3ab80302004f4f1228'}
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.components.input_boolean.yaml_collection] added wife_present: {'id': 'wife_present', 'name': 'Wife', 'icon': 'mdi:account'}
2020-02-21 10:12:05 DEBUG (MainThread) [async_upnp_client.traffic] Received packet from ('<IP_ADDRESS>', 47277):
b'HTTP/1.1 200 OK\r\nCACHE-CONTROL: max-age=1800\r\nDATE: Fri, 21 Feb 2020 10:12:04 GMT\r\nEXT:\r\nX-User-Agent: redsonic\r\nLOCATION: http://<IP_ADDRESS>:1080/upnp_device_desc.xml\r\nSERVER: Linux, UPnP/1.0, Private Upnp SDK\r\nST: uuid:www.dahuatech.com.device_3_0-3J060C4PAG00030\r\nUSN: uuid:www.dahuatech.com.device_3_0-3J060C4PAG00030\r\n\r\n'
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=persistent_notification.invalid_config, old_state=None, new_state=<state persistent_notification.invalid_config=notifying; title=Invalid config, message=The following integrations and platforms could not be set up:

hydrawise

Please check your config. @ 2020-02-21T10:12:05.419144-05:00>>
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event persistent_notifications_updated[L]>
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=persistent_notification, service=create, service_data=title=Invalid config, message=The following integrations and platforms could not be set up:

hydrawise
hydrawise.binary_sensor

Please check your config., notification_id=invalid_config>
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=persistent_notification, service=create, service_data=title=Invalid config, message=The following integrations and platforms could not be set up:

hydrawise
hydrawise.binary_sensor
hydrawise.sensor

Please check your config., notification_id=invalid_config>
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=group.computer_room, old_state=None, new_state=<state group.computer_room=unknown; entity_id=('switch.computer_room', 'switch.dummy', 'switch.quirky_outlet_1', 'switch.quirky_outlet_2', 'switch.siren', 'switch.spare'), order=4, friendly_name=Computer Room @ 2020-02-21T10:12:05.430484-05:00>>
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.yr_symbol, old_state=None, new_state=<state sensor.yr_symbol=unknown; attribution=Weather forecast from met.no, delivered by the Norwegian Meteorological Institute., friendly_name=yr Symbol, entity_picture=https://api.met.no/weatherapi/weathericon/1.1/?symbol=None;content_type=image/png @ 2020-02-21T10:12:05.433501-05:00>>
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.date, old_state=None, new_state=<state sensor.date=2020-02-21; friendly_name=Date, icon=mdi:calendar @ 2020-02-21T10:12:05.435660-05:00>>
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.date_time, old_state=None, new_state=<state sensor.date_time=2020-02-21, 10:12; friendly_name=Date & Time, icon=mdi:calendar-clock @ 2020-02-21T10:12:05.437562-05:00>>
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.date_time_iso, old_state=None, new_state=<state sensor.date_time_iso=2020-02-21T10:12:00; friendly_name=Date & Time (ISO), icon=mdi:calendar-clock @ 2020-02-21T10:12:05.439721-05:00>>
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.time_date, old_state=None, new_state=<state sensor.time_date=10:12, 2020-02-21; friendly_name=Time & Date, icon=mdi:calendar-clock @ 2020-02-21T10:12:05.443276-05:00>>
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.time_utc, old_state=None, new_state=<state sensor.time_utc=15:12; friendly_name=Time (UTC), icon=mdi:clock @ 2020-02-21T10:12:05.445199-05:00>>
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.internet_time, old_state=None, new_state=<state sensor.internet_time=@675; friendly_name=Internet Time, icon=mdi:clock @ 2020-02-21T10:12:05.447646-05:00>>
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.time, old_state=None, new_state=<state sensor.time=10:12; friendly_name=Time, icon=mdi:clock @ 2020-02-21T10:12:05.449490-05:00>>
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.simple_time_date, old_state=None, new_state=<state sensor.simple_time_date=unknown; friendly_name=Todays Date @ 2020-02-21T10:12:05.451132-05:00>>
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.simple_time, old_state=None, new_state=<state sensor.simple_time=unknown; friendly_name=Current Time @ 2020-02-21T10:12:05.452809-05:00>>
2020-02-21 10:12:05 DEBUG (MainThread) [async_upnp_client.traffic] Received packet from ('<IP_ADDRESS>', 47277):
b'HTTP/1.1 200 OK\r\nCACHE-CONTROL: max-age=1800\r\nDATE: Fri, 21 Feb 2020 10:12:04 GMT\r\nEXT:\r\nX-User-Agent: redsonic\r\nLOCATION: http://<IP_ADDRESS>:1080/upnp_device_desc.xml\r\nSERVER: Linux, UPnP/1.0, Private Upnp SDK\r\nST: urn:schemas-upnp-org:device:3.0-3J060C4PAG00030\r\nUSN: uuid:www.dahuatech.com.device_3_0-3J060C4PAG00030::urn:schemas-upnp-org:device:3.0-3J060C4PAG00030\r\n\r\n'
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=persistent_notification.invalid_config, old_state=<state persistent_notification.invalid_config=notifying; title=Invalid config, message=The following integrations and platforms could not be set up:

hydrawise

Please check your config. @ 2020-02-21T10:12:05.419144-05:00>, new_state=<state persistent_notification.invalid_config=notifying; title=Invalid config, message=The following integrations and platforms could not be set up:

hydrawise
hydrawise.binary_sensor

Please check your config. @ 2020-02-21T10:12:05.419144-05:00>>
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event persistent_notifications_updated[L]>
2020-02-21 10:12:05 DEBUG (SyncWorker_10) [homeassistant.util.json] JSON file not found: /config/.storage/input_select
2020-02-21 10:12:05 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=persistent_notification.invalid_config, old_state=<state persistent_notification.invalid_config=notifying; title=Invalid config, message=The following integrations and platforms could not be set up:

hydrawise
hydrawise.binary_sensor

Please check your config. @ 2020-02-21T10:12:05.419144-05:00>, new_state=<state persistent_notification.invalid_config=notifying; title=Invalid config, message=The following integrations and platforms could not be set up:

hydrawise
hydrawise.binary_sensor
hydrawise.sensor

Please check your config. @ 2020-02-21T10:12:05.419144-05:00>>

@franmiele have you checked that your configuration is valid? Because there are a lot of logs mentioning an invalid configuration.

Yes, it comes back VALID

This is a dupe of https://github.com/home-assistant/home-assistant/issues/31957
Hydrawise have confirmed they changed their API without notification. An upstream bug with the library has been raised to resolve the issue.

Duplicate of #31957


Better document toHaveTextContent's case sensitiveness

After having merged #72 I've realized the README is not clear about this, not even the examples hint at this, and they were even inadequate for how it behaved before this change.
toHaveTextContent documentation should be explicit about this. Maybe even mentioning that if someone wants it to behave as case-insensitive, they should use a regex with the i modifier (/some text/i) instead of a string.
@lourenci can you take this? I could but maybe you can tackle it before I can.

@gnapse yes, I can.


Fix broken prebuilt_downloader

I built it as written in CONTRIBUTING.md and got an error on the way.
This line was probably the cause, so I reverted.
https://github.com/ruby/ruby.wasm/commit/647b2eb7fa2b4b7346df11ae809991d1cd802116#diff-fb5ebe2655a98fd7ab64c546f729c3af1c3521d7b9aad6f611f49852228f4b08R11

Thank you for trying to fix the issue :pray: It was my bad, I made a fix in the main branch 666dadd689d979d81cee085d346ebfbf11bd3a12, could you try it?

I tried that and solved the problem!
Thanks for addressing it. 👍


filter test file from coverage report

closes #195

adds lcov-filter
modify script command to filter out all files with 'test' in the path [per docs]

Coverage decreased (-0.02%) to 98.936% when pulling 07be0ede48bc7525de9ae107ebd7c2fb044f3035 on ktravers:195-rm-test-from-coverage into 8e252e4eefacc680fae7211d5b80a4861385b7bb on mxstbr:dev.

Yes, I like this! Can it possibly be achieved without adding another dependency?

Coverage decreased (-0.02%) to 98.936% when pulling 9dd75e73322e50b3f85311de9b7fee4812541876 on ktravers:195-rm-test-from-coverage into 2852c09b4d0851ce46eea3dc55517f67fd1ab80d on mxstbr:dev.

@mxstbr absolutely, good call. since we're piping output to coveralls, we can use a nice simple grep -v to filter out any files with test in their path. will update description above accordingly

While I really appreciate you taking the time to fix this, #980 will supersede our current test setup in the next release, so this isn't necessary anymore.
Thanks for submitting this PR, I really appreciate it! I'm sure people that use the current version will find this very helpful 👍

@mxstbr no problem, excited for the move to Jest/Enzyme!


Added UKBB and open targets data source documentation

In this PR I have had a go at writing some bios for some of the data sources. Please let me know what you think (or if potentially I've put the text in the wrong markdown file)
The updated markdowns are:

docs/python_api/datasource/open_targets/_open_targets.md
docs/python_api/datasource/ukbiobank/_ukbiobank.md

The text is taken and updated partly from already existing descriptions in https://genetics-docs.opentargets.org/ and https://platform-docs.opentargets.org/target

Codecov Report

Merging #191 (1d8ddda) into main (c021e6b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #191   +/-   ##
=======================================
  Coverage   90.95%   90.95%
=======================================
  Files          67       67
  Lines        1459     1459
=======================================
  Hits         1327     1327
  Misses        132      132

Changes make sense. We can build from here.


fix pod antiaffinity issue.

Resolve: https://github.com/istio/istio/issues/13892

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: morvencao
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS [morvencao]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@morvencao: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
92fec5878ecf4af5dc490e0b0af5d59332b78821
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@linsun: changing LGTM is restricted to assignees, and assigning you to the PR failed.

In response to this:

/lgtm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: linsun, morvencao
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS [linsun,morvencao]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/test istio-pilot-multicluster-e2e

@morvencao: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
92fec5878ecf4af5dc490e0b0af5d59332b78821
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


CFBundleURLName is required

Per https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleurltypes this is a required field, but it's optional in the pydantic schema.

I am gonna close this - sorry for the noise. Let's see if we hit an issue with this in practice.


DNS Proof

My keybase: https://keybase.io/luisnell
I'm trying to proof a domain I own (originell.org). The process fails.
Not entirely sure, but could this have something to do with my site not being online?

you have a very long TTL.  our servers might have  a cached copy and might not have to reload until 63627s from now

Nice catch! However, I set that more than 17 hours ago. Should be about 25 hours now.
Nevertheless, if the entry looks correct to you, I might just wait another day.

		IN	TXT
;; ANSWER SECTION:
_keybase.rowankaag.nl.	149	IN	TXT	"keybase-site-verification=sw9fmRiPrnu8hYP7cOsVE4PRrJpi5sLTTbdI1wLjqgM"
;; Query time: 58 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: Sat Oct 21 18:08:11 2017
;; MSG SIZE  rcvd: 121

Note: I think my mistake was not specifying it for _keybase.originell.org. .. Total overlooked that part. Trying again. :)

p.s. iOS app says "verified", while macOS app says "DNS unreachable". Both behind the same network, firewall, etc.

update from my side: now that I specified the TXT record for _keybase, the verification worked.


libqpdf/Pl_Flate.cc functions

Hi,
I compiled 10.3.2 without issues on our system earlier but is no longer the case and I tried to get around with 10.4.0 and got the same error,
/bin/bash ./libtool --quiet --mode=compile --tag=CXX /usr/local/software/archive/linux-scientific7-x86_64/gcc-9/gcc-6.5.0-dtb6lagchexqdijlx6xgkin3zlfddpzi/bin/g++  -g -O2 -fvisibility=hidden -I/usr/local/software/archive/linux-scientific7-x86_64/gcc-9/zlib-1.2.11-lnf7bswyozdhprbg7jo6n5ha5633ftj2/include       -Wconversion -Wsign-conversion -I/rds/user/jhz22/hpc-work/include    -I/usr/local/software/archive/linux-scientific7-x86_64/gcc-9/zlib-1.2.11-lnf7bswyozdhprbg7jo6n5ha5633ftj2/include -I/rds/user/jhz22/hpc-work/include -I/usr/include/p11-kit-1    -Wold-style-cast -Wall -MD -MF libqpdf/build/Pl_Flate.tdep -MP -Iinclude -Ilibqpdf  -c libqpdf/Pl_Flate.cc -o libqpdf/build/Pl_Flate.o; sed -e 's/.o:/.lo:/' < libqpdf/build/Pl_Flate.tdep > libqpdf/build/Pl_Flate.dep
libqpdf/Pl_Flate.cc:75:73: error: no 'void Pl_Flate::setWarnCallback(std::function<void(const char*, int)>)' member function declared in class 'Pl_Flate'
Pl_Flate::setWarnCallback(std::function<void(char const*, int)> callback)
^
libqpdf/Pl_Flate.cc:81:41: error: no 'void Pl_Flate::warn(const char*, int)' member function declared in class 'Pl_Flate'
Pl_Flate::warn(char const* msg, int code)
^
libqpdf/Pl_Flate.cc: In member function 'void Pl_Flate::handleData(unsigned char*, size_t, int)':
libqpdf/Pl_Flate.cc:187:19: error: 'class Pl_Flate' has no member named 'warn'
this->warn(
^~~~
/bin/bash: libqpdf/build/Pl_Flate.tdep: No such file or directory
make: *** [libqpdf/build/Pl_Flate.lo] Error 1
I sense it might be due to availaibility of related software -- is there possible to find out?
Thanks,
Jing Hua

My guess is that you have an older version of qpdf installed on your system (or in one of the locations you have explicitly included in your include path) and the build is picking up headers from that instead of from the current version. Could that possibly be the case?

I would have thought the new installation will replace those at --prefix. However I would see if I can implement your suggestion.

I just pressed the wrong key -- I gather your sense was right! I dropped -I${PREFIX}/include and it continues steadily.

It is all done now -- after also sorting out hiccups over gnutls and nettle. Thank you!


Recommendation: Follow the DUI or CUI color configuration of the foobar2000

The current color configuration is unique and cannot be compared with the DUI or CUI color configuration that follows foobar2000, if I switch between light and dark or other colors in DUI or CUI, then you have to go to the component settings to set it.

Is that the most logical behavior? The spectrum is basically eye candy. I could use the colors as a starting point but after that I think the user should be able to deviate. Your thoughts?

You can refer to the color processing methods of the two visualization components foo_enhanced_spectrum_analyzer and foo_loudness_peakmeter, which can use user-defined colors or the system color configuration of DUI and CUI.
These two components could only use custom colors at first. After user feedback, they matched the system colors of DUI and CUI. The colors in View-Layout-Quick Settings are all accurately presented, and have a good visual affinity for the entire theme interface.

Also, the feature to use DUI/CUI's color configuration instead should be a default setting for consistency with built-in visualizations of foobar2000, and yes, even the original foo_musical_spectrum don't have a feature to automatically set colors according to the system color configuration of DUI and CUI

You can refer to the color processing methods of the two visualization components foo_enhanced_spectrum_analyzer and foo_loudness_peakmeter, which can use user-defined colors or the system color configuration of DUI and CUI.
These two components could only use custom colors at first. After user feedback, they matched the system colors of DUI and CUI. The colors in View-Layout-Quick Settings are all accurately presented, and have a good visual affinity for the entire theme interface.

All visual elements can now be styled individually with each of the DUI or CUI colors in 0.7.0-RC-2,


(Perhaps) Remove Range/Loop Safety, So Folks Don't Have to Optimize

See the conversation here: http://news.ycombinator.com/item?id=3371171
Most of their work on the decoder went fine, but they ran into one area where (by default) CoffeeScript wasn't generating acceptable performance code, and had to coax it a little. Perhaps the original behavior we used to have is preferable? One commenter says:

I've programmed in dozens of languages, and I can't think of another
one where loops could automatically run either up or down depending
on the start and end values.
Not knowing CoffeeScript well, when I see this code:
n = -10
for i in [0...n] doSomething()
I'd expect it to call doSomething zero times. At least that's what I'd expect
in JavaScript or any of the other languages I've used.

I like this solution:
step = a<=b ? 1 : -1;
for (i = a; step*i < step*b; i += step) {
  doSomething();
}

@michaelficarra Interesting. Mind whipping up a JSPerf (or even better, a JSLitmus) for it?

If breaking changes are on the table, then I'm for:

Assuming step to be 1 unless otherwise specified, eliminating the need for step = ... altogether.
Making for x in arr by -1 a valid way of iterating backward through arr.

Which issue was the one that proposed this (un)safety, by the way?

@devongovett Look at that compilation more carefully. It starts at 0, stops at arr.length, and steps by -1. Unless arr.length is negative, the result is an infinite loop.

@TrevorBurnham yup, realized that afterward and edited my post ;)

@devongovett See #1208 for previous discussion.

FWIW you can hate this transcompilaton even if you don't give a darn about performance.
for (i = 0; 0 <= n ? i <= n : i >= n; 0 <= n ? i++ : i--) {
  foo;
}

To borrow words from the HN comment, I can't think of another
programming language where loops could automatically run either up or down depending
on the start and end values.
It's just strange, and it sometimes leads to bugs for the degenerate case of algorithms.
I know that "step" can make the code deterministic, and I know that this regrettable decision may be hard to undo at this point, but it should be noted that this isn't just an optimization concern.

Here's a new variant:
var step = 0 <= end ? 1 : -1;
var loops = Math.abs(end - 0);

for (var i = 0, j = 0; j < loops; i += step, j++) {
  Math.pow(2, i);
}

http://jsperf.com/coffeescript-looping/2

+1 that this is not just optimization.
Recently I was writing an autocompletion system, which included implementation of rather complex data structures (tries in node Buffers, anyone?) and ~30% of debugging time went to chasing cases where for cycle went backwards instead of not doing anything. This was my worst complaint of CoffeeScript, otherwise a brilliant language. I've ended with a lot of ugly statements like this (I wasnt aware of the 'by 1' trick):
  if a < b
    for i in [a...b]
      # Do something with i.

Please, please, remove this unfortunate default. There is no other language I know of, that supports automatic forward-or-backward iteration and its a huge gotcha and source of confusion when implementing any real, non-trivial algorithm.
What I propose is:

Get rid of automatic forward-or-backward iteration at all. Always iterate forward. In 0.01% cases where the reverse is really needed, it could be written explicitly and be more understandable/supportable and less confusing for others.

Reverse iteration (which is itself rather rare) could be written, without the loss of comprehensibility as

  for i in reversed [0..3]

  # Equivalent
  arr = [0..3]
  for i in reversed arr

  # Equivalent
  for i in arr.reverse()

  # Emits compilation error
  for i in [3..0]

Step of iteration must be positive even in reverse iteration, again to prevent confusion.

  arr = [0..3]
  for i in reversed arr by 2

To maintain consistency, this may also mean that arr = [a..b] would be empty if a > b. arr = [20..0] could emit an error like in the for loop above to prevent mistakes. To get the reversed array in these rare case I would suggest, again by the principle of least confusion, arr = [0..20].reverse()

Arguably, these changes will make reverse iteration and reverse arrays look slightly uglier in exchange to be more predictable. I think this is a fair change, considering reverse iteration is not so frequent and can/should be more explicit.

A PR that improves performance is always welcome.


tour: [REPLACE WITH SHORT DESCRIPTION]

Context: https://tour.golang.org/methods/8
Change the title above to describe your issue and add your feedback here, including code if necessary

Empty issue, closing.


CursedObjectConstructor

I'll look into web failure later

Wow. The breakage of the examples looks like a deal breaker. :disappointed:

with router that hide the lifetimes behind reference counting string type the need of Request<'_> is absent for now.
But zero copy deserialize types like Query<'_> and Json<'_> is still the highest thought after feature based on this.


Mechs can't repair apparel, weapon and staff

Hello, noticed that tiered mechs can't repair anything wih this mod. They just take what require repair, repair kit, then stands in front of workbench (without adding HP to what they try to repair), then take repair kit of the table, take what they want to repair, place it again and loop this

Mod has not been updated in a while, and the comments all say that it's broken. I think it's an issue with that mod, not mine.

You're right, some comments stating that the mode is not working exist, but it is due to lack reading skills of commentators. They skip the part where mod maker explain that you need to craft repair kit before you can repair anything. I'm not pushing and don't want to say anything bad about your mod, you're good mod maker and I highly appreciate your effort!

Oh ok, do you know if the vanilla bots work with this mod?

Oh, sorry, I started my mechanitor career with your mod and built only cool mechs. Now, when I tried on clen save file with only two mods and spawned vanilla fabricator I see that there is issue even with vanilla. Sorry for disturbance
Exception in JobDriver tick for pawn Mech_Fabricor43688 driver=JobDriver_RepairItem (toilIndex=11) driver.job=(RepairItem (Job_6406) A=Thing_ElectricTableRepair43534 B=Thing_Apparel_CollarShirt1179 C=(124, 0, 129))
System.NullReferenceException: Object reference not set to an instance of an object
at Repair.JobDriver_RepairItem+<>c__DisplayClass4_0.b__1 () [0x0003f] in <3f4ea5fd60ac4e39bc78b2eca3f6412e>:0
at Verse.AI.JobDriver.DriverTick () [0x00163] in <1a99832471b046408678c845f00d13b6>:0
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 39)

No problem, sorry I couldn't help.


TS intellisense issues

VSCode Version: Code - Insiders 1.14.0-insider (5cb4570007af28b5e0c0b4177e0283dc961ebbb8, 2017-06-30T22:27:13.873Z)
OS Version: Darwin x64 16.5.0

Snippet like this in a TS file, using 2.4.1
import {ChildProcess} from 'child_process';

interface I1 {

}

class C1 {

}

With the cursor on an empty line, press ctrl+space
Type C - C1 appears in suggestions ✔
ChildProcess doesn't appear in suggestions :bug:
Type I - I1 doesn't appear in the suggestions :bug:

So in some cases, interfaces don't appear but other types do.
Maybe a separate issue,

Add a line let x: , cursor set to enter the type annotation
Press ctrl+space
Suggest box is empty

https://github.com/Microsoft/TypeScript/issues/16610 appears in the second part

For the first part, I believe typescript will now only show type suggestions in type annotation locations. ChildProcess is a type without a constructor or new or class, so it will not be shown in normal contexts.
Microsoft/TypeScript#16610 is the correct issue for the second case


Reply to wishlist reminder

People reply to the wishlist reminder mail with their wishlist. ... yeah, .... Not sure how to fix this but it happens too often.

We could implement some logic so we parse replied mails. Same thing like github does, when you reply to a notification mail they add the reply as a comment in the issue/pr

I think we should just ignore or bounce these emails. Parsing them and
forwarding them could easily expose the secret Santa (eg . signature).
Alternatively we could add functionality to communicate anonymously through
the site.
Tom
Op 19 dec. 2015 09:31 schreef "Jeroen Thora"<EMAIL_ADDRESS>
We could implement some logic so we parse replied mails. Same thing like
github does, when you reply to a notification mail they add the reply as a
comment in the issue/pr
—
Reply to this email directly or view it on GitHub
https://github.com/Intracto/SecretSanta/issues/57#issuecomment-165960801
.

I ignored these mails for a long time but that is not ok. I added a default reply in Kayako now. Parsing is an option but very error prone.

won't fix. This is sent by no-reply with autoreply now


merging changes in resume and template into develop branch

webpage is filled with ordered info blocks, some personal info added.

done


兼容jackjson中access中的READ_ONLY跟WRITE_ONLY修复

What this PR does / why we need it?
目前当系统使用到jackson跟fastjson2后，使用jackson
@JsonProperty(value = "password", access = JsonProperty.Access.WRITE_ONLY)
注解后，bean类序列化为json时返回前端不带password字段，该现象为正常的。
但通过JSON.parseObject(jsonObject.toJSONString(), SysUser.class);得到的bean中password为空
同时当user.setPassword("54321");System.out.println(JSON.toJSONString(user));时输出json中带password字段值
Summary of your change
对ObjectWriterBaseModule跟ObjectReaderBaseModule中字段对调
Please indicate you've done the following:

[ ] Made sure tests are passing and test coverage is added if needed.
[ ] Made sure commit message follow the rule of Conventional Commits specification.
[ ] Considered the docs impact and opened a new docs issue or PR with docs changes if needed.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.yousongshu seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

请签署CLA

好的，签署了

显示还没签署CLA，同时这个PR导致JsonPropertyTest1跑不过，这个Testcase也一起改了吧

好的，抱歉没看下方报错

https://github.com/alibaba/fastjson2/releases/tag/2.0.16
问题已修复，请用2.0.16版本

JsonProperty.Access.WRITE_ONLY || access = JsonProperty.Access.READ_ONLY
支持jackson JsonProperty的问题修复很好。但是带来的问题是后台redis缓存序列化和反序列化的时候还想要保留所有字段。
修复该bug后没有给出一个方法可以强制序列化所有字段，忽略WRITE_ONLY或者READ_ONLY；建议在JSONWriter.Feature增加相关Feature，用户可以手工指定忽略WRITE_ONLY或者READ_ONLY。
望采纳，谢谢！
目前只能在2.0.2版本，等待支持手工强制序列化、反序列化所有字段的版本出现。


Fixing Docstrings?

Hi, I really like this package you have designed! It offers some really cool functionality that is useful in a wide variety of contexts!
However, looking at the docs, many of the doc strings are not formatted correctly and are rendering improperly.
It is very challenging to read the package API as things stand right now.
Would it be possible to have them fixed?

Hi, thank you very much for your message and suggestions. We will fix the docs problem as soon as possible.

Hi, we have just released a significant update v0.2.7.  It has fixed the documentation issues you pointed out. In addition, we added a new set of universal grids that exactly satisfy the time symmetry. Thank you very much for trying our package, and let us know if there are any issues.

Since the problem has been fixed, I will close this issue. Thank you again!


How to not cleanup the container upon failure

Issue Type

Question

Molecule and Ansible details
ansible --version
ansible 2.6.3

molecule --version
molecule, version 2.19.0

Molecule installation method (one of):
pip
Ansible installation method (one of):
OS package
Desired Behavior
Molecule should provide a way not to destroy the container upon a test failure.
Actual Behaviour (Bug report only)
When a testinfra test fails (or any other failure for that matter), molecule immediately cleans up the created container.
It would be useful to 'suspend' the cleanup process in order to be able to inspect the container (ps exec -it xxx /bin/bash) in order to troubleshoot the error.
Unfortunately, the --debug option is not sufficient.
One use case is the following:

molecule dies in the 'idempotent' part of the scenario
the failure is related to a service that should be restarted
even with the --debug switch, the only details provided by molecule are the stdout and stderr
in some cases (for instance restarting the postfix service), only the syslog provides information about the reason of the failure
since molecule cleans up the container, there is no way to access this syslog

molecule test --destroy never

Thanks. I was sure molecule was great enough to already have this.
BTW, thanks for molecule!
On Oct 18, 2018 22:23, įoнииγ įoнииγ<EMAIL_ADDRESS>wrote:
molecule test --destroy never
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/metacloud/molecule/issues/1516#issuecomment-431147645, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACi1_3KOEIAkkybmmER4LgbEVDzFO3Riks5umONSgaJpZM4XtPFb.

@jaepetto no problem amigo! \m/


[Feature]: Introduce the seamless integration of AMS Catalog Service and Flink Engine

Description
AMS offers a Catalog service that can handle various formats such as iceberg, mixed hive, and paimon (as per #1269). The aim is to provide a speedy method of interfacing with the Flink engine without needing to create a catalog through Flink SQL DDL or Java. Ideally, I would like to find a way to seamlessly integrate with the Flink engine, thus avoiding the need to create AMS catalogs through flink SQL or Java.
Use case/motivation
One potential use case for AMS Catalog Service's support for multiple formats is for companies looking to improve the speed and efficiency of their data processing. By seamlessly integrating with the Flink engine, AMS Catalog Service allows for faster and more efficient data processing without the need for creating catalogs through flink SQL or Java. This can save companies time and resources while improving their overall data processing capabilities.
Now creating catalogs in AMS:

To access the AMS metadata using the Flink engine, we must create Flink Catalogs and register them into Flink's CatalogManager individually.
create catalog amoroCommerce With ('type'='arctic', 'metastore.url'='thrift://******:18050/hive_commerce');
create catalog amoroTrino With ('type'='arctic', 'metastore.url'='thrift://******:18050/hive_trino');
select * from amoroCommerce.db.table;
select * from amoroTrino.db.table;

Or through the Java language:
tableEnv.registerCatalog("hive_commerce", amoroCatalog1);
tableEnv.registerCatalog("hive_trino", amoroCatalog2);

Expected:
I want to introduce a simple way that allows the Flink engine to access all AMS Catalogs directly.
select * from amoroCommerce.db.table;
select * from amoroTrino.db.table;

Avoid users creating and registering AMS catalogs.
Describe the solution
1. Based on Flip-295 provide CatalogStoreFactory store AMS catalogs.
Using Configuration:
AMSCatalogStore will fetch and save AMS catalogs through the specific AMS thrift address.
table.catalog-store.kind: ams
table.catalog-store.ams.url: thrift://******:18050

Using Table API
public class CatalogStoreExample {
    public static void main(String[] args) throws Exception {
        // Initialize a catalog Store
        CatalogStore catalogStore = new AMSCatalogStore("thrift://******:18050");

        // set up the Table API
        final EnvironmentSettings settings =
                EnvironmentSettings.newInstance().inBatchMode()
                        .withCatalogStore(catalogStore)
                        .build();

        final TableEnvironment tableEnv = TableEnvironment.create(settings);
    }
}

Limitation: Flip-295 implements in version 1.18.
2. Provides a custom TableEnvironment with built-in AMS catalogs
public class FlinkTableEnvironmentImpl extends TableEnvironmentImpl {
    public FlinkTableEnvironmentImpl(CatalogManager catalogManager, ...) {...}

    public static TableEnvironmentImpl create(EnvironmentSettings settings) {
        // create a CatalogManager by the CatalogManagerBuilder.
        CatalogManager cm = new CatalogManagerBuilder().amsMetastoreAddress("").build();

        return new FlinkTableEnvironmentImpl(cm, ...);
    }
}

public class CatalogManagerBuilder {
    String amsMetastoreAddress;

    public CatalogManager build() {
        CatalogManager catalogManager =
                CatalogManager.newBuilder()
                        .defaultCatalog(this.defaultCatalog, buildDefaultCatalog())
                        .build();

        registerCatalogFromAMS(catalogManager);
        return catalogManager;
    }

    public CatalogManagerBuilder amsMetastoreAddress(String address) {
        this.amsMetastoreAddress = address;
        return this;
    }

    public void registerCatalogFromAMS(CatalogManager cm) {
        // fetch the catalogs from AMS by the thrift address, and register the catalogs into CatalogManager.
        cm.registerCatalog(name, catalog);
    }
}

public class Example {
    public static void main(String[] args) throws Exception {
        // set up the Table API
        final EnvironmentSettings settings =
                EnvironmentSettings.newInstance().inBatchMode().build();

        final TableEnvironment tableEnv = FlinkTableEnvironment.create(settings);
    }
}

The above two approaches are just a simplified description of the outline, the detailed design will be initiated again later.
Anyone who is interested can take part in the discussion.
Subtasks
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

This is a good idea, we are designing such a catalog management system, but we have to consider the low version of Flink (<1.18);

@dpengpeng  Thanks for your feedback. What tool do you use to submit the Flink SQL task, Flink SQL-Client, Flink SQL-Gateway, or internal submission tool?

@YesOrNo828 We consider using flink sql client, which also supports the use of TABLE/SQL API to write Java job running tasks.

@YesOrNo828 Do you consider external data sources such as MysqlCatalog, KafkaCatalog, etc.

@baiyangtx On the Alibaba Cloud Flink VVP platform, a variety of catalogs have been supported, such as KafkaCatlaog and MysqlCatalog. They can directly use Flink SQL to query table data and metadata information. We guess whether it is also possible to use a custom Catalog to manipulate external data sources.

@baiyangtx On the Alibaba Cloud Flink VVP platform, a variety of catalogs have been supported, such as KafkaCatlaog and MysqlCatalog. They can directly use Flink SQL to query table data and metadata information. We guess whether it is also possible to use a custom Catalog to manipulate external data sources.

Expanding support for more data source types and enabling smoother usage of multiple catalogs in Flink SQL is a fairly broad topic. Here, I will break it down and discuss it further.

Expanding support for more formats within a single Catalog.
Currently, for computing engines, Catalogs are essentially equivalent to data source types, but from the perspective of Catalog Services, a Catalog is an index of tables. A Catalog is not limited to a single type of table. Traditional Metastores like Hive can register tables of various types. Users are concerned with the business attributes of tables rather than storage formats.
Currently, the community is working on a feature called UnifiedCatalog. This feature allows for multiple formats to be supported within one Catalog created on AMS. Rather than creating multiple Catalogs for each table type, the engine can use various data lake formats under a single database based on business needs. This is a planned feature in this year's roadmap, and you can track its progress through this issue.
#1061

Eliminating the need for the computing engine to repeatedly create Catalogs.
Even with UnifiedCatalog, if multiple Catalogs are created due to business needs or federation is required between multiple Hives, the computing engine still needs to use CREATE CATALOG multiple times to point to the Catalog on AMS. We hope to provide a way for the computing engine to only configure the URI of AMS rather than the specific URI of each Catalog, so that when using Flink SQL, the user can write SQL like SELECT * FROM catalog.db.table without having to write CREATE CATALOG. This feature is called CatalogManager or CatalogStore. This issue is currently discussing this matter.
For Flink 1.18, CatalogStore is a natively supported feature, and we can complete this process by implementing the standard Flink CatalogStore API. However, for lower versions of Flink, it is not possible to provide such a non-invasive solution. A feasible solution is to provide an Amoro version of TableEnvironment, which can be easily implemented for SQL tasks submitted by packaging into jars through Maven dependencies. However, if Flink SQL Client or Flink SQL Gateway is used directly, the corresponding Flink source code must be modified to use this feature.

Extend UnifiedCatalog and CatalogStore to non-data lake tables, such as Kafka Topic Table.
Since Amoro was originally positioned as a lake table management platform on the data lake, when designing related features at the beginning, only how to connect to lake tables was considered. However, it now appears that serving as a metadata center for stream processing is also valuable, so we are also discussing how to expand the supported table format types.
One proposed solution is to allow InternalCatalog to register Kafka Topic Tables. As Kafka Topic Tables naturally do not have metadata services, Kafka itself can be considered a storage cluster, so kafka topics can be registered in InternalCatalog and accessed through UnifiedCatalog and CatalogStore. For other tables such as MySQL Tables, they can be registered as ExternalCatalog. This ultimately achieves the requirement of querying all types of tables required in stream processing tasks through Flink SQL.
However, this process has not been included in the roadmap yet.

If you are interested in those features, you can participate in the development together. Step 3 of expanding data source types can begin after supporting UnifiedCatalog in Step 1, without waiting for Step 2.

@YesOrNo828 Do you consider external data sources such as MysqlCatalog, KafkaCatalog, etc.

@dpengpeng  @baiyangtx  Glad to see the active discussion for enhancing the seamless integration of AMS and compute engines.
I'd like to share some thoughts on this:

We consider expanding the data sources, such as message queues, and relational databases. That is mentioned in here, but when would expend data source? It depends on the community.

Expanding support for more formats within a single Catalog.
How can this conflict be avoided and resolved if different catalogs have the same database or table name?
Some methods to consider are as follows: Give the user an option to choose, keep the former db/tables, keep the latter db/tables, or delete the conflicting db/tables
@baiyangtx @dpengpeng  WDYT?

@YesOrNo828 Do you consider external data sources such as MysqlCatalog, KafkaCatalog, etc.

@dpengpeng @baiyangtx Glad to see the active discussion for enhancing the seamless integration of AMS and compute engines.
I'd like to share some thoughts on this:
1. We consider expanding the data sources, such as message queues, and relational databases. That is mentioned in[ here](https://amoro.netease.com/docs/latest/catalogs/#future-work), but when would expend data source? It depends on the community.

2. Expanding support for more formats within a single Catalog.
   How can this conflict be avoided and resolved if different catalogs have the same database or table name?
   Some methods to consider are as follows: Give the user an option to choose, keep the former db/tables, keep the latter db/tables, or delete the conflicting db/tables
   @baiyangtx @dpengpeng  WDYT?

3. It makes sense to store the table metadata of KafkaCatalog(PlusarCatalog) in AMS.

How can this conflict be avoided and resolved if different catalogs have the same database or table name?
There won't be such conflict issue. The Catalog itself will solve this problem, which is also the core capability of the Catalog.


Examples often put objects just out of reach

Environment

GitHub
f46a07aa6455d4c0c59349f346b50aaad2cc55d4
5.5.1f1
Oculus
Oculus Utilities

Steps to reproduce
Have a smallish 2x2 playspace
Start any of the examples that use interactable objects like 005, 006, 014
Try to manipulate the objects
Expected behavior
Being able to easily manipulate the objects
Current behavior
Objects are often just inside, overlapping or even completely outside the play boundaries making them impossible to reach.
I think all examples that have interactable objects should enable teleporting.

I tend to agree with this assessment. Not including teleportation may make the minimum required scripts/setting in the examples more apparent, but there is a usability issue in smaller playspaces.

I had to go through and manually add teleportation to the play space (create play space) for a ton of them..  as well as add the current "update poses" script ...
Took so much time :/ but I became an expert at vrtk teleportation implementation (;

Also of interest with regard to adding teleport to every scene: #763
@KavanBahrami Good news is VRTK now fixes Valve's bugs, too: https://github.com/thestonefox/VRTK/commit/0b3b18535515f6208f780bacf955d3dd87810637

I think again this is a candidate for the new example scene thoughts.
I'm thinking some form of locomotion you can toggle.
I'm going to link these issues to this one: https://github.com/thestonefox/VRTK/issues/763
You ok for me to close this as it's now linked?


Option to be able to supply a theme for Shiki

Search Terms
Theme, Shiki
Problem
Our brand colours are basically a dark theme.  Typedoc is great at enabling you to create custom themes, but I don't see anywhere we can change the Shiki theme.  So when we render code it looks horrible.

Suggested Solution
I see here on line 28 that it is using a fixed light-plus.  It would be good if it was possible to pass in the theme.
Maybe an option such as highlight-theme where you can pass in one of the themes.
Could be added to the typedoc.json file

PR welcome! Should be fairly straightforward to implement. highlight-theme is good for now - but in 0.21 will need to be replaced with separate options for light and dark themes.

PR welcome! Should be fairly straightforward to implement. highlight-theme is good for now - but in 0.21 will need to be replaced with separate options for light and dark themes.

what is your thinking for 0.21?
my thinking with highlight-theme option would be to pass one of the actual Shiki themes through
export type Theme =
  | 'dark-plus'
  | 'github-dark'
  | 'github-light'
  | 'light-plus'
  | 'material-theme-darker'
  | 'material-theme-default'
  | 'material-theme-lighter'
  | 'material-theme-ocean'
  | 'material-theme-palenight'
  | 'min-dark'
  | 'min-light'
  | 'monokai'
  | 'nord'
  | 'slack-theme-dark-mode'
  | 'slack-theme-ochin'
  | 'solarized-dark'
  | 'solarized-light'

ie --highlight-theme slack-theme-dark-mode or via json "highlight-theme": "slack-theme-dark-mode"

what is your thinking for 0.21?
my thinking with highlight-theme option would be to pass one of the actual Shiki themes through
export type Theme =
  | 'dark-plus'
  | 'github-dark'
  | 'github-light'
  | 'light-plus'
  | 'material-theme-darker'
  | 'material-theme-default'
  | 'material-theme-lighter'
  | 'material-theme-ocean'
  | 'material-theme-palenight'
  | 'min-dark'
  | 'min-light'
  | 'monokai'
  | 'nord'
  | 'slack-theme-dark-mode'
  | 'slack-theme-ochin'
  | 'solarized-dark'
  | 'solarized-light'

ie --highlight-theme slack-theme-dark-mode or via json "highlight-theme": "slack-theme-dark-mode"

--highlight-theme seems good to me.
0.21 will require splitting this into --highlight-theme-light and --highlight-theme-dark since TypeDoc's default theme then will include both light and dark modes that users can choose between (much like Rust's docs https://doc.rust-lang.org/std/vec/struct.Vec.html)

--highlight-theme seems good to me.
0.21 will require splitting this into --highlight-theme-light and --highlight-theme-dark since TypeDoc's default theme then will include both light and dark modes that users can choose between (much like Rust's docs https://doc.rust-lang.org/std/vec/struct.Vec.html)

@Gerrit0 I have just created a pull request for the initial --highlightTheme option.
This will clearly need to change in 0.21. I'll be happy to port that over to 0.21 if you have a copy of that somewhere

@Gerrit0 I have just created a pull request for the initial --highlightTheme option.
This will clearly need to change in 0.21. I'll be happy to port that over to 0.21 if you have a copy of that somewhere

Awesome! Thanks :)
0.21 isn't in a state yet to need this, I'll merge it in once it is.

Awesome! Thanks :)
0.21 isn't in a state yet to need this, I'll merge it in once it is.

Resolved by #1486, releasing in v0.20.20, in half an hour or so

Resolved by #1486, releasing in v0.20.20, in half an hour or so

Champion, thanks @Gerrit0

Champion, thanks @Gerrit0


Add missing B&R features

Add the following missing UI features wrt B&R:

Add offering support that imports external offering
Support for backup user-defined schedule
Restore volume and attach it to a VM from a backup

Screenshots:

@utchoang cc @svenvogel since you'd done the snapshot schedule feature, can you pick this up - see http://primate-qa.cloudstack.cloud:8080/client/ for example of a backup schedule on the 'AdminFirstVM' VM. If possible can you prioritise this over your NSP support work? Thanks.

Hi @rhtyd , I can't connect to http://primate-qa.cloudstack.cloud:8080/client/ because when login I have gotten the message: "Invalid username or password.
This could also be a restriction on the IP address you are connecting from."
Although I have an input username / password correct.

Hi @utchoang can you try again, there was an issue at mysql/mgmt server that has been temporarily fixed.

Tested, LGTM.


Integrate krel obs into the release process

First of all we have to publish the release artifacts to the Google Cloud Bucket:
kpromo gh --org kubernetes-sigs --repo cri-tools --bucket k8s-artifacts-cri-tools --release-dir release --tags v1.28.0

Publishes the GitHub artifacts in https://console.cloud.google.com/storage/browser/k8s-artifacts-cri-tools/release
Then we need to run the following commands to release cri-tools in OBS:
krel obs stage --packages cri-tools --version 1.28.0 --project isv:kubernetes:core:stable:v1.28:build --stream --nomock

Runs a Google Cloud Build job and stages:
https://build.opensuse.org/package/show/isv:kubernetes:core:stable:v1.28:build/cri-tools
krel obs release --packages cri-tools --stream --project isv:kubernetes:core:stable:v1.28:build --nomock

Runs a Google Cloud Build job and releases:
https://build.opensuse.org/package/show/isv:kubernetes:core:stable:v1.28/cri-tools.20230814075509
Goal is to integrate the steps above into our release workflow, containing the right amount of permissions:
https://github.com/kubernetes-sigs/cri-tools/blob/master/.github/workflows/release.yml
@kubernetes-sigs/release-engineering we need:

OBS credentials to run krel obs
A service account token to access  k8s-artifacts-cri-tools

I can help with this. I'll add this issue to our project board so that we properly follow it.

Shouldn't this be in kubernetes-release, rather than cri-tools ?

The automation will happen in this repository, we can also consider moving the specfile here.

@kubernetes-sigs/release-engineering how about:

Creating a bot account similar to CRI-O to be able to publish packages for cri-tools
Move the specfile into this repository
Create an publish them similar to https://github.com/cri-o/packaging, but triggered by tags as part of this GitHub action: https://github.com/kubernetes-sigs/cri-tools/blob/master/.github/workflows/release.yml

@saschagrunert I think this is a solid plan. I would only try to avoid having a new repo for packaging (because getting repos in k or k-sigs is a more complicated process and it's not scalable).

@saschagrunert Yes, please create an issue in k/k8s.io to track getting a new service account.

@xmudrii closing the loop: https://github.com/kubernetes/k8s.io/issues/5957

/remove-lifecycle stale

We still need this, and could also think about proposing an automated vendor PR for the RC of a new Kubernetes version. This could include a hint that we may want to cut a release afterwards.

/remove-lifecycle stale

@xmudrii do you plan to work in this before v1.31 get's released?

@saschagrunert Yes, I'll be looking into this issue this week.
/assign

Let me know if you need anything, would be awesome to deliver it this cycle.

@xmudrii I'm planning to release cri-tools v1.31 this week. Do we still want to invest in automation or plan that for 1.32?

It's on my TODO list and we'll have it in place for v1.32. :shipit: Sorry for delay!

/remove-lifecycle stale


Got honor I shouldn't have

I unlocked a solution for a kata I was struggling with, then entered one of the correct solutions as I thought it was functionally equivalent to mine. It worked and gave me a load of honor, which I shouldn't have since unlocking solutions should prevent gaining honor for the kata.
Is there a way I can delete the honor I got from this?

I'm pretty sure this doesn't happen anymore.


jsubfinder: init at unstable-2022-05-31

Description of changes
Tool to search for in Javascript hidden subdomains and secrets
https://github.com/ThreatUnkown/jsubfinder
Related to #81418

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 178157 run on x86_64-linux 1

1 package built:

jsubfinder


Updating the bignum package source to a fork that works on Nim 0.20

The original repo https://github.com/FedeOmoto/bignum hasn't been
maintained in many years.
I am not an expert in bignum but I am maintaining a fork of it that
runs with the latest stable Nim version (v0.20.0 as of today).

CC @FedeOmoto


Generate request params as particular type

Hello!
I'm using this command for generate npx swagger-typescript-api -p public/swagger/v2.json -o ./assets/v2/src/api -n apiClient.ts --type-prefix=T
and I have this route in generated output.
      data: {
        firstName?: string;
        middleName?: string | null;
        lastName?: string;
        birthday?: string;
        gender?: TGender;
        phones?: string[];
        addresses?: TAddress[];
        contacts?: TContact[];
        avatar?: string | null;
        timezone?: string;
      },
      params: RequestParams = {},
    ) =>
      this.request<void, void>({
        path: `/user/profile`,
        method: "PUT",
        body: data,
        secure: true,
        type: ContentType.Json,
        ...params,
      }),

Is it possible to have particular interface with request type, e.g.
        middleName?: string | null;
        lastName?: string;
        birthday?: string;
        gender?: TGender;
        phones?: string[];
        addresses?: TAddress[];
        contacts?: TContact[];
        avatar?: string | null;
        timezone?: string;

Tried --extract-request-params and --route-types but no luck

Next release will have --extract-request-body option

Thanks @js2me
But seems like this feature doesn't use prefix.
Command:
npx swagger-typescript-api -p public/swagger.json -o ./assets/app/api -n apiClient.ts --type-prefix=T --extract-request-params --extract-request-body --route-types

Generated file contains correct declaration with prefix needed (T in my example):
export interface TAppControllerApiControllerPostRequestActionPayload {
  goods: TRequest[];
}

but lines below are looking for AppControllerApiControllerPostRequestActionPayload, without prefix:
export namespace AppControllerApiControllerPostRequestAction {
    export type RequestParams = {};
    export type RequestQuery = {};
    export type RequestBody = AppControllerApiControllerPostRequestActionPayload;
    export type RequestHeaders = {};
    export type ResponseBody = { uid: string; code: string };
  }

appControllerApiControllerPostRequestAction: (
      data: AppControllerApiControllerPostRequestActionPayload,
      params: RequestParams = {},
    ) =>
      this.request<{ uid: string; code: string }, any>({
        path: `/requests`,
        method: "GET",
        body: data,
        type: ContentType.Json,
        format: "json",
        ...params,
      }),

Checked it with recent version and it works like a charm. Thank you.


Auto-populate sort title

Look at feature in current LAE app--does it use language or is it just a canned list of articles?

This is language-dependent and configured in the current LAE app here: https://github.com/pulibrary/pul-store/blob/development/config/pul_store.yml.tmpl#L8-L28

Since language is a multi-select right now, how do we tell which is the title language?  Do we just use the first one?

Where "first" is ever changing. I guess thats the best we can do.

I think the current app uses dc:title for the first title, and
dc:alternative for the rest. That should solve one part of this. I'd say go
with the first language entered for the other.
-Js
Sent via mobile. Please excuse typos, brevity, etc.
On May 8, 2017 3:20 PM, "Trey Pendragon"<EMAIL_ADDRESS>wrote:
Where "first" is ever changing. I guess thats the best we can do.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pulibrary/plum/issues/1253#issuecomment-299964234, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA9BFStUUHxlOIf0_5lVBEEiyq5idmRAks5r32rhgaJpZM4NSWZj
.


[typescript]: "implements" keyword not highlighted properly

Using 0.10.7-insider on Windows 7
The implements keyword isn't highlighting correctly

duplicate of https://github.com/Microsoft/TypeScript-TmLanguage/issues/38


Company DashBoard

Figma Link

/assign

@ankit2001 what is the related PR for this issue?  Can you please link all PRs to issues?

This issue requires API.

This would be a good screen to do next.

Okay, sure!

@fredfalcon the screen has been made, I suggest you to close this issue.


Feature : Write console outputs to File

A logging flag that could enable a write-to-file module to keep a trace of games we played and chat logs. (as it shows on the console I guess)
The actual log files are more technical than details printed on our console ...

What would be use case of this?

I mean could be added as an optional feature

I mean could be added as an optional feature

Yeah ! Like the chat print basically, by default to false, that's why I was mentioning the fact that it could be a flag 😃

Added in 6d0ac04a20baa6dd79c84e2902240b033ba78b62 for now just terminal output but later will add more technical details


Support for unique ids when referencing paths

Fixes #29
Pretty simple change,  tags are included in the suffix pass and xlink:href and href are updated accordingly. The basic and performance tests pass for me locally, the fallback tests fail but they also fail on the current master branch? Not sure what's going on there.

Thanks for the pull request. #29 has been fixed with a more generic solution, so I am closing this one.


added option for showing different message when using dsym only option

Thanks for contributing to fastlane! Before you submit your pull request, please make sure to check the following boxes:

[x] Run bundle exec rspec from the subdirectory of each tool you modified. Alternatively, run rake test_all from the root directory.
[x] Run bundle exec rubocop -a to ensure the code style is valid
[x] Read the Contribution Guidelines
[x] We currently don't accept new actions, please publish a plugin instead, more information in Plugins.md

Before submitting a pull request, we appreciate if you create an issue first to discuss the change :+1:
Fix for #7492

This is great, thank you so much for your contribution @RishabhTayal 👍


[master] Bump Mesos to nightly master 4b9a0d5

High-level description
This is a routine bump to the latest Mesos and mesos-modules.
Related JIRA Issues
Checklist for all PRs

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Changelog:
https://github.com/apache/mesos/compare/84749967a1c1384f75c3c017bda45a85eea67787...4b9a0d553492731c3529cda1e3938591fbdba9dc

[ ] Test Results: [link to CI job test results for component]

[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot bump-ee

Closed in lieu of https://github.com/dcos/dcos/pull/3318


:bug: fix extract_target

close due to https://github.com/MountainDash/nonebot-plugin-send-anything-anywhere/issues/113