Syntax highlighting not working in jupyter lab v3.0.16

After upgrading jupyter + jupyter lab, IJulia no longer shows correct syntax highlighting within notebooks (examples: missing string highlighting, functions and arguments have the same color, closing brackets sometimes have different colors than opening brackets, some closing brackets highlighted as in red when under cursor even though they are correct).
Jupyter setup:
jupyter core     : 4.7.1
jupyter-notebook : 6.4.0
qtconsole        : not installed
ipython          : 7.25.0
ipykernel        : 5.5.5
jupyter client   : 6.1.12
jupyter lab      : 3.0.16
nbconvert        : 6.1.0
ipywidgets       : not installed
nbformat         : 5.1.3
traitlets        : 5.0.5

Julia setup:
(@v1.6) pkg> st IJulia
      Status `~/.julia/environments/v1.6/Project.toml`
  [7073ff75] IJulia v1.23.2

julia> versioninfo()
Julia Version 1.6.0
Commit f9720dc2eb (2021-03-24 12:55 UTC)
Platform Info:
  OS: Linux (x86_64-pc-linux-gnu)
  CPU: AMD EPYC 7742 64-Core Processor
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-11.0.1 (ORCJIT, znver2)

Downgrading jupyterlab to v3.0.0 solves this issue (haven't tested intermediate versions).

This just happened to me, and this comment solved it for me
https://stackoverflow.com/a/69545072/1914791
TLDR: just refresh the browser tab :)

Thanks! I'm currently running a setup similar to @urlicht and have not been having issues for a while.


MPC optim status infeasible when SOC lower than min SOC

Describe the bug
When SOC init is lower than min SOC, MPC run optim status will be infeasible.
This night my automations did not work because of infeasible optim status. I checked the logs and i'm pretty sure it's because my min SOC is 15%, but whatever reason my real SOC went to 14%.
For now I made a workaround like this:
       "soc_init": {{           [((states('sensor.ss_battery_soc') | int(0)) / 100), 0.15] | max         }},
To Reproduce
Set min SOC higher than your real SOC that you use as SOC init in MPC run
Expected behavior
I would expect optim status won't be infeasible in this scenario.
Screenshots
If applicable, add screenshots to help explain your problem.
Home Assistant installation type

Home Assistant Core

Your hardware

OS: Linux
Architecture: amd64

EMHASS installation type

Docker Standalone,

I have seen this aswell, same thing happens if SOC is above the maximum battery charge percentage

Expected behavior
I would expect optim status won't be infeasible in this scenario.

I don't understand this issue.
If you pass a SOC init that is lower than the SOC min then I do expect that the outcome is infeasible.
How would you expect this to not be infeasible?

Maybe the constraint could be less strict; can it be adjusted to only prevent discharges below the soc_min instead of treating it as an invalid value in general?
That way EMHASS could recover by charging the battery first, after a deep discharge, beyond the usual levels.
(i.e. in winter, when the battery is not charged with solar and simple loses charge over time)


Table.PutItemAsync not saving and not throwing an error

Describe the bug
We are attempting to update records via Table.PutItemAsync from a lambda function and the record is not updated. The same code works in a different lambda function pointing at another dynamodb table. The weird thing is that no exception is thrown.
The function has the necessary permissions to update the table.
Expected Behavior
I expected the record to be updated with the changes.
Current Behavior
Table is not updated when calling Table.PutItemAsync. I added logic to have the put return all old attributes, and the return is null. The implementation is below:
    public virtual async Task Save(TEntity obj, CancellationToken cancellationToken = default)
    {
        var document = Document.FromJson(JsonSerializer.Serialize(obj));

        var response = await _table.PutItemAsync(document,
            new PutItemOperationConfig { ReturnValues = ReturnValues.AllOldAttributes }, cancellationToken);

        if (response is not null && response.Count > 0)
        {
            _logger.Debug("Record was updated");
        }
        else
        {
            _logger.Debug("Record was inserted");
        }
    }

Reproduction Steps
Code snippet we are using to actually connect to the table was provided above.
Possible Solution
No response
Additional Information/Context
No response
AWS .NET SDK and/or Package version used
AWSSDK.DynamoDBv2/3.7.100
Targeted .NET Platform
.Net 6
Operating System and version
Lambda

One quick note, if I change the implementation to use an IAmazonDynamoDB implementation instead of table, the record saves. It looks like under the hood the Table implementation uses that as well.

Ok, I found the issue. Pointing at the wrong table. Nothing to see here...

But then in this case, you want to see an error saying wrong table, or something. Error messages would be useful. I have a similar case of debugging the unknown as no error is thrown.


feat: add metadata_filename parameter across all partition functions

Summary

Closes #589
Adds assert statements to existing tests to test for filename
Adds commented out assert statements to tests where the filename is not retained when a file is partitioned (None is returned)
Creates new tests for when metadata_filename is defined as an argument when parsing files
Adds some missing docstrings and mixes some typos

Great. Sounds good!

@MthwRobinson give me a sec to look over this PR again before merging. Now that I have the tests and understand what's the expected behavior, I may be able to remove some lines in the parsers where metadata = metadata or filename. I need to make those changes and run the new tests to make sure nothing breaks.

I'm working on them now


Helm upgrade from config even there is no changes passed while running command

