Updates user manual with new Windows installation process

The "Preparing a Windows System for RAVEN" section in the User Manual is revised by this merge to reflect the updated install procedure that uses native Windows Python language, packages, and compiler.
Refs #178

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code.
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[x] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[x] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[x] 8. If an analytic test is changed/added is the the analytic documentation updated/added?

Can you wait to merge this so I can add my modifications on the Linux and Mac part?

@bobkinl @joshua-cogliati-inl I updated the portion of the manual for Linux and MAC.
It is good to be reviewed now.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code. no computer code
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts). no syntax
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details. no computer code
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass. ok
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True. n/a
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync. n/a
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done. #178
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added? n/a

PR can be merged.


BIGTOP-3438. Upgrade protobuf-2.5.0 to 3.7.1 for Hadoop-3.3.0.

https://issues.apache.org/jira/browse/BIGTOP-3438
While Hadoop uses protoc-maven-plugin and v3.7.1 supports aarch64 and ppc64le, we still need locally installed protobuf for building libhdfspp. see HDFS-14900.

locally tested this on Rocky Linux 8 (x86_64) and Ubuntu 18.04 (aarch64).

+1
Tested it on Arm64 Debian10/11 and also successfully built out docker images ( bigtop/slaves:debian-10/11-aarch64).

Thanks, @iwasakims


tensorflow 1.2 release will support python 3.6？

tensorflow 1.2 release will support python 3.6？

Would love to know this too....

Closing as a duplicate of #6999


Frontend : HTML Style Attribute

Description 📜

I want to work on making documentation on  HTML Style Attribute  with its example code and output .
Please /assign this to me.

Domain of Contribution 📊

[x] Frontend Dev (HTML, CSS, JS)

/assign

May I work on this issue.
Name- Anshita Sharma
Batch- 7

/assign

/assign

/ assign

FrontEnd

@sifa123 can you please add the frontend labels to this issue

/assign

@sifa123 i have submitted a PR. Please Kindly review it.


Where can I find full list of Google Libraries and their docs (gapi libraries)?

Google JavaScript API reference is very poor. For example, gapi.load method. It says it accepts libraries as a string, but no any links to examples or any explanation what libraries are there, how they use it.
Where can I find full list of Google libraries and reference on how to use them

SO https://stackoverflow.com/questions/50695454/where-can-i-find-google-library-list-and-their-reference-gapi-libraries

Hey @wzup,
It looks like your question may have been answered on Stack Overflow. Are you still in need of help?
Thanks!

the SO page gives Page Not Found
it would be nice if google could answer this and improve their documentation

Could someone say where we can find that list?

I'm SO page is broken. Can someone post the answer here? I'm looking for the same information.

bump

Still an issue 😢


Flexbox layout support

fix #166
@meowgorithm @muesli This is not ready to be merged, but I'd like to have your opinion on it.
For some context, I'm the author of https://github.com/MichaelMure/git-bug.  Also by necessity (as Charm didn't exist or barely at that time), https://github.com/MichaelMure/go-term-text (equivalent of muesli/reflow, muesli/ansi) and https://github.com/MichaelMure/go-term-markdown (equivalent of charmbracelet/glow). Nowadays I'd like to transition to or leverage Charm for git-bug.
I nerd sniped myself into implementing this for two reasons:

to get a better sense of the Charm ecosystem (and what best for that than the hard way)
because I thought it was cool

As such, well, job done. I scratched that itch, and I'd be fine if this is not merged if it doesn't fit this project goals.
Now, onto the actual meat of this:
I find the idea of mirroring  CSS to be brilliant. It's one of those things that makes so much sense retrospectively. I sense however that lipgloss currently fall a bit short how its promise (or what I expected that promise to be): what makes the web model great for interfaces is CSS and HTML. Cascading style sheets and a hierarchy of content and containers.
What I mean by that is that lipgloss is great for styling and make a decent attempt at shaping content (width/height, alignment...),  but fell quite  short for laying out. JoinHorizontal and JoinVertical provides the beginning of that, but it's quite primitive: they lead to a world where we keep doing math with sizes, remaining space, and assembling fragment manually.
This is IMHO limiting, and why I toyed with this idea of flexbox. What if we had strong layout support, directly in the bedrock that lipgloss is? We could easily build interfaces where containers would grow and shrink nicely, or wrap and adapt if the available space is not enough. We'd get powerful capabilities for spacing containers, adapting their flow into columns, rows, changing their order ... and all that would be as easily tweak-able as a style.

I can see that happening in two ways:

Consider lipgloss as CSS and HTML. Style would learn to have children styles (thus making a hierarchy of content). Style.SetString() would become a first-class way to set content. Style.Render() would learn to layout children (classic layout, flexbox, or even CSS grids).
Keep a separation between styling and content. We'd have another base primitive to represent content and hierarchy. That would define containers and texts. Each of those would have a Style attached to set styling and layout properties. That new primitive would know how to leverage the layout functions like JoinHorizontal, flexbox ... to do the final render.

This hierarchy is a requirement, because a single layer of layout is still limiting. This page layout image I used higher is actually two flexbox. As the article container grow, it pushes the footer down. If the global container get squished, it might squish that article. A recursive layout is necessary to have those interactions both way.
I've included a toy program in test-flexbox to get a sense of the capabilities. You might still see some issues popping up. Also, not all flexbox is implemented.

The second idea could be something like that (largely pseudo code):
type Container struct {
	Style
	children []*Container
}

func (c *Container) PushFront(child *Container) {
	c.children = append([]*Container{child}, c.children...)
}

func (c *Container) PushBack(child *Container) {
	c.children = append(c.children, child)
}

func (c *Container) Render() string {
	// Step 1: cascade/inherit styles

	// TODO

	// Step 2: render
	switch c.GetDisplay() {
	default:
		fallthrough
	case DisplayBlock:
		return JoinVertical(Left, c.children)
	case DisplayFlex:
		return Flexbox(c.style, c.children)
	}
}

Nice work on the layout management! I guess I'll need a bit more time to digest all of this and play with it, before I can provide some proper feedback. Looks cool at first glance, tho! :smiley:

FWIW I tried to build a decently complex Charm app and hit the same problem that @MichaelMure did, with styling+layout being the same thing in lipgloss. A core reason this is problematic is because only a child knows how to reflow its contents, but the parent will be the one determining the sizes. If all the parent gets from the child is a string, then it can't do things like preserve padding, border, etc. in an intelligent way.
In my case, I ended up going a bit deeper and built https://github.com/mieubrisse/box-layout-test , which implements a two-pass component/layout system (like how sizing works in the browser) on top of bubbletea. Basically, step one is to get all the items' desired sizes, and then step two is to actually fit them within the viewport. Definitely still in-progress, though I think I have the mechanics working well.
Regardless of what the implementation is though, definite +1 to Michael's point that having styling & layout be the same in bubbletea is a big hindrance.


add attach to renderer

add the missing 'attach to render' task, without this, breakpoints in core won't be hit.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.002%) to 42.04%

Totals

Change from base Build<PHONE_NUMBER>:
-0.002%

Covered Lines:
26394

Relevant Lines:
56916

💛  - Coveralls


Readme example of use base url fix.

Codecov Report

Merging #15 (1b3c0c4) into main (8be2cd9) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #15   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           55        55
=========================================
  Hits            55        55

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 8be2cd9...1b3c0c4. Read the comment docs.


GraphQL Int doesn't work in variables

🙂 Expected behavior
Given the following query:
query getInput($inputIndex: Int!) {
  input(index: $inputIndex) {
    blockNumber
  }
}

And the following variable:
{
  "inputIndex": 0
}

The expected output is:
{
  "data": {
    "input": {
      "blockNumber": "38"
    }
  }
}

🫠 Actual behavior
However, this is the answer we get from 1.0.1:
{
  "errors": [
    {
      "message": "Variable \"$inputIndex\" got invalid value. Expected \"Int\".",
      "locations": [
        {
          "line": 1,
          "column": 16
        }
      ]
    }
  ]
}

🧪 Minimal test case
The test case was described above. It is possible to run it with rollups examples.
🌎 Environment
This bug was introduced in Rollups 1.0.1
✔ Possible solutions
The bug is because of https://github.com/cartesi/rollups/commit/d4a662eee419ea6ebaec25b1ff82e636320affa4.
The JSON integer values are parsed as 64-bit integers, even if the value fits in a 32-bit integer. We should revert the part of the change that affects variables.

Solved by https://github.com/cartesi/rollups/pull/239


Update Banner in README.md

Feature request-
Update the banner or design a new banner for the project with name WordNook

Note:

Do mention if your are working under GSSoC'21.
If you want to work on an issue, you should check if it has already been assigned to anyone. If the issue is free you can comment /assign to get the issue assigned to you.
If you are raising a new issue and want to work on it then also you should comment /assign under the issue to get it auto assigned.
Please refrain from adding labels to your issue/pull-request on your own. It is the job of the Project Admin and the Mentors to review your issue/pull-request and add labels accordingly.
According to the level of the issue, respective time will be allotted under which the task needs to be completed/resolved by the assigned person. If the issue is not resolved within the given time, it will be assigned to the next person. In case of any discrepancies, the decision of the maintainer will be final.

level - 0: 2 days
level - 1: 3 days
level - 2: 4 days
level - 3: 5 days

I can add a banner / gif. I am quite good at this :)

/assign

@aditisneh still working on this ?


Toolchain: Rollup doesn't fail

