Question of design of self attention mask

Hi,
Really nice job on the paper. I was excited to read it.
I was wondering if you could explain a bit further on the attention masks. FYI, I am referencing your Hybrid branch which I believe was used in the rest of the paper. So if I understood the paper / your code, the attention masks are just being used to prevent information leakage between the two groups (one-to-one and one-to-many) which makes sense.
However, I don't understand why you did not want to prevent information leakage between every query within the one-to-many group. I understand that you repeat the ground truth K times so multiple queries can match to the same object. However, I would think that the self attention perfromed in the decoder for the one-to-many group would naturally prevent multiple queries from selecting the same object since the whole point of self attention here is to remove duplicates. If you were to add attention mask here, I would think that would resolve this issue.
I think I may be fundamentally misunderstanding something as clearly this worked for you. Any insight would be appreicated. I linked the code below that I have looked at.
Thanks,
Owen
https://github.com/HDETR/H-Deformable-DETR/blob/5dea6f4436969fcded8f018b4797753c5b1c0a81/models/deformable_detr.py#L208-L217
https://github.com/HDETR/H-Deformable-DETR/blob/5dea6f4436969fcded8f018b4797753c5b1c0a81/models/deformable_transformer.py#L473-L480

Thank you for the detailed response! I did not realize the top 300 queries / 300-1500 queries were coming from the two-stage. This makes more sense but I still can't quite wrap my head around this idea. Maybe I just need more time to think about it. Does the model know that the 300-1500 queries are "bad queries" therefore it knows it can disregard the NMS whereas the top 300 queries are "good queries" therefore it knows it has to use NMS?
But as follow up question, I would think you would just be interested in matching and calculating the loss for the pred_boxes and ignoring the pred_logits for the one-to-many branch. This way, you still get localization but you don't interfere with the natural NMS of the self attention.

"Does the model know that the 300-1500 queries are "bad queries" therefore it knows it can disregard the NMS whereas the top 300 queries are "good queries" therefore it knows it has to use NMS?"
We used to try to use independent self-attention for the one-to-one branch and the one-to-many branch and observe slightly better performance. The one-to-many branch requires less on NMS but it also needs NMS to suppress the additional duplicates beyond the k-groups of matched ones.
In fact, we are studying how to decompose self-attention from the DETR in our future work.

Thanks for the response. That's exciting to hear you are continuing to work on HDETR.
Will definitely be sharing if I find improved results.


Very high sidebar scrolls, but not fixed

Hello!
Please, look at http://www.revda-info.ru/
Right sidebar very high relative to the screen, there are a lot of elements. Advertisement (first block) is not fixed and goes up. What am I doing wrong? Or so it runs by default?

Hi,
This is a feature added by #8. When the sticky element higher than the screen, it will keep scrolling until bottom or top of element. Otherwise, the users can not see the bottom part of the element until end.
The other thing is that you have fixed header on the top, so you should set the option "top", in your case {top:113}. Or it will stick the top position behind the header.
I can add a option to disable the scrolling feature in next feature.

I can add a option to disable the scrolling feature in next feature.
Add please

Hi,
I added a feature to disable scrolling in 0.2.3.
You can set overflowScrolling false to do this now.


Pytorch Backends Module Cannot Be Detected

In the code below, I can successfully import the torch package, but when I use torch.backends, Pylance gives me an error that the backends module cannot be found. However, the strange thing is that my code can run correctly, and I can directly import torch.backends, where Pylance does not give me an error. I wonder how to solve this problem.
# -*- coding: utf-8 -*-
import torch
from torch.backends import cudnn

if __name__ == '__main__':
    torch.backends.cudnn.benchmark = torch.backends.cudnn.is_available()
    cudnn.benchmark = cudnn.is_available()

Environment
Windows 10 Pro 21H2
Python 3.10.4
Visual Studio Code 1.19.1 (System Setup)
Python Extension v2022.10.1
Pylance Extension v2022.7.30
Python Virtual Environment Packages
Package                 Version       |  Package                 Version
----------------------- ------------  |  ----------------------- ------------
absl-py                 1.1.0         |  tqdm                    4.64.0
asttokens               2.0.5         |  traitlets               5.1.1
autopep8                1.6.0         |  typing_extensions       4.3.0
backcall                0.2.0         |  urllib3                 1.26.10
cachetools              5.2.0         |  visdom                  <IP_ADDRESS>
certifi                 2022.6.15     |  pyasn1-modules          0.2.8
charset-normalizer      2.1.0         |  pycodestyle             2.8.0
colorama                0.4.5         |  pydocstyle              6.1.1
cycler                  0.11.0        |  pyflakes                2.4.0
debugpy                 1.5.1         |  Pygments                2.11.2
decorator               5.1.1         |  pyasn1                  0.4.8
entrypoints             0.4           |  pyasn1-modules          0.2.8
executing               0.8.3         |  pycodestyle             2.8.0
fonttools               4.34.4        |  pydocstyle              6.1.1
google-auth             2.9.1         |  pyflakes                2.4.0
google-auth-oauthlib    0.4.6         |  Pygments                2.11.2
grpcio                  1.47.0        |  pylama                  8.3.8
idna                    3.3           |  pyparsing               3.0.9
IProgress               0.4           |  python-dateutil         2.8.2
ipykernel               6.9.1         |  pytz                    2022.1
ipython                 8.3.0         |  pywin32                 302
jedi                    0.18.1        |  pyzmq                   22.3.0
jsonpatch               1.32          |  requests                2.28.1
jsonpointer             2.3           |  requests-oauthlib       1.3.1
jupyter-client          7.2.2         |  rsa                     4.8
jupyter-core            4.10.0        |  scipy                   1.8.1
kiwisolver              1.4.3         |  seaborn                 0.11.2
Markdown                3.3.7         |  setuptools              61.2.0
matplotlib              3.5.2         |  six                     1.16.0
matplotlib-inline       0.1.2         |  snowballstemmer         2.2.0
mccabe                  0.7.0         |  stack-data              0.2.0
nest-asyncio            1.5.5         |  tensorboard             2.9.1
numpy                   1.23.0        |  tensorboard-data-server 0.6.1
oauthlib                3.2.0         |  tensorboard-plugin-wit  1.8.1
packaging               21.3          |  tensorboardX            2.5.1
pandas                  1.4.3         |  toml                    0.10.2
parso                   0.8.3         |  torch                   1.12.0+cu116
pickleshare             0.7.5         |  torch-tb-profiler       0.4.0
Pillow                  9.2.0         |  torchaudio              0.12.0+cu116
pip                     21.2.4        |  torchfile               0.1.0
prompt-toolkit          3.0.20        |  torchvision             0.13.0+cu116
protobuf                3.19.4        |  tornado                 6.1
pure-eval               0.2.2         |  wcwidth                 0.2.5
pyasn1                  0.4.8         |  websocket-client        1.3.3
pyasn1-modules          0.2.8         |  Werkzeug                2.1.2
pycodestyle             2.8.0         |  wheel                   0.37.1
pyasn1                  0.4.8         |  wincertstore            0.2

Your code is relying on fragile side effects of the Python import mechanism.
You're first importing torch, which does not import the submodule backends. If you were to access torch.backends after the first import, your code would likely crash. You're then importing the submodule torch.backends.cudnn and assigning the module to the local symbol cudnn. Later, your code is relying on the side effect that the backends attribute of the torch module was populated as a side effect of the second import statement.
Pylance intentionally does not model such side effects. In general, they cannot be modeled statically. Code should not rely on such side effects, so it is intentionally flagged as an error.
If your code is going to depend on accessing torch.backends.cdnn, it should include the statement import torch.backends.cdnn. Or if you would prefer to stick with the statement from torch.backends import cdnn, then you should use the local symbol cdnn to access the cdnn submodule.

Thank you for your reply. It is very helpful to me.
You mentioned in your reply that

If you were to access torch.backends after the first import, your code would likely crash.

But It seems that there are no similar statements in the official documents of PyTorch. In the doucuments, torch.backends seems to be used directly such as GPU specific optimizations and TensorFloat-32(TF32) on Ampere devices.
Besides, I wrote the following testing code, and no crash occurred:
# -*- coding: utf-8 -*-

import torch

if __name__ == '__main__':
    print(torch.backends.cuda.is_built())
    print(torch.backends.cudnn.is_available())
    print(torch.backends.cudnn.version())
    print(torch.backends.cudnn.enabled)
    print(torch.backends.cudnn.allow_tf32)
    print(torch.backends.mps.is_available())
    print(torch.backends.mps.is_built())
    print(torch.backends.openmp.is_available())
    print(torch.backends.mkldnn.is_available())

Could you please explain more on this to me so that there will be less potential problems in my code. Thank you so much!

Pytorch is a "py.typed" library, which means that it includes a "py.typed" file within its root directory. When such a file is present, a library indicates that it has type information. It also means that the library must follow certain conventions that indicate which symbols are meant to be part of the public interface contract and which are meant to be private implementation details. For details, refer to this documentation.
In the case of Pytorch, the torch/__init__.py file indicates that the backends submodule is not re-exported from the top-level module. Therefore, you need to import it with an explicit import torch.backends statement within your code. If the backends submodule is intended to be re-exported from the top-level module, the torch/__init__.py file will need to be updated to indicate this. You could file a bug report in the Pytorch github project.

Got it! Thank you very much for your reply.

Hi @erictraut, thanks for your explanation. However, I'm still kind of confused how I should deal with this kind of "error" messages.
The very begining
import torch

torch.backends.cuda.matmul.allow_tf32 = False
      ^^^^^^^^
torch.backends.cudnn.allow_tf32 = False
      ^^^^^^^^

If I import torch.backends, then
import torch.backends

torch.backends.cuda.matmul.allow_tf32 = False
               ^^^^
torch.backends.cudnn.allow_tf32 = False
               ^^^^^

and then
import torch.backends.cuda
import torch.backends.cudnn

torch.backends.cuda.matmul.allow_tf32 = False
torch.backends.cudnn.allow_tf32 = False
                     ^^^^^^^^^^

The last of those code blocks is correct. It works for me without any type errors. If you're seeing an error here, I suspect it's because you have an older version of torch that has a bug. If you upgrade to torch 1.12.1, it should work fine.

Thank you. You are right, I'm using torch 1.11.0.


Popup licence

