[SPARK-36049][SQL] Remove IntervalUnit

What changes were proposed in this pull request?
Remove IntervalUnit
Why are the changes needed?
Clean code
Does this PR introduce any user-facing change?
No
How was this patch tested?
Not need

Test build #140794 has started for PR 33265 at commit bf2f4df.

Test build #140795 has started for PR 33265 at commit e70a954.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45307/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45308/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45307/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45307/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45308/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45308/

Test build #140794 has finished for PR 33265 at commit bf2f4df.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140794/

Test build #140795 has finished for PR 33265 at commit e70a954.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

FYI @MaxGekk

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140795/

Test build #140810 has started for PR 33265 at commit 01d346c.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45321/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45321/

@AngersZhuuuu Could you re-trigger GitHub actions, please.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45321/

Test build #140816 has started for PR 33265 at commit 5428d0c.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45327/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45327/

+1, LGTM. Merging to master/3.2.
Thank you, @AngersZhuuuu .

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45327/

Test build #140810 has finished for PR 33265 at commit 01d346c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140810/

Test build #140816 has finished for PR 33265 at commit 5428d0c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140816/


Codestral response is suddenly 4 times slower in Continue when compared to others

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS:Linux 6.9
- GPU: Nvidia 4090 Mobile (16GB VRAM)
- Provider: Ollama
- Continue: 0.8.43
- IDE: VSCode
- Model: Codestral
- config.json:

{
  "models": [
    {
      "title": "Codestral",
      "provider": "ollama",
      "model": "codestral:latest"
    }
  ],
  "customCommands": [
    {
      "name": "test",
      "prompt": "{{{ input }}}\n\nWrite a comprehensive set of unit tests for the selected code. It should setup, run tests that check for correctness including important edge cases, and teardown. Ensure that the tests are complete and sophisticated. Give the tests just as chat output, don't edit any file.",
      "description": "Write unit tests for highlighted code"
    }
  ],
  "tabAutocompleteModel": {
      "title": "Codestral",
      "provider": "ollama",
      "model": "codestral:latest"
  },
  "allowAnonymousTelemetry": false,
  "embeddingsProvider": {
    "provider": "ollama",
    "model": "nomic-embed-text"
  }
}

Description
Codestral response via ollama has suddenly become very slow with latest updates, its at least 4 times slower when compared to response timings from other  other apps like open-webui, curl are very fast. Other models like deepseek-coder-v2 is working fine in Continue.
To reproduce

Setup Continue to use Codestral for chat and tabautocomplete.
Watch the the logs for ollama e.g. in docker its docker logs --follow ollama
Open Continue chat and give any prompt.
Note response time in the ollama logs and notice the latency in the chat.
Give the same prompt in curl or in open-webui to Codestral and note the response time.

Log output
Note: Model is already loaded in VRAM before testing.
Ollama logs for Codestral via Continue
[GIN] 2024/07/30 - 10:45:28 | 200 |         1m33s |      <IP_ADDRESS> | POST     "/api/chat"

Ollama logs for Codestral via open-webui
[GIN] 2024/07/30 - 10:46:32 | 200 |  5.142411188s |      <IP_ADDRESS> | POST     "/api/chat"

Yep, can confirm this. Codestral is extremly slow (one word per ~20 seconds) in Continue, while it is blazing fast using ollama's direct console. A striking difference


Clicking on item in outline is not jumping right

Issue Type: Bug
When you have a big header file and you click on function declarations in the outline window, the jump to the code is not correct. I always have an offset of about 300 lines.
VS Code version: Code 1.45.1 (5763d909d5f12fe19f215cbfdd29a91c0fa9208a, 2020-05-14T08:27:35.169Z)
OS version: Windows_NT x64 10.0.17763

\extC++


Can't convert non-rectangular Python sequence to Tensor.

When using CodeSpace I'm getting the error:

How can this be fixed ?

Hi @bleissem
Just ran into a similar issue with working on the same base. Not sure the precise reasoning of why my fix works but I think it may be something to do with dimensionality differences between the first iterations and n+1 iterations.
I made the following three changes and it fixed my the first bug and two following bugs that occurred during my runtime. In this screenshot the line changes are on 319, 327, 329:

Let me if this doesn't fix your problem I'd be happy to help debug :)

Hi @bleissem ,
You are getting this error due to variable size of inputs which you are passing to tf.convert_to_tensor().
A simple code snippet is mentioned below to reproduce the error where you can observe the input I have chosen is of variable size.You can refer the gist attached here for observing the error
arg=tf.constant([[1.0, 2.0], [3.0]])
tf.convert_to_tensor(arg, dtype=tf.float32)

To overcome this you need to ensure the argument to be of fixed size (like rectangular shape).
Thanks!


Logstash reload config instead of stop/start

Modify dmon-controller to use SIGUP to restart logstash instead of stop/start. See:
https://www.elastic.co/guide/en/logstash/current/reloading-config.html

Update to new version of logstash

Fixed by #142


Add carto.on function

Fix for https://github.com/CartoDB/carto-vl/issues/594

I hope to have solved all the issues


feat: improve test coverage of CairoVM core functions