Just a note, if the rollup step fails (due to being unable to load dependencies), it still seems to create a file. This is bad because subsequent runs of the makefile assume the rollup output is correct.
Fix would be to make rollup output to an intermediate file, and do a copy immediately after (assuming it's just not misconfigured).

Rollup now fails.


Add super secret stuff shhhhhhhhhhhhhhhhhhhhhhhhhhh

Stuff you need to bother an officer to get them juicy, juicy details

perhaps we just dont add this anywhere in the wiki, and keep it through word of mouth. or else it wouldnt b super secret

I agree 👌


⚠ Bofrost.lu has degraded performance

In 7b28a79, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 3243 ms

Resolved: Bofrost.lu performance has improved in 1edf41d after 9 minutes.


enhanceImprove the speed of obtaining table snapshots (#40717)

pick: https://github.com/apache/doris/pull/40717

run buildall

run p0


docs: add end-to-end tutorial on easy active learning in mnist

Uff, trying to fix the GH upload problem I merged the branch with main instead. The only commit to review is this one: https://github.com/encord-team/encord-active/pull/288/commits/6a65feb7f25d9eff38adb3922ce8cedf3294ca03


Mac OS X compilation error

Scanning dependencies of target jvar
[  8%] Building CXX object CMakeFiles/jvar.dir/src/str.cpp.o
[ 16%] Building CXX object CMakeFiles/jvar.dir/src/util.cpp.o
jvar-master/src/util.cpp:58:23: error: use of undeclared identifier 'CLOCK_MONOTONIC'
if (clock_gettime(CLOCK_MONOTONIC, &ts))
^
1 error generated.
It seems clock_gettime(CLOCK_MONOTONIC, &ts) is not implemented in mac os x
http://stackoverflow.com/questions/5167269/clock-gettime-alternative-in-mac-os-x

dk547, thanks for reporting the issue.  I don't have a mac to test... but I believe following should work..  Will you be willing to try it out and let me know?  You can also simple disable the getTickCount() function as it is not used for anything critical--just for measuring elapsed time...
#ifdef APPLE
#include <sys/timeb.h>
#endif
ulongint getTickCount()
{
#ifdef APPLE
timeb tb;
ftime(&tb);
return tb.millitm + (tb.time & 0xfffff) * 1000;
#else
struct timespec ts;
if (clock_gettime(CLOCK_MONOTONIC, &ts))
{
    return 0;
}
return (ts.tv_sec * 1000) + ts.tv_nsec / 1000000L;

#endif
}

Yep, this code seems OK.
One more thing:
library not found for -lrt
To link the library I removed -lrt from CMakeLists.txt

fixed


feat: support selects in modals

Summary

Readds modal selects. continuation of #558, #598
Checklist

Closing this for now, since there haven't been any updates on this from Discord's side for some time now, unfortunately; it was disabled a while ago, and was never officially documented.
Once Discord finalizes and releases the feature, we can take another look at this


EXEC_BAD_ACCESS in subscriptionExpirationDate

I just got anfatal error: unexpectedly found nil while unwrapping an Optional value for this code:
    public var subscriptionExpirationDate: Date
    {
        assert(isRenewableSubscription, "\(productIdentifier) is not an auto-renewable subscription.")

        return subscriptionExpirationDateString!.rfc3339date()
    }

This is caused by accessing an InAppPurchase an expired subscription (date-string is empty).

@rpitting Just pushed a new version with a fix.
Thank you.


Use bevy's suggested pattern for configuring plugins to configure the GenerationPlugin

See the recommended pattern here: https://github.com/bevyengine/bevy/pull/6336

In our particular case, this might end up being the same thing, because we have to pass the configuration variables to systems, which can only happen through resources?

Okay, yeah, I think this pattern is useful for passing data to the build function of a plugin, but it is not useful for passing data that is then going to be transferred to various systems.
One could set things up so that the GenerationPlugin has a config: GenerationConfig field on it. This structure can then be used for resource initialization. I'll make a PR that does this.


chore(ci): make use of yarn

Current coverage is 86.74% (diff: 100%)

Merging #18 into master will not change coverage

@@             master        #18   diff @@
==========================================
  Files            16         16
  Lines            83         83
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits             72         72
  Misses           11         11
  Partials          0          0

Powered by Codecov. Last update d86bba6...a5bdb1f


Veteran/Legendary/Intermediate Tags Removed

system_legend and system_trust_legend has been removed from Docs.
system_trust_intermediate and system_trust_advanced still need to be removed.

Resolved by #114


FORMS-237 # datetime/time with picker/native has broken model-view binding

for datetime, set date to 0000-00-00 in case time has valid value
for datetime, set time to 00:00 in case date has valid value
created tests to confirm binding.

I don’t know whether this should be attempted within the current work, but having “magic” values like 0000-00-00 and 00:00 can be problematic. That’s a real date and real time that one-day someone will want to use, but it’ll break because we have assigned special purposes for those values.
Ideally, we shouldn't have any code that checks for "0000-00-00" or "00:00". The complete value is either valid or invalid, without special treatment of certain values.
I think it makes sense for a date+time field that has a date but no time (e.g. 2015-01-01T), to automatically set the time part to 00:00. Automatically setting an empty time part to some value like this might help the user, especially if they don't care about the time part.
I don't think there's any valid assumption we can make about a date+time field that has a time but no date (e.g. T12:34).
I wonder if date, time and date+time views shouldn't send anything to the model unless it's complete?
That'll mean that the model will stay empty, failing REQUIRED validation if any, right up until the user puts in a completely valid value. And it means we wouldn't need to check for "0000-00-00" or "00:00" during validation.
What do you think?

LGTM
tests look like they cover the issue.
working with date and times is always painful :O
I actually think it would be easier if we had separate models and views for date, time, datetime as they are separate concepts, however that is not the focus of this ticket, and I dont know if the definition we use would allow for this... food for thought

why not null instead of the magic values?
there could be a problem with time of 00:00 for time but i think we'd be safe with 0000-00-00 for date

Yeah, I was mostly thinking out loud about ideals and purity. I don't think it's necessary to eliminate magic values within the scope of this Issue. I do think it's important to identity such magic values and get people thinking about alternatives.
LGTM :+1:


Removed confusing _INPUT suffix

Few things:

INPUT_FOLDER uses INPUT_PATH variable (should be one or another). Also way INPUT_PATH is currently interpreted required to start with / and then being treated as relative to SCRIPT_DIR is confusing. For now, would probably go with something like:
export INPUT_FOLDER="${INPUT_FOLDER:-"$SCRIPT_DIR"/../input}"
Username could be detected by shell (I have not tested in msys2/cygwin)
export CURRENT_USER_NAME="${CURRENT_USER_NAME:-$USER}"
when it comes jdk version I would probably accept both OTOOL_JDK_VERSION and JDK_VERSION
export OTOOL_JDK_VERSION="${OTOOL_JDK_VERSION:-${JDK_VERSION:-11}}"

Also current code has some problems when INPUT_FOLDER or  RESULTS_FOLDER_NAME are relative. But that is probably out of scope of this PR.

Ok, so problem seems to be, that testsuite does not like relative paths. However if  test  canonizes paths using:
export RESULTS_FOLDER="$( readlink -m $RESULTS_FOLDER )"
export INPUT_FOLDER="$( readlink -m $INPUT_FOLDER )"

Wrapper can simply do:
export RESULTS_FOLDER="${RESULTS_FOLDER:-results}"
export INPUT_FOLDER="${INPUT_FOLDER:-input}"

And default wrapper behavior does not change (when launched from repo root).
See my experiment (without comments/README changes):
https://github.com/zzambers/WindowsTPS/commit/8335e73c2f5788062e70bf91cb753bba7c8e697d

Fixed by #30


Create a formsflow Dashboard for management to view form submission stats

Could we have a dashboard built within formsflow to allow management to use when reporting on forms flow stats.
Stats to be generated:

total forms in the Review and Process Forms tab
total forms in the Submitted Forms tab
total draft forms in the Drafts tab

Closing Rolling into #1165


Update Registration process to include data from org-id.guide

[x] Registration page uses data from org-id.guide in "Organisation Registration Agency" list
[x] "Add Agency" link is removed now

[x] Settings page https://aidstream.org/settings uses org-id.guide data
[x] A script is developed that pulls the json data from the org-id.guide and stored locally.
[x] that "org-id.guide data" import script is placed in cron for daily updates

NOTE
PO element is already using org-id.guide list, we need to use them in registration process as well.

Anjesh dai,
This enhancement has been managed.
Thanks.
Regards,
Karuna


Exogenous variables normalization

When I set the scaler_type parameter, does it also normalize exogenous variables?
If not, should we normalize them? For each time series (so for each unique_id) or globally across the whole dataframe?
Thanks @kdgutier

Hi @candalfigomoro,
Thanks for using the library, in this link we explain the normalization strategies available with the NeuralForecast architectures:
https://nixtla.github.io/neuralforecast/common.scalers.html
You may also do your own normalization process outside of the fit, predict methods.

@kdgutier
Thanks!
When I use the Poisson loss (loss=DistributionLoss(distribution='Poisson', level=[80, 90], return_params=False)) I can't really normalize the y target (since it is "count data"). Is there a way to only normalize exogenous variables?

Hi @candalfigomoro,
You can use NeuralForecast's builtin scaler_type initialization argument, that simultaneously normalize the inputs and train against the original y data.
Here is the scalers documentation:

https://nixtla.github.io/neuralforecast/common.scalers.html

Here is an example where we fit zero-inflated count data:

https://nixtla.github.io/neuralforecast/examples/intermittentdata.html

Let us know if this solves your problem.

Hi @kdgutier,
in my previous message I was not very clear. This is the problem:
I have a dataset with the unique_id, ds and y columns (and some exogenous variables). Unfortunately, I can't share the dataset. Values in y are >= 0 (they are count data).
I'm trying these models:
models = [
    NHITS(
        h=horizon,
        input_size=2 * horizon,
        scaler_type='robust',
        futr_exog_list=futr_exog_list,
        #stat_exog_list=stat_exog_list,
        max_steps=100,
        loss=DistributionLoss(distribution='Poisson', level=[80, 90], return_params=True),
    ),
    NBEATSx(
        h=horizon,
        input_size=2 * horizon,
        scaler_type='robust',
        futr_exog_list=futr_exog_list,
        #stat_exog_list=stat_exog_list,
        max_steps=100,
        loss=MAE(),
    ),
]

Let's focus on the NHITS model (notice scaler_type='robust').
When I use a loss function such as MAE or MSE, it works.
When I switch the loss to DistributionLoss(distribution='Poisson', level=[80, 90], return_params=True) I get the following error when I call fit():
ValueError: Expected value argument (Tensor of shape (1024, 12)) to be within the support (IntegerGreaterThan(lower_bound=0)) of the distribution Poisson(rate: torch.Size([1024, 12])), but found invalid values:
tensor([[ 7.,  2.,  4.,  ...,  4.,  1.,  4.],
        [ 5.,  1.,  2.,  ...,  0.,  0.,  0.],
        [ 4.,  3.,  1.,  ...,  0.,  0.,  0.],
        ...,
        [ 0.,  0.,  0.,  ...,  0.,  0.,  0.],
        [27., 38.,  0.,  ...,  0.,  0.,  0.],
        [ 0.,  0.,  0.,  ...,  0.,  2.,  0.]])

However, the error disappears when I remove scaler_type='robust'. It looks like the scaler is generating some negative value when it shouldn't (the minmax scaler is also not working).
The funny thing is that, If I also remove futr_exog_list, I get this other error after about 5 mini-batches of training:
ValueError: Expected parameter rate (Tensor of shape (1024, 12)) of distribution Poisson(rate: torch.Size([1024, 12])) to satisfy the constraint GreaterThanEq(lower_bound=0.0), but found invalid values:
tensor([[nan, nan, nan,  ..., nan, nan, nan],
        [nan, nan, nan,  ..., nan, nan, nan],
        [nan, nan, nan,  ..., nan, nan, nan],
        ...,
        [nan, nan, nan,  ..., nan, nan, nan],
        [nan, nan, nan,  ..., nan, nan, nan],
        [nan, nan, nan,  ..., nan, nan, nan]], grad_fn=<SoftplusBackward0>)

So, basically, the only working combination to make the Poisson loss work is:

Don't use any scaler (otherwise I get the the IntegerGreaterThan(lower_bound=0) error)
Include some exogenous variable (otherwise I get tensors with NaN after some mini-batches of training)

I don't have these issues if I use the MAE() or MSE() loss.
Thanks

@kdgutier
Decreasing the learning rate helps with the all-NaN tensors (exploding gradients?). Still, there's the problem with scaling and the IntegerGreaterThan(lower_bound=0) error.

Hi @candalfigomoro,
Glad to know that reducing the learning rate helped with the exploding gradients.

After changing the activation and the learning rate is the NHITS+Poisson giving you reasonable results?
Or do we still need to check carefully the interactions between scaler_type and Poisson distribution?

@kdgutier Thank you very much!
Using the Poisson distribution seems more stable now (unfortunately it doesn't seem to provide good results with my forecasting problem, so I'll try to play with other losses such as the Negative Binomial).


Unit tests failing because of capability dependency bugifx

Capability dependencies are updated to allow SubgroupSize and SubgroupLocalInvocationId with SubgroupBallotKHR:
https://github.com/KhronosGroup/SPIRV-Headers/pull/57
I believe this is the cause of unit test failures like:
[ RUN      ] BuiltIn/EnumCapabilityTest.Sample/33
/home/travis/build/KhronosGroup/SPIRV-Tools/test/operand_capabilities_test.cpp:56: Failure
Value of: ElementsIn(CapabilitySet(entry->numCapabilities, entry->capabilities))
Expected: is equal to { 6 }
Actual: { 6, 4423 }
capability value 36
(Kernel is 6, and SubgroupBallotKHR is 4423)

FYI @s-perron @antiagainst

#1319 for fixing this


pipelines: enhance API documentation

Here is a description of the new CRUD operations of pipeline templates, and also the use of a template.
Use pipeline template
Uses a stored pipeline template on a given NIF or plain text input.
Method: POST
Endpoint: /pipelining/chain/{id}
id: Path parameter: id of the pipeline template to use.
Content-Type: HTTP Header parameter, can be one of text/turtle, application/json, application/ld+json, application/n-triples, application/rdf+xml, text/n3, text/plain, depending on the body.
Body: The input for the pipeline chain. This can be a NIF or plain text document.
Responses:

200 OK with the output of the last request in the pipeline chain in the body.
400 BAD REQUEST if the request cannot be processed.
401 UNAUTHORIZED if the user is not logged in.
404 NOT FOUND if the requestes template is not found.
500 Internal Server Error if something unexpected goes wrong.

Create pipeline template
Creates and stores a pipeline on the server the request is sent to.
The response contains the id of the created pipeline, which is to be used in further methods.
Method: POST.
Endpoint: /pipelining/templates/.
Content-Type: HTTP Header parameter, should be application/json.
persist: Optional parameter: values can be true or false. Indicates whether to persist the pipeline forever (true) or for just one week (false). If not given, it defaults to false.
visibility: Optional parameter: values can be PRIVATE or PUBLIC. A template with visibility PUBLIC is visible and usable by anyone. A template with visibility PRIVATE is only visible and usable by the owner. The default value is PUBLIC.
Body: The pipeline template as JSON string: It represents an object with a label, a description and a list of request objects. Example:
{
  "label": "Spotlight-Link",
  "description": "Recognises entities using Spotlight en enriches with geo information.",
  "serializedRequests": [
    {
      "method": "POST",
      "endpoint": "http://api.freme-project.eu/current/e-entity/dbpedia-spotlight/documents",
      "parameters": {
        "language": "en"
      },
      "headers": {
        "content-type": "text/plain",
        "accept": "text/turtle"
      }
    },
    {
      "method": "POST",
      "endpoint": "http://api.freme-project.eu/current/e-link/documents/",
      "parameters": {
        "templateid": "3"
      },
      "headers": {
        "content-type": "text/turtle",
        "accept": "text/turtle"
      }
    }
  ]
}

The fields of the returned object are:

label: The name of the pipeline template.
description: a description of the pipeline template.
serializedRequests: the chained requests as described in /pipelining/chain.

Responses:

200 OK with the generated pipeline. The id, persist parameter and visibility are included in the body if everything goes well. E.g.:

{
  "id":<PHONE_NUMBER>051,
  "label": "Spotlight-Link",
  "description": "Recognises entities using Spotlight en enriches with geo information.",
  "persist": false,
  "visibility": "PUBLIC",
  "owner": "userwithpermission",
  "serializedRequests": [
    {
      "method": "POST",
      "endpoint": "http://api.freme-project.eu/current/e-entity/dbpedia-spotlight/documents",
      "parameters": {
        "language": "en"
      },
      "headers": {
        "content-type": "text/plain",
        "accept": "text/turtle"
      }
    },
    {
      "method": "POST",
      "endpoint": "http://api.freme-project.eu/current/e-link/documents/",
      "parameters": {
        "templateid": "3"
      },
      "headers": {
        "content-type": "text/turtle",
        "accept": "text/turtle"
      }
    }
  ]
}

The fields of the returned object are:
* id: the generated id if the template. This is also the timestamp of creation, in milliseconds.
* label: The name of the pipeline template.
* description: a description of the pipeline template.
* persist: if false, the template will not automatically be deleted; if false it will live only for one week. To be implemented.
* owner: the owner, in this case the creator, of the pipeline template.
* serializedRequests: the chained requests as described in /pipelining/chain.

400 BAD REQUEST if the request cannot be processed, e.g. in case of a JSON syntax error.
401 UNAUTHORIZED if the user is not logged in.
500 Internal Server Error if something unexpected goes wrong.

Update pipeline
Updates a pipeline template on the server the request is sent to.
Method: PUT.
Endpoint: /pipelining/templates/{id}.
Content-Type: HTTP Header parameter, should be application/json.
id: Path parameter: the id of the pipeline.
persist: Optional parameter: values can be true or false. Indicates whether to persist the pipeline forever (true) or for just one week (false). If not given, it defaults to false.
visibility: Optional parameter: values can be PRIVATE or PUBLIC. A template with visibility PUBLIC is visible and usable by anyone. A template with visibility PRIVATE is only visible and usable by the owner. The default value is PUBLIC.
owner: Optional parameter: the new owner of the pipeline.
Body: The updated pipeline template as JSON object, as described in Create pipeline template.
Responses:

200 OK with the updated pipeline in the body if all goes well (see Create pipeline template for an example).
400 BAD REQUEST if the request cannot be processed;
403 FORBIDDEN if the user has no permission to update the template.
404 NOT FOUND if the pipeline does not exist.

Read pipeline
Returns the pipeline with the given id found on the server the request is sent to.
Method: GET
Endpoint: /pipelining/templates/{pipelineid}
id: Path parameter: the id of the pipeline.
Responses:

200 OK with the requested pipeline in the body if all goes well (see Create pipeline template for an example).
404 NOT FOUND if the requested pipeline does not exist.

Read pipelines
Returns is list of all visible pipeline templates on the server the request is sent to.
Method: GET
Endpoint: /pipelining/templates
Responses:

200 OK with a list of visible pipelines in the body if all goes well. Example:

[
  {
    "id":<PHONE_NUMBER>610,
    "label": "Spotlight-Link",
    "description": "Recognises entities using Spotlight en enriches with geo information.",
    "persist": false,
    "visibility": "PUBLIC",
    "owner": "userwithpermission",
    "serializedRequests": [
      {
        "method": "POST",
        "endpoint": "http://api.freme-project.eu/current/e-entity/dbpedia-spotlight/documents",
        "parameters": {
          "language": "en"
        },
        "headers": {
          "content-type": "text/plain",
          "accept": "text/turtle"
        }
      },
      {
        "method": "POST",
        "endpoint": "http://api.freme-project.eu/current/e-link/documents/",
        "parameters": {
          "templateid": "3"
        },
        "headers": {
          "content-type": "text/turtle",
          "accept": "text/turtle"
        }
      }
    ]
  },
  {
    "id":<PHONE_NUMBER>765,
    "label": "NER-Translate",
    "description": "Apply FRENE NER and then e-Translate",
    "persist": false,
    "visibility": "PRIVATE",
    "owner": "userwithpermission",
    "serializedRequests": [
      {
        "method": "POST",
        "endpoint": "http://api.freme-project.eu/current/e-entity/freme-ner/documents",
        "parameters": {
          "language": "en",
          "dataset": "dbpedia"
        },
        "headers": {
          "content-type": "text/plain",
          "accept": "text/turtle"
        }
      },
      {
        "method": "POST",
        "endpoint": "http://api.freme-project.eu/current/e-translation/tilde",
        "parameters": {
          "source-lang": "en",
          "target-lang": "fr"
        },
        "headers": {
          "content-type": "text/turtle",
          "accept": "text/turtle"
        }
      }
    ]
  }
]

404 NOT FOUND if the pipeline does not exist.

Delete pipeline
Deletes the pipeline with a given id.
Method: DELETE
Endpoint: /pipelining/templates/{id}
id: Path parameter: the id of the pipeline template.
Responses:

200 OK if all goes well. The body is a text/plain message: "The pipeline was sucessfully removed."
403 FORBIDDEN if the user has no permission to update the template.
404 NOT FOUND if the pipeline does not exist.

I omitted the response examples because they are somewhat self explanatory.


Guardian Admin Panel

REQUIREMENT:
As a user of the Guardian I want to be able to access and Admin Panel where we can enter the user parameters such as SCHEMA_TOPIC_ID, NFT_API_KEY without having to go into the Config Files in The Source Code.
DOD:

UI to update the parameters
Functionality working after updating the parameters
Update the ReadMe file.

We will be allowing users to update user parameters like SCHEMA_TOPIC_ID, NFT_API_KEY.

We also need UI to show System Logs

QA PASSED.

This issue was completed and QA approved on Mar 15th


chainChanged event not detected with WalletConnect

When using metamask through the web3Modal walletconnect provider, if I change the network on metamask after successfully connecting to the dapp the client does not appear to detect the chainChanged event.
// Subscribe to chainId change
provider.on("chainChanged", (chainId: number) => {
  console.log(chainId);
});

How to solve this problem？

I have tried networkChanged event too, but it only works when I change my wallet address and always gives undefined value.
If anyone know any solution can you please help.

connector.on("session_update", () => {}); doesn't work also

https://github.com/MetaMask/metamask-mobile/issues/2927

Same issue over here.

Do you use ethers or web3js?
The web3js seems to have the events, but not ethers

We are using web3js

With stable version 2.0.0 of Web3Modal now released, we are officially dropping support for version 1.x
Due to this this issue/pr was marked for closing. It is highly recommended to upgrade as 2.x will be receiving further updates that will enable functionality for some of our newer sdks like auth and push as well as support for WalletConnect v2 (See this post about WalletConnect v1 being deprecated https://medium.com/walletconnect/walletconnect-v1-0-sunset-notice-and-migration-schedule-8af9d3720d2e)
If you need to continue using Web3Modal 1.x and require this feature/fix implemented, we suggest adding it via forking V1 branch.


Small improvements propositions on the search API

This PR will list some propositions I have concerning the search workflow. I try to isolate each proposition into a single commit to make it easy to review and revert if you do not agree.

I propose to change some attribute names with datetimes. I think Time gives a more accurate hint of the type than Date (e.g. departureTime instead of departureDate, and is more consistent with the timeDelta attribute. I did not change {min,max}DepartureDate, despite also being datetimes  as in practice the date will matter more than the time (from my understanding). Should we change the type here or is it nitpicking?

As departureDate (or departureTime) is an optional parameter, I specified the behavior if omitted in the parameter description.

The price type enum "FREE", "PAYING", "UNKNOWN" is not really self-explanatory. I propose to remove "UNKNOWN", which can be guessed if type is "PAYING" but no amount is specified (optional field). I also mentioned that it is an estimate.

If I refer to the (unmerged) specification document I read "MaaS platforms and carpooling operators MUST support at least one of these 2 flows [deeplink or API] if they implement booking.". If everyone agree with this, I suggest to remove webUrl as a required parameter as it is not necessarily needed if only booking by API is available (I updated the description to notice that it is required to support booking by deeplink).

For consistency with other enumerations, I suggest to put the passengerPickupDay enum options all uppercase.

I find the vocabulary "driverJourney" and "passengerJourney" confusing. I also wonder if there is a semantic difference between "Journey" and "Trip". I haven't made any change on this, opened an issue instead (#24).

Hi @pierrecamilleri ,
Thank you for your proposals:
1- I can agree that departureTime is more explicit but this has previously been discussed in the GT and we decided to stick to departureDate. @adelcasse @osarrat @riclage what do you think?
2- 👍
3- 👍
4- 👍
5- 👍
6- To be discussed further (in the related issue)

Agree with @ccyrille .
I'm not generally a fan of implicit behaviors because it leaves things open to the interpretation of the implementation. If searching for "now", what's the harm in passing the time in the next 10 or 30 minutes depending on the searcher requirements for "now"?
Could we maybe consider removing the enum altogether? If it's free, the price will be 0, right?
👍
👍
I added a comment on the linked issue.

As discussed today :

Has already been discussed, so I'll revert it.
Ok for an explicit behavior as suggested by @riclage
After discussions, it seems that redundancy may not be totally unnecessary as the question of pricing is a difficult one, and having the type field may help to clear up edge cases. However, the current description does not apply well for deeplinking and needs to be revised accordingly.
Has not been discussed and no action will be taken.

As decided today after reviewing this PR live, I merge this without waiting for new reviews after my last changes.


add the img for the projects

closes #333
we added a key-value in the projects.json file with a new key: screenshot

Great PR!! How did you come up with such an amazing solution


Historical module removed by mistake?

Bug Report
Describe the bug
It seems that: https://github.com/gadicc/node-yahoo-finance2/commit/4603232698e168c8893a275828b860fece748f1f#diff-1053484f5a0528ed4685340b3a56e56da363fb9e32229da71e2d8d30537d63fd
has remove the historical module by mistake?

Oops... my mistake. This is a very unintended regression. Created #201 to fix.

@PythonCreator27, haha, looks like we both took this on at the same time...  but I beat you by about 1m ;)
@okomarov, thanks for reporting and for hunting this down!
Funny that we have over 1,000 tests and none of them check that we actually include all the modules :sweat_smile:   Guess we should add an integration test for it.

Fixed in f75040206bf23ce4446f87066633423424348efc

:tada: This PR is included in version 1.12.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


watchOS simulator build failed in Xcode 12.0 beta

missing required architecture x86_64 in file .../Pods/Realm/core/librealmcore-watchos.a
macOS 11 beta, Xcode 12 beta, succeed as physical device

Hi @FAN-WEIJIA
We are currently working on a fix for this: https://github.com/realm/realm-core/pull/3784
Thanks,
Lee

Has this issue been resolved in https://github.com/realm/realm-core/pull/3784? I still got build issues with Carthage and commit "5fb7651"
/src/sync/sync_user.cpp -o /Users/dennis/Library/Caches/org.carthage.CarthageKit/DerivedData/12.0_12A6159/realm-cocoa/5fb765106f0978735b350504d78c6f5b08457c23/Build/Intermediates.noindex/Realm.build/Release-watchsimulator/Realm.build/Objects-normal/x86_64/sync_user.o
In file included from /Users/dennis/Development/Private/DaftCloud/Carthage/Checkouts/realm-cocoa/Realm/ObjectStore/src/sync/sync_user.cpp:21:
In file included from Realm/ObjectStore/src/sync/impl/sync_metadata.hpp:24:
In file included from core/include/realm/obj.hpp:22:
In file included from core/include/realm/array.hpp:74:
core/include/realm/realm_nmmintrin.h:125:12: error: GNU-style inline assembly is disabled
    __asm__("pcmpgtq %1, %0" : "+x" (xmm1) : "xm" (xmm2));
           ^
core/include/realm/realm_nmmintrin.h:131:12: error: GNU-style inline assembly is disabled
    __asm__("pcmpeqq %1, %0" : "+x" (xmm1) : "xm" (xmm2));
           ^
core/include/realm/realm_nmmintrin.h:137:12: error: GNU-style inline assembly is disabled
    __asm__("pminsb %1, %0" : "+x" (xmm1) : "xm" (xmm2));
           ^
core/include/realm/realm_nmmintrin.h:143:12: error: GNU-style inline assembly is disabled
    __asm__("pmaxsb %1, %0" : "+x" (xmm1) : "xm" (xmm2));
           ^
core/include/realm/realm_nmmintrin.h:149:12: error: GNU-style inline assembly is disabled
    __asm__("pmaxsd %1, %0" : "+x" (xmm1) : "xm" (xmm2));
           ^
core/include/realm/realm_nmmintrin.h:155:12: error: GNU-style inline assembly is disabled
    __asm__("pminsd %1, %0" : "+x" (xmm1) : "xm" (xmm2));
           ^
core/include/realm/realm_nmmintrin.h:162:12: error: GNU-style inline assembly is disabled
    __asm__("pmovsxbw %1, %0" : "=x" (xmm1) : "xm" (xmm2) : "xmm1");
           ^
core/include/realm/realm_nmmintrin.h:168:8: error: GNU-style inline assembly is disabled
    asm("pmovsxwd %1, %0" : "=x" (xmm1) : "xm" (xmm2));
       ^
core/include/realm/realm_nmmintrin.h:175:12: error: GNU-style inline assembly is disabled
    __asm__("pmovsxdq %1, %0" : "=x" (xmm1) : "xm" (xmm2));
           ^

** BUILD FAILED **


DiscoverCharacteristics not returning promise iOS

The device I'm working against has a service 0000ffe0-0000-1000-8000-00805f9b34fb which is discovered just fine with discoverServices. When I call discoverCharacteristics with that ID the promise never gets returned. I did a little debugging and for some reason in the args for discoverCharacteristics in bluetooth.ios.js the id is coming through as ffe0 but everything seems fine until we get to this if statement.
if (UUID === pUUID && sUUID === args.serviceUUID)
Here the sUUID does not equal args.serviceUUID and this is where the call will hang at.
As far as I can tell I have 2 issues here.

The args isn't coming through properly.
The if statement above should return the promise as a reject if it is not met.

@jthottel thanks. Would you l'île to make a PR?

I can make a PR to fix the if statement issue but I still can't explain why on this particular service the arg doesn't get passed correctly.

@jthottel about the id is coming through as ffe0 i think it is a standard behavior for know services/chars in that "namespace". Can you try using ffe0 as serviceUUID?

@jthottel i will close this. Let me know if you still have an issue


Removes what is no longer at opscode-cookbooks

These cookbooks, removed from the regression list, are no longer among those in the Chef Community Cookbooks organization.

Closing this as #348 and #350 should be part of the same commit.


Skins and name changes

If I have IGN OldName and log into Civcraft, then change it to NewName, and then someone else takes OldName and changes the skin, does the skin change on Civcraft for me?

Nope.
On Feb 4, 2015 10:42 AM, "AkariAkaori"<EMAIL_ADDRESS>wrote:

If I have IGN OldName and log into Civcraft, then change it to NewName,
and then someone else takes OldName and changes the skin, does the skin
change on Civcraft for me?
—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/NameLayer/issues/54.


feat: Assign default value to fields and args of type enum with only one value (box/box-codegen#465)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

128 of 250 (51.2%)  changed or added relevant lines in 11 files are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.07%) to 43.84%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/test/commons.generated.ts
0
1
0.0%

src/managers/classifications.generated.ts
7
18
38.89%

src/schemas.generated.ts
89
199
44.72%

Files with Coverage Reduction
New Missed Lines
%

src/schemas.generated.ts
4
38.1%

Totals

Change from base Build<PHONE_NUMBER>:
0.07%

Covered Lines:
7391

Relevant Lines:
12991

💛  - Coveralls


[Feature] Widget pane issues

[ ] It is easier for users to grok text. Unfamiliar icons are not so easy to understand.

[ ] User should be able to pin his fav widgets to the top
[ ] Maybe its better if the user can see the widgets divided into folders logically

@momcilo-appsmith seems like we have covered most of this, Can you please take a look and close it


TypeError in Polygon.del: 'NoneType' object is not callable

Expected behavior and actual behavior.
Expected: Shapely disposes of resources cleanly and without raising exceptions.
Actual: Shapely does some kind of cleanup on the Polygon class which raises a TypeError. According to the Python documentation it's bad practice to mess with __del__ at all. Exceptions raised during __del__ are ignored by the interpreter and printed as warnings. This does not impact functionality but is really annoying and smells of potential memory leaks.
Steps to reproduce the problem.
>>> from shapely.geometry.polygon import Polygon
>>> <Ctrl+D>
Exception TypeError: TypeError("'NoneType' object is not callable",) in <bound method Polygon.__del__ of <shapely.geometry.polygon.Polygon object at 0x109863810>> ignored
Exception TypeError: TypeError("'NoneType' object is not callable",) in <bound method Polygon.__del__ of <shapely.geometry.polygon.Polygon object at 0x10a3e80d0>> ignored

Operating system
macOS Sierra 10.12.3 as well as on alpine linux 3.5; on python 2.7
Shapely version and provenance
>>> from shapely import __version__
>>> __version__
'1.6b4'

Retrieved via PyPi at https://pypi.python.org/pypi/Shapely/1.6b4

@privatwolke I believe you, but I can't replicate the above on my Macbook with Python 2.7.11 downloaded from python.org.
We've dealt with a possibly related issue in the past: https://github.com/Toblerity/Shapely/issues/264. Have you seen this problem with previous versions of Shapely?

Fixed locally for me with https://github.com/Toblerity/Shapely/pull/528

Closed via #528


Failing/Inconsistent E2E: smoke/checkout-flow

smoke/checkout-flow.e2e-spec.ts is inconsistent and therefore fails at times on Jenkins.
Fix the test so it is stable and passes every time.

PR: https://github.com/SAP/cloud-commerce-spartacus-storefront/pull/3174
Unable to reproduce when testing locally but it fails quite frequently on Jenkins and I'm confident that this will fix it. I will be monitoring Jenkins tests after it is merged to confirm the fix.


Clean up stream timeout handling for gRPC windmill streams to prevent…

… incorrect overriding in tests
Please add a meaningful description for your change here

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.

There is no functional change in this PR. The change is only in internal
tests separate from this.
On Wed, Jan 2, 2019 at 2:33 PM Kenn Knowles<EMAIL_ADDRESS>wrote:

Are there any tests of this functionality actually?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/beam/pull/7391#issuecomment-451006178, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AQsmNkgBLIHsuLob47pV87W1PqBnn1cPks5u_TOmgaJpZM4ZnUd9
.

--
Thanks,

Slava Chernyak


update runv to support oci specs

up to oci specs commit dca1dfdd92405129fba7ba0c91cfade2dae1d615

I don't think we need the runv spec command. Even the runc spec is not necessary for the future exec-driver.

The spec runv spec generates may provides some different configuration  with other runtimes.


Add support for double-sided materials

As reported here:
https://community.cesium.com/t/3d-tiles-model-appeared-with-face-orientation-flipped-backface-culling/34155
We previously weren't supporting glTF's doubleSided property. Now we are.
This was tricky because Unity controls this with a render-pipeline-dependent material property. I also had to add some nodes to our CesiumDefaultTilesetShader to flip the direction of the normal for back faces, as required by the glTF spec.
This is a draft because it's not quite working well in HDRP yet. For reasons I don't understand, HDRP defies all attempts to dynamically turn on double-sided rendering dynamically. I have some local changes where I turn it on via the UI, and then I'm able to turn it off dynamically. But I haven't committed that yet because it seems dodgy. Also, unlike the othe render pipelines, HDRP seems to automatically invert normals for back faces, which means my nodes that do that manually are now making the normals wrong again. I'm not sure yet the best way to deal with that.
Fixes #370
Fixes #486

I had hoped to get this PR ready for final review so it can be included in next week's release, but HDRP and I still are not getting along. Will probably need to push it until next release.

Ok I think this is working well now. Double-sided rendering is working in all pipelines. The way it works is that the Shader and Material now have double-sided mode enabled. At runtime, we disable it if the glTF does not require it by setting some material parameters. This seems to work a lot better than the opposite. I'm not 100% sure why, but my theory is that double-sided rendering is a "feature" (at least in some RPs). If the shaders are compiled with support for that feature, then dynamically disabling it at runtime is fine. However, if the shaders are compiled without support for the feature at all, then enabling it dynamically is not possible.
I also fixed cartographic polygons in HDRP by enabling "alpha clipping".

I'm moving this into next week's release, but time is short so we'll move it back out if there are any concerns at all.

Thanks @kring ! I verified that this was working using the TextureSettingsTest sample model.
Just to sanity check, I noticed some seemingly unrelated edits to the material? Some of them seemed like autogenerated additions, but I wasn't sure about this one. Was this done by Unity too?

@j9liu I didn't purposely change that, so I can only imagine Unity change it itself for some reason. I reverted it back to "Auto" though, and everything still seems to be working well, so I've pushed up that change.

Merging this one for tomorrow's release, too.


Progress bar for uploads

Would be neat to use something like https://docs.rs/indicatif/ (or any of the other progress bar crates) for a file upload progress bar.

@jpds This is a nice request. Might take a while before I come to it. There is a whole UX thing to think about on this one.


It crashes when connet without tablename

It works, but not as long.
When i go to http://<IP_ADDRESS>:8000/posts/1, i see correct output:
[{"id":1,"title":"testtitle","content":"Testcontent","created":"0000-00-00"}]
But when i go to http://<IP_ADDRESS>:8000/posts/, i cant see tablenames, i see just
[]
But when i go to http://<IP_ADDRESS>:8000, it crashes:
/mysql/lib/protocol/Parser.js:80
throw err; // Rethrow non-MySQL errors
^
TypeError: First argument must be a string or Buffer
at ServerResponse.end (_http_outgoing.js:739:13)
at Query. (/home/grimakon/apinode/js-crud-api/app.js:90:12)
at Query. (/home/grimakon/node_modules/mysql/lib/Connection.js:502:10)
at Query._callback (/home/grimakon/node_modules/mysql/lib/Connection.js:468:16)
at Query.Sequence.end (/home/grimakon/node_modules/mysql/lib/protocol/sequences/Sequence.js:83:24)
at Query.ErrorPacket (/home/grimakon/node_modules/mysql/lib/protocol/sequences/Query.js:90:8)
at Protocol._parsePacket (/home/grimakon/node_modules/mysql/lib/protocol/Protocol.js:278:23)
at Parser.write (/home/grimakon/node_modules/mysql/lib/protocol/Parser.js:76:12)
at Protocol.write (/home/grimakon/node_modules/mysql/lib/protocol/Protocol.js:38:16)
at Socket. (/home/grimakon/node_modules/mysql/lib/Connection.js:91:28)

when i go to http://<IP_ADDRESS>:8000/posts/

Can you try: http://<IP_ADDRESS>:8000/posts (without trailing slash)?

when you go to http://<IP_ADDRESS>:8000

The behavior is undefined for that case.

when i go to http://<IP_ADDRESS>:8000/posts/

Can you try: http://<IP_ADDRESS>:8000/posts (without trailing slash)?

when you go to http://<IP_ADDRESS>:8000

The behavior is undefined for that case.

The result is the same without trailing slash and with trailing slash - it show "[]".
When i go to go to http://<IP_ADDRESS>:8000 why it is crashes?

when i go to http://<IP_ADDRESS>:8000/posts/

Can you try: http://<IP_ADDRESS>:8000/posts (without trailing slash)?

when you go to http://<IP_ADDRESS>:8000

The behavior is undefined for that case.

How i can to define the behavior in this case? Can you help me? I am new in coding.


Adding pause and play buttons

Description
I would like to add a pause button and a play button so that the user can pause and play the game at their convenience.
Screenshots

Proposed Solution (optional)
Pls assign me this issue, I would love to work on it!
P.S. I have contributed successfully to this project before.
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)

@Dev-tanay can you change the label to gssoc?


remove redundant parameter grab call, we already have the data

Problem Statement
GetParametersByPathWithContext() already has all the parameters, decrypted. No need to query the API once more to get the same thing.
Looks like findByName() is a copy paste from the implementation for findByTag(), but in the latter case a different call is used - DescribeParametersWithContext() which requires additional GetParameterWithContext() call to get the value.
You can test that call easily by using AWS CLI aws sim get-parameters-by-path --path 'your/ssm/path' --with-decryption and see the output actually contains everything.
Related Issue
Haven't open one yet.
Proposed Changes
The change eliminates a redundant call which in my case is the difference between hitting AWS SSM rate-limits and not.
Checklist

[x] I have read the contribution guidelines
[x] All commits are signed with git commit --signoff
[x] My changes have reasonable test coverage
[x] All tests pass with make test
[x] I ensured my PR is ready for review with make reviewable

Tests are passing.

/ok-to-test sha= 2e595d0ed344eb6303c8ac08c7e02561c2965e3c

/ok-to-test sha=2e595d0ed344eb6303c8ac08c7e02561c2965e3c


Compiled a go package containing C code dependencies using -trimpath flag.
go version -m geth

go-ethereum/build/bin/geth: go1.21.6
        ...
	build	-buildmode=exe
	build	-compiler=gc
	build	-tags=urfave_cli_no_docs,ckzg
	build	-trimpath=true
	build	DefaultGODEBUG=panicnil=1
	build	CGO_ENABLED=1
	build	GOARCH=amd64
	build	GOOS=linux
	build	GOAMD64=v1
	build	vcs=git
	build	vcs.revision=2bd6bd01d2e8561dd7fc21b631f4a34ac16627a1
	build	vcs.time=2024-02-27T11:51:11Z
	build	vcs.modified=false

What did you see happen?
Some C packages with full paths embedded in binaries.
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
What did you expect to see?
Relative, trimmed, paths for all C libraries.

I was not able to reproduce doing cd cmd/geth && go build -trimpath . with 0d4c38865e9cda492e71221c4c429d9b1bec8ac5 and 9f9dd2bfd8a09083b21767d13df38ff67d7236d8 can you please post a reproduction ?

It is indeed broken, but not natively on arch (even with go1.21.6), I need to go through your Dockerfile to make it not work.
Using go1.22.2 didn't fixed anything.
However using today's ubuntu:latest base image fixed it for both go1.22.2 and go1.21.6.
I guess some integration bug somewhere with older releases of GCC ¿

cc cmd/cgo @golang/compiler

Btw thx for the effort into reproducing this, it's tricky given it depends on other factors on the system than go and the source you are building but you nailed it with the docker file. :+1: :slightly_smiling_face:

I suppose the answer is to use a recent version of gcc.
ubuntu bionic is past EOL anyway.


Fixed #23762 -- clarified CACHE_MIDDLEWARE_ANONYMOUS_ONLY deprecation in...

Made changes to 1.8.txt and deprecation.txt to clarify that the CACHE_MIDDLEWARE_ANONYMOUS_ONLY setting deprecation warning only applied to CacheMiddleware but not UpdateCacheMiddleware to avoid confusing users when the setting was deprecated in 1.8

Actually the deprecation section in the 1.6 release notes is the main place to clarify this.

Thanks, I've added that in my latest commit to ticket_23762.

merged in e83aba0e2cce16cd1b32d1c172239a4e20867e95, thanks.


[bug] list of deployments disappears when one deployment changes state

Steps to reproduce:
1 - make sure you have one or more deployments in the https://nuvla.io/ui/apps deployments tab
2 - launch a new deployment (or using an existing one which is in STARTED state)
3 - stop a deployment
Result: for the rest of that refresh interval, the deployment cards will disappear

fixed already


Color palette appears on top left position

Color palette appears almost on top left position on screen, while it should be a bit around editor, like on top of editor or bottom according to screen.

@anandsgx if possible could you please provide a screenshot of the issue?

Yes, please check attachment

.

Also an issue I am seeing, I am using angular 17.0.0. If I run command ng serve, so for first time if UI loads on browser I get this issue.

in html used in this way
<angular-editor name="description" [placeholder]="'Type here...'" [(ngModel)]="ideaDetail.description">

could be the setup, it kind of looks like a bug on the code though. Can you send me the package.json or parts of it and if possible the index html.

opened a PR to fix it: https://github.com/wfpena/angular-wysiwyg/pull/38

@anandsgx Created a new release v2.0.1 with the fix. Closing this issue

@wfpena Ok, it looks good now, thank you.


About safeTME

Dear Sir or Madam,
I am currently using spatialdecon and the safeTME deconvolution. I am wondering are there formal definitions of the abbreviations used in safeTME, like monocytes.C, monocytes.NC.I, mDCs. Specifically, does mDCs stands for conventional dendritic cells?  Thank you!

Hi @ydai3,
Our customer support team will be able to help you with this. Please email<EMAIL_ADDRESS>with your issue.
Thanks,
Maddy


pkg: Follow Go convention on capitalization

Signed-off-by: yulng<EMAIL_ADDRESS>According to the golang-lint specification, generic nouns need to be capitalized
Use API instead of Api
Thanks

Thanks for the PR.
Could you add the justification that you added in the PR description to the commit msg also, and state that this is a cosmetic commit with no functional change?
Could you also re-word the commit title to say "pkg: Follow Go convention on capitalization"?

ok ,commited it again ,Its changes have no functional change

Signed-off-by: yulng<EMAIL_ADDRESS>According to the golang-lint specification, generic nouns need to be capitalized Use API instead of Api Thanks

@nathanjsweet 😄😄

Smoke tests are passing and reviews are in. Given the trivial changes, I don't think we need to run the end-to-end tests.


deerma.humidifier.jsqs not returning water-shortage-fault

Device: deerma.humidifier.jsqs
Connects to home assistant but does not return water-shortage-fault (siid: 7, piid: 1)
siid 7 is custom
In the properties of the humidifier you can see:
exclude_miot_services:
-custom
How can I get the value of water-shortage-fault ?
Without it, my automation does not work correctly (turning on, off and changing the operating mode of the humidifier)

# configuration.yaml
xiaomi_miot:
  device_customizes:
    deerma.humidifier.jsqs:
      exclude_miot_services: null

https://github.com/al-one/hass-xiaomi-miot/issues/332#issuecomment-1031711816
https://github.com/al-one/hass-xiaomi-miot/issues/420

Еhanks.
I did not find the option with
exclude_miot_services:: null
in the documentation, the option
exclude_miot_services:: ""
was not work


Adding recipe version to result file name

Problem
We want to differentiate between versions of the same recipe while keeping all the results in the same folder for analyses.
Solution
Append the recipe version to the name of saved files and data.
NOTE: the recipe version is NOT appended to the grid file to avoid regenerating the grid when a recipe is changed.
Type of change

New feature (non-breaking change which adds functionality)

Change summary:

added recipe version to result file name
added option to disable plotting during analyses

Steps to Verify:

Setup the cellPACK environment as shown in the README
run pack -r cellpack/test-recipes/v2/peroxisomes_surface_gradient.json -c packing-configs/peroxisome_packing_config.json
Change version in the recipe and re-run packing to verify results are saved with appended version names in the same folder

Keyfiles (delete if not relevant):

Environment.py
Analysis.py

Unsure why linting fails. black doesn't raise any errors locally:

The same version of black is also installed during the check:


compose.html: Fix hotkey advice for new private message button.

Automated message from Dropbox CLA bot
@rishig, it looks like you've already signed the Dropbox CLA. Thanks!

Nice, merged, thanks @rishig!
Though I wonder whether from an i18n perspective we should move the key out of the i18n tags.  @YagoGG thoughts?

I definitely think that should be kept, having an untranslated tooltip wouldn't look quite right.
I was wondering... maybe we can move the (C) outside the i18n tag?

yeah that's what I was suggesting.  Just merged 36b9c5792a22f4c159c830082076128759dd0aea


Release 0.1.5 breaks semver

Thank so much for your work on this crate! It's been very useful.
I picked up the 0.1.5 release today and it doesn't seem to be backwards compatible with 0.1.4.
The compiler error looks like:
219 |         let (lat_rad, lon_rad, alt_m) = map_3d::ecef2geodetic(x_m, y_m, z_m);
    |                                         ^^^^^^^^^^^^^^^^^^^^^--------------- an argument of type `Ellipsoid` is missing

If this API change was intentional, I think 0.1.5 should be re-released as 0.2.0.

hello, i was not aware of the semantic versioning rules. This library was born as an exercise for learning rust.
Eventually for the next changes, i will keep the semver in mind. As of now i will keep the current version number.


Using toothpick with registry in lib doesn't build

I'm using TP in a project that own a android module, which hold class that need TP. This is in kotlin.
With reflexion, everything works well.
This is part of the build.gradle off the app:
    kapt {
        arguments {
            arg("toothpick_registry_package_name", "com.afaucogney.yope.app")
            arg("toothpick_registry_children_package_names", "com.afaucogney.yop")
        }
    }

Nothing is inside the build.gradle of the lib
And the config inside the App:
    Toothpick.setConfiguration(Configuration.forProduction().disableReflection())
        MemberInjectorRegistryLocator.setRootRegistry(com.afaucogney.yope.app.MemberInjectorRegistry())
        FactoryRegistryLocator.setRootRegistry(com.afaucogney.yope.app.FactoryRegistry())

I do use smoothie, but I do not think some code is needed for it.
MemberInjectorRegistry and FactoryRegistry are generated for the app, but nothing is generated for the lib.
Someone may help me where/how investigate my issue ?

Nothing is inside the build.gradle of the lib
This is the problem. Annotation processing is not run for the lib module, so nothing is generated.
You need to configure annotation processor in the lib's build.gradle as well, with arg("toothpick_registry_package_name", "com.afaucogney.yop")

sorry, after re-reading the wiki this information was well written in https://github.com/stephanenicolas/toothpick/wiki/Factory-and-Member-Injector-registries with:

The same would apply to lib1 has it doesn't depend on any library using Toothpick.

As this text wasn't well highlighted (or with code), I just didn't make enough attention !


[Tabs] Fix and improve visibility of scrollButtons using IntersectionObserver

Fixes the issues below:
Fixes #31936
Fixes #19673
Fixes #33349
Fixes #23711
This fix handle visibility of scroll buttons specially in dynamic content behavior and also it reduces the complexity of the code (calculation logic).
before: https://codesandbox.io/s/interesting-before-b3kdvn?file=/src/App.js
after: https://codesandbox.io/s/interesting-after-zej36n?file=/src/App.js

[x] I have followed (at least) the PR section of the contributing guide.

I've implemented a new method to handle the visibility of scroll buttons, using the IntersectionObserver. Essentially, it allows us to detect when a particular element (in this case, a tab) is in view on the screen.
With this new method, we're observing only the first and last tabs. If either the first or last tab is partially visible or completely invisible, we'll show the appropriate scroll button. For example, if the first tab is only partially visible,we'll show the scroll button that allows the user to scroll to the left and reveal more of the first tab. If the last tab is completely invisible, we'll show the scroll button that allows the user to scroll to the right and reveal the last tab.
By using the IntersectionObserver to only observe the first and last tabs, we're optimizing our code and reducing unnecessary calculations especially in dynamic content scenarios. This new method, the code should be easier to read and maintain.

Hi @mnajdova if you have a moment, could you kindly take a look and review this PR please.

@mnajdova  Are there any updates on this issue?

@mnajdova @SaidMarar Are there any updates on this issue?

@JoinerDev the PR needs only to be reviewed, so we can advance.

Hello @ZeeshanTamboli , Thank you a lot for your review :smile:

For the first issue you mentioned in the demos, i don't reproduce it with the latest changes. Please check the screenrecords below:

Dev:

Prod:

For the second issue in Argos, i just fixed it by removing debounce on both observers, because it causes a delay on render for the buttons.

@ZeeshanTamboli  Could you please post your resolutions, my environement test on Ubuntu 22.04:

Firefox 115.0 (64 bits), resolution 1920px 995px
Chrome Version 114.0.5735.198 (Build officiel) (64 bits), resolution 1920px 995px

My screen resolution is 1920px 1080px.

@ZeeshanTamboli it works also on iPhone.
https://github.com/mui/material-ui/assets/20561190/cecbef2f-0000-4b3e-b9e4-41c9b1efb869

@ZeeshanTamboli can you screenrecord,maybe it will help me to reproduce.

On Windows 10, Chrome Browser:
https://github.com/mui/material-ui/assets/20900032/543e8be9-e7cb-4352-a1b3-639b9baf970a

On Android Chrome:
https://github.com/mui/material-ui/assets/20900032/eed7564f-57cb-4c5d-aa6b-c264631e49a0

@ZeeshanTamboli could please post the values of scrollWidth of the elements below:

element with role="tablist"
element with className MuiTabs-scroller

@ZeeshanTamboli When you reach the last element could you please print the getBoundingClientRect (value of the attribute right) of:

The last element in tabs the button (item seven)
The element with class MuiTabs-scroller

@SaidMarar
https://github.com/mui/material-ui/assets/20900032/c48b1797-a020-4dd5-8099-864a4ee6dd3d

Thank you, @ZeeshanTamboli. It was very helpful, and I was able to reproduce it in both Chrome and Firefox. The problem persists even when we reach the maximum value of scrollLeft (the max value: scrollWidth - clientWidth). The last item on the x-axis always remains higher than its parent.

And this is a known issue and it was reported on chromium  too, as you can see in the example  the scrollLeft is returning a decimal value which is a bug.
For firefox i have doubts they are rounding the scrollLeft but the issue of boundingRect stays the same as chromium.
Possible solution is to use 0.99 as threshold, i tested it on local it resolved the problem.

@ZeeshanTamboli could you please test again ? :)

@ZeeshanTamboli if updateScrollButtons will remain accessible for developers who are relying on it, why we dont just change its old implementation to use IntersectionObserverAPI. The code will be simpler.
we create a state that is responsible to re-init the observer:
  const [updateScrollObserver, setUpdateScrollObserver] = React.useState(false);
we change the updateScrollButtonState implementation to this:
  const updateScrollButtonState = useEventCallback(() =>
    setUpdateScrollObserver(!updateScrollObserver),
  );

Finally we just append the Observer useEffect dependencies:
  [scrollable, scrollButtons, updateScrollObserver, childrenProp?.length];
What do you think ?

I think I understand what you mean. Whenever the updateScrollButtons action is triggered by the developer, you want to run the IntersectionObserver i.e the useEffect? Sounds like a good idea. Feel free to apply the changes. But when will you reset this scroll observer state?

@ZeeshanTamboli Yes the IntersectionObserver effect will run, when the developer triggers updateScrollButtons action.
Sorry, I don't understand what you mean by when i will reset the scroll observer state ?

Sorry, I don't understand what you mean by when i will reset the scroll observer state ?

Does the updateScrollObserver state, triggered by updateScrollButtons action, reset to false after the effect finishes running?

Does the updateScrollObserver state, triggered by updateScrollButtons action, reset to false after the effect finishes running?

No need to reset, because the updateScrollObserver state is used only to be toggled every time we call updateScrollButtons, ensuring the re-run of the effect, which means rebinding the IntersectionObserver to detect the visibility of buttons.

@SaidMarar It looks good! Thanks for your great contribution!

Thanks to you too for your assistance and help 👍🏻


Fix _removeReaction's reaction lookup

The emojiID that was used to remove a reaction from this.reactions was different from the emojiID that's used to add one.
_removeReaction would always return null, so the messageReactionRemove event could never get emitted. No more.

I had closed this because merging into master didn't seem right —
— but since I can't see the indev branch and the contribution guide doesn't mention it, I am reopening this guy. Full steam ahead

Yes, for future reference, master is now the dev branch. Stable is the release branch. From the announcement on the Discord.js Official Discord server:

We've restructured the Git branches a bit. What used to be the indev branch is now master, and the old master is now stable. So, if you want to run the latest in-development version of discord.js, you should now simply use npm install hydrabolt/discord.js.

instead of the build emoji thing, add a method to emojis which returns the correct string, maybe toEndpointString or something


Collect all fields that are required by GA measurement protocol in JavaScript collector

For #115 we need to collect all possible fields that are present in Google Analytics measurement protocol.
The most complicated is session control (sc). If this is necessary for accurate counting at all, we need to send this events from JS and process them only if GA destination is configured

Here's a field mapping
# https://developers.google.com/analytics/devguides/collection/protocol/v1/parameters

GA PARAM    VALUE                                       STATUS
----
v           1
t           /event_type if in [
            'pageview', 'screenview', 'event',
            'transaction', 'item', 'social',
            'exception', 'timing'];
            'pageview' otherwise;
            (treat 'transaction' as 'conversion')

tid         <config>
aip         false
ds          false
cid         /eventn_ctx/user/anonymous_id
uid         /eventn_ctx/user/anonymous_id
ip          /eventn_ctx/user/id                         new
ua          /eventn_ctx/user_agent
uip         /source_ip
dr          /event_ctx/referer
cn          /eventn_ctx/utm/campaign
cs          /eventn_ctx/utm/source
cm          /eventn_ctx/utm/medium
ck          /eventn_ctx/utm/term
cc          /eventn_ctx/utm/content
gclid       /eventn_ctx/click_id/gclid
dclid       /eventn_ctx/click_id/dclid
sr          /eventn_ctx/screen_resolution               new
vp          /eventn_ctx/vp_size                         new
de          /eventn_ctx/doc_encoding                    new
dl          /event_ctx/url
dh          /event_ctx/doc_host                         new
dp          /event_ctx/doc_path                         new
dt          /event_ctx/page_title
ul          /event_ctx/user_language                    new
ti          /conversion/transaction_id                  new
ta          /conversion/affiliation                     new
tr          /conversion/revenue                         new
ts          /conversion/shipping                        new
tt          /conversion/tt                              new


Move database/cache module from legacy /src to /lib

We create a /lib folder to store common shared libraries across microservices. We need to move database and cache module to /lib so that microservices could start using Ignite.

@chenpiaoping Could you please make a comment on this ticket so that the system would allow me to assign it to you? Thanks.

Please assign this task to me, Thank you.

Assigned @chenpiaoping  Thank you!


Clearer indication of progress

One feature I think would be great would be a clearer visual indicator of progress.
In a normal terminal we know when the script is finished becasue we can see the prompt again, in the vscode it just stops and you never see a terminal. I had to double check by going to the portal to make sure it had worked.
We can have something like a ">> COMPLETE <<" message or maybe a spinner whilst it's running which ends when it finished.

@jawache we released a new version of the extension last Friday - could you try it out and close this issue if you're satisfied with the experience?
We added a spinner as you described:

Added spinner and more prominent message in log.


Windows portable build

If I will change target from nsis to portable packaging will fault with exception:

Using electron-builder.yml configuration file
No native production dependencies
Error: Unknown target: portable

Portable is correct target from here

It just a day ago in electron-builder, we should upgrade it to ^14.4.0.

@chentsulin, greenkeeper is disabled on this repo?

I can PR for this. Not sure when but hopefully within a week or so. Migrated in a toy app that i was working on:
https://github.com/amilajack/contrast
Requires that we

[ ] Update the readme to reflect the new requirements of electron-builder
[ ] Fix our config options which have been deprecated

Fixed this


OBS crashes on close

When closing OBS with the script enabled, the message "Whoops, OBS has crashed!" is given.

Possibly related to issue #10


Feat/land refactor base token to common

Description
Initial base branch for the refactor
https://internal-jira.atlassian.net/browse/LR-59

Will try a different approach.


Define es:top-level or equivalent

When putting entity instances into documents, one always chooses one to be the root, and others to embed or denormalize into the document structure.
Entity Services in MarkLogic 9 does not provide this vocabulary, but repeated use of the code generation indicates that it could be automated significantly with this extra concept.

Entry point of a module is known.
Expectations of whether a reference property contains an embedded instance or a reference to an external one.
Refinement of extraction template to require less customization.

This issue is a proposed design change, but it needs more grounding in scenario to map the capability to an implementation.  Probably not for 9.0-3?

The other issue is more of an existential one: What is an entity? Is (the concept of) an “address” an entity? If you were the Post Office, maybe, but for many applications an address is a rich piece of data that only exists in the context (i.e. as a sub-property) of something else, like a Person or and Order.
As a Data Architect, I want to be able to define and reuse sub-entities, like Address. For example, in my  Order entity the shipTo property is not a string, but a type Address. That “type” definition is defined elsewhere and, like xs:string can be reused by reference in multiple entities.

Anything with sub-structure is an entity
Need a way to describe “important” or “top-level” entities, i.e. those that represent true business entities
Need a way to tell the materialization how to (completely) denormalize within another entity

“weak” entities (so it matches next time I search)


[WIP] New build scripts

This includes PR #103.
Goal:

Use and maintain separate directories for different architecture, allow to debug a variety of modified code once.
Add watch scripts.

Issues:

zip scripts is not working for now, I tried to solve it but encountered a few of problems. I hope this can be clearer, but I don't know how to do this. For example adding a helper.js to parse the parameters thus reduce the npm's scripts.

This looks like really promising.
Just a heads up. The "npm run build" commands start by calling "npm run clean" which deletes the "dist" directory containing the generated extension files. Deleting dist before every build is a hack I made early on to ensure no stale files were accidentally kept.
It's worthwhile to modify the build commands so that dist isn't deleted on every build. This will make incremental builds MUCH faster and make watch mode possible.

web-ext sound good but no output_filename support. https://github.com/mozilla/web-ext/issues/855


Kb Search

Allows users to search through the Knowledgebase for categories and articles using keywords

The search function is so cool, thank you! Here are some notes:

When searching the categories, can you include the short_description and description in the places to search?
When there's a category in the results, the short description text is too large, it should be the same font size as the View Articles button

I just pushed a commit that tweaks the query-printing a little bit; I use list() on the queries to force Django to run them, which might not match the actual query Django runs when it loads the page but gets close enough.


Standardize names; return exported types

Which issue this PR addresses:
Fixes 7970744
What this PR does / why we need it:
Rationale
The purpose of this is to make the code more consistent, maintainable, and accessible. You shouldn't have to spend more than a few seconds determining what the purpose of something is, especially when you are already familiar with some of the codebase. Having standard names makes it much easier to find all occurrences of things and see patterns.
Client names
Right now there is no standard way of naming clients in the codebase. Examples include accounts, configcli, vmClient, and collc (collection client). This makes it hard to read at a glance. In addition, some of those names are vague. For example, accounts refers specifically to storage accounts.
NewFoo
There are also some other names that don't describe what they do very well. For example, clusters.New does not create a cluster; it creates a cluster manager.
CamelCase
This PR also fixes names which should be camelCase or CamelCase, as is standard in Go. It's understandable that import names can be all-lowercase compound words, but variables and fields shouldn't be.
Return Exported Types
I also changed two functions so they return the exported interface type. If there is some reason this change won't work, I'll revert it.
Low priority
This PR can be the lowest priority to avoid inconveniencing other people. I will rebase and keep it up to date as needed until the time comes when it can be merged without causing too many headaches.
Test plan for issue:
Run existing tests
Is there any documentation that needs to be updated for this PR?
No

While consistent naming is important, the value of some of the proposed changes isn't that obvious to me. For example, I prefer "cli" to "somethingSomethingClient" when the name is local and it's obvious from the context which client it is. Struct fields, however, should be descriptive enough.
I let myself quote "The Go Programming Language" book here

There is no limit on name length, but convention and style in Go programs lean toward short names, especially for local variables with small scopes; you are much more likely to see variables named i than theLoopIndex. Generally, the larger the scope of a name, the longer and more meaningful it should be.

As well as the Effective Go

Long names don't automatically make things more readable. A helpful doc comment can often be more valuable than an extra long name.

While consistent naming is important, the value of some of the proposed changes isn't that obvious to me. For example, I prefer "cli" to "somethingSomethingClient" when the name is local and it's obvious from the context which client it is. Struct fields, however, should be descriptive enough.
I let myself quote "The Go Programming Language" book here

There is no limit on name length, but convention and style in Go programs lean toward short names, especially for local variables with small scopes; you are much more likely to see variables named i than theLoopIndex. Generally, the larger the scope of a name, the longer and more meaningful it should be.

As well as the Effective Go

Long names don't automatically make things more readable. A helpful doc comment can often be more valuable than an extra long name.

The locally scoped variables don't need to be as descriptive, but they should be consistent. As far as the naming scheme, I don't really care what it is, as long as it's consistent. If everyone likes the *cli convention, then let's apply that everywhere. At the very least, though, I would argue it should be camelCase (*Cli).

I wonder if there is anything we can do to make sure everyone on the team understands what the coding convention and naming standards (if any) are, so we don't need to repeat this type of effort? Ideally, calling out misleading, ambiguous code before PRs are merged is more efficient than naming refactoring effort.

Somehow when Client is appended all code looks very verbose.
What is wrong with just having groups, vm, kubernetes ?
@jim-minter  I think this needs discussions in some other forum than PR :)