This pull request offers the following:

Adds a layer option, termsURL, which allows a user to specify a URL for the terms and conditions link in the attribution. This means they can link to their own copy of the terms if preferred.
Allows null to be passed as the apiUrl parameter when the user wants to omit it but supply options.
Adds a hidden div containing a copy of the OS End User Terms.
If termsURL is not specified, adds a click handler attached to the terms and conditions link which shows the hidden div. Standard map interaction is disabled while this is visible.
Default styling for the div is provided in a css file. It sets a z-index of 1200 to ensure it appears on top of all other map artefacts.

It's a heck of a lot of code to add for a simple thing. The advantage is that, by default, users of the code will conform with OS Terms and Conditions. Whether it is worth burdening the module with that responsibility is a good question!

Nice approach!
Works well and does the job but... I'm not sure it is worth burdening the library with this content, like you say, and then having to maintain the content. I feel the logo is less likely to change and I'd prefer a few extra bytes to save a network request to a URL that may change - ideally OS would provide a link or at least an anchor for the End User T&Cs and we could use that.
I'm going to put it on hold for this version if thats OK? I don't think it would be a problem to add this in version 1.0.1 for example, I will think about it some more and get version 1.0 out first.
I see the End User T&Cs are way down the content the other end of the link we have but I think for now that satisfies the point 4.6.1 in the developer agreement.

Agreed. I have raised the issue on the forum, https://www.ordnancesurvey.co.uk/forums/discussion/1010372/link-to-end-user-terms but am deeply pessimistic that any action will be taken.


Text in backticks does not appear in search results

Observation:

Text in backticks that is a heading show ups in search results
Text in backticks that is regular text or in tables does not

createdAt:

The first result is a heading: /reference/api/keys.md#key-object
createdAt from /reference/api/indexes.md#index-object does not appear

uid

Only shows uids that are headings:

/reference/api/keys.md#uid
/reference/api/tasks.md#uid
uid is used in the /reference/api/indexes.md#index-object table and almost every “Path parameters” table, but these are not part of the search results

databaseSize
Only used in the /reference/api/stats.md#stats-object table but this table is not in the results

Hey @maryamsulemani97 and @dichotommy
I'll need to test this locally before I can answer. Thanks for raising this issue, I will look into it :)

Currently the docs scraper for https://docs.meilisearch.com only includes content from p / li tags. If you change the config to also include td it works:

The config.json I used:
{
  "index_uid": "meili",
  "sitemap_urls": ["https://docs.meilisearch.com/sitemap.xml"],
  "start_urls": ["https://docs.meilisearch.com"],
  "selectors": {
    "lvl0": {
      "selector": ".sidebar-heading.open",
      "global": true,
      "default_value": "Documentation"
    },
    "lvl1": ".theme-default-content h1",
    "lvl2": ".theme-default-content h2",
    "lvl3": ".theme-default-content h3",
    "lvl4": ".theme-default-content h4",
    "lvl5": ".theme-default-content h5",
    "text": ".theme-default-content p, .theme-default-content li, .theme-default-content td"
  },
  "strip_chars": " .,;:#",
  "scrap_start_urls": true,
  "custom_settings": {
    "synonyms": {
      "relevancy": ["relevant", "relevance"],
      "relevant": ["relevancy", "relevance"],
      "relevance": ["relevancy", "relevant"]
    }
  }
}

Thanks a lot for this investigation @ColinFrick.
Can you confirm this fixes your issue @maryamsulemani97  and @dichotommy ?

Hi @ColinFrick,
Adding .theme-default-content td to the config file fixed the issue. Thank you!

Closing this, thanks again @ColinFrick for this investigation ✨


Documentation Site

One of my favorite features in Flux is the code driven documentation which I assume will remain locked to the Influxdata version. Without it, I would have probable never scraped the surface of Flux.
Since some features will inevitably differ in this Community fork, Is there any way we can leverage the same mechanism to document this Community fork using github pages or any other mean? Alternatively, would InfluxData be willing to host the Community docs on their docs site?
Has anyone from the community resolved a similar challenge previously?
Thanks!

Answering my own question.
We ended up writing a simple processor to convert the autogenerated flux json into markdown.
For anyone interested, the resulting set is deployed here: https://metrico.github.io/fluXpipe
Closing


Feature request: get partial action information

Our current endpoint for retrieving action information is:  /namespaces/{namespace}/actions/{actionName}
and according to the OpenAPI specification offers no filtering.
We have been supporting larger action bodies, first for Java, then for NodeJS. In the current situation, a user with a 10M NodeJS action cannot retrieve the annotations attached to the action without downloading the entire action, which is problematic.
There are at least three viable solutions:

Do not reflect binary/large exec bodies in the returned payload unless requested explicitly (e.g. add a fullExec flag defaulting to false). This breaks backwards compatibility very slightly, but I think it's still safe to assume no one is relying on the current behavior (for binary exec.code values).
Add a flag to mark that exec is not required in the response (e.g. meta, defaults to false). Fully backwards-compatible.
Embrace annotations as entities on their own, add an endpoint:  /namespaces/{namespace}/actions/{actionName}/annotations which only supports GET as a first step.

There are of course many variations of the above. Thoughts?

i can see wanting to fetch exec.code only if !exec.binary. some sort of execUnlessBinary. editors would behave in this fashion.

once exec is an attachment then i envision fetching it explicitly.

This is now possible - the "code" is excluded from the action response unless explicitly requested.


Add go rountine version, runnable.