Output of helm version: version.BuildInfo{Version:"v3.3.4", GitCommit:"a61ce5633af99708171414353ed49547cf05013d", GitTreeState:"clean", GoVersion:"go1.14.9"}
Output of kubectl version: Client Version: version.Info{Major:"1", Minor:"17+", GitVersion:"v1.17.9-eks-4c6976", GitCommit:"4c6976793196d70bc5cd29d56ce5440c9473648e", GitTreeState:"clean", BuildDate:"2020-07-17T19:00:19Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):  EKS
when I run helm upgrade command multiple times without changing anything it deploy new revision.

Every time you run helm upgrade it does an update and goes through the process. This would mean a new Helm does have a new release.
Are any of the Kubernetes resources changing?

dexterisdiwap$ helm install test test/app
NAME: test
LAST DEPLOYED: Thu Oct  1 00:14:18 2020
NAMESPACE: development
STATUS: deployed
REVISION: 1
TEST SUITE: None
dexterisdiwap$ helm upgrade test test/app
Release "test" has been upgraded. Happy Helming!
NAME: test
LAST DEPLOYED: Thu Oct  1 00:14:39 2020
NAMESPACE: development
STATUS: deployed
REVISION: 2
TEST SUITE: None
dexterisdiwap$ helm upgrade test test/app
Release "test" has been upgraded. Happy Helming!
NAME: test
LAST DEPLOYED: Thu Oct  1 00:14:54 2020
NAMESPACE: development
STATUS: deployed
REVISION: 3
TEST SUITE: None

Here I deployed chart from repository. So there is no changes in chart but everytime I hit upgrade command it create new revision. If there is no changes in chart, I think there must not be new revision, instead it should be discarded.
Upgrading helm won't make any changes to the kubernetes resources. However that revision number doesn't make sense to me.

A couplt things here...

Helm follows semantic versioning. For a helm upgrade to not increment the release when there is no change is a change in behavior. So, Helm can't do it prior to a v4 release. Are you asking this as a feature request?
It is debatable if Helm should not increment the release. The action was to perform a release whether there were changes or not. In each case an action was taken. From an auditing point of view, it's a good idea to record the details. People interested in security request to see these things. Can you please make a case for not recording the upgrade with a new release?

There is a subtle element here... Helm is a package manager rather than a general tool to manage Kubernetes applications. A general Kubernetes application management tool would sit at a level higher in the stack than Helm.

@mattfarina so what would be the consistent approach whenever I have to rollback changes? Should I go with Kubernetes itself to undo deployment rather than using helm for that purpose?

@diwap Maybe the first question is, why are you deploying an upgrade when there are no changes?

ping

I'm going to close this ticket due to inactivity, but please re-open if this still needs to be addressed. Thanks!

  I for one would have loved to see such a feature.  Maybe a command line switch - such as --nochangenorevision - to inform HELM to not create a new revision if there are no changes in the deployment.

 I for one would have loved to see such a feature. Maybe a command line switch - such as --nochangenorevision - to inform HELM to not create a new revision if there are no changes in the deployment.

@ak2766 Would you be interested in designing/contributing a solution here? (it might not be --nochangenorevision, since there are probably several ways to achieve the desired behavior here and e.g. hooks like @igorushi mentions would need to be accounted for).

@gjenkins8 I would like to provide a solution. It seems to be simple to implement and will have value in our CICD.
The PR with code and tests will be enough you believe? Or it will require HIP (https://github.com/helm/community/blob/main/hips/hip-0001.md)
cc @bacongobbler @mattfarina

Bump, any update here? Would love to have this feature.

Thanks @igorushi -- I missed your PR. I will take a quick look myself (as a community member), and add to the the helm developer weekly meeting to hopefully get attention from a maintainer.

Hi @gjenkins8, did you had a chance to look?

@diwap Maybe the first question is, why are you deploying an upgrade when there are no changes?

@mattfarina I have found a use-case for this. Skaffold runs helm upgrade for each release on any code change. Upgrading even when there is no change adds significant time for redeploying a development environment on change
Here's a Skaffold issue related to this usecase https://github.com/GoogleContainerTools/skaffold/issues/5406. To only run helm upgrade for the changed release "requires a large refactor in our codebase" according to @ericzzzzzzz's response.
@igorushi's PR would allow skip-empty to be added as a Helm flag in Skaffold, allowing much faster development loops when using Helm to deploy.

Hi @gjenkins8 - is there a way to get attention on this PR to get this functionality in Helm? It would be really valuable for me.


Support Snake Cased URL Parameters

Currently if you use a snake_cased URL parameter without defining an
operationId in the Swagger file, the name for the function that is
generated will contain curly braces, which is invalid PHP. This fix
resolves that by correctly un-snaking the variable and camel casing it.

Thanks !


Bug for Menu order changing with each reload

Discussed in https://github.com/aminalaee/sqladmin/discussions/629

Originally posted by bilalovmc September 23, 2023
set - not ordered
the menu changes order every time you start, which leads to confusion
class Menu:
    def __init__(self) -> None:
        self.items: Set[ItemMenu] = set()

    def add(self, item: ItemMenu) -> None:
        for root in self.items:
            if root.name == item.name:
                root.children.update(item.children)
                return
        self.items.add(item)

list solved a problem
class MenuMY:
    def __init__(self) -> None:
        self.items: Set[ItemMenu]= list()
```</div>

Hi, thank you for fixing this.
I don't think this has been tagged though. Thank you

yes, I will prepare the release today or Monday.


Added better error message for 401 errors from JIRA

Added better error message for 401 error, handled /n added by mac base64 to make more resiliant and updated jenkins test server docker file

@jimzucker , Thank you for your proposed fix.  I have included some in-line comments; please address the TODOs and check the check boxes when verified/changed.
@tabladrum / @jdamick :  I have confirmed that @jimzucker's fix is required, as it resolves some confusion caused by the Mac implementation of base64 encoding, commonly used to generate the basic authentication username:password combo for the JiraFeatureCollector.  Once the above-noted check boxes are addressed, I am okay with this pull request.  This will also not derail my currently feature development.

@jimzucker @amp5208 can we do this PR to master? It is requesting merge to a feature branch.

Agreed - I missed that.  @jimzucker , please modify PR to push to Hygieia upstream master.  Also, be sure that your changes work with the modifications going into PR #606

LGTM


about term prefix

I would like to know does the term prefix support multiple input like "A,B" ?
Thanks.

Hello,
We do not support having multiple term prefixes for a package and don't plan on introducing such a feature.

Having multiple term prefixes introduces a problem of potential conflicts when there are foo and prefix_foo terms.
Multiple term prefixes would also make it impossible to use the seed feature of poe2arb, as the tool would not know which term is supposed to have which prefix (and introducing that to metadata is something we're not planning to do).

The use case for term prefixes ideally is to separate translations of multiple packages within a project:

Term prefix filtering
If you wish to use one POEditor project for multiple packages, ideally you do not want one package's terms to pollute all other packages. This is what term prefixes are for.
—https://github.com/leancodepl/poe2arb#term-prefix-filtering

I got it. Thanks for reply. 😄


QnA Maker without Azure Search

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
Is it possible to provision the QnA Maker without Azure Search for Enterprise Template?
Describe alternatives you've considered
Additional context

Hi @NobinJoseRad, as of today Azure Search is a requirement for using QnA Maker since it is the backend which surfaces the answers. https://docs.microsoft.com/en-us/azure/cognitive-services/qnamaker/overview/overview


Make workload labels not a single-element tuple.

Not sure how that snuck through.

Bizarre. Maybe some weird behavior of Black autoformatting? This is why I always have it run on save.


Add content packages endpoint

https://github.com/rstudio/connect/pull/28446

Possible recipes:

What content uses the X version of dependency Y?
Where is the dependency pinned in the requirements file vs when you can just redeploy the content.
How to collect the content that requires a dependency bump and then contact the owners.


Plugin Stops Working on Current Buffer After Closing Other Buffers.

Problem:
I've encountered an issue with the nvim-ts-autotag plugin that I'd like to report. The problem occurs when using the plugin alongside a buffer-closing mapping. After executing a mapping to close all buffers except the current one, the nvim-ts-autotag functionality ceases to work in the current buffer. This issue seems to affect the plugin's ability to automatically close tags.
Steps to Reproduce:

Install and configure nvim-ts-autotag for automatic tag closing in Neovim.
Create multiple buffers with HTML, XML, or JSX content.
Execute a mapping or command to close all buffers except the current one

Expected Behavior:
The nvim-ts-autotag plugin should continue to function as expected in the current buffer, automatically closing tags for supported languages.
Actual Behavior:
After closing other buffers as described in the steps to reproduce, the nvim-ts-autotag plugin stops working in the current buffer. It no longer closes tags automatically.

@windwp can we re-open this issue ?

happened to me too. I think this issue should be reopened

Hey folks if you're still having issues, I've begun maintaining a fork over @ https://github.com/PriceHiller/nvim-ts-autotag until windwp is active again.
Give it a shot and if it's still not working then open an issue over there and I'll investigate 🙂.


Feat multiselect option styling

Added style customization for multiselect option item MultiSelectedOption
SelectProps type refactor (Too much props, hard to read)
Added script "test:update": "jest __tests__ -u" for updating snapshots
Removed unused accessability type
Added placeholderTextColor = COLORS.GRAY as default value

multiSelectionOptionStyle  should be add to website/docs/api/styles.md


Change Card.add_label to pick the correct resource

POST to /labels/ if creating a label by name.
POST to /idLabels/ if assigning a label (pass Label instance).

@plish I agree they should be two methods .. I've got a fancy singledispatch-based implementation here: https://github.com/plish/Trolly/pull/36/files
It's outdated now, but I can update if you like the approach.

@jean never seen that before, but it is definitely a lot cleaner. Think that is the better approach.

@plish I'm at a C# shop now, so I was getting envious of them using multiple-dispatch all over the place. And turns out at least single-dispatch is easy :-)
I'm depending on singledispatch from PyPI for 2.7 compatibility. For 3.4+ it's part of functools. I wouldn't mind if Trolly went 3.4.
The only thing that bothers me about the approach in #36 is that the different implementations return different things: the original (/labels) API returns JSON for the new label, and the new (/idLabels) returns (logically) a list of label ids.
I don't think that this is a problem, since in the new case you already have the label object with all its properties.


Add taggingLabel for single and multiple select

issue #938

Please merge this one soon...

Sorry but there are so many issues to backtrack, can you post a Plunkr demonstrating the bug so I can verify this fixes it?  Maybe there already is a demo of the problem but I can't find it and would like to have it documented here for future reference. Thanks @viniciusdacal

In this first Plunkr you can see the error.
http://plnkr.co/edit/7tPA05od2FUCbZRqj8UY?p=preview
Just try to add a new item in the single select, It should show a label, but nothing happens.
In the multiple select, try to type "Adam" and you will get the follow error:
Error: [ngRepeat:dupes] Duplicates in a repeater are not allowed. Use 'track by' expression to specify unique keys. Repeater: person in $select.items track by person.name, Duplicate key: Adam
On this follow Plunkr, I just add my current version of select.js with the fixes.
http://plnkr.co/edit/bG7yvD8YotzwexvSHti0?p=preview
Thanks @brianfeister

@brianfeister, as this pull request fixes a critical function (taging on single select), can you allocate the time for merging it to master ?

+1

#1006

@brianfeister any news about it?

+1

+1

+1

+1

+1

+1

+1

Anything new?

+1

+1

+1

:+1:

+1

+1

Is there anything I could do to help having this PR merged?

any news about it?

+1

+1

Any news ?

We forked viniciusdacal's version and use it for like 6 months already.

As was mentioned here for me the easiest workaround was just to use a regular multiple with tagging and set limit="1".

this works in angular ^1.4?

@viniciusdacal your fork works in angular ^1.4?

Any news? It's been almost a year :(

This needs rebasing.

thanks @wesleycho.
I will work on this.

@wesleycho  updated.

any news about the revision?

There are still conflicts apparently, can you rebase again?
Are there no associated tests?

@user378230 when I rebase my branch last time, I got the current code and added the changes again. so, this code has all changes from the day I rebased.

+1

@user378230 when I rebase my branch last time, I got the current code and added the changes again. so, this code has all changes from the day I rebased.

Thats fine, just still need to make sure no changes are dropped prior to commit of copy-paste.
This still needs test(s), rebasing, example updating & squashing though. Once that is done, I'll merge.
Thanks for your patience and hard work! :+1:

I think you should add : ctrl.taggingLabel = '(new)'; in controller
Without this, if taggingLabel attribute doesn't exist ctrl.taggingLabel is not initialized and newItem = ctrl.search+' '+ctrl.taggingLabel; -> ctrl.search+' '+ undefined
There is a problem with the watchCollection : when the watch is throw, the tagging element is removed -> use a refreshDelay="500" to see


What is the best way to upgrade chatwoot?

I saw the message An update 3.6.0 for Chatwoot is available., just wonder what is the best way to upgrade to newer version if I'm using this template? Wait for this template update?

my bad, I will run the action soon

action has been ran, you can now redeploy your chatwoot service

Thanks @brody192, you are awesome!


np.sum() Is supported on numsharp0.20.5, but not on NumSharp0.30.0

np.sum() Is supported on numsharp0.20.5, but not on NumSharp0.30.0
the exception message :"Specified method is not supported."

What datatype are you trying to use?

double s = np.sum(w * w);
w data type is NDArray;

I mean what will this output on NumSharp 20.5?
Console.WriteLine(w.dtype);
Console.WriteLine(s.dtype);

At version 30.x+ @Oceania2018 has removed many supported DTypes which might cause NotSupportedException or NotImplementedException. Some even return null.

Thank you very much for your attention, the following is the supplementary content.

same problem. Is there a walkaround for now?

@lijianxin520 I was not able to reproduce this locally, can you or @bigdimboom provide with a simple unit test that reproduces this and I'll take a deeper look.

Hello,
I encountered this problem as well and here's some data to help investigate:

A sample code which reproduces the problem on my Mac - Visual Studio. https://github.com/ppsdatta/NpSumIssue
With version 0.30.0 the code fails with the not supported error.

With version 0.20.5 the code works without runtime exception.

having exact same error, numsharp 0.30.0

same error with NumSharp 0.30.0, with np.sum(NDArray[])

I also encountered the same error.
When the value of elements of NDArray is double, this error certainly occur.
To change the type double to float works well in my case.

same error here, sum() works for int but not for double, using version 0.30.0


Unable to parse errors

Lately when I've been trying to query Active Campaign's api, it has been returning what looks like an out of service message:

We are currently having some issues.  Please check back soon.

However, it looks like the node wrapper attempts to JSON.parse() this response, and this causes the script to crash.
Here is the relevant stack trace:

We are currently having some issues.  Please check back soon.

^

SyntaxError: Unexpected token <
    at Object.parse (native)
    at Request._callback (/Users/eahenke/github/integrator/node_modules/activecampaign/lib/Connector.js:190:35)
    at Request.self.callback (/Users/eahenke/github/integrator/node_modules/activecampaign/node_modules/request/request.js:200:22)
    at emitTwo (events.js:87:13)
    at Request.emit (events.js:172:7)
    at Request.<anonymous> (/Users/eahenke/github/integrator/node_modules/activecampaign/node_modules/request/request.js:1067:10)
    at emitOne (events.js:82:20)
    at Request.emit (events.js:169:7)
    at IncomingMessage.<anonymous> (/Users/eahenke/github/integrator/node_modules/activecampaign/node_modules/request/request.js:988:12)
    at Object.forward (/usr/local/lib/node_modules/strongloop/node_modules/strong-agent/lib/proxy.js:79:23)
    at IncomingMessage.eval (eval at wrap (/usr/local/lib/node_modules/strongloop/node_modules/strong-agent/lib/proxy.js:201:20), <anonymous>:3:21)
    at emitNone (events.js:72:20)
    at IncomingMessage.emit (events.js:166:7)
    at endReadableNT (_stream_readable.js:905:12)
    at /Users/eahenke/github/integrator/node_modules/loopback/node_modules/continuation-local-storage/node_modules/async-listener/glue.js:188:31
    at nextTickCallbackWith2Args (node.js:441:9)
    at process._tickDomainCallback (node.js:396:17)
    at process.fallback (/Users/eahenke/github/integrator/node_modules/loopback/node_modules/continuation-local-storage/node_modules/async-listener/index.js:450:15)```

Also it appears using npm install activecampaign pulls down an outdated version of the module, which lacks the most recent two commits 17437e507c705ea8b43930bac512a39f85120788 and 713a8a317d4ed621257ace2f9a9aa49d99af92d9.  It looks like former of those commits was aimed at this issue by adding a try/catch block for the JSON.parse.  However, this does fix the problem.  After rejecting the promise when the parse fails, the code outside the block runs and it tries to parse again, this time failing at line 154.

Same issue.
NPM is now on v1.2.1 :)

@molinto is correct; we are now on version 1.2.1, and that should fix this issue for you going forward.


Streamline Travis builds

Reduce Travis build matrix by 50%

Drop Python 3.4
Only run latest ES (1.7.5) with latest Python (3.5). This is a tradeoff for limited future-proofing.

@benghaziboy @MichaelButkovic @kand

👍


BytesCache bug leading to duplicate file reads for small files on remote storage

I'm working on an Azure Datalake Gen2 package using fsspec and encountered strange behavior with BytesCacheing, where the file being read from the datalake and calling compute() on the cached dataframe appears as an exact duplicate of rows of the same dataframe.
It appears to be caused by the _fetch method in BytesCache when reading a file into Dask.  During what should be the first read when calling "dd.read_csv()", the value of start (when none) is passed as zero, but when calling the .compute() method on the dataframe, the file gets read again, leading to the duplication of rows.  Explicitly setting start, end= 0,0 like:
    def _fetch(self, start, end):         # TODO: only set start/end after fetch, in case it fails?         # is this where retry logic might go?         if self.start is None and self.end is None:             # First read             start, end = 0, 0             self.cache = self.fetcher(start, end + self.blocksize)             self.start = start
appears to fix it for me.  Have you observed any issues with BytesCacheing elsewhere?

Continuing to work on the filesystem for Azure Datalake, I looked at the HTTPFileSystem implementation.  There, the method _fetch_all() and AllBytes was was introduced.  I replicated this design pattern in my work on adlfs by adding that same class in my package's core.py file.  But would it make sense to move the AllBytes class from the http.py implementation into core.py?

Just FYI, Martin is out for a few weeks, so responses will be a bit slow here.
At a glance, AllBytes looks similar to core.BytesCache. I notice that there's some leftover debug code with blocksize=None in there.

AllBytes exists for the case where we didn't know the size of the remote HTTP url, because the server wouldn't say, and then we ended up downloading all the data, which is less than the prescribed block size. This is a little specific; in the case we know the size, and it is smaller than the block size, BytesCache should behave the same way. I suppose it is a reasonable caching policy anyway, by which we say "download everything" regardless of block size - this is done in testing in places. It is not a good general-purpose cache, because we expect to want to read parts of very large files in a random-access manner!

(it would be better to isolate the bug in BytesCache and test against one of the backend implementations which use it)

In case this is useful ... we just hit this to through a dask dataframe read_csv call.
dd.read_csv('s3....').compute()
The file gets doubled -1 (column appears as a row twice).
Reverting to fsspec 0.4.1 seems to fix ... I haven't chased this all the way down into the fsspec stack.

@cottrell what version of fsspec did you observe the buggy behavior on?

The file gets doubled -1 (column appears as a row twice).

Can you clarify that?

Version 0.4.2 was buggy. 0.4.1 was ok.
This is a minimal version dump of a test env I used:
$ pip list
Package           Version
----------------- ---------
astroid           2.2.5
backcall          0.1.0
boto3             1.9.216
botocore          1.12.216
certifi           2019.6.16
cloudpickle       1.2.1
dask              2.3.0
decorator         4.4.0
docutils          0.15.2
fsspec            0.4.2
ipython           7.7.0
ipython-genutils  0.2.0
isort             4.3.21
jedi              0.15.1
jmespath          0.9.4
lazy-object-proxy 1.4.1
numpy             1.17.1
pandas            0.25.1
parso             0.5.1
pexpect           4.7.0
pickleshare       0.7.5
pip               19.2.2
prompt-toolkit    2.0.9
ptyprocess        0.6.0
Pygments          2.4.2
pylint            2.3.1
python-dateutil   2.8.0
pytz              2019.2
s3fs              0.3.3
s3transfer        0.2.1
setuptools        41.0.1
six               1.12.0
toolz             0.10.0
traitlets         4.3.2
urllib3           1.25.3
wcwidth           0.1.7
wheel             0.33.4

@cottrell , it would help us a lot if you could post a code sample which, in isolation, shows the problem - something like Tom's code above (which does not seem to reproduce it).

Here is some benign data that reproduces the error with the versions above:
import dask.dataframe as dd
import pandas as pd
df = pd.DataFrame(
    {'TICKER': {0: 'A', 1: 'AA', 2: 'AAAP', 3: 'AAC', 4: 'AAL'},
         'MIN_DATE': {0: '1999-11-18',
               1: '2016-11-01',
                 2: '2015-11-11',
                   3: '2014-10-02',
                     4: '2005-09-27'},
          'MAX_DATE': {0: '2019-08-26',
                1: '2019-08-26',
                  2: '2018-02-09',
                    3: '2019-08-26',
                      4: '2019-08-26'},
           'COUNT': {0: '4973', 1: '708', 2: '566', 3: '1233', 4: '3502'}})

filename = 's3://SOMELOCATION/test.csv'
df.to_csv(filename)
dd.read_csv(filename, dtype=str).compute() # ok
dd.read_csv(filename).compute() # fails

It is the count column that complains.
ValueError: Mismatched dtypes found in `pd.read_csv`/`pd.read_table`.

+------------+---------+----------+
| Column     | Found   | Expected |
+------------+---------+----------+
| COUNT      | object  | int64    |
| Unnamed: 0 | float64 | int64    |
+------------+---------+----------+

The following columns also raised exceptions on conversion:

- COUNT
  ValueError("invalid literal for int() with base 10: 'COUNT'")

Usually this is due to dask's dtype inference failing, and
*may* be fixed by specifying dtypes manually by adding:

dtype={'COUNT': 'object',
       'Unnamed: 0': 'float64'}

to the call to `read_csv`/`read_table`.

But you can see on debug that the number of rows is doubled:
In [23]: %debug
*** NameError: name 'pdb' is not defined
> /home/ubuntu/anaconda3/envs/tt/lib/python3.7/site-packages/dask/dataframe/io/csv.py(178)coerce_dtypes()
    176             rule.join(filter(None, [dtype_msg, date_msg]))
    177         )