What is wrong with just having groups, vm, kubernetes ?

Nothing - but I think whatever naming scheme we decide on should be consistently applied.

I'll convert it to a draft so it's clear this is still a proposal

@mjudeikis I have removed the *Client suffix - can you take another look?


how use dns "no-ip"  or other with this tool ?

Can you tell how or where put dns adress because in" LHOST"  option it's no possible

??

Hello,
At the moment the CHAOS don't support this.
I'll mark it to futures improvements.


[Bug] lua require"cmp.utils.feedkeys".run(...) is getting spammed into buffer

FAQ

[X] I have checked the FAQ and it didn't resolve my problem.

Announcement

[X] I have checked Breaking change announcement.

Minimal reproducible full config
vim.keymap.set('i', '<Up>',   '<C-o>gk',      { silent = true })
vim.keymap.set('i', '<Down>', '<C-o>gj',      { silent = true })

local ensure_lazy = function()
  local lazypath = vim.fn.stdpath('data') .. '/lazy/lazy.nvim'
  if not vim.loop.fs_stat(lazypath) then
    vim.fn.system({
      'git',
      'clone',
      '--filter=blob:none',
      'https://github.com/folke/lazy.nvim.git',
      '--branch=stable', -- latest stable release
      lazypath,
    })
  end
  vim.opt.rtp:prepend(lazypath)