Signed-off-by: linzhinan(zen Lin<EMAIL_ADDRESS>

conflict, closed it and new a PR again


how to downgrade?

i side-loaded the latest version (8) and went for a ride today.
curiously enough my temperature sensor and my vertical ascent sensor stopped working at exactly the same time.
as i want to rule out a problem with ki2, i attempted to downgrade back to 7.1.  i tried the following 2 commands:
$ ./adb install -r -d ki2-7.1-release.apk
$ ./adb install -r ki2-7.1-release.apk

but in both situations i received:
Performing Streamed Install
adb: failed to install ki2-7.1-release.apk: Failure [INSTALL_FAILED_VERSION_DOWNGRADE]

any ideas as to how to uninstall or successfully downgrade the software?
i would like to rule out ki2 as the cause of my sensor problem.
thanks in advance.

Hi, Android does not allow downgrades, you will need to uninstall Ki2 first and then install an older version.
What seems to be the problem with your other sensor?

my karoo is no longer seeing the temperature or any vertical information.  just very curious it started after i loaded ki2 version 8.


Check file extension in URL

https://github.com/yujong-lee/letsdmmf/blob/41458a2a08c0e9caaa9f8c31ebf6fdf9997a4c48/src/validate.rs#L87-L92
See also #7

Now I think checking file extension in URL is not needed.


Add command health check

This change will allow users to specify a COMMAND health check, as outline in the marathon docs. Here is the example they give
{
  "protocol": "COMMAND",
  "command": { "value": "curl -f -X GET http://$HOST:$PORT0/health" },
  "gracePeriodSeconds": 300,
  "intervalSeconds": 60,
  "timeoutSeconds": 20,
  "maxConsecutiveFailures": 3
}

Good addition! Thanks @ConnorAtherton


CI Improvements

The current CI configuration doesn't run the tests for all of the different platforms; it doesn't run tests for tvOS, it only builds the example application.
Running the tvOS tests locally from Xcode actually results in failures.
So I'd like to suggest to make the CI setup complete by fixing the tests for all platforms, and to run them all on CI.
Additionally, as suggested earlier in a comment, I'd see benefit in using a different CI provider than Travis, because Travis is slow (a lint run with cached dependencies on Travis takes over 5 minutes, on GitHub Actions, without cache takes little over 3).
I did mention GitHub Actions, but I've just found out they only provide Xcode 11, which might be an issue, since the current suite runs with Xcode 10. CircleCI however does have Xcode 10.
With a move from Travis to CircleCI the project wouldn't be the first; the React Native project migrated to CircleCI a long time ago already.
WDYT?

Running the tvOS tests locally from Xcode actually results in failures.

good catch! I think the tvOS example def needs some love.
Interested to learn more on the CircleCI stuff, is it faster than the Travis? I should at the very least, we should start looking into fixing the broken tvOS tests and use CI to run them for PRs, thanks for the suggestion here! cc @natestedman @bdotdub @Ziewvater @iperry90 too

How important is Xcode 10 support for us going forward? Xcode version support != iOS version support. Seems to me like we could probably get away with Github Actions if we wanted to.
The fact that other teams at FB have been using CircleCI probably means there's better internal support for it though, I'm going to look into that

For reference; I already experimented a bit with GitHub actions on my fork (where you can see it failing because of an invalid destination, which is not present with Xcode 11); https://github.com/koenpunt/IGListKit/pull/1
But now that I mention it, it might actually be possible to pull in additional simulators if necessary.

But now that I mention it, it might actually be possible to pull in additional simulators if necessary.

It is possible to create additional simulator configurations, but we're still limited in SDK versions.
I've now also played around with a configuration for CircleCI, but there the problems is that I can't really test, since macOS runners are not enabled by default.

Hi @koenpunt , thanks again for flagging this issue! I think I can def feel the pain points for the queue time gets long whenever publishing new PRs.
What's your evaluation on the approaches here? github Action vs. CircleCI? iiuc, u mentioned that CircleCI is not free and would require to pay in order to support macOS? whereas github Action is free, but doesn't have Xcode 10 support, am I right?
Thanks!


Improve documentation of Debug.watch

Specifically, it is tempting to call Debug.watch directly on a signal, which is not useful though. That can lead to puzzlement, since it then seems as if Debug.watch serves no purpose. See this question on the mailing list. The expanded documentation should make clear now that one needs to map Debug.watch into the signal if one wants to observe the value carried on the signal.

I wonder whether it would make sense to even make it illegal to call Debug.watch on something of Signal-type. Could be made a runtime error. Should be unproblematic since Debug.watch shouldn't be used in production anyway. And calling it on a signal is never what you want (because it has no effect). So the debugger would save you some trouble if it simply errored out (with a helpful message) if you accidentally call Debug.watch on a Signal-typed thing.

Same (concerning the proposed runtime error) for Debug.watchSummary, of course.

Comments inline; hopefully I'm not too nitpicky. I like where this is going.

I reformulated a few bits. I do think that "mapped into" is better here.

I won't fight you on it then. Should be good for whenever Evan gets back from his world tour.

Looks great to me, thank you @jvoigtlaender!


Will removing the unique index from the Mongo DB adapter improve performance?

This is something I'm interested in looking into. Possibly, this would remove the overhead of the database having to rebuild the index each time a statement is added (some research on this is still required).
self.statements.create_index('text', unique=True)

Some references https://docs.mongodb.com/manual/tutorial/optimize-query-performance-with-indexes-and-projections/

Removed as a part of #1391


[NETBEANS-1171] Ensure tlddoc can be build if invoked outside project…

… directory
The build procedure for the tlddocs was tested from within the
web.core.syntax module. The build fails if called from another
directory, which happens when invoked from the global build.
Adding the ${basedir} ensures, that the correct directory is used
for the build.

which happens when invoked from the global build

Does it mean this?
cd incubator-netbeans
ant -Dcluster.config=full

I did not fail both before and after. (generated*.zip files are created)

Sorry, my description was not precise enough. The ZIPs are created, but they are empty. If you run this before and after this PR, you can simulate the situation without doing a full build:
cd incubator-netbeans
rm web.core.syntax/external/generated-*.zip
ant -f web.core.syntax/build.xml prepare-doc

The above sequence fails prior to the PR - the callout to tlbdoc invokes tlddoc from the current directory and that is different. If the build process is started from the module the current directory is the directory of the module, when run from the global build it is most probably the root of the repository or the nbbuild directory.
The solution: Do the same as junit does for its tasks, that is resolve the paths relative to the ${basedir}

I see now. Thanks for your explanation.
I've verified the error before this PR. Then, verified that zip files generated correctly after this PR.


Create a codesandbox to replace the playground

One of the issues with the playground is that it doesn't permit users to explore the file system part of nexus. Namely about typegen file, grpahql SDL file, and model/api type mapping.

Here's what it is going to look like:


[Lab2] Q15

Trailing green led when re-initializing chase from any state to initial state

closed with last commit


Raw identifiers cause error

Describe the Bug
Trying to use a struct with a raw identifier in wasm causes an error to be thrown.
Steps to Reproduce
use wasm_bindgen::prelude::*;
#[wasm_bindgen]
pub struct Column {
  pub r#type: u8,
}

Expected Behavior
I expect valid rust to compile to valid wasm.
Actual Behavior
rustc: custom attribute panicked
Additional Context
Docs about raw identifiers

Happy to review a PR fixing this!
Should be pretty straightforward with syn.

quote::format_ident will probably be useful here (similar to #3541).

Hi, I would like to take this issue, and I believe we can simply solve it by adding format_ident to theree and add format_ident to make js_name handle raw identifier correctly.
https://github.com/rustwasm/wasm-bindgen/blob/373b7a57be3b8632499ce2198ea832fe216ef7fd/crates/macro-support/src/parser.rs#L422

it seems that unraw method belongs to the Ident structure in syn crate, but the Ident structure we use seems from the proc_macro mostly, so I think if we gonna using unraw method, maybe we need to convert Ident from proc_macro to ident from syn crate/

It sounds to me like format_ident should do the trick then if unraw requires unnecessary conversions.
I'm happy to review a PR.

it seems that unraw method belongs to the Ident structure in syn crate, but the Ident structure we use seems from the proc_macro mostly, so I think if we gonna using unraw method, maybe we need to convert Ident from proc_macro to ident from syn crate/

We're using proc_macro2::Ident, not proc_macro::Ident, and syn::Ident is just a re-export of proc_macro2::Ident, so there's no conversion needed.

Hi @Liamolucko thanks for your reply, You are right! it's my fault that confused with proc_macro and proc_marco2, unraw would work as format_ident, thanks for your catch ~


visualize_point-cloud problem

hi, i to ran this command in blob/main/docs/inference.md:
python ./tools/misc/visualize_point-cloud.py
configs/depthformer/depthformer_swinl_22k_w7_nyu.py
checkpoints/depthformer_swinl_22k_w7_nyu.pth
--output-dir point-cloud
result:
Traceback (most recent call last):
File "./tools/misc/visualize_point-cloud.py", line 187, in
main()
File "./tools/misc/visualize_point-cloud.py", line 108, in main
cfg = build_data_cfg(cfg, args.cfg_options)
File "./tools/misc/visualize_point-cloud.py", line 63, in build_data_cfg
show_pipeline = cfg.eval_pipeline
File "/home/ray/.conda/envs/sfm_py38/lib/python3.8/site-packages/mmcv/utils/config.py", line 506, in getattr
return getattr(self._cfg_dict, name)
File "/home/ray/.conda/envs/sfm_py38/lib/python3.8/site-packages/mmcv/utils/config.py", line 48, in getattr
raise ex
AttributeError: 'ConfigDict' object has no attribute 'eval_pipeline'

I forget to include the eval_pipeline in the configs. I will complete it soon.


(gitextensions) Install Failure for v3.2

cup gitextensions
Chocolatey v0.10.15
Upgrading the following packages:
gitextensions
By upgrading you accept licenses for the packages.
You have gitextensions v3.1.1 installed. Version 3.2 is available based on your
source(s).
Progress: Downloading gitextensions 3.2... 100%
gitextensions v3.2 [Approved]
gitextensions package files upgrade completed. Performing other installation ste
ps.
Installing gitextensions...
WARNING: Generic MSI Error. This is a local environment error, not an issue with
a package or the MSI itself - it could mean a pending reboot is necessary prior
to install or something else (like the same version is already installed). Plea
se see MSI log if available. If not, try again adding '--install-arguments="'/l*
v c:\gitextensions_msi_install.log'"'. Then search the MSI Log for "Return Value
3" and look above that for the error.
ERROR: Running ["C:\Windows\System32\msiexec.exe" /i "C:\ProgramData\chocolatey
lib\gitextensions\tools\GitExtensions-<IP_ADDRESS>81.msi" /quiet /norestart ADDDEFAU
LT=ALL REMOVE=AddToPath ] was not successful. Exit code was '1603'. Exit code in
dicates the following: Generic MSI Error. This is a local environment error, not
an issue with a package or the MSI itself - it could mean a pending reboot is n
ecessary prior to install or something else (like the same version is already in
stalled). Please see MSI log if available. If not, try again adding '--install-a
rguments="'/l*v c:\gitextensions_msi_install.log'"'. Then search the MSI Log for
"Return Value 3" and look above that for the error..
The upgrade of gitextensions was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\gitextensions\tools\chocolate
yInstall.ps1'.
See log for details.
Chocolatey upgraded 0/1 packages. 1 packages failed.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
Failures

gitextensions (exited 1603) - Error while running 'C:\ProgramData\chocolatey
lib\gitextensions\tools\chocolateyInstall.ps1'.
See log for details.

Take a look at c:\gitextensions_msi_install.log to see details. I suspect this is not chocolatey specific and that you will get the same error if you run installer non silent.

Can't confirm with 3.2.1 (and also in disucss comments)
Here is from my machine:
10 [ clean ]  19-10-22 23:22:50
master~> cinst gitextensions
Chocolatey v0.10.15
Installing the following packages:
gitextensions
By installing you accept licenses for the packages.
Progress: Downloading git 2.23.0... 100%
Progress: Downloading git.install 2.23.0... 100%
Progress: Downloading gitextensions 3.2.1... 100%

git.install v2.23.0 [Approved]
git.install package files install completed. Performing other installation steps.
Using Git LFS
Installing 64-bit git.install...
git.install has been installed.
git.install installed to 'C:\Program Files\Git'
  git.install can be automatically uninstalled.
Environment Vars (like PATH) have changed. Close/reopen your shell to
 see the changes (or in powershell/cmd.exe just type `refreshenv`).
 The install of git.install was successful.
  Software installed to 'C:\Program Files\Git\'

git v2.23.0 [Approved]
git package files install completed. Performing other installation steps.
 The install of git was successful.
  Software install location not explicitly set, could be in package or
  default install location if installer.

gitextensions v3.2.1 [Approved]
gitextensions package files install completed. Performing other installation steps.
Installing gitextensions...
gitextensions has been installed.
Added C:\ProgramData\chocolatey\bin\gitex.exe shim pointed to 'c:\program files (x86)\gitextensions\gitex.cmd'.
  gitextensions may be able to be automatically uninstalled.
Environment Vars (like PATH) have changed. Close/reopen your shell to
 see the changes (or in powershell/cmd.exe just type `refreshenv`).
 The install of gitextensions was successful.
  Software installed as 'msi', install location is likely default.

Chocolatey installed 3/3 packages.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).


[Attribute] Regex validation for attributes is missing from the console. This is available in IS 6.1.0

Describe the issue:
User is unable to set a regex validation for an attribute via console.


Prevents text selection in live preview

When occura is enabled and I select text (e.g. a whole paragraph), it immediately deselects.
disabling occura fixes the problem.
obsidian 1.7.4 windows 11

Hello @huachuman I will try to check, cause I don't have win 11, I have checked it on MacOS and 1.7.4 and I was not able to reproduce this behavior:(

I will close the issue, if you will be ready to provide more data about problem, please reopen IR


installing to stage/etc causes problems

Opened by request. My direct issue is fixed, thank you for your help.
@bdrewery helped me track this one down.
Some of my ports were getting this message on build:
"/usr/ports/Mk/bsd.port.mk" line 1198: UNAME_r (12.2-RELEASE-p9) and OSVERSION (1300139) do not agree on major version number.
Some ports were OK.
The cause was an error in another port which, because of an undeclared variable, was installing to stage/etc.
@bdrewery  said: "maybe I should set make.conf and login.conf to schg"
The cause:
PF_JAIL_PATH=           ${FP_JAILS_DIR}/freshports
${INSTALL_SCRIPT} ${WRKSRC}/Jail/files/etc/make.conf ${STAGEDIR}${FP_JAIL_PATH}/etc

That PF on the first line should be FP.

This is the file in question, now properly installed:
root@13amd64-default-master-list:~ # cat /jails/freshports/etc/make.conf
# this avoids Abort trap when cc is invoked in a makefile
CC=echo

# OSVERSION
OSVERSION!= /sbin/sysctl -n kern.osreldate

To be clear, this file was accidentally installed to stage/etc/make.conf instead of stage/jails/freshports/etc/make.conf
grepping old IRC logs, 2017-01-09.log has a discussion with mat. This might be why, but I'm not sure.
Conclusion: I have no idea why.
[07:23:40]  Why does it care?
[07:23:41]  $ make makesum
[07:23:42]  make: "/usr/home/dan/WorkingCopyPortsTree/Mk/bsd.port.mk" line 1148: UNAME_r (11.0-RELEASE-p2) and OSVERSION (1002000) do not agree on major version number.
[07:29:06] <mat_> dvl, because some things it does are slightly different for different FreeBSD versions, so, it tells you that you have to tell it which version you really want
[07:56:12]  mat_: How do I tell it what version I really want?
[07:56:44] <mat_> dvl, you put UNAME_r or OSVERSION (or both) in your environment
[08:00:32]  mat_: success.  Thank you.


update preprint.bib

swapped out wikipedia homoiconicity ref with Kay thesis

can you also update the .tex file to use this new reference, and the README.md so that it matches?

Yes! oops!
On Mon, Dec 12, 2016 at 12:43 PM, Daniel S. Katz<EMAIL_ADDRESS>wrote:

can you also update the .tex file to use this new reference, and the
README.md so that it matches?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/danielskatz/software-vs-data/pull/42#issuecomment-266546994,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALtLv-hX8wPfMXv8wAXPsExVbZky5PaZks5rHbH-gaJpZM4LK9PY
.

the website says you should "Add more commits by pushing to the patch-1 branch on brandles/software-vs-data"

ok, I was able to go to your branch and make a PR, then I merged it, so I'm going to close this now


refine contextualbar

remove body transform to avoid broken modal view
contextualbar is relative to the parent by default
when need fixed contextualbar, it can be setupable using fixed prop

Hey @avriq, while reviewing your PR, I'd suggest the following code changes:
👉 Code Suggestion for #1329

https://github.com/privy-open-source/design-system/pull/1329

You can also review and apply these suggestions locally on your machine.
Learn more about GitKraken Code Suggest

Code Suggest liberates your code reviews from GitHub's restrictive, comment-only feedback style. As simple as suggesting changes in a Google-doc, provide real code suggestions from where you code, e.g. your IDE, and on anything in your project — not just on the lines of code changed in the PR.

Join your team on GitKraken to speed up PR review.


Any interest for a splay sort implementation?

I could contribute with a somehow decent splay-sort implementation. Basically it works by insert elements one by one in a splay tree + visit of the tree ordering the data.
Main advantage, as with tim-sort, is that's it's adaptive (& stable).
Main drawback is that it requires 2 pointers per element memory overhead.
Not sure whether this could make sense with the approach / scope of this library.

A splaysort certainly falls in the scope of the library, especially since I like interesting adaptive comparison sorts. An implementation would be welcome as long as all tests pass - which I can help with.
Ideally I want to make a separate library for extras and contributions (see #147), but I haven't started the work on it and I'm not working much lately, so you can ignore it and make a PR to the main repository (here) instead.

Perfect, I will have to review the implementation and adapt it, I will ping when I am closer to something ready to be merged.


bugfix: Matter Switch Device Type (0x010C) profile

Per Matter Specification, 0x010C has color control as well as temperate, switching the profile to "light-color-level" to add the Color control support.

 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.

Closing due to misreading of the device type


500 error on time-pondersource-com

curl -i -d'["test"]'<EMAIL_ADDRESS>HTTP/1.1 500 Internal Server Error
Date: Thu, 01 Sep 2022 04:50:29 GMT

heroku logs --app=time-pondersource-com
[...]
[01-Sep-2022 04:50:29 UTC] PHP Fatal error:  Uncaught TypeError: count(): Argument #1 ($value) must be of type Countable|array, string given in /app/src/platform.php:149

@michielbdejong I see what is the problem

Ah yes, I think it's because print-timesheet-json returns a string instead of an array of strings. I think I fixed it now.

@michielbdejong Yes, but I did it in the same time that you in my PR, ok.


I can't build freerdp-android under mac osx

I got the following error:
[  1%] Building C object winpr/libwinpr/CMakeFiles/winpr.dir/synch/wait.c.o
/android/FreeRDP-master/winpr/libwinpr/synch/wait.c:108:12: error: static declaration of 'pthread_mutex_timedlock' follows non-static declaration
static int pthread_mutex_timedlock(pthread_mutex_t mutex, const struct timespec timeout)
^
In file included from /android/FreeRDP-master/winpr/libwinpr/synch/synch.h:50:0,
from /android/FreeRDP-master/winpr/libwinpr/synch/wait.c:44:
/android/android-ndk/platforms/android-L/arch-arm/usr/include/pthread.h:208:5: note: previous declaration of 'pthread_mutex_timedlock' was here
int pthread_mutex_timedlock(pthread_mutex_t, const struct timespec) __nonnull((1, 2));
^
make[2]: *** [winpr/libwinpr/CMakeFiles/winpr.dir/synch/wait.c.o] Error 1
make[1]: *** [winpr/libwinpr/CMakeFiles/winpr.dir/all] Error 2
make: *** [all] Error 2

@xyz8808 without more information we won't be able to help. Have a look to https://github.com/FreeRDP/FreeRDP/wiki/BugReporting

The problem is solved.  Replace android ndk r10b to r9d ,and then it passed.


CI: Test that sort order is enforced.

This should fail right now.
https://circleci.com/gh/dask/dask-ml/1531

That last one failed because I didn't include isort in the env. https://circleci.com/gh/dask/dask-ml/1534 should fail for the right reason now :)

isort seems finicky about the environment that runs it. I'm getting different outputs based on which environment is running the command, but with the same version of isort in each environment.
I've tried to pin down all the modules that gave me troubles in setup.cfg, but others may have different troubles. I'd recommend merging this once it passes, and then just disabling this check if it gives people any trouble.

Going to merge this, but to other contributors please speak up if all these linting rules become obnoxious.
I've found that using pre-commit and this .pre-commit-config.yaml configuration helps reduce annoyances.
repos:
-   repo: https://github.com/ambv/black
    rev: stable
    hooks:
    - id: black
      language_version: python3.6

-   repo: https://github.com/pre-commit/mirrors-isort
    rev: "f35773e46d096de5c45365f1a47eeeef36fc83ed"
    hooks:
    - id: isort


Factor out types

As a good house keeping activity it seems worth factoring out the repetition of the basic value | object | array types

P.S. This builds on Pull Request #2 (Make Target rule name more explicit) as it affects many of the same code lines, and if the changes were against master it would just result in merge conflicts.

dang it. I should have merged this one instead of #2.

If it's causing trouble I'll re-create it off the latest branch

No problem. Already fixed the conflict.
On Thu, Oct 1, 2015 at 10:57 AM, Pete Cordell<EMAIL_ADDRESS>wrote:

If it's causing trouble I'll re-create it off the latest branch
—
Reply to this email directly or view it on GitHub
https://github.com/arineng/jcrvalidator/pull/5#issuecomment-144771087.

Awesome.  Thanks.


Re-added the ability to set the angle from which one-way collision is active.

As well as exposing them in the editor for CollisionPolygon2D, CollisionShape2D and TileSets.
Uses an angle instead of a directional vector as it did in 2.14, since the ability to toggle it on and off makes it easier to preserve the angle it had before it was turned off, which required a bit of housekeeping using the old vector method.
The side from which a shape is solid from is always displayed correctly in the editor now as well, displayed as an arrow pointing towards the edge that the shape is solid from, which I made a different color than it was before because it was hard to see the blue arrow on top of the blue collision shapes.
Closes #12791.
I learned C++ for this 2 days ago, so apologies if anything I did was egregiously wrong!

Heh, nice try but it's completely wrong :P
I would do this the following way:

Simply add a One Way Collision Angle to Shape
That value should be relayed to Physics2DServer as a vector for performance, some function like Physics2DServer::shape_set_one_way_collision_vector()
I would change the places where one way collision is checked, which are: body_shape_2d_sw.cpp (setup function), and space_2d_sw.cpp in the test_motion function (it also does check for KinematicBody)

TileMap,CollisionPolygon2D,etc. don't need any change at all.
If you want to give it another try, let me know if you need something!

Gonna address these a bit out of order just to get the easier ones out of the way first:
Re: 3) What file do you mean by body_shape_2d_sw.cpp? I can't find any like that, and no file that sounds similar came up when I was looking through how one way collision is handled.
As for space_2d_sw.cpp, yea, that's  exactly what I did.
The 3 changes made to space_2d_sw.cpp in the test_body_motion are the only thing responsible for actually handling the collision_angle value I added to all the necessary classes. All it is doing is rotating the valid_dir Vectors that were previously always pointing upward to point towards the angle set by taking body rotation, shape rotation and the new angle value into account.
By the way, this was buggy before. The body would only ever be solid from the top, no matter how the body or shapes were rotated.
Re: 2) I have to admit I don't really know how to properly optimize this, because I'm not actually sure where the functions defined in physics_2d_server(_sw).cpp actually get called from. As far as I can tell, they never are and I really just added the one for the angle because I figured it would make sense to do so, since there also was a function for enabling one way collision and to disable the shape there.
What should I be changing here? Could you explain to me what these functions are used for?
Re: 1) This suggestion I'm a little bit confused about. It might just be that I am massively misunderstanding how the shapes system works, but none of the actual Shape2D classes have any information about their current physics state defined in them, as far as I can tell that is all handled by the shape owner.
It's a little bit more confusing because one_way_collision_enabled was found in exactly the classes I edited too, namely TileSet, CollisionShape2d and CollisionPolygon2D. Which I think makes sense, right? Since the shape classes themselves aren't actually used exclusively for physics, but also for things like drawing polygons with a regular Polygon2D node. It makes sense to me to keep that information out of the shape classes and retain it in the Body and Collision classes, where all the other information used for physics calculations is stored.
Additionally, even if we were to make an exception for this new member for some reason and move it to the Shape classes themselves, I think it would be sort of weird if the setting to enable one-way collision was in the editor helper classes CollisionPolygon2D and CollisionShape2D, but the actual angle to set that one-way direction is moved to the shapes.