In the register update functions, here are some refactorings that can be done:
In updatePc, in the switch, expressions like this one:
https://github.com/keep-starknet-strange/cairo-zig/blob/de93e4e4b968214a9363b3aa8f171ecb3ce19fc5/src/vm/core.zig#L435
are too verbose and can be replaced by:
.Regular => { // Update the PC.

In updateAp, one configuration is not tested properly at the moment:

If instruction.ap_update is .Add, the configuration resulting in try self.run_context.ap.*.addMaybeRelocatableInplace(val); is not tested at the moment (only error.ApUpdateAddResUnconstrained is).

The following methods have no unit tests and all configurations must be tested here:

addOperands:
https://github.com/keep-starknet-strange/cairo-zig/blob/de93e4e4b968214a9363b3aa8f171ecb3ce19fc5/src/vm/core.zig#L659-L686
mulOperands:
https://github.com/keep-starknet-strange/cairo-zig/blob/de93e4e4b968214a9363b3aa8f171ecb3ce19fc5/src/vm/core.zig#L694-L707
subOperands:
https://github.com/keep-starknet-strange/cairo-zig/blob/de93e4e4b968214a9363b3aa8f171ecb3ce19fc5/src/vm/core.zig#L713-L728

Please, assign me this issue

Please, assign me this issue

@javimaravillas Just assigned


EOS token in the prepare_redpajama script

Hello,
I noticed that you didn't add eos token at the end of the examples in prepare_redpajama script. So, I tokenized my data without it. The model performs quite well in the pretraining, but off course I encountered a problem when I generate some text; which is I don't know when I should stop the generation.
I ran the prepare_redpajama script again with tokenizer.encode(.., eos=True), I found the pretrainig result is very bad, the model generates text that is not related at all to the prompt text, and the model never generate my eos token.
Also, I noticed that there is a difference between prepare_redpajama scripts in lit-llama and lit-parrot:
lit-llama:
builder = packed_dataset.PackedDatasetBuilder(
            outdir=destination_path,
            prefix=set_name,
            chunk_size=chunk_size,
            sep_token=tokenizer.bos_id,
            dtype="auto",
            vocab_size=tokenizer.vocab_size,
        )

the sep_token is bos.
lit-parrot:
builder = packed_dataset.PackedDatasetBuilder(
            outdir=destination_path,
            prefix=prefix,
            chunk_size=chunk_size,
            sep_token=tokenizer.eos_id,
            dtype="auto",
            vocab_size=tokenizer.vocab_size,
        )

the sep_token is eos.
Is this the cause of my problem?
I'm using a different tokenizer than LLama, so in my case should I follow lit-parrot approach?

not sure but thismay answer my question..

Hi @LamMoh1, a few points that make pre-training different from supervised fine-tuning:

the pre-training task is next token prediction on a single token, not a whole sequence; so you may need to predict a "e" or a "m" and that would be good
which means that you can just pack sequences one after the other, separated by EOS (we do separate them by EOS when we build the packed dataset), and compute the loss on the predicted token; in this case, you would also attend to extraneous sentences, but that may not be that important in practice

The format is similar to what used here: https://huggingface.co/blog/stackllama#supervised-fine-tuning
Note that for pre-training you can also not pack and instead add padding tokens for sequences that are shorter than the context length. This is more akin to what done conventionally, what option yields better results is still unclear AFAIK.

Thank you @lantiga, Your answer was clear and very helpful. I really appreciate that.


Navigation bar of ParentViewController is hiding when scroll

I have implemented this pagemenu on a controller. I have used view controller from storyboard. So when i scroll the navigation bar of parent view controller hides.
How to resolve this??

Same problem here, actually its works fine when you slide your fingers, but when tapped on each buttons, external views hiding behind the navigation bar.


Tags are automatically created - should we automatically return them?

All the upload endpoints upon successful upload automatically create a Tag that is returned in the response header Swarm-Tag.
Currently, we return only the reference but should we return the object instead with both values?

Originally this was the motivation behind returning object types with a reference property in it: so that it can be extended with information about other things, for example tags.
I can imagine some possible ways forward:

Change back to return response object including tags. This would be a breaking change and make the most common operation (to get the reference) a bit more complicated.
Add alternative functions that would return an object including the tags. That would pollute the Bee class and could introduce duplication making maintenance more difficult.
Add a flag that would change the behavior of the existing function to return an object with tags instead of a reference. Not sure this can be done easily with Typescript though.
Extend the Reference type (or whatever we return) with a tag property. This is a similar hack that we did with Data.

Extend the Reference type (or whatever we return) with a tag property. This is a similar hack that we did with Data.

I originally thought that it might not be possible since it is a string, but I just tried it and it is possible, but I would still avoid it as I think it will create more problems as for example console.log on such an object does not return the string etc.

Change back to return response object including tags. This would be a breaking change and make the most common operation (to get the reference) a bit more complicated.

Since we gonna have a breaking release we could maybe incorporate this change in this fashion?

I originally thought that it might not be possible since it is a string, but I just tried it and it is possible, but I would still avoid it as I think it will create more problems as for example console.log on such an object does not return the string etc.

I agree, it's a hack and it can be also confusing to explain it in the docs.

Change back to return response object including tags. This would be a breaking change and make the most common operation (to get the reference) a bit more complicated.

Since we gonna have a breaking release we could maybe incorporate this change in this fashion?

That seems the most straightforward option anyhow so let's do it.


iOS: How to make a "drop down list"?

On Android, I'm using https://www.npmjs.com/package/react-native-dropdown-android which works great.
On iOS I believe one uses a UITextField and sets the inputView value to a UIPickerView, but unfortunately the react-native TextInput doesn't have an inputView property.
We already have a PickerIOS component, it seems like a small step to somehow marry it to the TextInputcomponent. I'm sure almost all apps have a drop down list somewhere, so this should be a solved problem?
Is there a best practice already that I am not aware of to solve this issue?

I use <ListView> with a search bar. Search bar text change reduces the list.

That would be a great solution for lists with a lot of items, but for just quickly picking one of three options, I think having the PickerIOS in the Keyboard would be better.

@facebook-github-bot stack-overflow

@mbrochh I'm in the exact same situation. Did you find any solution?


Allow molo.* modules to be included when scaffolding an app.

We need it for other sites we do.

This is happening in https://github.com/praekelt/molo.profiles/

Changing this ticket to change the scaffolding to allow other modules to be included from the command line:
$ molo scaffold testapp --include=molo.profiles

This would make testing these molo.* packages significantly easier since we can easily create a project for them that includes them.

This PR is stuck until a new release of cookiecutter is out. The current version automatically does calls str() on whatever values are passed in via the extra_context variable. It's impossible to pass anything along that's not a string. I'm trying to pass along a list which ends up being unicode in the template context :disappointed:

unstuck & ready for review @miltontony

tests pass, coveralls just complaining because I mocked out more than I did before.

:+1:


CSV file's UTF8 BOM header is part of first field name

If a CSV file contains the UTF8 BOM header - EF BB BF as the first 3 bytes of the file, it will be read as part of the first field name by the CSV plugin, which causes failed to select the first field in the Query Editor.  This is assuming the first line of the csv file is the row header.
I could reproduce the issue on the latest plugin version 0.6.12, and Grafana version is on 8.5.4.

Hi @gnaish,
can you please provide a file that I can reproduce this with? Also if you can try it out with https://grafana.com/docs/plugins/yesoreyeram-infinity-datasource/latest/ and let us know how that goes would be awesome.

Thanks for the heads up and really appreciate for your efforts to develop this great plugin.
We will explore Infinity datasource plugin.


CLI GitHub Action

This PR adds a simple GitHub CI action from the price-calculator repo. The action will run the test and compile the codebase on each push

Any explanation for changes in the CLI layer?

Any explanation for changes in the CLI layer?

Well, the GitHub action was initially failing due to that parameter I removed: https://github.com/ardriveapp/ardrive-cli/actions/runs/1279875121
This commit made the action work: 19634cd
yarn test and self-testing still functioned fine after removal, so I asked Mati if removing that code would be fine in his commander API. He confirmed that it should be okay.
So I didn't really dig too much further into it after this workaround. Not the best explanation, and I'm still not sure why the tests were failing on GH and not for me locallly

I think this mocha env is re-using the same module instances. That's why it failed the 1st time.
I wonder if there's a way of running a test after another has run, because it fails just after parse() is called:
  CLICommand class
    ✔ Calls the library API function once when a command is set
    ✔ The library parses the given argv
    ✔ CLICommand won't allow to declare a command after parsed

  CommonContext class
    1) Actually reads the value from argv
    2) Boolean parameter false
    3) Boolean parameter true
    4) Array parameter
    ✔ Required parameter throws if missing

But I'm just fine with removing the _doneSettingCommands parameter, that's easier


docs: update supported file types table in partition documenation

Is your feature request related to a problem? Please describe.
The docs for partitioning include a table of supported file types. It looks like these are missing a number of extensions -> file types that we map against in auto partitioning, looking here.
Describe the solution you'd like
Documentation has a comprehensive list of file types supported.
Describe alternatives you've considered
NA
Additional context
NA

CC @amanda103


shorten room-names in UI fixing #135 #136 #139

Limiting the number of maximum lines of room-names on the Home page with
display: -webkit-box;
-webkit-line-clamp: /*linecount*/;
-webkit-box-orient: vertical;

should be considered

lets clamp 3 lines for now

@benawad Do you add the 3 lines when merging the PR or should I update the PR?

Can you add it to this pr

I hope we can fix it. :)

Ok we are now breaking long words into multiple lines and clamp them if they exceed 3 lines.


Formatter adding unnecessary blocks after traces

What Git revision are you using?
aiken v1.0.21-alpha+4b04517
What operating system are you using, and which version?
Ubuntu 22.04.2 LTS
Describe what the problem is?
When formatting a file with traces, the formatter adds unnecessary blocks wrapping whatever follows each trace. It seems to happen if there's more than one expression following the trace.
Before format:

After format:

What should be the expected behavior?
Unnecessary blocks should not be added upon format.

Thanks for reporting

Any idea when will this be released?

@jeffhappily we can probably make a new release asap


Allow . in param/result names via subscript.

This change allow folks to use . in parameter names (e.g. dev.mattmoor.my-param), and reference them via the subscript operator (e.g. params["dev.mattmoor.my-param"]) to avoid ambiguity introduced by the mixing of .s.
TEP: https://github.com/tektoncd/community/pull/503
/kind enhancement
/hold
Holding until the TEP is merged.
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Docs included if any changes are user facing
[ ] Tests included if any functionality added or changed
[ ] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Release notes block below has been filled in or deleted (only if no user facing changes)