end

ensure_lazy()

-- Using Lazy.nvim
require('lazy').setup({
  -- Plugin manager itself
  { 'folke/lazy.nvim' },

  -- LSP Zero
  { 'VonHeikemen/lsp-zero.nvim',        branch = 'v4.x' },
  { 'williamboman/mason.nvim' },
  { 'williamboman/mason-lspconfig.nvim' },
  { 'neovim/nvim-lspconfig' },
  { 'hrsh7th/cmp-nvim-lsp' },
  { 'hrsh7th/nvim-cmp' },
})

Description
When holding up or down at the edge of a buffer it spams the tail end of lua require"cmp.utils.feedkeys".run(...) repeatedly into the buffer.
I am pretty sure it has triggered in the middle of the file before but it is much less likely than at the edges of the buffer and I don't really have any proof.
Steps to reproduce
This issue is EXTREMELY difficult to reproduce on a minimum config and likely will not show if your machine is at all performant. (I only experience this on my laptop with an Intel Celeron N4000 processor, 4GB of ram, and emmc memory)

Open or create a large file (The size of the file isn't necessary but it seems to increase the chance the issue triggers)
Switch to insert mode
Hold up while at the top of the file or down at the bottom of the file

Expected behavior
No input whatsoever
Actual behavior
It spams varying amount of the tail end of lua require"cmp.utils.feedkeys".run(...) into the buffer. It can spam as little as a ) or as much as the full line though usually it only a couple of the characters unless you hold it long enough that nvim starts slowing down.
Additional context

