Not an issue

Hi! Just wanted to wish you all a happy new year :) I've been seeing a lot of returning users contributing fantastic features and feedback. I'll name just a few but I am forgetting others, thanks a lot @jannuary @abegert @Diegovsky @sei0o  @Douile @TotalDarkness-NRF  I'll try (can't promise!) to keep up to pace with you people :) And if there's anything I can help you with to make your work as contributors easier (more visibility? documentation? dedicated communication channel? a proper roadmap?), please do tell me!

Happy new years everybody :tada::tada::tada:
It's been fantastic contributing to this project so far and I really appreciate the review process :D
Ragarding making it easier for contributors: One thing that got me while writing my most recent PR is understanding how Events, Actions and Commands interact with each other. I think a github Wiki page documenting how events are handled and how they're propagated would be really nice :)

Sounds absolutely reasonable, I'll do that!

I started working on some doc here  -- I'm sure there are better ways to generate technical documentation for rust projects but those are the tools I enjoy using. Hopefully the figures here will help!

I took some time to read the docs and it's pretty solid! I also liked Facebook's Flux architecture talk you linked - it's great material and it helps a lot; I belive this is a good start with the docs :)


Create Snapshoot Appears a bug

when i create a data snapshoot , a column which its data type is Integer, CHANGED double (maybe float), added by one （sample: ID column 1 ==> 1.0）, sometimes it is not supposed to be this.(Details: data is still valid in dataflow , bug appears when creating data snapshoot by a wrangled dataset)

@BookXHD I'll be very appreciated if you attach the file tested, then it'll help to debug a lot.

@joohokim1 Of course ,this is a EXCEL file with 3 sheets inside, and i use the sheet named 'Orders' to find the BUG(maybe)
Test.zip

And the same file , the same sheet ,when i use it for creating a datasource, the Row ID mess up again(in other way)

@BookXHD @ksparknot In data preparation, data type auto-detection seems like have a bug.
As I tested so far, it's because of the characteristic of the excel library we use. It yields the number values as double type "text".
I'm working on it.
By the way, you can change into long type in data preparation so that the column type of the data snapshot to be integer.


Iss728 update high time resolution to time resolved Phase 1

Summary of changes (Bug fix, feature, docs update, ...)

Please check if the PR fulfills these requirements

[x] Closes #728  (Replace xxxx with the Github issue number)
[x] Tests added and passed if fixing a bug or adding a new feature
[x] All code checks passing - black --line-length 110 run over code, mypy and flake8 not showing any errors
[x] Documentation and tutorials updated/added
[x] Added an entry in the latest CHANGELOG.md file if fixing a bug or adding a new feature
[x] Added any new requirements to requirements.txt and recipes/meta.yaml

Codecov Report
Patch coverage: 5.12% and project coverage change: -0.08% :warning:

Comparison is base (47415d6) 33.13% compared to head (0ea1746) 33.06%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##            devel     #779      +/-   ##
==========================================
- Coverage   33.13%   33.06%   -0.08%
==========================================
  Files         177      177
  Lines       13936    13966      +30
==========================================
  Hits         4618     4618
- Misses       9318     9348      +30

Files Changed
Coverage Δ

openghg/retrieve/_search.py
0.00% <0.00%> (ø)

openghg/standardise/_standardise.py
0.00% <0.00%> (ø)

openghg/standardise/emissions/_openghg.py
0.00% <0.00%> (ø)

openghg/store/_emissions.py
0.00% <0.00%> (ø)

openghg/store/_footprints.py
0.00% <0.00%> (ø)

openghg/tutorial/_tutorial.py
0.00% <ø> (ø)

tests/store/test_footprints.py
99.32% <ø> (ø)

tests/retrieve/test_access.py
93.33% <100.00%> (ø)

tests/retrieve/test_search.py
100.00% <100.00%> (ø)

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

Closing - Changes covered in https://github.com/openghg/openghg/pull/968


Explicitly don't use Series.ravel()

I tried to implement Series.ravel(),
But i think it seems that it requires to compute whole dataset that has potentially raises out of memory.
So i think that we better don't support this function explicitly and let users know alternative. (to_numpy().ravel())
>>> ks.Series([1, 2, 3]).ravel()
Traceback (most recent call last):
databricks.koalas.exceptions.PandasNotImplementedError: The method `ks.Series.ravel()` is not implemented. If you want to collect your flattened underlying data as an NumPy array, use 'to_numpy().ravel()' instead.

Codecov Report

Merging #1074 into master will decrease coverage by 2.66%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1074      +/-   ##
==========================================
- Coverage    95.2%   92.54%   -2.67%
==========================================
  Files          34       34
  Lines        6868     6868
==========================================
- Hits         6539     6356     -183
- Misses        329      512     +183

Impacted Files
Coverage Δ

databricks/koalas/missing/series.py
100% <100%> (ø)
:arrow_up:

databricks/koalas/usage_logging/__init__.py
24.54% <0%> (-72.73%)
:arrow_down:

databricks/koalas/usage_logging/usage_logger.py
50% <0%> (-50%)
:arrow_down:

databricks/koalas/__init__.py
78.72% <0%> (-8.52%)
:arrow_down:

databricks/conftest.py
92% <0%> (-6%)
:arrow_down:

databricks/koalas/frame.py
93.43% <0%> (-3.31%)
:arrow_down:

databricks/koalas/utils.py
95.12% <0%> (-3.05%)
:arrow_down:

databricks/koalas/groupby.py
89.34% <0%> (-2.05%)
:arrow_down:

databricks/koalas/namespace.py
85.8% <0%> (-1.55%)
:arrow_down:

databricks/koalas/plot.py
93.33% <0%> (-0.96%)
:arrow_down:

... and 2 more

Continue to review full report at Codecov.

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


[BUG] Python random split sum to 1 error

Description
Python random split with multiple ratio options fails even when ratios sum to 1
In which platform does it happen?
Python all OSs
How do we replicate the issue?
from reco_utils.dataset.movielens import load_pandas_df
from reco_utils.dataset.python_splitters import python_random_split
df = load_pandas_df()
x, y, z = python_random_split(df, ratio=[.7, .2, .1])

yields
Traceback (most recent call last):
  File "C:\Users\scgraham\AppData\Local\Continuum\anaconda3\envs\reco_base\lib\site-packages\IPython\core\interactiveshell.py", line 3325, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-5-49ca4e7e6410>", line 1, in <module>
    x, y, z = python_random_split(df, ratio=[.7, .2, .1])
  File "C:\Users\scgraham\repos\Recommenders\reco_utils\dataset\python_splitters.py", line 38, in python_random_split
    splits = split_pandas_data_with_ratios(data, ratio, shuffle=True, seed=seed)
  File "C:\Users\scgraham\repos\Recommenders\reco_utils\dataset\split_utils.py", line 155, in split_pandas_data_with_ratios
    raise ValueError("The ratios have to sum to 1")
ValueError: The ratios have to sum to 1

this occurs because sum([.7, .2, .1]) == .999999.... and there is a check in split_utils.py:39 which fails and renormalizes, subsequently split_utils:154 has the same check which also fails which leads to this error state
Expected behavior (i.e. solution)
data is split into train, test, and validate sets with expected fraction.
Other Comments

Good catch. Will fix it.

Resolved in #874 and validated in #876


Resolve bare specifiers PRIOR to compilation.

There's an issue about specifiers NOT being transformed when the AMD transform is involved as reported in https://github.com/Polymer/tools/issues/3402 https://github.com/Polymer/tools/issues/3403
This PR is a possible alternative to https://github.com/Polymer/tools/pull/3404, inferring from that work that the ordering of babel transform plugins was at issue.  This simply moves specifier resolution to the beginning of the js-transform sequence.

cc @btopro @westbrook

were you able to confirm this fixes the transform issue? I believe I tried this first initially and the issue is that it doesn't process the plugins in the same order. It seems like CallExpression are processed after Program, so the other PR changes the transform statement to be a looping Program as opposed to single CallExpression that runs post-transformation.

@btopro OH the nature of the problem comes from the fact that our babel-plugin-dynamic-import-amd.ts is doing a path.traverse in its own Program visitor 🤦♂
I'm going to try and fix that right now too.

@btopro I'm going to go with your solution in #3404


I want to add more Linked List algorithims in C

I want to add more Linked List algorithms in C
Is your feature request related to a problem? Please describe.
These are basic Linked List algos
Describe the solution you'd like
I'll be adding the solutions
Additional context
From my GitHub thisisrick25
Languages

[ ] Python
[ ] Java
[x] C
[ ] C++

I would like to contribute in this python

@thisisrick25 assigned to you


ENH/DEP: add temporary action pending framework fix

Sorry, I'm sure y'all have discussed at length, and I'm just butting in, but what is the issue here? Can't the framework handle this case just fine right now, since both of these types are working with the same view type?

Can't the framework handle this case just fine right now, since both of these types are working with the same view type?

Following up to my own question: in theory, yes, but in practice, no: https://github.com/qiime2/qiime2/pull/547


Add OpenAPI 3.1.0 enumeration style

In OpenAPI 3.1.0 there is a new method of enumerating things that allows us to have proper names for enumerations.
Here is an example of that.
properties:
  LogLevel:
    type: integer
    oneOf:
      - title: Trace
        const: 0
        description: "A trace log level"
      - title: Debug
        const: 1
        description: "A debug log level"
      - title: Information
        const: 2
        description: "A information log level"

The main page of the project says that it supports OpenAPI 3.1 but this part still doesn't seem to be supported.
Here is a thread on the subject

Let's fix this please.  What will it take for it to be supported properly by Swagger (UI) and the like?

Or even x-ms-enum format which gives you the value that should be used, the name and description all of which can be used to generate an extended enum in Dart too

Update, I have code that does this properly. It requires that the property have  the enum array to be able to determine that it is indeed an enum.
If you'd like I can do a pull request and you can hack it up to meet your needs. This is what it produces:
// coverage:ignore-file
// GENERATED CODE - DO NOT MODIFY BY HAND
// ignore_for_file: type=lint

import 'package:json_annotation/json_annotation.dart';

@JsonEnum()
enum ArticleCategories {
  /// Politics
  @JsonValue('1')
  politics('1'),

  /// Sports
  @JsonValue('2')
  sports('2'),

  /// Entertainment
  @JsonValue('4')
  entertainment('4'),

  /// Finance
  @JsonValue('8')
  finance('8'),

  /// Technology
  @JsonValue('16')
  technology('16'),

  /// Travel
  @JsonValue('32')
  travel('32'),

  /// Health
  @JsonValue('64')
  health('64'),

  /// Religion
  @JsonValue('128')
  religion('128'),

  /// Science
  @JsonValue('256')
  science('256'),

  /// Education
  @JsonValue('512')
  education('512'),

  /// Environmental
  @JsonValue('1024')
  environmental('1024'),

  /// Lifestyle
  @JsonValue('2048')
  lifestyle('2048');

  const ArticleCategories(this.json);

  final String? json;