--> 178         raise ValueError(msg)
    179
    180

ipdb> up
> /home/ubuntu/anaconda3/envs/tt/lib/python3.7/site-packages/dask/dataframe/io/csv.py(74)pandas_read_text()
     72     df = reader(bio, **kwargs)
     73     if dtypes:
---> 74         coerce_dtypes(df, dtypes)
     75
     76     if enforce and columns and (list(df.columns) != list(columns)):

ipdb> df.shape
(11, 5)

ipdb> df
    Unnamed: 0  TICKER    MIN_DATE    MAX_DATE  COUNT
0          0.0       A  1999-11-18  2019-08-26   4973
1          1.0      AA  2016-11-01  2019-08-26    708
2          2.0    AAAP  2015-11-11  2018-02-09    566
3          3.0     AAC  2014-10-02  2019-08-26   1233
4          4.0     AAL  2005-09-27  2019-08-26   3502
5          NaN  TICKER    MIN_DATE    MAX_DATE  COUNT
6          0.0       A  1999-11-18  2019-08-26   4973
7          1.0      AA  2016-11-01  2019-08-26    708
8          2.0    AAAP  2015-11-11  2018-02-09    566
9          3.0     AAC  2014-10-02  2019-08-26   1233
10         4.0     AAL  2005-09-27  2019-08-26   3502

Yes, it appears to be fixed with 0.4.3.


Invoke wsfunction

Hi, I'm trying to fetch my courses using core_enrol_get_users_courses.
I tried using the following code
import { Client } from "joodle";

const client = new Client({
  baseURL: "https://elearning.dm.unipi.it",
  token: "mytoken",
});

(async () => {
  try {
    const courses = await client.invoke("core_enrol_get_users_courses",{
        userid: "myuserid"
    });
    console.log(courses)
  } catch (error) {
    console.error(error)
  }
})();

but seems like Client class is not exported by your module and I also have no idea how to pass the parameters.
I really appreciate any kind of help.

Client is an abstract class, Joodle is the exported implementation of Client that you need to use.
Taking your code, it would need to look something like this:
import { Joodle } from "joodle";

const client = new Joodle({
  baseURL: "https://elearning.dm.unipi.it",
  token: "mytoken",
});

// ... use `client` here

Let me know if you need anything else!


Docs: EOL note for 3.1

VERSION_NUMBER is automatically being substituted with the content of the VERSION file in book.json. This PR adds a new configuration field "version" with the ArangoDB version (VERSION_NUMBER), e.g. v3.1.29 or 3.4.devel ....
This version string is then used by the arangodb-outdated plugin to add a sentence about EOL of vX.X. If no version could be determined (should never be the case), the entire sentence is left out as it would make little sense without a version. The second sentence about the docs being obsolete is shown regardless.
However, the updated plugin replaces the Latest Manual link to https://docs.arangodb.com/latest/<path-the-user-is-looking-at> with label Try latest. If the structure / file names didn't change between the viewed version and the latest version, then the user will get to the latest online docs with a single click. If it can't be found, he will be redirected to the latest Manual as before. The node-documentation routing could be later improved to try to redirect to the closest parent page instead of the Manual.
Related PR for building on Windows in Cygwin: https://github.com/arangodb/arangodb/pull/5684
There seem to be Swagger related build issues at the moment that need to be sorted out.

Preview build: https://docs.arangodb.com/review_eol_31/
No build errors on my desktop PC. Not sure what's wrong on my laptop, maybe CRLF Windows line endings again?


table view crash

The browser crashes when the amount of data is high

we are working on a total rewrite of the table chart. In the meantime, you can add row limit or pagination (from the Customize tab) to mitigate this issue.

@ktmud
thx
But the demand side needs to query all the data, and the data volume is quite large

Hi is it resolved?

Hi is it resolved?


MKL-DNN LBR-GRU Inference Integration (FP32 LBR-GRU)

Description
Reopen #15621 here. We integrated the mkl-dnn Linear-Before-Reset GRU into MXNet. Currently, it supports FP32 inference. Please take some reviews on this PR.@ciyongch @TaoLv @pengzhao-intel
Performance
We tested the performance of FusedRNN with mode='gru' using the same dimension as that in PR#14713, i.e. seq_length = 300, batch_size = 20, input_size = 800, hidden_size = 800.

mode
Layer
Direction
MXNET_USE_MKLDNN_RNN=0
MXNET_USE_MKLDNN_RNN=1
SpeedUp

Throughput (samples/sec)
Latency (ms)
Throughput (samples/sec)
Latency (ms)
Throughtput
Latency

gru
1
1
430.03
20.43
806.27
4.28
1.87
4.78

gru
1
2
218.58
119.50
416.55
8.58
1.91
13.93

gru
5
1
89.47
100.07
177.52
21.20
1.98
4.72

gru
5
2
39.68
611.38
71.15
46.45
1.79
13.16

We also compared the performance of this PR with that of the previously integrated LSTM, vRNN tanh, vRNN Relu on branch master. It seems that there is a distinct regression with mode='lstm'.

Mode
Layer
Direction
 a26af2b
This PR ( cfc6910 )
Gap

Throughput (samples/sec)
Latency (ms)
Throughput (samples/sec)
Latency (ms)
Throughput
Latency

lstm
1
1
630.78
4.82
670.23
4.87
1.06
0.99

lstm
1
2
313.71
9.68
338.51
9.72
1.08
1.00

lstm
5
1
139.85
23.59
138.22
23.48
0.99
1.00

lstm
5
2
54.63
51.19
54.27
51.28
0.99
1.00