Reproduction with provided minimum config:
https://youtu.be/HmgRijZhuZ4
Note: Half the video is me copying and spam pasting the config to make the file super large. Even after pasting thousands of lines of code this only cropped up once. I was holding down pretty much the entire time after I hit the bottom of the file.
Reproduction with my normal config:
https://youtu.be/b0N2umon8pQ
This it shows up super easily but I only have issues with it on my low powered machine. My regular desktop does not trigger this issue. (I haven't tried super hard though)
For all I know this could be an issue with nvim itself but since the line that gets pasted is a call to this plugin's function I figured you would have the best shot at figuring out what's going on.
I'll include a copy of my full nvim config as well in the event it helps you reproduce (the .txt is cause apparently github doesn't allow uploading of lua files)
init.lua
Also I don't know if the 2 insert mode mappings are contributing to the error but it didn't trigger in any of the tests without them. That could however just be because of how hard it is to trigger on the provided minimum config.

Looking at the code this is probably the output I'm seeing in my file https://github.com/hrsh7th/nvim-cmp/blob/ae644feb7b67bf1ce4260c231d1d4300b19c6f30/lua/cmp/utils/feedkeys.lua#L27
While I haven't looked too very deeply into this code base my assumption is that this is a race condition where if command mode is exited before it finishes executing this line it instead inserts the rest of the line into the buffer. I have no clue what's interfering with this line though.
By the way, I just want to throw it out there that I am more than willing to help test patches and stuff. This isn't a case of report and leave. Just let me know what you need from me and I'll happily help you out in trying to get this resolved.

