Multiple conflicting required requirements

related to https://github.com/datactive/bigbang/issues/576
There are multiple files/places in the repository that could be treated as the required requirements for the bigbang package.

https://github.com/datactive/bigbang/blob/main/environment.yml
https://github.com/datactive/bigbang/blob/main/requirements.txt
https://github.com/datactive/bigbang/blob/3bbb7358eb97d5ca5f94170e7217ca383200957e/setup.py#L23

Ideally there should be only place and with the least amount of requirements. Like jupyter shouldn't be a requirement as there is nothing in the codebase of the bigbang library that requires jupyter to work. The notebooks requires jupyter but that shouldn't be part of bigbang-as-a-package requirements.

I went through all the imports inside the codebase and bigbang seems to depends on these libraries:
 numpy
 networkx
 requests
 pandas
 bs4
 chardet
 python-dateutil
 html2text
 pytz
 tqdm
 pyyaml
 certifi
 levenshtein
 ietfdata

There are other dependencies:
 python-docx
 GitPython
 nbformat
 nbconvert

which could be turned into optional dependencies as they are used at very specific places. This can make the initial install quicker for users. I think the docx and git ones are pretty bulky installs.

Hi @MridulS Thanks so much for all of this....
One question. Historically, we've supported both pip and conda installation paths:
https://bigbang-py.readthedocs.io/en/latest/installation.html
I think the main reason why we have both an environment.yml and requirements.txt file is because we wanted to support both installation paths. At the time when this was set up (five years ago or so), there wasn't a way to declare requirements for both systems simultaneously (or else I didn't know it).
Is there a way to consolidate the requirements into one configuration file that would work with both conda and pip? If so, we should switch to whatever that is.

I agree with what you are saying about trimming the dependencies for the python package to what is necessary for the library.
Things have been awkwardly designed because for 90% of users thus far, the repository has been used like this:

Clone the repo and create a local installation
Run the scripts to pull data from a remote source like IETF
Open the notebooks, load the data into memory, and play around with scipy commands to make nice plots

So the pypi package has been secondary to this hackier use case.
I'm quite glad we are moving to a different, more standard paradigm!
I do think we may need to have some documentation that supports the older use case. Which maybe just means loading optional dependencies so that people have jupyter installed.
What do you think?

One question. Historically, we've supported both pip and conda installation paths:
https://bigbang-py.readthedocs.io/en/latest/installation.html

We can have a conda installation path available just by having a clean pip install. I will submit https://github.com/MridulS/staged-recipes/tree/bigbangpy_on_conda_forge to conda-forge once we make a new release on pypi. Then there is a bot setup which will auto release new conda packages built by using the pip package. So we only need to worry about the pip packages.

I do think we may need to have some documentation that supports the older use case. Which maybe just means loading optional dependencies so that people have jupyter installed.
What do you think?

Yes definitely, with a lean pip/conda install-able bigbang-py package we should be able to create good documentation for different workflows. The optional dependencies bits can be documented (we can also just add them to the normal deps list if required)

Oh, I see. We wouldn't be using conda for the development instalaltion, and we would have clean development and 'user' use cases. That's much better. Great. Thanks.


gnushogi: fix build

Description of changes

Fix gnushogi build silently succeeding with empty output
Example build: https://hydra.nixos.org/build/219348389/nixlog/1

Fixes #211433
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Please mark broken on darwin

this derivation will be built:
  /nix/store/ynkdj7r87lfw7ysim3d9kird0pxnxpv2-gnushogi-1.4.2.drv
this path will be fetched (0.37 MiB download, 0.37 MiB unpacked):
  /nix/store/2a9cf6lmjbmkgyzkxdn3lpmjnlnm59r4-gnushogi-1.4.2.tar.gz
copying path '/nix/store/2a9cf6lmjbmkgyzkxdn3lpmjnlnm59r4-gnushogi-1.4.2.tar.gz' from 'https://cache.nixos.org'...
building '/nix/store/ynkdj7r87lfw7ysim3d9kird0pxnxpv2-gnushogi-1.4.2.drv'...
unpacking sources
unpacking source archive /nix/store/2a9cf6lmjbmkgyzkxdn3lpmjnlnm59r4-gnushogi-1.4.2.tar.gz
source root is gnushogi-1.4.2
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file gnushogi-1.4.2/win32/Makefile
patching sources
configuring
configure flags: --prefix=/nix/store/y3197j3amzgca4549780w9vdv4i58idw-gnushogi-1.4.2
configure: C compiler
checking for gcc... clang
checking whether the C compiler works... no
configure: error: in `/private/tmp/nix-build-gnushogi-1.4.2.drv-0/gnushogi-1.4.2':
configure: error: C compiler cannot create executables
See `config.log' for more details
error: builder for '/nix/store/ynkdj7r87lfw7ysim3d9kird0pxnxpv2-gnushogi-1.4.2.drv' failed with exit code 77;


Merge release/1.55 into master

Hi Pablo,
there are two additional commits. That looks a bit fishy. Is that intended?

Updated with a force push, because we've erased some PR from 1.55 release.

Hi Pablo,
there are two additional commits. That looks a bit fishy. Is that intended?

In a GVC with Henning we agreed that is intended

Hi Pablo,
there are two additional commits. That looks a bit fishy. Is that intended?

For reference: There was a problem with pierric's commit. But having additional commits in here is normal and there was nothing wrong in that regard with the PR.
Looks good!


SQL Tracker Store credentials

core=0.14.0a1
nlu= 0.15.0a4:
3.6.5:
windows10
Issue: hello rasa friend i have a issue for how to work the tracker store
i´ll see what this version of rasa core supports SQL database and i don´t know how to connect
anyone know, i´ll put al the tracker store credentials in the endpoints.yml but i have no answers

Thanks for raising this issue, @wochinge  will get back to you about it soon.

Can you share your endpoints.yml with us?

tracker_store:     type: SQL     dialect: "sqlite"  # the dialect used to interact with the db     url: "localhost"  # (optional) host of the sql db     db: "rasa.db"  # path to your db     username:  # username used for authentication     password:  # password used for authentication
thanks for answering, the other issue i have is: there is a posibilty to extract entities for this method and what are the step to follow
regards

If you have another issue, please create another issue. If it's a question please check out our forum: https://forum.rasa.com.
What exactly is your error message?

i not have error message, the bot run normally the only thing is the tracker don´t  save the
flow that should keep,
so i´ll suposse what i put something wrong in the endpoints.yml

Should be clear now with the new Rasa 1.0 docs


Add Support for AAAA Records

I have just added ipv6 support in https://github.com/coreos/alb-ingress-controller and would like to be able to automate adding AAAA records to Route 53, and other providers in the future.
I can see in the Route 53 we currently set the record to be an A record using the RRTypeA
https://github.com/kubernetes-incubator/external-dns/blob/2319a44fc1242e2598cc3e53898e76b9f45b3c52/provider/aws.go#L379
However the AWS SDK also includes the type RRTypeAaaa
https://github.com/aws/aws-sdk-go/blob/b72688f15ec0b32551a50dceeeb2bd53f2e0d690/service/route53/api.go#L14804
Could we just add a new annotation for ipv6 support, and in the isAWSLoadBalancer check, we check if the annotation is set, and then also add/modify an AAAA record. Or do we add the record type as a new parameter of the newChange function, do the annotation check there, and then manage AAAA and A records separately. What about ingress controllers that already have annotations that add ipv6 support to those, for instance alb.ingress.kubernetes.io/ip-address-type for the https://github.com/coreos/alb-ingress-controller ingress controller.
I'm happy to create a pull request with these changes, just want to understand the approach that would like to be made here.

Does anybody found a solution for IPv6 support or working on one?


Add launch script

This is a rough draft of the launch script concept. It follows the pattern used by the postBuild script, except uses the ENTRYPOINT directive.
closes #196

What do you think of implementing the idea from https://github.com/jupyter/repo2docker/issues/196#issuecomment-364078438?
We also need to test this PR with the various ways kubespawner allows people to set the command that is executed. I remember it was a bit hairy last time we discussed this because there are several similar words that all mean slightly different things for docker and kubernetes :-/

@betatim - I've just pushed another commit here. This follows @yuvipanda's suggestion for how this could be implemented. I've tested locally and it actually works.

We also need to test this PR with the various ways kubespawner allows people to set the command that is executed.

What is the best way to do this? I haven't quite sorted out the unit test approach in this repo yet.

Can you make travis happy? https://travis-ci.org/jupyter/repo2docker/jobs/411604989#L912 :-)

I can. I was waiting until we had come to some agreement on the approach but if there are not high-level concerns, I will wrap this up.

ah fair enough - if @minrk is happy w/ the approach (maybe @yuvipanda has thoughts too?) we can move forward!

I think the general approach is good. However we need to adjust it so the existing tests pass. Seems like at least some of this is due to handling multiple arguments and such.

Just changing the launch script path to using the home directory seems to have fixed all the failing tests. Nice call @minrk. This is ready for final review.

@jhamman you're at the pangeo thin in Colorado, yeah? Maybe you can chat w/ @yuvipanda about this while you're both there!

@minrk do you imagine people doing malicious things with this somehow?


When pausing and starting again, the final track is only the last clip

I see this was supposed to be addressed in #17 but I've just installed the npm package, but I am still running into this problem. The jsfiddle provided in the demo also seems to have this issue: https://jsfiddle.net/grishkovelli/rb1anxyj/.
I get an error thrown here: https://github.com/grishkovelli/vue-audio-recorder/blob/master/src/lib/recorder.js#L52

thnx a lot. fixed


Example using slick codegen - not for merge to master

Example using slick codegen

