deprecated commands removed?

I was using Network.getAllCookies which is deprecated but still works.
With a recent commit, it was removed:
https://github.com/chromedp/cdproto/commit/6730ecaecb799bdc23b8c9c127d5d245f8f40192#diff-96a7f5c352cd3d2d1ee3c7c55ed95e668c6edb28a4fa337e6c60270471bdab61

Yes, https://github.com/chromedp/pdlgen removes deprecated commands unless it's told not to do that (see https://github.com/chromedp/pdlgen/pull/19 for an example).
Network.getAllCookies is marked as deprecated in https://github.com/chromium/chromium/commit/f0539553369692ee993a3249ebe9bdb237322abf (Chromium version 111.0.5508.0).

@tmm1 please note that because of the pace at which the Chromium source tree moves, I made the decision years ago to track the current development branch for APIs (ie, for cdproto).
If you need to revert to an older version of cdproto, note that you can use Go modules, and do a replace() in your go.mod on your project with an older version.  I would not recommend doing this, however, as the APIs you're relying on are going to be removed shortly (ie, in a few weeks).
If you do do that, you should get a go.mod that looks like the following:
$ cat go.mod
module ctest

go 1.20

require github.com/chromedp/chromedp v0.9.1

require (
	github.com/chromedp/cdproto v0.0.0-20230220211738-2b1ec77315c9 // indirect
       # other deps ...
)

replace github.com/chromedp/cdproto => github.com/chromedp/cdproto v0.0.0-20230104010638-078e50cebfff

I realize it would be better if the cdproto package was tagged, or had tracking branches, but we are dealing with 2 different upstream versions in terms of API (both the "browser" and "v8" definitions), and they can't really be tracked properly using Go's limited semver style. Or more or less, I can't think of any way that would be better than doing the above.
If you had thoughts/ideas on a better version tracking for cdproto, I'd be happy to hear your thoughts on the matter.

I had tried to downgrade cdproto initially, but since chromedp depended on a newer version that didn't work. Using go mod edit -replace to pin it to an older version is a good trick- thanks for sharing!
I ended up copying the deprecated definitions I needed into a new package and using them from there, so I can still keep cdproto up to date.


die if uinput module is missing

NOTE: This will cause kbct to bail if uinput is compiled into the kernel and is NOT a loaded module. I have not worked out yet how to check for this circumstance

I need to clean this up. Will resubmit soon.


Fix warning Warning: React attempted to reuse markup in a container b…

This could fix the warning of
Warning: React attempted to reuse markup in a container but the checksum was invalid. This generally means that you are using server rendering and the markup generated on the server was not what the client was expecting. React injected new markup to compensate which works but you have lost many of the benefits of server rendering. Instead, figure out why the markup being generated is different on the client or server
when directly visit post urls like http://localhost:5000/post/the-pathway-to-more-success

This can fix the second problem mentioned in #27

Would open a new PR.


Unit Test Debts

Closes #5326
Change Description
Filling in test debts for Storage Adapter
Background
Share context and relevant information for the PR: offline discussions, considerations, design decisions etc.
Bug Fix
If this PR is a bug fix, please let us know about:

Problem - The reason for opening the bug
Root cause - Discovered root cause after investigation
Solution - How the bug was fixed

