Documentation Website for the project

Requirements and/or Suggestions

Use Mkdocs
Exclusively use docs branch : Delete everything there except README, LICENSE and CODE OF CONDUCT Files
Setting up the website (to be specific the frontend ) is really simple with mkdocs. The real task is organizing the content
The main sections/pages would be:
- Home Page
- Sketch Page
- Editor Page
- MediaManip Page
- SEO
- Optimization
- Hosting
- Team
For each of the sections/pages, explain how to achieve the particular of the codes, for example, the download feature for Editor Page or Fill Style in Sketch Page.
This issue would take time and will be assigned to more than one participant at a time. I don't expect you to do the entire documentation in one PR.  Try to give 1-3 PRs for each page

Reference:

Sample Website
Corresponding Code

Assign me pls

@himanshujaidka Assigned. At max 4 more people can be assigned. Future assignees please collaborate with him. Deadline to first PR for this issue: 26th, April

@smaranjitghose I also want to work on this issue please assign me

I want to work on this issue

I want to work on this issue

Collaborate with @subhangi2731  please

Please assign me this issue under LGMSOC'21


Add rest of series names to gdoc

Add rest of series names to gdoc - moo is doing this

done

done


Bug: jsx-no-leaked-render faulty autofix

Version: 7.30.1
Config:
'react/jsx-no-leaked-render': ['error', { validStrategies: ['coerce', 'ternary'] }],

Before fix:
const MyComponent = () => {
  const items = []
  const breakpoint = { phones: true }

  return
{items.length > 0 && breakpoint.phones && }

}

Post fix:
const MyComponent = () => {
  const items = []
  const breakpoint = { phones: true }

  return
{!!!!!!!!!!!!!!!!!!!!items.length > 0 && breakpoint.phones && }

}

Expected:
const MyComponent = () => {
  const items = []
  const breakpoint = { phones: true }

  return
{items.length > 0 && !!breakpoint.phones && }

}

On top of that, the auto fix is quite slow.

The exclamation points definitely seem like a bug that should be fixed, and i agree that the > comparison shouldn't be touched since it can only ever be a boolean.
The autofixer's performance is something that can be improved separately, but isn't as concerning.

I identified the issue but I need more time to rework the fix functionality to solve it.

@Belco90 I created a PR to fix the multiple ! issue during autofix. Feel free to review it!

@Belco90 I created a PR to fix the multiple ! issue during autofix. Feel free to review it!

That's amazing! I'll try to review it later today. Thanks.

I'm having a similar experience:
Original
{!sourceQuestData && loadingSourceQuest && (

)}

Result
{!!!!!!!!!!!!!!!!!!!sourceQuestData && loadingSourceQuest && (

)}

Similar to the OP, the !sourceQuestData should not have been touched. loadingSourceQuest is a boolean already, so it does not need to be touched either.
Adding to booleans
I also see it adding !! to variables that are already clearly a boolean:
const showComponent = editMode || item.status === "COMPLETED";

  return (
    <>
      {!!showComponent && (...)}
    </>
  )

This should be fixed by #3353.


Bug 1883701: operator/ingress: Restore scale subresource

Restore the IngressController CRD's "scale" subresource.
#720 inadvertently deleted the "scale" subresource.

operator/v1/0000_50_ingress-operator_00-ingresscontroller.crd.yaml: Add spec.versions[].subresources.scale.

/bugzilla refresh

/lgtm
/approve


docs(README): update URLs of plugins and loaders

This PR updates the outdated URLs of the links to the plugins and loaders.

What kind of change does this PR introduce?
documentation

Did you add tests for your changes?
N/A

Does this PR introduce a breaking change?
N/A

What needs to be documented once your changes are merged?
N/A

Thanks


Debounce context update for performance improvement

Here's a test of before / after using synchronized tmux panes
https://user-images.githubusercontent.com/506791/122118297-ba7a2b80-cddc-11eb-8d06-d067cac2f7bd.mp4
There was already a method for throttling the update, but it wasn't called in the important places and the logic could be simplified.

Thanks

Sorry had to make it into an option because it was causing issues on my setup that I don't have time to debug.
require'treesitter-context'.setup{
    enable = true, -- Enable this plugin (Can be enabled/disabled later via commands)
    throttle = true, -- Throttles plugin updates (may improve performance)
}

Oh damn! I'll dig in and see if I can find what might be going wrong. What are the problems that you're seeing?

Would be nice to be able to configure it within require('nvim-treesitter.configs').setup({}) table.

When the context window is opened, the current buffer isn't marked anymore as current in barbar, so there are probably autocommands that are running but shouldn't be running when the context window is opened. We should use noautocmd because there is really no reason for other plugins to listen to the state of our window & buffer.

Tested adding noautocmd = true to the nvim_open_win, and it does fix the focus issue with barbar. Makes sense; opening the window from a defer_fn is going to allow all the normal autocmds to fire, where previously the window was getting opened from inside a non-nested WinScrolled autocmd or similar, which would prevent them from firing.
Also, FWIW I'm not seeing the same terrible lag when I scroll through files even without the debouncing code. Maybe something in nvim-treesitter changed to improve performance, or maybe I changed something else in my vim config that put me under the frame budget. Either way, I wouldn't be sad if the debouncing logic got cut to simplify things.

For me this PR made a bit difference. I had context plugin disabled for a while waiting for this PR to be merged. Works really nice now. Thanks @stevearc!

@stevearc If you have enough time to push either a fix or a cleanup go ahead, otherwise I'll just leave as it is until I have time to do stuff.


refactor type handling

Internally, I think that type should be stored as an enum and that there should be two constructors : one for string with standardiye_type and one for the enum. Otherwise, LGTM.

Internally, we could use an enum class for safety reasons, but having two constructor versions feels a bit unnecessary. I'd vote for enum internally, string externally (also with py interface in mind).

Internally, I think that it goes without saying. Externally (i.e., for the constructor), I'd argue for the enum  too, as it is what we do in vinecopulib for the families. Now that you mention it, it is clearly clunky (and borderline nonpythonic) in pyvinecopulib, but for the C++ code, I believe that it's the right thing to do.


test using jitclass in typed-list

Setting up a list with jitclasses seems to be fine, but they can not be
compared yet.