I also encountered this when I use nvim-autopairs' fast-wrap, cmp insert the exact same string into buffer, I also believe this is a race condition, because when I change defer_fn to vim.schedule everything is good.

I had posted on the other issue about this. That was quite a long time ago and I can't repro it anymore.
I also noticed I had altered my mappings at some point to use norm! instead of <c-o>.
Does this help at all?
vim.keymap.set('i', '<up>', '<cmd>norm! gk<cr>', { silent = true })
vim.keymap.set('i', '<down>', '<cmd>norm! gj<cr>', { silent = true })

@vurentjie that fixed the issue for me.  Thank you!


Lowering log, so we don't have to configure logging in any project us…

…ing this, that logs on INFO.

@schup This is really a detail, but I'm actually waiting for this for years. I mean it is just a bit silly to litter our log4j2.xml configurations with:
    <Logger name="com.joestelmach.natty.Parser"  level="WARN" />
We use to have the root-logger on 'INFO', but what the parser is logging is obviously for debugging, imho.

Indeed, doesn't make sense to log at info level.


CassandraEmptyRDD

Oughtn't there be a cassandra flavored EmptyRDD?
It would be handy to be able to return an empty RDD rather than wrapping in Try or Option.

Migrated to JIRA:
https://datastax-oss.atlassian.net/browse/SPARKC-37