  String? toJson() => json;

  @override
  String toString() {
    switch(this) {
        case ArticleCategories.politics:
          return "Politics";
        case ArticleCategories.sports:
          return "Sports";
        case ArticleCategories.entertainment:
          return "Entertainment";
        case ArticleCategories.finance:
          return "Finance";
        case ArticleCategories.technology:
          return "Technology";
        case ArticleCategories.travel:
          return "Travel";
        case ArticleCategories.health:
          return "Health";
        case ArticleCategories.religion:
          return "Religion";
        case ArticleCategories.science:
          return "Science";
        case ArticleCategories.education:
          return "Education";
        case ArticleCategories.environmental:
          return "Environmental";
        case ArticleCategories.lifestyle:
          return "Lifestyle";
    }
  }

  String toDescription() {
    switch(this) {
        case ArticleCategories.politics:
          return "Politics";
        case ArticleCategories.sports:
          return "Sports";
        case ArticleCategories.entertainment:
          return "Entertainment";
        case ArticleCategories.finance:
          return "Finance";
        case ArticleCategories.technology:
          return "Technology";
        case ArticleCategories.travel:
          return "Travel";
        case ArticleCategories.health:
          return "Health";
        case ArticleCategories.religion:
          return "Religion";
        case ArticleCategories.science:
          return "Science";
        case ArticleCategories.education:
          return "Education";
        case ArticleCategories.environmental:
          return "Environmental";
        case ArticleCategories.lifestyle:
          return "Lifestyle";
    }
  }

}

Bump: This is still broken and the enums it creates are "valueXXX" instead of proper names despite the fact that these are indeed available in the schema. It also doesn't properly override toString to return the proper values per the docs on new enums.

I gave up on my pull request, but this is still a major blocker to this working correctly as it's basically impossible to use enums right now because you don't know which one is what.


Introduce 'operatorfunc' option for custom operators

This PR introduces the 'operatorfunc' option. This option contains the name of a function that can act like a custom operator, and is called by the g@ command, such as in this example from the #702 discussion:
nnoremap gx :set opfunc=Redact<cr>g@
function! Redact(type)
    execute "normal `[v`]rx"
endfunction

Using a command such as gxiw, this map will invoke the custom operator function on a given word, and replace it with x characters.
The 'opfunc' option can be the name of a function, a reference from function('…') or funcref('…') or a lambda.
This PR also allows an extension to export a script function that can be called from the VimScript executor, which is a simple wrapper function that invokes extension code. A helper function has been added to create a script function with the right signature for operator functions. All extensions have been updated to export a function, and to use the 'operatorfunc' option.

Oh, wow

Rebased onto current master, fixing conflict.

Rebased onto current master and force pushed.
Also fixes SetCommandTests and friends by being more consistent with the temporary/hidden flag. Options that are feature flags for work-in-progress or diagnostic behaviour are hidden from normal use and unit tests. They are always visible for internal mode.
@AlexPl292 @lippfi are we happy to merge this?

Hi, yes, sorry for the delays. We haven't yet reviewed this, but the plan is to first merge the changes about the regex, then make a release, and then handle your changes to avoid too many refactorings in one release.

Merged! Thank you!


Corlogix managed prom support

@Avi-Robusta Don't we need to somehow pass the cluster on the query? Isn't that a managed Prometheus that has metrics from multiple clusters?
How do they know which cluster the metrics are from?

Im going to do that in a separate PR, its not a unique to corlogix issue it is the same for all the centralized prometheus from what I can see


Avatar download image size larger than avatar size

Downloaded avatar images are 361x445 rather than matching what appears to be 350x350 for the avatars.
Example download:

Thanks, issue fixed for the demo


Two Error Handling examples failed