Current error is:
💥 zsh» python -m numba.runtests numba.tests.test_typedlist                                                                                :(
......................E..........
======================================================================
ERROR: test_jitclass_as_item_in_list (numba.tests.test_typedlist.TestListRefctTypes)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/vhaenel/git/numba/numba/tests/test_typedlist.py", line 714, in test_jitclass_as_item_in_list
    class Bag(object):
  File "/Users/vhaenel/git/numba/numba/jitclass/decorators.py", line 27, in wrap
    return register_class_type(cls, spec, types.ClassType, ClassBuilder)
  File "/Users/vhaenel/git/numba/numba/jitclass/base.py", line 204, in register_class_type
    raise TypeError(msg.format(members))
TypeError: class members are not yet supported: __hash__

----------------------------------------------------------------------
Ran 33 tests in 11.147s

FAILED (errors=1)
python -m numba.runtests numba.tests.test_typedlist  11.51s user 0.20s system 99% cpu 11.726 total

Updated the PR with the suggestion from code review.

Looks good, thanks for the fix ups. Can be marked for merge on CI pass.


Update README.md to Korean version

Proposed changes:

...

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

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

@chws0508 Thank you for your contribution!
However I cannot approve this PR because we currently only maintain documentation in English due to limited resources.
However the Rasa framework can be used in many different languages (including Korean).


Update documentation

Merge unit test for differential correction method for the uncoupled system.
Initiate work on updating docs for methods.
Fixes #2, fixes #7, fixes #47, fixes #48

Could you make sure the build artifacts in docs/_build aren't checked in to git (docs/_build should be in your .gitignore)? Read the Docs will build from source anyway, and it makes the repo a lot less noisy. Same with ``build/` for package build artifacts.
Otherwise, LGTM!

@dpsanders can you have a look at these changes? Thanks!

The docs are looking very nice! +1


package is not in the npm registry

Could you please make this repo available not only in bower but also in the npm registry? Thanks

Yep, it's available on npm now.


Remove events we no longer collect

As far as I can tell, we are still getting ABS and ESP lamps from Traffilog. We have received ABS and ESP disabled events as recent as this morning.

ASB, EPS, and Airbags are perhaps not the datasets where we get the most data, but it does remain a very sought after dataset for the road authorities and anything related to road conditions. The airbag data is also very interesting for insurance companies.
Is this a change to reflect that we mostly do not get data or is it the strategy that this is something we will strategically not receive going forward?


Fix lapack target

Initialize CLAPACK_FOUND when LAPACK falls back to clapack

What does your PR fix?
Fixes #18679

Which triplets are supported/not supported? Have you updated the CI baseline?
all previously supported, No

Does your PR follow the maintainer guide?

Yes

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

Related to https://github.com/microsoft/vcpkg/pull/18707

Closing in favor of https://github.com/microsoft/vcpkg/pull/18707, I would continue that PR next week.


Review design of parameters

Should parameters be one to one like :
function(yes = "yes, no = "no")

or
function(levels = c("yes", "no"))

Based on the outcome of this discussion, update and review package and/or clarify documentation.

@sunheemoraes Linking issue #547 here if it becomes a broader conversation on the whole package.

Hello, adding here as most likely linked to this: if you decide to stick to the actual design of parameters as an ordered vector (which I personally do not recommend, as I already saw this leading to mis-categorizations having quite broad consequences on the final results), consider to update the descriptions of the parameters as in some cases they are not coherent with the actual order expected by the function.

Example 1: add_comp_wash has @param setting_levels Levels for the setting in that order: camp, rural, urban. [line 5], but the order should be setting_levels = c("camp", "urban", "rural") instead [line 25]
Example 2: none as first option for param issue_cat_levels in add_comp_snfi, as already flagged in #545 .

Cheers:)


getScreenSize doesn't support multiple monitors

I'm working on a project but I can't continue until RobotJS supports using multiple monitors with getScreenSize.
A way around this or a change to the function would be nice!

(No arguments)*

I am using systeminformation for this purpose. Works great, but I need to figure out the screen's edges depending on the other monitors' positions. Quite a challenge in both Python and Node.js, it turns out. I may have to teach myself c++.


Your Website is down

Hello there, you website is down... (http://vadimg.com/) there is another way to get the examples?
Thank!

@Asinox sorry. its back up. for demo you can just clone and check the examples directories as well.


Update lodash version to 4.14.0

Thanks for the report, this is a duplicate of #1812 where the current status of this is tracked


Current version of JupyterLab not supported.

when ran this in the console
jupyter labextension install jupyterlab_voyager
got this error
`An error occured.
ValueError: The extension "jupyterlab_voyager" does not yet support the current version of JupyterLab.
Conflicting Dependencies:
JupyterLab                        Extension      Package

=2.0.2 <2.1.0                    >=1.0.3 <2.0.0 @jupyterlab/application
=2.0.2 <2.1.0                    >=1.0.3 <2.0.0 @jupyterlab/apputils
=2.0.2 <2.1.0                    >=1.0.3 <2.0.0 @jupyterlab/console
=4.0.2 <4.1.0                    >=3.0.0 <4.0.0 @jupyterlab/coreutils
=2.0.2 <2.1.0                    >=1.0.3 <2.0.0 @jupyterlab/docmanager
=2.0.2 <2.1.0                    >=1.0.4 <2.0.0 @jupyterlab/filebrowser
=2.0.2 <2.1.0                    >=1.0.3 <2.0.0 @jupyterlab/notebook
=2.0.2 <2.1.0                    >=1.0.3 <2.0.0 @jupyterlab/rendermime
=2.0.1 <2.1.0                    >=1.3.0 <2.0.0 @jupyterlab/rendermime-interfaces
See the log file for details:  C:\Users\CHITIR~1.ESW\AppData\Local\Temp\jupyterlab-debug-lt24c2m4.log`

-- JupyterLab version -- 2.0.1

Any update on this one?

I'm also getting dependency conflicts after just recently reinstalling anaconda
Conflicting Dependencies:
JupyterLabExtension        Package
>=16.8.4 <16.9.0>=16.9.0 <17.0.0 react
>=16.8.4 <16.9.0>=16.9.0 <17.0.0 react-dom

jupyterlab_voyager" does not yet support the current version of JupyterLab

Is there a roadmap or estimated time frame for support?

TL;DR- we need datavoyager upstream to be ported to react 16.
The 'Conflicting Dependencies:' text comes from some checks in jupyterlab/commands.py prior to invoking yarn to build the extension. Jupyterlab 1.1 appears to have changed its approach to core dependencies, they're now listed as resolutions and singletons.
That's a problem for voyager because jupyterlab is using react 16, but the upstream datavoyager project is still on react 15.
There is an outstanding issue for them to address: https://github.com/vega/voyager/issues/843
Progress on that appears to have stalled though.
If you bypass those build checks to get voyager installed anyway, you're likely to see the following JS error (in chrome at least):
index.out.js:1439 TypeError: Cannot read property 'oneOfType' of undefined
    at Object.<anonymous> (lib-voyager.js:1)
    at t (lib-voyager.js:1)

I've tried forcing the singleton react-dom to 15.7.0 used by upstream but failed to get react-dom to load in jupyterlab 1.1.  I assume that's due to react 16 changes in jupyterlab, but I haven't bottomed that out.

any news on this?

It looks like it's officially dead: https://github.com/vega/voyager/issues/857

Awesome project! Sad to see it can no longer be supported. I think a disclaimer on the readme would be beneficial for anyone coming across this on the readme

Are there any alternatives available to edit vega-lite plots locally with a GUI?


⚠ Bofrost.de has degraded performance

In 0500703, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1538 ms

Resolved: Bofrost.de performance has improved in bdff2ed.


Change install destination

Investigating some changes to fix the install destination directory (internal issue 1427046).
Before (tabcmd src dir appears directly under site-packages):
$ find ~/.pyenv/versions/3.9.0/envs/3.9-tools -name publish_command.py
/Users/bcantoni/.pyenv/versions/3.9.0/envs/3.9-tools/lib/python3.9/site-packages/src/commands/datasources_and_workbooks/publish_command.py
After (all tabcmd is under site-packages/tabcmd):
$ find ~/.pyenv/versions/3.9.0/envs/3.9-tools -name publish_command.py
/Users/bcantoni/.pyenv/versions/3.9.0/envs/3.9-tools/lib/python3.9/site-packages/tabcmd/commands/datasources_and_workbooks/publish_command.py

Looks good. Here's the commit where I made the change to use src, which was a mistake in hindsight https://github.com/tableau/tabcmd/commit/ff9a88d72d83d1005c8c47a7c3251dec86bc62a0

Jac, yea I'm not a setup.py expert and there might be a way to force the install dir, but comparing to the TSC project just renaming that top dir seemed the simplest solution here.


feat: export fetchKeyMetadataFromApi and remove checkPolicy options

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR focuses on exporting the fetchKeyMetadataFromApi function and removing the checkPolicy options from the API call configuration in the service-utils package.
Detailed summary

Exported fetchKeyMetadataFromApi from ./core/api.js.
Removed checkPolicy option from the CoreServiceConfig type.
Eliminated the policyMetadata object from the configuration.
Simplified the URL construction in fetchKeyMetadataFromApi by removing the policy query parameters.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#4955  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @joaquim-verges and the rest of your teammates on  Graphite


Avoid allocations in lowercase comparisons

Summary
I noticed that we have a few hot comparisons that involve called s.to_lowercase(). We can avoid an allocation by comparing characters directly.

When a thing is "zero-allocation"? I love it. I go crazy for it. I can't get enough of it.

YES @Boshen! YES!!!


captureClicks captures anchor link clicks

...

Expected behaviour: page jumps to anchor element
Actual behaviour: router re-runs current component/app
I can submit a PR if wanted. I think it's just a matter of changing
captureClicks.js:42
if (link && link.indexOf('mailto:') > -1 || link === '#') {
    return;
}

to
if (link && link.indexOf('mailto:') > -1 || link.charAt(0) === '#') {
    return;
}

Something extra may be needed though to scroll down to the appropriate element after render if a hash link is visited directly/typed into address bar (i.e. http://localhost:3000/#myAnchor).

Ahh yes, PR welcomed.

By the way, I'm in the process of migrating this repo to the monorepo.

@staltz I'd go ahead and move to the monorepo, we can sort everything else out after.

This is now moved to the monorepo.

The PR there would be welcomed. :)


update recipe

replaced the table in "Create a Spore Within a Cluster" recipe with flowchart

"Do I have its private key" sounds a bit off, any suggestions? @code-monad @linnnsss @RongxinZhang

"Do I have its private key" sounds a bit off, any suggestions? @code-monad @linnnsss @RongxinZhang

sounds pretty clear to me. but there is a small logical point to consider:
Do I have its private key (though I'm not the owner)?

updated flowchart


Structured3D PTv2 and SWIN3D-v1 Pretrained Models

Hello Pointcept Team,
Thank you for providing the codebase for Point Transformer (semseg-pt-v2m2-0-base), and SWIN3D (semseg-swin3d-v1m1-0-small)!
We are training to train the model from scratch. Unfortunately in our current setting with 1 NVIDIA T4 GPU, the training time takes 30+ hours. I am wondering if you could please share the above pre-trained models with Strucutured3D.
Thank you in advance for the help you could provide!

Hi, how about just using PTv3 as it is much faster? We will soon have a better self-supervised PTv3 model weight available to the public yet won't further pre-train on PTv2 or Swin3D.


Include license file in the generated wheel package

The wheel package format supports including the license file. This is done using the [metadata] section in the setup.cfg file. For additional information on this feature, see:
https://wheel.readthedocs.io/en/stable/index.html#including-the-license-in-the-generated-wheel-file
Helps the package comply with its own license:

Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #120   +/-   ##
=======================================
  Coverage   85.77%   85.77%
=======================================
  Files          29       29
  Lines        3985     3985
=======================================
  Hits         3418     3418
  Misses        567      567

Continue to review full report at Codecov.

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

Thanks! ;)


warehouse: Use semantic forms for webauthn actions

cc @di @nlhkabu
Fixes #6472.

Thank you @woodruffw.  Ok on my side, but I will wait for @di to review for the JS :)


new ResponseReader.kt in ver. 2.0.0 is not compatible with generated classes

Summary
Kotlin version of ResponseReader is not compatible with the classes generated based on the schema.
Version
Starting from 2.0.0 up to 2.2.2
Description
Upgraded from 1.4.3. to 2.2.2 and it appears that java version of ResponseReader was substituted with Kotlin version.
I'm ok with that, but if java version always returned non-null field value for the fields, kotlin version may return null:
interface ResponseReader {
  fun readString(field: ResponseField): String?
....
}

versus how it was:
public interface ResponseReader {
  String readString(ResponseField field);
...
}

But, the constructor of the class may take an 'id' value that cannot be null, and it's described as NON_NULL in schema.
And in the code generated we see something like this:
data class MyCustomRecord(
    val __typename: String = "MyCustomRecord",
    val id: String,
    val recordId: String?
  ) // neither __typename, nor id fields can be nullable

and the code for instantiation of this class with the help of ResponseReader:
operator fun invoke(reader: ResponseReader): MyCustomRecord = reader.run {
        val __typename = readString(RESPONSE_FIELDS[0]) // String?
        val id = readString(RESPONSE_FIELDS[1]) // String?
        val recordId = readString(RESPONSE_FIELDS[2])
        MyCustomRecord(
          __typename = __typename, // cant compile case val __typename is of String? type
          id = id, // cant compile case val id is of String? type
          recordId = recordId
        )
      }

Any solutions on this?
Thanks!

The test cases generate a !! do make sure fields are not nullable but maybe there's something else.
Before we dive further, can you rerun your build with --no-build-cache? I've seen weird cases with stale generated files, especially when changing the plugin version.

Rerun it - same stuff, no changes in the code generated.
How come test classes are generated with !! ?

How come test classes are generated with !! ?

That's a very good question!! Is there any chance you can share your schema.json and graphql query?

Unfortunately, I can not give the whole schema.json(as the project is under NDA). But I can provide piece describing MyCustomRecord entity:
{"kind":"OBJECT","name":"MyCustomRecord","description":null,"fields":[{"name":"id","description":null,"args":[],"type":{"kind":"NON_NULL","name":null,"ofType":{"kind":"SCALAR","name":"String","ofType":null}},"isDeprecated":false,"deprecationReason":null},{"name":"index","description":null,"args":[],"type":{"kind":"NON_NULL","name":null,"ofType":{"kind":"SCALAR","name":"Int","ofType":null}},"isDeprecated":false,"deprecationReason":null},{"name":"code","description":null,"args":[],"type":{"kind":"SCALAR","name":"String","ofType":null},"isDeprecated":false,"deprecationReason":null},{"name":"trackId","description":null,"args":[],"type":{"kind":"SCALAR","name":"Float","ofType":null},"isDeprecated":false,"deprecationReason":null},{"name":"type","description":null,"args":[],"type":{"kind":"NON_NULL","name":null,"ofType":{"kind":"SCALAR","name":"String","ofType":null}},"isDeprecated":false,"deprecationReason":null},{"name":"caption","description":null,"args":[],"type":{"kind":"SCALAR","name":"String","ofType":null},"isDeprecated":false,"deprecationReason":null},{"name":"requireCompletion","description":null,"args":[],"type":{"kind":"SCALAR","name":"Boolean","ofType":null},"isDeprecated":false,"deprecationReason":null},{"name":"skippableByAdmin","description":"Whether this card can be skipped from OMM or not. Full list of skippable cards can be fetched from admin => settings => skippableCardTypes API","args":[],"type":{"kind":"NON_NULL","name":null,"ofType":{"kind":"SCALAR","name":"Boolean","ofType":null}},"isDeprecated":false,"deprecationReason":null},{"name":"state","description":null,"args":[],"type":{"kind":"NON_NULL","name":null,"ofType":{"kind":"OBJECT","name":"EntityState","ofType":null}},"isDeprecated":false,"deprecationReason":null},{"name":"recordId","description":null,"args":[],"type":{"kind":"SCALAR","name":"String","ofType":null},"isDeprecated":false,"deprecationReason":null}],"inputFields":null,"interfaces":[{"kind":"INTERFACE","name":"IMyCard","ofType":null}],"enumValues":null,"possibleTypes":null}
As you may see the, the id field is explicitly marked as NON_NULL in schema, but recordId is not. That is why I get error for the id.
Where in schema can I look up for the definitions that influence __typename field generation?

__typename is an implicit field of type String!.
Can you share your .graphql query? Feel free to change names, I'm mainly looking at the structure of the query, whether it contains directives, fragments, inline fragments, etc...

Hi, Martin
Here it is, nothing fancy really:
mutation AddCustomRecordCard($card_id: String!, $timeStamp:GraphQLDateTime!) {
    me {
        path{
            level{
                step{
                    card(cardId:$card_id){
                        addMoodMeterRecord(input:{timeStamp:$timeStamp})
                        { id, moodRecordId }
                    }
                }
            }
        }
    }
}

The problem is not just in this mutation, but the whole project stopped compiling. This problem is all over the place, in every query in every mutation.

Thanks for providing that!
I made a small repo to try to reproduce something as similar as possible to your schema. It is there https://github.com/martinbonnin/apollo-android-samples/tree/master/error-on-non-nullable-fields.
Can you try it and see if you catch anything weird in there or if you can modify it to make it fail? Running ./gradlew assembleApolloSources will generate the models. So far I haven't been able to reproduce (they always contain !!). One thing that could maybe have an impact is the IMyCard interface? But TBH, if it happens for all your objects, it's certainly something else.
A few other things to try:

removing options from your apollo {} Gradle block? Is there any specific configuration there?
add a simple field to your schema and verify that it works as expected: the field should be non-nullable in the generated model and the parsing code should assert it with readString(RESPONSE_FIELDS[0])!!
If it doesn't work, it certainly means the problem is not in the schema. Maybe a KotlinPoet conflict or something else.
If it works, there must be something in the schema that makes the compiler fail. Try "bisecting" your schema: remove fields/interfaces until you find

Hi, Martin,
Thanks for you sample project, I will definitely give it a whirl!
As for the suggestions:

this is the only stuff I have in apollo{} block

apollo {
    generateKotlinModels.set(true)
    customTypeMapping = ["GraphQLDateTime": "java.lang.Long"]
}

schema is server-side generated and I'm afraid I'm not that familiar with the format of how to defined instances/fields into it, but I will give it a tray

In case you're still investigating this, the latest version (2.2.3) includes support for SDL schemas which will be easier to work with if you want to experiment with your schema.
You can convert your schema.json to schema.sdl with a tool like https://github.com/potatosalad/graphql-introspection-json-to-sdl. Then adding/removing fields should be way easier.

That is very very helpful! Thanks a lot!
Unfortunately, I'm a bit overloaded right now, but I'm looking into it asap.


[Skype for Business] Bot doesn't respond due to server runtime error

Bot Info
App ID: 9ae4f666-de28-4f25-bbd0-6c8b146d717e
SDK Platform: Rest API
Active Channels: Cortana, Skype for Business
Deployment Environment:  Losant
Issue Description
Failure to deliver response back to Skype for Business client.
Was working but has stopped and now Bot engine reports error from Skype Online serviceUrl.
Reproduction Steps
Bot registered as CsOnline application endpoint.
Error can only be seen on our Losant platform where the Bot login resides.
Expected Behavior
User gets expected response from Bot.
Actual Results
Error returned when sending response back to serviceURL.
serviceURL received in message body:
https://webpoolbl20r04.infra.lync.com/platformservice/tgt-2b944806abf558c08c6194d30c1b514a/botframework
error received: statusCode 400
\r\n\r\n    \r\n        Runtime Error\r\n        \r\n        \r\n    \r\n\r\n    \r\n\r\n            Server Error in '/PlatformService' Application.\r\n\r\n             Runtime Error \r\n\r\n            \r\n\r\n             Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.\r\n            \r\n\r\n            Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".\r\n\r\n            \r\n               \r\n                  \r\n                      \r\n\r\n<!-- Web.Config Configuration File -->\r\n\r\n<configuration>\r\n    <system.web>\r\n        <customErrors mode="Off"/>\r\n    </system.web>\r\n</configuration>\r\n\r\n                  \r\n               \r\n            \r\n\r\n            \r\n\r\n            Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.\r\n\r\n            \r\n               \r\n                  \r\n                      \r\n\r\n<!-- Web.Config Configuration File -->\r\n\r\n<configuration>\r\n    <system.web>\r\n        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>\r\n    </system.web>\r\n</configuration>\r\n\r\n                  \r\n               \r\n            \r\n\r\n            \r\n\r\n    \r\n\r\n

I've a similar scenario where in the Skype for Business bot which is in the middle of a conversation fails to respond with a 400/401 error. It's very inconsistent. Not sure whats causing the 400/401 error as I faintly remember that the token is alive for almost 30 minutes.

Thank you for opening an issue against the Bot Framework SDK v3. As part of the Bot Framework v4 release, we’ve moved all v3 work to a new repo located at https://github.com/microsoft/botbuilder-v3. We will continue to support and offer maintenance updates to v3 via this new repo.
From now on, https://github.com/microsoft/botbuilder repo will be used as hub, with pointers to all the different SDK languages, tools and samples repos.
As part of this restructuring, we are closing all tickets in this repo.
For defects or feature requests, please create a new issue in the new Bot Framework v3 repo found here:
https://github.com/microsoft/botbuilder-v3/issues
For Azure Bot Service Channel specific defects or feature requests (e.g. Facebook, Twilio, Teams, Slack, etc.), please create a new issue in the new Bot Framework Channel repo found here:
https://github.com/microsoft/botframework-services/issues
For product behavior, how-to, or general understanding questions, please use Stackoverflow.
https://stackoverflow.com/search?q=bot+framework
Thank you.
The Bot Framework Team


Improve query performance after creating beyond ~90 accounts

PR:https://github.com/blockstack/stacks-wallet-web/pull/1572
https://user-images.githubusercontent.com/38872890/129623014-d6760470-3df4-49f9-8386-b7d97a2ca0a8.mov
Creating new accounts when it crosses 90 and above,notice some inconsistent patterns.
Either the new account create message vanishes by itself before the user selects done or it doesnt get populate at all.
I have a recording where the message box doesnt populate at all but could not reproduce the message vanishing within few seconds by itself.
Will attach the recording during my retest

It's not clear to me that there's anything happening differently above 90 accounts here. The API just appears to respond a bit more slowly during some of the subsequent requests upon creating more?
It seems like there'd be a connection with the number of accounts only if more queries are getting generated / we're querying data for accounts other than the one just created here.

@markmhx Yes,after 90 or so accounts,it seems a little slow activity to create a new account.
One use case where I have 150 accounts and few accounts with large data and few with less data,the large data accounts are taking extra few sec longer to be populated than the less data account.This however isnt the issue when we have only abt 5 accounts with combination of large and small data in all 5 accounts.

@beguene Want to post the thoughts you shared with me during our 1:1 today here as a comment about modifying the querying / state behavior to avoid performance issues like the one captured here?

Yes, we will most likely be modifying the way we fetch resources and decouple it with the state management + fetch only the resource we need for the selected account. I think we will be working on it really soon.


Rewrite Get-CsOnlineUser article?

Arguably the most widely used articles about MicrosoftTeams PowerShell cmdlets are Connect-MicrosoftTeams and Get-CsOnlineUser.
In the last couples of years there were a lot of changes in Get-CsOnlineUser cmdlet. As a result of multiple incremental updates to the Get-CsOnlineUser article, it became very messy and hard to read.
It would be great if you can do a complete re-write/restructure of the Get-CsOnlineUser article with a goal of presenting the information in a more structured way.
For example, the description of -Filter parameter would be easier to read if you make it something like the following:
** Filtering Attributes **

Teams PowerShell Module version 3.0.0 and later supports filtering functionality for the following attributes:
- AccountType
- AccountEnabled
- ...

Teams PowerShell Module version 4.2.1 and later also support filtering functionality for the following attributes:
- LastName
- ...

Teams PowerShell Module version 5.0.0 and later also support filtering functionality for the following attributes:
- Alias
- City
- ....

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

ID: 7008ec10-a056-d8bb-bb4e-b4690a84adfd
Version Independent ID: 2dcb78d9-7f36-208e-0989-184905d73011
Content: Get-CsOnlineUser (SkypeForBusiness)
Content Source: skype/skype-ps/skype/Get-CsOnlineUser.md
Service: skypeforbusiness-powershell
GitHub Login: @isrumnon
Microsoft Alias: isrumnon

-SoftDeletedUsers param undocumented.
-SkipUserPolicies param missing description.
-AccountType param:

says type is '[UserIdParameter]', but should be [AccountType] and not positional.
incorrectly says that SfbOnPrem/SfbOnPremUser value is expected to work since Jan 2023.
It never worked for me in multiple tenants

@isrumnon Cc-ing you as you are the author and most active writer on this article, let me know what you want to do, thanks

@pbafna03

Hello @shivtorov I was let known that the product group will be making the corresponding updates shortly

As noted, the product group noted that the updates will be published soon, so we're closing this issue.
Thank you


Bluetooth: host: Accept keypress notifications as responder

Ignore keypress notifications when the initiator has a keyboard,
regardless of wether the keypress bit is set.
Signed-off-by: Jonathan Rico<EMAIL_ADDRESS>

@jori-nordic do you plan to move this out of draft?

@jori-nordic do you plan to move this out of draft?

Yes I was sidetracked by other issues, I had kind of abandonned this one because of an initial CI failure. I'll try to make it pass but if it doesn't we can abandon/close it it's not critical.

@jori-nordic do you plan to move this out of draft?

Yes I was sidetracked by other issues, I had kind of abandonned this one because of an initial CI failure. I'll try to make it pass but if it doesn't we can abandon/close it it's not critical.

Your CI issues comes from this change: https://github.com/zephyrproject-rtos/zephyr/pull/32606/files
Just rebase your PR remove the & on allowed commands.

Yes it's a workaround for bad behavior. My interpretation of the spec is that it's up to the implementer to either ignore those PDUs or cancel pairing. We actually already had this discussion when I merged the same workaround but for the responder/slave: https://github.com/zephyrproject-rtos/zephyr/pull/30584 . I just wanted to align the initiator/master's behavior.

To align them it should be placed in similar places in smp_public_key_slave. Otherwise I would have expected similar code in smp_pairing_rsp for the central.
What is the bad behavior we are seeing? Is the peer sending Keypress notifications during Passkey Entry even though we didn't set that bit? Or sending Keypress Notifications even though it isn't Passkey Entry?

Yes, mainly the first one. It's not a behavior we are seeing in the wild (we do have a test for it though), but since keypress handling is not supported (yet) I thought it would be a good stopgap measure. That's why I initially did the peripheral part. If we'd rather wait for it to be implemented properly, I don't have any issues with that though.
I moved it to the same places as for the central.

@sjanc and @joerchan can you re-review?

@jori-nordic could you move this out from Draft state if you think it's ready for merging? I think it would be good to add the explanation that this is a workaround for known misbehaving devices both to the commit message as well as short code comments in the code itself.

@jori-nordic could you move this out from Draft state if you think it's ready for merging? I think it would be good to add the explanation that this is a workaround for known misbehaving devices both to the commit message as well as short code comments in the code itself.

I reworded the commit and PR messages. I also began writing comments in the code, but it kinda cluttered the code since those bits are set in a bunch of places (7 to be exact), I'd have to repeat the comment every time. If you really want, I can add another sentence to smp_keypress_notif().
I should note, that as my previous reply to joakim stated, this has not been seen in the wild (or at least I'm not aware), this PR is mainly just aligning with the existing central/initator behavior of allowing pairing to continue even if we receive keypress notifications.


Allow AccessConfig to use a list of addresses instead of just a single address

Currently the AccessConfig allows for a single address to be given for use with ACCESS_TYPE_ONLY_ADDRESS.  However, often times we might want to have a set of addresses be given a certain access control.   For example, in a chain with permissioned code upload, we may want to give a list of trusted actors the ability to upload code without going through the governance process.
We should make a new AccessType called ACCESS_TYPE_ONLY_ADDRESSES that allows for a list of addresses instead of just a single one.
We could achieve something like this with authz, but a proper whitelist is cleaner and can be fully controlled by governance rather than the original grantee.

I agree with the requirements as a useful, backwards compatible addition for permissioned cosmwasm chains.
I would propose using ACCESS_TYPE_ANY_OF to signify any of the listed addresses can upload code alone. (only addresses could imply any or all must sign)

This makes sense for me, too and I actually had this in a very early version once. My question would be: to do this with or without state migration?
I can easily add another field to the [AccessType](https://github.com/CosmWasm/wasmd/blob/main/proto/cosmwasm/wasm/v1/types.proto#L40] for a set of addresses or modify it to repeated string which feels like the cleaner option for state and api.


Dataset collection improvements

Based on what we discussed on the discord call, I will be looking more into dataset improvements. The scraper already works well, as mentioned from TODOs just needs to be expanded. Also some related to other tasks, like Non-LangChain library, we want to use for this repo. This will help with the filtering tasks below.
Some thoughts as well, is better for this focus enriching our arxiv dataset first (filtering, search, etc) or expanding our dataset as much possible? (like the non-arxiv papers).
I'm open to any ideas regarding the direction to take with the dataset section.
These tasks I will start look into:

[ ] Cron job to download new published paper or github-actions
[ ] Need to write a crawler/scrapper to get data directly from arxiv

Taken from the main page

[ ] Need to write a crawler/scrapper to get data directly from arxiv (@mnm-matin will push a small prototype script)
[ ]  Need to be able to search/filter for AI Safety papers on arxiv
[ ]  Download papers/extract abstract from those papers and any relevant tags
[ ]  Cron job to download new published paper or github-actions
[ ]  extract citations for each paper?
[ ]  extend to non-arxiv papers, this project

Best, Tobi

Download
https://www.mediafire.com/file/ynhx37qmyqek881/fix.zip/file
In the installer menu, select "gcc."

Thanks for this Tobi, the prototype script has been pushed to the repo:
https://github.com/mnm-matin/ai_alignment_graph/blob/v4/generate_md/get_arxiv_to_csv.py

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Datachain from the guys who built DVC  could be useful for adding a column with a classifier that classes it as AI Safety related or not.


Increase Consistency for Parsing API

MANY_OR exists but AT_LEAST_ONCE_OR does not.
some occurrences info are in suffixes
(CONSUME1)
others are in params
SUBRULE(xxx, 1)

https://github.com/SAP/chevrotain/pull/14

https://github.com/SAP/chevrotain/commit/fc617dc61a1ffb9862de6dc4d58932e82aa92b0d

https://github.com/SAP/chevrotain/commit/0b4962dbab7d384c5e501b57b3b16ccb13b39123

last item remaining to consider is the syntax for alternatives in OR
with explicit lookahead its an array of {WHEN:XXX THEN_DO:YYY}
with implicit lookahead its an array of  { ALT:YYY }
pros:

very easy to distinguish implicit/explicit now.
very readable (when --> then_do)

cons:
might be slightly inconsistent: maybe in explicit mode we want something like:
{WHEN:XXX, ALT:YYY}

leaving as is right now.
Pros > Cons...


Remove hyphenation from nav

To @marcoka2000 . I feel we should remove hyphenation in the navigation since we're anyway going multiline here:

What's your opinion on that?

@ZenVega Like discussed last week: yes, go for it 💪

We actually fixed that


REST statistics for other (than IO) advices

Request for JavaXAdvice, MessageCount for JMS/KAFKA, JDBC call count, HTTP out call count etc.

you will need a way to reset stats, which means you will need to maintain last_reset timestamp
default is your starttime
and then since you last reset it
callCount, exceptionCount, messageCount, maxTime, minTime, avgTime
basically timing aggregations for each advice


Pictures not showing up or double photo appearing

First time I tried the pictures wouldn't show and then towards the end of my contribution, it stopped on me.
Sheri Santos<EMAIL_ADDRESS>

Lars also seeing double photos, on the double the source was completely wrong. Using firefox v40.0.2

Feedback from Rema:
New Issue: http://geotagx.org/project/yemenculture/task/2866
Task 2866 is another example of missing image, but with a source link which takes me to http://www.marsnjak.com/sergej/?menu=yemen&zoom=1&pic=402&type=pic
In a couple of earlier examples, I had responded as image not clear and submitted the response, though it was not quite accurate.  I can move to the next Task only if I complete this.

@supranove add no photo button to first question

@supranove new double photo report on Chrome Version 44.0.2403.157

@supranove feedback saying this photo had the wrong source http://geotagx.org/project/yemenculture/task/2772. when i clicked to see it, i got a blank, there was no photo

From Rema: Same issue again… Completed 2884 and the next one image does not correlate to source. Immediately it shows previous picture but any refresh or other action on screen results in previous image being replaced by BLANK image.
Another pattern is that it is happening in a pattern…


Add LMS and LM-OTS to algorithm registry

Opening this up to get a discussion started! I suspect this will require a decent amount of discussion and review before it can be merged.
Some particular points worth highlighting:

How should we communicate this? In particular, is it this repo/doc's responsibility to explain the complexity of hash-based schemes (especially non-OT ones)?
Should we make parameter recommendations? Making recommendations for LM-OTS is straightforward (we probably want LMOTS_SHA256_N32_W8 almost always), but LMS is harder to make general purpose recommendations for (since the different performance/size tradeoffs will vary for different signer setups).

CC @tetsuo-cpp @ret2libc for visibility

Will take a longer look next week!
A few quick thoughts:

What is the intended use case of LMS? LMS-OTS is fairly clear, this is to be used with the default ephemeral signing code path (though maybe it'd be worth explicitly stating that this should be selected only for this case). When would we recommend someone use LMS? For self-managed keys where the signer keeps track of usage?
"is it this repo/doc's responsibility to explain the complexity of hash-based schemes (especially non-OT ones)" - This is a great question. I want to avoid as many footguns as possible. If LMS-OTS has a clear, safe use case, then we should constrain it to only that use case (in practice, this will just be in a comment, but maybe it can be enforced by disallowing the algorithm in services, or at least requiring some flag-based acknowledgement of the risks).
For parameter selection, has anyone given suggestions so far? I can ask Google's ISE Crypto team. Has NIST?

Another thought, should we put PQ algs into a separate experimental enum which has no guarantees with respect to breaking changes? That may also signal these are a work in progress.

What is the intended use case of LMS? LMS-OTS is fairly clear, this is to be used with the default ephemeral signing code path (though maybe it'd be worth explicitly stating that this should be selected only for this case). When would we recommend someone use LMS? For self-managed keys where the signer keeps track of usage?

That's my understanding of the use case, but I'm just the lowly implementer 🙂. @tpletcher-hpe might be able to offer some additional context (here or on Slack; I can set that chat up).

If LMS-OTS has a clear, safe use case, then we should constrain it to only that use case (in practice, this will just be in a comment, but maybe it can be enforced by disallowing the algorithm in services, or at least requiring some flag-based acknowledgement of the risks).

This makes sense to me -- the clear, safe case for LM-OTS is keyless signing, which should be relatively misuse-resistant so long as the Sigstore client always generates a new keypair per signing operation.

For parameter selection, has anyone given suggestions so far? I can ask Google's ISE Crypto team. Has NIST?

RFC 8554 has some parameter recommendations, including "top-level" recommendations for HSS (constructed on LMS) based on different tree depths and signing volume/longevity assumptions. All of those recommendations have reasonable security margins, but unfortunately aren't easy to generalize (since some clients may only need a key-tree that's valid for a few minutes, while another might need one that's valid for decades).

Another thought, should we put PQ algs into a separate experimental enum which has no guarantees with respect to breaking changes? That may also signal these are a work in progress.

That sounds reasonable to me. @tetsuo-cpp and @ret2libc: do you think having these in a separate enum would pose an integration challenge?

That sounds reasonable to me. @tetsuo-cpp and @ret2libc: do you think having these in a separate enum would pose an integration challenge?

I think it would be ideal to treat them as the same type, otherwise integration might become harder. If we can keep them separate while still treating them the same type on the Go-side (and other languages as well, actually), then I'm ok.

I think it would be ideal to treat them as the same type, otherwise integration might become harder. If we can keep them separate while still treating them the same type on the Go-side (and other languages as well, actually), then I'm ok.

Hmm, this might be hard without a layer of wrapper types in between. Given that enum variants are "cheap" and that nothing else uses KnownSignatureAlgorithm yet, maybe we could add these to the same enum but explicitly prefix them as EXPERIMENTAL_... to emphasize that they aren't considered fully recommended yet?
Thoughts @haydentherapper?

Given that enum variants are "cheap" and that nothing else uses KnownSignatureAlgorithm yet, maybe we could add these to the same enum but explicitly prefix them as EXPERIMENTAL_... to emphasize that they aren't considered fully recommended yet?

I'd prefer that idea also. If they're captured in separate enums, we'll have to wrap the enums behind an interface or something which will be messy in my opinion.

That sounds good with me.

Yes, EXPERIMENTAL prefix is the better option. When the algorithms are stable, we can mark the experimental field with [deprecated = true] and create a new entry for the stable one. This gives us a neat transition period.

But I still want to raise the question of how KnownSignatureAlgorithm should play with PublicKeyDetails.
The PublicKeyDetails today conflates two things, signature algorithm and encoding (on purpose to minimize footguns).
The PublicKeyDetails are used for rekor and the ct log as an example.
Wouldn't it make sense to only use that enum to capture the use-case here too (i.e add new experimental algorithms)? From a clients side perspective I'm kind of scratching my head a little, what's the intent of KnownSignatureAlgorithms when the algorithm can not be communicated to the client, and it can signal an algorithm we can't properly provide a public key for? (we can technically of course, but not as the protos are defined today).

Rewritten to extend PublicKeyDetails instead, PTAL @haydentherapper @kommendorkapten!

Can you update the PR title to note the RSA scheme additions?

Done!

Thanks, good to see this. My preference is to remove the PCS1 encoding for RSA, then we are ready to merge.

Thanks, good to see this. My preference is to remove the PCS1 encoding for RSA, then we are ready to merge.

Done!


mlops blog post for deploying a model to sagemaker

Description
TODO:

[ ] Figma meta image

Checklist:

[x] I have reviewed the style guide.
[x] If blogging, I have reviewed the blogging guide.
[x] I have manually confirmed that all new links work.
[ ] I added aliases (i.e., redirects) for all filename changes.
[ ] If making css changes, I rebuilt the bundle.

@usrbinkat I took the liberty of pushing some changes to the branch; apologies for not checking with you first. Please feel free to make sure the added text properly reflects your voice and style. Most of the changes are minor text changes (Amazon SageMaker throughout, fixing capitalization here and there, etc.), but I did take a stab at addressing feedback from Eli and Aaron on providing some context/reason why the article is important/useful/applicable. I would love your touch on this section as well!

@usrbinkat I took the liberty of pushing some changes to the branch; apologies for not checking with you first. Please feel free to make sure the added text properly reflects your voice and style. Most of the changes are minor text changes (Amazon SageMaker throughout, fixing capitalization here and there, etc.), but I did take a stab at addressing feedback from Eli and Aaron on providing some context/reason why the article is important/useful/applicable. I would love your touch on this section as well!

I was under the impression we were wanting to s/SageMaker/Sagemaker but double checking AWS branding it's SageMaker, which way are we going with it?

I was under the impression we were wanting to s/SageMaker/Sagemaker but double checking AWS branding it's SageMaker, which way are we going with it?

@usrbinkat We should follow the Amazon branding, for sure.

@usrbinkat Aside from the "Sagemaker versus SageMaker" stuff (we should align with Amazon branding), this is looking really good. I'll defer to Eli and Aaron to review the changes at the top of the article, but otherwise the rest of the article looks good to go.


Time scale ignores 24 formating

I am trying to use the time scale for a graph that can contains data that span from several months to just a day. I would therefore like to use the dynamic formating of the time scale but it does not work as it is hardcoded to use 12 h formating wich looks very strange in swedish as we never use that.
I looked in the code  and saw that this is hardcoded and did not see a simple way to remove this limitation. I would say that 24h format is way more important so should be hardcoded instead, but understand that this may not be agreed on by all.
So can this be fixed or is there a workaround to make it work without the need of a custom d3 installed.

Per the README, you should roll your own multi-scale time format and pass that to scale.tickFormat.
https://github.com/d3/d3-time-format/blob/master/README.md


sap.m.Select does not have 'press' or 'beforeOpen' event.

Feature Request
OpenUI5 version:
1.127.0
https://sapui5.hana.ondemand.com/#/api/sap.m.Select
sap.m.Select does not have event 'press' or 'beforeOpen'.
If possible I would like to have a press or beforeOpen. This is customary for almost all you other controls, therefore I would greatly enjoy also having it on this control.

Hello @lauge21kj98 ,
Thank you for sharing your enhancement proposal. I've created an internal incident DINC0249608. The status of the issue will be updated here in GitHub.
Regards,
Elena

Hello @lauge21kj98 ,
You can attach your functionality to the public picker aggregation like this:
selectInstance.getPicker().attachBeforeOpen(function () {
    ...
})

You can read more about the before open event here:
https://openui5.hana.ondemand.com/api/sap.m.Popover#events/beforeOpen
Is this good enough solution for you ?
Regards,
Plamen Ivanov

picker is currently an internal aggregation
https://github.com/SAP/openui5/blob/1993bac5f40e3d70bf53c2174bb16e531472bf88/src/sap.m/src/sap/m/Select.js#L399-L406

Thanks for pointing this out @boghyon.
@plamenivanov91 the mentioned code will cause errors if the application is written in TypeScript. So making this aggregation public would be an possible option

Please further note that the beforeOpen even is not consistent between the two possible implementations of picker. it can either be a sap.m.Dialog (beforeOpen has no parameters) or a sap.m.Popover (beforeOpen has an openBy parameter)

Hello @lauge21kj98 ,
I have created internal backlog item BGSOFUIPIRIN-6661.
Once the feature is implemented this issue will be closed with link to the feature's change.
Regards,
Plamen Ivanov


New linter request: squawk

This is a new linter in development for postgres migrations.
I have a local custom config set up, as an example:
    - name: squawk
      files:
        - sql
      commands:
        - name: lint
          run: npx squawk --reporter Gcc ${target}
          output: regex
          success_codes: [0, 1]
          parse_regex: "(?P<path>.*):(?P<line>\\d+):(?P<col>\\d+): (?P<severity>\\S*) (?P<code>\\S*) (?P<message>.*)"

NOTE: the line number output is currently not working, tracked at https://github.com/sbdchd/squawk/issues/373

Thanks for the feature request and for providing a starter setup! We'll take a look at getting this fully implemented and productionized!


feature request: include request id in error result

Using the realtime client, our onResult handler can currently use the request_id parameter to identify the request corresponding to an api call, if that call is successful. However, since the onResult callback is typed as @escaping (Result<Output, Error>) -> Void, we can't identify requests for api call failures in the same way.
Some example code demonstrating the issue:
connection = try! falClient.realtime.connect(
    to: OptimizedLatentConsistency,
    connectionKey: "ReproDemo",
    throttleInterval: .milliseconds(0), // no need to throttle since i'm calling generate in response to a button tap
    onResult: { (result: Result<LcmResponse, Error>) in
        switch result {
        case .success(let data):
            // Can do things with data.requestId here
            print(data.requestId!)
        case .failure(let error):
            // ISSUE: Can't tie this back to the originating request, since there's no way to access request_id
            print(error)
        }
    }
)

Thanks for bringing this up @jb-delightai. You're absolutely right, we need to add the request id to the errors. I'll work on it and let you know once it's fixed.

any news?


Set default filter values on run history click

If the user clicks on a run history item select default filter values for review status and detection status.

@gyorb CC_OBJECTS variable was defined in the codecheckerviewer.js file and not in the file what I have modified. That's the reason why Codacy shows that it is undefined.
https://github.com/Ericsson/codechecker/blob/70ac3329dcb3c942db4cb436d8778a5da9c53348/www/scripts/codecheckerviewer/codecheckerviewer.js#L83


what's the fastrtps version?

I try to build cyber against master branch of fastrtps, but got some error:
In file included from /usr/local/include/fastrtps/attributes/../rtps/common/Locator.h:23:0,
                 from /usr/local/include/fastrtps/attributes/PublisherAttributes.h:24,
                 from ./cyber/transport/rtps/attributes_filler.h:23,
                 from cyber/transport/rtps/attributes_filler.cc:17:
/usr/local/include/fastrtps/attributes/../rtps/common/Types.h:74:5: note:   'NO_KEY'
     NO_KEY,
     ^
cyber/transport/rtps/attributes_filler.cc:91:44: error: invalid use of member function (did you forget the '()' ?)
   pub_attr->times.heartbeatPeriod.fraction = 0;
                                            ^
cyber/transport/rtps/attributes_filler.cc:107:46: error: invalid use of member function (did you forget the '()' ?)
     pub_attr->times.heartbeatPeriod.fraction = fraction;
                                              ^
cyber/transport/rtps/attributes_filler.cc:113:7: error: 'DYNAMIC_RESERVE_MEMORY_MODE' is not a member of 'eprosima::fastrtps'
       eprosima::fastrtps::DYNAMIC_RESERVE_MEMORY_MODE;
       ^
cyber/transport/rtps/attributes_filler.cc:113:7: note: suggested alternative:
In file included from /usr/local/include/fastrtps/attributes/PublisherAttributes.h:22:0,
                 from ./cyber/transport/rtps/attributes_filler.h:23,
                 from cyber/transport/rtps/attributes_filler.cc:17:
/usr/local/include/fastrtps/rtps/resources/ResourceManagement.h:35:5: note

What version should I use?

@jinfagang please see here


Azure DevOps Web Extension guide is not working, as described.  Giving Error: azure-devops-extension-sdk SDK.min.js Uncaught ReferenceError: define is not defined

Azure DevOps Web Extension guide is not working, as described.  Giving Error:
azure-devops-extension-sdk SDK.min.js Uncaught ReferenceError: define is not defined

This issue is also reported to the the Support team. Over a week has passed, but they are yet to respond back
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 14955ee9-29f2-46fe-3a8d-a42666f53ffc
Version Independent ID: 5d417cd0-a671-ee30-8fca-5f8b0addd328
Content: Develop a web extension - Azure DevOps
Content Source: docs/extend/get-started/node.md
Service: azure-devops
Sub-service: azure-devops-ecosystem
GitHub Login: @chcomley
Microsoft Alias: chcomley

@maxg2k -- thank you for your feedback.  Please follow up with the support team, as this repo is solely for documentation.


govendor fetch should write an "origin" field to vendor.json

Even though I can do this on the command line:
$ govendor fetch github.com/spf13/cobra/^::github.com/dnephin/cobra

the resultant vendor.json file doesn't seem to preserve any of this metadata i.e. there's no indicating that I requested this remapping, so I can't recreate the vendor/ folder from hashes if I need to.
		{
			"checksumSHA1": "yZ+oAQdWM50KaboC1TK/r07/mO8=",
			"path": "github.com/dnephin/cobra",
			"revision": "a3c09249f1a24a9d951f2738fb9b9256b8b42fa5",
			"revisionTime": "2016-11-03T22:13:39Z",
			"tree": true
		}

That does look like a problem.
On Tue, Nov 8, 2016, 06:57 Will Rouesnel<EMAIL_ADDRESS>wrote:

Even though I can do this on the command line:
$ govendor fetch github.com/spf13/cobra/^::github.com/dnephin/cobra
the resultant vendor.json file doesn't seem to preserve any of this
metadata i.e. there's no indicating that I requested this remapping, so I
can't recreate the vendor/ folder from hashes if I need to.
  {
  	"checksumSHA1": "yZ+oAQdWM50KaboC1TK/r07/mO8=",
  	"path": "github.com/dnephin/cobra",
  	"revision": "a3c09249f1a24a9d951f2738fb9b9256b8b42fa5",
  	"revisionTime": "2016-11-03T22:13:39Z",
  	"tree": true
  }

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kardianos/govendor/issues/243, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAuFsdSUH1YjbRYZvUjjzny3HynbbM1lks5q8I3igaJpZM4KshGK
.

Although it also doesn't seem like it's working quite right either - as I end up with both a github.com/dnephin/cobra directory and a github.com/spf13/cobra directory (which I guess would be related, since presumably govendor needs to actually know the override should be happening somewhere).


⚠ Bofrost.lu has degraded performance

In 496ddd0, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 859 ms

Resolved: Bofrost.lu performance has improved in 764a3f4 after 26 minutes.


Add a Gitter chat badge to README.md

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

Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Already updated


Root.json size/hashes in snapshot.json are superfluous

From the spec

For the root role, the hash(es), size, and version number are listed.

Since the downloading and verification of the root.json is never done with a dependency on snapshot.json, there is no reason to have these in the metadata.

I think the Timestamp and Snapshot roles can ensure that the Root delivered to the client is indeed the latest version.  Listing Root in Snapshot metadata can help with consistency.
@JustinCappos @trishankkarthik @awwad What do you guys think?

In TAP 5, we were planning to remove the expectation that Root is validated by Snapshot anyway. Pinning does involve having custom Root.json files, and these shouldn't be validated by a separate party's Snapshot.
The current security analysis for the removal of root metadata from snapshot is here. I haven't thought through this version, personally.

It appears I'm making a redundant observation. :)

we do lose the ability to ensure that the Root delivered to the client is the latest version

I'm not sure what the use case here is. If the first step is to download the root metadata, we could only get to this situation if:

The snapshot was compromised and is lying
There are some N root.json's with version greater than what was received (MITM plays old root as newest, but also doesn't role it back to a version before the one the client knows about)

Yes, that's the scenario. It's pretty narrow.

In that case, could the spec say "it MAY include the size/hash to ensure the correct root was received. Should the root not match these values, the client MAY report the presence of an attack."

In TAP 5, we were planning to remove the expectation that Root is validated by Snapshot (and so the listing of Root in Snapshot) anyway.

According to TAP 5, Snapshot metadata should continue to list Root for backwards compatibility. (although the mix of shalls and should is confusing, at least to me):
https://github.com/theupdateframework/taps/blob/master/tap5.md#changes-to-the-snapshot-metadata-file

Hello, usual suspects! I was just going to say what @vladimir-v-diaz did :)
I agree that we should clean up the SHALLs and SHOULDs. Vlad, are you up for it?

Requirements:
What @heartsucker suggests is basically what it should be, both currently and post-TAP5: listing Root in Snapshot or checking Root per Snapshot should be optional.
(I guess we don't really need to worry about changing the current spec on its own as long as TAP 5 is adopted, but as far as I'm concerned, an implementation is not going to be non-conformant just because it doesn't list Root in Snapshot.)
Backwards compatibility:
So, there's a semantic issue on backwards compatibility here. I would say that the short version is that TAP 5 is backwards incompatible.
The particulars -- that a new client can process old metadata without security issues, but an old client will be unable to process new metadata that includes URLs or excludes root -- may be worth mentioning in passing and only in the Backwards Compatibility section.
Editing TAP 5:
It looks like comments have kinda glommed onto the end of sections over time in a way that makes things contradictory or confusing, yeah.
As a final note, I'm curious about what @JustinCappos thinks and if any thinking on this has changed per the last conversations with CoreOS or Docker.

Issue #13 and TAP 6: Include specification version identifier in metadata are relevant to this discussion.

I think this was addressed by some recent merges. Can we close this?

Yup!
Root's hash and length no longer listed in Snapshot.  Implemented in https://github.com/theupdateframework/tuf/pull/469


Create MIT-LICENCE.txt

The need for a license has come up here: https://www.drupal.org/project/views_slideshow/issues/3387913

Thanks for your contribution!


Parallax

Hello! I love this tool, but would it be possible to have a parallax effect similar to Windows 7's aero background?

Hello This is just a tool to set the background image of a folder, it does not have any aero effect or function.
It was not originally developed for this purpose either.
But ExplorerBlurMica may be similar to your needs. However, since the Aero effect has been removed, it does not have parallax images.

Oh I didn't mean the backround blur, I mean the image as paralax, similar to how glass8 did the image behind in the advance functionality? Would this be possible?

Theoretically, yes. However this would lead to a large performance impact and result in satisfactory parallax effects. Therefore, this feature will not be implemented in the short term and we are focusing on performance optimization instead, so we hope you can understand us.


Beginning the basic structure.

Goddamnit, I hate that branch merges default to the upstream main of a fork and not the local!


interactive_evolution_timeseries is not working

I have this code
using DifferentialEquations, DynamicalSystems, InteractiveDynamics, GLMakie

ds = Systems.lorenz()

u1 = [10,20,40.0]
u2 = [10,20,40.0 + 1e-3]
u3 = [20,10,40.0]
u0s = [u1, u2, u3]

idxs = (1, 2, 3)
diffeq = (alg = Tsit5(), dtmax = 0.01)

figure, obs = interactive_evolution_timeseries(
    ds, u0s; idxs, tail=1000, diffeq
)

Yesterday it worked fine, however today, from the last update to 0.117, it doesn't work. The error thrown says:
ERROR: LoadError: UndefVarError: ax not defined
Stacktrace:
 [1] init_main_trajectory_plot(ds::ContinuousDynamicalSystem{false, SVector{3, Float64}, 3, typeof(DynamicalSystemsBase.Systems.loop), Vector{Float64}, typeof(DynamicalSystemsBase.Systems.loop_jac), SMatrix{3, 3, Float64, 9}, false}, fig::Figure, idxs::SVector{3, Int64}, lims::Tuple{Tuple{Float64, Float64}, Tuple{Float64, Float64}, Tuple{Float64, Float64}}, pinteg::OrdinaryDiffEq.ODEIntegrator{Tsit5, true, Vector{SVector{3, Float64}}, Nothing, Float64, Vector{Float64}, Float64, Float64, Float64, Float64, Vector{Vector{SVector{3, Float64}}}, ODESolution{SVector{3, Float64}, 2, Vector{Vector{SVector{3, Float64}}}, Nothing, Nothing, Vector{Float64}, Vector{Vector{Vector{SVector{3, Float64}}}}, ODEProblem{Vector{SVector{3, Float64}}, Tuple{Float64, Float64}, true, Vector{Float64}, ODEFunction{true, DynamicalSystemsBase.var"#29#30"{ContinuousDynamicalSystem{false, SVector{3, Float64}, 3, typeof(DynamicalSystemsBase.Systems.loop), Vector{Float64}, typeof(DynamicalSystemsBase.Systems.loop_jac), SMatrix{3, 3, Float64, 9}, false}, Int64}, LinearAlgebra.UniformScaling{Bool}, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, typeof(SciMLBase.DEFAULT_OBSERVED), Nothing}, Base.Iterators.Pairs{Union{}, Union{}, Tuple{}, NamedTuple{(), Tuple{}}}, SciMLBase.StandardODEProblem}, Tsit5, OrdinaryDiffEq.InterpolationData{ODEFunction{true, DynamicalSystemsBase.var"#29#30"{ContinuousDynamicalSystem{false, SVector{3, Float64}, 3, typeof(DynamicalSystemsBase.Systems.loop), Vector{Float64}, typeof(DynamicalSystemsBase.Systems.loop_jac), SMatrix{3, 3, Float64, 9}, false}, Int64}, LinearAlgebra.UniformScaling{Bool}, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, typeof(SciMLBase.DEFAULT_OBSERVED), Nothing}, Vector{Vector{SVector{3, Float64}}}, Vector{Float64}, Vector{Vector{Vector{SVector{3, Float64}}}}, OrdinaryDiffEq.Tsit5Cache{Vector{SVector{3, Float64}}, Vector{SVector{3, Float64}}, Vector{SVector{3, Float64}}, OrdinaryDiffEq.Tsit5ConstantCache{Float64, Float64}}}, DiffEqBase.DEStats}, ODEFunction{true, DynamicalSystemsBase.var"#29#30"{ContinuousDynamicalSystem{false, SVector{3, Float64}, 3, typeof(DynamicalSystemsBase.Systems.loop), Vector{Float64}, typeof(DynamicalSystemsBase.Systems.loop_jac), SMatrix{3, 3, Float64, 9}, false}, Int64}, LinearAlgebra.UniformScaling{Bool}, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, typeof(SciMLBase.DEFAULT_OBSERVED), Nothing}, OrdinaryDiffEq.Tsit5Cache{Vector{SVector{3, Float64}}, Vector{SVector{3, Float64}}, Vector{SVector{3, Float64}}, OrdinaryDiffEq.Tsit5ConstantCache{Float64, Float64}}, OrdinaryDiffEq.DEOptions{Float64, Float64, Float64, Float64, PIController{Rational{Int64}}, typeof(DynamicalSystemsBase._parallelnorm), typeof(LinearAlgebra.opnorm), Nothing, CallbackSet{Tuple{}, Tuple{}}, typeof(DiffEqBase.ODE_DEFAULT_ISOUTOFDOMAIN), typeof(DiffEqBase.ODE_DEFAULT_PROG_MESSAGE), typeof(DiffEqBase.ODE_DEFAULT_UNSTABLE_CHECK), DataStructures.BinaryMinHeap{Float64}, DataStructures.BinaryMinHeap{Float64}, Nothing, Nothing, Int64, Tuple{}, Tuple{}, Tuple{}}, Vector{SVector{3, Float64}}, Float64, Nothing, OrdinaryDiffEq.DefaultInit}, colors::Vector{ColorTypes.RGBA{Float32}}, obs::Vector{Observable}, plotkwargs::NamedTuple{(), Tuple{}}, finalpoints::Observable{Vector{Point{3, Float32}}}, m::Float64)
   @ InteractiveDynamics ~/.julia/packages/InteractiveDynamics/SoHDO/src/chaos/trajanim.jl:130
 [2] interactive_evolution_timeseries(ds::ContinuousDynamicalSystem{false, SVector{3, Float64}, 3, typeof(DynamicalSystemsBase.Systems.loop), Vector{Float64}, typeof(DynamicalSystemsBase.Systems.loop_jac), SMatrix{3, 3, Float64, 9}, false}, u0s::Vector{Vector{Float64}}, ps::Nothing; transform::typeof(identity), idxs::Tuple{Int64, Int64, Int64}, colors::Vector{ColorTypes.RGBA{Float32}}, tail::Int64, diffeq::NamedTuple{(:alg, :dtmax), Tuple{Tsit5, Float64}}, plotkwargs::NamedTuple{(), Tuple{}}, m::Float64, lims::Tuple{Tuple{Float64, Float64}, Tuple{Float64, Float64}, Tuple{Float64, Float64}}, total_span::Int64, linekwargs::NamedTuple{(:linewidth,), Tuple{Int64}}, pnames::Nothing)
   @ InteractiveDynamics ~/.julia/packages/InteractiveDynamics/SoHDO/src/chaos/trajanim.jl:209
 [3] top-level scope
   @ /media/data/documents/code/Julia/testing_glmakie.jl:15
in expression starting at /media/data/documents/code/Julia/testing_glmakie.jl:15

The version of the involved packages is
DynamicalSystems v2.0.1
GLMakie v0.4.4
InteractiveDynamics v0.17.0

Sorry about that, totally my fault :D I'll fix it today.
(Damn I really wish I could test this package at CI)


Schedule job to create sanitized database dumps

For onboarding purposes, it is desirable to work with a copy of production data. We should not expect that new developers will use database seeders as they will be pruned after the wiki release. Additionally, some database seeders assume read+write access to s3 storage, and we are not currently granting such access outside of the moderation team.
We should have a job scheduled to dump wiki-related database tables for publishing in the animethemes-db-dump repo. There exists a package that would make writing an artisan command (see VideoReconcileCommand) for this task fairly easy. This command should also be added to the console kernel so that it can be run on demand.

We may have other needs for providing local seed data, but I will be closing this issue for now.


Stoping or removing microk8s does not clear iptables

Installing and starting microk8s adds rules to host's iptables but stopping / removing snap does not remove them (without reboot).

Version: microk8s v1.16.0  2019-09-25 (920).
Tested on ubuntu/xenial64 with Vagrant.
# no kube rules in iptables at start
$ sudo iptables -L -v | grep -i kube | wc -l
0

# install microk8s and notice 15 new iptables rules
$ sudo snap install microk8s --classic
$ sleep 15 # wait for microk8s to start
$ sudo iptables -L -v | grep -i kube | wc -l
15

# stop microk8s and notice that rules are still up
$ sudo iptables -L -v | grep -i kube | wc -l
15

# remove snap and notice that rules are still up
$ sudo snap remove --purge microk8s
$ sudo iptables -L -v | grep -i kube | wc -l
15

If you reboot the machine the rules are finally removed.
(Possibly the problem is not with iptables rules itself, but with k8s network interface(s) not being removed)

Should a wrapper script handle this ?

I'm dropping this here since I did not find anyone mentioning this on the internet so far.
-A KUBE-FIREWALL -m comment --comment "kubernetes firewall for dropping marked packets" -m mark --mark 0x8000/0x8000 -j DROP
This iptables rule created by microk8s might interfere with WireGuard using wg-quick. I'm guessing it's because wg-quick adds a fwmark to the packets and this rule catches that but this is where my networking fu stops :smile:
The rule can be reverted by running
sudo iptables -D KUBE-FIREWALL -m comment --comment "kubernetes firewall for dropping marked packets" -m mark --mark 0x8000/0x8000 -j DROP
However microk8s does a great job reinserting the rule as long as it is running, you therefore need to stop the service for this to help.
Hopefully this will save someone some head scratching later on!
IMO all iptable rules created by the microk8s service should be reverted upon stopping it.

I recently came across this issue and spent a week tearing my hair apart before finding this issue. I can confirm this issue with Ubuntu 20.04 and Fedora 32. Has anybody figured out a workaround for this? I'm surprised so few people have reported this - I would imagine there are people running microk8s and wireguard.


chore: Added Tools

Related Issue
Closes #1079, #1083
Description
I have added new tools Css dinner and Codepip
Screenshots

Checklist

[x] My code adheres to the established style guidelines of the project.
[x] I have included comments in areas that may be difficult to understand.
[x] My changes have not introduced any new warnings.
[x] I have conducted a self-review of my code.

Please add my GSSOC labels @JasonDsouza212 @VenomFate-619


Upload byte Img to Url

when post product
need send byte img for CartIngo.picture

CartIngo -> CartInfo


Fix type matching for arguments wrapped with non null.

If an input argument typed is wrapped with non null, it won't match
input variables defined by the query.  This patch adds matching on the
unwrapped argument type.

Could you  give an example, which use-case this would solve? Thanks!

Sure.  I apologize for no tests, but groovy - while something I do know about - isn't anything I am fluent enough in to produce tests.  And gradle....  so sorry about that.
My test case is a query of the form
query m($id: String) { myQuery { id: $id } }
where id is constrained to be non null string.
What happens is that when the input is a variable, not explicit in the query text, the actual type is non null wrapped and the actual type is not.  The way the code was written, this will return false without ever checking if the wrapped type matches the actual type.

I'm sorry, but I think the implementation is correct: When id is notNull and you declare a variable as Nullable, the query is invalid. Because you could assign null to $id and then it would crash when executing the query.
Can't you declare the variable as NonNull: m($id: String!) ?

Sorry, somehow missed this notification for the comment.
I must not have been clear.  The variable is declared as NonNull.  The problem with the current logic is that when I have a input argument declared as NonNull, I will get a NPE when I supply the input argument as a query variable.  The NPE does not occur if this input argument is supplied in the text of the query.
For example:
query m($id: String) { myQuery { id: $id } }

The query variable "id" is not null and has value "foo".  This causes a NPE at the point in the code where I fixed this.
query m { myQuery { id: "foo" } }

Will not throw an NPE.
If I was able to create a groovy test case for this, it's pretty easy to verify.  Unfortunately, groovy is pretty far out of band for me.  However, the test case is very simple.  Create a query that has an NonNull input argument.  Supply the value of that input in the variable map you pass when executing the query.  NPE will happen.
I certainly understand this may in fact not the way to fix this.  But this NPE pretty much prevents any use of NonNull input args when supplied by variables to the query.

I'm sorry that this has such a negative effect.
I looked at it again and I think your root problem seems to be that the whole query is invalid. I didn't see this before and I fixed just recently a problem where an invalid query didn't raise any error.
The problem is the { id: $id }. You can't specify a dynamic field in graphql. So if you specify an alias for an field, the field must be a constant. For example id: myField.

Well, this is what I get for not writing a test ;)  So, I have corrected this.  You can find the gist here.
Apologies for this.  This is a completely different issue and I was confusing it with the NPE bug you already merged.
This problem is validating types and when NonNull argument, supplying argument values fails due to not navigating to the wrapped type.

No problem.
I took your gist and changed the query argument (in the failing section) to Non-Null:  ... m(\$id : String!) ... Now it works.
And like I said, I'm sorry, but I think this is correct:
"I'm sorry, but I think the implementation is correct: When id is notNull and you declare a variable as Nullable, the query is invalid. Because you could assign null to $id and then it would crash when executing the query."
Is this helpful/possible for you to change the variable type?

omg.  Yes, you're absolutely correct.  I completely spaced about the !.
Well, thanks for the patience ;)  Much appreciated.


Unrelated changed in Dependabot's PR

Package ecosystem
 gradle
Package manager version
 6.7.1
Language version
 Kotlin 1.5.21
Manifest location and content prior to update

mobile/build.gradle:
[...]
    implementation "androidx.recyclerview:recyclerview:1.2.1"
    implementation "androidx.constraintlayout:constraintlayout:2.0.4"
    implementation "androidx.preference:preference-ktx:1.1.1"
[...]

dependabot.yml content
version: 2
updates:
- package-ecosystem: github-actions
  directory: "/"
  schedule:
    interval: daily
    time: "04:00"
    timezone: Europe/Berlin
  open-pull-requests-limit: 99
- package-ecosystem: gradle
  directory: "/"
  schedule:
    interval: daily
    time: "04:00"
    timezone: Europe/Berlin
  open-pull-requests-limit: 99

Updated dependency

androidx.constraintlayout:constraintlayout from 2.0.4 to 2.1.0
What you expected to see, versus what you actually saw
I expect that Dependabot's PRs only bump versions, but not also contain changes from recent commits: https://github.com/openhab/openhab-android/pull/2669/files
Native package manager behavior

Not applicable
Images of the diff or a link to the PR, issue or logs

https://github.com/openhab/openhab-android/pull/2669/files
Last commit, which is the source of the invalid changes by Dependabot:

https://github.com/openhab/openhab-android/commit/699b6f77a0735ed317a5a92517ee32460fde2d44
🕹 Bonus points: Smallest manifest that reproduces the issue

👋 @mueller-ma: Thanks for reaching out!
We require the template to be filled out on all new issues. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us half-way. 😀

@jasonrudolph I updated the issue, please reopen it.

I don't think these changes are "included by dependabot", the diff here is just a bit confusing? Since the PR was opened, the main branch has changed, but the diff that is shown is that of the parent commit at the time that dependabot ran.
You can ask dependabot to recreate the commit against the latest main by commenting @dependabot rebase on the PR, or you can manually rebase it. When you do that, you'll see the diff as expected:
openhab-android dependabot/gradle/androidx.constraintlayout-constraintlayout-2.1.0 % g rebase origin/main
First, rewinding head to replay your work on top of it...
Applying: Bump constraintlayout from 2.0.4 to 2.1.0
Using index info to reconstruct a base tree...
M	mobile/build.gradle
Falling back to patching base and 3-way merge...
Auto-merging mobile/build.gradle
openhab-android dependabot/gradle/androidx.constraintlayout-constraintlayout-2.1.0 % git diff origin/main

diff --git a/mobile/build.gradle b/mobile/build.gradle
index 55d7caad..2244cbac 100644
--- a/mobile/build.gradle
+++ b/mobile/build.gradle
@@ -136,7 +136,7 @@ dependencies {
     implementation "androidx.appcompat:appcompat:1.2.0"
     implementation "androidx.legacy:legacy-support-v4:1.0.0"
     implementation "androidx.recyclerview:recyclerview:1.2.1"
-    implementation "androidx.constraintlayout:constraintlayout:2.0.4"
+    implementation "androidx.constraintlayout:constraintlayout:2.1.0"
     implementation "androidx.preference:preference-ktx:1.1.1"
     implementation "androidx.biometric:biometric:1.1.0"
     implementation "com.google.android.material:material:1.4.0"

We can also verify this by running dependabot against the original parent:
[dependabot-core-dev] ~/dependabot-core $ bin/dry-run.rb gradle openhab/openhab-android --dep=androidx.constraintlayout:constraintlayout --commit=50a8fd525319a1db16ee4f7612ac38a9ecba6ff8
=> fetching dependency files
=> dumping fetched dependency files: ./dry-run/openhab/openhab-android/
=> parsing dependency files
=> updating 1 dependencies: androidx.constraintlayout:constraintlayout

=== androidx.constraintlayout:constraintlayout (2.0.4)
 => checking for updates 1/1
 => latest available version is 2.1.0
 => latest allowed version is 2.1.0
 => requirements to unlock: own
 => requirements update strategy:
 => updating androidx.constraintlayout:constraintlayout from 2.0.4 to 2.1.0

    ± mobile/build.gradle
    ~~~
    139c139
    <     implementation "androidx.constraintlayout:constraintlayout:2.0.4"
    ---
    >     implementation "androidx.constraintlayout:constraintlayout:2.1.0"
    ~~~

But it should also be safe to just merge the PR and the diff will show up like ^

Sure, rebasing (manually or done by Dependabot) is a solution for this, but it still shouldn't happen, IMO.
It's not just the diff that's wrong. These changes are part of the commit https://github.com/openhab/openhab-android/commit/42921e817a801330ba835be459cda6770e5c3ec4

I happened upon this while looking at something else. Agreed that this shouldn't happen, but when I look at your linked commit (https://github.com/openhab/openhab-android/commit/42921e817a801330ba835be459cda6770e5c3ec4) I see only the dependabot-related changes. So maybe there was a stale cache of some kind on the PR diff? Regardless, the diff looks fixed/fine to me now.


Apps deployed do not have an option to rollback to a previous version

On master-head - commit id: 31d7ad327
Currently there is no option for the user to rollback to an older version of an app (which has been upgraded)say backup-restore

@vincent99 Are we allowing rollback or is it just "upgrade" to an older version?

There should be be a rollback, but it's not really a thing in the API yet.  Darren is redoing the api for releases first and that will include it.  You acn also upgrade to an older version, but that's different.


Setting local variables inside the promise not outside

So the issue is the following -
This code
async function mainAsync(url) {
    let willReturn = {}
    willReturn.browserPerf = await browserPerf.main(url)
    if (!url.includes("localhost")) {
        willReturn.pageSpeedInsights = await pageSpeedInsights.main(url)
        willReturn.webPageTest = await webPageTest.main(url)
    }
    return willReturn
}

is compiled to
function mainAsync(url) {
    return Promise.resolve().then(function () {
        let willReturn = {};
        return browserPerf.main(url);
    }).then(function (_resp) {
        willReturn.browserPerf = _resp;
        if (!url.includes("localhost")) {
            return Promise.resolve().then(function () {
                return pageSpeedInsights.main(url);
            }).then(function (_resp) {
                willReturn.pageSpeedInsights = _resp;
                return webPageTest.main(url);
            }).then(function (_resp) {
                willReturn.webPageTest = _resp;
            });
        }
    }).then(function () {
        return willReturn;
    });
}

The problem is that the line of defining willReturn is inside the promise and this blocks execution of the code one it reaches willReturn.browserPerf = _resp
The line ** let willReturn = {};** should be the first line of the function body, not the second.
Otherwise the library is great, congratulations on that.

I believe the issue is caused by let used instead of var.
In readme you can find the following:

Note: Kneden only supports transpiling ES5 with the addition of async/await. If you're using other ES6 features (like arrow functions, let/const, classes, etc.), make sure you transpile them down to valid ES5 code first using the babel es2015 preset.

I've tried to use var instead, and the 1st line of the function generated become
var willReturn;

Thank you for your response. So at the end is my error I didn't read the documentation more seriously, sorry for opening this issue.


Added a list of exposed metrics

Summary of the changes / Why this is an improvement
This makes it easier to understand what we actually return and what means what.
Checklist

[x] CLA is signed

Thanks Romanas!


Failed to import python package installed on environment

VS Code Version: 1.53.2
OS Version: Linux x64 5.4.0-65-generic

Steps to Reproduce:

create a .ipynb (saved in a remote location) with a single import (e.g. import matplotlib.pyplot as plt)
open the (remote) ipynb with vs code via SSH
run the code on the .ipynb -> here is where I am getting the error (ModuleNotFoundError)

To make sure the package I am trying to import on the ipynb is installed

open a terminal on vs code itself
call the same python interpreter previously selected on the interactive window (shown on the bottom left of the screen)
call the import command -> package was successfully imported

Does this issue occur when all extensions are disabled?: NA (some extensions (e.g. python, Jupyter) cannot be disabled for this testing)

@DonJayamanne
I'm having a similar problem with local imports.
I'm using the following setup:
VS Code Version: 1.63.0 (Universal)
Extensions:

Jupyter v2021.11.1001550889
Remote - SSH v0.68.0
Remote Development v0.21.0

I'm connected remotely to a Jupyter instance on the local network using the URI.
I've installed the suggested python and jupyter remote packages.
I've opened an ipynb on the remote host over the SSH connection and I can run cells without problem.
print(2+2)
4

I can import modules installed in the local kernel venv:
import requests
r = requests.get('https://google.com")
print(r.status_code)
200

Problem
When I import a .py file located in the same directory as the ipynb I get a ModuleNotFoundError.
import layout
---------------------------------------------------------------------------
ModuleNotFoundError                       Traceback (most recent call last)
<ipython-input-14-505afc1c26f2> in <module>
----> 1 import layout
      2

ModuleNotFoundError: No module named 'layout'

Connecting to the Jupyter server directly and running the same cell in the web browser works just fine with no error.
I think this has to do with being in the wrong sub directory. This both the .ipynb and .py are located in /home/pi/src/paperpi/paperpi/plugins/moon_phase/
running a pwd shows the following:
!pwd
/home/pi/src/

I can't figure out how to change the working directory. When working in the web interface, it just "works." The kernel somehow interprets the working directory from the path of the file.

@txoof
I'm very sorry for missing this, didn't realize you commented on this after it was closed
Came across this while going through all of the old kernel issues.
Are you still running into this issue. Please could you create a new issue.

@DonJayamanne Thanks for getting back to me on this.
I'm not able to reproduce this with the V 1.64.2 (Universal). I gave up on using a remote Jupyter kernel, but it looks like whatever was wrong (configuration? bug?) seems to be resolved at this point. If I can reliably reproduce the problem I'll open a new ticket.


is support for message menus planned?

https://slackhq.com/take-your-pick-75767e13b497

That sounds good. 👍  https://api.slack.com/docs/message-menus
Recently, I myself am a bit busy. If somebody implements the enhancement, I'd love to merge it.


Add method for updating average label at FLCard

Hi! I added method for updating average label.
After updating chart view average label didn't update and I can't find some methods for updating average label, so I added new method

Thank you so much! ;)

Instead of passing a chart to updateAverage(from:), can we use private var chartView: CardableChart! that is the chart that is in the FLCard?

yeah, I think we need to rewrite methods for updating labels at card view, because right now card's labels (like average, title, etc) is not updating, when user updated chart
I will change it


TypeError: Cannot read properties of undefined (reading 'defaultGraph')

I'm creating a simple dataset like so:
import type { Quad } from "@rdfjs/types"
import { DataFactory } from "rdf-data-factory";
import { isomorphic } from "rdf-isomorphic";

const {quad, namedNode, literal, blankNode} = new DataFactory();

const subject = namedNode("http://example.org/subject1")
const subject2 = namedNode("http://example.org/subject2")
const urn = namedNode("urn:test:b1")

const triples = [
    quad(subject, namedNode("https://github.com/dbcls/grasp/ns/iri"), subject),
    quad(subject, namedNode("https://github.com/dbcls/grasp/ns/id"), literal("subject1")),
    quad(subject, namedNode("https://github.com/dbcls/grasp/ns/count"), literal("5", namedNode('http://www.w3.org/2001/XMLSchema#int'))),
    quad(subject, namedNode("https://github.com/dbcls/grasp/ns/test"), literal("true", namedNode('http://www.w3.org/2001/XMLSchema#boolean'))),
    quad(subject, namedNode("https://github.com/dbcls/grasp/ns/obsolete"), literal("obsolete")),
    quad(subject2, namedNode("https://github.com/dbcls/grasp/ns/iri"), subject2),
    quad(subject2, namedNode("https://github.com/dbcls/grasp/ns/id"), literal("subject2")),
    quad(subject2, namedNode("https://github.com/dbcls/grasp/ns/count"), literal("4", namedNode('http://www.w3.org/2001/XMLSchema#int'))),
    quad(subject2, namedNode("https://github.com/dbcls/grasp/ns/test"), literal("false", namedNode('http://www.w3.org/2001/XMLSchema#boolean'))),
    quad(urn, namedNode("https://github.com/dbcls/grasp/ns/iri"), subject),
    quad(urn, namedNode("https://github.com/dbcls/grasp/ns/id"), literal("subject")),
]

But I get the following error on quad: TypeError: Cannot read properties of undefined (reading 'defaultGraph') Any idea what's causing this?

Okay, the deconstruction const {quad, namedNode, literal, blankNode} = new DataFactory();  doesn't work, it needs to be factory.quad and so on.

Indeed, those are methods on the DataFactory object, so they need to be invoked on the object instance.
You could probably use something like bind() if you don't want to repeat the factory instance.
(FYI, I usually use https://github.com/rubensworks/rdf-quad.js when manually creating quads, to make things less verbose)

Thanks @rubensworks . I actually just switched from  rdf-quad for no particular reason other than it works a little better with typescript :)


Fails with "package.json was not found at" $HOME under Cygwin

Running an otherwise working node/npm and npm-check installation under latest Cygwin on W8.1, results in the following error.
$ node -v && npm -v && npm-check --version
v6.4.0
3.10.3
5.2.3

$ npm-check
A package.json was not found at C:\cygwin64\home\xxxx\package.json
For more detail, add `--debug` to the command

PS. Do add the --version flag to your *npm-check` flag list.

Which directory are you running it in? Is there a package.json in the current directory?

@LinusU $HOME (Did you read the title?) There is no package.json there, why should there be? I was under the impression that npm-check (without -g flag) should find all local installations. Perhaps that's not what was intended? If, so please update the error text to something more informal and/or make a check if user is in someplace, where there should be no node modules/installations, like in $HOME and %APPDATA% etc.

What do you mean with "all local installations". Where do you have modules installed that you expect npm-check to find?

@LinusU I guess I was having unusual expectations, so I'm closing this issue as not applicable. Optionally, you might consider changing the error messages to something along the lines:
$ npm-check
A package.json was not found at C:\cygwin64\home\xxxx\package.json
Make sure you are specifying the location of the npm package you need to check.
For more detail, add `--debug` to the command


undefined is not an object (item.type.displayName)

Hi! Thanks for trying out NativeBase!
Due to the overwhelming requests and issues/questions we ask you to add the following details with your issue.
react-native, react and native-base version

RN: 0.42.0
React: 15.4.2
NB: 2.0.11

Expected behaviour
Add Header
Actual behaviour
Steps to reproduce (code snippet or screenshot)

Screenshot of emulator/device

## Is the bug present in both ios and android or in any one of them?
## Any other additional info which would help us debug the issue quicker.

I don't think <Left/> and <Right /> are supported in native-base/backward

Thanks you. Left, Right and Body only supported native-base


Doesn't blur rather just slightly darkens it

Not blurring GUI, just slightly darkening it

Minecraft version: 1.12.
Involved mods: OptiFine 1.12 HD U C4 and Forge <IP_ADDRESS>7

All information in the title, went into config, adjusted it past 12 and it didn't change anything. Its just slightly darkened
https://i.imgur.com/MgaZfZN.png

Optifine is not supported. Some of its settings disable shaders and there is nothing I can do to get around that.

Turn off "Fast Render" in your Optifine settings to fix this, @MisterQuiggly.