This looks nice!
Do you know whether we can customize the types at all? We're currently converting the SQL Timestamp type to java.time.Instant in the FileTable type: https://github.com/nationalarchives/tdr-prototype-sangria/blob/8779cd89f9e8bfdd334216787bd6930a6f3f0656/core/src/main/scala/uk/gov/nationalarchives/tdr/api/core/db/dao/FileDao.scala#L69-L72
Can we do something similar in the code-generated version, or will we need to handle Timestamp values in the DAO?

I'm going to close this as it has been around for a while. The branch is still there if anyone wants to look at this.


Deleted duplicate Ishika cards also added mine.

Deleted duplicate Ishika cards also added mine.

Congrats @ProtyayMnd50 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

Star this repository. ⭐

SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .

Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.

Thanks for merging my PR  @nikhil25803
My Profile:
https://www.clueless.tech/profile/admin/96626338
or
https://www.clueless.tech/profile/96626338
Looking forward to work more with Clueless-Community!


Dataperf V1

The dataperf create interface looks like this, which is the most noticeable change to the UI:

There seems to be some philosophical differences between our two teams about what needs to be done here. The differences are about if we should use a MultiLabelClassifier vs N Binary Classifiers in the data performance challenge. Although theoretically MultiLabelClassification and N-binary classifiers should produce the same results they have different implications on labeling. Creating datasets for each binary classifier for a specific label will cause the labeler to determine high quality positive and negative samples for a given labeled dataset. Dataset creation for a multilabel classifier is tailored for the multilabel problem where the positive and negative samples are chosen to minimize the models uncertainty of samples for the given task (multi-label prediction). We would need to converge on our philosophical views here because on our end a labeler would not be able to label N distinct datasets for N-binary classifiers and extend it to your code unless we have the same samples in each dataset so that we would be able to combine the labels across each sample to create a multi-label dataset. To highlight this point let's assume we have 2 labels CAT and DOG, our dataset for CAT has {Sample1: positive_sample, Sample2: negative_sample} and dataset DOG has {Sample3: positive_sample, Sample4: negative_sample} there will be no way to combine these datasets since it is unclear if the CAT sample exists in the DOG dataset.
I've listed below some of the Pros and Cons of going the N-binary classification route
Pros

DataPerf challenge evaluates selection strategies of an easier task (binary classification)
The full multilabel dataset and selection needs to be updated if we want to evaluate on a new label whereas in binary classification we would just need to create 1 new dataset.
Cons
Code to handle N-binary classifiers is more complex

Can you describe how you tested this code change? It will make it easier to test some modifications on my branch.

Can you describe how you tested this code change? It will make it easier to test some modifications on my branch.

It is a lot of work, but you are welcome to get it set up. Follow the installation instructions for this repo. You also need to set up your own AWS. After you've done this, I can help you get the evaluation server running (we don't have documentation for that yet).


child + adult version: reasoning

for children we plan to automatically record audio when they are asked why they made a certain choice in the dilemma. This recording can be stopped with a button.
for adults: they can type their response.
-> can both functions be on the same slide? or should we rather make two versions (audio + type / children + adults)?

Needs further discussion...


Add primary key to GameUser table.

The altar table statement is:
ALTER TABLE GameUser ADD PRIMARY KEY (gameID, userID);
On a local test setup with 1000 users and 70000 games this reduces the game api query on a user page from 760ms to 5ms, and on the recent_games page from 2 seconds to 100ms. Currently the recent_games request on the live server typically takes between 2.5-3.5 seconds.

Thank you!


Slot dp_input and text-input

Describe the bug
When I use slot dp_input to customize styles of date picker the value doesn't change.
To Reproduce
Steps to reproduce the behavior:
1: configurated datepicker with options:
{
  format: "dd.MM.yyyy",
  openMenu: true,
}

2: The input value was changed when openMenu option is false
Expected behavior
The problem is that when the user types to input in the slot, the value doesn't change and can't validate so I added onInput event.
Screenshots
<Datepicker
  v-model="personalData.birthday"
  text-input
  :text-input-options="textInputOptions"
  :format="dateFormat"
  placeholder=" "
  model-type="dd.MM.yyyy"
  :enable-time-picker="false"
  :auto-apply="true"
  :clearable="false"
 >

<template #dp-input="{ value, onInput }">
  <input type="text" @input="onInput($event)" :value="value" />
  <label>{{ $t("personal.birthday") }}</label>
</template>

</Datepicker>

@Icoder9699 i'm experiencing the same problem. Did you manage to solve it?

@Icoder9699 @prostoleo If you want to type in the input field, set text-input prop.


[WIP] Release 2.9.1

This release is scheduled for Monday. I'm aiming to set this up now so that it's an easy release to push on Monday.
@shazow, what are the odds that we can get a urllib3 patch release 1.13.1 containing the fix for shazow/urllib3#761 by Monday? I'd owe you lots of :custard: if we could get it! :heart:

Note: please don't merge this until we're ready to release on Monday! We may land other patches between now and then, and we'll want to make sure the changelog is updated!
For those who are interested: the reason we're enforcing a delay between 2.9.0 and 2.9.1 is to try to land as many regression fixes as possible in a single release, rather than rapidly releasing several versions as issues become apparent to us.

@Lukasa are you thinking about making an exception to our release document in this case?

@sigmavirus24 Yeah, good question, but I think I am, given that the urllib3 release would itself be a patch release. Any concerns there? @ralphbean @eriol?

@Lukasa Could do. Could try to sneak in SOCKS support too, if you wanna.
Also I noticed some of your changelist includes an update note to the urllib3 version, some don't. Dunno if that's intentional.

@shazow I'd rather leave SOCKS out for now: makes 1.13.1 very clearly a simple bugfix release.
Yeah, the missing changelist notes are in error, we should try to fix it.

Sounds good, I'll push out v1.13.1 before monday (maybe today).

@Lukasa yeah, if it's just a couple small bug-fixes, that's fine by me. I think we've been bitten in the past by urllib3 having a lot more than just bug fixes when we pulled it in.

:+1: here.  I just finished packaging 2.9.0.  Bumping to 2.9.1/1.13.1 shouldn't be an issue.  Thanks!

@ralphbean Frankly I don't recommend releasing 2.9.0, it had enough nasty bugs that going straight to 2.9.1 is going to be the better approach.

:+1: from me. I will skip 2.9.0 since 2.9.1 is going to be released soon, thanks!

urllib3 v1.13.1 is live.

Frankly I don't recommend releasing 2.9.0, it had enough nasty bugs that going straight to 2.9.1 is going to be the better approach.

Acknowledged.  I attached a comment to let people know on the 1.9.0 Fedora updates.

\o/ Thanks @shazow!

@Lukasa is this still a WIP? I believe you wanted to cut this today

Heh, was just waiting for you. No longer a WIP, should be good to go.

:sparkles: :cake: :sparkles:
:sparkler: :shipit:


[Docs]: Using the new mstest SDK project

Page(s)
Getting started with MSTest & playwright is getting easier
in the page https://playwright.dev/dotnet/docs/intro when using MSTest.
Description
see https://devblogs.microsoft.com/dotnet/introducing-mstest-34/#playwright
@Evangelink, @MarcoRossignoli running dotnet new mstest creates a regular SDK project, it's not clear how to create a new project using the new MSTest SDK using the dotnet cli

The new template for MSTest SDK project is included in net9.0 dotnet SDK. Try installing the preview, please.

The template will not yet use the global.json for defining MSTest.Sdk version but we are working on it at the moment to be ready before the launch.

We improved .NET SDK for the support of global.json and we are working with VS team to have it also working there.

https://github.com/dotnet/test-templates/pull/325 introduced the templates nunit-playwright and mstest-playwright


sys.exit on kaggle.json is bad

Hard exiting when the kaggle.json file doesn't exist is just bad. We only need the file during submit.
An error should be raised during submit not import/initialization!
I can submit a PR if that helps?

PR's are always welcome.  I do plan to improve error handling soon.

ValueErrors are now raised instead as of 1.4.0.


color legend doesn't account for fillOpacity

Color legends show the color with opacity: 1. Thus the legend might look quite different than the plot, in case you set the fillOpacity < 1

True, but it's not always what you'd want anyway. However, it might be useful to support an optional constant fillOpacity option in the legend options:
Plot.dot(penguins, { fill: "island", fillOpacity: 0.2 })
  .plot()
  .legend("color", { fillOpacity: 0.2 })

Yes, we should support an opacity option for the color legend. (We already support a similar color option for the opacity legend!)


Added support for reading service account from JSON string env variable.

This is a convenient way to not have to store files on disk separate from a .env file.
Adds a new env var FCM_SERVICE_ACCOUNT_KEY (minus the _PATH).
This option is also in google-cloud-kit

It is now available since 2.10.0 tag 🥳
@Andrewangeta thank you very much for the contribution! ❤

It is now available since 2.10.0 tag 🥳
@Andrewangeta thank you very much for the contribution! ❤


Error when querying liquidityPools from Uniswap V3 Polygon