Release Notes
Parameter and result names may now contain `.` and be referenced via the subscript operator (e.g. `$(params["foo.bar"])`

I'm sure there are some docs changes needed for this, although I'm not sure where those docs are, so if folks could provide pointers to any docs they think should be updated to reflect this change I'd appreciate it 🙏
/kind feature

I'm going to try and expand this with e2e test coverage as well, so not checking the test box yet.

Only failure seems to be outside of what I've modified, so let's see if it repro's.
/retest

I think docs/tasks.md may be the place to update for the docs ✅ , looking at that now.

Ok, I updated docs/tasks.md and also found docs/variables.md and added a couple rows to the pertinent tables with the new syntax.  The prior commit also tweaked a few of the e2e tests to exercise the subscript syntax, so I've checked off "docs" and "e2e".  I'm ofc happy to expand both of these if folks have specific pointers to things I missed.
For the commit message, I've left this unchecked as I am somewhat reluctant to fork the TEP PR as the source of truth (esp. before it is merged), but if folks have a good example, I'd be happy to circle back and update things to follow a strong precedent.

/unhold
The TEP has merged

/hold cancel
Maybe ? 😛

/unhold works for Knative prow, so either we have some snowflake or y'all are on a really old version 😅
Either way, thanks!

/unhold works for Knative prow, so either we have some snowflake or y'all are on a really old version
Either way, thanks!

Really old version it is 😉 😛 😅

/lgtm
nice!

(holding just a day or two or less to allow core team to review 👼🏼 )

Are we still waiting on anything here?

@dlorenc let's validate this in the upcoming API WG (today) 👼🏼

@vdemeester Just seeing this, but don't think it was discussed... 😅

@vdemeester Just seeing this, but don't think it was discussed...

That's a good point 😅
@tektoncd/core-maintainers last call for review, I'll check tomorrow morning before the release 😝

Just popped open my pending PR list and saw this (I'd forgotten about it 🤣 ), should we /hold cancel it?

/hold cancel
Indeed 😛

Late to the party but I'm excited to see this going in! Next release is gonna be a good one :D

That being said, one more process nit: technically the TEP should be "implementable" before the implementation gets merged (another opportunity for some automation to enforce?) - I added a comment to the TEP pr also https://github.com/tektoncd/community/pull/503/files#r709442151

I'm curious if there are examples of TEPs that have been merged as "proposed" and never been made "implementable"?  I'm sort of curious why this extra hop is in there, and whether it's been useful historically?
Happy to discuss elsewhere as this is sort of an odd place to have that discussion 🤣

@mattmoor wouldn't be surprised - the process is documented at https://github.com/tektoncd/community/blob/main/teps/0001-tekton-enhancement-proposal-process.md#tep-workflow - looking at some of the history there might help; a great place to discuss changes would be the API working group and/or an issue/pr over there

I know this PR is merged already, but I think it would make a lot of sense to support single quotes in addition to double quotes. This both matches how Kubernetes references info with the downwards api and also how bracket notation is typically used.


[BitSail][Doc] Building the project home page based on GitHub Pages

Is your feature request related to a problem? Please describe
A clear and concise description of what the problem is.
Example: I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

already online, https://bytedance.github.io/bitsail/


Add iter_data() to Assembler

This is part of the groundwork for #256. I wanted to open a separate PR for this so that @whitequark could provide comments on the approach I am taking.
This adds a new method iter_data() to the Assembler. It performs the calculation of data ranges that are stored given a byte offset.

Wow, @whitequark, you were quick! I tried to sneak in one last-minute commit amend, but you'd already approved it by then. (Just a documentation tweak, which turned out not to be helpful.)
I have reverted to the version the Homu bot approved, hopefully that will unstick the build.

@m-labs-homu r+

:pushpin: Commit a6d364a has been approved by whitequark

:hourglass: Testing commit a6d364a2ccfdc59d5c4e644b6fe49c01c51b8215 with merge 2acd13fe8b54ccac4f4b62158845c767b47f4b49...

:sunny: Test successful - status-travis
Approved by: whitequark
Pushing 2acd13fe8b54ccac4f4b62158845c767b47f4b49 to master...


pull request for e2e test at 11/09/2016 01:15:09

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

Details

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


A couple errors in branch v2.0.0beta

Describe the bug
I have a dataset of 11kk of rows, and after 20 minutes the process break to show "ValueError: f(a) and f(b) must have different signs". I was thinking if it was possible to detect this kind of problems before hand.
After it I tried to comment phi-k correlation which was the problem and there was another problem (ValueError: Unstacked DataFrame is too big, causing int32 overflow), I was going to create another issue to mention it but for not creating too many issues
To Reproduce
The line used to run is in the errors, the dataset to reproduce it.. is harder because it of the company, and not sure how I can create fake data that resembles the dataset and it has 11618532 rows. Maybe I could try to shift the numeric numbers to change the info, and with the categorical columns... not sure.
Version information:
alembic==1.0.7
astroid==2.2.5
async-generator==1.10
atomicwrites==1.3.0
attrs==18.2.0
backcall==0.1.0
bitarray==0.8.3
bleach==3.1.0
certifi==2018.11.29
chardet==3.0.4
cloudpickle==1.1.1
confuse==1.0.0
constants==0.6.0
cycler==0.10.0
dask==1.2.2
decorator==4.3.2
defusedxml==0.5.0
entrypoints==0.3
findspark==1.3.0
future==0.17.1
htmlmin==0.1.12
idna==2.8
importlib-metadata==0.17
impyla==<IP_ADDRESS>
ipykernel==5.1.0
ipython==7.3.0
ipython-genutils==0.2.0
isort==4.3.20
jedi==0.13.3
Jinja2==2.10
jsonschema==3.0.0
jupyter-client==5.2.4
jupyter-core==4.4.0
jupyterhub==0.9.4
jupyterhub-ldap-authenticator==0.3.1
kiwisolver==1.0.1
lazy-object-proxy==1.4.1
ldap3==2.5.2
llvmlite==0.29.0
locket==0.2.0
Mako==1.0.7
MarkupSafe==1.1.1
matplotlib==3.0.3
mccabe==0.6.1
missingno==0.4.1
missingpy==0.2.0
mistune==0.8.4
more-itertools==7.0.0
nbconvert==5.4.1
nbformat==4.4.0
notebook==5.7.4
numba==0.44.0
numpy==1.16.2
packaging==19.0
pamela==1.0.0
pandas==0.24.2
pandas-profiling==2.0.0
pandocfilters==1.4.2
parso==0.3.4
partd==0.3.10
pexpect==4.6.0
phik==0.9.8
pickleshare==0.7.5
plotly==3.10.0
pluggy==0.12.0
ply==3.11
prometheus-client==0.6.0
prompt-toolkit==2.0.9
ptyprocess==0.6.0
py==1.8.0
pyasn1==0.4.5
Pygments==2.3.1
PyHive==0.6.1
pyhs2==0.6.0
pylint==2.3.1
pyod==0.7.2
pyparsing==2.3.1
pyrsistent==0.14.11
pytest==4.6.1
pytest-pylint==0.14.0
python-dateutil==2.8.0
python-editor==1.0.4
python-oauth2==1.1.0
pytz==2018.9
PyYAML==5.1
pyzmq==18.0.0
requests==2.21.0
retrying==1.3.3
sasl==0.2.1
scikit-learn==0.20.3
scipy==1.2.1
seaborn==0.9.0
Send2Trash==1.5.0
six==1.12.0
SQLAlchemy==1.2.18
sudospawner==0.6.0.dev0
terminado==0.8.1
testpath==0.4.2
thrift==0.11.0
thrift-sasl==0.2.1
thriftpy==0.3.9
toolz==0.9.0
tornado==5.1.1
traitlets==4.3.2
typed-ast==1.3.5
urllib3==1.24.1
virtualenv==16.4.3
wcwidth==0.1.7
webencodings==0.5.1
wrapt==1.11.1
zipp==0.5.1
Additional context
ValueError                                Traceback (most recent call last)
<ipython-input-12-b3ba44380000> in <module>
----> 1 df.profile_report(missing_diagrams={'dendrogram': False, 'heatmap': False}).to_file(output_file="report.html")

/usr/lib/python3.6/site-packages/pandas_profiling/controller/pandas_decorator.py in profile_report(df, **kwargs)
     14         A ProfileReport of the DataFrame.
     15     """
---> 16     p = ProfileReport(df, **kwargs)
     17     return p
     18

/usr/lib/python3.6/site-packages/pandas_profiling/__init__.py in __init__(self, df, **kwargs)
     37
     38         # Get dataset statistics
---> 39         description_set = describe_df(df)
     40
     41         # Get sample

/usr/lib/python3.6/site-packages/pandas_profiling/model/describe.py in describe(df)
    415
    416     # Get correlations
--> 417     correlations = calculate_correlations(df, variables)
    418
    419     # Check correlations between numerical variables

/usr/lib/python3.6/site-packages/pandas_profiling/model/correlations.py in calculate_correlations(df, variables)
    167                     continue
    168
--> 169             correlations["phi_k"] = df[selcols].phik_matrix(interval_cols=intcols)
    170
    171     if config["correlations"]["cramers"].get(bool):

/usr/lib/python3.6/site-packages/phik/phik.py in phik_matrix(df, interval_cols, bins, quantile, noise_correction, dropna, drop_underflow, drop_overflow)
    154     data_binned, binning_dict = bin_data(df_clean, cols=interval_cols_clean, bins=bins, quantile=quantile, retbins=True)
    155     return phik_from_rebinned_df(data_binned, noise_correction, dropna=dropna, drop_underflow=drop_underflow,
--> 156                                  drop_overflow=drop_overflow)
    157
    158

/usr/lib/python3.6/site-packages/phik/phik.py in phik_from_rebinned_df(data_binned, noise_correction, dropna, drop_underflow, drop_overflow)
    108
    109         datahist.columns = datahist.columns.droplevel()
--> 110         phikvalue = phik_from_hist2d(datahist.values, noise_correction=noise_correction)
    111         phiks[':'.join(comb)] = phikvalue
    112

/usr/lib/python3.6/site-packages/phik/phik.py in phik_from_hist2d(observed, noise_correction)
     53
     54     # phik calculation adds noise pedestal to theoretical chi2
---> 55     phik = phik_from_chi2(chi2, observed.sum(), *observed.shape, None, None, pedestal)
     56
     57     return phik

/usr/lib/python3.6/site-packages/phik/bivariate.py in phik_from_chi2(chi2, n, nx, ny, sx, sy, pedestal)
    145         return 0
    146
--> 147     rho = optimize.brentq(chi2_from_phik, 0, 1, args=(n, chi2, corr0, scale, sx, sy, pedestal))
    148     return rho

/usr/lib64/python3.6/site-packages/scipy/optimize/zeros.py in brentq(f, a, b, args, xtol, rtol, maxiter, full_output, disp)
    752     if rtol < _rtol:
    753         raise ValueError("rtol too small (%g < %g)" % (rtol, _rtol))
--> 754     r = _zeros._brentq(f, a, b, xtol, rtol, maxiter, args, full_output, disp)
    755     return results_c(full_output, r)
    756

ValueError: f(a) and f(b) must have different signs

---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-6-f7c582662276> in <module>
----> 1 df.profile_report(missing_diagrams={'dendrogram': False, 'heatmap': False}, correlations={'phi_k': False}).to_file(output_file="report.html")

/usr/lib/python3.6/site-packages/pandas_profiling/controller/pandas_decorator.py in profile_report(df, **kwargs)
     14         A ProfileReport of the DataFrame.
     15     """
---> 16     p = ProfileReport(df, **kwargs)
     17     return p
     18

/usr/lib/python3.6/site-packages/pandas_profiling/__init__.py in __init__(self, df, **kwargs)
     37
     38         # Get dataset statistics
---> 39         description_set = describe_df(df)
     40
     41         # Get sample

/usr/lib/python3.6/site-packages/pandas_profiling/model/describe.py in describe(df)
    415
    416     # Get correlations
--> 417     correlations = calculate_correlations(df, variables)
    418
    419     # Check correlations between numerical variables

/usr/lib/python3.6/site-packages/pandas_profiling/model/correlations.py in calculate_correlations(df, variables)
    175
    176     if config["correlations"]["recoded"].get(bool):
--> 177         correlation = recoded_matrix(df, variables)
    178         if len(correlation) > 0:
    179             correlations["recoded"] = correlation

/usr/lib/python3.6/site-packages/pandas_profiling/model/correlations.py in recoded_matrix(df, variables)
     70         A recoded matrix for categorical variables.
     71     """
---> 72     return categorical_matrix(df, variables, partial(check_recoded, count=len(df)))
     73
     74

/usr/lib/python3.6/site-packages/pandas_profiling/model/correlations.py in categorical_matrix(df, variables, correlation_function)
    101         categoricals.items(), 2
    102     ):
--> 103         confusion_matrix = pd.crosstab(data1, data2)
    104         correlation_matrix.loc[name2, name1] = correlation_matrix.loc[
    105             name1, name2

/usr/lib64/python3.6/site-packages/pandas/core/reshape/pivot.py in crosstab(index, columns, values, rownames, colnames, aggfunc, margins, margins_name, dropna, normalize)
    519     table = df.pivot_table('__dummy__', index=rownames, columns=colnames,
    520                            margins=margins, margins_name=margins_name,
--> 521                            dropna=dropna, **kwargs)
    522
    523     # Post-process

/usr/lib64/python3.6/site-packages/pandas/core/frame.py in pivot_table(self, values, index, columns, aggfunc, fill_value, margins, dropna, margins_name)
   5757                            aggfunc=aggfunc, fill_value=fill_value,
   5758                            margins=margins, dropna=dropna,
-> 5759                            margins_name=margins_name)
   5760
   5761     def stack(self, level=-1, dropna=True):

/usr/lib64/python3.6/site-packages/pandas/core/reshape/pivot.py in pivot_table(data, values, index, columns, aggfunc, fill_value, margins, dropna, margins_name)
    107             else:
    108                 to_unstack.append(name)
--> 109         table = agged.unstack(to_unstack)
    110
    111     if not dropna:

/usr/lib64/python3.6/site-packages/pandas/core/frame.py in unstack(self, level, fill_value)
   5990         """
   5991         from pandas.core.reshape.reshape import unstack
-> 5992         return unstack(self, level, fill_value)
   5993
   5994     _shared_docs['melt'] = ("""

/usr/lib64/python3.6/site-packages/pandas/core/reshape/reshape.py in unstack(obj, level, fill_value)
    386     if isinstance(obj, DataFrame):
    387         if isinstance(obj.index, MultiIndex):
--> 388             return _unstack_frame(obj, level, fill_value=fill_value)
    389         else:
    390             return obj.T.stack(dropna=False)

/usr/lib64/python3.6/site-packages/pandas/core/reshape/reshape.py in _unstack_frame(obj, level, fill_value)
    409                                value_columns=obj.columns,
    410                                fill_value=fill_value,
--> 411                                constructor=obj._constructor)
    412         return unstacker.get_result()
    413

/usr/lib64/python3.6/site-packages/pandas/core/reshape/reshape.py in __init__(self, values, index, level, value_columns, fill_value, constructor)
    122
    123         if num_rows > 0 and num_columns > 0 and num_cells <= 0:
--> 124             raise ValueError('Unstacked DataFrame is too big, '
    125                              'causing int32 overflow')
    126

ValueError: Unstacked DataFrame is too big, causing int32 overflow

Thank you for your report. Could you add the output of df.info()?  I was thinking if it is possible to do the process incrementally because it takes a lot of RAM.
And another unrelated problem is the font, since I'm in a cluster with linux, and I can't install the Windows fonts.
/usr/lib64/python3.6/site-packages/matplotlib/font_manager.py:1241: UserWarning:
findfont: Font family ['sans-serif'] not found. Falling back to DejaVu Sans.

@set92 are you still planning to provide us with some fake data?

@sbrugman here you have, at the end I had to take most of the string columns bcs I couldnt fake them much, so not sure if it will be useful https://drive.google.com/open?id=1nzlkaw8AMQwWIf-vLxQLwKXwoeA5ocZ0. But if not you can always use it to do tests of performance.

Thank you @set92, working with this data was very fruitful.
Testing your dataset provided the following observations:

posted_on, trans_date and trans_date_di are datetimes, but no feedback is given if they are passed as categoricals. Mitigated by giving a warning for datetimes mascaraded as categoricals.
(mini) histograms break for the full DataFrame. The problem is that too many plots remain open, due to a missing closing statements in a specific execution flow. Solved by closing the plots.
For this larger dataset, percentages of near 0 and 100 are rounded so that they appear to that number exactly, which is confusing. These edge cases are now displayed as < 0.1% and > 99.9%.

The source of the errors seem to be the categorical variables with a high number of distinct values. I improved the detection for these scenario's and drop variables if they exceed a configurable threshold.


requery-processor 1.4 not available in kotlin

I'm trying to run version 1.4.0 with the following in build.gradle:
compile 'io.requery:requery:1.4.0'
compile 'io.requery:requery-kotlin:1.4.0'
kapt 'io.requery:requery-processor:1.4.0'

and receive the following error:
Error:Could not find io.requery:requery-processor:1.4.0.
Searched in the following locations:
    https://repo1.maven.org/maven2/io/requery/requery-processor/1.4.0/requery-processor-1.4.0.pom
    https://repo1.maven.org/maven2/io/requery/requery-processor/1.4.0/requery-processor-1.4.0.jar
    https://jitpack.io/io/requery/requery-processor/1.4.0/requery-processor-1.4.0.pom
    https://jitpack.io/io/requery/requery-processor/1.4.0/requery-processor-1.4.0.jar
    https://dl.bintray.com/kotlin/exposed/io/requery/requery-processor/1.4.0/requery-processor-1.4.0.pom
    https://dl.bintray.com/kotlin/exposed/io/requery/requery-processor/1.4.0/requery-processor-1.4.0.jar
Required by:
    project :

Note that version 1.3.2 refreshes just fine:
    compile 'io.requery:requery:1.3.2'
    compile 'io.requery:requery-kotlin:1.3.2'
    kapt 'io.requery:requery-processor:1.3.2'

Hi 1.4 was mistakenly not available on maven central, it was published only on bintray. That has been fixed so it should be fine now, thanks for reporting. However It also looks like you are resolving to bintray but your path is wrong it shouldn't start with kotlin/exposed, so you may want to check your gradle build script.


 Path delimiters are always '/'.
Special Characters:
- ! at the beginning of the pattern negates it
- \ marks the following character as a literal
- ? matches any non-slash character
- * matches multiple non-slash characters
- ** matches multiple characters with infinite depth

Sub-patterns:
- brackets [] denote a set of characters that can be matched:
    - loose set of characters, e.g. [cake] which matches the characters c, a, k, and e
    - range of characters, e.g. [0-5] which matches all numbers from 0 to 5
    - posix class, e.g. [[:word:]] which match certain pre-defined rules
    - ! at the beginning of the set inverts it, e.g. [!.] matches anything that isn't a period
- parentheses () denote a certain amount of matches:
    - ? matches 0 or 1 times
    - TODO: * matches 0 or more times
    - TODO: + matches 1 or more times
    - TODO: {a,b} matches between a and b times, e.g. {3,5} matches 3-5 times

Absolute paths have highest specificity, followed by paths with the most nesting, then by path segments with the least ambiguity.

after discussing in-person with @DragaDoncila, I will close this as it is out of scope (will discuss with @tlambert03 and @nclack later on if wildmatching is a desirable feature) and open a PR just for specificity scoring according to fnmatch's rules


invalid key/value pair in file /etc/udev/rules.d/99-realsense-libusb.rules

Operating System & Version: Linux 5.4.70 (aarch64) built by yoctor
udevd version: 3.2.8
udevadm version: 228
I'm deploying the realsense SDK 2.45 to my iMX8 board. And follow the installation guideline, I copied 99-realsense-libusb.rules and run the command of "udevadm control --reload-rules && udevadm trigger".
Then I got following error:
[ 1589.181217] udevd[261]: invalid key/value pair in file /etc/udev/rules.d/99-realsense-libusb.rules on line 81, starting at character 154 ('.')
But it seems the SDK and camera (D455) work as expected. However every time the system is booting, the above error will be shown when starting udevd.

Hi @yzkzero   Regarding the information Linux 5.4.70 (aarch64) built by yoctor - do you mean Yocto, please?
I haven't seen this particular error in librealsense before.  There has been a past reported issue with using udevadm control --reload-rules && udevadm trigger in a Docker container on an Arm-based Nvidia Jetson board though.  The i.MX8 board is Arm-based too.  Is your project using a Docker container?
https://github.com/IntelRealSense/librealsense/issues/7849

Hi MartyG,
Sorry for the typo. Yes, it's built by Yocto.
I'm not using docker or any container. The error only displays in serial console (serial port connected). If I execute the command in ssh or telnet console, there's no error displayed. But the error is immediately displayed in serial console once I execute the command in ssh/telnet console. And as I mentioned, each time the system is booting up, the error is also shown. It can also be observed in boot log.

Would it be possible to provide a link to the installation instructions that you used, please?  The process that you used sounds similar to the one in the link below.
https://stackoverflow.com/questions/62134563/how-to-give-permission-to-intel-realsense-camera-on-ubuntu/62369143#62369143

I referred to installation instruction of raspberry pi : https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_raspbian.md
What I did are:
$ git clone https://github.com/IntelRealSense/librealsense.git
$ cd librealsense
$ sudo cp config/99-realsense-libusb.rules /etc/udev/rules.d/
$ sudo udevadm control --reload-rules && udevadm trigger

The official raspbian_md guide is suited to Pi 3.  If you have a Raspberry Pi 4 then the similarly structured Acrobotic installation guide for Pi 4 and Raspbian is a better choice.
https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_raspbian.md
RealSense users who have performed installation with these guides have also recommended using a more modern version of Protobuf than the ones in the guides, such as version 3.14 in order to reduce the likelihood of build errors.

Hi MartyG,
I just referred to the part of applying udev rules from raspberry doc.
The only things I did on my iMX8 board are:
$ git clone https://github.com/IntelRealSense/librealsense.git
$ cd librealsense
$ sudo cp config/99-realsense-libusb.rules /etc/udev/rules.d/
$ sudo udevadm control --reload-rules && udevadm trigger

If the invalid key/value pair message is not affecting the D455's operation then would it be an option to simply ignore the message?

If the invalid key/value pair message is not affecting the D455's operation then would it be an option to simply ignore the message?

Yes, it currently doesn't affect the RGB and depth function on D455 so far. But I'm not sure if it will affect the IMU or any other function I am not aware of.
The comment for the error line is:
# For products with motion_module, if (kernels is 4.15 and up) and (device name is "accel_3d") wait, in another process, until (enable flag is set to 1 or 200 mSec passed) and then set it to 0. KERNEL=="iio*", ATTRS{idVendor}=="8086", ATTRS{idProduct}=="0ad5|0afe|0aff|0b00|0b01|0b3a|0b3d|0b64|0b68", RUN+="/bin/sh -c '(major=uname -r | cut -d "." -f1 && minor=uname -r | cut -d "." -f2&& (([ $major -eq 4 ] && [ $minor -ge 15 ]) || [ $major -ge 5 ])) && (enamefile=/sys/%p/name && [cat $enamefile = \"accel_3d\" ]) && enfile=/sys/%p/buffer/enable && echo \"COUNTER=0; while [ \$COUNTER -lt 20 ] && grep -q 0 $enfile; do sleep 0.01; COUNTER=\$((COUNTER+1)); done && echo 0 > $enfile\" | at now'"
So it looks like the rule is for the motion module.

If you are using a text-only display in a terminal and are not able to run graphical tools such as the RealSense Viewer, it may be difficult to validate the Motion Module's performance (though it is likely that it is a one-off warning rather than something that impacts Motion Module performance).
You could perhaps profile the IMU streams and collect 60 seconds worth of data into a log file using the SDK's rs-data-collect tool.
https://github.com/IntelRealSense/librealsense/tree/master/tools/data-collect

Hi @yzkzero  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.

I have the exact same issue when doing this on Xilinx ZCU104 running Petalinux 2020.2. I get the error in doing the exact same steps as below.
$ git clone https://github.com/IntelRealSense/librealsense.git
$ cd librealsense
$ sudo cp config/99-realsense-libusb.rules /etc/udev/rules.d/
$ sudo udevadm control --reload-rules && udevadm trigger

After finally building and installing the SDK my 435i camera is not being detected. I beleive it is because of this error in /etc/udev/rules.d/99-realsense-libusb.rules on line 81, starting at character 154 ('.').
Is the cause of this error found yet? If so please guide me to fix it.

Hi @nalithlakshan  There are very few references for installing the librealsense SDK on Xilinx products, and only for Xilinx Ultra96 FPGA.  These references are listed at the link below.
https://support.intelrealsense.com/hc/en-us/community/posts/6673895808915/comments/6674992093459
I would recommend trying the libuvc backend installation method, as it bypasses the Linux kernel and so is not dependent on Linux versions of kernel versions and does not require kernel patching.
https://github.com/IntelRealSense/librealsense/blob/master/doc/libuvc_installation.md


csrf_set_cookie() fails under nginx+php-fpm

This is due to $_SERVER['HTTPS'] do not exists in the default fastcgi/php-fpm configuration delivered with nginx.
A work around is to force $_SERVER['HTTPS'] = 'on' in a config, or set it manually in nginx.conf if using HTTPS.
The best solution would be to change csrf_set_cookie() to check for SERVER_PORT and HTTPS, if either matches - use the connection is secure - and the cookie should be set.
/ Jim

It's just most tutorials don't instruct users to pass  'fastcgi_param HTTPS on', while they should.


Update 138 with clarified text on HST

Clarified HST emissions = HNT emitted to HST Holders.
Added detail on who HST are for those who are not familiar.
Other clarifications

Closed as outdated.


External Equity Links should be added in the Free Columns

I'm using the Python library and when I look at the lsapi.py file I see that the externalLinks column (with the BitFlag of 32) says it's not available to users with a free account.  However, when I reference your API documentation it shows that it is available with a free account.  See here
Can we add this to the lsapi.UMCols.freeCols attribute?

I see that externalLinks is included in the lsapi.UMCols.freeCols tuple.  But I don't see an attribute in the response that corresponds to it:
metrics = l.urlMetrics(['www.moz.com', 'seriouseats.com'], lsapi.UMCols.freeCols)
print metrics

[{'fmrp': 5.837410743247288,
  'fmrr': 1.0137685781330276e-07,
  'pda': 91.46535716211868,
  'uid': 4859,
  'ulc':<PHONE_NUMBER>,
  'umrp': 6.089938967209491,
  'umrr': 3.1160789797773323e-09,
  'upa': 73.25686321997019,
  'us': 301,
  'ut': u'',
  'uu': 'www.moz.com/'},
 {'fmrp': 5.92159020570692,
  'fmrr': 1.257740684586365e-07,
  'pda': 84.46559166894879,
  'uid': 46617,
  'ulc':<PHONE_NUMBER>,
  'umrp': 6.320415213589495,
  'umrr': 7.250263171269388e-09,
  'upa': 71.82088128899844,
  'us': 200,
  'ut': 'Serious Eats: The Destination for Delicious | Serious Eats',
  'uu': 'seriouseats.com/'}]

I see the attribute uid, but according to your documentation that should be the [number of Links](The number of links (equity or nonequity or not, internal or external) to the URL) (The number of links (equity or nonequity or not, internal or external) to the URL).  The External Equity Links should have the attribute ueid (The number of external equity links to the URL).

That's interesting. I'll try to reproduce it. FWIW, this code is also available under https://github.com/seomoz/linkscape-py

Figured out the issue. I'll get a pull request going, but in the mean time, the workaround is to say:
metrics = l.urlMetrics(['www.moz.com', 'seriouseats.com'], lsapi.UMCols.freeCols | 32)

Fixed by #19.


Feedback window will close on click

The Feedback panel in the Windows version will close as soon as you click the input to type your feedback.

It's fixed in https://github.com/thanhlmm/refi-app/issues/40.
Thank you for your feedback @csfalcao  🙇 , I will release it soon!


No module named service_identity

Hi yi-ji,
I ran the NeteaseMusicProxy.py and it returned the message as following:
:0: UserWarning: You do not have a working installation of the service_identity module: 'No module named service_identity'.  Please install it from https://pypi.python.org/pypi/service_identity and make sure all of its dependencies are satisfied.  Without the service_identity module, Twisted can perform only rudimentary TLS client hostname verification.  Many valid certificate/hostname mappings may be rejected.
2019-07-31 17:29:07+1000 [-] Log opened.
2019-07-31 17:29:12+1000 [-] NeteaseMusicProxyFactory starting on 32794
2019-07-31 17:29:12+1000 [-] Starting factory <main.NeteaseMusicProxyFactory instance at 0x10c84e7e8>
2019-07-31 17:32:20+1000 [-] http://music.163.com/api/feedback/client/log?MUSIC_A=72d9020673feb01447ed48f7e0e8a781430ebca26d55f21723449d12b82d2f3dcb9352d2bb3cb879f1dc06d1aab65e3e850c61c4b018d14c853dc3117a0bd5d135c0f8303e3442ba5f4137cf0c987435a2942e412df393ea39cd2d04ccb8fc2744a96df7ffa646ab9e2c3c7640b5c6f80dbe115efc218ca4c3061cd18d77b7a0
2019-07-31 17:32:20+1000 [-] Starting factory <main.NeteaseMusicProxyClientFactory instance at 0x10c867bd8>
2019-07-31 17:32:21+1000 [-] "<IP_ADDRESS>" - - [31/Jul/2019:07:32:20 +0000] "POST http://music.163.com/api/feedback/client/log?MUSIC_A=72d9020673feb01447ed48f7e0e8a781430ebca26d55f21723449d12b82d2f3dcb9352d2bb3cb879f1dc06d1aab65e3e850c61c4b018d14c853dc3117a0bd5d135c0f8303e3442ba5f4137cf0c987435a2942e412df393ea39cd2d04ccb8fc2744a96df7ffa646ab9e2c3c7640b5c6f80dbe115efc218ca4c3061cd18d77b7a0 HTTP/1.1" 200 12 "-" "NeteaseMusic/790 CFNetwork/897.15 Darwin/17.5.0 (x86_64)"
2019-07-31 17:32:21+1000 [-] [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionDone'>: Connection was closed cleanly.
2019-07-31 17:32:21+1000 [-] ]
2019-07-31 17:32:21+1000 [-] Stopping factory <main.NeteaseMusicProxyClientFactory instance at 0x10c867bd8>
2019-07-31 17:34:21+1000 [-] http://music.163.com/api/feedback/client/log?MUSIC_A=72d9020673feb01447ed48f7e0e8a781430ebca26d55f21723449d12b82d2f3dcb9352d2bb3cb879f1dc06d1aab65e3e850c61c4b018d14c853dc3117a0bd5d135c0f8303e3442ba5f4137cf0c987435a2942e412df393ea39cd2d04ccb8fc2744a96df7ffa646ab9e2c3c7640b5c6f80dbe115efc218ca4c3061cd18d77b7a0
2019-07-31 17:34:21+1000 [-] Starting factory <main.NeteaseMusicProxyClientFactory instance at 0x10c9aeb00>
2019-07-31 17:34:22+1000 [-] "<IP_ADDRESS>" - - [31/Jul/2019:07:34:22 +0000] "POST http://music.163.com/api/feedback/client/log?MUSIC_A=72d9020673feb01447ed48f7e0e8a781430ebca26d55f21723449d12b82d2f3dcb9352d2bb3cb879f1dc06d1aab65e3e850c61c4b018d14c853dc3117a0bd5d135c0f8303e3442ba5f4137cf0c987435a2942e412df393ea39cd2d04ccb8fc2744a96df7ffa646ab9e2c3c7640b5c6f80dbe115efc218ca4c3061cd18d77b7a0 HTTP/1.1" 200 12 "-" "NeteaseMusic/790 CFNetwork/897.15 Darwin/17.5.0 (x86_64)"
2019-07-31 17:34:22+1000 [-] [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionDone'>: Connection was closed cleanly.
2019-07-31 17:34:22+1000 [-] ]
2019-07-31 17:34:22+1000 [-] Stopping factory <main.NeteaseMusicProxyClientFactory instance at 0x10c9aeb00>
Hope you can offer a quick solution. Thank you so much in advance~
Cheers,
Katrine

FYI, the working environment was public Wi-Fi

Follow up:
The package service_identity has been installed, given the warning message as above. However, it didn't solve the problem, as the Helper script is still not working. : (
Log:
2019-07-31 17:55:03+1000 [-] Log opened.
2019-07-31 17:55:08+1000 [-] NeteaseMusicProxyFactory starting on 32794
2019-07-31 17:55:08+1000 [-] Starting factory <main.NeteaseMusicProxyFactory instance at 0x110c224d0>

Please try pip install service_identity --force
Also replace pip with pip3 if you're using python3
Could you report your macOS version, python version, NeteaseMusic version and check the network proxy setting as listed in FAQ?

Hi yi-ji,
Thanks for the reply.
I have installed the service_identity module with pip, after that there is no warning message coming out.
Log#2:
2019-08-01 01:58:34+1000 [-] http://music.163.com/api/feedback/client/log?MUSIC_A=72d9020673feb01447ed48f7e0e8a781430ebca26d55f21723449d12b82d2f3dcb9352d2bb3cb879f1dc06d1aab65e3e850c61c4b018d14c853dc3117a0bd5d135c0f8303e3442ba5f4137cf0c987435a2942e412df393ea39cd2d04ccb8fc2744a96df7ffa646ab9e2c3c7640b5c6f80dbe115efc218ca4c3061cd18d77b7a0
2019-08-01 01:58:34+1000 [-] Starting factory <main.NeteaseMusicProxyClientFactory instance at 0x108c0cbd8>
2019-08-01 01:58:36+1000 [-] "<IP_ADDRESS>" - - [31/Jul/2019:15:58:35 +0000] "POST http://music.163.com/api/feedback/client/log?MUSIC_A=72d9020673feb01447ed48f7e0e8a781430ebca26d55f21723449d12b82d2f3dcb9352d2bb3cb879f1dc06d1aab65e3e850c61c4b018d14c853dc3117a0bd5d135c0f8303e3442ba5f4137cf0c987435a2942e412df393ea39cd2d04ccb8fc2744a96df7ffa646ab9e2c3c7640b5c6f80dbe115efc218ca4c3061cd18d77b7a0 HTTP/1.1" 200 12 "-" "NeteaseMusic/790 CFNetwork/897.15 Darwin/17.5.0 (x86_64)"
2019-08-01 01:58:36+1000 [-] [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionDone'>: Connection was closed cleanly.
2019-08-01 01:58:36+1000 [-] ]
2019-08-01 01:58:36+1000 [-] Stopping factory <main.NeteaseMusicProxyClientFactory instance at 0x108c0cbd8>
=======================
python version: Python 2.7.14
MacOS version: 10.13.4
NeteaseMusic version: 2.1.1
The network proxy setting has been set as "Automatic Proxy Configuration" .
Cheers,
Katrine

I just reinstalled NeteaseMusic in the version 1.5.10 and it works very well.
Problem solved! : ) Cheers mate~

I see.
Sorry this tool does not support NeteaseMusic version 2.0.0 and above (#29) as of now.
Please install NeteaseMusic with versions 1.x.x. Sorry for the inconvenience.

That's all right. A good tool overall. Thank you all the same!


Disable codecov from failing CI if there is an upload issue

Description
Seeing a ton of CI failures due to code coverage upload failures.  I'd like to fix this - but I'd rather keep the builds flowing in until we have a better solution.
E.g: https://github.com/opensearch-project/security/actions/runs/6153593099/job/16697726519?pr=3339

Related https://github.com/opensearch-project/security/issues/2649

Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Retrying tests, network error on windows hosts, case of the network issue we've been tracking [1].

[1] https://github.com/opensearch-project/security/issues/3266


Add eip check script to openshift-tools rpm

+1 from https://github.com/openshift/openshift-tools/pull/3804


User's profiles

I write in several programming languages. Each of them has its own plugins and settings. Plugins take up resources. I would like to change the profiles depending on the language used. I want profiles to be synced via github or a microsoft account. Example. React Profile (plugins: type script, eslint...), Arduino Profile (Platformio plugins, c++), Flutter Profile (plugins: Dart, Flutter).

/duplicate - see #139409


Update SPI Readme

Here is my initial draft to update the SPI README.  I have some TODO areas identified.
I looked at the updated section on GPIOs and I think the simplified schematics is all it needs.  I finally figured out the previous schematic, but it didn't make a lot of sense when the 1st example used the second drawing and the 2nd example used the first one.
I've updated the example to use the MCP3008 from the conference talk.  I need to add the marked up figure 5-1 from the slides and I think it might be helpful to add the top of table 5-1 to show how to figure out the mode and sensor inputs.
I'm sure some of my terminology is incorrect, so please let me know if I need to change some terms.  I'm also not tied to any of the other wording or paragraphs.
I'll keep working on the TODOs.  Let me know if I'm off-base and you want me to write it up differently.
Axel

I like it so far. I added some text, but now I need to leave for the evening. I'll check back again when I have a chance. Thank you so much for writing this up!

I have included the content I would recommend adding.  There are still a few TODOS I probably need your help with.  Let me know what you think.

I'm planning to review again for grammar, consistency and clarity.


Rename BuildTests to JSON_BuildTests

This avoids potential conflicts with other libraries when the library is
built from source and included in a bigger cmake build.

Coverage remained the same at 100.0% when pulling cd800522e42b81ae261c44d23e1559fc11649c40 on olegendo:develop into 7dee868a42d788f2652a442d3fbead406a029a74 on nlohmann:develop.

Thanks a lot!

Sure, no problem.  Are you going to merge it into the develop branch?

Coverage remained the same at 100.0% when pulling cd800522e42b81ae261c44d23e1559fc11649c40 on olegendo:develop into 7dee868a42d788f2652a442d3fbead406a029a74 on nlohmann:develop.


Mark paused VMs as unready

What this PR does / why we need it:
This PR marks VMIs as unready when they are paused.
This is done by adding a custom pod condition to the virt-launcher pod, which serves as a readiness gate.
The condition's value is toggled according to whether the VMI is paused or not, which sets the virt-launcher as unready when the condition value is false. The pod readiness condition is then synced back to the VMI and the VM for proper reporting.
This also ensures that service-fronted VMs aren't targeted with service traffic when they are paused.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #5920
Special notes for your reviewer:
This PR also slightly refactors the code in pkg/controller/conditions.go (at least until Go generics land).
Release note:
Paused VMIs are now marked as unready even when no readinessProbe is specified

/retest

/retest

/retest

/retest

/retest

@rmohr review comments addressed, do you mind giving this another pass?

/retest-required

/approve
@zvikorn needs another rebase due to the delay but looks perfect otherwise.

needs another rebase due to the delay but looks perfect otherwise.

@rmohr done

@rmohr this is now ready for another /lgtm :-)

/lgtm


chore: update maintainers list

Link to GitHub repository
Plugin: https://github.com/jenkinsci/snyk-security-scanner-plugin
Request confirmation: @asaf92, @bastiandoetsch
When modifying release permission
If you are modifying the release permission of your plugin or component, fill out the following checklist:
Release permission checklist (for submitters)

[x] The usernames of the users added to the "developers" section in the .yml file are the same the users use to log in to accounts.jenkins.io.
[x] All users added have logged in to Artifactory and Jira once.
[x] I have mentioned an existing team member of the plugin or component team to approve this request.

Yep, looks correct. I wonder if there's a mechanism for cross-github org cleanup - e.g. making status in jenkins dependent on membership in the snyk org.

if there's a mechanism for cross-github org cleanup - e.g. making status in jenkins dependent on membership in the snyk org.

Note these user lists are Jenkins community accounts, not GH accounts, adding a level of indirection/translation.


[Python] Scanner does not free memory

Describe the usage question you have. Please include as many useful details as  possible.
I am trying to create a table in duckdb using an arrow scanner on a dataset of parquet files with a batch size of 1000 files, I realized that the more files are processed, more memory is used and is not released until the end of the scan, producing this certain memory problems if the dataset is very large. I thought that only the part of the files scanned at that moment is loaded in memory.
How can I solve this problem?
code:
con = duckdb.connect()

ds.dataset("parquet_folder")

my_arrow_dataset = ds.dataset('parquet_folder/')

arrow_scanner = ds.Scanner.from_dataset(my_arrow_dataset ,batch_size=1000)

con.execute("CREATE TABLE my_table AS SELECT * FROM arrow_scanner ")

Component(s)
Python

My guess is that you are seeing the parquet metadata getting cached as per https://github.com/apache/arrow/issues/33888


Laravel 5.8 support

Add support of Laravel 5.8

Can you update in the Packagist as well, please?

Version 6 completely changes and i cannot update to it.
Can you make sure you support 5.8 in your version 5 please!?

@hassanazimi you are right. This package has changes a lot and it's completely another approach.
I see here 2 solutions:

Make a fork and maintain it by yourself
I can resurrect laravel-likeable package, from which this one was born, but it will get only version support releases without any new features implementation. If anybody want to maintain and improve old implementation I can share an access to it.

@hassanazimi I fork this project https://github.com/taliptako/laravel-love

@taliptako you still have 6.x tags:

in repository: https://github.com/taliptako/laravel-love/tags
in packagist: https://packagist.org/packages/taliptako/laravel-love

You'd better remove them, because they could bring conflicts in the future.

thanks @taliptako <3
v6.x is a nice feature rich improvement, but I will wait for the feature like $article->collectLikers();
@antonkomarev is something already implemented, where I get the reacters collection, also by type would be awesome :-)

@antonkomarev Thanks i did actually if you also add 5.8 support for version 5 that would be better i think you dont need to maintain it just merge the pull requests when needed its enough

@taliptako I decided to stop improving old architecture because it's really hard or impossible to implement some features on it. I can accept PRs to support v5, but only if they wouldn't be breaking, because then it will require to make new major release what breaks SemVer, and package already gone forward.
v5 branch created. If you want - make a PR to add 5.8 support to it and I release a new version.

@affektde you can get reacters from reactant reactions:
$reactions = $article
    ->getLoveReactant()
    ->reactions()
    ->get();

foreach ($reactions as $reaction) {
    dump($reaction->getReacter());
}

Or specify concrete type of the reactions:
$likeReactions = $article
    ->getLoveReactant()
    ->reactions()
    ->where('reaction_type_id', ReactionType::fromName('Like')->getId())
    ->get();

foreach ($reactions as $reaction) {
    dump($reaction->getReacter());
}

The main problem with adding Laravel 5.8 to Love 5.x, that it will require to drop PHP7.0 support or Laravel 5.5. And this is breaking changes. I think I will leave it as is, but turn off Laravel 5.5 tests, because they will fail all the time.

Laravel Love v5.2.1 released with Laravel 5.8 support. @taliptako added to contributors list :+1:


Topic/angular momentum

Recently, I made task function for angular momentum.
The task is exactly same as that in the pinocchio-inv-dyn.
More specifically,

"task-angular-momentum-equality.cpp" was generated with "TaskBase" class.
(Existed tasks such as "com", "jointposture", and "EE" are based on "TaskMotion" class.
If you don't like this new task based on "TaskBase", Please tell me. I will modify it. )
I made a few of unit-test codes which are related on angular momentum task.
I added angular momentum task in the demo_romeo.py and demo_quadprog.py.

ps. [stack-of-tasks with devel branch] The unit-test, tsid-formulation.cpp, was not passed in my computer. I don't know if this error is only a problem for my computer.

Hi @ggory15, thanks for providing this PR! This is a feature I was hoping to get supported by TSID as well :)
From your description it sounds like the task is tracking only the angular momentum. Would it be possible to track the linear momentum with the same task as well? If you are only interested to track the angular moment, you could set the grains for the linear momentum to zeros and thereby get an angular momentum task.

Hi @ggory15, thanks for providing this PR! This is a feature I was hoping to get supported by TSID as well :)
From your description it sounds like the task is tracking only the angular momentum. Would it be possible to track the linear momentum with the same task as well? If you are only interested to track the angular moment, you could set the grains for the linear momentum to zeros and thereby get an angular momentum task.

Setting the gains to zero wouldn't be enough, but you can get what you want by using the mask

I will fix this function with suggestions. (after next monday.)

Can I close this PR ?

@ggory15 Hi Sanghyun, do you think you would have time to update the PR, or should we find a way to do it ourselves ? Thanks a lot !

@ggory15 Hi Sanghyun, do you think you would have time to update the PR, or should we find a way to do it ourselves ? Thanks a lot !

I am sorry that I totally forget to update it. Because of my ph.d defense, I can't consentrate on this work. Can you close this PR? I will update it later.


Add RSS feed

I don't know exactly how to do this with Jekyll. Can we make it an automatic part of the build process, when we push? Or should it be manual?

May be related to https://github.com/RichardLitt/richardlitt.github.com/issues/77.


stop pollution of "globalThis" and prevent it from happening again in tests

some weird stuff is happening with process object definitely. it does not seem like the interop between cdk-web and node is really working when executed in node.
this should be investigated. for example it's not possible to chdir into a different directory for the nodejs lambda when executed in node.

addressed by https://github.com/3p3r/cdk-web/pull/141


Updated Visual Basic IDE topic

Added links to Refactoring and Code Generation; removed old Refactoring
link and topic; updated TOC.
Fixes #1269 Fixes #1270

isn't there a location that you could redirect the file refactoring-and-rename-dialog-box.md instead of simply excluding? the redirection works across repos.

@mairaw The dialog box no longer exists in VS 2017. Refactoring is done directly in the editor.

ok, but 301 redirections are better than 404. shouldn't we redirect folks looking for that topic to https://docs.microsoft.com/visualstudio/vb-ide/refactoring-vb?

@mairaw For the Refactoring Dialog topic, would you suggest leaving the old topic and redirecting to MSDN?

I think they should go to related content in the latest version. If the dialog doesn't exist anymore, shouldn't they just go to that topic you're linking to on the vs docs?

No, if they're linking to that topic they are most likely using an older version of VS. The instructions in the new Refactoring topics only work on VS 2017.

I'll leave it up to you if you want to redirect people to the old behavior or the new behavior (my vote would be for the new one). The redirect works with full URL redirection too according to the docs.


EnvironmentPlugin: destructuring process.env doesn't work

Do you want to request a feature or report a bug?
report a bug

What is the current behavior?
Destructuring process.env doesn't work.
console.log(MY_VAR); logs undefined
Steps to reproduce.
webpack.config.js
const path = require("path");
const {EnvironmentPlugin} = require("webpack");

module.exports = {
    entry: "./main.js",
    output: {
        path: path.resolve(__dirname),
        filename: "bundle.js"
    },
    plugins: [
        new EnvironmentPlugin(["MY_VAR"])
    ]
};

main.js
const {MY_VAR} = process.env;
console.log(MY_VAR); // logs undefined
console.log(process.env.MY_VAR); // logs "test"

command
MY_VAR=test webpack

What is the expected behavior?
console.log(MY_VAR); should log "test"
Node.js version: 8.2.1
webpack version: 3.4.1
OS version: Ubuntu 17.04

@EvgenyOrekhov
With
new EnvironmentPlugin(["API_BASE_URL"])

Running node bundle.js I'm getting
undefined
undefined

With
new EnvironmentPlugin(["MY_VAR"])

I get the documented output of
undefined
test

Should the webpack.config.js have new EnvironmentPlugin(["MY_VAR"])

@ismail-syed Yes, sorry, copy-paste error.

That's because under the hood, EnvironmentPlugin uses DefinePlugin to perform text replacement, which means that it only swaps the text process.env.MY_VAR for whatever the value is. It isn't smart enough to figure out you're actually using the variable.

Any news here since summer 2017 ?
Just bumped into the problem and it's kind of (very) annoying when you have dozen of env variables (literally).
Will try to work on a PR if nobody's on it.

I'm still waiting

i have a similar issue i think?
i have code like:
if (process && process.env && process.env[key]){
    json = process.env[key];
}

i currently use the webpack.DefinePlugin as such:
new webpack.DefinePlugin({
    'process.env': {
        MY_CONFIGS: JSON.stringify(process.env.MY_CONFIGS)
    }
})

which ends up replacing every instance of process.env with:
Object({ MY_CONFIGS: '{"stuff": "things"}' })

where '{"stuff": "things"}' ends up being a more significant json string.
is there a way to simply set a key on process.env without replacing every usage with the value?

@busticated
new webpack.DefinePlugin({
    'process.env.MY_CONFIGS': JSON.stringify(process.env.MY_CONFIGS)
})

@lutzk - that's what i thought as well but since i'm doing a dynamic lookup - process.env[key] - webpack never actually sees the process.env.MY_CONFIGS token and thus cannot replace it.

ah ok that might be
but in your example you replace the whole process.env obj:
youre telling the plugin to set 'process.env' = { MY_CONFIGS: JSON.stringify(process.env.MY_CONFIGS) }
thats why process.env is then Object({ MY_CONFIGS: '{"stuff": "things"}' })

Had this working with envify / Gulp. Moving to Webpack breaks all that..

I know the people asking for what's up or say +1 are annoying but this is "P2: Very Important" issue yet there is no update for 2 years now so @sokra or the rest of the maintainers what do you think about this issue. Maybe fix it in the V5 ?
Why not replacing process.env by an object instead of replacing process.env.NAMEOFTHEVARIABLE ?

Automatic Node.js Polyfills removed in webpack@5, see https://github.com/webpack/changelog-v5#automatic-nodejs-polyfills-removed

@vankop Hi! what if someone still wants to use webpack<5? i know it's something related to compilers/transpilers (e.g. babel), but any ideas on how to solve this?

@xeptore can you provide reproducible test repo with example of the problem?

@evilebottnawi of course, here is the link to it:
https://gitlab.com/the-xeptore/sandbox/webpack-env-destruction
sorry for late response.

@xeptore To be honestly it is the bug and feature, EnvironmentPlugin (and EnvironmentPlugin) just find something.other.value and replace it on provided value, so destructuring is not working, but I think we can improve it

@evilebottnawi yes. it's replacing based on tokens, and destructing is not exactly what it should replace. i play around with parsed version of both examples in this gist and it doesn't seem to be much difference between those trees. maybe one step further :)

Hello,
Why not just defining the process variable ?
Since it doesn't exist in browser, it will not create any conflict.
Thanks

closing in favor of https://github.com/webpack/webpack/issues/14800
pls track problem there


Feature request: Easier CLI concept regarding release name

The 'release name' concept is sometimes to inconvenient to use.
helm install [CHART] [flags] --name <name>

helm upgrade [RELEASE] [CHART] --install --name <name>

The problem are the auto generated release. They are mostly none-sense words which give no information about what resource if for.
I think it were easier if (one or more of):

The package developer can apply a default release name (short name of what the package is about)
The user can specify a release name in the values file to stick always with the same name

It would be better because:

On this way you stop accidently release charts because as default it's always the same release
CLI were easier to use for most use cases

However release names should be reusable by default.
The release name auto generation could be an option '--generate-release-name' - This is much more natural.
This is not a detailed concept about a solution but describes direction of a potential solution and the issue itself.

Until 3.0, no changes can be made to these commands that break backward compatibility. (e.g. if a shell script works one way today, it must keep working that way until 3.0.)
That means:

Autogenerated names must be the default until 3.0 (though the algorithm for generating could change)
If helm install chartname is run twice in a row, it MUST produce two releases

So I've marked this for discussion in the 3.x planning phase. But if you can figure out a way around those two requirements, it could be done sooner.

It would be nice if there was a switch like '-N' to disable the auto-generated names as we tightly control the naming of the releases based on our own charts.  Tonight, I went to install 'grafana' into the monitoring namespace and it ended up being deployed as 'grafana-grafana', where we just want the release and name to both simply be 'grafana'.  There will only ever be one instance in this namespace.  e.g. - this is one of those "I know what I'm doing" kind of switches.  :)
I was hopeful when I saw '--name-template' land, but it didn't provide ability to remove the naming duplication.
If you don't want to expose it as a switch, then an environment variable would be fine, as our helm control is mostly scripted anyhow.

switch that disables auto-generation, coupled with the '-n' switch
switch that specifies the name exactly as given: '-N grafana'
developer environment variable that accomplishes #1 above

any of the above would work for our use case.
Thank  you for your consideration.

@technosophos Any chance my above recommendation would make it into the 3.x series?

+1 for this. The default behavior works, but an extra switch for this would be great.
See http://blog.lwolf.org/post/how-to-create-ci-cd-pipeline-with-autodeploy-k8s-gitlab-helm/ meanwhile for an alternative when doing CI/CD with helm.
Instead of ifs I'd like to be able to simply do helm upgrade --install --values values.yaml --release-name myRelease charts/mychart
TL;DR:
export API_VERSION="$(grep "appVersion" Chart.yaml | cut -d" " -f2)"
export RELEASE_NAME="libr-files-v${API_VERSION/./-}"
export DEPLOYS=$(helm ls | grep $RELEASE_NAME | wc -l)

if [ ${DEPLOYS}  -eq 0 ]; then helm install --name=${RELEASE_NAME} . --namespace=${STAGING_NAMESPACE}; else helm upgrade ${RELEASE_NAME} . --namespace=${STAGING_NAMESPACE}; fi

/remove-lifecycle rotten
Seems a good proposal to me


docs: Create best-practices.md documentation

Relates to:
Eliza community’s best practices documentation

Risks
Low risk. This PR focuses on updating documentation to reflect the latest best practices for submitting pull requests, including pre-review with AI and template usage. No functional code changes are involved.
Background
What does this PR do?
This PR updates the contributing guidelines to include new best practices for pull request submissions. It adds a recommendation for conducting pre-reviews using AI tools, elaborates on the use of PR templates, and emphasizes the importance of squashing commits.
What kind of change is this?

Documentation: This PR add the best practices documentation to streamline the contribution process and make it more consistent for all team members.

Documentation changes needed?
My changes require an update to the project documentation. The best practices guidelines have been added to include instructions about using AI tools for pre-review, PR templates, and squashing commits. All updates have been made accordingly.
Testing
Where should a reviewer start?
Review the updated sections on "Pre-Review with AI," "Pull Request Templates," and "Squashing Commits" in the best-practices documentation.

Can you create issues for the tests that failed ? Thanks


Added ViewEngine / Layout support

Hi, I've removed the MVC specific stuff. I'll set that up in a second project.

Thanks - sorry for the delay, I am on vacation and only occasionally checking the computer. :)

Can you let me know when you've set up the second repo? Would like to see it & link to it!

Hi, the repo is here: https://github.com/mcintyre321/Handlebars.Net.Mvc
Thanks!


Adding button to show wrong/right questions

Show a button so if someone wants to try the moodle it's possible

Related to https://github.com/jovit/fy-moodle/issues/15

solves https://github.com/jovit/fy-moodle/issues/16


Completed Everything

@mdhishaamakhtar solve the issues pointed out by the bot

Those issues are there in our readme template itself. Anyway I will solve it

All changes made


Failed to initialize Zoom SDK

whenever I try to make any action like joining a meeting or creating a meeting  I got this error
Failed to initialize Zoom SDK
is anyone ca help me solving this issue ?

hey did you solve this issue ?


Add Generate Kubernetes YAML blog post

Proposed changes

Unreleased product version (optional)

Related issues (optional)

@spara Do you want to give this a read before it gets merged?