docs: Fix typo

Haha, nice. Thanks!

No problem. Trying to get more familiar with GitHub and this seemed like an opportunity to try branching and creating a pull request.

It was much appreciated :octocat:.
(Just in case my meaning got muddled I was chuckling at the nature of the typo not anything you did)

No muddling here. I thought it was funny too. That release note caught my eye because I added the "numeric id" feature to a local copy of the code, but never got it fully working with expandTo(). The v1.0.2 release seemed to fix my problem.


Add cibuildwheel to test building many platforms

Codecov Report

Merging #364 (18fd1e2) into unstable (3f0b6ed) will increase coverage by 0.04%.
The diff coverage is 84.61%.

@@             Coverage Diff              @@
##           unstable     #364      +/-   ##
============================================
+ Coverage     74.57%   74.61%   +0.04%
============================================
  Files            10       10
  Lines          1282     1292      +10
  Branches        230      233       +3
============================================
+ Hits            956      964       +8
  Misses          224      224
- Partials        102      104       +2

Flag
Coverage Δ

unittests
74.61% <84.61%> (+0.04%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

setup.py
91.66% <84.61%> (-8.34%)
: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 3f0b6ed...18fd1e2. Read the comment docs.


Remove useless a.out ELF file and ignore *.out

In commit 32dc9e7b9fd2 ("appimage: Fix lldb in appimage builds") introduce an a.out ELF file by mistake.

@Rtoax Good catch! Do we know if this a.out gets re-generated when doing the app image build? (cc @danobi)

I'm tempted to do a force-push to get the binary file out of the repo's history. What do people think?

I'm tempted to do a force-push to get the binary file out of the repo's history. What do people think?

I don't feel strongly but I'm not opposed. I don't imagine this binary has some malware in it. I just want to make sure we didn't introduce something where the binary will return.

I'll clean it up in a force push now then. The sooner the better to avoid more people pulling the current version

Thanks for spotting this @Rtoax!


[Feature] Different Font

Maybe consider changing the font? it doesn't quite fit in in my opinion.

I will make this an option once I have added settings.

Added in 4e9c1b.


Update GPU support page to reflect correct libraries required for TF 2.5.0

URL(s) with the issue:
https://www.tensorflow.org/install/gpu
Description of issue (what needs changing):
The documentation has not been updated to state the correct versions of cuda, cudnn and nvinfer that the current stable Tensorflow version (2.5.0) requires.
For example in the Ubuntu 18.04 configuration, instead of:
# Install development and runtime libraries (~4GB)
sudo apt-get install --no-install-recommends \
    cuda-11-0 \
    libcudnn8=<IP_ADDRESS>-1+cuda11.0  \
    libcudnn8-dev=<IP_ADDRESS>-1+cuda11.0

It should be something like:
# Install development and runtime libraries (~4GB)
sudo apt-get install --no-install-recommends \
    cuda-11-2 \
    libcudnn8=<IP_ADDRESS>-1-1+cuda11.2  \
    libcudnn8-dev=<IP_ADDRESS>-1+cuda11.2

It's also particularly unclear which version of the nvinfer libraries are required to enable TF-TRT optimizations since it's also not stated in the Build from source page and it's also not obvious how to check that TRT is enabled.

Thanks for your issue. This is tracked with https://github.com/tensorflow/tensorflow/issues/49175


feat: (airbyte-protocol) add new record message type

Context
To be competitive with very large data volumes, we have no other option than to add file-based bulk data transfers.

How
Through the CDK, we will leverage the file-based connector's ability to write a file locally instead of sending records and emit a new record message with metadata related to the file.
{
  "type": "RECORD",
  "record": {
    "stream": "simpsons_locations",
    "file": {
      "file_url": "/tmp/airbyte-file-transfer/sftp-testing-for-file-transfer/sftp-folder/simpsons_locations.csv",
      "bytes": 182776,
      "file_relative_path": "sftp-testing-for-file-transfer/sftp-folder/simpsons_locations.csv",
      "modified":<PHONE_NUMBER>000,
      "source_file_url": "//sftp-testing-for-file-transfer/sftp-folder/simpsons_locations.csv"
    },
    "emitted_at":<PHONE_NUMBER>632,
    "data": {}
  }
}

Now we want to formerly move this message in the cdk to airbyte protocol.
Here, you can find a ref to the documentation of the project.
How would be used in python (CDK)?
Initially, this should replace this file so we don't import this but get from protocol library in this other import. Now, final implementation could require more work if we decide to change keys naming and structure.
Also, we could change this dataclass to have a new file key rather than threat as another record class.
Note:
We agree to wait a little bit here, but it's nice to have some point to start talking about for future change, so there's no rush on this.

How would be used in python (CDK)?

I added a section How would be used in python (CDK)? in the PR description.


33 -update readme with badges

Add open & closed issues & # of stars badges

Yeah, per @suvasan19 / the issue, it is just missing yourself as the maintainer. After seeing @tbartram's update it probably makes sense to include your name / Harled email AND your GitHub handle.


added alert, confirm, prompt to browser

I know alert, confirm, prompt are not part of the DOM, but all browsers handle them

I agree with @istvan-antal and @timendum
Putting confirm in devel makes no sense. It's a user interface.

@ianwalter you are free to add alert and console to your globals if you are happy your project using them for user interface.

@lukeapage I was speaking specifically about confirm although you could make the same argument for alert and prompt. They are browser-supported user interface APIs so I think putting them under the browser flag makes sense. Putting console under devel makes sense since its an API used by developers and doesn't have full browser support.