@reduz I'd like to get this in before the feature freeze but am still not very sure what to change right now, since I feel like I've mostly done exactly what you suggested to do.
Just to lay that out again, the only reason TileSet, CollisionPolygon2D etc. were edited was so that you can set the angle on each shape through the inspector, as well as tweaks to the arrow drawn in the editor window. All they do is edit the angle value that I gave Shape (as you had suggested).
They don't hold any new logic that checks for collision or anything, so even if I were to redo this I can't think of any way to make the angle variable show up in the inspector without editing those files.
The actual change in logic for this is all in space_2d_sw.cpp, where I only changed the way it calculates the normal it will detect collisions from (which I think is what you suggested as well).

If this is ok to merge could be good to have it to test for any issues during beta period.

I tried to resolve the conflicts, but that just made builds fail, oops. The changes work fine on my local copy so I'm not sure why that is..

Since this is woefully outdated and wasn't the desired route to begin with, I'll close this for now.
Hope someone who knows how to work this out properly can do that eventually!

Thanks for your contribution though, it definitely gives a base to start another implementation. It will likely only happen for 3.1 though, but that should arrive soon.


dependencies update

I'm wondering are you planning to update all dependencies excepting/including webpack? I tried to update all dependencies excepting webpack and had a lot of errors one by one.
Also, I'm wondering how can I update scripts and dependencies in the already created project? In case it is injected or not