rnn_tanh
1
1
1573.45
2.44
1576.23
2.51
1.00
0.97

rnn_tanh
1
2
836.43
4.63
830.33
4.67
0.99
0.99

rnn_tanh
5
1
381.32
11.44
379.88
11.50
1.00
1.00

rnn_tanh
5
2
159.76
24.92
149.86
24.90
0.94
1.00

rnn_relu
1
1
1536.55
2.65
1540.29
2.75
1.00
0.96

rnn_relu
1
2
805.00
5.09
807.68
5.06
1.00
1.01

rnn_relu
5
1
373.27
12.41
377.79
12.32
1.01
1.01

rnn_relu
5
2
154.21
26.93
153.80
26.61
1.00
1.01

what's the reason to open a new PR instead of the previous one?

@pengzhao-intel I incorrectly used git rebase, which introduced all the changes on apache/incubator-mxnet/master since last merged commits into this branch.

@pengzhao-intel I incorrectly used git rebase, which introduced all the changes on apache/incubator-mxnet/master since last merged commits into that branch. So I cut off a new branch.

Thanks for the explanation.

Do all comments in the original thread are resolved?

Do all comments in the original thread are resolved?

Yes, all comments are resolved.
@TaoLv Could you check on this PR for LBR-GRU integration again? Specifically, the type of input params of GetMKLDNNRNNCacheMemorySize is changed to size_t,
https://github.com/apache/incubator-mxnet/blob/fd1e21443eaad240210079b0fbebd5c062f06663/src/operator/nn/mkldnn/mkldnn_rnn_impl.h#L138-L144
and using reference or pointer to access a memory.
https://github.com/apache/incubator-mxnet/blob/fd1e21443eaad240210079b0fbebd5c062f06663/src/operator/nn/mkldnn/mkldnn_rnn_impl.h#L304
https://github.com/apache/incubator-mxnet/blob/fd1e21443eaad240210079b0fbebd5c062f06663/src/operator/nn/mkldnn/mkldnn_rnn_impl.h#L472
https://github.com/apache/incubator-mxnet/blob/fd1e21443eaad240210079b0fbebd5c062f06663/src/operator/nn/mkldnn/mkldnn_rnn_impl.h#L490-L491

@pengzhao-intel This PR might also contain flaky unit tests with gpu context. For instance,
test_operator_gpu.test_rnnrelu_sym: http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-gpu/detail/PR-15741/4/pipeline
test_operator_gpu.test_rnnrelu_sym: http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Fwindows-gpu/detail/PR-15621/2/pipeline
test_operator_gpu.test_rnntanh_bidirectional: http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-gpu/detail/PR-15621/2/pipeline
test_operator_gpu.test_rnntanh_bidirectional: http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-gpu/detail/PR-15621/8/pipeline

Could you analyze why the flaky test is generated? It's from the numerical difference or algorithm level difference.

I tried to reproduce the failures on our internal GPU platforms, but all worked well. And it should be noticed that the source code was compiled with cuda-9.0 and cudnn-9.0-linux-x64-v7.1.2, which are older that the oldest version tested by CI (cuda-10.x and cudnn-xxx-v7.6).

@ciyongch please take a review again :)
@DickJC123 @ptrendx some common codes are adjusted to make it work for both CPU and GPU based on your previous approach. Would you mind take a look as well?

cc @szha @eric-haibin-lin

Thanks for the heads up about the changes surrounding gpu code.  With the reported flakiness, I'd like to have tomorrow (Friday) to investigate.

@DickJC123 Thanks for your patient. And FYI, it seems that the possible flaky tests become effective with the edited UTs for RNN variants. I have tried to modify the code following the instructions from https://github.com/apache/incubator-mxnet/pull/14476#pullrequestreview-225789440, but it didn't work on *UNIX system (CI has passed on windows-gpu, while it was failed on *UNIX-gpu with test_gluon_gpu.test_layer_bidirectional_varseqlength). Though the modifications are not included in this PR, you can find it from this link. Need your help since I'm not familiar with GPU :)

The lessons of https://github.com/apache/incubator-mxnet/issues/15034 and https://github.com/apache/incubator-mxnet/pull/15056 are that the GPU workspace should be allocated from the MXNet tempspace resource.  Since the flakey tests of #15034 seemed to appear on a P40 GPU, I'm trying to get access to such a system to hopefully repro the current failure, a necessary step before we can say we've solved the problem with this PR.
Also, I notice that this PR expands the testing from 1 problem-size to 36 for many of the tests.  I'm not sure if this is a factor in the apparent flakiness of the tests.

From the CPU perspective, the FusedRNNCells are constructed in three ways,

Fuse all the layers, when input_size == state_size, direction == 1
Fuse all the layers except for the first layer, when input_size != state_size, direction == 1
No fusion, layer by layer, when direction == 2

Thus we intended to expand the tests to allow for the three cases above. It is possible that the expanded test causes the apparent flakiness of the tests. I'm not sure if there are some corner cases with the tests, which may be rarely used in real production.

@DickJC123  And I also found that reserve_space_ is allocated from Storage. Is there a problem with this?
https://github.com/apache/incubator-mxnet/blob/b2aaf966eb0700dc9923f45253f1332e88eced4a/src/operator/rnn-inl.h#L1495-L1497

I need some help understanding exactly which flakiness we're trying to track down here:
- I see two runs posted by @zixuanweeei above from PR 15621where one output is all 0's.  Do we think this serious behavior is still present?
- It seems like all failures from this PR 15741 would be cured by doubling the atol (to 0.0002).  This doesn't seem so terrible, but are we trying to uncover why, given that these failures only occur when the framework is built with both MXNET_USE_MKLDNN=1 and MSHADOW_USE_CUDNN=1?

Not sure why the outputs of fused cell are all zeors. We made mem_space_ for MKL-DNN, which is allocated from Storage in #15621 , be allocated from tempspace resource in this PR.
https://github.com/apache/incubator-mxnet/blob/b2aaf966eb0700dc9923f45253f1332e88eced4a/src/operator/rnn.cc#L272-L275
Does this matter?
And for the another one, I think we should reproduce the failures at first. I have looked through the Forward interface trying to locate the problem and found no joint use of temp space. @DickJC123 Would you mind checking it again? If the failures don't appear again, I think we can just move further since MKL-DNN is going to be update to another new version. And I think the stateful FStatefulComputeEx interface of RNN needs some refactoring after update. What's your opinions? @pengzhao-intel @TaoLv @ciyongch

Seems the failures occured this time, when the framework is built with MXNET_USE_MKLDNN=0 and MSHADOW_USE_CUDNN=1. http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-gpu/detail/PR-15741/17/pipeline/311

I was not able to repro the CI failures despite running 100's of iterations of test_rnntanh_bidirectional on the same GPU arch (52=Maxwell) and cuDNN version (7.5) as the CI.  The MXNet CI is a little unusual in that the framework is build against the cuDNN 7.6.0 header, but then the linked lib is from cuDNN 7.5.
I notice the centos gpu CI runner hasn't seen any rnn test failures.  It runs linked against cuDNN 7.6.0, but then also is not compiled with MXNET_USE_MKLDNN.  To eliminate one of these differences, I've started an experimental '[Do not merge]' PR https://github.com/apache/incubator-mxnet/pull/15847 with the linked cudnn lib bumped up to 7.6.0.  It may be worth experimenting with cuDNN 7.6.1 since the cuDNN release notes for 7.6.1 mention resolved rnn issues.
The last failure mentioned by @zixuanweeei seems troubling in that there is no apparent correlation between the small values of the output tensors.
I have not studied the code changes of this PR yet, preferring to have a local repro mechanism in hand first.  If that is not possible, then I may have to troubleshoot the flakiness purely through the MXNet CI.

Thanks for your efforts @DickJC123 . Hope PR #15847 will work out one of the possible problems :)

Cherry picked from commit 1cf63e1 according to https://github.com/apache/incubator-mxnet/pull/15847#issuecomment-522840815

@TaoLv please take a review again and I plan to merge after the CI pass.

If it still needs lots of efforts to pass ci, we can drop it and wait to our 1.0 upgrade.
@zixuanweeei you can make a decision :)

@pengzhao-intel Sure. There are lots of refactor work both on MKL-DNN RNN and naive RNN. At present, MKL-DNN related stuff is under review. Perhaps, we can just drop this PR, and start a new one from current commit on master.

What does Linear-Before-Reset mean?

What does Linear-Before-Reset mean?

See the different definition of c(t) in GRU and LBR GRU: https://intel.github.io/mkl-dnn/dev_guide_rnn.html#Linear-before-reset-GRU

closing this PR since we will migrate it with MKL-DNN 1.0.


Allow live previews of ecosystem theme

Closes https://github.com/Qiskit/qiskit_sphinx_theme/issues/348.
Our live preview mechanism only allows one site per deployment. It would be highly involved to try to have it deploy two sites simultaneously, both the Ecosystem and Qiskit themes.
It seems "fine enough" to only have one live preview at a time because our PRs only focus on changing one theme at a time. If we need to see how it impacts both, we can either:

Rely on the artifact upload from CI, or
Run CI twice so we have two previews

The default theme will always be the Qiskit theme, since that is where 90% of our custom styling code lives. Then, in your PR, you can temporarily toggle a line in the Dockerfile to have the Ecosystem theme build. I considered something more "elegant" like having you set a GitHub label on the PR, but it seemed way too complex.
This isn't the most "elegant" solution, but it's simple and gets the job done.

I can't check that it worked since the second deployment overwrote the first one, but I believe it. I think it'll be very easy to forget that you've toggled the Dockerfile and not revert the change. I think the build on PR label option is elegant, and it's nice to be able to sort PRs by ecosystem vs. Qiskit too. Is the difficulty there how to pass the build option to the Dockerfile so it know which tox env to use?


Adding a badge for a friend

Username and Discrim: Ariana aka deznuts#2929
User ID:<PHONE_NUMBER>92309248
Image Link: https://emoji.gg/assets/emoji/4073_daddy.png

i manually uploaded the image to imgur cause it has to be uploaded either on there or through discord's cdn.discordapp, mainly because vulns (incase).
but done :D

np <3


Unable to set drag image for tree node

Hi,
I am trying to implement multiple node drag / drop functionality similar to google drive.
While the function can be implemented quite easily with action mapping ( thanks dev ! ), there is no way to change the behavior of dragging ghost image.
We are usually able to change the image with setDragImage.  I tested the api with https://jsfiddle.net/f47zzg7v/2/ .
The api seems to not working in dragStart event. It seems to me that setTimeout is causing the problem here. I remove the line and setDragImage is working like a charm.
https://github.com/500tech/angular-tree-component/blob/7314f893f1182fed36b29f27bd1a40d0b0fec04a/lib/directives/tree-drag.directive.ts#L25
It also seems to me that drag event are not implemented. Is there a particular reason why ? It would be very helpful for user who wish to implement a more complex drag image using absolute position dom.

Hey,
Drag is something that needs to be rewritten to support mobile using regular mouse / touch events.
But for now I guess it's possible to fix the timeout issue and the drag event.
Maybe if you are already into the code - could you make a pull request?
Thanks