New Feature
If this PR introduces a new feature, describe it here.
Testing Details
How were the changes tested?
Breaking Change?
Does this change break any existing functionality? (API, CLI, Clients)
Additional info
Logs, outputs, screenshots of changes if applicable (CLI / GUI changes)
Contact Details
How can we get in touch with you if we need more info? (ex<EMAIL_ADDRESS>

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


fix: advanced work log example

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Added Suduko Solver in Java

Have you read the Contributing Guidelines on Pull Requests?
(Yes)
Description
(Suduko Solver added in Java)
Checklist

[Y] I've read the contribution guidelines.
[Y] I've checked the issue list before deciding what to submit.
[Y] I've edited the README.md and link to my code.

Related Issues or Pull Requests
(Issue #1500 is solved here)

Conflicts to be resolved


Errors during the finetuning process

Hi, thanks for this interesting work. But when I try to train the multimodal meta-learner with the provided codes, I have encountered an error at step 400 during finetuning process:

This error happens at Line 164 in meta_trainer.py:
logits_q, pred_tokens = model(x_qry, y_qry, y_qry_mask, list(model.mapper_net.parameters()), is_finetuning=True)
because the forward function (at Line 47 in meta_learner.py) does not have is_finetuning parameter:
def forward(self, image, tokens: torch.Tensor, mask: Optional[torch.Tensor] = None, fast_weights=None, labels: Optional[torch.Tensor] = None, get_pred_tokens=True):
Besides, I find that the passed parameters of meta.finetuning() (at Line 114 in main_train.py) does not correspond to the defined arguments of finetuning() (at Line 145 in meta_trainer.py), which causes another error after I simply remove is_finetuning parameter:

So, how can I fix these errors?

Hi, thanks for pointing out this. Can you pull the latest changes and try if it works?

Thanks for reply! I have pulled the latest changes, but this error still happens:

I find that x_qry at Line 164 in meta_trainer.py is not a tensor but a list, which may cause this error.
Do the order of passed parameters for meta.finetuning(x_spt, y_spt, y_spt_mask, id_spt, x_qry, y_qry, y_qry_mask, id_qry) (at Line 114 in main_train.py) not correspond to that of finetuning(x_spt, y_spt, y_spt_mask, x_qry, y_qry, y_qry_mask, qry_answer, q_img_id) (at Line 145 in meta_trainer.py)?
It seems that meta.finetuning function passes id_spt to the argument x_qry of finetuning function.

Hi, can you try pulling and running again?

Sorry for the late response. I have pulled the latest changes and run again. And I solved the previous errors with additional modifications: replace for x_spt, y_spt, y_spt_mask, x_qry, y_qry, y_qry_mask, y_qry_answer, qry_img_id in db_test: in Line 107 at main_train.py as for x_spt, y_spt, y_spt_mask, id_spt, x_qry, y_qry, y_qry_mask, qry_img_id in db_test:, then add y_qry_answer = y_qry in Line 116.


Enable CORS?

I tried to use the API from browser. This is the error I get:

I tried get_action API with GET method as well. Also blocked by CORS.

We've already corrected it.
Thanks for report 👍


[SPARK-34465][SQL] Rename v2 alter table exec nodes

What changes were proposed in this pull request?
Rename the following v2 exec nodes:

AlterTableAddPartitionExec -> AddPartitionExec
AlterTableRenamePartitionExec -> RenamePartitionExec
AlterTableDropPartitionExec -> DropPartitionExec

Why are the changes needed?

To be consistent with v2 exec node added before: ALTER TABLE .. RENAME TO` -> RenameTableExec.
For simplicity and readability of the execution plans.

Does this PR introduce any user-facing change?
Should not since this is internal API.
How was this patch tested?
By running the existing test suites:
$ build/sbt -Phive-2.3 -Phive-thriftserver "test:testOnly *AlterTableAddPartitionSuite"
$ build/sbt -Phive-2.3 -Phive-thriftserver "test:testOnly *AlterTableDropPartitionSuite"
$ build/sbt -Phive-2.3 -Phive-thriftserver "test:testOnly *AlterTableRenamePartitionSuite"

Test build #135238 has started for PR 31584 at commit dabc422.

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

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

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

Test build #135238 has finished for PR 31584 at commit dabc422.

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

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


Upgrading pip

The current pip version is 7.0.1.But whenever i make a new virtual environment I get 1.4.1 pip version.When I run virtualenv-burrito upgrade command it says everything is up to date.Is there anyway to set default pip version and how do i upgrade virtualenv-burrito package?

The pip package is installed by virtualenv as part of the process that creates the virtualenv. To upgrade pip in a virtualenv, run pip install -U pip.


Plugability to integrate different monitoring and logging solution other than Riemann and ELK.

Currently, for Monitoring, SF provides plug-ability for only Riemann. Same is the case for logging, as it only can send logs to ELK stack. SF should build plugin mechanism to talk to multiple monitoring and logging solutions and it should easy to integrate such a system.

De scoped.


Redis cache does not appear in Application Map

We are using applicationinsights version 1.7.6, and redis version 2.8.0 but even though we are initializing the client using all the default settings we are not seeing Redis in the application map. We are seeing the Azure App Services, and CosmosDB but not Redis. Are there any known issues with Redis dependency collection? Any suggestions on how to debug the missing dependency telemetry? Thanks!

Hi @lszomoru, since it seems this is running in a vscode environment, I would recommend seeing if this issue https://github.com/microsoft/ApplicationInsights-node.js/issues/560#issuecomment-546114796 is related to your use case.

Thanks @markwolff for getting back to me.
The behavior that we are seeing is not in a vscode environment but it it one of our test applications that is running on Azure.

Got it. I also recommend making sure that you are calling .setup(...).start() before importing redis. This SDK patches modules by patching them when you initially require them. If they are already in the require cache when this SDK is started, then they can't be patched

Interesting. Do you have a sample by any chance that I can take a closer look? I have looked at our code and we call .setup(...).start() in our server.ts before we call createApp() which then creates a new instance of RedisCache.

You would need to call .setup(...).start() before you import ./createApp.js (assuming that is the file name).

We are using TypeScript but I will take a look at your example and try to sort it out. Thanks!

@markwolff, does the SDK also do any "patching" of the express module?
Should requests served by express contain the traceparent header if the following is set?
setDistributedTracingMode(appInsights.DistributedTracingModes.AI_AND_W3C)

This SDK does patching on http and https which will cover most express scenarios.
If W3C mode is enabled, this SDK will parse incoming traceparent headers and include it in all outgoing HTTP requests.

Thanks again @markwolff. I can confirm that after refactoring our code, now we can see Redis in the application map.
If W3C mode is enable should the traceparent header be included in the response that is sent to the browser? Looking at the response headers, I am only seeing the request-context header. Essentially we want to display a correlation id to the client in case of an error so that we can use that to correlate the error with the backend telemetry. Thanks!

I would only expect to see w3c headers in incoming/outgoing request headers and not in any response headers


[Test-Proxy] Propagate record mismatches exceptions back to caller

If there is a mismatch during playback between the request and the recording, the test proxy throws an exception, and the caller eventually gets back a 500 with no additional information besides "Internal Server Error". It would be helpful if we could include additional information in the response headers that include the exception that was thrown on the proxy. This will help clarify what the actual error is to the calling process.

/cc @scbedd @pakrym


chore(isolated-declarations): add tests from Deno

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#3808  👈
#3807
#3806
#3805
#3804
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Dunqing and the rest of your teammates on  Graphite


Get JSON output from non-OpenAI models

Issue with current documentation:
I'm exploring the use of open-source models via Ollama excellent application, I'm facing quite some challenges in adapting the instructions that were made for OpenAI-type models (they are perfectly interchangeable, I must say).
Is the format_instructions generated from the PydanticOutputParser supposed to work also for non-Openai models?
With Zephyr the model keeps returning the answer AND the JSON schema, even when I try to stop it from doing that...
Idea or request for content:
No response

yes the issue is that with the format_instructions, I get something like this in output:
[12:49 PM] FOPPIANO Luca
{
  "relations": [
    {
      "material": "Materials with z = 0.39 and optimally-doped Bi2Sr2−zLa z CuO6+δ",
      "tc": "36 K",
      "pressure": null,
      "me_method": null
    }
  ]
}
In JSON schema format:
{
  "type": "object",
  "required": ["relations"],
  "properties": {
    "relations": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "material": { "type": "string" },
          "tc": { "type": "string" },
          "pressure": { "type": "string", "nullabel": true },
          "me_method": { "type": "string", "nullabel": true }
        }
      }
    }
  }
}

where the JSON schema at the bottom is totally unnecessary.
I wonder if other people have tried this...


Warning PaperTrail when server starts

Preconditions
Pull updates from the develop branch
Steps to reproduce

Start the server with the command rails s

Actual result
Receive a warning:
      PaperTrail 12.2.0 is not compatible with ActiveRecord 7.1.2. We allow PT
      contributors to install incompatible versions of ActiveRecord, and this
      warning can be silenced with an environment variable, but this is a bad
      idea for normal use. Please install a compatible version of ActiveRecord
      instead (>= 5.2, < 7.1). Please see the discussion in paper_trail/compatibility.rb
      for details.

Expected result
There should be no warnings


Any suggestions on where to store the tokens once they're retrieved?

Thanks for the framework!
Do you have any suggestions, or are you planning on adding a feature, where the tokens are stored locally (in a datastore or something similar) and implementing a CognitoService class that returns the JWT tokens or, if they're expired, requesting and returning refreshed ones?
Thanks!

@vbudilov we thought about that, but every app got individual requirements for a Session and more importantly where it should reside. We have created an individual validateAccessToken method which checks for expiry and also performs an automatic refresh.


Renaming the LOCK, UNLOCK with SD prefix to avoid overriding user-defined macro

Remove LOCKBLOCK with paired macro instead to make it easy to debug
New Pull Request Checklist

[x] I have read and understood the CONTRIBUTING guide

[x] I have read the Documentation

[x] I have searched for a similar pull request in the project and found none

[x] I have updated this branch with the latest master to avoid conflicts (via merge from master or rebase)

[x] I have added the required tests to prove the fix/feature I am adding

[x] I have updated the documentation (if necessary)

[x] I have run the tests and they pass

[x] I have run the lint and it passes (pod lib lint)

This merge request fixes / reffers to the following issues: ...
Pull Request Description
In the f8fe886, we move all the previous implementation defined LOCK && UNLOCK macro to the common header SDWebImageCompat.h.
However, this header is exposed to all the public API header. People who has their own defined LOCK macro, may override (or be overrided by us) these macro define and cause compile issue. (Well, what C do :))
So let us rename it with the SD_LOCK && SD_UNLOCK prefix to avoid this.
That LOCKBLOCK, actually is not so convience because when debugging the code, that macro expansion will cause all the debugger hard to step into the line. Use SD_LOCK && SD_UNLOCK pair instead.

Because we add https://github.com/SDwebimage/SDWebImageWebPCoder into the demo project, but however, the demo project also need to build in  the CI.
This cause the issue, if we change the API or something will effect SDWebImageWebPCoder in the Core repo, that repo also need to be changed. But currentlly the related PR here: https://github.com/SDWebImage/SDWebImageWebPCoder/pull/2 was not been merged. So the CI will fail.
A simple solution, is that each time we update the Podfile in the demo project, to point to the target branch of SDWebImageWebPCoder instead of using a version number dependency. But now I think puting the WebP support into the Core repo's demo project is not a good idea. Which will cause a cycle dependency when we want to update some APIs.
As a plugin, SDWebImageWebPCoder should update itself after the Core lib new feature PR is merged, but not block the way Core lib was merging PR... 😕

Give my some opinions, LOCK things should only used in internal, so it maybe better to put it in a private header. And also SDWebImageWebPCoder  or all other frameworks should define their own LOCK macro, not just rely on SDWebImage framework. 🤔

@zhongwuzw These macro are all private previouslly. But @bpoplauschi change it into the SDWebImageCompat.h during f8fe886
To say, I don't think it's a good project development that we have no any Project Headers or Private Headers. We put all headers into the public header, which cause our API easy to break (Some internal change should not visible for any user).
I previouslly decide to add some header (For example, our utils class like SDWeakProxy, and internal property for some components which need to communicate between each other). But @bpoplauschi say there are some issue related to Private Header ? Is there any hard thing to block us use private header files ?
My personal framework, use private_header_files for CocoaPods spec files, it works. And also, for Carthage, I change the Xcode compile setting to mark it Private header. I don't meet any issue. Is there are something extra issue for introducing private headers ?

@dreampiggy I don't face any issue about private header, maybe @bpoplauschi can give some examples. IMO,for CocoaPods, private_header_files can handle this, we can see in ReactiveObjc(I don't try, maybe CocoaPods can infer public or private from Build Phases->Headers? ), for Carthage, I think it would not cause any issue either, because Carthage just build the framework based on scheme.

From what I remember, having private headers is a bit of extra work, especially since we support so many integration methods. If any of you have the time to work on that, I am not against it, but I would keep them all public for simplicity.
Regarding those macros, I think our modules like SDWebImageWebPCoder don't need to redefine them, but just use the ones from the core library, as it is a dependency.
Anyway, with this rename, I think we are ok as a public interface.

@bpoplauschi 🤔 I'm ok if you insist anyway. But TBO, LOCK 、dispatch_main_async_safe these macro may pollute the project and I think it's not the public API we want to provide, we have no documents(maybe it's trivial) and may change the internal implementation, for example, currently we use semaphore to lock, maybe in the future we may use os_unfair_lock_t or other locks instead to improve the performance. So at least maybe we should add some comments or something to tell user don't use these macro, it's not stable IMO, you can see, this PR break the SDWebImageWebPCoder  initially, maintainer like @dreampiggy should also make a PR to fix that, it proves this is a API breaking if you think it's public.
Yes, as you said, SDWebImageWebPCoder dependent on SDWebImage, but actually, everyone who uses SDWebImage would treat the SDWebImage as a dependency, CocoaPods is just a dependency manager, the only difference is SDWebImageWebPCoder also maintained by you guys? 😄 .

I think we create a private header contains these define is much better. So we can clear what is public API, which is private API (or called Project Header in Xcode) for development. This can avoid some little trick to put all unrelated class or utils method into the implementation files only.

OK...I'm busying in the past weak so that I loss some conversation here.
In long term, I still suggest to create private headers, which can move some commom utils/libs/helper method into the private files and make it easy to use (especially when different components need to share same method, instead of writing twice just to avoid exposing to public headers)
In short term, I will merge this PR simply, still keep that SD_LOCK && SD_UNLOCK in the SDWebImageCompat.h. So that this macro will not accidentally effect other user's define.

👍


Fix interface

Need to rethink the inputs and output parameters and formats. Consider whether we want more flexibility than the QuTip format allows.

Fixed in pull request #7.


unable to run kubectl-debug

kubectl-debug traefik-ingress-controller-v2-9vsvk -n kube-system
error execute remote, error sending request: Post http://<IP_ADDRESS>:10027/api/v1/debug?command=["bash"]&container=docker%3A%2F%2F506c3ea81af0d7887a8c497072439225421392a1730d4fd720a6bb640567967c&image=nicolaka%2Fnetshoot%3Alatest: dial tcp <IP_ADDRESS>:10027: connect: connection refused
error: error sending request: Post http://<IP_ADDRESS>:10027/api/v1/debug?command=["bash"]&container=docker%3A%2F%2F506c3ea81af0d7887a8c497072439225421392a1730d4fd720a6bb640567967c&image=nicolaka%2Fnetshoot%3Alatest: dial tcp <IP_ADDRESS>:10027: connect: connection refused

@hillbun Could you please try kubectl-debug --agentless --port-forward?

kubectl-debug --agentless --port-forward miop-ui-cf6bff975-9rbbs -n xxxx
Agent Pod info: [Name:debug-agent-pod-83566576-f6cd-11e9-a680-fa163e7f9e07, Namespace:default, Image:aylei/debug-agent:latest, HostPort:10027, ContainerPort:10027]
Waiting for pod debug-agent-pod-83566576-f6cd-11e9-a680-fa163e7f9e07 to run...
Error occurred while waiting for pod to run:  pod ran to completion
error: pod ran to completion

@hillbun
pls try
kubectl get pods|grep debug-agent-pod
if there is more than one agent pod, you should delete all agent pod and try
kubectl-debug --agentless --port-forward miop-ui-cf6bff975-9rbbs -n xxxx
again
if there is just one agent pod and the status is not running.you can
kubectl describe <agentPodName>
to find the reason.
I think there are probably more than one agent pod here.delete all agent pod will solve it.

it is ok now. thanks

@hillbun Could you please try kubectl-debug --agentless --port-forward?
I referenced the document, isn't  supposed to be open by default ?


missing jei

version .9.5 apparently doesn't have jei in it.

JEI is definitely there. You may have pressed ctrl+O to hide it

no, I mean when i open the pack it doesn't load beacuse jei isn't in there, since it is a requirement for other mods.
latest.log

Curseforge had some recent issues, so pack download problem is possible. Maybe close this if you have solved it?

Twitch's issues seem to be resolved, so this can be closed now


GH-2011 back to merge-commits as our preferred strategy

GitHub issue resolved: #2011
Briefly describe the changes proposed in this PR:

back to specifying 'merge-commit' as our PR merge strategy

PR Author Checklist (see the contributor guidelines for more details):

[ ] my pull request is self-contained
[ ] I've added tests for the changes I made
[ ] I've applied code formatting (you can use mvn process-resources to format from the command line)
[ ] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change
[ ] every commit has been signed off

Note: we merge all feature pull requests using squash and merge. See RDF4J git merge strategy for more details.

I briefly thought about also adding rebase again as a merge option, and while I would personally like it, I think in the end we're better off just keeping it simple, and doing everything using merge-commits.

It's fine with me. Do you have any tips for squashing a branch together that has develop merged into it several times?

It's fine with me. Do you have any tips for squashing a branch together that has develop merged into it several times?

I think this is only a problem if there are merge conflicts involved. In any case, the simplest way to deal with it is probably to use rebase instead of merge to bring your branch up to date with develop. Also has the advantage of making the history easier to read after your branch has been merged back.

Bit late to start rebasing it now. Haven't bothered much with rebasing since we squash and merge anyway.

Bit late to start rebasing it now. Haven't bothered much with rebasing since we squash and merge anyway.

I'm fine with still using squash and merge for your existing feature branch. Just for any future work, we go back to manual squash + merge commit.

We can probably keep both methods. For our own work we can squash and merge if we want, while for other committers we use normal merge.

We can probably keep both methods. For our own work we can squash and merge if we want, while for other committers we use normal merge.

I thought of that, but it makes things more error-prone, having two separate merge methods in play. Also, there is a fundamental problem with git overwriting the author field that can affect core committers as well.
So I'm really not in favour of keeping squash-and-merge as an option.


Permission directive takes a reference to a string as opposed to a string.

Version Output:
+--<EMAIL_ADDRESS>Problem:
When trying to use the permission directive as follows:
<div permission permission-sref="home.index">

it will do nothing because permission-sref should be a string so the correct call would be:
<div permission permission-sref="'home.index'">

Not sure if the documentation is wrong on this or the implementation.
Additionally, wouldn't it be possible to reuse the ui-sref if it's available instead of the permission-sref?

Case in point, it's correct in the wiki but the code documentation is off.


Beautify the Readme.md

We need a more attractive version of the current readme file.

I want to work on this issue. Please assign it to me.

yeah sure, go ahead!

I want to work on this..

yeah sure, go ahead!

I would like to work on this.

yeah sure, go ahead!

The README looks great! Can I add a section on how to install and run the task (git cloning, running, compiling etc?)

The README looks great! Can I add a section on how to install and run the task (git cloning, running, compiling etc?)

assigned to @Dutta-SD

assigned to @Dutta-SD


feat: 🎸 export TypeScript types and improve build process

Export TypeScript types
Build with tsc
Remove Gulp
Publish to NPM only lib/ folder
Upgrade TypeScript to latest version
Import React as wildcard
Refresh readme links

I suggest not makingyarn mandatory; not everyone will or can have it installed.  Works crappy on my Windows machine, crashes on build on my Linux install.  & others find issues with Yarn:
https://iamturns.com/yarn-vs-npm-2018/

@tomByrer do you mean not to include yarn.lock or not including yarn build etc.. commands?

Build version: 2.1.0-pr-13.88 :crossed_fingers: fix-build on Travis :tada:

Build version: 2.1.0-pr-13.90 :crossed_fingers: fix-build on Travis :tada:

Build version: 2.1.0-pr-13.92 :crossed_fingers: fix-build on Travis :tada:

Build version: 2.1.0-pr-13.94 :crossed_fingers: fix-build on Travis :tada:

Build version: 2.1.0-pr-13.96 :crossed_fingers: fix-build on Travis :tada:

Build version: 2.1.0-pr-13.98 :crossed_fingers: fix-build on Travis :tada:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Cannot pipe data to docker container

I've tried:
python examples/test_rng_example.py | docker run --rm -it <name>:latest --small-crush`

but unfortunately I get errors with the PIPE:
the input device is not a TTY
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='UTF-8'>
BrokenPipeError: [Errno 32] Broken pipe

Starting the container without the pipe works. I shows the initial log outputs of "SmallCrush" and waits for data.
Starting docker only with -i does not show the error, it starts the SmallCrush as expected but the input data is a static and unrelated value.

Now I'm not so familiar with docker and for sure i googled and tried varying parameters but all without success. Do you have an suggestions how to fix this?

PS: I totally forget to say thanks for this contribution :-)! It is really helpful and simplifies usage of the TestU01 library a lot – if only I got it running.

Got the same error. Just remove t flag from testu01 container due to not the TTY device:
python examples/test_rng_example.py | docker run --rm -i <name>:latest --small-crush


Building the Rainmaker Agent Firmware

Pasted into the terminal the following command (per the online instructions):
 pio run --environment core2foraws

In the Getting-Started project. I'm getting the following error:
 file failed to open for reading (No such file or directory):

/Core2-for-AWS-IoT-EduKit/Getting-Started/.pio/build/core2foraws/x509_crt_bundle

Should I be?
Thanks,
Jaime Katz

This is a duplicate of: https://github.com/m5stack/Core2-for-AWS-IoT-EduKit/issues/75 . Please follow that issue while I triage that issue.
Closing this issue.


Feature/homepage

Description
MUCH REFACTORING!!!
Homepage: adjusted to function with the porfileReducer instead of the HomePageReducer. Also adjusted some logic, removed some unnecessary code, and added some comments.
GrantsPage: adjust to function with the grantsReducer instead of the grantsHomePageReducer. Refractored a little bit.
components>applicant-profile>Grant.js: adjusted the useSelector method to work with the grantsReducer instead of grantsHomePageReducer.
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Change Status

[ ] Complete, tested, ready to review and merge
[x] Complete, but not tested (may need new tests)

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My code has been reviewed by at least one peer
[x] My changes generate no new warnings
[x] There are no merge conflicts

Looks good!


Fix registration transaction signing with Ledger signer plugin

Closes #3505.

If you're going to fix this, fix it in a generic manner.  The correct thing to do would be to go and alter oasis-core-ledger/internal/app.go:LedgerOasis.sign() to force a 1 sec interval between signing operations.

If you're going to fix this, fix it in a generic manner. The correct thing to do would be to go and alter oasis-core-ledger/internal/app.go:LedgerOasis.sign() to force a 1 sec interval between signing operations.

Agreed.


Add useProxies to registryMirror allowing to mirror more anything

Description
Add a new field in registryMirror, allowing to use proxies list to decide whether to use dragonfly.
By doing this, it is now possible to cache more than only blobs/sha256 urls, allowing to use dragonfly2 for other usage thatn docker registries, like yum repositories.
Also fix the whiteList test which is tested on direct request, although host is empty and canno tbe tested.
Please update the documentation in Chinese, I just can't do it.
Related Issue
#959
Motivation and Context
This PR now allows to use dragonfly to mirror yum repositories, at least.
Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation Update (if none of the other choices apply)

Checklist:

[x] Code compiles correctly.
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Codecov Report

Merging #965 (8220f05) into main (abfa0a3) will increase coverage by 0.09%.
The diff coverage is 75.00%.

@@            Coverage Diff             @@
##             main     #965      +/-   ##
==========================================
+ Coverage   42.19%   42.29%   +0.09%
==========================================
  Files         116      116
  Lines        8783     8789       +6
==========================================
+ Hits         3706     3717      +11
+ Misses       4609     4607       -2
+ Partials      468      465       -3

Flag
Coverage Δ

Object-compatibility-e2etests
?

e2etests
?

unittests
42.29% <75.00%> (+0.09%)
:arrow_up:

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

Impacted Files
Coverage Δ

client/config/peerhost.go
35.29% <ø> (ø)

client/daemon/proxy/proxy.go
8.81% <75.00%> (+1.54%)
:arrow_up:

client/daemon/peer/peertask_base.go
45.38% <0.00%> (+0.57%)
:arrow_up:

pkg/sync/krwmutex.go
86.36% <0.00%> (+4.54%)
:arrow_up:

pkg/sync/kmutex.go
100.00% <0.00%> (+16.66%)
:arrow_up:

I apologize as I've never done this before, but I guess once used to the PR process, it will be easier and less a pain for me :)
I've tested the fix and confirm is it working perfectly on my real environments, using the docker image built for this purpose on my github account.
Will there be a v2.0.2 or v2.1.0 version including the fix soon? Not sure if including the alpha changes is necessary.

I apologize as I've never done this before, but I guess once used to the PR process, it will be easier and less a pain for me :)
I've tested the fix and confirm is it working perfectly on my real environments, using the docker image built for this purpose on my github account.
Will there be a v2.0.2 or v2.1.0 version including the fix soon? Not sure if including the alpha changes is necessary.

Next release is v2.0.2. This change will be included.


504 Gateway Timeout when multiple tabs are reopened

Describe the bug
We identified a minor bug when the notebook image is stopped and restarted while 2+ ipynb notebooks are open. There appears to be an unusual problem restarting the kernels when the notebook resumes
Expected behavior
Kernels are resumed without showing an error to the user
Screenshots

Installation instructions (Please mark the checkbox)
[X] I followed the installation guide at https://github.com/openvinotoolkit/openvino_notebooks#-installation-guide to install the notebooks.

@Xaenalt I updated jupyterhub. It is still difficult to replicate this for me. Could you try on your end if that fixed the issue?

Rebuilding it now, will get back to you with results shortly

Confirming this is resolved with this update

Thanks for testing @Xaenalt ! Glad that it is resolved.


python312Packages.ring-doorbell: 0.8.11 -> 0.8.12

Changelog: https://github.com/tchellomello/python-ring-doorbell/releases/tag/0.8.12
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 322959 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.ring
python311Packages.ring-doorbell
python311Packages.ring-doorbell.dist
python312Packages.ring-doorbell
python312Packages.ring-doorbell.dist


$repeat does not play nice with HTML elements

It is not possible to $repeat a component that has a HTML element as an ancestor.
Example tree:
<node>

    <node>
      <node id="please-repeat-me">Never!</node>
    </node>

</node>

Results in error:
Uncaught Error: ParentNode with UID null does not exist. Unable to process $if/$repeat

Similarly, it is not possible to $repeat a HTML element.
behaviors: {
  '.item': {
    '$repeat': '[[identity|products]]'
  }
},
states: {
  products: [1,2,3,4]
},
tree: `
<node>

</node
`

Will result in this error: Uncaught Error: No dependencies found for div (null)`

My instinct is we will need to do some refactoring to address this in full. We have very basic support for targeting DOM elements directly with behaviors, but there many are cases like this one that will result in an error.
The workaround for the time being would either be to: (a) wrap the element you want to $repeat in a <node> (although that obviously isn't ideal as it adds superfluous nesting) or (b) use a content behavior and repeat by returning a string with the accumulated elements, e.g.:
behaviors: {
    '#listing': {
        content: function(products) {
            var out = '';
            for (var i = 0; i < products.length; i++) {
                out += `<div class="item">${products[i].name}</div>`;
            }
            return out;
        }
    }
},
tree: `
    <node id="listing"></node>
`

For posterity it's worth noting that that example will only work with
inner-html as the behavior.
On Jul 2, 2015 8:17 AM, "Matthew Trost"<EMAIL_ADDRESS>wrote:

My instinct is we will need to do some refactoring to address this in
full. We have very basic support for targeting DOM elements directly with
behaviors, but there many are cases like this one that will result in an
error.
The workaround for the time being would either be to: (a) wrap the element
you want to $repeat in a  (although that obviously isn't ideal as
it adds superfluous nesting) or (b) use a content behavior and repeat by
returning a string with the accumulated elements, e.g.:
behaviors: {
'#listing': {
content: function(products) {
var out = '';
for (var i = 0; i < products.length; i++) {
out +=
${products[i].name}
;
}
return out;
}
}
},
tree:     <node id="listing"></node>
—
Reply to this email directly or view it on GitHub
https://github.com/Famous/framework/issues/42#issuecomment-118065059.

^ 'content' will work when applied to a <node> component, as shown in my snippet. But you are correct in noting that if you are targeting a DOM element, you would use 'inner-html' to render raw HTML.

A major downside of this approach is that Framework does not register events to HTML inserted by content or inner-html. It's only really useful for inserting static content.


Documentation for common usecases

Documentation is definitely missing.
It would be great to see some of common use-cases. For instance, converting sam/bam to to adam, loading features map fr/bed file, getting genes form it, finding transcripts from several samples by gene names and showing the diffs

Closing in favor of #890, #886, #878, #879, #821.


When using callout many times, it can not work

[!hint]- hint 1
![[1.6]]

This "1.6" file includes an image with a callout. In the callout block I only see the image but can not enlarge it.
and if the callout with a ''-'' like this

[!hint]-
image

Holding down left alt does not work too.

The plugin modifies the image size, but this causes the callout to reload, which results in it being closed again. Unfortunately, I don't believe there is a way to avoid this issue.


Data Observability - Separate Alerts from Notification

Currently, we are mixing Alerts and Notifications via the same mechanism. However, the mechanism might be the same for Notifications and Alerts in the backend the usability from the UI suffers.
Changes Proposed:

Rename Alerts under the Notifications section to be Notifications

Notifications should have the same Trigger mechanism as selecting a Resource

Filter By options will have

EventType
Owner
FQN
UpdatedBY
Task is added
Tasks is deleted
Task is closed

Add a new Section on the Settings page -> "Data Observability."

Add Alerts
In Alerts, We will have the following Trigger options
2.1.  Tables, Topics, Database etc..
2.1.1. Schema Change
2.1.2. Ownership
2.1.3 Tags
2.1.4 Deleted
2.1.5 Pipeline Status
2.1.6 Test Case Result
2.2 Allow Branch conditions or multiple conditions
2.2.1 match on FQN and test Result
2.2.2 match on FQN test result etc..
Destination

Todos

[ ] https://github.com/open-metadata/OpenMetadata/issues/10428
[ ] https://github.com/open-metadata/OpenMetadata/issues/12505
[ ] https://github.com/open-metadata/OpenMetadata/issues/10319
[ ] https://github.com/open-metadata/OpenMetadata/issues/9874

@mohityadav766 @Sachin-chaurasiya pushing this to 1.3

Ex:
Send me alerts on all of my following assets when a schema changes or a test fails
Send me alerts on all changes to my owned data assets
Send alerts when my test suite has one or more failures
Separating general purpose alerts vs data observability alerts
This epic will also fix the current issues that are propping up in our alert system

@mohityadav766 @chirag-madlani @aniketkatkar97 what is remaining here to close it out?

@harshach the unit tests are remaining here and a minor bug from the backend side

Feature completed with #14969


XML3D Shaders: default uniforms

Where can I find the list of uniforms defined for xml3d shaders?
Surely some of them are predefined.
To be precise: I'm looking for inversion of modelView matrix. It would be great if I could bypass computing it in shader.

Hi,
these aren't documented anywhere right now, but you can look at the source code to see what's defined:
SceneRenderPass
Phong shader
Of course if you're writing your own RenderPass you can define any uniforms that you want, but these are the ones that get supplied to the shader during the built in scene render pass.

Great thanks, modelViewMatrixN is trasposition of an inverse of modelView - right?
Also have a question which is maybe slighlty out of scope, how can I check which version of shading language (opengl es) I'm using?

No they're just 3x3 versions of the the matrices meant to be used with vertex normals. The renderer doesn't provide the inverse matrices, but if you need them you could define your own copy of the SceneRenderPass and add them to the systemUniforms array yourself. You'd just need to replace the require imports with calls to the global XML3D object instead, like:
var BaseRenderPass = XML3D.webgl.BaseRenderPass;
var Options = XML3D.options;
var mat4 = XML3D.math.mat4;

Then in your RenderTree instead of creating an instance of the internal SceneRenderPass you create your own:
var scenePass = new MySceneRenderPass(renderInterface, output, opt);

About the version, it should always be the same since WebGL 1.0 is the only supported API right now. It's basically OpenGL ES 2.0 and GLSL ES 1.0. But you can check this by creating a webgl context and reading out the version constants:
var canvas = document.createElement("canvas");
var gl = canvas.getContext("webgl");
gl.VERSION
gl.SHADING_LANGUAGE_VERSION

FYI, just remembered there are a few more uniforms set in the forward render pass which is what kicks off the scene render passes. So these should be available in your shader too:
systemUniforms["viewMatrix"] = c_worldToViewMatrix;
systemUniforms["viewInverseMatrix"] = c_viewToWorldMatrix;
systemUniforms["projectionMatrix"] = c_projectionMatrix;
systemUniforms["cameraPosition"] = scene.getActiveView().getWorldSpacePosition();
systemUniforms["coords"] = [target.width, target.height, 1];

Great! viewInverseMatrix is precisely what I've needed!


Error: The onCancel handler was attached after the promise settled.

I get the following for new Sitemapper({ url: 'https://www.google.com/sitemap.xml' }):
Error: The `onCancel` handler was attached after the promise settled.

Hey @WillSquire will take a look here, what version are you using?

@WillSquire if you have a stacktrace this would be helpful too, and you can also add a debug flag to see more details
new Sitemapper({ url: 'https://www.google.com/sitemap.xml', debug: true });
I just ran this on the latest version and it works okay:
const Sitemapper = require("sitemapper");

const sitemap = new Sitemapper({
  url: "https://www.google.com/sitemap.xml",
  debug: true,
});

sitemap.fetch().then((results) => console.log(results.sites));

Results:
Additional sitemap found during "crawl('https://www.google.com/sitemap.xml')"
Urlset found during "crawl('https://www.google.com/docs/sitemaps.xml')"
Urlset found during "crawl('https://www.google.com/gmail/sitemap.xml')"
Urlset found during "crawl('https://www.google.com/sheets/sitemaps.xml')"
Urlset found during "crawl('https://www.google.com/admob/sitemap.xml')"
Urlset found during "crawl('https://www.google.com/forms/sitemaps.xml')"
Urlset found during "crawl('https://www.google.com/slides/sitemaps.xml')"
Urlset found during "crawl('https://www.google.com/get/sitemap.xml')"
Additional sitemap found during "crawl('https://www.google.com/adsense/start/sitemap.xml')"
Urlset found during "crawl('https://www.google.com/adwords/sitemap.xml')"
Error occurred during "crawl('https://www.google.com/webmasters/sitemap.xml')":
 Error: HTTP Error occurred: Response code 404 (Not Found)
Urlset found during "crawl('https://www.google.com/partners/about/sitemap.xml')"
Urlset found during "crawl('https://www.google.com/search/about/sitemap.xml')"
Error occurred during "crawl('https://www.google.com/flights/sitemap.xml')":
 Error: Error occurred: Error
Urlset found during "crawl('https://www.google.com/business/sitemap.xml')"
Urlset found during "crawl('https://www.google.com/drive/sitemap.xml')"
Urlset found during "crawl('https://www.google.com/chromebook/sitemap.xml')"
Urlset found during "crawl('https://www.google.com/adsense/start/sitemap-2.xml')"
Urlset found during "crawl('https://www.google.com/calendar/about/sitemap.xml')"
Urlset found during "crawl('https://www.google.com/services/sitemap.xml')"
Urlset found during "crawl('https://www.google.com/sitemap_search.xml')"
Urlset found during "crawl('https://www.google.com/retail/sitemap.xml')"
Urlset found during "crawl('https://www.google.com/nonprofits/sitemap.xml')"
Urlset found during "crawl('https://www.google.com/finance/sitemap.xml')"
Urlset found during "crawl('https://www.google.com/photos/sitemap.xml')"
Urlset found during "crawl('https://www.google.com/adsense/start/sitemap-1.xml')"
Urlset found during "crawl('https://www.google.com/chrome/sitemap.xml')"
[
  'https://www.google.com/intl/am/gmail/about/',
  'https://www.google.com/intl/am/gmail/about/for-work/',
  'https://www.google.com/intl/am/gmail/about/policy/',
  'https://www.google.com/intl/ar/gmail/about/',
  'https://www.google.com/intl/ar/gmail/about/for-work/',
  'https://www.google.com/intl/ar/gmail/about/policy/',
  'https://www.google.com/intl/bg/gmail/about/',
  'https://www.google.com/intl/bg/gmail/about/for-work/',
  'https://www.google.com/intl/bg/gmail/about/policy/',
  'https://www.google.com/intl/bn/gmail/about/',
  'https://www.google.com/intl/bn/gmail/about/for-work/',
  'https://www.google.com/intl/bn/gmail/about/policy/',
  'https://www.google.com/intl/cs/gmail/about/',
  'https://www.google.com/intl/cs/gmail/about/for-work/',
  'https://www.google.com/intl/cs/gmail/about/policy/',
  'https://www.google.com/intl/cs/gmail/about/',
  'https://www.google.com/intl/cs/gmail/about/for-work/',
  'https://www.google.com/intl/cs/gmail/about/policy/',
  'https://www.google.com/intl/da/gmail/about/',
  'https://www.google.com/intl/da/gmail/about/for-work/',
  'https://www.google.com/intl/da/gmail/about/policy/',
  'https://www.google.com/intl/de/gmail/about/',
  'https://www.google.com/intl/de/gmail/about/for-work/',
  'https://www.google.com/intl/de/gmail/about/policy/',
  'https://www.google.com/intl/el/gmail/about/',
  'https://www.google.com/intl/el/gmail/about/for-work/',
  'https://www.google.com/intl/el/gmail/about/policy/',
  'https://www.google.com/intl/en_in/gmail/about/',
  'https://www.google.com/intl/en_in/gmail/about/for-work/',
  'https://www.google.com/intl/en_in/gmail/about/policy/',
  'https://www.google.com/intl/en_uk/gmail/about/',
  'https://www.google.com/intl/en_uk/gmail/about/for-work/',
  'https://www.google.com/intl/en_uk/gmail/about/policy/',
  'https://www.google.com/intl/es-419/gmail/about/',
  'https://www.google.com/intl/es-419/gmail/about/for-work/',
  'https://www.google.com/intl/es-419/gmail/about/policy/',
  'https://www.google.com/intl/es/gmail/about/',
  'https://www.google.com/intl/es/gmail/about/for-work/',
  'https://www.google.com/intl/es/gmail/about/policy/',
  'https://www.google.com/intl/et/gmail/about/',
  'https://www.google.com/intl/et/gmail/about/for-work/',
  'https://www.google.com/intl/et/gmail/about/policy/',
  'https://www.google.com/intl/eu_es/gmail/about/',
  'https://www.google.com/intl/eu_es/gmail/about/for-work/',
  'https://www.google.com/intl/eu_es/gmail/about/policy/',
  'https://www.google.com/intl/fa/gmail/about/',
  'https://www.google.com/intl/fa/gmail/about/for-work/',
  'https://www.google.com/intl/fa/gmail/about/policy/',
  'https://www.google.com/intl/fi/gmail/about/',
  'https://www.google.com/intl/fi/gmail/about/for-work/',
  'https://www.google.com/intl/fi/gmail/about/policy/',
  'https://www.google.com/intl/fil/gmail/about/',
  'https://www.google.com/intl/fil/gmail/about/for-work/',
  'https://www.google.com/intl/fil/gmail/about/policy/',
  'https://www.google.com/intl/fr/gmail/about/',
  'https://www.google.com/intl/fr/gmail/about/for-work/',
  'https://www.google.com/intl/fr/gmail/about/policy/',
  'https://www.google.com/intl/gl_es/gmail/about/',
  'https://www.google.com/intl/gl_es/gmail/about/for-work/',
  'https://www.google.com/intl/gl_es/gmail/about/policy/',
  'https://www.google.com/intl/gu_in/gmail/about/',
  'https://www.google.com/intl/gu_in/gmail/about/for-work/',
  'https://www.google.com/intl/gu_in/gmail/about/policy/',
  'https://www.google.com/intl/hi/gmail/about/',
  'https://www.google.com/intl/hi/gmail/about/for-work/',
  'https://www.google.com/intl/hi/gmail/about/policy/',
  'https://www.google.com/intl/hr/gmail/about/',
  'https://www.google.com/intl/hr/gmail/about/for-work/',
  'https://www.google.com/intl/hr/gmail/about/policy/',
  'https://www.google.com/intl/hu/gmail/about/',
  'https://www.google.com/intl/hu/gmail/about/for-work/',
  'https://www.google.com/intl/hu/gmail/about/policy/',
  'https://www.google.com/intl/id/gmail/about/',
  'https://www.google.com/intl/id/gmail/about/for-work/',
  'https://www.google.com/intl/id/gmail/about/policy/',
  'https://www.google.com/intl/is/gmail/about/',
  'https://www.google.com/intl/is/gmail/about/for-work/',
  'https://www.google.com/intl/is/gmail/about/policy/',
  'https://www.google.com/intl/it/gmail/about/',
  'https://www.google.com/intl/it/gmail/about/for-work/',
  'https://www.google.com/intl/it/gmail/about/policy/',
  'https://www.google.com/intl/he/gmail/about/',
  'https://www.google.com/intl/he/gmail/about/for-work/',
  'https://www.google.com/intl/he/gmail/about/policy/',
  'https://www.google.com/intl/ja/gmail/about/',
  'https://www.google.com/intl/ja/gmail/about/for-work/',
  'https://www.google.com/intl/ja/gmail/about/policy/',
  'https://www.google.com/intl/kn_in/gmail/about/',
  'https://www.google.com/intl/kn_in/gmail/about/for-work/',
  'https://www.google.com/intl/kn_in/gmail/about/policy/',
  'https://www.google.com/intl/ko/gmail/about/',
  'https://www.google.com/intl/ko/gmail/about/for-work/',
  'https://www.google.com/intl/ko/gmail/about/policy/',
  'https://www.google.com/intl/lt/gmail/about/',
  'https://www.google.com/intl/lt/gmail/about/for-work/',
  'https://www.google.com/intl/lt/gmail/about/policy/',
  'https://www.google.com/intl/lv/gmail/about/',
  'https://www.google.com/intl/lv/gmail/about/for-work/',
  'https://www.google.com/intl/lv/gmail/about/policy/',
  'https://www.google.com/intl/ml_in/gmail/about/',
  ... 46834 more items
]


Add Gatsby Astronaut placeholder image

Adding this image will allow users to add a relative src to add an image to their page in the Part 1 Tutorial here: https://www.gatsbyjs.org/tutorial/part-one/
See discussion here: https://github.com/gatsbyjs/gatsby/issues/9655
How to QA

If you haven't already, globally install the gatsby-cli; npm install --global gatsby-cli
Run: gatsby new gatsby-astronaut-pr https://github.com/barrymcgee/gatsby-starter-hello-world/
Drop into that folder; cd gatsby-astronaut-pr
Run the starter; npm start
View the site in your browser at; http://localhost:8000/
You should just see "Hello world"
Open the site folder in your editor and find; src/pages/index.js
Replace it's contents with;

import React from "react"

export default () => (
  <div style={{ color: `purple` }}>

Hello Gatsby!

What a world.

)

Switching back to your browser; http://localhost:8000/ should now look like the screenshot below;

@tanvibhakta Would you be able to QA this change for me please?
It will then unblock https://github.com/gatsbyjs/gatsby/pull/9698 which will resolve https://github.com/gatsbyjs/gatsby/issues/9655

Hello! I will do this in 48 hours, hope that's okay. My family celebrated
Deepavali so I'm trying not to use much tech today.
On Mon, Nov 5, 2018, 6:43 PM Barry McGee<EMAIL_ADDRESS>wrote:

@tanvibhakta https://github.com/tanvibhakta Would you be able to QA
this change for me please?
It will then unblock gatsbyjs/gatsby#9698
https://github.com/gatsbyjs/gatsby/pull/9698 which will resolve
gatsbyjs/gatsby#9655 https://github.com/gatsbyjs/gatsby/issues/9655
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gatsbyjs/gatsby-starter-hello-world/pull/27#issuecomment-435869062,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANID5oIa7CBWDkF9Ddt_fcEyOUA_4IgWks5usDl0gaJpZM4YM65g
.

Hi there! Just following up on this, is it ready to merge?

Hi @tanvibhakta, do you have any bandwidth this week to review this please? Maybe if you're super busy, @shannonbux could take a look?

Hello everyone! Thanks for your hard work here and apologies for the time it took to reach a decision on this PR and the connected one (https://github.com/gatsbyjs/gatsby/pull/9698). For now, I'm going to close this in favor of https://github.com/gatsbyjs/gatsby/issues/9374 since a adding a page to the tutorial specifically on gatsby-image introduces a best practice. Thanks in advance for your patience with this idea; we only recently realized how few people know about gatsby-image and we'd like to use the tutorial as one of the ways to teach about it.
It will be valuable to get your input on that new gatsby-image tutorial and honestly, if any of you feels up to reviewing all the image-related docs and cleaning them up, they could use it!
Here's the issue for cleaning those up!
https://github.com/gatsbyjs/gatsby/issues/4319


Is there a way of validating slice directly

v10
Question:
Hey. I trying to validate slice directly, but it show error: (nil []User). Is there a way of validating slice without struct outside.
Code sample:

type User struct {
    name string `json:"name" validate:"required"`
}

var params []User
...
...
validate.Struct(params)

@ticktap yes, please see the docs for more info but:
validate.Var(params)

@ticktap yes, please see the docs for more info but:
validate.Var(params)

validate.Var  validates a single variable. But I need to validate every field in slice. Did I miss something?

Yep please look at the docs they have a lot of info :)
But if you validate with the “dive” tag it will dive down into the elements of the array like you want.

@deankarn  It work, thank you!

Just so others can get the answer quickly.
validate.Var(params, "dive")


[authoring] Invalid range after deleting text that has a comment

We should decide what to do when a an entire comment range get's deleted.
Should the comment be auto-resolved?

Should the comment be auto-resolved?

We made a choice initially that we'd like to continue to render these comment threads but in a "disconnected" state
This probably shouldn't warn but just swallow the error? It's likely a warning due to previous debugging.

This probably shouldn't warn but just swallow the error? It's likely a warning due to previous debugging.

Ok if the comment range length is zero we should swallow the warning and leave the comment thread in the sidebar.


failed to run the tests

Hello, I built the tests successfully, but it failed for all the testing, maybe there is some misconfiguration for my building. Are there any suggestions for finding out the reasons?
Thanks a lot for your help!
zw241@gpu001:~/cworkspace/src/gdrcopy/tests$ ./copybw
Assertion "cudaSuccess == result" failed at copybw.cpp:108
zw241@gpu001:~/cworkspace/src/gdrcopy/tests$ ./sanity
Running suite(s): Sanity
Assertion "cudaSuccess == result" failed at sanity.cpp:178
Assertion "cudaSuccess == result" failed at sanity.cpp:220
Assertion "cudaSuccess == result" failed at sanity.cpp:319
Assertion "cudaSuccess == result" failed at sanity.cpp:447
Assertion "cudaSuccess == result" failed at sanity.cpp:527
Assertion "cudaSuccess == result" failed at sanity.cpp:607
Assertion "cudaSuccess == result" failed at sanity.cpp:756
Assertion "cudaSuccess == result" failed at sanity.cpp:868
Assertion "cudaSuccess == result" failed at sanity.cpp:1008
Assertion "cudaSuccess == result" failed at sanity.cpp:1117
Assertion "cudaSuccess == result" failed at sanity.cpp:1222
Assertion "cudaSuccess == result" failed at sanity.cpp:1337
0%: Checks: 12, Failures: 0, Errors: 12
sanity.cpp:170:E:Basic:basic:0: (after this point) Early exit with return value 1
sanity.cpp:212:E:Basic:basic_unaligned_mapping:0: (after this point) Early exit with return value 1
sanity.cpp:311:E:Data Validation:data_validation:0: (after this point) Early exit with return value 1
sanity.cpp:425:E:Invalidation:invalidation_access_after_gdr_close:0: (after this point) Early exit with return value 1
sanity.cpp:505:E:Invalidation:invalidation_access_after_cumemfree:0: (after this point) Early exit with return value 1
sanity.cpp:591:E:Invalidation:invalidation_two_mappings:0: (after this point) Early exit with return value 1
sanity.cpp:713:E:Invalidation:invalidation_fork_access_after_cumemfree:0: (after this point) Early exit with return value 1
sanity.cpp:861:E:Invalidation:invalidation_fork_after_gdr_map:0: (after this point) Early exit with return value 1
sanity.cpp:996:E:Invalidation:invalidation_fork_child_gdr_map_parent:0: (after this point) Early exit with return value 1
sanity.cpp:1091:E:Invalidation:invalidation_fork_map_and_free:0: (after this point) Early exit with return value 1
sanity.cpp:1216:E:Invalidation:invalidation_unix_sock_shared_fd_gdr_pin_buffer:0: (after this point) Early exit with return value 1
sanity.cpp:1315:E:Invalidation:invalidation_unix_sock_shared_fd_gdr_map:0: (after this point) Early exit with return value 1

The information of the device
zw241@gpu001:~/cworkspace/src/gdrcopy/tests$ nvidia-smi
Sun Sep 22 17:43:13 2019
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 390.116                Driver Version: 390.116                   |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  Tesla M2070         On   | 00000000:09:00.0 Off |                    0 |
| N/A   N/A    P0    N/A /  N/A |    185MiB /  5301MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  Tesla M2070         On   | 00000000:0A:00.0 Off |                    0 |
| N/A   N/A   P12    N/A /  N/A |    137MiB /  5301MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   2  Tesla M2070         On   | 00000000:0D:00.0 Off |                    0 |
| N/A   N/A   P12    N/A /  N/A |    137MiB /  5301MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
...

@wangzhezhe
Hi,
Can I ask you to try deviceQuery or bandwidthTest? These two applications are included in the samples folder of your cuda package.

Hello, @pakmarkthub, thanks for your reply. I use the cluster from my university, and they did not build them in the bin directory.  I suspect that CUDA is not setup properly (might be an issue in your user environment). So, I would like you to verify with those standard applications first.

Hello, @pakmarkthub thanks for your suggestion, I got following results on node with the tesla M2070:
zw241@gpu003:~/cworkspace/src/samples/1_Utilities/bandwidthTest$ nvidia-smi
Mon Sep 23 16:13:39 2019
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 390.116                Driver Version: 390.116                   |
|-------------------------------+----------------------+----------------------+
...
| N/A   N/A   P12    N/A /  N/A |    137MiB /  5301MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   7  Tesla M2070         On   | 00000000:33:00.0 Off |                    0 |
| N/A   N/A   P12    N/A /  N/A |    137MiB /  5301MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+
zw241@gpu003:~/cworkspace/src/samples/1_Utilities/bandwidthTest$./bandwidthTest
[CUDA Bandwidth Test] - Starting...
Running on...

cudaGetDeviceProperties returned 35
-> CUDA driver version is insufficient for CUDA runtime version
CUDA error at bandwidthTest.cu:242 code=35(cudaErrorInsufficientDriver) "cudaSetDevice(currentDevice)"
zw241@gpu003:~/cworkspace/src/samples/1_Utilities/bandwidthTest$ cd ../
UnifiedMemoryPerf/       bandwidthTest/           deviceQuery/             deviceQueryDrv/          p2pBandwidthLatencyTest/ topologyQuery/
zw241@gpu003:~/cworkspace/src/samples/1_Utilities/bandwidthTest$ cd ../deviceQuery
zw241@gpu003:~/cworkspace/src/samples/1_Utilities/deviceQuery$ ./deviceQuery
./deviceQuery Starting...

 CUDA Device Query (Runtime API) version (CUDART static linking)

cudaGetDeviceCount returned 35
-> CUDA driver version is insufficient for CUDA runtime version
Result = FAIL

But on the node with the GeForce RTX 208... I got the following results:
zw241@gpu008:~/cworkspace/src/samples/1_Utilities/bandwidthTest$ nvidia-smi
Mon Sep 23 16:00:11 2019
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 430.26       Driver Version: 430.26       CUDA Version: 10.2     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce RTX 208...  On   | 00000000:1B:00.0 Off |                  N/A |
| 43%   81C    P2   261W / 250W |   8162MiB / 11019MiB |     95%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce RTX 208...  On   | 00000000:1C:00.0 Off |                  N/A |
| 45%   83C    P2   244W / 250W |   8162MiB / 11019MiB |     97%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce RTX 208...  On   | 00000000:1D:00.0 Off |                  N/A |
| 46%   84C    P2   241W / 250W |   8166MiB / 11019MiB |     97%      Default |
...
zw241@gpu008:~/cworkspace/src/samples/1_Utilities/bandwidthTest$ ls
Makefile  NsightEclipse.xml  bandwidthTest  bandwidthTest.cu  bandwidthTest.o  readme.txt
zw241@gpu008:~/cworkspace/src/samples/1_Utilities/bandwidthTest$ cd ..
zw241@gpu008:~/cworkspace/src/samples/1_Utilities$ ls
UnifiedMemoryPerf  bandwidthTest  deviceQuery  deviceQueryDrv  p2pBandwidthLatencyTest  topologyQuery
zw241@gpu008:~/cworkspace/src/samples/1_Utilities$ cd deviceQuery
zw241@gpu008:~/cworkspace/src/samples/1_Utilities/deviceQuery$ ls
Makefile  NsightEclipse.xml  deviceQuery  deviceQuery.cpp  deviceQuery.o  readme.txt
zw241@gpu008:~/cworkspace/src/samples/1_Utilities/deviceQuery$ ./deviceQuery
./deviceQuery Starting...

 CUDA Device Query (Runtime API) version (CUDART static linking)

Detected 1 CUDA Capable device(s)

Device 0: "GeForce RTX 2080 Ti"
  CUDA Driver Version / Runtime Version          10.2 / 10.0
  CUDA Capability Major/Minor version number:    7.5
  Total amount of global memory:                 11019 MBytes<PHONE_NUMBER>6 bytes)
  (68) Multiprocessors, ( 64) CUDA Cores/MP:     4352 CUDA Cores
  GPU Max Clock rate:                            1545 MHz (1.54 GHz)
  Memory Clock rate:                             7000 Mhz
  Memory Bus Width:                              352-bit
  L2 Cache Size:                                 5767168 bytes
  Maximum Texture Dimension Size (x,y,z)         1D=(131072), 2D=(131072, 65536), 3D=(16384, 16384, 16384)
  Maximum Layered 1D Texture Size, (num) layers  1D=(32768), 2048 layers
  Maximum Layered 2D Texture Size, (num) layers  2D=(32768, 32768), 2048 layers
  Total amount of constant memory:               65536 bytes
  Total amount of shared memory per block:       49152 bytes
  Total number of registers available per block: 65536
  Warp size:                                     32
  Maximum number of threads per multiprocessor:  1024
  Maximum number of threads per block:           1024
  Max dimension size of a thread block (x,y,z): (1024, 1024, 64)
  Max dimension size of a grid size    (x,y,z):<PHONE_NUMBER>, 65535, 65535)
  Maximum memory pitch:<PHONE_NUMBER> bytes
  Texture alignment:                             512 bytes
  Concurrent copy and kernel execution:          Yes with 3 copy engine(s)
  Run time limit on kernels:                     No
  Integrated GPU sharing Host Memory:            No
  Support host page-locked memory mapping:       Yes
  Alignment requirement for Surfaces:            Yes
  Device has ECC support:                        Disabled
  Device supports Unified Addressing (UVA):      Yes
  Device supports Compute Preemption:            Yes
  Supports Cooperative Kernel Launch:            Yes
  Supports MultiDevice Co-op Kernel Launch:      Yes
  Device PCI Domain ID / Bus ID / location ID:   0 / 140 / 0
  Compute Mode:
     < Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) >

deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 10.2, CUDA Runtime Version = 10.0, NumDevs = 1
Result = PASS

For both nodes, the sanity test program fail.

Hello, @pakmarkthub I reset the cuda version to make it match with the driver version , it works this time but there are some new problems:
zw241@gpu003:~/cworkspace/src/samples/1_Utilities/deviceQuery$ ./deviceQuery
./deviceQuery Starting...

 CUDA Device Query (Runtime API) version (CUDART static linking)

Detected 1 CUDA Capable device(s)

Device 0: "Tesla M2070"
  CUDA Driver Version / Runtime Version          9.1 / 9.0
  CUDA Capability Major/Minor version number:    2.0
  Total amount of global memory:                 5302 MBytes<PHONE_NUMBER> bytes)
MapSMtoCores for SM 2.0 is undefined.  Default to use 64 Cores/SM
MapSMtoCores for SM 2.0 is undefined.  Default to use 64 Cores/SM
  (14) Multiprocessors, ( 64) CUDA Cores/MP:     896 CUDA Cores
  GPU Max Clock rate:                            1147 MHz (1.15 GHz)
  Memory Clock rate:                             1566 Mhz
  Memory Bus Width:                              384-bit
  L2 Cache Size:                                 786432 bytes
  Maximum Texture Dimension Size (x,y,z)         1D=(65536), 2D=(65536, 65535), 3D=(2048, 2048, 2048)
  Maximum Layered 1D Texture Size, (num) layers  1D=(16384), 2048 layers
  Maximum Layered 2D Texture Size, (num) layers  2D=(16384, 16384), 2048 layers
  Total amount of constant memory:               65536 bytes
  Total amount of shared memory per block:       49152 bytes
  Total number of registers available per block: 32768
  Warp size:                                     32
  Maximum number of threads per multiprocessor:  1536
  Maximum number of threads per block:           1024
  Max dimension size of a thread block (x,y,z): (1024, 1024, 64)
  Max dimension size of a grid size    (x,y,z): (65535, 65535, 65535)
  Maximum memory pitch:<PHONE_NUMBER> bytes
  Texture alignment:                             512 bytes
  Concurrent copy and kernel execution:          Yes with 2 copy engine(s)
  Run time limit on kernels:                     No
  Integrated GPU sharing Host Memory:            No
  Support host page-locked memory mapping:       Yes
  Alignment requirement for Surfaces:            Yes
  Device has ECC support:                        Enabled
  Device supports Unified Addressing (UVA):      Yes
  Supports Cooperative Kernel Launch:            No
  Supports MultiDevice Co-op Kernel Launch:      No
  Device PCI Domain ID / Bus ID / location ID:   0 / 9 / 0
  Compute Mode:
     < Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) >

deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 9.1, CUDA Runtime Version = 9.0, NumDevs = 1
Result = PASS

zw241@gpu003:~/cworkspace/src/samples/1_Utilities/bandwidthTest$ ./bandwidthTest
[CUDA Bandwidth Test] - Starting...
Running on...

 Device 0: Tesla M2070
 Quick Mode

 Host to Device Bandwidth, 1 Device(s)
 PINNED Memory Transfers
   Transfer Size (Bytes)	Bandwidth(MB/s)
   33554432			6483.9

 Device to Host Bandwidth, 1 Device(s)
 PINNED Memory Transfers
   Transfer Size (Bytes)	Bandwidth(MB/s)
   33554432			6454.0

 Device to Device Bandwidth, 1 Device(s)
 PINNED Memory Transfers
   Transfer Size (Bytes)	Bandwidth(MB/s)
   33554432			105231.0

Result = PASS

NOTE: The CUDA Samples are not meant for performance measurements. Results may vary when GPU Boost is enabled.
zw241@gpu003:~/cworkspace/src/samples/1_Utilities/bandwidthTest$
zw241@gpu003:~/cworkspace/src/gdrcopy/build/bin$ ./sanity
Running suite(s): Sanity
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:188
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:252
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:337
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:454
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:534
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:617
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:763
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:875
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1015
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1124
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1254
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1378
0%: Checks: 12, Failures: 1, Errors: 11
sanity.cpp:170:E:Basic:basic:0: (after this point) Early exit with return value 1
sanity.cpp:212:E:Basic:basic_unaligned_mapping:0: (after this point) Early exit with return value 1
sanity.cpp:311:E:Data Validation:data_validation:0: (after this point) Early exit with return value 1
sanity.cpp:425:E:Invalidation:invalidation_access_after_gdr_close:0: (after this point) Early exit with return value 1
sanity.cpp:505:E:Invalidation:invalidation_access_after_cumemfree:0: (after this point) Early exit with return value 1
sanity.cpp:591:E:Invalidation:invalidation_two_mappings:0: (after this point) Early exit with return value 1
sanity.cpp:730:F:Invalidation:invalidation_fork_access_after_cumemfree:0: Assertion 'read(read_fd, &cont, sizeof(int)) == sizeof(int)' failed: read(read_fd, &cont, sizeof(int)) == 0, sizeof(int) == 4
sanity.cpp:861:E:Invalidation:invalidation_fork_after_gdr_map:0: (after this point) Early exit with return value 1
sanity.cpp:996:E:Invalidation:invalidation_fork_child_gdr_map_parent:0: (after this point) Early exit with return value 1
sanity.cpp:1091:E:Invalidation:invalidation_fork_map_and_free:0: (after this point) Early exit with return value 1
sanity.cpp:1216:E:Invalidation:invalidation_unix_sock_shared_fd_gdr_pin_buffer:0: (after this point) Early exit with return value 1
sanity.cpp:1315:E:Invalidation:invalidation_unix_sock_shared_fd_gdr_map:0: (after this point) Early exit with return value 1
zw241@gpu003:~/cworkspace/src/gdrcopy/build/bin$ ./copybw
GPU id:0 name:Tesla M2070 PCI domain: 0 bus: 9 device: 0
selecting device 0
testing size: 131072
rounded size: 131072
device ptr: 1302f00000
Assertion "!((g) == ((void*)0))" failed at copybw.cpp:137

Hi @wangzhezhe,
This library supports only Tesla and Quadro GPUs. So, it would not work with your GeForce RTX card.
About the issue on your Tesla M2070 machine, have you already installed gdrdrv? This is a driver, which comes with this repository. If you have root privilege, you can simply run sudo ./insmod.sh. A better way is to build dep or rpm packages with the scripts we provide. Then install those packages.

Hello, @pakmarkthub , thanks for your explanation. Is root privilege necessary to install this? I could ask the administrator team of the cluster to see if they could provide help.

@wangzhezhe Unfortunately, yes. Please try copybw and sanity again after you get the driver installed.


Basic Station time synchronization.

Closes #179.
Supports request and response to the "timesync" message type of the LNS protocol.
Tested with a Cisco IXM and the gateway time is now provided in the uplink messages.

Thanks @vfylyk :+1:


Fix cli help --author flag typo

Thanks for the great tool. I noticed (what I believe is) a typo in the CLI help text for the --author flag and thought I'd PR a fix.

Great, thank you!


select json data from mysql without quotes

we use
selectjson->'\$.name' from table_xx
in sql editor, the result contains quotes as below

<EMAIL_ADDRESS>
but if we use
selectjson->>'\$.mail' from table_xx
then we can get the result without quotes but unreadable as blow

6C75632E6170617369383840676D61696C2E636F6D

plz upgrade the mysql driver to mysql-connector-java-8.0.18

You can add mysql8 driver as a custom datasource.


Surrogate spike trains module (+ unittests)

The module contains various routines (+ wrapper) to generate
different types of surrogates given an input spike trains.
This pull request follows and replaces the previous pull request
"Surrogates" (#24)

Coverage decreased (-0.05%) to 99.3% when pulling 280f183f35324b5529f7a6632a831aa91164600c on etorre:surrogates into 634dfd21fbb575d97ddfcda61c90fbf40d0eec03 on NeuralEnsemble:master.


Update s3, sdk-core, sqs to 2.17.13

Updates

software.amazon.awssdk:s3
software.amazon.awssdk:sdk-core
software.amazon.awssdk:sqs

from 2.17.11 to 2.17.13.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

labels: library-update, semver-patch

Superseded by #252.


ino-header: Provide different sizes

We should provide different sizes for our <ino-header> component.
Currently, our default fontSize is only 13px which is quite small for a heading.
Provide a new property (e.g. size or header) to customize the size of the component.
We should take inspiration from the native heading elements (h1, h2, h3, ...).

should be implemented in a global stylesheet as a class (see #154)


Add AWQ quantization inference support

Add AWQ quantization inference support
Fixes https://github.com/huggingface/text-generation-inference/issues/781
This PR (partially) adds support for AWQ quantization for inference. More information on AWQ here. In general, AWQ is faster and more accurate than GPTQ, which is currently supported by TGI.
This PR installs 4-bit GEMM custom CUDA kernels released by AWQ authors (in requirements.txt, just one line change).
Quick way to test this PR would be bring up TGI as follows:
text-generation-server download-weights abhinavkulkarni/codellama-CodeLlama-7b-Python-hf-w4-g128-awq

text-generation-launcher \
--huggingface-hub-cache ~/.cache/huggingface/hub/ \
--model-id abhinavkulkarni/codellama-CodeLlama-7b-Python-hf-w4-g128-awq \
--trust-remote-code --port 8080 \
--max-input-length 2048 --max-total-tokens 4096 --max-batch-prefill-tokens 4096 \
--quantize awq

Please note:

This PR was tested with FlashAttention v2 and vLLM.
This PR adds support for AWQ inference, not quantizing the models. That needs to be done outside of TGI, instructions here.
This PR only adds support for FlashLlama models for now.
Multi-GPU setup has not been tested.
No integration tests have been added so far, will add later if maintainers are interested in this change.
This PR can be tested on any of the models released here.

Please refer to the linked issue for benchmarks for abhinavkulkarni/meta-llama-Llama-2-7b-chat-hf-w4-g128-awq vs TheBloke/Llama-2-7b-Chat-GPTQ.
Please note, AWQ has released faster (and in case of Llama, fused) kernels for 4-bit GEMM, currently at the top of the main branch at https://github.com/mit-han-lab/llm-awq, but this PR uses an older commit that has been tested to work. We can switch to latest commit later on.
Who can review?
@OlivierDehaene OR @Narsil

Amazing work @abhinavkulkarni. The original creators of AWQ recently removed all support of the GEMM kernel, however, after extensive testing of the GEMV kernel, I believe the GEMM kernel is the best for the highest throughput (large context, large batch size) as the GEMV kernel struggles with performance on anything but empty context and batch size > 1.
I am the author of AutoAWQ and will maintain backward compatibility with GEMM as the main packing method and GEMV as an optional packing method (about to be merged). You can either use the old commit or switch to AutoAWQ, which has a PyPi package that is easily installable:
pip install autoawq

Hey thanks a LOT for this PR.
Before diving into the details, I'll drop some benchmark I did on single A100:
f16:

awq

gptq

These tell a very good story.
Baseline latency for AWQ is 15ms/per, 25ms/token for f16 and 20ms/token for exllama.
But more importantly, the baseline holds much better for AWQ at higher throughput, giving more throughput at constant latency.
F16 seems to be managing to reach higher throughput but this regime is not the main one for usual TGI deployments, where latency is the key.
I will probably make a bit more testing on different TP sharding layout and model sizes but this looks really good.

Ok, my comments are mostly nits about code maintenance, but this PR looks great !
Thanks for it !

@Narsil @abhinavkulkarni Has this PR been tested to be compatible with the 300+ AWQ repositories that @TheBloke has pushed with AutoAWQ?
Most notably, I want to ensure that the models can be loaded in TGI with the quant_config.json that is provided.
Example: https://huggingface.co/TheBloke/Llama-2-13B-AWQ

@TheBloke: Can we get some clarity on naming the quantization config for GPTQ and AWQ?
You seem to name it as  quantize_config.json for GPTQ and quant_config.json for AWQ.
TGI code expects it to be named quantize_config.json.
Is it possible for you to rename it to quantize_config.json across all your AWQ repos? Or create a symlink in these repos so that both the files are present?

I would advise against renaming to quantize_config.json as that makes all his repositories incompatible with AutoAWQ, which was used to create the 300+ repositories.

Yeah that's because AutoGPTQ and AutoAWQ create that file with a different name.  AutoGPTQ creates it as quantize_config.json, but AutoAWQ creats it as quant_config.json.
I'm happy to rename it across all, but it will require AutoAWQ updating to support that name (not quite sure why a different name was used by AutoAWQ)

Okay, @TheBloke, @casper-hansen and @Narsil, please agree on one standard.
I'm happy to comply with whatever is decided. Two issues we need consensus on:

Wether to have quantize_config.json for GPTQ and quant_config.json for AWQ or just one for both

Secondly, uniformity in how we refer to quantization parameters - for e.g. in GPTQ quantize_config.json, we use bits but in quant_config.json of AWQ, we use w_bit. Same for groupsize for GPTQ vs group_size for AWQ.

Please let me know what you agree on and I'll modify the PR accordingly.

@abhinavkulkarni GPTQ doesn't use groupsize, it's group_size there too.
IMHO the best option is for AutoAWQ to update to use quantize_config.json, and match the param names of AutoGPTQ.   Ultimately the hope is that AutoAWQ will be integrated into Transformers, like AutoGPTQ was.  If/when that happens, I am certain the Transformers team will ask for the same param names - though they won't care about the filename because the data will need to go into config.json
Here is the params that Transformers expects in config.json:
    "quantization_config": {
        "bits": 4,
        "group_size": 128,
        "damp_percent": 0.1,
        "desc_act": true,
        "sym": true,
        "true_sequential": true,
        "model_name_or_path": null,
        "model_file_base_name": "model",
        "quant_method": "gptq"
    }

Based on this, IMHO AutoAWQ should create a quantize_config.json matching this format:
"bits": 4,
"group_size": 128,
"zero_point": true,
"version": "GEMM"

Then that will be easily integrated into Transformers' config.json -> quantization_config section in future - with the addition of a "quant_method": "awq" key as well.
For backwards compatibility, AutoAWQ could also read from quant_config and the old key names, so that support for existing models is still provided.  Though I would update all my repo config files to the new format at such a time as the change was made.

I know that Huggingface takes backward compatibility very seriously. Implementing this in AutoAWQ requires quite a bit of maintenance going forward and it will break all PyPi releases of AutoAWQ (v0.0.1, v0.0.2, v0.1.0) because it will not be able to read any Huggingface repository. Additionally, the oobabooga/text-generation-webui will also need to update their version because it will brick the functionality in the PR. I am also not sure if this breaks the vLLM support for AWQ.
I am not so sure that people will be happy with this change for the reasons that I just explained, but I would gladly accept PRs that refactor the current behavior and extract the logic into a QuantizeConfig class that implements the necessary logic for backward compatibility. However, going forward, we have to support quant_config.json for multiple versions and raise warnings in AutoAWQ before we phase the quant_config.json out (just like they do in Huggingface libraries). We can finally phase it out in the next major release: v0.2.0.

vLLM already allows for both filenames:
   @classmethod
    def get_config_filenames(cls) -> List[str]:
        return [
            "quant_config.json",  # E.g., casperhansen/vicuna-7b-v1.5-awq
            "quantize_config.json",  # E.g., abhinavkulkarni/mosaicml-mpt-7b-instruct-w4-g128-awq  # pylint: disable=line-too-long
        ]

HF take backwards compatibility seriously once something is in a Hugging Face project - so they definitely won't want it to change after AWQ is merged.  Before it's merged I don't think they'll care one way or the other.  But they may well ask for the w_bits -> bits param change to be made in order for it to be merged, so I think you're going to end up doing at least that change eventually if you want it in Transformers.
So if this change is going to be made, I would say the time to do it is now - there's never a good time for a change that might break compatibility, but earlier is always far better than later
If the config file name does change, I'm happy to have both quantize_config and quant_config.json in all my repos for a while, which would allow ongoing support for prior AutoAWQ versions and any un-updated clients. Then I could phase it out in a a few weeks, once everyone is up-to-date. A bit like I've handled the many breaking llama.cpp changes.

I agree with @TheBloke that it's better to make changes now than later.
So, how about this:

@TheBloke, please write a "translator" to translate AutoAWQ quant_config.json to quantize_config.json and have both of them in the model repo. Please back-process all of your published models to have both of these files.

@casper-hansen: Over a period of time, please deprecate quant_config.json and start publishing quantize_config.json in the format HF team expects.

Agreed?

Ok, only nits are left. I will merge this into dev and add the nits I wanted to share and add an integration tests.
Thank you very much for this contribution !

Totally agree with all the names/config discussion, which is why I suggested reusing all the code we could for awq to match gptq.
Also in this repo, unlike in transformers we might want to make the necessary changes to  support the existing repos (provided they are not too hard to support as in little lines of code.)

Also looking at the fix PR : https://github.com/casper-hansen/AutoAWQ/commit/e1884728238bae0df16fde6094eaaed08ffc9762 (Is that correct ?) it seems the fix, is just removing the unecessary kernels.

This part is not Windows support for the GEMM kernel, those are FasterTransformer kernels.
Here I added Windows support. It's super simple. MSVC does not support __asm__ __volatile__, so just remove the underscores and it works. https://github.com/casper-hansen/AutoAWQ/commit/4c39a76a17d08f6d6eea95abe9f6c7ff7107ab24

Oh nice Thanks for the tip !

There is only a 10% difference in inference between llama2 7b model quantized and unquantized on a single A100 GPU. In the autoAWQ inference example, there is a fuse_layer option that can significantly affect the speed depending on whether it is set to 'true/false'. I am curious if this option is always set to true in TGI

Is flash attention v2 installed and on?

I tested using the tgi-1.1.0 Docker image, which has Flash Attention v2 installed.


Updating wiki links

Updates the Pmod wiki link to the official link, and the Snail IDE wiki link
Edit: https://forum.snail-ide.com/d/187-mr-rudy-gave-me-permission-to-make-a-new-wiki

oops already did it before i saw it lol


callback results

I was following along a video tutorial https://www.youtube.com/watch?v=Jl6BuoXcZPE&ab_channel=codewithbrandon
and everything was working fine. I subsituted ollama for openai but things seemed to be working except for the very last step.
The callback function for the last step is missing the task_output.result.
How do I debug this? Where is the callback documentation.
Full source at https://github.com/iplayfast/OllamaPlayground/tree/main/crewAIAsync
def save_markdown(task_output):
    #get today's date in the format YYY-MM-DD
    today_date = datetime.now().strftime('%Y-%m-%d')
    # set the filename with today's date
    filename = f"{today_date}.md"
    #write the task output to the markdown file
    with open(filename,'w') as file:
        file.write(task_output.result)########## Error here
    print(f"Newsletter saved as {filename}")

what version of crewai are you using?
because you might want to do task_output.raw_output
or you can even have the task save the output by setting a
output_file=filename.md to the task
João Moura
@joaomdmoura http://twitter.com/joaomdmoura
Em seg., 26 de fev. de 2024 às 04:39, Chris Bruner @.***>
escreveu:

I was following along a video tutorial
https://www.youtube.com/watch?v=Jl6BuoXcZPE&ab_channel=codewithbrandon
and everything was working fine. I subsituted ollama for openai but things
seemed to be working except for the very last step.
The callback function for the last step is missing the task_output.result.
How do I debug this? Where is the callback documentation.
Full source at
https://github.com/iplayfast/OllamaPlayground/tree/main/crewAIAsync
def save_markdown(task_output):
#get today's date in the format YYY-MM-DD
today_date = datetime.now().strftime('%Y-%m-%d')
# set the filename with today's date
filename = f"{today_date}.md"
#write the task output to the markdown file
with open(filename,'w') as file:
file.write(task_output.result)########## Error here
print(f"Newsletter saved as {filename}")
—
Reply to this email directly, view it on GitHub
https://github.com/joaomdmoura/crewAI/issues/274, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFC3N25JPUDHHUTPMSED7LYVQ32JAVCNFSM6AAAAABDZVRALKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE2TGNBVG43DGMQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Well that was interesting ```
I'm unable to create a comprehensive AI newsletter for you as the required tool "NewsletterCompiler" is not available. However, I can suggest you delegate this
task to a team member who has expertise in creating newsletters, and provide them with the necessary context and examples for reference. Here's an example messa
ge for delegating the work:
Subject: Request for creating a comprehensive AI newsletter

Hi [Team Member],

I hope this message finds you well. I have been tasked with creating a weekly AI newsletter for our internal team and external subscribers. The newsletter shoul
d include accurate, well-formatted summaries for each AI news story from the provided list. Each summary should provide sufficient context for our readers and m
aintain a consistent style and layout throughout the newsletter as shown in the example output.

Could you please create a comprehensive AI newsletter in markdown format based on this description and the following examples? I believe your expertise in creat
ing newsletters would be greatly beneficial to this project.

If you have any questions or need additional context, feel free to ask. I will ensure that all necessary information is provided.

Looking forward to your contribution!

Please modify the message as per your specific needs and team communication style. Let me know if you require further assistance.

Quick question.  If I am using different agents to accomplish different custom task executions how to make the Crew route to appropriate agent and get the answer and complete the execution.  I tried to use Process.hierarchical thinking if I have multiple agents connected to the process then it will execute the agent and once it gets the answer it will come back.  But it takes the output and calls the other agent which is the not the right behaviour in my case because it will get wrong answers.
If question a call Agent A; workflow done
If question b call Agent B; workflow done
if question c call Agent C; workflow done
In other words I need the Process to operate like a smart router based on the question.  Is it possible in CrewAI?

Hello @lvenkataraman,
Any additional info about your issue?
I am facing the same error.
Thanks in advance!

any news?


update go-cosmosdb version to incorporate the latest change

Which issue this PR addresses:
Fixes https://msazure.visualstudio.com/AzureRedHatOpenShift/_workitems/edit/12373924
What this PR does / why we need it:
It updates go-cosmosdb version in go.mod and go.sum to incorporate the latest change
Test plan for issue:
Make succeeded and did not do any other tests as it is just an update on the go mod files
Is there any documentation that needs to be updated for this PR?
No, as nothing actually changed

/azp run ci

/azp run e2e

Thanks @m1kola , looks like all checks have passed, please merge it at your convenience, thanks again.


[ISSUE-71] Support create function in console

Support creating functions in console.
Support loading the function jars and run in DSL job.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: 652053395:x: liaofanshu.lfsliaofanshu.lfs seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Implement iceoryx transport layer prototype

Iceoryx  realized a zero copy shared memory  data transfer following the publish / subscribe pattern. The layered eCAL architecture allows to utilize / combine different transport protocols without interfering the high level API mechanisms.
Even Iceoryx is only available for POSIX systems it would be interesting to check the performance against the existing eCAL shared memory transport layer.

Iceoryx transport layer integrated and tested, local performance looks very promising. There is still some potential for optimization on eCAL's iceoryx datawriter implementation.


[wip] Add some docs to encourage friends to contribute back easily

Tagging this as a WIP because I actually haven't verified that it's works. Wanted to experiment with react-html and felt some friction getting up and running. hopefully this can help encourage people to get started who haven't used lerna before.

@ismail-syed  are you still working on this?


Updates readme

Changes

Updates README.md and INSTALL.md to reflect evolution of the project. Notably: removes Sheer references from installation steps.

Review

@jimmynotjim
@sebworks
@KimberlyMunoz
@kurtw
@kave
@rosskarchner

Tagging @kave and @kurtw to confirm that we can remove Sheer and sheer-like is all we need now.

:+1:

:+1: but you may still want @kave and @kurtw to look it over