I'm seeing the below error when querying liquidityPools from the Uniswap V3 Polygon Subgraph.
I can make the same query from tokens and swaps without any issue. I can also query the first 100 liquidityPools with no issue (although if I try this and paginate by filtering for id_gt the last id in the previous query,  I eventually get the same error again at around the 10th query).
Subgraph: https://thegraph.com/hosted-service/subgraph/messari/uniswap-v3-polygon
Query; {liquidityPools(first: 1000) { id }}
Output: TypeError: Network request failed at E.s.onerror (https://thegraph.com/hosted-service/_next/static/chunks/pages/_app-11330c6ef94b9304.js:17:898478)
Am I doing something wrong or is there an issue with the subgraph?

Hi @bmeo, appreciate the feedback! This is an error on The Graph's side. You should raise it either in The Graph's official Discord or https://github.com/graphprotocol/graph-node

@this-username-is-taken thanks I've raised an issue on their github: https://github.com/graphprotocol/graph-node/issues/3872
Will close this issue now.


fix compile error when EMC_MULTIPLE_CALLBACKS 1

Simple fix to #include <list> when using multiple callbacks with EMC_MULTIPLE_CALLBACKS set to 1

Oh, was this forgotten?
Question though: any specific reason to reorder the includes?

to include config.h(config.h is included in MqttClient.h) before checking EMC_MULTIPLE_CALLBACKS , so if it is 1 compiler will include  and


Best practice for develop "Like and Dislike" buttons using Callback Queries

Hi Robin.
I'm just wondering what is the best practice for develop a bot for getting like and dislike feedback from users?
It's important that this bot can manage a huge number of requests for avoiding Error code 429, Error: Too many requests.

Dear webiox,
Please close the issue (since it's not caused by the library) and contact https://telegram.me/BotSupport, they will probably be able to help you with your challenge.
Kind regards,
Martijn Verbakel


Additional options to the --defined-by argument

The --defined-by argument provides two options:
all:   every entity that has any properties other than rdf:type will be annotated.
strict: only owl:Class, owl:ObjectProperty, owl:DatatypeProperty, owl:AnnotationProperty and owl:Thing entities will be annotated.
I'm proposing:
(1) Add owl:NamedIndividual to strict.
(2) Provide a real all option where every entity is annotated. This is to support, say, ontology scaffolding where terms have not been fleshed out. Perhaps current all could be renamed full or something similar.

@bpelakh These are straightforward fixes, but I wanted to get your take before submitting a PR. Was there some reason why you excluded NamedIndividual to the list of types in strict?

@bpelakh These are straightforward fixes, but I wanted to get your take before submitting a PR. Was there some reason why you excluded NamedIndividual to the list of types in strict?

Unfortunately I don't remember the exact cause for the exclusion, but I suspect it had to do with auto generated Protege import stubs

Fixed in PR #113.


autocomplete dropdown will affect the rest of the display items

If i have an autocomplete menu, and open it up, it will push down all the other DIVs below it.
I would have expected the menu items that show up to be on their own fixed layer and not affect the rest of the display
closed

open:

This is a regression introduced after Popover.


[Feature] Support function roundBankers

Search before asking

[X] I had searched in the issues and found no similar issues.

Description
ClickHouse supports function roundBankers but Doris doesn't support now
If you are interested in it, you could leave a comment for me.
Use case
No response
Related issues
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

Can I try it?

Can I try it?

Sure. And feel free to discuss with me if you have any problems

Can I try it?

Sure. And feel free to discuss with me if you have any problems

Thanks, please assign to me

Can I try it?

Sure. And feel free to discuss with me if you have any problems

Thanks, please assign to me

Done. Look forward to your PR :)


Vite create color without constrast

Describe the bug
When creating a new vite project, some frameworks are invisible depending on the terminal (powershell hides preact, for example). I know it's cool to have a different color for each one, but it can be hard for people with color blindness or with low constrast monitors.
Reproduction
just run a create vite command
System Info
Not necessary

Used Package Manager
yarn
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Since everyone's terminal could have different themes, we can't please everyone with the right contrast. If you have issues viewing the colors, you can try configuring your terminal to auto-adjust them with custom themes. Or you can also run the command as NODE_DISABLE_COLORS=1 npm init vite


add kernel experiment (#10820)

Porting my addition of the experiment for ZMQ from ds/rawKernel into master. Experiment needs to be in master so that it gets downloaded and cached. Then I can actually use the experiment in the ds/rawKernel branch.

[ ] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[ ] Title summarizes what is changing.
[ ] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).
[ ] The wiki is updated with any design decisions/details.

This is just a port of the experiment that I added in ds/rawKernel to master. Same issue as @rchiodo was hitting in that it needs to be in master so that I can actually use / reference it.

Codecov Report

Merging #11013 into master will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master   #11013      +/-   ##
==========================================
- Coverage   60.77%   60.76%   -0.02%
==========================================
  Files         582      582
  Lines       31774    31777       +3
  Branches     4522     4523       +1
==========================================
- Hits        19312    19308       -4
- Misses      11476    11481       +5
- Partials      986      988       +2

Impacted Files
Coverage Δ

src/client/common/experimentGroups.ts
100.00% <100.00%> (ø)

src/datascience-ui/react-common/arePathsSame.ts
75.00% <0.00%> (-12.50%)
:arrow_down:

src/client/common/utils/platform.ts
64.70% <0.00%> (-11.77%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0.00%> (-2.23%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
76.56% <0.00%> (-1.57%)
:arrow_down:

...client/datascience/kernel-launcher/kernelFinder.ts
75.70% <0.00%> (-0.94%)
:arrow_down:

src/client/common/process/proc.ts
14.49% <0.00%> (-0.73%)
:arrow_down:

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 b0877ca...62427eb. Read the comment docs.

Only fail is windows timeout, so pushing.


Create a higher level method to extract data attributes (with a defaultValue)

Follow-up from https://github.com/dreditor/dreditor/pull/165#discussion_r13028805:

This should probably use the more modern dataset with fallbacks, like:
id: parseInt(this.dataset && this.dataset.uid || this.getAttribute('data-uid') || 0, 10),

Upon further thought, I think it'd be nice to have something like (off the top of my head, probably not complete):
Dreditor.getData = function (element, key, defaultValue) {
  element = element instanceof jQuery ? element.first().get(0) : element;
  var value = element.dataset && element.dataset[key] || element.getAttribute('data-' + key) || null;
  defaultValue = defaultValue || null;
  switch(typeof defaultValue) {
    case 'number':
      // Determine whether value is an integer or float.
      // @see http://stackoverflow.com/a/3886106/1226717
      var float = parseFloat(defaultValue);
      var int = parseInt(defaultValue, 10);
      value = float == int && !isNaN(defaultValue) ? parseInt(value, 10) : parseFloat(value);
      break;
  }
  return value || defaultValue;
};

Dreditor is being decommissioned due to the lack of availability of current maintainers and the fact that Drupal.org is becoming more feature rich at a much faster rate than Dreditor itself now.
This decision was also partially made due to the amount of work (complete rewrite) it would take to create an "official" Firefox extension (#256).
If you already have the extension installed, it should continue working for a while until, inevitably,  the markup on Drupal.org changes. It will no longer be updated.
We understand that many of you love this extension, as do we. This isn't the end, in fact, it's a much brighter beginning. All the things we love about Dreditor can, and should, be moved into Drupal.org natively.
For more information, please follow: https://www.drupal.org/node/2779729

This issue was moved to dreditor/dreditor#23


.min.css files not minified

In my opinion a file should be minified if it ends with .min.css.

@Virinum Can you assign me that little task?


Added wishlist icon and fixed position of logo

Description!!
Fixed the position of Logo and added wishlist icon at the nav bar
Screenshots!!
Before:

After:

Why these changes made!!
To enhance the UI of the page , improve customer engagement and experience!!

@JyothiPriya5 Please follow the guidelines #90

I have raised an issue but didn't mention in the pill request if I mention will it be accepted?


Core || Analysis Adjoint Wavelet Transform

Translate the adjoint of the analysis wavelet transform from s2let (c) to s2wav (base python).
Difficulty:

High

Background:

The wavelet transform can be performed as either analysis or synthesis, both with corresponding adjoint operators. Here we consider the adjoint of the analysis transform which should map from wavelet coefficients to a signal on the sphere (kind of).

S2let File to translate:

can be found here ignore the function on this line as it is no longer necessary.

S2Wav File location:

should be put in the main package directory here

Notes:

These functions will require some helper functions from ssht and so3 You should be able to access the necessary functions from the python versions of these packages for the time being. Look here for SSHT and here for so3 functions.

It is important that these transforms support both real and complex fields, however these two implementations are extremely similar and should (in the end) be refactored into a single function. Hence the sub-issues will be as follows:

[ ] Implement real transform
[ ] Implement complex transform
[ ] Refactor real + complex transform into a single function call (i.e. use parameter dict as a switch)


unsupported methods fails violently

I noticed that some methods are not available. In particular:

eth_chainId
personal_sign
eth_signTypedData_v3

While I understand that not all methods are implemented (chainId is a shame, as it shouldn't be that hard to implement) ... my biggest issue is that this fails violently. I'm can't even manage to catch it! Is that a known issue?

Check our wrapper here incase it solves the issues:
https://github.com/LibertyPie/Wallet-Provider

Check our wrapper here incase it solves the issues:
https://github.com/LibertyPie/Wallet-Provider

Hmm... not entirely sure what you mean by failing violently, but personal_sign and eth_signTypedData_v3 should work. We will add eth_chainId, but in the mean time you should be able to use net_version (which isn't exactly the same thing, but close enough)

Hmm... not entirely sure what you mean by failing violently, but personal_sign and eth_signTypedData_v3 should work. We will add eth_chainId, but in the mean time you should be able to use net_version (which isn't exactly the same thing, but close enough)

hi. sorry for the belated response. we are marking stale issues closed for now. please open a new one if needed. thanks.


Rename octa to okta

Merge this after new deploy of MOSI to prod.

I would assume the precondition for this pull request is fulfilled. Please validate and merge, documentation should match code.


Issue with time_intervals

I think my AlertManager is having an issue, or I didn't understand well how time intervals are supposed to work.
What did you do?
I struggled a lot to have my AlertManager sending alerts (mail and webhook) only during working hours, because I don't want my colleagues or myself to be spammed at night, on weekends, or even on public holidays.
I defined several time intervals so AlertManager would be active only between 08:30 and 18:30, from Monday to Friday. However, it never worked properly. Each time I gave it a try after some fixes to my configuration, there were two possibilities:

or AlertManager was always firing, with no care of my time intervals (really always).
or it would never fire, always saying notification was not sent because the route was within mute time, when it was obviously not supposed to be.

I thought long about all the possibilities that made this behavior occur. I finally thought, "Maybe fields are exclusive, which means that if I define weekdays and times into the same time interval, that can't work because it is either checking time or weekday, but can't check both at once." I found that functioning silly, but it would all explain why I am struggling so much after trying so many different things.
I checked your documentation again, and it goes against my idea; it is written: "All fields are lists. Within each non-empty list, at least one element must be satisfied to match the field. If a field is left unspecified, any value will match the field. For an instant of time to match a complete time interval, all fields must match." Which means I am supposed to define several fields into a time interval because it will check if every field is matching, right? However, I gave it a try because it fit so well with the issue I was facing.
I tried those 2 configurations on Friday at 15:00:
First one:
  - name: 'offhours'
    time_intervals:
      - times :
        - start_time: 00:00
          end_time: 08:30
      - location: 'Europe/Paris'

Then, the second one:
  - name: 'offhours'
    time_intervals:
      - times :
        - start_time: 00:00
          end_time: 08:30
      - weekdays: ['Monday', 'Tuesday', 'Wednesday', 'Thursday', 'Friday']
      - location: 'Europe/Paris'

Those time intervals are used on all routes except the root one, as expected.
Here is an example of a route:
...........

  routes:

    ############## ROUTES SPECIALES SSL (PAS DE REPETITION) ##############

    - receiver: 'x'
      matchers:
        - severity=~critical|error|warning
        - type=ssl
      # on redéfinit pour ne recevoir l'alerte qu'une seule fois

      mute_time_intervals:
        - offhours

      continue: true

    - receiver: 'xx'
      matchers:
        - type=ssl
      # l'alerte ne sera pas reçue par d'autres receveurs

      mute_time_intervals:
        - offhours

      continue: false

     #################### ROUTES PAR DEFAUT INFRA ########################

    - receiver: 'x'

      matchers:
        - destinataire=infra
        - severity=~critical|error|warning

      mute_time_intervals:
        - offhours
      # définit si l'alerte est transférée aux receveurs suivants ou non
      continue: true

..........

What did you expect to see?
I expected alerts to be sent in both cases. (at Friday 15:00)
What did you see instead? Under which circumstances?
Alerts were fired only in the first case. AlertManager thinks he is within mute time in the second one but not the first one.
With the second definition of 'offhours', logs show :
May 26 15:21:38 xxxxxxxx alertmanager[15532]: ts=2023-05-26T13:21:38.577Z caller=notify.go:826 level=debug component=dispatcher msg="Notifications not sent, route is within mute time"
I don't think I'm doing something wrong. Please correct me if I do, but it seems to be a bug.
Environment

System information:

Linux 5.10.0-0.deb10.16-cloud-amd64 x86_64

Alertmanager version:
alertmanager, version 0.25.0 (branch: HEAD, revision: 258fab7cdd551f2cf251ed0348f0ad7289aee789)
build user:       root@abe866dd5717
build date:       20221222-14:51:36
go version:       go1.19.4
platform:         linux/amd64

Prometheus version:

prometheus, version 2.43.0+stringlabels (branch: HEAD, revision: d8ec24a7c76ab90a2332893fe12fa34e2d6e5570)
build user:       root@d7c52397d929
build date:       20230321-12:13:15
go version:       go1.19.7
platform:         linux/amd64
tags:             netgo,builtinassets,stringlabels

I add that when I ask my system "What day is it ?", it gives me the correct answer.
#date +%A Friday

Your time interval syntax is incorrect. location is not a list item, it is a key. So, your first example should instead be:
time_intervals:
- name: offhours
  time_intervals:
  - times:
    - start_time: "00:00"
      end_time: "08:30"
    location: Europe/Paris

You should have seen an error logged when trying to parse your config, since it would have failed syntax validation.

Hello, thanks for your response !
I used amtool everytime I tried a new config, and it succeeded every time, I never had syntax error due to this.
However, I will try that and update my post.

Can you verify that the config has been ingested as expected with amtool config show ?

@ThomasWattez If I apply the time interval definition that you originally described, it loads without error, but it's obvious what the problem is. The relevant output from amtool config show:
time_intervals:
- name: offhours
  time_intervals:
  - times:
    - start_time: "00:00"
      end_time: "08:30"
  - location: Europe/Paris

Bear in mind that the time_intervals in Alertmanager are a bit confusing. There is the named time_interval (in this case "offhours"), and then within that there can be one or more time_intervals, which can be time ranges, weekdays, days of the month, months, or years - all with an optional timezone.
Your config has resulted two criteria within the "offhours" time_interval:

restrict the time range to 00:00 - 08:30 UTC (no timezone specified)
open-ended, no restrictions, but with Europe/Paris as the timezone.

Compare that to the subtly different:
time_intervals:
- name: offhours
  time_intervals:
  - times:
    - start_time: "00:00"
      end_time: "08:30"
    location: Europe/Paris

This now specifies one criteria for the "offhours" time_interval:

restrict the time range to 00:00 - 08:30 in the Europe/Paris timezone.

By extension, your second example will specify three criteria, and also definitely won't do what you expect:
- name: offhours
  time_intervals:
  - times:                                                    # <- first criterion
    - start_time: "00:00"
      end_time: "08:30"
  - weekdays: [monday, tuesday, wednesday, thursday, friday]  # <- second criterion
  - location: Europe/Paris                                    # <- third criterion

What you more likely want is:
- name: offhours
  time_intervals:
  - times:
    - start_time: "00:00"
      end_time: "08:30"
    weekdays: [monday, tuesday, wednesday, thursday, friday]
    location: Europe/Paris

Thanks a lot for your time and your knowledge man.
It was really clear and helpful.
It seems to work now ! :)
Indeed, documentation and time_intervals definition are really confusing.
I may let this open so prometheus' team can see that misunderstandings about this part will occur, because I don't think I'm the only one who struggled there.
It's a wonderful tool but informations are sometimes hard to find !
Thanks again, I wish you a good day. :)

You're most welcome. I'm glad it's now working as you intended.

i have a similar problem with time intervals. Tried using the https://prometheus.io/webtools/alerting/routing-tree-editor/ to parse it using { namespace="app-dev", label_team="TeamA"} as the label set, but it always routes to TeamC when i'd expect it to route to TeamE during office hours, and TeamC on the weekends.

global:
  resolve_timeout: 5m

route:
  receiver: default
  group_by:
  - alertname

  routes:

  - receiver: TeamA
    matchers:
    - label_team="TeamA"
    routes:
      - receiver: TeamC
        matchers:
        - namespace=~".+dev|.+uat"
        active_time_intervals:
        - weekends
      - receiver: TeamE
        matchers:
        - namespace=~".+dev|.+uat"
        active_time_intervals:
        - officehours

  - receiver: TeamB
    matchers:
    - label_team="TeamB"
    routes:
      - receiver: TeamD
        matchers:
        - namespace=~".+dev|.+uat"
        active_time_intervals:
        - weekends

receivers:
- name: default
- name: TeamA
- name: TeamB
- name: TeamC
- name: TeamD
- name: TeamE

time_intervals:

- name: weekends
  time_intervals:
  - weekdays: [saturday, sunday]
    location: Europe/London

- name: officehours
  time_intervals:
  - times:
    - start_time: "08:00"
      end_time: "20:00"
    weekdays: [monday, tuesday, wednesday, thursday, friday]
    location: Europe/London

I don't believe the routing tree editor has any concept of time intervals, since there is no way to supply the time at which you want it to simulate the routing decision.


[IOTDB-1261] add client csharp

Support IoTDB client for CSharp

Coverage increased (+0.2%) to 68.063% when pulling eaa75555504c10686676f985af5441fdb58179b7 on lausannel:master into 5c6d11bd7e3f4b5e842bd3a71b262be5692e2ad6 on apache:master.

Coverage increased (+0.1%) to 68.037% when pulling eaa7555 on lausannel:master into 5c6d11b on apache:master.

so, what does this actually mean

Add an auto lint tool and some build scripts for the PR?


added npm auto-update for cdnjs

prepare milligram for cdnjs

[Request] Add Milligram #6579

I'm not really sure but it would be better to have auto-update enabled on the main repository than just the library on cdnjs.
https://github.com/cdnjs/cdnjs/blob/milligram/documents/autoupdate.md

This section only need to be added on cdnjs's repo.

@PeterDaveHello thanks for the clarification, @cjpatoilo I'll close this now.

Thanks for your help @vkeusebio


accounts endpoint

endpoint: /middleware/accounts returns the list of all accounts sorted in desc order by amount of AE.

params: limit
e.g.: /middleware/accounts?limit=10


Add a script to set main company country

This will help in cases where you need to make sure it has a given chart of accounts, instead of the deafults l10n_us + l10n_generic_coa.

This fixed nothing.


License

We're working on a conda recipe for this package at https://github.com/conda-forge/staged-recipes/pull/823 and we're wondering what version of the BSD license specifically (2-Clause or 3-Clause) you're using?

@bryanhelmig would you know of any resources we could tap into for clarity on the which BSD license django-rest-hooks works best under?
For reference:
2-Clause BSD Language
3-Clause BSD Language
Notes:

Paraphrased: "A 3rd clause prohibits others from using the name of the project or its contributors to promote derived products without written consent."

3 clause is 💯 .

Thanks for the quick reply! To be sure: everyone agrees that the license field of the recipe can be updated to say BSD 3-Clause?

Sure - I don't mind multi-licensing this - MIT, ISC and BSD 3-clause. Pick which one you want. 👍


Loginfix

Fixes the issues with failed logins.  Not pretty but it is working for me.

@ngori you said in the issue over in the homebridge repo:

The code is ugly and also has my garage door implementation but obviously we need a pull request to get it out and tested.

I don't see the garage door implementation in your code, I was going to look at how you were doing that and add it to entire project. Do you have some other code that I can look at?


Vscode debbuger & ubunto, unabale to open ...

Hello everyone!
How can I easily fix it without reinstallation? as from googling it, its sound comlicated...
(After changing something in my code I dont see it anymore, but its not the first time I saw that, and I wonder if there is a quick fix for it)

Unable to open 'strcmp-avx2.S': Unable to read file 'vscode-remote://wsl+ubuntu-20.04/build/glibc-ZN95T4/glibc-2.31/sysdeps/x86_64/multiarch/strcmp-avx2.S' (Error: Unable to resolve non-existing file 'vscode-remote://wsl+ubuntu-20.04/build/glibc-ZN95T4/glibc-2.31/sysdeps/x86_64/multiarch/strcmp-avx2.S').

When trying to open whatever local folder or something it say its needing, it paste this:

Unable to write file 'vscode-remote://wsl+ubuntu-20.04/build/glibc-ZN95T4/glibc-2.31/sysdeps/x86_64/multiarch/strcmp-avx2.S' (NoPermissions (FileSystemError): Error: EACCES: permission denied, mkdir '/build')

TERMINAL:

[1] + Done                       "/bin/gdb" --interpreter=mi --tty=${DbgTerm} 0<"/tmp/Microsoft-MIEngine-In-mhnpm5ir.thc" 1>"/tmp/Microsoft-MIEngine-Out-zi4alcxx.sqx

Probably the same, but I didnt see there any simple way to solve it... thanks anyway, guess I will manage :)
The code is writing basic shell in C. (mark where's the prob with //~explaination~)
int main(void) {     char str[1024];     int waited0, stat0;      char *args[64]={};     int k=0;         while(k==0) {         printf("$ ");          fgets(str, 100, stdin);         strip(str);         parse (str, args);         char text[100];         sprintf(text,"/bin/%s",args[0]);         int i=0;         char *check[100]={};         while (args[i]!=NULL) {           check[i]=args[i];          i++; }         if (!strcmp(args[0],"exit")) //~~~here is the cause, when I change it from 'args' to 'check' it works good. ~~~          {           k=1;           waited0=wait(&stat0);           return 0;          }         else          do_user_input(check);         } }

I still don't understand what's the issue about... Please give steps and describe what happens and what is expected.

As I said its looks like a common prob, that I dont understand it exactly.
The steps as described, change args =>check and it somehow solve the prob...
Even though their definitions are almost the same...
Thanks for trying, I guess I will manage. All the best :)


regarding Instruction adherence

As mentioned in the paper section  (H) "Alignment of GPT-4 Evaluation and Human Evaluation",
I can not figure out in your code how did you performed the instruction adherence of the generated code.
Was this done manually or automatically?
If automatically,  Could you guide me in which file I can find this code.
Thanks

Hi @meaem, thank you for your interest in our work.
In the paper, we did both manual and automatic (GPT-4) evaluation to check the instruction adherence, and calculated the Cohen’s Kappa value between these two types of evaluation. This is done to validate the idea of using GPT as a convenient evaluator.
The code used for GPT evaluation in Appendix H is not included in this repo. We provided the prompt for GPT evaluation in Appendix C:
Given a code editing instruction, please determine if the output is an acceptable edited code response to the instruction
and input.

Hope this answers your question :)

Ok thank you for your reply
It 'd be a good idea to share this code, if you don't mind.
Regards


added environment-dev.yaml file

Summary of changes (Bug fix, feature, docs update, ...)
Added environment-dev.yaml file. Updated one documentation.

Please check if the PR fulfills these requirements

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

Codecov Report
Patch coverage: 65.18% and project coverage change: -0.62% :warning:

Comparison is base (e9bfa4f) 33.82% compared to head (f9f8bc9) 33.20%.
Report is 26 commits behind head on devel.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the GitHub App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##            devel     #769      +/-   ##
==========================================
- Coverage   33.82%   33.20%   -0.62%
==========================================
  Files         176      177       +1
  Lines       14014    13942      -72
==========================================
- Hits         4740     4630     -110
- Misses       9274     9312      +38

Files Changed
Coverage Δ

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

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

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

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

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

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

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

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

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

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

... and 16 more

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

demo output


non-ASCII request body characters may get corrupted in a non UTF-8 environment

def String serialize(ObjectMapperSerializationContext context) {
    def object = context.getObjectToSerialize()
    JsonEncoding jsonEncoding = getEncoding(context.getCharset())
    def mapper = createJackson2ObjectMapper(object.getClass(), context.getCharset())
    def stream = new ByteArrayOutputStream()
    JsonGenerator jsonGenerator = mapper.getJsonFactory().createJsonGenerator(stream, jsonEncoding)
    mapper.writeValue(jsonGenerator, object)
    return stream.toString()
}

Shown above is the serialize method from com.jayway.restassured.internal.mapping.Jackson2Mapper.  I'm experienceing an issue with it.  The problem arises if I have a non-ASCII character in the body.  I'm running with:
 RestAssured.config = new RestAssuredConfig().encoderConfig(new EncoderConfig("UTF-8","UTF-8"));

If I run a JUnit test in an enviroment where Charset.defaultCharset() returns UTF-8 all works correctly.  The same test when run in a Windows environment where Charset.defaultCharset() returns windows-1252 results in the issue.
Let's walk through the code with an attribute in the request body having a value of "Ñ" without the quotes (corresponding to the Unicode U+00D1 code point).  The "charset" in the context object (ObjectMapperSerializationContextImpl) on line 51 is UTF-8.  As such, "jsonEncoding" is UTF-8 based and after line 55 (mapper.writeValue()) is executed the stream byte array contains C3 91 for "Ñ". The two bytes C3 91 are the correct UTF-8 represenatation for "Ñ".  The issue arises in the next line - stream.toString().  Absent any charset specified to toString() (there is a variation of toString() which takes a charset name argument) the code to construct a String from a byte array will use Charset.defaultCharset() which in this case is windows-1252.  So it interprets C3 91 as being in windows-1252 encoding and not UTF-8 (which it is) and results in serialize() returning the following 2 Unicode characters: 00C3 and 2018 (conforming to https://en.wikipedia.org/wiki/Windows-1252).  These two characters (00C3 and 2018) are seen in the Controller method for that request body attribute.
In short "stream.toString()" needs to take the charset corresponding to the encoding used by mapper.writeValue - in my case since mapper.writeValue() writes the bytes out in UTF-8 stream.toString() should read it as UTF-8 and not use the default charset which may or may not be UTF-8.

Thanks for a detailed error report. I've tried taking charset into account when generating the string. I've now deployed a new snapshot that hopefully fixes this. Please try version 2.9.1-SNAPSHOT after having added the following Maven repository:
<repositories>
        <repository>
            <id>sonatype</id>
            <url>https://oss.sonatype.org/content/repositories/snapshots/</url>
            <snapshots />
        </repository>
</repositories>

Thanks, Johan, for taking care of this so promptly.  Your change addresses the problem. We're not allowed to consume SNAPSHOTs at our site.  When do you expect the next release to be?

Thanks for trying it out. Unfortunately I cannot tell when it's going to be released. I'd like to look into a few other issues as well and since I'm (mostly) working on RA on my spare time I cannot give any promises. I'll close this issue for now.


Update LandfireLatLongBox to produce expected map shapes from H, W

Investigate behavior of different operational locations
Summary
From the perspective of SimHarness, we would like to be able to train (and evaluate) on multiple operational locations in a given experiment. However, it is currently unclear how to configure the operational settings of the simfire config to ensure a resulting map size of shape (X, Y). When it comes to the RL training aspect, we must ensure that the map size is consistent across operational locations. The batches used for training are constructed from samples in the respective environments, and we have a predefined observation space that the arrays must "fit" into. For example, if train location A has fire map shape (121, 121) and train location B has fire map shape (129, 130), the current training code will fail.

We know that the main fields of importance are the latitude, longitude, height, and width.

If we fix the latitude and longitude, but change the height and width, the resulting map sizes will be different.
If we fix the height and width, but change the latitude and longitude, the resulting map sizes may differ. The important thing is we can't guarantee that fixed H,W results in same map size across operational locations.

Addressing 1. isn't urgent wrt SimHarness, as we want multiple operational locations, not multiple map sizes for the same location. However, I believe it is crucial to understand this behavior in order to eventually scale up the map sizes used for training (and evaluation).
Addressing 2. is crucial for training on multiple operational locations!
Steps to reproduce (using simfire v1.5.8)

Example: Vary height and width

Say we choose to use the following location from the BurnMD dataset:
BurnMDOperationalLocation(uid='Oregon_2020_242', latitude=42.68383321400006, longitude=-121.96376057099997)

To use this location, we can set the operational section in the simfire config with:
operational:
  seed:
  latitude: 42.68383321400006 # top left corner
  longitude: -121.96376057099997 # top left corner
  height: 5000
  width: 5000
  resolution: 30
  year: 2019

Using the above config, we get a resulting screen size of (121, 121) - get this via sim.fire_map.shape, sim.terrain.topo_layer.data.shape, sim.terrain.fuels.shape, etc.
Now change height and width from 5000 to 6000. The resulting screen size is (145, 145).

Example: Vary longitude and latitude

Say we choose to use the following 2 locations from the BurnMD dataset:
loc_A = BurnMDOperationalLocation(uid='Oregon_2020_242', latitude=42.68383321400006, longitude=-121.96376057099997)
loc_b = BurnMDOperationalLocation(uid='Wyoming_2019_Fishhawk', latitude=44.44007334400004, longitude=-109.89815622099997)

To use loc_A, we can set the operational section in the simfire config with:
operational:
  seed:
  latitude: 42.68383321400006 # top left corner
  longitude: -121.96376057099997 # top left corner
  height: 5000
  width: 5000
  resolution: 30
  year: 2019

Using the above config, we get a resulting screen size of (121, 121) - get this via sim.fire_map.shape, sim.terrain.topo_layer.data.shape, sim.terrain.fuels.shape, etc.
To use loc_B, we can set the operational section in the simfire config with:
operational:
  seed:
  latitude: 44.44007334400004 # top left corner
  longitude: -109.89815622099997 # top left corner
  height: 5000
  width: 5000
  resolution: 30
  year: 2019

Using the above config, we get a resulting screen size of (129, 130).

Possible fixes
From the perspective of SimHarness:
Option A: Take all the operational locations used for training (evaluation), and get the minimum fire map size across all training (evaluation) locations. Then, crop observations to the "smallest" size before returning from step() and reset(). I'm not sure if this is the best approach, but it's a start. We would need to be clever with the cropping strategy, ie. don't crop out the fire, etc.
Option B: We could try to "pad" the smaller maps to the size of the largest map. The tricky piece here is that we would want to set the values to "make sense" in the context of the fire map and respective data layers. But, if the total number of "padded" squares is small, this may not be a huge issue.

Solution proposed by @mdotter-mitre: Pad slightly more pixels to the height/width than is specified from LandFireLatLongBox and force a crop to the desired H, W. This ensures that SimFire users do not experience unexpected FireMap sizes.


Cort1237 master

@cort1237 I added you as a contributor to the main repository, so you should be able to directly push to this repository.

Oh awesome thanks. I have a WIP build with toypad colors that I'm gonna clean up and probably post in a week or so.


WIP: Create package middleware

Middleware should exist in its own pkg. And each middleware should have its own source file in middleware package.
- What I did

[x] Created pkg/middleware package directory
[x] Move all current middlewares to their own source files under that folder
[x] Move all current middleware functions into their own structs
[x] Each middleware implements prometheus metrics
[x] Removed WithMetrics
[x] Metrics are added globally through out the package.

- How I did it
N/A
- How to verify it
N/A

- Description for the CHANGELOG
Refactored middleware

Closes #4


Add pnpm as well

This would help me add a Bolt app in a Turbo repo.

This would help me add a Bolt app in a Turbo repo.

I have been using pnpm all along.
just remove yarn form the package.json , and then use pnpm


Vulnerability roundup 76: patch-2.7.6: 2 advisories

search, files

[ ] CVE-2018-1000156 (nixos-19.09)
[ ] CVE-2018-20969 (nixos-19.09)

Scanned versions: nixos-19.09: e34ac949d1b. May contain false positives.

CVE-2018-1000156: already patched but needs a name = "CVE-2018-1000156"; in the derivation.
CVE-2018-20969: https://git.savannah.gnu.org/cgit/patch.git/commit/?id=3fcd042d26d70856e826a42b5f93dc4854d80bf0

As it turns out these are already patched in 19.09 and master, just badly tagged (doesn't help that the same vuln has two CVEs...). I think 19.03 might also need the same fix, but I'm not sure why vulnix isn't complaining about it.


Support for Julia files

Hey, thank you 👏  can you please fix the failing tests?

Hey it looks like there is something wrong with consecutive comments, nice catch! I'll take a look at it and update soon 🙏

Closed and merged by #122
Thank you so much for your contribution and the critical bug (of multi-line) discovery 🏆

No problem, thank you so much for resolving!
On Fri, Nov 15, 2019 at 10:37 AM Gilad Peleg<EMAIL_ADDRESS>wrote:

Closed #121 https://github.com/pgilad/leasot/pull/121.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pgilad/leasot/pull/121?email_source=notifications&email_token=AG2KIL23GCSFFZUSFB4L4V3QT3UAHA5CNFSM4JNWF7MKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOU4NZFZQ#event-2803602150,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG2KIL4THONR5YDFHA3LJCLQT3UAHANCNFSM4JNWF7MA
.


iOS 9 processName unavailable

Hi there :)
Due to iOS 9 privacy policy changes + (NSString*) processName:(int) pid is not longer available.
You can see this log statement in debug:
ERROR: KSSysCtl.c (228): _Bool kssysctl_getProcessInfo(const int, struct kinfo_proc *const): Could not get the name for process 326: Operation not permitted

Setup: Xcode Version 7.0 beta 3 / OS Yosemiti 10.10.3

Hi,
Any update on this?

Hi,
Any update on this?

I removed parent process name in the latest commit, so this should no longer be a problem.


Packaging interface

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@e9bd31e). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #27   +/-   ##
=========================================
  Coverage          ?   37.80%
=========================================
  Files             ?        1
  Lines             ?      328
  Branches          ?        0
=========================================
  Hits              ?      124
  Misses            ?      169
  Partials          ?       35

Flag
Coverage Δ

unittests
37.80% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out 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 e9bd31e...a795a73. Read the comment docs.


The unique modifier is optional now

Parsing breaks because the unique modifier now isn't required:
type core.Recipe = {
  metadata: [Text],
  description: Text,
  ingredients: [Text],
  steps: [Step]
}

Glancing at the code, is the change required to fix this here?
https://github.com/kylegoetz/tree-sitter-unison/blob/master/grammar/type.js#L61
and if it's omitted it's a unique type?

Thanks for the catch! I knew there was discussion about defaulting to unique but didn't know it was official yet!
Yes, I will do a fix for this right now. Shouldn't be hard.

gonna lump in a couple other things and do a new version bump + deploy


Docusaurus Node/SSR could not render static page because of error: Minified React error #130 after upgrading to v2 beta 0

🐛 Bug Report
I'm trying to upgrade my site from 2.0.0-alpha.72 to 2.0.0-beta.0, and am getting a large number of errors like this one when running yarn build (which is docusaurus build):
Docusaurus Node/SSR could not render static page with path=/404.html because of error: Minified React error #130; visit https://reactjs.org/docs/error-decoder.html?invariant=130&args[]=undefined&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

Have you read the Contributing Guidelines on issues?
Yes
To Reproduce

Clone https://github.com/batect/batect.dev
Switch to branch renovate/docusaurus-monorepo (from https://github.com/batect/batect.dev/pull/252)
Run yarn build

Expected behavior
Site builds without error, or shows a clearer error message telling me what's wrong and how to fix it (or at least pointing me in the right direction).
Actual Behavior
yarn build fails with lots of errors like
Docusaurus Node/SSR could not render static page with path=/404.html because of error: Minified React error #130; visit https://reactjs.org/docs/error-decoder.html?invariant=130&args[]=undefined&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

A full build log can be seen in this GitHub Actions build.
yarn start launches the local dev version of the site without any errors.
Your Environment

Public source code: https://github.com/batect/batect.dev
Public site url: https://batect.dev
Docusaurus version used: 2.0.0-beta.0
Environment name and version (e.g. Chrome 78.0.3904.108, Node.js 10.17.0): Node.js 16.1.0
Operating system and version (desktop or mobile): macOS 11 and GitHub Actions Linux runner

Reproducible Demo

Clone https://github.com/batect/batect.dev
Switch to branch renovate/docusaurus-monorepo (from https://github.com/batect/batect.dev/pull/252)

Your site has webpack + babel customizations and also using internal code like fileLoaderUtils.
Regenerating the lockfile + del node modules + removing your extra babel configuration seems to fix it: https://github.com/batect/batect.dev/pull/256
We can't support you in such case and it is your responsibility to make sure your site customizations still work on upgrades. If you are not comfortable with that, you should not do such customizations in the first place and keep a simple Docusaurus site.

No worries, thanks for your help. Is there any way to get a more detailed error message from the build process so I can diagnose problems like these myself? There weren't any clues in that error message that I could see that could have led me towards checking the customisations I've added, and I wasn't getting an error when running in dev mode, as I mentioned in my original bug report.

I definitively get a console log error message when browsing your homepage.
Something like: exports is not defined
Which makes think of a potential transpilation issue related to Webpack or
babel.
We can't do anything to make those error messages more clear, and it
remains your responsability to debug those issues, even if it is time
consuming
Le jeu. 13 mai 2021 à 12:46, Charles Korn @.***> a
écrit :

No worries, thanks for your help. Is there any way to get a more detailed
error message from the build process so I can diagnose problems like these
myself? There weren't any clues in that error message that I could see that
could have led me towards checking the customisations I've added, and I
wasn't getting an error when running in dev mode, as I mentioned in my
original bug report.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/facebook/docusaurus/issues/4783#issuecomment-840477000,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFW6PSGEHGCSL4Z2DE2Z5TTNOUXPANCNFSM442GI6PA
.

I had to do this to fix the import/export issue
module.exports = {
  presets: [require.resolve('@docusaurus/core/lib/babel/preset')],
  plugins: ["@babel/plugin-transform-modules-commonjs"]
};


Not able to add custom CSS

Please ensure:

[X] The bug is caused by Refined GitHub. It doesn't happen if I disable the extension.
[X] The bug happens after clearing extension cache. The "Clear cache" button can be found at the bottom of the options page.

Example URLs
https://raw.githubusercontent.com/catppuccin/github/main/catppuccin.css
Extension version
22.1.18
Browser(s) used
Brave
Description
I've been using the Catppuccin CSS for a while, so I thought to change it out to another theme, but after changing it out I can't revert back to the previous one. Even after i reinstall the extension, the custom CSS is not being added into it. Here is the CSS I'm trying to add.
https://raw.githubusercontent.com/catppuccin/github/main/catppuccin.css
Video:
https://user-images.githubusercontent.com/70198692/151800857-84c0cd6d-ff03-4591-98e7-4e7dc765a0ae.mp4
Include in this issue:

[X] Screenshots/video/gif demonstrating the bug, if it’s visual
[ ] Console errors, if any

Can you try to leave the box before clicking the X?

Can you try to leave the box before clicking the X?

Is this what you're talking about?
https://user-images.githubusercontent.com/70198692/151805733-eaf4c9d2-c555-4f24-94ac-935a54158641.mp4

Did that help? If not can you try to click on another box within the popup?

Did that help? If not can you try to click on another box within the popup?

I've tried both and as soon as i close the dialogue box. The Custom CSS box becomes empty.

It's the CSS problem. I think it was changed or updated. I found the old CSS on another browser and it works just fine.

What CSS you input shouldn't matter. It would still be helpful if you can provide the problematic CSS so we can prevent situations like this.
This was the CSS i was trying to use:
https://raw.githubusercontent.com/catppuccin/github/main/catppuccin.css

Hi @SakethKanchi! I had the same problem, but removing the comments fixed it.

It works for me (Safari) but I suspect this is a space issue (e.g. you have too much cached content).
However since our style injection is delayed I'd advise using Stylus instead for this kind of overarching style changes.


github.com/mattn/go-sqlite3 requires CGo

cryptix: if the cgo based sqlite ever becomes a problem, there always is madscience: https://gitlab.com/cznic/sqlite
cryptix: o/ is a machine translated version of the C "dialect" in sqlite to pure Go. so it can be cross-compiled and used in environments where cgo is difficult or unavailable. possibly even wasm
statlz: if in wasm, would it run in the browser, but ... where would it store the data?
cryptx: not saying we need a wasm room but i disregarded sqlite before for other projects becasue cgo can be a pain
cryptix: like, if i wanted go-ssb-room on my small FreeBSD NAS, I need to compile for FreeBSD with a full C environment.. installing Go on the box isn't even enough then but also a full gcc/clang stdenv

The sqlite driver is the only CGo dependency we have, everything else can be cross-compiled.
I'm not jumping ship for the new, cgo-free version because I'm quite sure it still has some teething problems to go through but it's super impressive to see.
related links:

https://dave.cheney.net/2016/01/18/cgo-is-not-go
https://blog.golang.org/cgo
https://gitlab.com/cznic/sqlite
https://github.com/mattn/go-sqlite3

would folx be keen for arm64 cross-compilation? i'm keen to run butt.nz` on a Raspberry Pi. :pie:

Gitea are currently going for it in https://github.com/go-gitea/gitea/pull/20614 so I think it might be worth a look again!


[doc] Testplans are now generated as markdown.

Testplans are now rendered into a markdown document as oppose to a large HTML table.
These HTML tables were unwieldy when viewed from the site or as plain text. The original pipe output was not standard markdown.
New version of the GPIO Testplan:

Related to https://github.com/lowRISC/opentitan/issues/19078

That's much more readable, thanks Hugo

Now using setdefault

@hcallahan-lowrisc Fixed the md headings in testplan problem.

Added double newline after headings

Thanks @HU90m
Will these files be included with CMDGEN in the future?

Will these files be included with CMDGEN in the future?

That's the plan

Will these files be included with CMDGEN in the future?

That's the plan

Are we sure about this? Wouldn't that just be duplicating the content from the .hjson? I think that could be confusing.

Are we sure about this? Wouldn't that just be duplicating the content from the .hjson? I think that could be confusing.

Could this not be said about the register docs as well?

Are we sure about this? Wouldn't that just be duplicating the content from the .hjson? I think that could be confusing.

Could this not be said about the register docs as well?

Partly yes, but there is a transformation to add wavejson and covert fields to tables. With the testplans, there really isn't much being transformed.


PB850PS2 wont update sensors

System Health details
System Information

version
core-2023.11.1

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.11.6

os_name
Linux

os_version
6.1.59

arch
x86_64

timezone
America/Chicago

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

GitHub API Calls Remaining
4418

Installed Version
1.33.0

Stage
running

Available Repositories
1332

Downloaded Repositories
30

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 11.1

update_channel
stable

supervisor_version
supervisor-2023.10.1

agent_version
1.6.0

docker_version
24.0.6

disk_total
30.8 GB

disk_used
24.6 GB

healthy
true

supported
true

board
ova

supervisor_api
ok

version_api
ok

installed_addons
Terminal & SSH (9.7.1), File editor (5.6.0), Home Assistant Google Drive Backup (0.111.1), Duck DNS (1.15.0), NGINX Home Assistant SSL proxy (3.5.0), Vaultwarden (Bitwarden) (0.20.1), Studio Code Server (5.13.0), Z-Wave JS UI (3.0.1), Cloudflared (4.2.10)

keymaster

zwave_integration
zwave_js

network_status
on

Dashboards

dashboards
1

resources
15

views
5

mode
storage

Recorder

oldest_recorder_run
October 29, 2023 at 9:23 PM

current_recorder_run
November 6, 2023 at 12:48 PM

estimated_db_size
842.46 MiB

database_engine
sqlite

database_version
3.41.2

Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue
I have connected my Pitboss PB850PS2 via bluetooth and none of the sensor data is updated. Looks like there is a time out issue.
Reproduction steps
Connect Smoker
Turn On
Debug logs
This error originated from a custom integration.

Logger: homeassistant
Source: custom_components/pitboss/coordinator.py:58
Integration: PitBoss (documentation, issues)
First occurred: 12:50:29 PM (1 occurrences)
Last logged: 12:50:29 PM

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/bleak/backends/bluezdbus/client.py", line 209, in connect
    reply = await self._bus.call(
            ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/dbus_fast/aio/message_bus.py", line 399, in call
    await future
asyncio.exceptions.CancelledError

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

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/bleak_retry_connector/__init__.py", line 350, in establish_connection
    await client.connect(
  File "/usr/src/homeassistant/homeassistant/components/bluetooth/wrappers.py", line 292, in connect
    connected = await super().connect(**kwargs)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/bleak/__init__.py", line 605, in connect
    return await self._backend.connect(**kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/bleak/backends/bluezdbus/client.py", line 146, in connect
    async with async_timeout(timeout):
  File "/usr/local/lib/python3.11/asyncio/timeouts.py", line 111, in __aexit__
    raise TimeoutError from exc_val
TimeoutError

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

Traceback (most recent call last):
  File "/config/custom_components/pitboss/coordinator.py", line 58, in reset_device
    await self.api.start()
  File "/usr/local/lib/python3.11/site-packages/pytboss/api.py", line 143, in start
    await self._conn.connect()
  File "/usr/local/lib/python3.11/site-packages/pytboss/ble.py", line 87, in connect
    self._ble_client = await bleak_retry_connector.establish_connection(
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/bleak_retry_connector/__init__.py", line 374, in establish_connection
    _raise_if_needed(name, device.address, exc)
  File "/usr/local/lib/python3.11/site-packages/bleak_retry_connector/__init__.py", line 314, in _raise_if_needed
    raise BleakNotFoundError(msg) from exc
bleak_retry_connector.BleakNotFoundError: PBL-0297D6C - 4A:55:D4:67:84:66: Failed to connect after 4 attempt(s): TimeoutError

Diagnostics dump
No response

I can think of a few things that could cause this:

Your HA machine being too far away from your grill/smoker, causing too much latency in the bluetooth connection
The PitBoss firmware being super picky about connections it will accept
Bluetooth generally being a disaster and Linux APIs being even worse

Hopefully this is just (1), but (2) and (3) are unfortunately also common. ☹

Unfortunately I don't think it is number 1. My phone can connect just fine from the same spot via bluetooth.
Anyway I can help determine the other 2?

Fyi I figured this out. My bluetooth adapter was not compatible. Tried a different one, working now. Thank you!

Fyi I figured this out. My bluetooth adapter was not compatible. Tried a different one, working now. Thank you!

What adapter did you use that ended up working because I have similar issues

Fyi I figured this out. My bluetooth adapter was not compatible. Tried a different one, working now. Thank you!

What adapter did you use that ended up working because I have similar issues

I am using the Sena UD100-G03 (CSR8510A10). I just upgraded for better range and connectivity. I would highly suggest the following controllers, as they seem to work with home assistant far better. I tried the ESPHOME bluetooth proxy setup, it did not work as well.


【Not an issue】A quick start to use SAM2 interactively

I developed this simple tool since the release of SAM. I just naively integrated the newly released SAM2 into it. Feel free to give it a try or adapt it to your own application! Feel free to contribute and fix some bugs as well.

      first frame seg

      SAM2

Wow, So quick, Thanks for this. Really needed something like that.

@lujiazho How you make it work with CPU only? Can you use SAM-2 with only CPU?

@lujiazho How you make it work with CPU only? Can you use SAM-2 with only CPU?

Yes we can. Just use a machine with only CPU or manually set device='cpu'. Try it out on colab! It would be crazily slow though.

@lujiazho How you make it work with CPU only? Can you use SAM-2 with only CPU?

Yes we can. Just use a machine with only CPU or manually set device='cpu'. Try it out on colab! It would be crazily slow though.

can this tool eazily put any frame into the SAM2, or just only can use first frame?


Add FDO spec

Description
Adding FDO spec to openapi.json
Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Documentation update
[ ] Tests update

Checklist:

[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I run go fmt ./... to check that my code is properly formatted
[x] I run go vet ./... to check that my code is free of common Go style mistakes

Codecov Report

Merging #397 (fad48b0) into main (08321bc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #397   +/-   ##
=======================================
  Coverage   30.57%   30.57%
=======================================
  Files          32       32
  Lines        3159     3159
=======================================
  Hits          966      966
  Misses       2091     2091
  Partials      102      102

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 08321bc...fad48b0. Read the comment docs.


Support double-escaping and unbalanced quotes in sp_tables table_type

Description
It is suggested to relax table_type parameter handling in sp_tables procedure, so strings with technically invalid quotation are also accepted. See details in the linked issue.
Issues Resolved
#2404
Test Scenarios Covered
Existing test is updated with new input.
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 72.24%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
40404

Relevant Lines:
55930

💛  - Coveralls

@staticlibs can you please also commit this in 3_X_DEV.

Task: BABEL-4887

@staticlibs Since it is bug fix, its need to be cherry-picked in all branches. I have back-ported it in BABEL_2_X_DEV on behalf of you.


Add vstecb.txt

@SmrtMartin First stage of verification passed, official domain is vstecb.cz as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@SmrtMartin Pull request merged. Thank you!


Facebook Login

As we all know, we must provide a sign up and login option with Facebook. For this feature, Facebook's approval for our application might take some time. Is there anyone experienced with this? I think we should assign this to someone ASAP.

I don't know but I guess @mfatihm might have dealt with this before. If not I can ask people from outside of our team.

There are three different types of Facebook login according to how much data you gather. Initial one is enough for us since higher ones require corporate contract etc.
As far as I know, Facebook now requires Privacy Policy and Terms of Service for this feature.

First level which can be obtained without a review is sufficient for our app. Thus I'm closing this one.


Should be able to read elegant lte files

Addressing this with the parse_elegant branch.  Turns out that this is quite a bit of work...

Done


[cxx-interop] Make sure interop does not trigger TBD validation errors

rdar://83405989 / https://github.com/apple/swift/issues/56458

@swift-ci please smoke test

@swift-ci please test

@swift-ci please smoke test

@swift-ci please test

I think that's fine, but we should be mindful that it's not necessarily a fix, rather a workaround. We do have additional issues tracking this here:
https://github.com/apple/swift/issues/61453, but there are probably other cases.

@swift-ci please smoke test


get using http returns https url

Visiting http://httpbin.org/get will give a response specifying the url is (incorrectly) https.
{
  "args": {},
  "headers": {
    "Accept": "text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3",
    "Accept-Encoding": "gzip, deflate",
    "Accept-Language": "en-AU,en;q=0.9,en-US;q=0.8,ja;q=0.7",
    "Dnt": "1",
    "Host": "httpbin.org",
    "Upgrade-Insecure-Requests": "1",
    "User-Agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.86 Safari/537.36"
  },
  "origin":
  "url": "https://httpbin.org/get" <--- incorrect
}

Confirmed that this is happening for me, and caused a test failure. I assume there is some enforced redirect on the server occurring.

@kenneth-reitz Can this be marked as a bug?

https://github.com/postmanlabs/httpbin/issues/440
https://github.com/postmanlabs/httpbin/issues/489
https://github.com/postmanlabs/httpbin/issues/533
https://github.com/postmanlabs/httpbin/issues/536
https://github.com/postmanlabs/httpbin/issues/545

As an alternative this site offers both protocols:

http://postman-echo.com/get
https://postman-echo.com/get


Document interoperability with Jakarta Transactions

The spec needs to state what must happen if there is a JTA transaction already on the thread when a repository method is invoked so that users can know what to expect, both for resources types that are enlistable (these participate in the transaction) and for those which are not (these do not participate in the transaction).  The spec should also acknowledge that a failure running a repository method might cause a transaction to be marked as rollback-only (JPA does this in some cases) so that users are not surprised by that behavior.

Rebased to resolve merge conflict.


fix(css): better recovery mode

Better recovery mode, now we can parse
{}
a { color: red }

Why we need selectors as optional?

Recovery mode
Ideally recovery mode should be implement inside parser/selector/mod.rs, because we have two bad states - bad selector and bad simple block, now we use the same logic for both states, but due this we lose ability to recovery a lot of case (after merge this PR I will send a new with more cases)
Also our selector parser is greedy, but it is invalid (and wrong by spec), because we can't reuse parser for parsing selectors inside other things, for example

/* 'li, .test' is selector */
:nth-child(2n+1 of li,.test) {}

Also we will need it for :is()/:has()/etc pseudo-classes
Due greedy behavior we always faced Err(InvalidSelector) if the next token is not accepted by selector parser, we should refactor it on lazy, it means some function like parse_selectors and parse_complex_selector should return PResult<Option<SelectorList>>/PResult<Option<ComplexSelector>>, so it give ability to - reuse parser inside other things + good recovery mode
Yep, it can be slightly dirty right now, but it for future improvements :star:

Yes, it is invalid, I found better solution for this, I will send a PR


Add server-side raft encryption

We need to either encrypt all of raft, or at least the sensitive portions of it: secrets and the root key.
This should be done with an in-memory-only key (#1467).

@diogomonica @cyli Can we close this one?

@aluzzardi I think so, yes


Disconnect between States and Drives

Describe the bug
I stopped at our mailbox on the way home to check the mail, and note that the subsequent short drive from the mailbox to home is not shown in the Drives dashboard, but it does appear in the States dashboard.  Why should these two dashboards be inconsistent?
Relevant entries from the logs
You have to provide the logs of the teslamate container / application unless the bug is limited to Grafana only. To fetch the logs of the teslamte container run the following command: docker-compose logs teslamate
teslamate_1  | 11:33:54.613 [info] Sent 200 in 2ms
teslamate_1  | 17:28:19.946 [info] GET /
teslamate_1  | 17:28:19.949 [info] Sent 200 in 2ms
teslamate_1  | 17:28:22.827 [info] GET /
teslamate_1  | 17:28:22.829 [info] Sent 200 in 1ms
teslamate_1  | 17:28:24.039 car_id=1 [info] Start / :online
teslamate_1  | 17:30:41.756 [info] GET /
teslamate_1  | 17:30:41.758 [info] Sent 200 in 2ms
teslamate_1  | 17:33:13.950 [info] GET /
teslamate_1  | 17:33:13.953 [info] Sent 200 in 2ms
teslamate_1  | 17:33:17.135 car_id=1 [info] Driving / Start
teslamate_1  | 17:40:09.596 car_id=1 [info] Driving / Ended / 6 km – 7 min
teslamate_1  | 17:40:09.596 car_id=1 [info] Start / :online
teslamate_1  | 17:41:42.130 car_id=1 [info] Driving / Start
teslamate_1  | 17:42:02.602 [info] GET /
teslamate_1  | 17:42:02.605 [info] Sent 200 in 2ms
teslamate_1  | 17:42:49.536 car_id=1 [warn] Vehicle went offline while driving
teslamate_1  | 17:42:54.956 car_id=1 [info] Vehicle is back online
teslamate_1  | 17:42:56.664 car_id=1 [info] Driving / Ended / 0 km – 1 min
teslamate_1  | 17:42:56.664 car_id=1 [info] Start / :online
teslamate_1  | 17:43:54.771 [error] TeslaApi.Error / 504 – %{"error" => "upstream_timeout", "error_description" => "", "response" => nil}
teslamate_1  | 17:43:54.772 car_id=1 [warn] Error / upstream timeout
teslamate_1  | 17:53:47.705 car_id=1 [info] Suspending logging

Screenshots
Last drive in Drives is from Work to our mailbox.  The subsequent drive from the mailbox to Home is not shown:

States shows both drives:

Operating environment (please complete the following information):

OS: Ubuntu 19.10 via Docker
Version: v1.13.2

The drive dashboard only displays drives longer than one minute. I will consider removing this condition.

Thanks for the explanation.  I did not realize that short drives were not included in the Drive Dashboard by design.


posix timer values are truncated

Required information
Operating system:
on aarch64 targets like Raspberry PI
Compiler version:
E.g. GCC 9.3.0
Observed result or behaviour:
The Posix Timer is getting double values on the API which are then converted into int64_t internally. This conversion leads to a loss of data because the compiler will truncate the value. This can lead to abnormal behaviour when using small numbers like 1 nanoseconds.
Expected result or behaviour:
Remove the double literals from the posix timer API and expect only integer als time values. Then we avoid this constraint and have a clean calculation.
Conditions where it occurred / Performed steps:
Try to start a timer with 1 nanosecond waiting time. It will no execute because the time is internally set to zero. This disarms the timer and it is not proceeding.

I can confirm. But first lost some time my Pi before finding this issue...

@dkroenke I think this related to the underlying long double of units::Duration. Should we rephrase this bug to fix the problem on its source?
@elfenpiff suggested in #337 to use
struct duration_t {
     uint64_t seconds;
     uint32_t nanoseconds;
};

as base instead of long double

@dkroenke I think this related to the underlying long double of units::Duration. Should we rephrase this bug to fix the problem on its source?
@elfenpiff suggested in #337 to use
struct duration_t {
     uint64_t seconds;
     uint32_t nanoseconds;
};

as base instead of long double


In simulation, have higher sampled forward projected volumes, to comply with nyquist sampling

Added in https://github.com/PolarizedLightFieldMicroscopy/forward-model/commit/4760065be89b8dbba94767afcb981a89042db0ac


#Add Code_Of_Conduct.md

closes #13
This PR has been raised to address the addition of code of conduct markdown file that caters to the users and engagers of the Uber-like Project repository.
Please review and action accordingly.
I also request to add level1 and gssoc-ext labels to this PR before merging!
Thank you!

Hey @KiranBaliga ! 👋
First off, I want to extend a huge thank you to all of you for your amazing contributions to this project! Your support and hard work mean a lot, and I truly appreciate everything you do. 🙏
I have a small favor to ask: if you think I’ve been helpful and supportive throughout your contributions, I would be honored if you could nominate me by filling out this form: Nominate me.
Your nomination would mean the world to me, and it’s a great way to help me continue supporting our awesome community. Thanks again for all the amazing work, and let's keep making great things happen! 🚀
Best,
Vishesh


Fix/challenges & rewards style

This PR fixes the safari visual bug in the countdown and adds a nowrap to 'pts' in rewards

challenges

before

after

rewards
With 390px width:

before

after

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


Add function to get Ostentus firmware version

It would be nice if we could read the Ostentus firmware version from the Zephyr side of things to check whether the display is running the latest firmware.

Agreed! We have this on the backlog but so far I haven't been able to get Ostentus to send data back to Zephyr over i2c. We're blocked until the low level issues in that repo can be ironed out.