Hi,
I can write a patch to fix both issue i mention here. I just want to
confirm the reason behind timeout and absent of drag event.
On Tue, Jul 11, 2017, 6:38 PM adam klein<EMAIL_ADDRESS>wrote:

Hey,
Drag is something that needs to be rewritten to support mobile using
regular mouse / touch events.
But for now I guess it's possible to fix the timeout issue and the drag
event.
Maybe if you are already into the code - could you make a pull request?
Thanks
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/500tech/angular-tree-component/issues/348#issuecomment-314404972,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAnsp56ug1uYkfqHxP3miHS8SVoE6fh5ks5sM1CvgaJpZM4OPHQr
.

I think for now better leave it as it is and make a fork to fit your needs.
Because I plan to refactor the drag & drop completely soon


Consolidating Packages

We could combine the Elixir and native client repositories to simplify development and setup. Let me know your thoughts on this, and if there's any major drawbacks I'm overlooking.
There would then be 1 repo per platform:

liveviewnative/swiftui

Package.swift
mix.exs
lib - Elixir code
Sources - Swift code

liveviewnative/jetpack

settings.gradle.kts

Would need to rename lib to something else for one of the packages, probably the Kotlin one? Both let you configure this.

mix.exs

Currently no Elixir Jetpack library, but that would be top level too.

lib - Elixir code
client? - Kotlin code

How does this simplify things?
1. Development
For example, let's say we want to add a modifier to the SwiftUI client.
Currently, we need to open 2 PRs:

Open a PR to liveviewnative/live_view_native_swift_ui with the modifier schema
Open a PR to liveviewnative/liveview-client-swiftui with the modifier struct

These need to be reviewed and merged together. Then, if we ever need to update the schema, 2 more PRs need to be opened and synced.
With a combined repository, we could simply open one PR with the necessary changes to both libraries.
2. Releases
When releasing, we need to make sure the versions are synchronized with each other. With the libraries being in the same repo, releases can be coordinated more easily.
3. Setup/DX
When a user is setting up their project to adopt LVN, they need to be aware of 2 repos per platform. If the repositories were consolidated, it would only require them to know about 1 repository for each platform they target.
Their dependencies for each platform still need to be updated separately to point to the same version.

I'm :+1: on this idea. Would also provide a framework for future clients to follow and keep everything in one tidy place. Let's discuss on standup today. I cannot think of any immediate drawbacks.

I'm all for this. Making cross-cutting changes right now is somewhat annoying and this would dramatically simplify that. It would also clear up the naming convention for repos—right now having both liveview-client-swiftui and live_view_native_swift_ui is pretty unclear as to which is the front/back end.

I know GitHub sets up 301 redirects for renamed repos but I wonder if we can get a redirect setup for the live_view_native_siwft_ui repo to this one.

I may open this as a separate issue to discuss but I was thinking that for the eventual addons that can be written there will probably be same addon for swiftui, jetpack, winui3, etc... and it would be best to have a single repo that contains each client's version of the addon. Unlike the client itself which just should have the native code and the elixir code. What I would suggest as a project structure:

addon-name

client-name

client package information

elixir

elixir package information

This would be better than separate platform specific client addons because likely functionality ideation can be consolidated in the same repo. Bugs could exist all clients. Client specific bugs shouldn't be overwhelming.

In addition to this conversation I think changing the name of this repo to create a convention of library names. I propose: liveview-native-swiftui. Then any libraries/addons that target a specific framework: liveview-native-swiftui-<name>. And if there is a cross framework library that encapsulates common behavior: liveview-native-<name> inside that repo the framework specific directory structure should exist as noted above


stop due to errors issues!!

your idea is good, and the script as well. but I think this idea is very bad. because I have an API request, but this function just stops the process and makes *****.todo files. which is weird to use this script again and again. could you make the new function to force the request to complete the file scan?

any update boss?

Hey @blackcodersec . Sorry, I seemed to miss this one. The errors that occur can be related to the KNOXSS API, and carrying on processing could potentially be a waste of time and better to run again later.
Can you run with -v next time, and if there are specific errors that have caused it to stop, then let me know what they were? If there are errors that turn out to be target specifc rather that the API then I'll make sure they don't cause it to stop

If 6-10 errors are found in the output knoxnl auto stops the process and creates a new file which is filename..todo.
If I run .todo file for scanning again, I see the same thing happen again. and creating a new file filename..todo.**.todo. It is too big a name file, there is no option where I can set the name value for *****.todo file.
But I want here that if the requests get the error while scanning, the scan will be full.
I hope you understand, if not, feel free to comment.

Hey @blackcodersec . Thanks for raising an issue. The problem with the filename getting bigger has been fixed in the latest version I released yesterday.
If I do any code changes, then I will update the version for 2 reasons: People won't know there is a later version if I keep it the same, and the code change would have been done for a reason, AND in order to upload any change to PyPi (so can intall with pip), it has to be a unique version number.
Thanks

hey @xnl-h4ck3r,
Ok,
But I want here that if the requests get the error while scanning, the scan will be full.
Is it possible boss?

Sorry, I don't fully understand what you are asking. Do you mean that even if there are errors with the API, that you want it to continue even though they're likely to fail?

Yes, there is no API error, sometimes some subdomain blocks knoxss IP, so it shows some error, but if knoxnl finds more than 6-10 times error, knoxnl stops auto scan. which is bad (I think)
Because some subdomains won't accept Knoxss IP but other links will be accepted. but knoxnl did not check that urls. knoxnl makes a file which is ****.todo

It shouldn't stop on those errors. In your example screenshot it stopped because it was failing to connect to KNOXSS itself rather than issues with the targets through the API.
Can you send me a screenshot of a new run where it stops because of a target blocking KNXOSS or something to do with the target? I'm not sure how to replicate the issue

Check the image. knoxss IP blocking issue here,

Ho @blackcodersec . Again the last errors that caused it to stop were the API timing out and then being unable to establick a connection to the API. If we can't contact the API, everything would fail if we carry on,
I'm unsure why there are issues connecting to the API at that time

I'll look into this more to try anf figure out the issue

I think it would be good. another thing is, I think knoxss server config is not good. most of the time url not scanned fully.

I am asking to Knoxss, and he told me, now Knoxss has to handle a lot of requests, so sometimes there are problems with requests.

I'm thinking of making a change that will pause for 30 seconds if one of these API issues happen, and then try again. Maybe have an argument for the amount of retries and seocnds to wait, and default to 3 and 30 seconds respectively. What do you think?

That's why, I think it would be good.

How to avoid this type of error? I think if you implement retries scan, when a URL will not be scanned or error will occur. It would be great update.

Hi @blackcodersec, I think is is related with an issue with the KNOXSS API itself. It happens when there is a runtime error of failed to establish a new connection when trying to call the API. It can occur if you are running low on memory (which has happened for some people on limited VPS running lots of other things), but it is most likely an issue with the KNOXSS API. So bascially, there is nothing we are able to do with that. There are changes coming soon that will wait for a while and do a number of retries if errors like this happen.

@xnl-h4ck3r
 _           _ ___    __      _
| | ___ __   V_V\ \  / /_ __ | |
| |/ / '_ \ / _ \\ \/ /| '_ \| |
|   <| | | | (_) / /\ \| | | | |
|_|\_\_| |_|\___/_/  \_\_| |_|_|
                 by @Xnl-h4ck3r

Current knoxnl version 4.0 (latest)

NOTE: Overriding "API_KEY" from config.yml with passed API Key xxxx-aa8d-xxxx-8a3c-xxxx

Calling KNOXSS API for 6852 targets...

[ SAFE ] - (GET)  https://stage-gr-en-origin.test.test.com/ [51/5000]
[ SAFE ] - (GET)  https://bcassets.test.com/FUZZ [52/5000]
[ ERR! ] - (GET)  https://storeship-dev.test.com/FUZZ  KNOXSS ERR: Target is blocking KNOXSS IP [52/5000]
[ SAFE ] - (GET)  https://daq.test.com.tw/ [53/5000]
The KNOXSS service is currently unavailable. Please try again later.
[ ERR! ] - (GET)  https://np-msapi.test.com/FUZZ  KNOXSS ERR:  [53/5000]
[ ERR! ] - (GET)  https://www.load-mid-management.test.com/#/.  KNOXSS ERR:  [53/5000]

API calls made so far today - 53/5000

Had to stop due to errors. All unchecked URLs have been written to /home/nishant57/BB/test.com/xsstest/urls.txt.20240415_145750.todo

The following domains seem to be blocking KNOXSS and might be worth excluding for now: storeship-dev.test.com
No successful XSS found... better luck next time! 🤘

Hi @Nishantbhagat57. It stopped because there was an issue with the KNOXSS API. Unfortunatley there is much I can do if the API is having issues. I am working on a change to wait for a while when the API is having problems to try again a few times before stopping.


Feature Request: Use Promptfoo to generate DPO datasets

I use promptfoo a lot. It was the missing piece of a proper development stack for LLM-based applications.
As part of creating extensive evals, you get to compare a lot of different models with ease. That helps a lot with selecting the right model for a given task.
However, there will always be a goal to replace more expensive models with fine-tuned open-source alternatives.
Wouldn't it be great to take the existing data generated by running promptfoo to automatically create DPO datasets?
This could be as simple as using the UI to thumbs up one of the model responses per prompt.
Then all the ingredients should be pretty much there. The input system message/prompt, as well as a response pair with one response being marked as preferred.
Does that make sense?

Hey @streichsbaer,
#482 starts the work on this.  A couple areas where I'm seeking feedback

I've made chosen and rejected string arrays rather than strings, because some users have multiple columns.  Does that make sense to you, or does it make ingesting this data more cumbersome?
I am assuming that system and question are test case vars.  Does that match workflow?  I'm wondering if there is a better way to do this more generically.  I could just add the vars map to the object.

Hi @typpo, thanks for that, and sorry for the late response.

Strings should be fine for chosen and rejected, but having string arrays is ok too. The post-processing of this is not an issue.
Correct, the system and question are the test case vars. Adding the vars map to the object is a good idea, then there is more flexibility in the post-processing steps.

This feature is released in 0.50.0.  Thanks and let me know if you have any more feedback!

Awesome, thanks @typpo 🙏


Virtual private database with mutitenanacy

Have any option to achieve secure multi tenancy access with postgrest ?, Have any virtual private data base concept?

You can create different users with different access to tables within a single database. You can also run two copies of postgres configured to run on entirely different databases on a single postgresql server. Can you tell me more about your specific use case?

Did my comment help or do you have more questions?

@begriffs
Let me to explain my usecase.
I have 4 clients (tenants) , A, B, C, D
I have kept all clients data in the same database, means same table and using clientId/ tenant Id to distinguish records.
If I have provided postgrest to access data for each client , how can I ensure  Tenant A will access only A's data, Never ever know/access B's Data. any option in postgrest to achieve it easily.

If you have a look at issue #123 I talk about what I think you are asking about.
There is the current_user inside postgres views and triggers that you can use but it cannot be done based on the user logged in via postgrest, but rather the role that is assigned to the user.
See also the wiki here for info on to setup security and permissions: https://github.com/begriffs/postgrest/wiki/Security-and-Permissions#scenario-signed-in-authors-can-edit-own-content
Does this help answer the question?