We generally only update dependencies if there's a reason (new functionality, security issue, etc.) As you've seen for yourself updating all the project's dependencies at once breaks a lot of things and we don't want to do that unless there's a good reason.
You can update react-scripts if your project hasn't been ejected:
$ # Upgrade to the latest version of react-scripts
$ yarn upgrade react-scripts
$ # Upgrade to a specific version of react-scripts
$ yarn upgrade<EMAIL_ADDRESS>


Seperate apiBaseUrl and userContentBaseUrl into two options

Previously if 'apiBaseUrl' is defined, 'userContentBaseUrl' will have no effect.
This PR separates 'apiBaseUrl' and 'userContentBaseUrl' into two options in status-page.
Note that previously userContentBaseUrl was added directly to config which is non-intuitive.
This PR also adds 'apiBaseUrl' and 'userContentBaseUrl' to '.upptimerc.yml' so that it's very obvious to change.

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

https://github.com/upptime/upptime/issues/702 related

@AnandChowdhary


Support for null-safety

Any plans on adding support for null-safety (dart 1.12) any time soon? Looks like the two dependencies (buffer, crypto) are already migrated.

https://github.com/stablekernel/postgresql-dart/pull/153 Done.  It would probably take me 1 day to migrate a similar library now. Migration is pretty straight-foward.


Syntax errors on examples in README.md

According to https://www.algolia.com/doc/javascript#MultiQuery

Hi thanks for this. Both syntaxes should work, I assume it did not work for you?

It didn't work for me, I get  Uncaught SyntaxError: Unexpected token {

oh yeah sorry it was a syntax error. I first thought you proposed to use {params: query}, it would also have worked.
We have a dedicated project for all api docs: https://github.com/algolia/algoliasearch-client-readme-generator/blob/master/include/JavaScript/multiple_queries.snippet
either we will do the change here or if you are up to, please do it ;)
thanks a lot! Hope you like our new JavaScript client.

I didn't see this dedicated repository, I'm doing changes in this one.


can't bind any TCP service on bash.exe

Please use the following bug reporting template to help produce actionable and reproducible issues. Please try to ensure that the reproduction is minimal so that the team can go through more bugs!

Same issue here on public build 15063.138
Insider was previously working, but after updating to build 16176 the issue appeared.

Same issue,  15063.138
python / node all not working, WSL lost it's meanings ...
python -m SimpleHTTPServer  #can't access at 8000
npm start                   #can't access express project at 3000

@all Thanks for your posts. If you are having problems connecting to a TCP port, please gather\try these additional steps. There are some known limitations around Anti-Virus/Windows firewall not integrating well with WSL.

Disable all Anti-Virus.
Disable Windows firewall. From a admin powershell do netsh advfirewall set allprofiles state off.
Start the service in WSL that binds/listens on a particular port.
From a Windows cmd prompt, do netstat -a | findstr <port>. Do you see the port in the list?
If you don't see the port in in the list, then that's a difficult one.
If you see your port in the list and the service is not able to connect, then share the strace of the command that connects to the service. Ex: strace -o <trace_file> -ff <command>

Let us know the results of your experiments.

@all - I have posted some instructions at #1554 to gather traces. If you can help with the trace collection, that would be great.

This problem is in the bash.exe himself , when i try to bind some TCP ports on BashOnWindows and list process status using lsof i have this information on socket :
"server        5     root    7u     sock    0,0                        18 can't identify protocol "
so I think the problem is in one of many dll with use bash.exe.
Virtual kernel process can't bind socket so windows shell can't find it .

I have a working box and a non-working one, both on the same release. On the working box, i have the same output from lsof.

@sunilmut Thanks! Turning off Windows firewall solves the problem. And I wonder if there are other ways to let incoming connections on bash pass through the Windows Firewall, so that I don't have to turn off the entire firewall for the sake of security? I have tried to add rules to allow incoming connections on bash.exe, wslhost.exe and conhost.exe, but it doesn't work.

@wrayzheng i suggest updating to 1809. the firewall would prompt up for allowing the listern permission at the bind call.


Add missing block in AT-TLS configuration

Describe your pull request here:

Remove redundant table of contents from AT-TLS articles in v3 and v2.18 (already available in sidebar)
Add missing block from inbound AT-TLS rules

List the file(s) included in this PR:

docs/user-guide/configuring-at-tls-for-zowe-server.md
versioned_docs/version-v2.18.x/user-guide/configuring-at-tls-for-zowe-server.md

I'd also add example of the TTLSKeyringParms parameter block that is currently missing in the doc. I.E.
{
    ...
    TTLSKeyringParmsRef ZoweKeyring
}

TTLSKeyringParms ZoweKeyring
{
  Keyring ZOWERING
}

I've also noted that TTLSSignatureParms is not documented anywhere. Is it always required?

TTLSSignatureParms

I believe this can be removed, can you also confirm in your setup? We should aim at the simplest setup possible

I'd also add example of the TTLSKeyringParms parameter block that is currently missing in the doc. I.E.
{
    ...
    TTLSKeyringParmsRef ZoweKeyring
}

TTLSKeyringParms ZoweKeyring
{
  Keyring ZOWERING
}

Thanks, I'll check this one and add it

TTLSConnectionAction ClientConnectionAction
{
  HandshakeRole Client
  TTLSCipherParmsRef CipherParms
  TTLSConnectionAdvancedParmsRef ConnectionAdvancedParms
  CertificateLabel
}

Is CertificateLabel required? Also, it looks it misses the value

TTLSConnectionAdvancedParms ApimlClientX509ConnAdvParms
{
  ApplicationControlled Off
  CertificateLabel Zowe Server
  SecondaryMap Off
}

ApplicationControlled Off is missing in our internal setup. Maybe that won't be necessary.

ClientEnvironmentAdvParms example is missing too.

ClientEnvironmentAdvParms and ServerEnvironmentAdvParms are also not documented.

these are documented in the full example


update index.html

@tonalmathew   thanks for making your first contribution, I will be merging your Pull Request, also look at the issues so that you can get a chance to win a limited community Swag from me.
If you like the project and Repo please give it a star and Follow me on Github (would be appreciated)

@tonalmathew  try this year for Hacktoberfest and have a look at the updated repo and contribute.
HAPPY HACKING


fix: some windows versions don't make this directory?

This fixes the failing Windows tests, but I'm not sure if it's the right way. I don't know why those directories are missing on Windows 3.7 and 3.8.

In general, I don’t like to supress errors if I don’t understand why they happen. But is there any way to find out?

I guess the way to find out is to get a Windows 3.7 or 3.8 installation and try those commands.  I'm not a fan of suppressing errors either, but in this case, we're trying to delete a directory.  Is it really an error that the directory doesn't exist in the first place?

Another option is to check if the directory exists before trying to remove it.

I don’t think that checking that the directory exists has much advantage over suppressing the error.
The existence or non-existence of the directories is not at all relevant to the test. The reason why I added the code to delete the directories is to make it not blow up up in the cleanup part of in_venv_world_fixture, which deletes some files in the directory, but not directories. To be honest, I did not fully understand why it cleans up and why some directories are excluded from it (e.g. 1a6844ae32781f2117d46363ece697d509f6935d added another directory).


How to stream only audio?

Is there a way to use the library to just stream audio?
I dont need to show a camera feedback to the user. But the RtmpCamera1 needs a surface to be init.
This idea for streaming only audio is almost the same to stream video without feedback. Is there a way to doy or a workaround?
PD: If you dont understand me at all I could find another way to be understandable.

I did an implementation of it. Only tested in RTMP but RTSP should work.
https://github.com/pedroSG94/rtmp-rtsp-stream-client-java/commit/6141815ca9b7fcf8e392d0c1a995e7a5a4ee863b
For now you only can stream. I have plan to add record audio.

Thanksssssssssssss you rockssssssssss


Allow all conventions of SelectorFormat with NameFormat

Currently I am allowed to use camel case for CSS selectors, but not for variables and functions.
So please, add all options used by SelectorFormat to NameFormat: snake_case, camel_case, hyphenated_BEM.
Regards,
Masi
Sidenote: The explanation "Using lowercase with hyphens in CSS has become the de facto standard" is strange. The SASS features dealt with by NameFormat will never appear in the generated CSS.

I don't think hyphenated_BEM makes sense for a variable name, as it is a convention that explicitly applies to selectors.
This actually points out an issue with NameFormat which hasn't been addressed, which is that it exposes BEM as a naming convention option, but that doesn't really make sense for reasons already mentioned. I think this was just an oversight when it was first implemented.
NameFormat should expose snake_case and camel_case as options, and should not expose anything BEM-related.

Actually I have no idea what BEM is. I just copied all the available options :)

Added snake_case in 21be0e3, camel_case in a2ddd68, and removed BEM in f73135a.

@sds I just noticed this now when upgrading to the latest scss-lint, but at Brigade we were relying on the BEM option of NameFormat, specifically for some placeholder names, but also in some local variable names. It is nice for these names to match up conceptually with the selector format we are using.
I'm going to replace it with this regex I just cooked up for now ^[a-z0-9][a-z0-9-]*(?:__[a-z0-9-]*)?$, but it would actually be nice to have the same options here as we do for SelectorFormat. Thoughts?