Windows 10 21H1
Blade v0.0.6/MSVC
The following error handling examples failed (https://bladelang.com/tutorial/error-handling).
 Looks like a bug for Windows. I'll look into it ASAP


Error with unsupported new metrics on V100 GPU's

Running 2.4.6-2.6.9 and if I enable the following metrics:
DCGM_FI_PROF_PIPE_TENSOR_IMMA_ACTIVE
DCGM_FI_PROF_PIPE_TENSOR_HMMA_ACTIVE

The DaemonSet set works and reports metrics for nodes with A100 GPU's
For nodes with V100-16GB GPUs the DaemonSet fails with the following message:
setting up csv
/etc/dcgm-exporter/dcp-metrics-bolt.csv
done
time="2022-07-20T01:54:11Z" level=info msg="Starting dcgm-exporter"
time="2022-07-20T01:54:11Z" level=info msg="DCGM successfully initialized!"
time="2022-07-20T01:54:11Z" level=info msg="Collecting DCP Metrics"
time="2022-07-20T01:54:11Z" level=info msg="No configmap data specified, falling back to metric file /etc/dcgm-exporter/dcp-metrics-bolt.csv"
time="2022-07-20T01:54:12Z" level=fatal msg="Error watching fields: Feature not supported"
running

@hassanbabaie,
The 1013 and 1014 metrics are not supported on pre-Ampere GPUs.
WBR,
Nik

Thanks @nikkon-dev however it would be better if there was some form of graceful skip, if they are not supported log it and don't report any metrics for those.
For example when using profiling metrics with an unsupported driver version the metrics are just not provided/skipped but we can still use the same DCGM DaemonSet for all nodes.

Agreed. We'll modify that behavior.

thank you!


HiddenSelect aria-hidden elements are not focusable nor contain focusable elements

🐛 Bug Report
The Deque Axe Tool is returning this serious issue when using a HiddenSelect component.
ARIA hidden element must not be focusable or contain focusable elements
🤔 Expected Behavior
No issue reported
😯 Current Behavior
This issue can be replicated on the react-aria/useSelect page (https://react-spectrum.adobe.com/react-aria/useSelect.html) with the axe DevTools installed. After scanning the entire page 7 serious issues are raised.
An example message is:
Ensures aria-hidden elements are not focusable nor contain focusable elements
[more informationLink opens in a new window](https://dequeuniversity.com/rules/axe/4.7/aria-hidden-focus?application=AxeChrome)
Element Location:
#example-0 > .example_d569a7.spectrum_2a241c.spectrum_b37d53 > div > div[aria-hidden="true"]
<div aria-hidden="true" style="border: 0px; clip: rect(0px, 0px, 0px, 0px); clip-path: inset(50%); height: 1px; margin: -1px; overflow: hidden; padding: 0px; position: absolute; width: 1px; white-space: nowrap;">
To solve this problem, you need to fix the following:
Focusable content should be disabled or be removed from the DOM
Related Node
<input type="text" tabindex="0" style="font-size: 16px;">
💁 Possible Solution
The input tabindex should be -1
<input type="text" tabindex="-1" style="font-size: 16px;">
🔦 Context
We are using the HiddenSelect component and want to be as accessible as possible.
💻 Code Sample
🌍 Your Environment

Software
Version(s)

react-aria
3.25.0

Browser
Chrome 114.0.5735.106

Operating System
MacOS 13.4

🧢 Your Company/Team
🕷 Tracking Issue (optional)

We are tracking this false positive in our wiki here. aXe doesn't know that we manually handle focus in such a way that the HiddenSelect will move focus to the actual Select element so it throws that error.

Thank you for the instant reply. So, there shouldn't be an impact on accessibility?


Modernization

I was getting some warnings about invalid escape sequences in some regular expression pattern strings from this library under Python 3.12, gave it a look, and noticed this repo could use a little sprucing up, so I thought I'd do a little bit of work to get it up to contemporary standards so people can continue to use it for years to come. No substantive changes here to this great library, just a little housekeeping.

If I had been smarter I would have looked at some of the other PRs and noticed that this was long forked over to docopt-ng, which has all this and more already.


Add info on using the OSG 23 tarballs (SOFTWARE-5701)

I think that Brian wanted to use 23-main for the version instead of 23.

I think I fixed the issues; anything else?


Failing tests

I've cloned the repository and tried running the tests, but I get the following output from pytest:
================================= short test summary info =================================
FAILED tests/test_api.py::test_weather_get - assert 404 == 200
FAILED tests/test_api.py::test_weather_list_get - assert 404 == 200
=============================== 2 failed, 3 passed in 6.02s ===============================

Since no instructions were given on how to properly run the tests, I've installed the requirements.txt dependencies using pip into a python 3.8 virtual environment and simply ran pytest, without parameters.

For me, this PR solves the breaking tests, so this issue will be resolved once it's in.


Upgrade to client-go v12

client-go v12 is out, but we just upgraded to v11 in 0.14 and I don't want to chase the bleeding edge to closely as the backwards compat story for client-go is underspecified.
Let's aim to upgrade to client-go v12 in the 0.15 milestone

I'd like to have a look at this one

Sure thing, but please hold til 0.15 in August

On 6 Jul 2019, at 20:09, Dylan Graham<EMAIL_ADDRESS>wrote:
I'd like to have a look at this one
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hey @DylanGraham, are you still planning on working on this? We just released v0.14 so feel free to take this one if you'd still like to do that.

Sure, I can have a look tonight

The tests passed but should I be concerned about what go mod has removed from the indirect dependencies?

Should be fine, CI always builds from what is in go.mod, so if it
doesn't complain then everything is fine.
On Tue, 23 Jul 2019 at 05:08, Dylan Graham<EMAIL_ADDRESS>wrote:

The tests passed but should I be concerned about what go mod has removed from the indirect dependencies?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


[WIP] Add object retirement_requester

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1638502
We should be setting the retirement_requester on the object, not just the retire request.

@miq-bot add_label hammer/yes, bug, blocker, gaprindashvili/yes
but please don't backport, will need to open a whole new PR for gap
@miq-bot add_reviewer @tinaafitz
@miq-bot add_reviewer @bdunne
@miq-bot add_reviewer @kbrock

@miq-bot remove_label wip

@miq-bot assign @gmcculloug

@miq-bot add_reviewer @mkanoor

Anyone? Anyone? I know you all are 👻 s but it's 12 lines of code.

It's g/yes but can't be backported, will be opening another for the gap branch.
don't backport me to g, please
though h is fine...

Hammer backport details:
$ git log -1
commit c7715ec2ef78f24933420868fa2c1dc2fb2e4711
Author: Keenan Brock<EMAIL_ADDRESS>Date:   Mon Oct 22 14:39:22 2018 -0400

    Merge pull request #18113 from d-m-u/adding_object_retirement_requester

    Add object retirement_requester

    (cherry picked from commit aaf424f04def8ce40be7e639730782c9f8f38042)

    https://bugzilla.redhat.com/show_bug.cgi?id=1638502


Allow trust_remote_code and use_fast to be specified in args for Hugging Face

trust_remote_code
Currently, attempting to set trust_remote_code in args for HuggingFaceClient fails because trust_remote_code is already hardcoded to True, resulting in the error message:
Traceback (most recent call last):
  File "/.../helm/venv/lib/python3.8/site-packages/retrying.py", line 251, in call
    attempt = Attempt(fn(*args, **kwargs), attempt_number, False)
  File "/.../helm/src/helm/clients/auto_client.py", line 111, in make_request_with_retry
    return client.make_request(request)
  File "/.../helm/src/helm/clients/huggingface_client.py", line 267, in make_request
    huggingface_model: HuggingFaceServer = HuggingFaceServerFactory.get_server(
  File "/.../helm/src/helm/clients/huggingface_client.py", line 209, in get_server
    HuggingFaceServerFactory._servers[helm_model_name] = HuggingFaceServer(
  File "/.../helm/src/helm/clients/huggingface_client.py", line 89, in __init__
    self.model = AutoModelForCausalLM.from_pretrained(
TypeError: from_pretrained() got multiple values for keyword argument 'trust_remote_code'

We fix this by only passing trust_remote_code=True to AutoModelForCausalLM if it is not specified in args. Eventually we will break backwards compatibility - we will stop passing trust_remote_code=True if unspecified, and require users to specify it trust_remote_code in args if they need it. This is because the trust_remote_code=True default is a security risk.
use_fast
Currently, it is not possible to set use_fast for Hugging Face tokenizers, because two different Hugging Face tokenizers are instantiated for a run that uses HuggingFaceClient, one inside HuggingFaceClient here and one inside HuggingFaceTokenizer. This is problematic because the first tokenizer is instantiated using the args from the model_deployment.yaml, not the args from tokenizer_config.yaml, whereas the second tokenizer is instantiated using the args from tokenizer_config.yaml. Attempting to set use_fast in model_deployments.yaml results in this error:
Traceback (most recent call last):
  File "/.../helm/venv/lib/python3.8/site-packages/retrying.py", line 251, in call
    attempt = Attempt(fn(*args, **kwargs), attempt_number, False)
  File "/.../helm/src/helm/clients/auto_client.py", line 111, in make_request_with_retry
    return client.make_request(request)
  File "/.../helm/src/helm/clients/huggingface_client.py", line 267, in make_request
    huggingface_model: HuggingFaceServer = HuggingFaceServerFactory.get_server(
  File "/.../helm/src/helm/clients/huggingface_client.py", line 209, in get_server
    HuggingFaceServerFactory._servers[helm_model_name] = HuggingFaceServer(
  File "/.../helm/src/helm/clients/huggingface_client.py", line 89, in __init__
    self.model = AutoModelForCausalLM.from_pretrained(
  File "/.../helm/venv/lib/python3.8/site-packages/transformers/models/auto/auto_factory.py", line 563, in from_pretrained
    return model_class.from_pretrained(
  File "/.../helm/venv/lib/python3.8/site-packages/transformers/modeling_utils.py", line 3550, in from_pretrained
    model = cls(config, *model_args, **model_kwargs)
TypeError: __init__() got an unexpected keyword argument 'use_fast'

We fix this by deleting the first tokenizer and only using the second tokenizer.
Fixes #2639

These changes were merged by #2647


Consistent code style

I suggest running clang-format over all the code (with your preferred style, ofcourse).

There was no clang-format 10 years ago, I think. Now it is too late. Reformatting would essentially reset all the past commit history.


Template validation

Is it possible to make template validation before creating actual report?

The commands in the template are arbitrary JavaScript, so you cannot really validate them without executing the entire template. At least i havent found a convenient way to do so.

Maybe there is a way check template syntax?
I mean to check if commands
+++ QUERI { data { title, description }} +++
    ^^^^^
Error: Syntax error near 1:1. Unknown identifier "QUERI"

are written in the write way but skip values accessing

You can use listCommands to get a list of all the commands, but you'll have to parse and validate them using your own custom validation routine. But still, the only 100% sure way to validate template correctness is by running the code in the template commands.


update Examine plugin to trigger on ground items

Fixes #6201.
These PR updates a conditional in the Examine Plugin so that price lookups are triggered when examining items on the ground and a message is posted to chat, the same way it behaves when examining an inventory item.

Does this enhancement still need to be worked on? If so, I can make an attempt at it.

I think I just need to address the comments from Nightfirecat above. I lost track of this stuff because I started a new job right as hacktoberfest ended. I can wrap this up right when 2019 comes around I'm sure.

Ok, I will leave it to you


🕛 👥 - Schedule community meetups - your (yes you!) input requested!

We would like to restart community meetups in the new year targeting the end of January - if folks have time-preferences please emoji react on the slack thread!
https://kubernetes.slack.com/archives/C03B6BJAUJ3/p1702528750088229

I'm excited about this!  I submitted my response on Slack.

The Zarf community meetup timing has been set! (thanks to those who provided input! Monday won with a split between morning / afternoon)
Please join us on Monday January 22nd at 1200 MST to discuss upcoming changes to Zarf (required -> optional :eyes:), our plans for the future and to meet fellow Zarf users!
This event will take place in our community gather.town space accessible here: https://app.gather.town/invite?token=i5DrbM-WQhO792nXUR7m - feel free to join it at any time to get acquainted with the space - we'll kickoff in the large central room on the Zarf rug.
https://kubernetes.slack.com/archives/C03B6BJAUJ3/p1705447722692329


convolve2d and correlate2d read memory outside of inputs in some cases

When calling scipy.signal.convolve2d and correlate2d with an in1.shape that has a value that is less than half of the corresponding value in in2.shape then boundary!="constant" and mode!='valid' will read outside of the array. This can be see in https://github.com/scipy/scipy/blob/4e3d82268eae3c89e94ff5f3c3774bb12c12982a/scipy/signal/firfilter.c#L166-L175. In those lines it is possible that ind0 < 2*NS[0] or ind0 > 2*NS[0] when in1.shape has a value that is less than half of the corresponding value in in2.shape resulting in an ind0 that is still out-of-bounds after those if statements. The circular conditions (or wrap) need a % operation while the reflect conditions (or symm) need at least a % and min operations.
There are a similar set of lines later for ind1 and NS[1].
As a quick check that garbage is not being read, the following should be True:
import numpy as np, scipy.signal as sig, scipy.ndimage as ndi
a = np.arange(1, 10*3+1, dtype=float).reshape(10, 3)
b = np.arange(1, 10*10+1, dtype=float).reshape(10, 10)
print((sig.convolve2d(a, b, mode='same', boundary='wrap') == ndi.convolve(a, b, mode='wrap', origin=(-1, -1))).all())

I have identified that this also always occurs when mode='full' and boundary != 'constant'. Example:
a = np.arange(1, 3*3+1, dtype=float).reshape(3, 3)
b = np.arange(1, 6*6+1, dtype=float).reshape(6, 6)
sig.convolve2d(a, b, mode='full', boundary='wrap') == ndi.convolve(np.pad(a, ((3, 3), (3, 3)), 'wrap'), b, mode='wrap')[:-1,:-1]

Currently only the central 4x4 region is equal and the bordering 2 rows and columns on each side are incorrect. In fact, this time around for me, some of the values in the output of just sig.convolve2d(a, b, mode='full', boundary='wrap') were in the order of magnitude 1e228 indicating usage of memory not part of the data at all.


Do not put ember-cli-memory-leak-detector in <meta name="frontend/config/environment" ...

Even if the memory-lead detector is disabled, I see it puts this:
"ember-cli-memory-leak-detector":{"enabled":false,"failTests":true,"remoteDebuggingPort":9222,"timeout":null,"ignoreClasses":[],"writeSnapshot":false}

In the meta tag for Ember's environment in the HTML. Is it possible to change this behavior so this happens only when the detector is enabled?

I see why this would be desired, however I'm not sure this is something that is possible.
This seems to be where ember-cli inserts that meta tag, and I don't see any way for an individual addon to prevent its config from being included there.
https://github.com/ember-cli/ember-cli/blob/master/lib/utilities/ember-app-utils.js#L95-L101
Are your concerns related to adding unnecessary content/file size? Or something else?
One way around this could be defaulting the enabled flag to false. This way you could omit the entire config for ember-cli-memory-leak-detector in environments where you don't want it to run, and you would need to opt-in to specific environments by adding a config object with enabled: true.
This would be a breaking change so I'd like to consider other options there may be before going down that road.

@steveszc - thanks for the answer. Where I saw this was in our integration tests. We have a check that there are no null values in the HTML. And when I updated ember-cli-memory-leak-detector, there suddenly were - because of the newly added timeout setting which defaulted to null and was put in the HTML.
Not a big problem, of course, I just added a value for it, but in any case it would be nice to not have this (if possible). Especially for production where ember-cli-memory-leak-detector shouldn't be run at all.


FR: Change Font CSS

Description
To comply with legal requirements, the font "Helvetica" and fallback font "Arial" owned by Monotype, must be replaced. "Inter" an open-source font, will serve as the new CSS fallback font across all Mack Truck website domains.
Priority
Critical
Acceptance Criteria
Some identified areas where Arial exists (TBU): @alexiscoelho

[x] Dealer locator

[x] HTML pages fallback

[x]  Remove all fallback font information related to “Arial” and "Helvetica" and change it to "Inter" for all Mack Trucks domains:

[x] USA
[x] Canada
[x] Mexico
[x] Australia
[x] New Zealand
[x] Bahamas
[x] Dominican Republic
[x] Haiti
[x] Costa Rica
[x] El Salvador
[x] Guatemala
[x] Panama
[x] Nicaragua
[x] Honduras
[x] Middle East
[x] Nigeria
[x] Argentina
[x] Bolivia
[x] Chile
[x] Colombia
[x] Ecuador
[x] Guyana
[x] Peru
[x] Trinidad and Tobago
[x] Venezuela

[ ] Once the above is completed, we should include a link to a license notice on the relevant websites so that we are in line with good open source practice. (see e.g. https://www.lego.com/en-us/legal/notices-and-policies/open-source/?locale=en-us as an example, where LEGO provides a notice for its use of Noto Sarif under the OFL)

[ ]  Verify font usage across all sites for layout issues, ideally in a staging environment prior to go-live.

Value creation
Compliance & standards
Cost of fixing
Low cost
Technical complexity
S
References
Inter (by Google Inc.) as a fallback font for websites: https://fonts.google.com/specimen/Inter/license
• Inter is licensed under the SIL Open Font Licence V. 1.1 (“OFL”)
Out of Scope

[x] Helvetica to be addressed in a separate ticket when needed

Related Tickets
https://github.com/hlxsites/vg-roadchoice-com/issues/251
https://github.com/hlxsites/vg-volvotrucks-us/issues/667
https://github.com/hlxsites/vg-partsasist/issues/114

regarding Helvetica, this also apply for Helvetica Neue LT Pro and Helvetica Neue?
the following font family list are affected:

Helvetica Neue LT Pro 55 Roman
Helvetica Neue LT Pro 65 Medium
Helvetica Neue LT Pro 75 Bold
Helvetica Neue LT Pro 56 Roman Italic
Helvetica Neue LT Pro 66 Medium Italic
Helvetica Neue LT Pro 76 Bold Italic
Helvetica Neue 85 Heavy

@jonatan-lledo-netcentric Yes - all of those related fonts for Helvetica will need to be removed and replaced.

Testing completed. Everything works accordingly!

Helvetica is also addressed in this ticket.
The 2 remaining ACs, are open to be taken care by the content team.

Testing finished on one more market (Bahamas). Everything works accordingly.

@Meli-lazarte  and @Kannan-CM Moving content task to CMS board in Sharepoint: Once the above is completed, we should include a link to a license notice on the relevant websites so that we are in line with good open source practice. (see e.g. https://www.lego.com/en-us/legal/notices-and-policies/open-source/?locale=en-us as an example, where LEGO provides a notice for its use of Noto Sarif under the OFL)


Consider publishing src/parser.rs under separate Cargo crate

src/parser.rs's code is mostly independent from HVM now. I think it's a really nice parser to use in general and would love to see it published under a separate crate to encourage other people to use it without them having to care about HVM (or having to copy-paste the code into their own projects).
Thanks to the MIT license I could obviously do this myself and become the maintainer of the parser, but that seems a bit silly since I never even contributed to the parser and am completely unrelated to the HVM project. That is why I am asking here if the HVM developers want to do it themselves.

I think this is nice. I was already thinking about doing it for Kind2 (but generating the parser with Tree-sitter). It would help to compile and use the parser independently on the browser, for example.
I just need the time. 😅

It isn't that nice of a parser though, but it is indeed independent so yes, may be a good idea.

Closing the issue, but I intend to do it later on.


Run functions from australia-southeast1 region

Resolve error:
Access to fetch at 'https://australia-southeast1-team-bldr.cloudfunctions.net/createStripePrice' from origin 'https://team-bldr.web.app' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: Redirect is not allowed for a preflight request.

Functions need to be deployed to work :) Otherwise, you will get this error.


Updated sops binary to the latest release 3.6.1

some usefull features were added
e.g.: --unencrypted-regex
usage example:
--unencrypted-regex '^(kind|apiVersion|group|metadata)$'
see
https://github.com/mozilla/sops/releases/tag/v3.6.1
unencrypted-regex wasn't supported in the
previous versions and if someone uses it
sops krm-function with older binary won't be able
to decrypt that.
PS
build is failing, but I guess just need to rebase after https://github.com/GoogleContainerTools/kpt-functions-catalog/pull/121 is merged

: lstat /tmp/kpt-get-384055262/examples/helm-template: no such file or directory
error: lstat /tmp/e2e.kpt_helm_inflator_declarative_example.xEXaF4Yy/helm-template/local-configs: no such file or directory

@Shell32-Natsu It seems there is a test failure related to helm-inflator, can you please take a look?

: lstat /tmp/kpt-get-384055262/examples/helm-template: no such file or directory
error: lstat /tmp/e2e.kpt_helm_inflator_declarative_example.xEXaF4Yy/helm-template/local-configs: no such file or directory

@Shell32-Natsu It seems there is a test failure related to helm-inflator, can you please take a look?

@mengqiy let me just rebase that. I think it will work after that. I made this change before the helm-inflator changes.


fix bashism

[[ ]] is not available in POSIX sh, and test -o is not well defined either.
Move the facts-gathering script out so it can be tested with shellcheck.

@mergify queue


Add missing documentation for benchmarking synthetic data generation tutorial

This PR adds the missing documentation for the benchmarking synthetic data generation tutorial.
Note: A draft of Section 6 on benchmarking already exists, which I've renamed to "draft" for clarity. We might want to include some ideas from this "draft" to improve the tutorial. For example, the section on "Choosing the Best VM for the Job".

I have changed this PR to merge to main in order for the docs to get updated asap. After the merges ill merge dev into main again

I will send more comments soon. Sorry I could not do this before.

When can we merge this PR? Since this is merging to main now, every commit will trigger an action to run our tests (run the python tests for each simulator) that takes around 40 minutes.
If the PR is still not ready for merging lets change the merge to dev and only when we are ready to merge we can change merge to main to avoid triggering the action every time.

When can we merge this PR? Since this is merging to main now, every commit will trigger an action to run our tests (run the python tests for each simulator) that takes around 40 minutes.
If the PR is still not ready for merging lets change the merge to dev and only when we are ready to merge we can change merge to main to avoid triggering the action every time.

I was waiting for the tests to complete. I will merge it now.


build.sh does not work in zsh, but in bash

When I started the build.sh in zsh it only changed directory to /build, but it did nothing else. When I started bash (even from zsh) and started build.sh again everything worked.

I'm not a bash or zsh expert. I'm lucky I got the current script working as is 😅.
Do you see anything glaringly obvious as to why it's not working? Basically I just wanted to add some checks to see if there was a valid build for each font before processing. Any help would be appreciated.
Thanks!

I am having the same issue

Hm... not sure why you're getting the errors. It's working here for me.
As you can see, I switched to the zsh shell. Are you getting any error messages?

Have you tried running ttx or node from the command prompt?

Also having the same issue. Running the ./build.sh command creates a build folder but nothing happens. No error messages...just back to a blank line after.

@dinophile that sounds more like your font files have the wrong filenames. See #26.

@kiliman Ah right...thank you for pointing that out! Will try again when I get back to my keyboard!


Fix eof issue

Codecov Report

Merging #1254 into master will increase coverage by 20.05%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master    #1254       +/-   ##
===========================================
+ Coverage   79.86%   99.91%   +20.05%
===========================================
  Files          30       31        +1
  Lines        2299     2319       +20
  Branches       86       88        +2
===========================================
+ Hits         1836     2317      +481
+ Misses        462        1      -461
  Partials        1        1

Impacted Files
Coverage Δ

tests/test_cli/test_common/test_utils.py
100% <0%> (ø)

tests/conftest.py
100% <0%> (+2.5%)
:arrow_up:

tests/test_dcos_e2e/test_legacy.py
100% <0%> (+14.63%)
:arrow_up:

tests/test_cli/test_dcos_vagrant/test_cli.py
100% <0%> (+100%)
:arrow_up:

tests/test_cli/test_dcos_docker/test_cli.py
100% <0%> (+100%)
:arrow_up:

tests/test_cli/test_dcos_aws/test_cli.py
100% <0%> (+100%)
:arrow_up:

Continue to review full report at Codecov.

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


Incompatible with Zotero 6.0.10

When I try to install the v6.7.17 into the newest Zotero, I got an incompatible error. But, v6.3.0 can be installed.

BBT is tested every night on the latest version (on Linux), and I've just downloaded 6.7.17 and installed it on Zotero 6.0.10 on Mac, and both work. What platform are you on, and what error are you getting?

I'm using elementary OS :
Distributor ID:	Elementary
Description:	elementary OS 6.1 Jólnir
Release:	6.1
Codename:	jolnir

Linux version 5.11.0-40-generic (buildd@lgw01-amd64-010) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #44~20.04.2-Ubuntu SMP Tue Oct 26 18:07:44 UTC 2021

How did you install Zotero?

Followed the steps here: Download the tarball, extract/copy the directory, and run.

Do you know where I can download an image of elementary OS?

NM, got it

I can't install elementary in a VM, the install window paints what I assume must be the "install" or "continue" button outside the VM display.

Em ... Don't worry. I can continue to use the old one. Just curious about what's wrong with the newest version.

I don't support old ones. The newest version is fine AFAICT, I've also just installed it on my Ubuntu machine without problems, so that makes 3 machines across two platforms that install without issue. Are you willing to try out the deb packages from https://github.com/retorquere/zotero-deb/ ?

I also can't install elementary on virtualbox on linux, same problem with the screen size. Without access to a box with elementary, I cannot do anything. But it is simply not true that 6.7.17 is incompatible with zotero 6.0.10, and I'd love to fix your problem.

I'm not sure the apt error traces back to my zotero packages. The dependencies of the zotero packages are
Depends: gnupg, libatk1.0-0, libc6, libcairo-gobject2, libcairo2, libdbus-1-3, libdbus-glib-1-2, libfontconfig1, libfreetype6, libgdk-pixbuf2.0-0, libglib2.0-0, libgtk-3-0, libharfbuzz0b, libpango-1.0-0, libpangocairo-1.0-0, libpangoft2-1.0-0, libstdc++6, libx11-6, libx11-xcb1, libxcb-shm0, libxcb1, libxcomposite1, libxcursor1, libxdamage1, libxext6, libxfixes3, libxi6, libxrender1, libxt6

I also don't see apt installing zotero in your output. When I install on ubuntu, I see this:
$ sudo apt install zotero
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
  crda
Use 'sudo apt autoremove' to remove it.
The following NEW packages will be installed:
  zotero
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 71,6 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 https://zotero.retorque.re/file/apt-package-archive ./ zotero 6.0.10 [71,6 MB]
Fetched 71,6 MB in 13s (5.337 kB/s)
Selecting previously unselected package zotero.
(Reading database ... 309864 files and directories currently installed.)
Preparing to unpack .../zotero_6.0.10_amd64.deb ...
Unpacking zotero (6.0.10) ...
Setting up zotero (6.0.10) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Processing triggers for desktop-file-utils (0.26-1ubuntu3) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu3) ...
Processing triggers for shared-mime-info (2.1-2) ...

notice the Get -- that's not present in your output.
What happens if you try to install anything else, eg sudo apt install thunderbird? I'm curious whether you would see the same "Unmet dependencies". If so, it looks like your install is b0rked.

I finally managed to install elementary, and the debs install there without any problem whatsoever, and BBT installs without issue in those. I'm afraid you have broken your Elementary installation.

I've also encountered this in Archlinux. Installing latest BBT v6.7.17 gives me a "it may be incompatible with this version of Zotero" error, while v6.7.16 works fine.
❯  uname -srv
Linux 5.18.11-arch1-1 #1 SMP PREEMPT_DYNAMIC Tue, 12 Jul 2022 15:40:51 +0000
❯  zotero --version
Zotero Zotero 6.0.5, Copyright (c) 2006-2018 Contributors

@heyrict that is a different issue, BBT 6.7.17 is indeed not compatible with Zotero 6.0.5, you will need to upgrade to at least Zotero 6.0.9.

A note for anyone else who had this issue; On Arch, I had this just now. I can't remember exactly which version of Zotero I had (I'd assumed up-to-date, I'd literally just updated everything), but after hitting "Find Updates" on BetterBibTeX I still had the same message.
I ended up searching for the zotero package (I'm on Arch) - weird, I had it installed, but it wasn't available on the repositories. zotero-bin was, however, available on the AUR, and I installed it (uninstalled the current installation as part of the process). Plugins window wouldn't show, so I rebooted, and now everything's fine and dandy.
TL;DR: Installed zotero-bin from Arch repos and rebooted, fixed it for me. Still not sure which of the two (or both) did it, but there we go.

@zxdawn I don't see what I can do here, short of logging in in on your system and fixing your apt state. Unless you have other suggestions I am going to have to close this issue.

@retorquere The Get step isn't shown because I have run that before.
The broken package is discussed on stackoverflow, but no answer yet.
Anyway, I have switched to Mac OS and everything works well .... I'm gonna close this and if users have similar problem, they can check it.


Is neo4j-rake_tasks useful for production?

I'm doing a few benchmarks for my app using derailed gem.
I noticed that neo4j is including neo4j-rake_tasks, that is useful for development, but I don't think it's very useful for production environment. Is there any way to exclude it?
I tried:
gem 'neo4j-rake_tasks', require: false, group: :production

But... well. It was not a great idea :laughing:

Can you just do this?
gem 'neo4j-rake_tasks', group: [:development, :test]

Bundler should only auto-require for the environment's gems, I think

I tried, but derailed says that it's still required. :
I think bundler is ignoring me, since neo4j-rake_tasks is an explicit dipendence ...

Oh, right, yeah, it probably is because neo4j-core depends on it...
Perhaps we should make neo4j-rake_tasks be an explicit dependency of apps.  We could remove it as a dependency of neo4j-core, though we'd probably want to give a deprecation warning first.  And/or maybe when we remove it we could temporarily create rake tasks in neo4j-core (which neo4j-rake_tasks would override) which just output a message about how you now need to require the gem explicitly and providing an example of how to do it just in development / test
Pinging @subvertallchris for an additional opinion

I think closed by https://github.com/neo4jrb/neo4j-core/commit/4ac9a4156eaad06b3b11c29f7d6a33d1c4c1683c


evse_notification  incorrectly used to detect shutdown request from EVSE in dinspec

Hi,
For din spec on the EV side, EVSE initated shutdown is checked like this:
`
if dc_evse_status.evse_notification == EVSENotification.STOP_CHARGING:
    logger.debug("EVSE Notification received requesting to stop charging.")
    await self.stop_charging()

`
DIN spec states however that evse_notification should always be set to None.
What you actually want to check is DCEVSEStatusCode.
There for if the EVSE wants to initate shutdown it currently will not work

Hi @heavyweight87 ,
Thank you for pointing this out. Linking the corresponding requirement below:
[V2G-DC-500] For DC charging according to DIN SPEC 70121, the value of EVSENotification shall always be set to “None”.

And the following regarding EVSEStatusCode:
In the context of DIN SPEC 70121, “EVSE_Shutdown” is used by the SECC to trigger a termination of the charging process in situations other than an emergency shutdown, see chapter <IP_ADDRESS>.2. “EVSE_EmergencyShutdown” may be used by the SECC to inform the EVCC that the EVSE is in the process of, or has just executed, an emergency shutdown. However, to force the EV to participate in the emergency shutdown, the SECC does not use this value, but instead uses the CPL in accordance with IEC 61851-23. In all other cases, the expected value for EVSEStatusCode is “EVSE_Ready” or “EVSE_IsolationMonitoringActive”.

I have created an internal ticket to fix this. Will update here once it goes in to a release. Or feel free to open a PR to fix this if this is quite urgent for you and we can merge the fix.

Hi
I opened a PR for this as well as a previous issue I opened about the EVCC not having a way to indicate when charging is enabled (i.e. going to state C) #368


Integrated terminal stops responding in Powershell on Ctrl+C

Open the integrated terminal with Powershell (7.2.11)
Press Ctrl+C
The terminal no longer responds to any input 🐛

This does not happen with cmd.exe

Relevant error:
workbench.desktop.main.js:sourcemap:688 Uncaught TypeError: Cannot read properties of undefined (reading 'replaceAll')
    at s (workbench.desktop.main.js:sourcemap:688:4739)
    at e.ShellIntegrationAddon.u (workbench.desktop.main.js:sourcemap:688:2879)
    at e.ShellIntegrationAddon.r (workbench.desktop.main.js:sourcemap:688:2021)
    at t.OscHandler._handler (workbench.desktop.main.js:sourcemap:688:1334)
    at t.OscHandler.end (OscParser.ts:223:18)
    at t.OscParser.end (OscParser.ts:159:45)
    at c.parse (EscapeSequenceParser.ts:777:43)
    at E.parse (InputHandler.ts:485:35)
    at n._action (CoreTerminal.ts:145:99)
    at n._innerWrite (WriteBuffer.ts:164:27)
    at WriteBuffer.ts:124:29

The fix for this was merged today, afk at the moment but let us know if you see it tomorrow


Provide a way to set media type for a file in FileService

Motivation:
We want to provide a way to add custom MimeTypeFunction implementation to FileService to be able to use for resolving MediaType.
Modifications:

Add a new interface MimeTypeFunction.
Add mimeTypeFunction to  FileServiceBuilder to allow user to add custom implementation. if not set then default which implements using MimeTypeUtil is used.
Add MimeTypeFunction into FileServiceConfig.
Alter FileService to use MimeTypeFunction for resolve MediaType.

Result:

Users able to add custom implementation of MimeTypeFunction to FileService
Closes #4001

Example:
FileService.builder(rootDir)
           .mimeTypeFunction(new CustomMimeTypeFunction())
           .build());

 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.

Thank you for all the feedback🙏. I'll get back to you once I finish. By the way, I have a question.

Should I also propagate MimeTypeFunction configuration to FileSystemHttpVfs so that we can use at https://github.com/line/armeria/blob/b34ae5975a089c33ead3a83c2ff5d60b015934af/core/src/main/java/com/linecorp/armeria/server/file/FileSystemHttpVfs.java#L107 ?

Should I also propagate MimeTypeFunction configuration to FileSystemHttpVfs ? So that we can use at

Yes, I think so. 😄
We can deprecate blockingGet and add the variant of blockingGet which takes MimeTypeFunction to use it. 😄

We can deprecate blockingGet and add the variant of blockingGet which takes MimeTypeFunction to use it.

Do you mean I should leave the old implementation and annotate with @Deprecated then copy the same function which takes MimeTypeFunction, right?
I have to update HttpVfs.get(...) add MimeTypeFunction to arguments. Should I also leave the old implementation and create a new method instead?

If I misunderstood anything, please let me know🙏. Thank you.

Do you mean I should leave the old implementation and annotate with @Deprecated then copy the same function which takes MimeTypeFunction, right?

Yes, exactly. 😄 We can't just change the method because it would be a breaking change.
So we need to add an additional method that delegates the call to the original method so that the subclasses of
AbstractBlockingHttpVfs implemented by users don't get any breaking changes. 😄
We are going to fix it when we reach 2.0.
// AbstractBlockingHttpVfs.java
protected HttpFile blockingGet(Executor fileReadExecutor, String path, Clock clock,
                               @Nullable String contentEncoding, HttpHeaders additionalHeaders,
                               MimeTypeFunction function) {
    return blockingGet(fileReadExecutor, path, clock, contentEncoding, additionalHeaders);
}

I have to update HttpVfs.get(...) add MimeTypeFunction to arguments. Should I also leave the old implementation and create a new method instead?

Yeah, we should do that for the same reason. 😄
default HttpFile get(Executor fileReadExecutor, String path, Clock clock,
                     @Nullable String contentEncoding, HttpHeaders additionalHeaders,
                     MimeTypeFunction function) {
    return get(fileReadExecutor, path, clock, contentEncoding, additionalHeaders);
}

@klurpicolo Could you resolve the coflicts?

Thank you guys for helping me to review my commits!!

Thanks a lot for your work, @klurpicolo!


fix(chisel): improve Etherscan API error handling

Motivation
I was getting unexpected "Contract is not verified!" errors when trying to use the !fetch feature. Turns out I had an old API key set as an environment variable and Etherscan was actually complaining about that. But the current error handling interprets any non-JSON result value as the contract not being verified.
Solution
Etherscan responds status == "1" if it was successful, so check for that instead. When status != "1", then the result field contains a human readable error. So report that if it's present.
Now we get the expected "Invalid API Key" or "Max rate limit reached..." message which makes it clear why it's failing.

Fixed the lint errors


fix: full width ai bubble menu

Apparently, Tippy's maxWidth is set to 350px by default...
However, changing that option alone doesn't give it full width. I had to directly target the tippy-2 element to get this to work. (see #30)

Note: was looking at Notion's menu and i think that constraining the menu to be inside the text editor would be better. For reference:

@redac this looks awesome – thank you! Can. you please make this PR against the ai-edit branch instead? It's a bit hard to tell which code changes did you make 😅

@steven-tey Just changed the PR's base to ai-edit, does that do it? 😅

@redac yes, thank you! Will take a look today!

Closing this for now – will need to rethink the UI 😅 thanks though!


Unable to create a policy tag or list the tag from a target taxonomy

Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Please run down the following list and make sure you've tried the usual "quick fixes":

Search the issues already opened: https://github.com/googleapis/python-datacatalog/issues
Search StackOverflow: https://stackoverflow.com/questions/tagged/google-cloud-platform+python

If you are still having issues, please be sure to include as much information as possible:
Environment details

OS type and version: Ubuntu 20.04 LTS
Python version: python --version: 3.8.10
pip version: pip --version: 22.3.1
google-cloud-datacatalog version: pip show google-cloud-datacatalog :3.9.3

Steps to reproduce

? Create a taxonomy in asia-southeast1 using the code from python-datacatalog\samples\snippets\data_catalog_ptm_create_taxonomy.py
? Try to create a policy tag attach to the taxonomy above using the code from python-datacatalog\samples\generated_samples\datacatalog_v1_generated_policy_tag_manager_create_policy_tag_sync.py

Code example
# example

# Create taxonomy
parent = datacatalog_v1.PolicyTagManagerClient.common_location_path(
            project_id, location_id
)
taxonomy = datacatalog_v1.Taxonomy()
taxonomy.display_name = taxonomy_id  # type: ignore
taxonomy.description = "This Taxonomy represents ..."  # type: ignore
try:
    taxonomy = self.client_ptc.create_taxonomy(parent=parent, taxonomy=taxonomy)
except Exception as e:
    print(f"The taxonomy_id={taxonomy_id} is already exists")
    return False
else:
    print(f"Created taxonomy {taxonomy.name}")
    return True

# Create policy tag, this part failed
parent = datacatalog_v1.PolicyTagManagerClient.common_location_path(
    project_id, location_id
)
client = datacatalog_v1.PolicyTagManagerClient()
request = datacatalog_v1.CreatePolicyTagRequest(
    parent=parent,
)
response = client.create_policy_tag(request=request)
print(response)

Stack trace
Traceback (most recent call last):
  File "d:\np\npblind\.venv\lib\site-packages\google\api_core\grpc_helpers.py", line 72, in error_remapped_callable
    return callable_(*args, **kwargs)
  File "d:\np\npblind\.venv\lib\site-packages\grpc\_channel.py", line 946, in __call__
    return _end_unary_response_blocking(state, call, False, None)
  File "d:\np\npblind\.venv\lib\site-packages\grpc\_channel.py", line 849, in _end_unary_response_blocking
    raise _InactiveRpcError(state)
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
        status = StatusCode.INVALID_ARGUMENT
        details = "Request contains an invalid argument."
        debug_error_string = "UNKNOWN:Error received from peer ipv4:<IP_ADDRESS>:443 {grpc_message:"Request contains an invalid argument.", grpc_status:3, created_time:"2022-12-02T04:23:19.522059716+00:00"}"
>

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "C:\Users\nnopp\AppData\Local\Programs\Python\Python38\lib\runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "C:\Users\nnopp\AppData\Local\Programs\Python\Python38\lib\runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "c:\Users\nnopp\.vscode\extensions\ms-python.python-2022.18.2\pythonFiles\lib\python\debugpy\adapter/../..\debugpy\launcher/../..\debugpy\__main__.py", line 39, in <module>
    cli.main()
  File "c:\Users\nnopp\.vscode\extensions\ms-python.python-2022.18.2\pythonFiles\lib\python\debugpy\adapter/../..\debugpy\launcher/../..\debugpy/..\debugpy\server\cli.py", line 430, in main
    run()
  File "c:\Users\nnopp\.vscode\extensions\ms-python.python-2022.18.2\pythonFiles\lib\python\debugpy\adapter/../..\debugpy\launcher/../..\debugpy/..\debugpy\server\cli.py", line 284, in run_file
    runpy.run_path(target, run_name="__main__")
  File "c:\Users\nnopp\.vscode\extensions\ms-python.python-2022.18.2\pythonFiles\lib\python\debugpy\_vendored\pydevd\_pydevd_bundle\pydevd_runpy.py", line 321, in run_path
    return _run_module_code(code, init_globals, run_name,
  File "c:\Users\nnopp\.vscode\extensions\ms-python.python-2022.18.2\pythonFiles\lib\python\debugpy\_vendored\pydevd\_pydevd_bundle\pydevd_runpy.py", line 135, in _run_module_code
    _run_code(code, mod_globals, init_globals,
  File "c:\Users\nnopp\.vscode\extensions\ms-python.python-2022.18.2\pythonFiles\lib\python\debugpy\_vendored\pydevd\_pydevd_bundle\pydevd_runpy.py", line 124, in _run_code
    exec(code, run_globals)
  File "d:\np\npblind\npblind\core\tools.py", line 85, in <module>
    npb.create_policy_tag(taxonomy_id=taxonomy_name, location_id=location_id)
  File "d:\np\npblind\npblind\core\tools.py", line 75, in create_policy_tag
    response = client.create_policy_tag(request=request)
  File "d:\np\npblind\.venv\lib\site-packages\google\cloud\datacatalog_v1\services\policy_tag_manager\client.py", line 1132, in create_policy_tag
    response = rpc(
  File "d:\np\npblind\.venv\lib\site-packages\google\api_core\gapic_v1\method.py", line 154, in __call__
    return wrapped_func(*args, **kwargs)
  File "d:\np\npblind\.venv\lib\site-packages\google\api_core\grpc_helpers.py", line 74, in error_remapped_callable
    raise exceptions.from_grpc_error(exc) from exc
google.api_core.exceptions.InvalidArgument: 400 Request contains an invalid argument.

Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!

I am getting the same error
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
        status = StatusCode.UNIMPLEMENTED
        details = "Received http2 header with status: 404"
        debug_error_string = "UNKNOWN:Error received from peer ipv4:<IP_ADDRESS>:443 {created_time:"2022-12-12T16:45:18.560286+00:00", grpc_status:12, grpc_message:"Received http2 header with status: 404"}"
>

when calling the list policy tags method
    client = datacatalog_v1.PolicyTagManagerClient()

    # Initialize request argument(s)
    request = datacatalog_v1.ListTaxonomiesRequest(
        parent="***",
    )

    # Make the request
    page_result = client.list_taxonomies(request=request)

For the issue in https://github.com/googleapis/python-datacatalog/issues/449#issuecomment-1346881899, the stack trace looks the same as the one in https://github.com/googleapis/gapic-generator-python/issues/1650 . You'll need to specify a regional endpoint for this API.  For example,
endpoint = "us-west1-datacatalog.googleapis.com"
client_options = {"api_endpoint": endpoint}
client = datacatalog_v1.PolicyTagManagerClient(client_options)

instead of
client = datacatalog_v1.PolicyTagManagerClient()

There is an open issue https://github.com/googleapis/gapic-generator-python/issues/1650 which tracks improving the code snippets to show that a regional endpoint is required.

Hi @parthea thanks for coming back! yes I figured that out back in December and forgot to comment

For the error message in the original post, I was able to reproduce the issue. The problem appears to be that the parent field in CreatePolicyTagRequest needs to include information about the taxonomy.
I tried
parent = PolicyTagManagerClient.common_location_path(
    'PROJECT', 'LOCATION'
)
client = datacatalog_v1.PolicyTagManagerClient()
request = datacatalog_v1.CreatePolicyTagRequest(
    parent=parent,
)

but I received error
400 Request contains an invalid argument. [detail: "[ORIGINAL ERROR] generic::invalid_argument: invalid name \'projects/<PROJECT>/locations/<LOCATION>\'"

The correct format is parent="projects/<PROJECT>/locations/<LOCATION>/taxonomies/<TAXONOMY>"
parent="projects/<PROJECT>/locations/<LOCATION>/taxonomies/<TAXONOMY>"
client = datacatalog_v1.PolicyTagManagerClient()
request = datacatalog_v1.CreatePolicyTagRequest(
    parent=parent,
)

https://github.com/googleapis/gapic-generator-python/issues/1640 will track improving the automatically generated sample code to provide better sample snippets with examples for values.
I'm going to close this issue as we're tracking the documentation improvements in https://github.com/googleapis/gapic-generator-python/issues/1640.


"CXABI_1.3.9 not found" in 1.53.0 (CentOS 7)

VSCode Version: 1.53.0
OS Version:CentOS 7

Steps to Reproduce:

yum update code
open code
View -> Terminal

Error message occurs: "The terminal process failed to launch. A native exception occurred during launch (/lib64/libstdc++.so.6: Version 'CXXABI_1.3.9' not found (required by /us/share/code/resources/app/node_modules.asar.unpacked/node-pty/build/Release/pty.node))."
I downgraded to 1.52.1, all is fine again.

Does this issue occur when all extensions are disabled?: Yes

I have the same problem when I run code --list-extensions from the terminal.
OS Version: Linux x64 3.16.0-11-amd64 (debian jessie)

/duplicate of #115784


Fixes #3, fixes #4

Add Travis config
Add the build badges
Add the coverage generation

Fix concerns raised here https://github.com/looplab/eventhorizon/pull/231#issuecomment-424855169


Add type inference for ReduceScatterOp

Request description
Add type inference for ReduceScatterOp. Note: follow the split decision in https://github.com/openxla/stablehlo/issues/623

Looks like this is Infeasible and requires non-trivial infrastructure changes. See https://github.com/openxla/stablehlo/pull/564
Close for now and reopen when there's a clear plan.


Error is occurred after connector is published to azure web service

I am getting this error after calling "saveEvent.notifySuccess()". Can someone help me to fix the issue and I need to know is there any specific limitations for the connectors based on the Office365 subscriptions?

Note: this is worked for ngrok without any error.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0b92bda5-e2b6-843f-efdb-3cd1fda4d77a
Version Independent ID: 1119b12b-8650-f99a-4298-cc3f93f420f3
Content: Connectors developer dashboard - Outlook Developer
Content Source: docs/actionable-messages/connectors-dev-dashboard.md
Product: outlook
Technology: o365-connectors
GitHub Login: @jasonjoh
Microsoft Alias: jasonjoh

@piyumi25 we're limited in our ability to provide support in this forum. You might get better results posting on Stack Overflow. If this is working fine in your dev setup with ngrok but not after deploying, then you're likely looking at a configuration issue: either your connector registration needs to be updated with the new URLs of your Azure service, or there's some config issue on your Azure web app preventing the requests from going through.

@piyumi25 we're limited in our ability to provide support in this forum. You might get better results posting on Stack Overflow. If this is working fine in your dev setup with ngrok but not after deploying, then you're likely looking at a configuration issue: either your connector registration needs to be updated with the new URLs of your Azure service, or there's some config issue on your Azure web app preventing the requests from going through.


Update User.hs

Adds lenses for User data type.
Is there a reason, why this is missing?

No - they are deliberately missing for Preferences though as it causes ghc to run out of memory.

Thanks!


Filter.watch is awkward if you don't know how to use gevent (or even if you do)

Version: x.x.x
Python: 2.7/3.4/3.5
OS: osx/linux/win

What was wrong?
Currently, this won't work.
filter = web3.eth.filter('latest')
filter.watch(sys.stdout.write)

while filter.running:
    gevent.sleep(0)

The reason it doesn't work is that until the first gevent.sleep(..) call happens to yield the execution context, the filter's greenlet doesn't actually spin up.
How can it be fixed.
I think that this could be fixed one or both of two ways.

Within Filter.watch add a gevent.sleep(0) to allow the greenlet to spin up.  (This might be a bad idea.  It feels a little wrong but it might just work fine)
Within the Filter.watch method set the running flag to True so that the pattern above will work.

Cute Animal Picture

Within Filter.watch add a gevent.sleep(0) to allow the greenlet to spin up. (This might be a bad idea. It feels a little wrong but it might just work fine)

In my limited gevent understanding this doesn't feel wrong - you're just explicitly yielding the context. Is there a possible side effect I'm missing?

Not that I know of.  Is say proceed with that approach until a better idea
shoes up or it proves problematic.
On Tue, Oct 11, 2016, 2:12 AM rain<EMAIL_ADDRESS>wrote:
Within Filter.watch add a gevent.sleep(0) to allow the greenlet to spin up.
(This might be a bad idea. It feels a little wrong but it might just work
fine)
In my limited gevent understanding this doesn't feel wrong - you're just
explicitly yielding the context. Is there a possible side effect I'm
missing?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pipermerriam/web3.py/issues/106#issuecomment-252842523,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAyTgqi0Dh7sztqyUKjIqqo30765Qp_Rks5qy0T9gaJpZM4KI_V3
.

Added a PR https://github.com/pipermerriam/web3.py/pull/119

Fixed via #119


Add baggage http endpoint to agent

Coverage remained the same at 100.0% when pulling 2b0eac2d7718f3168df68f41b80abd35625aff97 on add_bagge_agent_endpoint into f6bca1c1d9e385323eeb5012a41cfe2955eb7c08 on master.

Coverage remained the same at 100.0% when pulling c130988c853d6ea661d771b7cf478361843d8a35 on add_bagge_agent_endpoint into f6bca1c1d9e385323eeb5012a41cfe2955eb7c08 on master.

Coverage remained the same at 100.0% when pulling a98cb0dbf27e39527ccb3ef5718f9d01dc575018 on add_bagge_agent_endpoint into f6bca1c1d9e385323eeb5012a41cfe2955eb7c08 on master.

Coverage remained the same at 100.0% when pulling 66ade9e6c12ea7d92c21e30ad77dbdc787babedd on add_bagge_agent_endpoint into 3c5b63cc1c167ee4b180cee4ce17eea01bb5f1a6 on master.

Coverage remained the same at 100.0% when pulling 4f68b391ad3e2862ac5f9dc3af593f3e4ffafb23 on add_bagge_agent_endpoint into 3c5b63cc1c167ee4b180cee4ce17eea01bb5f1a6 on master.


toc: need to set it within it's own style

div="content"
Is it possible to change this if I am now using ul else?

https://chat.openai.com/share/53b843d3-f2e0-46bd-a1dc-eeb44d4bd66d

If inserting JavaScript is not possible, see how to tap the collapsible chevron in SUMMARY

There is a CSS in Summary for collapsible menu

TODO

Just integrate these things in and see if it works.

Since I cannot "toc" generated connect, (I.e. add class, id, etc.) I cannot alter the way it looks.

Back at it.
I am having ChatGTP evaluate both mdbook-toc and mdbook to figure out how toc html is generated and can I insert class/id so I can CSS the heck out of it.

CAN: Hello! Thank you for your patience. I've been examining the provided mdBook codebase.
The rendering process in mdBook is handled by a number of different components, but the HTML generation for the Table of Contents (ToC) seems to be largely controlled by the render_item function in the html_handlebars_helpers.rs file.
Here is the relevant part of that file:
Copy code
pub(crate) fn render_item(item: &BookItem, ctx: &RenderItemContext) -> String {
    match *item {
        BookItem::PartTitle(ref part_title) => {
            render::render_part_title(part_title, ctx)
        },
        BookItem::Chapter(ref ch) => {
            render::render_chapter(ch, ctx)
        },
        _ => String::new(),
    }
}

The render_chapter function calls the render::render_chapter function, which seems to generate the HTML for each chapter, including the ToC.
Unfortunately, due to the complexity of the mdBook codebase and the lack of ability to execute and test the Rust code in this environment, I can't provide an exact code modification to add the class="toc" attribute to the ul and li tags.
However, you should look into the render_chapter function in the render.rs file and the render_item function in the html_handlebars_helpers.rs file. This is likely where you'd need to modify the code to add the class="toc" attribute.
Let me know if you need further assistance.


Readme

Hello,
Thank you for your great work!
Is this possible to add some guidelines for running experiment ?
Best regards,

Thanks for your interest in our work!
I have provided details about training our network in the readme file.
Thanks again!


feat: rfox dashboard claim rows

Description
... without click functionality for release, i.e this guy:

The reason is we can't do this without an ugly level of indirection, because of the nested memory routers and step index shenanigans, which means that instead of a simple history.push(),
we end up with a fugly (but working) diff to do a poor man's "push to claim confirm" (see PR on top of this one https://github.com/shapeshift/web/pull/7151)

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[x] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

relates to https://github.com/shapeshift/web/issues/6948

Risk

High Risk PRs Require 2 approvals

What protocols, transaction types or contract interactions might be affected by this PR?

Low, this only displays claims, nothing more here
Testing

Claims in RFOX dashboard are happy

Engineering

^

Operations

^

Screenshots (if applicable)

develop env

https://jam.dev/c/4b67e1ef-d887-4c29-a4eb-2dffc66596c1

prod env with REACT_APP_FEATURE_RFOX monkey patched to true

Ty for the stellar review @NeOMakinG!

399101f6e2: ensures we don't fire the onClick handler when outside of claim widget context
ef498d38b3: similarly, ensures we don't apply hover styles when outside of claim widger context
1b250fc481: the more meaty one, with proper loading states:

adds a new "Error fetching claims" copy/state
ensures <ClaimSelect /> also handles said errored state for UI consistency
does proper loading states handling in <Claims />, handling the pending, loading and success states properly to display either a skeleton when we're actually loading, a "No claims" state, or an errored state
directly related to the point above, useGetUnstakingRequestQuery becomes better at query programmativity. Not wanting to fire the request if not needed is good against overfetching, but not firing the query is not so good if we're trying to handle all loading states proper, as we'll be in an infinite pending state on unstaking request failures/no unstaking requests
ensures both useGetUnstakingRequestCountQuery and useGetUnstakingRequestQuery don't retry in case of errors, which may lead in very long loading states before surfacing the error

e1e5dfc3c8: propagates said loading changes to <ClaimSelect /> for consistency

https://jam.dev/c/45a9092a-9b91-4030-bb7c-910d04df01e7

Happy with the current implementation, UI and loaders are well fine grained
Except one thing that has been introduced here:
jam.dev/c/9242a091-2b44-4f5b-bcd9-b439505ae3c7
The claim empty state is shown initially inside the widget 👀

Very very nice catch @NeOMakinG - tackled in https://github.com/shapeshift/web/pull/7182!

Happy to merge this PR as-is with the other related PRs in flight 🙏
gm sers


State-blocks exchange queue

Instead of directly calling the routines to fetch and publish blocks they should be added to a queue and processed by a worker.
If a block fails to be fetched or published it should be scheduled for a retry on said queue.

Fixed with a simple retry mechanism, no need for queues yet


Environment feature

These are simple key/value yaml files that can be used as a map against the config as if the config were a python string.Template template.
This allows for substituting values based on the environment, which seems like it might be a pretty common use case.

:+1:


Enemy turning

Created function in game director that checks for enemies at a turn tile and re directs them.
Worked with Toni, got the a-ok.

I'M SO STOKED ABOUT ENEMIES TURNING! But let's test this before we merge it in.

Looks great!


Frimware version could not be automatically detected!!!

Hi everybody
A few weeks ago, I had run PM2.5 sensor on Raspberry Pi and it worked fine. Today I checked it again, but it does not work! I receive following error message: "Your frimware version could not be automatically detected. This is usually caused by bad wiring or a poor power supply. If niether of these are likely candidated open an issue on the github ...". I checked the power connections, everything is OK.
Before of this, I have update Rasbian OS. Also I attached a BME280 sensor to my board too. Can anybody help me?

I have put "alpha=opc.OPCN2(spi) in a while loop as follows (to remove the previously mentioned startup error in working by PM2.5 sensor):
while True:
try:
alpha = opc.OPCN2(spi)
break
except Exception as e:
print ("Error:{}".format(e))
but it still does not work. As I checked, alpha.histogram() does not return related items.

Can you explain how do you connect your sensor to the Raspberry Pi?
What kind of update OS procedure did you use?
What version of the python are you using? Have the OS update touched python?

I connect my sensor using GPIO based on pin assignment in
http://py-opc.readthedocs.io/en/latest/
Nothing changes during the time (the sensor worked well a few weeks ago).
Today I have update the OS using simple update command in terminal.
and finally I use python 3.4 (same as before).

Maybe the OS update modified GPIO interface somehow, what is the update command did you use?
Did you do usual unplug and replug, power off and on?

For BME280, I had to install Adafruit package I part of this was about installing GPIO frimware as follows:
sudo apt-get update
sudo apt-get install build-essential python-pip python-dev python-smbus git
git clone https://github.com/adafruit/Adafruit_Python_GPIO.git
cd Adafruit_Python_GPIO
sudo python setup.py install

Is it possible that these installations made changes in my PM2.5 driver?

Maybe.
I need to know more about how you setup your Raspberry Pi hardware-wise. In other words, did you connect BME280 to GPIOs as the same time as alphasense?

Yes. I use a prototyping P1 extension board connected on top of my Raspberry pi board. My alphasense sensor uses "GND, 5.0v,MOSI,MISO,CLK and CS0" pins and BME280 uses "SDA,SCL,3.3v and GND" pins on the extension board. This boards only uses first 26 pins of standard GPIO pins of Raspberry pi 3.

Yes, at the same time, BME280 was attached to the extension board, but it did not work. Today I used BME280 using Adafruit and after that I saw that Alphasense did not work.

I am sorry but I did not understand your first sentence, due to many commas there. What I wanted to know are the hardware changes between your alphasense working to not working.
For example, did your alphasense work when connected directly to GPIOs without extension board?

The hardware did not change. BME280 was attached to the board, but I did not setting up it. Today I set it up and after that Alphasense did not work!

Okay, your recent software changes may have messed things a bit up for you.
@dhhagan should know more about GPIOs than I do, let wait for him to pop by.

It is interesting that I turned off the Raspberry pi and after a while I turned it on again. Then I test the alphasense in Python terminal, it worked well. After that, I added one second sleep time before reading alpasens.histgram() and now my code run perfectly!!!
It seems Raspberry Pi has some performance problems and it could not act well in all situations.
Thank you @DancingQuanta for your kindly support.

Hey @H60gh have you tried setting the firmware version manually to see if that is the only call that has an issue? If that doesn't work, could you provide the entire code snippet you're using (for ex., what is spi?) as well as a simple wiring diagram? I have seen several people run into issues when there is not enough current to drive the OPC-N2, which would happen if using the 5V GPIO pin rather than a separate power supply.

Ahh, yea I've seen people also experience that. Could you open a new issue that suggests adding that note to the documentation? It may help others in the future. I'm not sure of the root cause, but I assume it has something to do with the i2c timing/i.e. not letting the fall complete before the next rise.

Hi @dhhagan
Thanks for the reply. Ok, I'll open a new issue.


WIP: Type checker

Fixes #50
This took around two evenings of work, but there it is.
Currently not integrated in build system and generators because everything is going to break horribly in that case.
A quick design overview:
There are 3 main components to this:

Checked AST
Type table
Scope table

Checked AST
The checked AST is quite similar to the regular parsed AST with a few additions:

All expressions have a result type attached to them
Types in all structures are mandatory and inferred if needed. For functions that don't have a return type, void is used
Variables and types are referenced by IDs in their respective tables

Type table
The type table is actually a tree structure that stores and deduplicates types. Each type is given a unique Id value which can then be used to reference it anywhere in the type checker. The Type structure stores some metadata about the type like size and alignment (necessary for QBE/LLVM codegen) and a Repr (standing for representation) which is what "type" usually refers  to.
Basic types are:

any (any type can be converted to it, currently has no defined size; TODO)
int
string
bool
void

The base types are inserted into the type table during its construction and their IDs are available as fields of the types::Table struct.
Those can be combined into composite types:

T[n] - fixed arrays
T[] - dynamic arrays
struct{...} - structures

There's also a special named type, which just relays information about its inner type but can be referred to by name. This is currently only used for structs, but can allow for more generic type aliases like C's typedef or Rust's type a = b;.
Though, I'm currently not very happy with the design of named types in particular right now
Scope table
Scope table is a tree-like structure, implemented similarly to type table, that tracks scopes and their relations, as well as variables in those scopes. A scope is established by either a function declaration, a loop or a block statement. Scopes also store a loop flag which makes tracking loops for break/continue much easier.
A scope stores mappings of variables to their type IDs, it could possibly also store additional information for codegen.
Random comments

The somewhat messy parser-level type inferencer is no longer needed
scopes can be removed from parsed AST as they are no longer necessary
let x with neither type nor value is really strange and has no well-defined type for the variable. This should probably be removed
Why is the left side of ast::Expression::ArrayAccess a String instead of Expression? Something like a.b[1] should be allowed
capacity field of ast::Expression::Array seems to be completely redundant
ast::Expression::FieldAccess should use a String for the field being accessed, unwrapping the Variable expression is a bit strange
Should + operator be defined on strings as concatenation? This is used feature in tests and examples, and my current type checker only allows + to be used on integers
Can the assignment binary operations +=, -=, *= and /= be turned into statements? If not, they should probably return something then? Currently my type checker assumes they return void

Where to go from here

Add special properties for function scopes, namely the return type. Currently the type checker won't complain about return "one" from a function that returns an int
A major feature missing from the type checker are methods, they need to be implemented. This could be made a bit easier with function types
Add types for functions which can simplify call checker as well as paving the way for call-by-reference
Type hints for array types. Currently an empty array literal doesn't work because the type checker doesn't tell apart let x: int[] = [] and let x: string[] = [] when checking the [] expression
Implement proper size, alignment and offset calculation for structs (prerequisite for QBE and LLVM generators)
Add a system for casts to signal implicit conversions (such as passing a value to a parameter with any type) to code generators
Fix up error messages and add more context (such as affected types)
Implement a better system for error reporting. Currently any stages after parsing have no access to position information, would be useful to add that to the syntax tree as well as returning something more meaningful than String for errors (hints should also fit here)
Make naming consistent across parsed and checked AST
Refactor code generation to use the checked AST

Oh wow, nice work!
This check phase is quite complex, but I assume there's no way around a second AST structure if we want proper typing.
(Please don't forget to add tests and fix up the dev docs afterwards, but I'm sure you're aware of that)

The type checker finally supports all language features! I also went through a few rounds of refactoring and I think the new internal API turned out to be a bit better. There are some improvements for parser/AST here, which are independent of the type checker. Most notable change is disallowing uninitialized bindings without an explicit type (let x).
I also removed the int restricting for +, it can also concatenate strings now. I'm not sure what the exact semantics should be, but I ended up allowing string + (int|string|bool). The code also turned out to be a bit convoluted, I feel like it's better to move concatenation into a separate operator.
A few last things to be solved:

There needs to be a way of declaring a prototype for a function so that the type checker knows types of its arguments and return type
Handle duplicate objects in a better way. Currently I expect a lot of things to break if something is declared twice
Figure out the semantics of any for non-JS backends

My next goal is going to be adding tests for all this, refactoring error handling (it's inconsistent and lacks useful context), and trying to integrate it with the build system and generators


Not saving empty strings / values for relationships forms / NestedForm

Laravel Version: 1.6.15
PHP Version: 7.3.3
Laravel-admin: 5.8.21

Description:
When saving relationship forms in laravel-admin and trying to reset the value to something empty. Example: an empty string. The value is not saved.
The value is converted to an a null value by the following middleware (Http/kernal.php)  \Illuminate\Foundation\Http\Middleware\ConvertEmptyStringsToNull::class
and null values are begin ignored when saving relationships forms.
Disabling this middleware makes it work but a has the side effect that fields that can not handle empty values like integer throw an error with saving. This can be fixed by disable the mysql strict mode. Although it would be nice if empty values are not ignored by the relationship formsl
Steps To Reproduce:

create relationship form:

    $form->hasMany('somerelation', function (Form\NestedForm $form) {
         $form->text('title');
    });

fill the title field of the relationship with a text string
try removing the value (empty value)
saving the empty value is ignores

Problem not fixed..

Problem not fixed..

I tried to find bug in Encore\Admin\Form\Field\HasMany + Encore\Admin\Form
Spent two hours, but nothing =(
@z-song maybe you can find?

appreciate anyone can help me with this issue :(


[Hydro]  Fix hydro storage time label

Description
The labels in the "Time" column of the "Hydro Storage" TS screen which are daily and not hourly data with 365 lines which in the screen below should therefore go from 01/07 to 30/06 and not from 01/07 00:00 to 16/07 04:00
Screenshots

Environment

[x] Production
[x] Staging

##Multiple matrices "Time" column need to be fixed
###TODO

[ ] The "Hydro storage" "Run of river", "Reservoir levels", "Water values" and "Energy credit" matrices should be Daily instead of Hourly (currently)
Daily power:

[ ] Change the matrix first column (without name) + 2 rows with label "Generating power" and "Pumping power

Standard credit:

[ ] The Standard credit matrix in the Energy Credits tab should be Daily

Water values:

[ ] The name of the cols should be 0%-n% instead of TS-n


Allow hasChanged() without parameter

Description
Overload Entity hasChanged() to support a check if any attributes have been changed.
Checklist:

[X] Securely signed commits
[X] Component(s) with PHPdocs
[x] Unit testing, with >80% coverage
[X] User guide updated
[X] Conforms to style guide

Ref https://github.com/codeigniter4/CodeIgniter4/pull/2002


Rewards Link in Wallet is Inactive after Activating and Dismissing

DESCRIPTION:
On the Wallet page there is a prompt at the top asking the user to create an account to receive rewards. Clicking this the first time works, but if the user dismisses the window which appears, the rewards link no longer works until a restart.

REPRO STEPS:

Install and Launch LBRY 0.15.6 on Android 9
Click 'Use LBRY'
Navigate to 'Menu > Wallet'
Click 'Skip Account'
Click the blue banner at the top
Click 'Not Interested'
Click the blue banner at the top

Results: Nothing happens
Expected: Account creation prompt appears

ENVIRONMENT:

Galaxy S5
Android 9
LBRY 0.15.6

MEDIA:

INTERNAL USE:

DEFINITION OF DONE:

[ ]  Tested against acceptance criteria
[ ] Tested against the assumptions of the user story
[ ] The project builds without errors
[ ] Unit tests are written and passing
[ ] Tests on devices/browsers listed in the issue have passed
[ ] QA performed & issues resolved
[ ] Refactoring completed
[ ] Any configuration or build changes documented
[ ] Documentation updated
[ ] Peer Code Review performed

LBRY ADDRESS:
bZSqrVdpxt5KJdn2eGMUzT9Jn3gEiRet7b
<EMAIL_ADDRESS>

Thank you for your report. This is fixed in https://github.com/lbryio/lbry-android/commit/c6a6ea0445d3ea1856a102f8bbc500ed4b7860ff and will be available in the next release.

Fix Confirmed 0.15.8


Hideout management skill doesn't provide bonuses for Air filtering unit

General information:
Project issue is for:
SPT 3.6.1
Expected result:
Hideout management skill should provide bonuses according to it's level for Air filtering unit
Actual result:
Hideout management skill doesn't provide bonuses to Air filtering unit
How to reproduce:

Build Air filtering unit
Level up Hideout management skill
Look at bonuses which provides Air filtering unit

Here is video demonstration: https://youtu.be/yMtfCstDqew

Originally written by Armanello

Pretty sure this is a client issue, I don't believe the server applies any skill bonus to the area bonuses.
Library seems to work fine, and that's a similar "SkillGroupLevelingBoost" bonus.
Probably has something to do with the fact that it's the only bonus that isn't passive, as well as the only one that is tied to production.

Originally written by gasmo

I've looked into the code and can see the consumption bonus is taken into account already:
https://dev.sp-tarkov.com/SPT-AKI/Server/src/branch/<IP_ADDRESS>/project/src/helpers/HideoutHelper.ts#L808

Originally written by chomp

I've looked into the code and can see the consumption bonus is taken into account already:
https://dev.sp-tarkov.com/SPT-AKI/Server/src/branch/<IP_ADDRESS>/project/src/helpers/HideoutHelper.ts#L808

It should provide bonus not only for consumption, it also should provide bonus for leveling up physical skills

Originally written by Armanello

I agree with @gasmo this is also like this on live

Originally written by CZPZ

Air filter XP bonus does not benefit from Hideout Management skill on live (at least in all resources I've seen), this is working as intended by BSG. Recommend closing this issue.

Originally written by gasmo


how can I change the cwd of notebook

Does this issue occur when all extensions are disabled?: Yes

版本: 1.67.2 (system setup)
提交: c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5
日期: 2022-05-17T18:15:52.058Z
Electron: 17.4.1
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Steps to Reproduce:
I'm using Jupyter notebook running python.
unlike python file, we can run py file with current workspacefolder as cwd, no matter where the py file is
but, when we use notebook to run python script, the cwd of py env is the folder of the ipynb file. if we move the ipynb file to another folder/subfolder, the cwd will change.
so how can we using notebook with python as runing python file.
we just want to storage my ipynb file everywhere in a single workspace and have only one top-cwd

Not really sure what you are trying to achieve (maybe an example would help) but you can also set the working directory for notebooks using the jupyter.notebookFileRoot configuration setting. So create a .vscode folder with a settings.json file containing the aforementioned setting to specifiy a fixed notebook working directory. If you open that folder with VS Code you can run any notebook with that fixed working directory independent of the notebook file location. Of course that setting can also be global but it would be better to provide that together with your actual workspace.

@jackthepanisher thanks you 👍
it works as expected
"jupyter.notebookFileRoot": "${workspaceFolder}"


properties aren't all added to element.

For example:
   { xmlns: 'http://www.w3.org/2000/svg',
     'xmlns:xlink': 'http://www.w3.org/1999/xlink',
     width: '500',
     height: '272.82',
     viewBox: '0,3.574,100,54.564' },

viewBox and xmlns properties are lost

Use svg rather than h
See https://github.com/Matt-Esch/virtual-dom/blob/master/virtual-hyperscript/test/svg.js for an example.

Wow thanks very must this just solved my problem. Not sure if this closes the issue but its a simple fix.


How can hide the measurement data text

Hi everyone,
When we draw some measurement in one slide I think we will confuse because we have lots of line and text.
I think we just show the data text when we hover mouse into the measurement, normally whe hide this text.
So how can I make the style, hide the text, and show it when hover mouse on?

Look at the tool's render method. This logic fires on each render, which is happening in sync with the screen's draw. We often use information in the tool's state, options, and configuration to influence how the tool and it's info are rendered.
If you look at an annotation tool with pointNearTool implemented, this returns true when a tool is more or less being hovered.
You could use these two things to help inform when/if you should render different elements.
We have had more formal talks about introducing a "hovered" and "selected" states for annotation tools, but without outside resources, these changes are unlikely to move forward.


Adds Dead Letter Queue support for Queue

This is my first contribution, so I appreciate feedbacks.
This PR fixes #480 by adding deadLetterQueue parameter to the Queue class and updates the examples.

Oh nice. Let me ask Frank to review.

Thanks @brunocleite.
Rename the prop to dlq to keep it short.


Create Northern Virginia Community College

please add the Northern Virginia Community College student accounts to be able to have free educational access to PyCharm for classes.

@safwan2283 Northern I am sorry, I have to close the request without merging, because you made a mistake in a request and did not specify any filepath. Please ensure that you are familiar with this repository rules located at the bottom of this page and make a new correct request. Thank you for your understanding!