Thanks @pvdvreede  , Just tried and understood it is possible. and hopes postgres 9.5 release will make more easier.

PostgreSQL 9.5 beta has been released!
New documentation now lives at postgrest.com and we'll be adding a section about your use case.


Apply Hall sensor

Check if the arm doesn't apply too much pressure on the robot, to prevent our mechanism to break it.

Functionality was fine last sprint, but it still has to be attached and we don't have the model that can support the weight of the platform.
This sprint we have to improve the existing design to make a more refined version of the arm.

This sprint we have a more stable arm, with better materials and overall a better build. We added extra support for the top part of the mechanism, so the platform would stay secure and fixed to the mechanism, without it bending the mechanism to the heavier side.
This would've been a non-issue if the platform only had to hold the hallsensors and not the pressure block as well.

Issue has been moved to issue "Project".
All equivalent issues will be moved there too.


Add playwright with nextjs project and github workflow

Adds first playwirght scenarios with github workflow
Addresses #76

Great work 🐐


Request failed to decode: truncated

MacOS 10.14.5
XCode 10.2.1
swift --version: Apple Swift version 5.0.1
protoc --version: libprotoc 3.7.1
git log -1:
commit 7bf52ab1f5ee87aeb89f2a6b9bfc6369408476f7 (HEAD, tag: 1.5.0)
Author: Thomas Van Lenten<EMAIL_ADDRESS>Date:   Mon Apr 15 10:54:40 2019 -0400
Update the docs on min Swift version required.

Hi all,
when I exec
/bin/sh -c protoc\ \/Developer/Proto/test.proto\ --swift_opt=Visibility=Public\ --swift_out=\/Developer/Proto\ --proto_path=\/Developer/Proto
I get this error
protoc-gen-swift: Request failed to decode: truncated --swift_out: protoc-gen-swift: Plugin failed with status code 1.
after several times I retry to exec it again the error disappear, but (apparently randomly) it appears again sometimes.
Can you help me pls? ty

update:
if i use this proto:
`syntax = "proto3";
message Contact {
enum ContactType {
SPEAKER = 0;
ATTENDANT = 1;
VOLUNTEER = 2;
}
string first_name = 1;
};`
i get no errors
if i use this
`syntax = "proto3";
message Contact {
enum ContactType {
SPEAKER = 0;
ATTENDANT = 1;
VOLUNTEER = 2;
}
string first_name = 1;
string last_name = 2;
};`
i get the error
protoc-gen-swift: Request failed to decode: truncated --swift_out: protoc-gen-swift: Plugin failed with status code 1.
can you help me plis? ty

I'm not able to repo the issue, but I am using a newer version of protobuf.
$ ../protobuf/src/protoc --version
libprotoc 3.8.0
$ cat a.proto
syntax = "proto3";
message Contact {
enum ContactType {
SPEAKER = 0;
ATTENDANT = 1;
VOLUNTEER = 2;
}
string first_name = 1;
};
$ cat b.proto
syntax = "proto3";
message Contact {
enum ContactType {
SPEAKER = 0;
ATTENDANT = 1;
VOLUNTEER = 2;
}
string first_name = 1;
string last_name = 2;
};
$ ../protobuf/src/protoc --swift_out=$HOME/Desktop/ --swift_opt=Visibility=Public a.proto
$ ../protobuf/src/protoc --swift_out=$HOME/Desktop/ --swift_opt=Visibility=Public b.proto
$ cat ~/Desktop/a.pb.swift
// DO NOT EDIT.
//
// Generated by the Swift generator plugin for the protocol buffer compiler.
// Source: a.proto
//
// For information on using the generated types, please see the documenation:
//   https://github.com/apple/swift-protobuf/

import Foundation
import SwiftProtobuf

// If the compiler emits an error on this type, it is because this file
// was generated by a version of the `protoc` Swift plug-in that is
// incompatible with the version of SwiftProtobuf to which you are linking.
// Please ensure that your are building against the same version of the API
// that was used to generate this file.
fileprivate struct _GeneratedWithProtocGenSwiftVersion: SwiftProtobuf.ProtobufAPIVersionCheck {
  struct _2: SwiftProtobuf.ProtobufAPIVersion_2 {}
  typealias Version = _2
}

public struct Contact {
  // SwiftProtobuf.Message conformance is added in an extension below. See the
  // `Message` and `Message+*Additions` files in the SwiftProtobuf library for
  // methods supported on all messages.

  public var firstName: String = String()

  public var unknownFields = SwiftProtobuf.UnknownStorage()

  public enum ContactType: SwiftProtobuf.Enum {
    public typealias RawValue = Int
    case speaker // = 0
    case attendant // = 1
    case volunteer // = 2
    case UNRECOGNIZED(Int)

    public init() {
      self = .speaker
    }

    public init?(rawValue: Int) {
      switch rawValue {
      case 0: self = .speaker
      case 1: self = .attendant
      case 2: self = .volunteer
      default: self = .UNRECOGNIZED(rawValue)
      }
    }

    public var rawValue: Int {
      switch self {
      case .speaker: return 0
      case .attendant: return 1
      case .volunteer: return 2
      case .UNRECOGNIZED(let i): return i
      }
    }

  }

  public init() {}
}

#if swift(>=4.2)

extension Contact.ContactType: CaseIterable {
  // The compiler won't synthesize support with the UNRECOGNIZED case.
  public static var allCases: [Contact.ContactType] = [
    .speaker,
    .attendant,
    .volunteer,
  ]
}

#endif  // swift(>=4.2)

// MARK: - Code below here is support for the SwiftProtobuf runtime.

extension Contact: SwiftProtobuf.Message, SwiftProtobuf._MessageImplementationBase, SwiftProtobuf._ProtoNameProviding {
  public static let protoMessageName: String = "Contact"
  public static let _protobuf_nameMap: SwiftProtobuf._NameMap = [
    1: .standard(proto: "first_name"),
  ]

  public mutating func decodeMessage<D: SwiftProtobuf.Decoder>(decoder: inout D) throws {
    while let fieldNumber = try decoder.nextFieldNumber() {
      switch fieldNumber {
      case 1: try decoder.decodeSingularStringField(value: &self.firstName)
      default: break
      }
    }
  }

  public func traverse<V: SwiftProtobuf.Visitor>(visitor: inout V) throws {
    if !self.firstName.isEmpty {
      try visitor.visitSingularStringField(value: self.firstName, fieldNumber: 1)
    }
    try unknownFields.traverse(visitor: &visitor)
  }

  public static func ==(lhs: Contact, rhs: Contact) -> Bool {
    if lhs.firstName != rhs.firstName {return false}
    if lhs.unknownFields != rhs.unknownFields {return false}
    return true
  }
}

extension Contact.ContactType: SwiftProtobuf._ProtoNameProviding {
  public static let _protobuf_nameMap: SwiftProtobuf._NameMap = [
    0: .same(proto: "SPEAKER"),
    1: .same(proto: "ATTENDANT"),
    2: .same(proto: "VOLUNTEER"),
  ]
}
$ cat ~/Desktop/b.pb.swift
// DO NOT EDIT.
//
// Generated by the Swift generator plugin for the protocol buffer compiler.
// Source: b.proto
//
// For information on using the generated types, please see the documenation:
//   https://github.com/apple/swift-protobuf/

import Foundation
import SwiftProtobuf

// If the compiler emits an error on this type, it is because this file
// was generated by a version of the `protoc` Swift plug-in that is
// incompatible with the version of SwiftProtobuf to which you are linking.
// Please ensure that your are building against the same version of the API
// that was used to generate this file.
fileprivate struct _GeneratedWithProtocGenSwiftVersion: SwiftProtobuf.ProtobufAPIVersionCheck {
  struct _2: SwiftProtobuf.ProtobufAPIVersion_2 {}
  typealias Version = _2
}

public struct Contact {
  // SwiftProtobuf.Message conformance is added in an extension below. See the
  // `Message` and `Message+*Additions` files in the SwiftProtobuf library for
  // methods supported on all messages.

  public var firstName: String = String()

  public var lastName: String = String()

  public var unknownFields = SwiftProtobuf.UnknownStorage()

  public enum ContactType: SwiftProtobuf.Enum {
    public typealias RawValue = Int
    case speaker // = 0
    case attendant // = 1
    case volunteer // = 2
    case UNRECOGNIZED(Int)

    public init() {
      self = .speaker
    }

    public init?(rawValue: Int) {
      switch rawValue {
      case 0: self = .speaker
      case 1: self = .attendant
      case 2: self = .volunteer
      default: self = .UNRECOGNIZED(rawValue)
      }
    }

    public var rawValue: Int {
      switch self {
      case .speaker: return 0
      case .attendant: return 1
      case .volunteer: return 2
      case .UNRECOGNIZED(let i): return i
      }
    }

  }

  public init() {}
}

#if swift(>=4.2)

extension Contact.ContactType: CaseIterable {
  // The compiler won't synthesize support with the UNRECOGNIZED case.
  public static var allCases: [Contact.ContactType] = [
    .speaker,
    .attendant,
    .volunteer,
  ]
}

#endif  // swift(>=4.2)

// MARK: - Code below here is support for the SwiftProtobuf runtime.

extension Contact: SwiftProtobuf.Message, SwiftProtobuf._MessageImplementationBase, SwiftProtobuf._ProtoNameProviding {
  public static let protoMessageName: String = "Contact"
  public static let _protobuf_nameMap: SwiftProtobuf._NameMap = [
    1: .standard(proto: "first_name"),
    2: .standard(proto: "last_name"),
  ]

  public mutating func decodeMessage<D: SwiftProtobuf.Decoder>(decoder: inout D) throws {
    while let fieldNumber = try decoder.nextFieldNumber() {
      switch fieldNumber {
      case 1: try decoder.decodeSingularStringField(value: &self.firstName)
      case 2: try decoder.decodeSingularStringField(value: &self.lastName)
      default: break
      }
    }
  }

  public func traverse<V: SwiftProtobuf.Visitor>(visitor: inout V) throws {
    if !self.firstName.isEmpty {
      try visitor.visitSingularStringField(value: self.firstName, fieldNumber: 1)
    }
    if !self.lastName.isEmpty {
      try visitor.visitSingularStringField(value: self.lastName, fieldNumber: 2)
    }
    try unknownFields.traverse(visitor: &visitor)
  }

  public static func ==(lhs: Contact, rhs: Contact) -> Bool {
    if lhs.firstName != rhs.firstName {return false}
    if lhs.lastName != rhs.lastName {return false}
    if lhs.unknownFields != rhs.unknownFields {return false}
    return true
  }
}

extension Contact.ContactType: SwiftProtobuf._ProtoNameProviding {
  public static let _protobuf_nameMap: SwiftProtobuf._NameMap = [
    0: .same(proto: "SPEAKER"),
    1: .same(proto: "ATTENDANT"),
    2: .same(proto: "VOLUNTEER"),
  ]
}

When you use the --swift_out option, the protoc program parses your proto files and sends the parsed result to the protoc-gen-swift program which is then responsible for producing Swift source code.  This error means that the protoc-gen-swift program is getting a corrupted version of your proto.  Unfortunately, it's not clear whether the problem is with protoc or protoc-gen-swift or the communication between them.
First, can you please try upgrading protoc to the newest version (I believe 3.8.0 is the current version) and see if that makes a difference?