I think part of my desire to remove it entirely was because it felt weird to apply a convention intended for selectors to variables. Placeholders I guess would still be valid.
Having said that, even if we added it back, we would still need to differentiate between hyphenated_BEM and strict_BEM.


[usermanager] Prevent removing current user. Fixes JB#49464

Drop  from context="default" in dbus policy. It shouldn't be needed after this.


EBS volumes don't store KmsKeyId

from moto import mock_ec2
import boto3

mock = mock_ec2()
mock.start()

resource = boto3.resource("ec2")

kwargs = {
    "AvailabilityZone": "ap-southeast-2a",
    "Size": 8,
    "Encrypted": True,
    "KmsKeyId": "key"
}

volume = resource.create_volume(**kwargs)

print(volume.kms_key_id)

The above prints None. I was expecting it to print key.
moto 1.3.14

Thanks for raising this @tekumara - marking this as an enhancement

This is now available as of moto >= 1.3.16.dev65


Add additional elements to the envelope structure

The Data Hub Framework would like to see es:triples and es:headers added to the es:envelope.
The current envelope in the hub looks like:
<envelope>
  <headers></headers>
  <triples></triples>
  <content></content>
</envelope>

content already maps to es:instance. The triples and headers will make our plan for world domination complete.

@paxtonhare What is headers used for?
Just to be clear, the envelop that Entity Services prescribes is just the default. You can change it however you see fit in the transformation code. Agreed, though if we could make the defaults more applicable, users would have to do less modification of the out-of-the-box transforms.

The headers are there to let users store arbitrary key/value data that
doesn't fit elsewhere.
On Thu, Sep 1, 2016 at 3:42 PM, Justin Makeig<EMAIL_ADDRESS>wrote:

@paxtonhare https://github.com/paxtonhare What is headers used for?
Just to be clear, the envelop that Entity Services prescribes is just the
default. You can change it however you see fit in the transformation code.
Agreed, though if we could make the defaults more applicable, users would
have to do less modification of the out-of-the-box transforms.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/marklogic/entity-services/issues/143#issuecomment-244189682,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAmebpEr4P0nvOANmKb802eITcrWbqE0ks5qlyq0gaJpZM4Jy-wY
.

We will add es:headers, es:triples, but not es:content.

Whichever envelope format we come up with, it’s only the default—a user could write her own. However, the out-of-the-box implementation is a key indicator of how to think about envelopes and why you need them. Thus we should try to provide the primary use cases out-of-the-box.
As a data steward, Stewart needs to track various dimensions of the data in order to capture everything he knows about a particular entity.
In general, these fall into three categories:

Canonicalized forms: Materialized entity type instances
Raw source(s): Raw inputs from upstream sources, perhaps multiple instances for entities that are merged
Materialized views: Materializations of different representations mostly for performance reasons. (The same materialization logic should effectively work to transform an instance on read too.)
Metadata: Data about the the entity as a whole, such as provenance and governance

Any of these may be represented as JSON, XML, or triples.
<es:envelope>
  <es:instance>…</es:instance>
  <es:view type="http://example.com/Patient#Billing">…</es:view>
  <es:view type="http://example.com/Patient#QualityOfCare">…</es:view>
  <es:metadata>…</es:metadata>
</es:envelope>

(Note: These names are placeholders for the sake of this discussion. This issue is to decide the names of these things.)
It also might be the case where you want to scope metadata to a particular canonical instance or source.
<es:envelope>
  <es:instance>…</es:instance>
  <es:view type="http://example.com/Patient#Billing">
    <es:metadata>…</es:metadata>
    …
  </es:view>
  <es:view type="http://example.com/Patient#QualityOfCare">…</es:view>
  <es:metadata></es:metadata>
</es:envelope>

Now that I wrote that down, isn’t <es:instance/> just a specialized case of <es:view/>? Wouldn’t Stewart want to model the QualityOfCare view just like the canonical (and then do model-to-model) transformation?
(Copying @damonfeldman too.)

The idea of multiple views is very interesting. Instead of naming sections after their likely use (source, metadata, etc.) it asserts no opinion about use and simply states that they are alternate presentations for the same data (view type=x, view type=y). The distinctions are now system distinctions - what corresponds to your entity definition (es:instance), and what does not.
I want to call out the use of different envelope sections that is perhaps the most helpful in the field though. Often the key distinction is that one section is coupled to external consumers and the other is for internal database use (indexable forms, materialized counts, structures query-able as unique elements without positional indexes, etc.)
In that case, external clients only depend on the "content" which allows the MarkLogic/database team to quickly add new fields or change things in the other ("header") section, without risking a breaking change or coordinating with other teams.

Often the key distinction is that one section is coupled to external consumers

Isn’t that the whole point of views? To maintain a static interface, even if the physics data doesn’t necessarily reflect that.

Yes. The externally-visible form is certainly a view. The internal section is more "the API to the indexes."

Copying self @bsrikan to the issue

Index: Data you want to affect the index, but not necessarily serve
Serve: Return data to clients without runtime transformation
Raw: Maintain (immutable) source for future views or autidability
Metadata: Information about the data or lifecycle

After our discussions today, I'm starting to feel more comfortable with the original envelope naming. (headers, triples, content). The reason is that it conveys a sense the the  is the main thing, but you can add more in , without assuming the particular use.
Using the data hub framework as an example, the Raw/Staging database is "about" raw data. So the content is raw data there representing records as they came in from a source. But the Final database is "about" something else (often serv-able, canonical data). To continue the example, the raw data would likely use  for metadata and linkage to the sources; harmonized would be very different and would likely use  for derived data or search hints, or materialized views (averages, counts, risk scores or similar).
Long story short, I'm leaning toward some fuzzy notion that conveys that there is one section that is primary, and another that is somehow secondary. But primary and secondary mean very different things in different contexts.
I could see a "metadata" section added - though that can always be nested as a child of the header as a  child if appropriate.

I feel strongly that the wrappers should convey the purpose of the wrapped data. headers, triples, content is all over the place, mixing format and position. Yes, you can do anything with MarkLogic. However, the point here is to be prescriptive about a way.  We identified four key use cases above for why you’d want to segregate data in an envelope:

Index: Data you want to affect the index, but not necessarily serve as part of an external API, such as denormalizing or formatting data types
Serve: Data that you want to be able to quickly return to a client without having to do a transformation, such as pre-computing aggregates or rendering the exact view a client would want
Raw: Maintain an (immutable) copy of the raw source, for example, to project future index/serve views or to provide an auditable record
Metadata: Information about the data or the envelope’s lifecycle. This is intentionally ambiguous because different uses will require dramatically different metadata. (…and that’s OK.)

Index and serve are two sides of the same coin: Materialize some stuff so we don’t have to figure it out at query time. How do we figure out which “stuff”?

With some custom code
By projecting out of an entity model (and then running the upstream data through some generated code)

Thus, I propose that we combine those two under the instance rubric.
<es:envelope>
  <es:instance type="…">
    <es:metadata>…</es:metadata>
    <erp:BillingParty>…</erp:BilllingParty>
  </es:instance>
  <es:instance type="…">
    <es:metadata>…</es:metadata>
    <qc:Patient>…</qc:Patient>
  </es:instance>
  <es:source>…</es:source>
  <es:metadata>…</es:metadata>
</es:envelope>

es:envelope (exactly 1): Outer wrapper (mostly because XML requires a root element)
es:instance (0 to many): A materialized representation of an entity, either from an Entity Services model or from custom code; it does’t matter. The representation could be a document (fragment) or (serialized) triples or a combination of both. The @type attribute allows you to link back to the code or model that defines the instance, for example to generate downstream artifacts.
es:source (0 to many): A materialized instance that has the no-op transform applied. (Yes, this could be an es:instance too, but I think it’s important to distinguish the purpose.)
es:metadata (0 to many per parent): Bag of anything. Can be a child of any of the above.

What I hadn’t fully appreciated until recently is that a conceptual entity can have multiple materializations, to either support indexing or serving. In the simplest case you have one source, one type, and one instance. (The current Entity Services implementation makes some assumptions about having one es:instance element.) However, MarkLogic can handle multiple sources and types with aplomb.
In an ideal world, you wouldn't materialize instances at all. Rather, you’d do model-to-model translations at runtime. (This is how TDE works, in fact.) However, we know that does’t scale for the general case of documents-to-documents.

I'm a little unclear about what an es:instance is. I think of it as data that conforms to a defined model, as distinct from data that is handled less formally and does not have a model defined. To avoid BMOF (big modeling up front) I think it is important to have both, so in that view many things would not be instances. Is that accurate?
I actually like , ,, . Can we use that? If something is index-only, I don't think of it as an instance, and it feels like we'd be shoehorning data into an "instance" because we have the instance hammer, so want the extra data to be an instance. Please correct me if I've misunderstood the nature of an instance.

I think you have the notion of instance right, but it's more about SMOF (small model up front).  Only define the things you know you'll need.  Successive iterations will expose more of the common model.
This iterative approach I realize may not be a good assumption.  Is it acceptable for folks to create just a sparse model and expect to migrate it forward over time?

@damonfeldman said,

I actually like <index>, <serve>,<instance>, <metadata>. Can we use that?

The effect is the same though, with index, serve, and instance: materialization of some model, wether explicit from and Entity Services definition or implicit from some code. What if you want to both index and serve a particular instance of an entity? The distinction gets fuzzy and unhelpful. (Yes, I’m contradicting what I asserted above.) Couldn’t we collapse these into an es:entity?

This iterative approach I realize may not be a good assumption. Is it acceptable for folks to create just a sparse model and expect to migrate it forward over time?

The iterative approach should be our default assumption. One of the reasons MarkLogic is better is because you can model gradually as you understand the data/requirements. There may be greenfield applications that start with a mostly formed model upfront, but I think that’s the exception not the rule.

I don't see anything actionable here right now -- it could be that Data Hub and Entity Services have complementary ways of editing the envelope now, or that a kind of entity services empty-envelope-generator function would help.
Set milestone to backlog, we can revisit as needed.


Build the docs for Pull Requests and upload them to a separate repository