If you set the shell environment variable PROTOC_GEN_SWIFT_LOG_REQUEST to a filename, then protoc-gen-swift will write a copy of the data it receives from protoc into the named file.  That would let us verify that when you see this message, the data really is corrupted.

ty for the fast reply.
protoc --version
libprotoc 3.8.0

no differences, same error
protoc-gen-swift: Request failed to decode: truncated
--swift_out: protoc-gen-swift: Plugin failed with status code 1.

i tried to add PROTOC_GEN_SWIFT_LOG_REQUEST variable
my .proto was:
syntax = "proto3";
message Contact {
enum ContactType {
SPEAKER = 0;
ATTENDANT = 1;
VOLUNTEER = 2;
}
string first_name = 1;
string last_name = 2;
};

in the PROTOC_GEN_SWIFT_LOG_REQUEST i got this
hr/hut/person.protoVisibility=Public�"�z�
hr/hut/person.proto"
Contact

first_name (	R	firstName
	last_name (	RlastName"8
ContactType
SPEAKER�
	ATTENDANT
	VOLUNTEERJ�

any suggestion? ty

The failing one does fail to parse with protoc's --decode or --decode_raw support.  The fact that it is 512 bytes is also really odd, it is missing the end of the payload.  Doing a quick look at the protoc code for talking to a plugin, I don't see anything obvious there (the src/google/protobuf/compiler submodule code is where the writing happens).  On the Swift side, we do use FileHandle.standardInput.readDataToEndOfFile(), and I wonder if there is some odd rase where only one buffer of data was written and we read it and Foundation decides that was the "end" of the file even though protoc was about to write more.
@bazdav can you try using SwiftProtobuf 1.4.0's plugin instead?  Does that reproduce the failure?  If you can't, then it would appear to be the change in how we were reading from stdin.

Solved.
I've reinstalled swift-protobuf version 1.5.0
ty all for the helping.


feature/nccl only (delete MPI)

I don't think we can avoid the file system alltogether, as without MPI, this is the only "communication layer" that we actually have available before we initialize NCCL.
we should be much more careful about this file, though, e.g., if such a file remains left-over from a previous run, I think we just get race conditions in our file-system now.

Copy pasting some Discord discussion. Adjustment to this PR
maybe one way we could do it is we

remove MPI for all actual compute
keep MPI as optional, use it for initializing NCCL
in case you hate MPI or can't get it to work, fall back on the janky file system idea
so in this world we keep the convenience of MPI and use it to init NCCL. and we don't delete that code, but we'd move it to its own mpi.h
if you don't have MPI we fall back to init NCCL through shared file system
certainly i think during the actual model run it feels very janky to use both MPI + NCCL for bits and pieces together.


AstarGrid2D (get_cell_tile_data) does not detect "custom data layer" in Tilset

Hi,
thanks a lot for this really powerfull addon.
i meet an issue. i coded a AI movement for NPC via AstarGrid2D algo.
All works fine with a tilemap made in Godot 4.But it does not work with a tilemap made in Tiled then imorted via YATI.
Node is found but i think get_cell_tile_data function does not find  custom data layer "walkable" (Tileset property)
Any idea plz?

my fault, it work !


Update bower.json to allow patch and minor updates

Bower.json should have its dependencies' versions marked with a ^ instead of a ~, which would allow both patches and minor updates to be available instead of just patches. Currently, this leads to several conflicts on projects using more recent polymer elements.

Polymer does not follow semver when updating elements. For that reason I am using ~. If you have specific dep issues, let me know which ones and we can update the version in bower.json.


Generate a new btc address when the previous has been used

Currently, BBW reuses onchain addresses. We should implement a change so that once address has been used, a new address is created for receiving another onchain payment.

Fixed https://github.com/GaloyMoney/galoy/pull/2340


Update guidance on recency

So far, it seems that typical recency numbers at steady-state are in the high 50s, not "around 50%." I might update the conditional formatting to change color informatively and update the README to reflect this operational knowledge.

Conditional formatting updated around the following intervals, reflecting high-50s being a standard good place to be:
GREEN - 0.55 - YELLOW - 0.5 - RED


Accessibility Audit

WCAG AA level Accessibility compliance
https://wagtail.org/accessibility/

Accessibility checker: https://www.siteimprove.com/glossary/wcag-compliance-checker/
Accessibility checker: https://www.accessibilitychecker.org/

Reach out to Wagtail's Accessibility team + Thibaud

Note:

Some ALT missing
Skip to content button missing


Optional authentication by access token

Authentication is enabled with the new rascsi -P option, which expects the full path of a token file. The first line of the token file is the token string. The token file must be owned by root and must be readable by root only.
When started with the new -P option rascsl prompts the user for a password.
>rasctl -l
Error: Authentication failed
>rasctl -l -P
Password:
No images currently attached.

The VERSION_INFO operation is the only operation that does not require authentication, because a client may need the version number in order to make decisions on how to proceed. @rdmark I'm not really sure whether VERSION_INFO should be covered by authentication or not and would like to hear your thoughts on this.
In order to be able to handle authentication errors specifically without parsing an error message string (error message string contents are undefined and may change any time) the PbErrorCode enum was introduced, see .proto file.
All changes are backwards compatible.

@uweseimet I don't have a concern with leaving the VERSION_INFO unprotected. It simply returns the three components of the version string, which I don't see how it can aid much an a malicious attack.

@rdmark I agree, but I reverted my decision to unprotect it for consistency reasons, and because there was not really an advantage of not protecting it.
Disclosing version informnation actually is a security risk. Not necessarily for RaSCSI but in general. It helps an attacker to decide on the kind of attack, and if there ever were vulnerable versions of a software, based on the version the attacker would immediately know which attack would work.


Update install_requirements.sh to pt/pt dev20241217

Looks like the nightly is missing on pytorch/pytorch for 1217 https://github.com/pytorch/pytorch/issues/143434

Working with tune folk to debug failure:

Import succeeds on pt1213, but fails on 1218
Failure shows up on tune=1126 and 1218


Write Tests for API Examples of snack_bar.0, elevated_button.0, stepper.0, radio.0, filled_button.0, outlined_button.0 & card.0

Write Tests for API Examples of snack_bar.0, elevated_button.0, stepper.0, radio.0, filled_button.0, outlined_button.0 & card.0
Part of #130459
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Not sure why it's failing... seems flakey


Fix blocker_id to friendable's id

When friendship is blocked by user, the blocker_id  of each friendship is assigned by user’s id and friend’s id. And two complementary friendships have different blocker_id.
The blocker_ids should be assigned to the actor.

Coverage increased (+0.0005%) to 99.787% when pulling 3f98d494570020cf02408d00f78b2ca6f717bdfc on skswhwo:master into 2718e53be4f770dbb0465a135072f13d2ce70f49 on sungwoncho:master.

Thanks, you have a fair point.
I am wondering two things. Please correct me if any of these concerns are invalid, because I have not used this gem personally in a while.

Will this change be backward compatible? I think the current users of this gem might break their app with this change. We might need to write a migration with an appropriate upgrade instruction (see here).

Is there a point in creating two friendship records in this case?


Unable to append a type to an existing tuple

TypeScript Version:  3.2.4

Search Terms:
Tuple, merge, combine
Code
function combine<T, U extends any[]>(item: T, items: U): [T, ...U] {
    return [] as any;
}
const result = combine("hello", ["goodbye", 123, true]);

Expected behavior:
result should be typed as [string, string, number, boolean].
Actual behavior:
Compile error:
A rest element type must be an array type.
Playground Link:
Link
Related Issues:

Your playground link links to an empty Playground.

You attempt spreading the type,, that does not work.
This works.

sorry about that, link in original post fixed.

Duplicates #5453 and fixed in TS3.0 by #24897 via tuples in rest/spread positions:
type Cons<H, T extends any[]> = ((h: H, ...t: T) => void) extends ((
  ...r: infer R
) => void)
  ? R
  : never;

function combine<T, U extends any[] | [any]>(item: T, items: U): Cons<T, U> {
  const ret = items.slice() as Cons<T, U>;
  ret.unshift(item);
  return ret;
}
const result = combine("hello", ["goodbye", 123, true]);
// const result: [string, string, number, boolean]

That's an ...interesting way of fixing this!
Updated link
This is a hack though right? It's a very roundabout way of fixing the issue IMHO.
Very appreciative of the solution though :-)

It's a hack in that it's roundabout, but that's probably a separate issue #26113.  But this definition of Cons uses all supported and documented language features, so it's not a hack in the sense that "it just happens to work".


No Request, just Info

I'm missing some devices in the description / tested devices and I just wanted to confirm they are are working with V 4.x and V 5.x:
Fritz!Box 6591 Cable
Fritz!Repeater 3000
Good job 👍

@Holydevil66
Thanks :)


Package import issues?

Dear author:
where is 'setup_default_logging()'
train.py

Thank you for your interest in this work.
that function gets imported using this line. It is defined in timm library mainly.


Module 4 Assignment

The post can be browsed at https://education.github.community/t/module-4-exercise-1-student-programs/26002/389?u=pattacini.

This is a fantastic writeup! Thanks for sharing!

Thanks @ericdrosado!
Looking forward to the Campus Advisor interview!


Instruction in ReadMe on how to compile the documentation is not working

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Check that you are using the latest version of kaobook.
Check that your issue isn't already filed: https://github.com/fmarotta/kaobook/issues

Description
Compiling the documentation as described in the ReadMe does not work.
Minimal Working Example
From the ReadMe:

cd into the root of the repository, and run
pdflatex -output-directory examples/documentation main # The .tex is optional
biber -output-directory examples/documentation main
pdflatex -output-directory examples/documentation main
pdflatex -output-directory examples/documentation main
pdflatex -output-directory examples/documentation main

This fails because there is no main.tex in the root of the repo:
$ pdflatex -output-directory examples/documentation main
This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020) (preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
! I can't find file `main'.
<*> main

(Press Enter to retry, or Control-D to exit)
Please type another input file name:

If I cd examples/documentation/ and run pdflatex there I get
$ pdflatex main
This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020) (preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(./main.tex
LaTeX2e <2020-10-01> patch level 4
L3 programming layer <2021-02-18>

! LaTeX Error: File `kaobook.cls' not found.

Type X to quit or <RETURN> to proceed,
or enter new name. (Default extension: cls)

Copying the main.tex file to the root does not work either because then paths to the packages
\usepackage{kaobiblio}
\usepackage{mdftheorems}
\usepackage{plaintheorems}

and to the files
\input{chapters/options.tex}
\input{chapters/textnotes.tex}
\input{chapters/figsntabs.tex}
\input{chapters/references.tex}

are wrong.
Expected behavior:
It would be great if there were only one command necessary to compile the documentation (including the glossary and nomenclature). Maybe this can be done with latexmk or make.
Actual behavior:
Described above.

Weird, the commands work on my machine. But I agree that having to run just one command would be better. I'll try to set up latexmk

Okay, I just figured out what is going on:
For me, the .tex extension was not optional.
So
pdflatex -output-directory examples/documentation main.tex

starts the compilation, but after some time fails with
! LaTeX Error: File `kaobiblio.sty' not found.

Type X to quit or <RETURN> to proceed,
or enter new name. (Default extension: sty)

Enter file name:

Then I installed kaobook as described in these instructions. Now kaobiblio.sty is found and for some reason the .tex extension is also optional.
As you probably have kaobook installed like this, it explains why it worked for you.
So the problem is fixed for me, but I guess most users will not have kaobook installed like this.

Thanks for the report. Having the packages inside a separate styles directory made the code slightly more organised, but loading the packages with something like \usepackage{styles/kaobiblio} made it very difficult to pass custom options to these packages. So I started loading them like \usepackage{kaobiblio} in all the examples, which resulted in the present issue. Moreover, I discovered that my edit also caused errors on Overleaf.
I think that the best option is to move the packages to the root of the repository, so that they can be called with \usepackage{kaobiblio} and everything, including the custom options and the compilation method proposed in the README (except possibly for the optional extension), should work again. I have now implemented this strategy: the two packages mdftheorems.sty and plaintheorems.sty were merged into a single package kaotheorems.sty (the framed option can be passed to this package to activate the behaviour of mdftheorems.sty, as mentioned in the updated documentation), while the other two packages, environments.sty and packages.sty, have been merged into the kao.sty package.

I was referring to this commit: d411f681b167e91daf4e4d15cfb7089871f6c1e1

Impressive reorganization! Thank you!
I just tested it and it works for me. Closing this issue.


Appium - Android Hybrid - unable to switch context to WebView using Selenium VB wrapper

Hello Florentbr:
This is my first communication with you and take this opportunity to Thank You for this wonderful tool.
I am currently using version <IP_ADDRESS>.
I used it for automating websites and also Android mobile apps using Appium.
Currently, i face a problem automating the WEBVIEW of an Android Hybrid App.
Appium tells me to switch context to the webview eg in other languages: driver.switch_to.context('WEBVIEW'). However - using the VB wrapper i dont know which method to use to perform this context switch. I have tried driver.SwitchToWindowByName etc... without results.
Please help.
thanks,
Bipo

Appium tells me to switch context to the webview eg in other languages: driver.switch_to.context('WEBVIEW'). However - using the VB wrapper i dont know which method to use to perform this context switch. I have tried driver.SwitchToWindowByName etc... without results.

The context command is specific to appium and not defined in the Selenium API:
https://github.com/appium/appium/blob/88e67ce987d78ce44de252219e07dc176a3511c2/docs/en/advanced-concepts/hybrid.md
http://www.w3.org/TR/webdriver/
You could try the "autoWebview" capabilty:
driver.SetCapability "autoWebview", True

I'll see to add a generic method to send a command in the next release. It should look like this:
driver.Send "POST", "/context", "name", "WEBVIEW"

@florentbr
Thank you for the insight. For now will use the hard http post to achieve the switch.
Really looking forward to the generic method. From the sample command you have shown, it is also probably going to support all verbs and will return the response.
Many thanks again,
Bip

The ability to send a customized command was added in release v<IP_ADDRESS>
Example:
driver.Send "POST", "/context", "name", "WEBVIEW"

Thank You once again @florentbr. It has been very helpful as usual.
Slipping in a question on the same to ask if i could use the same for making soap requests. If yes, can you provide an sample example how it should be like?


Continuously building other docker images inside a Jenkins that is itself running in a container

Is building other docker images inside a Jenkins that is itself running in a container advisable?
Or should I use a bear metal slave for that?
What is the best practice here?

Please ask questions in Jenkins mailing list https://github.com/jenkinsci/docker/blob/master/CONTRIBUTING.md


Add website to project

This task should be quick to complete by a project maintainer in under a minute.
With the web UI, modify the project "About" settings to add a website to https://spatialreference.org
This allows anyone looing at this GH Project to easily navigate to the rendered website.

done


I have added a website made by me. It's also available on http://bbksamiti.ezyro.com

Pull Request Template

Please provide all of the details below. Pull requests missing any of the information below will be closed!
Providing the issue number/url helps us identify the problem being solved and keep the issues tab clean and tidy

This is not a fix. This is a request to add login and signup pages to the site.
Summarize what this PR fixes:-
Fixes #
Checklist
(Add an x between the brackets to check the items)

[ ] I have summarize what this PR fixes above
[ ] I have provided the issue ID/URL above
[ ] I have not added Bootstrap or jQuery and used correct styling guide.
[ ] This PR fixes only the issue mentioned above (create separate PRs for separate issues)
[ ] I was the first one to claim the issue or I created the issue - I created the issue

This is not a current issue for this site. Anything added needs to first be an approved issue.


fix: make schema singleton

The get schema() function of the api classes creates an object all the time, causing high memory usage.
This PR applies singleton pattern for this function.

[x] generate all services
[x] changelog update after release

I hope that solves most of the issues, did you check that the types work well for navigation properties?

Yes, for example, you can build filters like below with autocompletion:
commonEntityApi.schema.TO_SINGLE_LINK.filter()

I hope that solves most of the issues

I'll test it with canary version after merging.


Use latest stable version of metadata.

The latest version of metadata lib is used, migration is provided
Fixes #298

Overwrites the https://github.com/OpenConext/OpenConext-engineblock-metadata version introduced in #301 with the released version containing the same code, see https://github.com/OpenConext/OpenConext-engineblock-metadata/releases/tag/2.0

@quartje @thijskh, this should resolve #298 and has a migration for the new metadata table.

:+1:


Replace suppress from discovery with staff suppress

Replace suppress from discovery added by mistake

plz put ticket number in PR name


Define "small improvement" in Contributor's Guide

We need to update https://docs.mattermost.com/developer/contribution-guide.html with definition and examples of "small improvement".
Criteria:

Consensus improvement is small--i.e. 100% of core committers reviewing PR agree
Does not require an update to docs.mattermost.com
Not more than a few lines of changes

Examples (need to link to PR examples, we can probably fine better examples than these):

Adjustments to better align with UX guidelines
Tidying up small bits of code
Small improvements to make help text more clear

Examples
some one just update a file and forgot to update the same method within a function of that file:
https://github.com/mattermost/platform/pull/5878

Would the term "incremental improvement" in place of "small improvement" be more or less self-explanatory here?

I agree with @JeffSchering on using the term "incremental improvement".

See #1083 for proposed changes

@JeffSchering when I read "incremental" the first thing that comes to mind is something that will be on-going whereas "small" comes in as something of minor, in a fixed size. I do think that incremental would fit more in the "technical writing" jargon but as a person that often misunderstand technical writing, I would say "small" is much more friendly, or perhaps "minor improvement". Then again that is just my personal opinion, and perhaps I am the minority that sees it that way, or rather read it that way.

Thanks @prixone for the feedback, really appreciate your input here.
I added a comment in my PR, which had a related note, feel free to add any feedback? https://github.com/mattermost/docs/pull/1083#discussion_r111788163


add eth.pp.ua

add support for stratum eth.pp.ua
valid send hashrate

I don't see any stratum related additions in this pull-request. This project is not here for pumping someone's business with false marketing.
If you need to modify eth_submitHashrate call and force proxy to push actual hashrate estimated from shares instead of proxying data from ethminer you have to propose these changes with commit message like "Submit mining hashrate to upstream from internal proxy stats".
Also, I don't see GenerateClientId function is used anywhere:
https://github.com/General-Beck/ether-proxy/commit/615501eca905bfa5e338055271026e70d61075eb#diff-99f38c7c07bfcc03a528180716bafab5R34
And also commented out debug lines must be removed https://github.com/General-Beck/ether-proxy/commit/615501eca905bfa5e338055271026e70d61075eb#diff-3ac192716a1df66bbd1008d327af8792R211


Initial PGM charter draft

Hey @Valdorff even if we disagree on the implications (maybe especially because there is disagreement), I recommend putting a section on Security Considerations in here.

The onchain pDAO stuff coming in Houston supersede this.


ASK - Console.log the result

So, i tried this library and here's the codes:
var voucher_codes = require('voucher-code-generator');

voucher_codes.generate({
    length: 8,
    count: 5
});

I want to console.log the result from the function. How can I do that?

Ahh, finally I solved the issue just add few codes from the sample in test folder.
var voucher_codes = require('voucher-code-generator');

var basicCodes = voucher_codes.generate({
    length: 6,
    count: 5
});
console.log(basicCodes)

I close this issue now. Thanks

No problem @yogieputra8! Happy coding ;)


IntervalVarContainer within SearchMonitor

Hello,
Following the break exemple for the routing library :
https://github.com/google/or-tools/blob/39f44709bba203f5ff3bc18fab8098739f189a6d/examples/cpp/cvrptw_with_breaks.cc#L209
I now try to monitor those values for intermediates solution using a SearchMonitor or a SearchLimit.
It seems that the assignement doesn't carry those values or don't expose them.
Is it possible to monitor the IntervalVarContainer from an intermediate assignment ? And how ?
Thanks

I guess you misunderstand how local search works.
The assignment is not managed, changed during search. At a leaf, all neighborhoods are created, tested, and successful ones are propagated back to the variables.
This only happens there, and the purpose of the search monitor (and search limit), this is an atomic operation.

If I understand well, when we are within the scope of AtSolution() All constraints are propagated to the variables. So has I can access the intermediate solution even if some still have unfixed values, but a reduced set. Why couln't I access the IntervalVar ?

Why do you need the container ?
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le mar. 13 août 2019 à 08:26, Gwénaël Rault<EMAIL_ADDRESS>a
écrit :

If I understand well, when we are within the scope of AtSolution() All
constraints are propagated to the variables. So has I can access the
intermediate solution even if some still have unfixed values, but a reduced
set. Why couln't I access the IntervalVar ?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1494?email_source=notifications&email_token=ACUPL3MIZ7JEMHKT2B5TD3DQELHC3A5CNFSM4ILKHIJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4GAZUI#issuecomment-520883409,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3KY655V4FXAVXZOZ2LQELHC3ANCNFSM4ILKHIJQ
.

The use case is the following :
We are monitoring the improvement of the best solution. So every time a new best solution is found we store it. The detail is not really important but we need to know the order of the nodes and the IntervalVar Container is needed to get an estimation of where are placed the breaks in the solution.

You are at a leaf, you need to look at the IntervalVar variables, not at
the assignment container, which, IMO, will not contain anything useful.
Still, I am only vaguely familiar with that code.
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le mar. 13 août 2019 à 09:06, Gwénaël Rault<EMAIL_ADDRESS>a
écrit :

The use case is the following :
We are monitoring the improvement of the best solution. So every time a
new best solution is found we store it. The detail is not really important
but we need to know the order of the nodes and the IntervalVar Container is
needed to get an estimation of where are placed the breaks in the solution.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1494?email_source=notifications&email_token=ACUPL3LCOZBCSBO53CGQLH3QELLWRA5CNFSM4ILKHIJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4GEX5Q#issuecomment-520899574,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3M44UBTQW2QB5GHU2DQELLWRANCNFSM4ILKHIJQ
.

Ok, I was assuming that the IntervalVarContainer would avoid me to define some redundant variables. That was the point of my misunderstood. Thank you for the clarification !