Once #132 is merged we'll be hosting the docs in fatiando/docs and similar repositories. The docs are built by TravisCI for PRs anyway for testing. What would be nice is if Travis also uploaded the HTML for each PR into a repository (like pr-docs or something). The repository would have folders for each PR (by number) that would contain the built docs for that PR. This would allow easy checking of doc integrity on PRs.

Fixed by #219
Check the PR docs in http://www.fatiando.org/pull/PR_NUMBER


fix Fix rewrite wrongly when sync and async materialized view name is same

Proposed changes
This is brought by https://github.com/apache/doris/pull/33699
AbstractMaterializedViewRule#isMaterializationValid check would fail when sync and async materialized view name is same, because the Materialization valid check result is cached by name。this will cause the async materialized view check fail wrongly. This fix this by make sync materialized view name unique in every place.

run buildall

run buildall


fix: use path join to compose the middleware url

Description

Previously the middlewareUrl parameter was composed using new URL. However, this approach removes the base url subpath making the final url invalid. For example new URL('/api', 'http://localhost:3000/shop/').href will result in http://localhost:3000/api instead of desired http://localhost:3000/shop/api.
This caused middleware connection errors when trying to serve the app under a subpath.
Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

@rafalcymerys @fpdrozd Thanks for the fixes. The issue is resolved now.


Re-enabled lenient mode

This re-adds the support for the "deprecated"/old syntax for conditions:

[x] as a feature in the crate
[x] that the server enables, and checks whether some condition did use the deprecated syntax while parsing the config file, and possibly warns the user (despite being logged at ERROR level, as this is the default level):

[2022-08-29T20:05:17Z ERROR limitador_server] You are using deprecated syntax for your condition! See guide https://kudrant.io/migration/limitador/constraints

The address is:

[ ] open to suggestion, wrt to its parts as well
[ ] missing the content that explains what's expected…

Should we add a "non-lenient" parser option, so the user can validate their newer files? Or make a "only validate limit file" option, that will not start the server but only parse the limits file… so that can stay even after this lenient mode gets deprecated, I think @maleck13 proposed something like that actually…

Regarding the "ugly" static switch, It is ok as it is, but I would have added one error per condition, possibly flooding the log. IMO it is a fair toll to pay when using deprecated syntax.

So, to stderr from the crate itself directly? Or have a static Vec<String> with all the deprecated style conditions, so the logger can log them all (rather than the current generic message)?

Eventually, in the next release or after, when the deprecated syntax is dropped (or entirely changed by a new struct), this "hack" can be removed

Yes, this goes away in a minor release to come, totally!


Run go generate and go vet on all packages

Fixes: https://github.com/go-gitea/gitea/issues/30512
I think this does mean those tools would run on a potential vendor directory, but I'm not sure we really support vendoring of dependencies anymore.
release has a vendor prerequisite so likely the source tarballs contain vendor files?

On the other hand, I'm pretty sure golang tools would ignore files in the well-known vendor directory itself, at least for go vet.


Cannot embed on s3 subfolders

I can successfully create embeds on the asset source root folder,
but not on any subfolder.
There is no error showed.
I have set allowed format to JSON in general.php

Duplicate of #70
Closing this. sorry for that.


VLAN not working with eth_nxp_enet driver

When switching from v3.6 to v3.7 we realized that VLAN is not working on our SOC_MIMXRT1064 board anymore.
After analyzing the problem we found out the problem is the default setting of the new nxp_enet driver (with the eth_mcux in v3.6 it worked fine)
The new driver has the HW acceleration (ETH_NXP_ENET_HW_ACCELERATION) enabled by default.
If using CONFIG_NET_VLAN the checksums for IP, TCP/UDP are calculated in SW as the VLAN interface does not use the information from the lower interface. The HW then calculates the checksums with non-zeroed values which results in checksum with the value 0xffff instead of the correct value.
If CONFIG_ETH_NXP_ENET_HW_ACCELERATION is disabled in the config and everything calculated in SW it works fine.
To make use of the HW acceleration and VLAN at the same time, I have added the following lines, which work fine in our setup:
--- A/zephyr/subsys/net/ip/net_if.c	2024-10-01 13:31:51.000000000
+++ B/zephyr/subsys/net/ip/net_if.c	2024-10-01 11:02:28.000000000
@@ -5169,12 +5169,16 @@
 			      enum net_if_checksum_type chksum_type)
 {
 #if defined(CONFIG_NET_L2_ETHERNET)
 	struct ethernet_config config;
 	enum ethernet_config_type config_type;

+	if (IS_ENABLED(CONFIG_NET_VLAN) && net_eth_is_vlan_interface(iface)) {
+		iface = net_eth_get_vlan_main(iface);
+	}
+
 	if (net_if_l2(iface) != &NET_L2_GET_NAME(ETHERNET)) {
 		/* For VLANs, figure out the main Ethernet interface and
 		 * get the offloading capabilities from it.
 		 */
 		if (IS_ENABLED(CONFIG_NET_VLAN) && net_eth_is_vlan_interface(iface)) {
 			iface = net_eth_get_vlan_main(iface);

This should be fixed by this https://github.com/zephyrproject-rtos/zephyr/pull/78745

oops did not find the fix...
already fixed in 00bb90a42e7f583704090c5e38e1b3fd933cf409


DISPATCH_QUEUE_CONCURRENT is missing

DISPATCH_QUEUE_CONCURRENT (as a second argument to dispatch_queue_create) is missing

WinOBJC is using libdispatch DrPizza fork, which doesn't support this at this point and it is not part of our immediate roadmap.  We could consider this in the future..


Rounds block: Dashboard

As per https://github.com/OpenTechFund/opentech.fund/issues/808 with the following additional acceptance criteria:

[x] Block is title "Your rounds and labs"
[x] Only displayed for OTF staff where user is the 'Round lead' (does not display for other user types)
[x] If no Round/Labs then block does not display
[x] Styling as per https://github.com/OpenTechFund/opentech.fund/issues/809

QA criteria
Dev:

[x] checked feature meets acceptance criteria/conforms exactly to the specification.
[x] provided good unit test coverage (if this is non-trivial behaviour).
[x] checked all tests for the project pass with this feature enabled.
[x] checked code conforms to the project coding standards.
[x] had code reviewed by another developer and resolved any issues raised.
[x] tested this feature as an end user of the website/app (Can I get to it? Is it useable? Can I break it? Does it work in an end-to-end context?)
[x] checked that this feature works on the server/s I am deploying it to.

QA:

[x] tested this feature as a front end user and it meets the acceptance criteria/conforms to the specification and design.
[x] checked that the feature works on the server/s deployed to

Hi @fourthletter, @danblah, @arduina
This work is now ready for testing. This work is the “your rounds and labs” block on the dashboard (https://test-apply.opentech.fund/dashboard/), showing rounds and labs that the user is the lead for.
Please test this against the acceptance criteria noted in the initial issue description where you will also see a link to the design.
Please let us know if anything is unclear or if you have any questions. Otherwise please provide feedback of any issues you find or if everything is working as expected, please confirm and we can get this work deployed to the live site and issue closed off.
Thanks,
Maya

Not sure if we're testing this correctly.

Went to existing round (https://test-apply.opentech.fund/admin/pages/778/edit/), changed lead to Dan Blah
Go to https://test-apply.opentech.fund/dashboard/
The round doesn't show up (only see submissions I'm set to review)

Ah, I see. I don't believe you can change the lead of a round once the round is active. You can change the lead of specific submissions (this was the requirement we has in phase 1 whereby at the end of a round there may still be some submissions hanging over which get allocated to the lead of the next round), but not the round itself. I will get @todd-dembrey to confirm this though.
The best way to test this is to login as yourself (since you are an admin), click on your name in the top right "Dan Blah" which will open up your account page. Use the 'Become' feature to view the system as another user. Select Maya Gibbs or Nat Kretchun (the users who currently have rounds assigned to them) and then view the dashboard as that user. You should then see the rounds that user is leading.

@danblah just realised you won't be able to test as Nat since he is a superuser, but you can test with the Maya Gibbs account.

Just tested by creating a new round, submitting new app and all good!

Nice one, thanks @danblah . Assigning to @todd-dembrey for deployment to production.


Specify required juju version in metadata.yaml

Currently the charm includes the following in metadata.yaml:
assumes:
  - juju

However, it seems the current version of the charm requires juju 3.4.3 or greater. This can be managed by setting the assumes option per https://juju.is/docs/sdk/charmcraft-yaml#heading--assumes. Note that there's also an any-of sub-option if you want to allow 2.9 or >= 3.4.3.

Hi, @mthaddon! Thanks for the report.
It should be improved by https://github.com/canonical/postgresql-operator/pull/518.

Hi, Tom! Revisions 439 and 440 contain the required minimum Juju versions.


treewide: makeWrapper buildInputs to nativeBuildInputs

Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Even though I notice potentially many other incorrect placements of dependencies in buildInputs, I will restrict myself to moving makeWrapper only.

This is being done manually. Many of the packages that I moved makeWrapper into nativeBuildInputs use it in the installPhase. So it should not actually affect the end result.

Last time I checked, makeWrapper only behaved correctly inbuildInputs, but not nativeBuildInputs. Did this get fixed?

It did not get fixed and this PR breaks cross-compilation for all these packages :D. The offending code is at https://github.com/nixos/nixpkgs/blob/master/pkgs/top-level/all-packages.nix#L513..L514

@yorickvP can you elaborate on how exactly this breaks cross?

The makeWrapper from buildPackages makes a wrapper with the shell from the builder, not the target.

@Ericson2314 could you help here?

Yeah use targetPackages.runtimeShell

@ofborg eval

Any updates?

The makeWrapper from buildPackages makes a wrapper with the shell from the builder, not the target.

Is that fixed or not?

Yeah use shell = targetPackages.runtimeShell in the definition.

Does this still need to be done?

Yeah use shell = targetPackages.runtimeShell in the definition.

Does this still need to be done?

I have a commit in this PR that does it.

Rebased.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 112276 run on x86_64-linux 1

1 package failed to build and are new build failure:

hydra-unstable: log was empty

2 packages built:

home-assistant
nixpkgs-review

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

hydra-unstable:

gpl3 is a deprecated license, check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/development/tools/misc/hydra/common.nix:133:5:
    |
133 |     license = licenses.gpl3;
    |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/unclear-gpl.md
autoconf is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/development/tools/misc/hydra/common.nix:81:3:
   |
81 |   buildInputs =
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/build-tools-in-build-inputs.md
automake is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/development/tools/misc/hydra/common.nix:81:3:
   |
81 |   buildInputs =
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/build-tools-in-build-inputs.md
libtool is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/development/tools/misc/hydra/common.nix:81:3:
   |
81 |   buildInputs =
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/build-tools-in-build-inputs.md
makeWrapper is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/development/tools/misc/hydra/common.nix:81:3:
   |
81 |   buildInputs =
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/build-tools-in-build-inputs.md
perl is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/development/tools/misc/hydra/common.nix:81:3:
   |
81 |   buildInputs =
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/build-tools-in-build-inputs.md
subversion is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/development/tools/misc/hydra/common.nix:81:3:
   |
81 |   buildInputs =
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/build-tools-in-build-inputs.md
unzip is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/development/tools/misc/hydra/common.nix:81:3:
   |
81 |   buildInputs =
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/build-tools-in-build-inputs.md
Unused argument: fetchFromGitHub.
Near pkgs/development/tools/misc/hydra/common.nix:1:40:
  |
1 | { stdenv, nix, perlPackages, buildEnv, fetchFromGitHub
  |                                        ^

Unused argument: darcs.
Near pkgs/development/tools/misc/hydra/common.nix:3:23:
  |
3 | , top-git, mercurial, darcs, subversion, breezy, openssl, bzip2, libxslt
  |                       ^

Unused argument: guile.
Near pkgs/development/tools/misc/hydra/common.nix:4:3:
  |
4 | , guile, perl, postgresql, nukeReferences, git, boehmgc, nlohmann_json
  |   ^

We should do another PR where we move unzip to native.

see #112302

Thanks for cleaning things up :+1:
FYI this broke elasticsearch6 and elasticsearch7 with enableUnfree = true. They had a trap of overwriting nativeBuildInputs to add autoPatchelfHook, which removes makeWrapper and fails with:
installing
/nix/store/zf4mhdlksqlfnqi2psdkfpcdbm56jw1f-stdenv-darwin/setup: line 1321: wrapProgram: command not found
builder for '/nix/store/1ky7sybw853746gxcl3f64ybs2y4gjdx-elasticsearch-7.5.1.drv' failed with exit code 127

Also, it looks like commit https://github.com/NixOS/nixpkgs/pull/112276/commits/e8993319724901f132dd4ed997f5383c4a482940 broke evaluation for cross android stdenv, by causing infinite recursion.
Can be reproduced with:
nix-instantiate -A pkgsCross.aarch64-android-prebuilt.stdenv
nix-instantiate -A pkgsCross.armv7a-android-prebuilt.stdenv

This breaks cross-compiled python3.buildEnv/python3.withPackages with an eval failure:
error: --- EvalError --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- nix-build
at: (520:79) in file: /home/ben/Documents/Projects/nixpkgs/pkgs/top-level/all-packages.nix

   519|
   520|   makeWrapper = makeSetupHook { deps = [ dieHook ]; substitutions = { shell = targetPackages.runtimeShell; }; }
      |                                                                               ^
   521|                               ../build-support/setup-hooks/make-wrapper.sh;

attribute 'runtimeShell' missing

.../nixpkgs $ env -i nix-build -A pkgsCross.aarch64-multiplatform.python3Packages.libevdev
error: attribute 'runtimeShell' missing, at .../nixpkgs/pkgs/top-level/all-packages.nix:517:79
(use '--show-trace' to show detailed location information)

Reverting e8993319724901f132dd4ed997f5383c4a482940 fixes eval.
It seems to affect anything using buildPythonPackage.
This happens at the merge commit of this PR (c34b032ccb5cb1cf282ed141d7f60420879e2b42), on the current tip of nixos-unstable (0aeba64fb26e4defa0842a942757144659c6e29f), and at the tip of staging (d39fafe40933de071535f28084b8503bfa9204b8). Note that #114902 changes nothing to this issue.


ListTrainer with chatbot

@hochochoc could you please provide more information about this issue?

Sorry,
I train my bot with ListTrainer. However, when I change something in Response B to Statement A in train list, I will receive the old response, not the new I have changed. I understand how ListTrainer works and how chatbot select response. But can you guess me how to get the new response, not the old one? May I have to make a new chatbot - select response or something like that?
Thank you very much.

Currently training process is static, if you made any changes in your train data, you have to retrain your bot or create new one.
I don't understand why you are trying to change existing statements? Is there any use case behind?
Some of the reference, that might useful to you
https://github.com/gunthercox/ChatterBot/pull/103
https://github.com/gunthercox/ChatterBot/issues/94#issuecomment-167920604

I don't know why it keep processing the old response when I try to create new bot with new ListTrainer.

Same is here, and I have a problem to delete letters with another iso code, let's say I have letter with Č,Ć,Đ.. I cant delete them from admin

@milanmaximo In your case you could write your own pre-processors to convert your text into desired format, if these chars are unicode apply convert_to_ascii.
If not write your own pre-processor, here some documentation how to write own processor


Unified NLP not working on self-compiled AOSP 7

Background info here:
https://github.com/microg/android_packages_apps_GmsCore/issues/216
I was directed here to check #55 but I couldn't find any overlay that would interfere with the Android 6 patch (which adds the required package name to the framework).

I recompiled and signed with the platformkey. The app is still installed in /data. The warnings went away but the location provider still does not work. The microg's settings don't show the tick next to "UnifiedNlp is registered in system".

did you reboot after installation?

Yes! I also tried several location provider just to be sure.

Just to verify: Self-Check has everything ticked but "registered in system" and "has known location"?

That is correct. Everything ticked beside "registered", further no last known location present  and no update within 10 seconds " warnings".

Confirmed and reported upstream https://code.google.com/p/android/issues/detail?id=226358. Until now it should be enough to put the app into /system. Updates can still be installed to /data as long as a copy in /system is present.

Thanks a lot! It's a pity seeing aosp getting more and more crippled with each release :-/

@danielegobbetti one of the reasons I'm still sticking to LP. Sadly.

@IzzySoft Android 6 worked well for me with microg.

@IzzySoft Like @danielegobbetti I've been using Android 6 with no issues. I self-compile AOSP so with the signature spoof changed needed for GmsCore and I've been running GmsCore with its built-in UnifiedNLP.

@danielegobbetti @n76 I wasn't so much speaking of microG (pretty sure it will do its job), but e.g. hat the crippled permission system in mind. I guess Xprivacy should do its job independently from that (as it doesn't care about those "declarative permissions" but rather covers "functionalities/interfaces") – but before someone confirms "with enthusiasm and authority" that's the case I'll stay hesistant :)

OK, I took the opposite approach and patched the aosp file responsible for the additional check. I can confirm that the change works (all checks are green now, and unifiednlp started working immediately) with no apparent drawback.
Do you want me to make a pull request with the patch for android N?

@danielegobbetti Thanks for your work.
If you can setup a PR with the patch required to run UnifiedNlp (not the signature patching of GmsCore) in a patches/ subfolder.
If you don't mind, it would also be awesome if you push the patch to CM and OmniROM gerrit, but I can do this as well if you want.

@mar-v-in closing this in favor of #103. I'd prefer if you could do the push to Omnirom and other ROMs. I am available to test other approaches if there are suggestions!

Big fan of microg and the effort to make FOSS Android usable again - so first thanks for the continued work!
I'm on the 0.2.4-22-gcb356d2 gmscore build (with UnifiedNlp) and found this issue after about two weeks of not being able to get location to work.
I didn't have any plans (or time) to compile/flash my own rom, so I booted into recovery, mounted /system and copied the following to /system/priv-app:

com.google.android.gms-1
com.google.android.gsf-1
org.fitchfamily.android.wifi_backend-1
org.fitchfamily.android.gsmlocation-1
org.microg.nlp.backend.ichnaea-1
org.microg.nlp.backend.nominatim-1

Obviously I didn't know if I should just copy com.google.android.gms-1 or if the gsf framework and backends needed to be in /system/priv-app as well - so I just played it safe and copied them all.
Point being, it might be really helpful for other users like myself who align with the FOSS mentality but aren't Android-first devs/tinkers, if the wiki was updated with a note concerning which apk{s} needs to be copied to /system/priv-app until the newer builds are stable.

@nikolowry: Installing it manually in the system partition is likely to cause problems since there are many things to consider and it differs on various Android version.
To do it more easily you could try my flashable ZIP
Note: In case you try remove the files you have already copied before installing the ZIP.


store raw json incoming notification

Is your feature request related to a problem? Please describe.
To improve management of incoming data and provide later support to recover badly formatted data not mapping to columns, it would be nice to store raw json data.
Describe the solution you'd like
have a "_raw" column for each data entry in the entity column where we can store source json data. this column should be stored also in case the normal injection fails
Describe alternatives you've considered
have a separate table where raw json data are stored.

closed by #335


Added a Gitter room for general discussions and questions

Created a Gitter room for general discussions about the paper, code and the dataset.

@Naveenal now that I thought about it carefully and to avoid dividing the community, maybe the research forum should be a channel on beta.comma.ai
But lets wait to see what @geohot thinks about it


Avoid initial new line when using custom group separator

I think this screenshot will highlight what I feel like an inconsistency:

Thanks for the contribution, @ArnaudBarre!


Method to check if a path has domain name

In the Automate model relationships are typically defined without the domain name so that they can be overridden at runtime with instances from other high priority domains. This allows for customers to override our instances without updating the locked instances in the ManageIQ domain.
The UI code would like to know if a path has the domain name included.
Proposal is to add a path_includes_domain?(path) to check if the path for the instance has the domain name included in it.

@tinaafitz @bmclaughlin @gmcculloug
Please comment


custom host ?

Can we set custom hosts ?

Nope, it's not supported yet, should be pretty easy to add though.

Yep, I am reading your source at the moment, any roadmaps for the library ? I'd love to contribute.

Closest thing to a roadmap would be TODO section in the readme :) One big missing piece is chunked outgoing responses/requests (it already can parse incoming chunks). Or do you have something in mind?

Oh not much, I just want it to be a replacement of 'http'.createServer for my use case then I can host an extremely lightweight express like server on the top of it and that lets devices talk securely for me. I wish to contribute though so wanted a starting point which is why I asked for a Roadmap.