Error: RTT not supported on device without HW breakpoints

My project is just started.  I followed the instructions for stm32-hal2 and the Knurling template.  The project builds and flashes to the device successfully as far as I can tell.  However, after flashing it prints the titular error about RTT support.  Here's the full output:
> cargo rb hello
    Finished dev [optimized + debuginfo] target(s) in 0.01s
     Running `probe-run --chip STM32L562CETxP target/thumbv7m-none-eabi/debug/hello`
  (HOST) INFO  flashing program (6.98 KiB)
  (HOST) INFO  success!
Error: RTT not supported on device without HW breakpoints

hello is provided by the app template.  It's not clear whether this error is coming from the HAL or probe-run or probe-rs, so I'm starting here.  Is it possible to simply turn off RTT?
I've uploaded my project here:
https://github.com/jonahbron/rollova/

I'll look into this and get back to you. Are you running this with the thumbv8 target?

This target: thumbv8m.main-none-eabihf

Updated the example config.toml with which target to use by MCU, to make this more explicit. (I don't think this is the problem here of the RTT error)

Note: To narrow it down to see if this crate is the cause, try commenting out the stm32_hal2 import, and all uses of it in your code, and see if you get the same error

Thanks for the quick response.  I mis-understood the target options.  Unfortunately, changing the target had no effect on the error.
Removing the dependency and references in the code also had no effect.  Do you think it's a probe-rs issue then?

I think it's likely with probe-rs or probe-run, with a small chance it's defmt. I'm curious what's going on, and would like to put a fix for it in the readme here etc once we figure it out.

Yes, ST-LINK (v2).  Only connecting 4 wires (Vdd, Vcc, SWDIO, SWCLK).  I've used OpenOCD to read from the registers, but that's it.  I'm not certain what exactly I would replace with OpenOCD, but I can look into it if you think that might help.

Are you able to connect the reset line as well? I'm not sure if that's related, as when I disconnect it, probe-rs can't recognize the device at all.

Just tried with the RST line connected, but the result was the same.
Okay, let me do some research and figure out how to do that.

All right, I made a lot of progress, but didn't quite get there.  After going through everything in the installation section of the Embedded Rust Book, I got most of the way through the GDB debugging section.  I could run load over gdb, but if I continue to run the program, it spits this out:
(gdb) continue
Continuing.

Program received signal SIGTRAP, Trace/breakpoint trap.
lib::__bkpt () at asm/lib.rs:49
49	asm/lib.rs: No such file or directory.

This seems kind of unrelated to the previous error about RTT though.  I can set breakpoints as the book suggests, and they seem to work fine.

If you haven't already, I recommend posting issues in the probe-rs and/or probe-run repos. I'm curious what the cause is. Wish I had an L5 to try to reproduce with.

Another thought: do you have the l5 rt feature enabled in Cargo.toml for this HAL?
ie:
stm32-hal2 = { path = "../../stm32-hal", features = ["l562", "l5rt"]}

I will file a bug over there next, but I think I've gotten closer to finding the source of the openocd issue.
>>> arm-none-eabi-gdb -q target/thumbv8m.main-none-eabihf/debug/hello
Reading symbols from target/thumbv8m.main-none-eabihf/debug/hello...
(gdb) target remote :3333
Remote debugging using :3333
cortex_m_rt::Reset ()
    at /home/jonah/.cargo/registry/src/github.com-1ecc6299db9ec823/cortex-m-rt-0.6.13/src/lib.rs:497
497	pub unsafe extern "C" fn Reset() -> ! {
(gdb) load
Loading section .vector_table, size 0x400 lma 0x8000000
Loading section .text, size 0x1410 lma 0x8000400
Loading section .rodata, size 0x448 lma 0x8001810
Loading section .data, size 0x30 lma 0x8001c58
Start address 0x08000400, load size 7304
Transfer rate: 17 KB/sec, 1826 bytes/write.
(gdb) monitor arm semihosting enable
semihosting is enabled

(gdb) break main
Breakpoint 1 at 0x80004ae: file /home/jonah/Projects/rollova/src/bin/hello.rs, line 6.
Note: automatically using hardware breakpoints for read-only addresses.
(gdb) continue
Continuing.

Breakpoint 1, hello::__cortex_m_rt_main_trampoline ()
    at /home/jonah/Projects/rollova/src/bin/hello.rs:6
6	#[cortex_m_rt::entry]
(gdb) step
halted: PC: 0x080004b4
hello::__cortex_m_rt_main () at /home/jonah/Projects/rollova/src/bin/hello.rs:8
8	    let x = 1 + 3;
(gdb) step
halted: PC: 0x080004be
halted: PC: 0x080004c0
9	    defmt::info!("Hello, world!, {}", x);
(gdb) step
halted: PC: 0x080008e4
defmt::export::acquire ()
    at /home/jonah/.cargo/registry/src/github.com-1ecc6299db9ec823/defmt-0.2.1/src/export.rs:36
36	    unsafe { _defmt_acquire() }
(gdb) step
halted: PC: 0x08000778
defmt_rtt::_defmt_acquire ()
    at /home/jonah/.cargo/registry/src/github.com-1ecc6299db9ec823/defmt-rtt-0.2.0/src/lib.rs:25
25	#[defmt::global_logger]
(gdb) step
defmt_rtt::{{impl}}::acquire ()
    at /home/jonah/.cargo/registry/src/github.com-1ecc6299db9ec823/defmt-rtt-0.2.0/src/lib.rs:39
39	        let primask = register::primask::read();
(gdb) step
cortex_m::register::primask::read ()
    at /home/jonah/.cargo/registry/src/github.com-1ecc6299db9ec823/cortex-m-0.7.2/src/register/primask.rs:29
29	    let r: u32 = call_asm!(__primask_r() -> u32);
(gdb) step
halted: PC: 0x08000b80
lib::__primask_r () at asm/lib.rs:50
50	asm/lib.rs: No such file or directory.
(gdb)

As you can see, stepping through the program makes it all the way to a crate called cortex-m, which is a dependency of stm32-hal2.  Some missing assembly it seems.  Does that spark any ideas?

Have you confirmed you're using the l5rt feature when loading the HAL? This triggers adding the runtime feature in that cortex-m crate.

I misunderstood the example and didn't realize both were needed.  I've updated it, but the behavior is not different (even after a cargo clean and re-building).  Latest is pushed up to the repo.
https://github.com/jonahbron/rollova/

Going to close this, since it's likely not something we can fix here. Please re-open, or post another issue if you find out more.


Create Reusable Search Bar Component with API Console Log

Issue Details:
Create a search bar component in components folder. Style with Tailwind CSS. On search click, console log the output from the API service class using the search bar's text and "Yash Bhatia" as the user.
Technical Requirements:

SearchBar.tsx in components.
Style with Tailwind.
Console log API service class output on search.

Acceptance Criteria:

Exists in components.
Styled with Tailwind.
Console logs API output on search.

Search bar in the components folder is imported in the page.tsx class. However when trying to render the search bar the webpage could not compile(react state management issue).

error ./app\components\searchBar.tsx
ReactServerComponentsError:

You're importing a component that needs useState. It only works in a Client Component but none of its parents are marked with "use client", so they're Server Components by default.
Learn more: https://nextjs.org/docs/getting-started/react-essentials
,-[C:\Users\17156\CSCI4961\lrda_website\app\components\searchBar.tsx:1:1]
1 | import React, { useState } from 'react';
:                 ^^^^^^^^
2 | import ApiService from './ApiService';
3 |
3 |
`----
Maybe one of these should be marked as a client entry with "use client":
./app\components\searchBar.tsx
./app\layout.tsx
This error would appear in the terminal and on the webpage. Requires further troubleshooting.

I saw that you were having issues with compiling and importing the files so I just imported the files and fixed up the issues. Then we had other render issues from an old layout.tsx so I cleaned up that file. So now search works and it console logs so this issue is actually finished and ready to be merged into main.


Extract unnamed calendar attachment from emails

Some emails contain calendar (vcal?) attachments that have no filename, only these headers:
Content-Type: text/calendar; charset="utf-8"; method=CANCEL
Content-Transfer-Encoding: base64

It would be nice to show them as plain-text attachments.
When somebody decides to work on this, they should ping thiss issue and I'll add an example file to testdata and link it here.

moved https://github.com/CRJI/EIC/issues/568


adding Toolbar js object

Fixes #218

@filoozom I'll be travelling for next couple of days, can you please publish the new version after merging this?

Sure, was just about to open a pull request for this too 😄

Still need to bind _onChange I think.

done


URL Cleanup

This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener).
Fixed URLs
Fixed Success
These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended.

[ ] http://www.apache.org/licenses/ with 1 occurrences migrated to:
https://www.apache.org/licenses/ (https result 200).
[ ] http://www.apache.org/licenses/LICENSE-2.0 with 433 occurrences migrated to:
https://www.apache.org/licenses/LICENSE-2.0 (https result 200).

Merged as https://github.com/spring-projects/spring-amqp/commit/1614a4b0532b83e29b2a2fdb8dac102576b8aa51 after updating Copyrights to the current year.


SQL Testing

Dependent on a more mature frontend-backend-database setup.  Then we can write SQL checks with more intelligence that pg_isready.  E.g. queries with counts or expected values.
Will ask for @rparfig to help!
Benefit: we'll know if backups are any good!

Out of scope.


Remove warnings.warn deprecation calls in favor of warnings.deprecated once supported by PyCharm

See https://github.com/pydantic/pydantic/pull/8294/files#r1424534166 for more details.
Tracked issue:

https://youtrack.jetbrains.com/issue/PY-61651/Deprecation-highlighting-with-PEP-702-deprecated-decorator

@Viicos, thanks for logging this reminder!


want to add an random  quote generator page

build using html , css, javascript and node
Can you assign this to me


info: list users

I opened an issue on the baileys repo concerning if list users is possible.
I received an answer which may well be of use to mudslide:
await client.groupFetchAllParticipating()

Hi @lightaffaire
I've seen the Bailyes issue, unfortunately that library function lists all the groups a user is a member of (Mudslide is already using it).
AFAIK there is no library call to get a list of users.


Update deprecation message

Update the deprecation message to include both our March 2023 deprecation for JAVA/JS/Python and September 2023 deprecation for .NET/Golang

I made some additoinal changes.

I made some additoinal changes.

Thanks for polishing the header message, did not relize the .net date plane has different deprecation date. I'm ok with this change


Fix database detection for lsvast

:notebook_with_decorative_cover: Description
@lava feel free to push onto this branch if you immediately see the issue with the second commit. I don't think it's worth spending too much time on the matter.
:memo: Checklist

[x] All user-facing changes have changelog entries.
[x] The changes are reflected on docs.tenzir.com/vast, if necessary.
[x] The PR description contains instructions for the reviewer, if necessary.

:dart: Review Instructions
Commit-by-commit. To be reviewed by @lava.

@JoeLoser as a side note for your planning: we plan to migrate the functionality of lsvast into a dedicated command vast dump db. If you are up for this slightly more involved refactoring, we'd love to give you more details.

@mavam I think you may have skipped the part where this PR was opened by @dominiklohmann , not @JoeLoser ;)
Also, our plan was to expose the functionality in addition to having a separate binary, since we always stressed that this is primarily a debugging tools so it's important to guarantee that lsvast does not modify the on-disk state (in particular does not append to server.log) and can still work with corrupted database dirs, which is hard to verify after we have spawned our entire regular actor system.

Looks good to me. I've enabled auto-merge.

@mavam I think you may have skipped the part where this PR was opened by @dominiklohmann , not @JoeLoser ;)

Oh boy, indeed! 🙈
Well, @JoeLoser is contributing so much goodness that I begin to assume he's authoring most of the refactoring PRs. 😅


Log cluster/master name instead of entire object when reconciling

There's a slight inconsistency in the JSON logs from the orchestrator where it usually logs the name of the cluster or master when reconciling - except for when logging "reconciling cluster" and "cluster failover finished" where the cluster and master keys in the JSON output contains the entire API resource.
This is causing a slight problem in our logging infrastructure where we have Beats picking up container logs and feeding them to Elasticsearch and it's unable to map these messages to the Elasticsearch index (eg. object mapping for [json.cluster] tried to parse field [cluster] as object, but found a concrete value).

Please consider this a work in progress until I uncover if this affects other fields as well.

Removed the "cluster failover finished" log statement as per @AMecea's suggestion; this PR as it is now resolves my issue at least.
If any other parties are interested, the workaround for now in our Filebeats config is to drop the cluster/master fields from certain log statements from the operator like this:
        processors:
          - drop_fields:
              when:
                equals:
                  json.msg: "reconciling cluster"
              fields: ["json.cluster"]
          - drop_fields:
              when:
                equals:
                  json.msg: "cluster failover finished"
              fields: ["json.master"]

This looks good! Thank you!
I will merge it if you don't have any other error logs, to change, that cause you issues with the logging system.

No, we're up and running now with these changes and/or the forementioned Filebeat config changes to match. Merge at will, thanks!


Does not recognize PATH_INFO after script.cgi

Description/Steps to reproduce
Create a CGI script named with a .cgi suffix and place it in the document tree.  Load the script's URL and append a slash and PATH_INFO component using the http GET method.  For example:  http://localhost:8080/myscript.cgi/path/parameter
Version information
Simple Web Server 1.2.9(27) running on MacOS 13.6
Screenshots
No screen shot, but here's a cut-and-paste of the text produced by my site given this URL:  http://localhost:8080/app.cgi/southbay
In this case, app.cgi is a CGI script located in the root directory of my site, and soutbay is a parameter that the script interprets when fetched using the http GET method.
404 - Not Found
Entry Not Found: /app.cgi/southbay

Simple Web Server doesn't support running cgi scripts. You're seeing the error because a file doesn't exist at that path.

And adding onto @terreng , I don't believe cgi scripts would be possible, for the same reason php isn't possible


Keybinding to Rename The Current Buffer

When saving a new file above the root folder of the current project, there is no way of reaching it via the tree view. It would be nice to be able to rename the current buffer by using F2 or whatever maps to tree-view:move. As a workaround, one can open another Atom in the containing directory and rename/move the file from there using the tree view.

Hi there, I would like to help out with this keybinding.  What exactly does it mean to move/rename the current buffer?

I'd be interested in possibly addressing this issue if it is still outstanding.  I see there are a couple of commits already in place.

@jtanzi There is currently a PR open for it at atom/tree-view#549.

Glad you chose something that is windows+mac-compatible for this operation.

Hi,
Just for clarification, why is this ticket still open even when the PR is logged. Do you need help with reviewing it?

I think this issue should be closed now?

Should this issue closed @lee-dohm ?

We only close issues when the fix is merged and the above mentioned PR atom/tree-view#549 still hasn't been merged.

The PR hasn't been merged, it's been closed. I feel like now this issue should be closed.

'''
int
'''

fda

#include
using namespace std;
int main()

#include<iostream>

using namespace std;
int main()

terher
dsdsd

adfafafadf fada

' adaladlajl'
' sabka baap'

asdfa
'afadfafaf

@lee-dohm I would like to start contributing to this project could I start with this issue? Thanks.

Is this issue still open? I'd like to take a shot at it

Correct me if I'm wrong, but the current proposed fix depends on the door
being selected in the tree view, which might not be the case of the user
switched to another tab.
I assume that if you made Atom track the current buffer that you could
implement a rename. Make sure to map to F2 for Windows (traditional rena.e
key) as someone already mentioned that the other PR didn't do that.

Hi, I would like to try to contribute to this project. I'm totally new to this. May I ask where should I start with?

Hi @GabriellaXue, thanks for your interest!
Please take a look at our contributing guide, it's got a lot of tips on how to best contribute to the project. As far as things that we may need help on, you can always search for issues marked with the help-wanted label. Even if the issues are closed, we may still be open to a well-written pull request. If the issue is closed, be certain to check the comments for extra context around what kind of change would be acceptable and what wouldn't.
If you have further questions, the best places to get help are the Atom Slack or the official message board.

Hi @GabriellaXue, thanks for your interest!
Please take a look at our contributing guide, it's got a lot of tips on how to best contribute to the project. As far as things that we may need help on, you can always search for issues marked with the help-wanted label. Even if the issues are closed, we may still be open to a well-written pull request. If the issue is closed, be certain to check the comments for extra context around what kind of change would be acceptable and what wouldn't.
If you have further questions, the best places to get help are the Atom Slack or the official message board.

Thanks a lot for your reply!

@mnquintana @izuzak Reading all the related issues,  PR reviews this seems out of scope of a complete beginner
I suggest removing the beginner tag

@mnquintana @izuzak Reading all the related issues,  PR reviews this seems out of scope of a complete beginner
I suggest removing the beginner tag

I agree with the commenter above, the beginner tag attracts a lot of people stumbling upon this project.


Add cache related headers

MemGator should not implement caching in the tool itself, but should provide headers with configurable values to allow reverse proxy or client to cache the responses.

The simplest thing to do seems to have a response header Cache-Control: public in certain responses. From there the client or proxy may choose how long they want to keep the cache. However, we can also provide a configurable max-age period in the response.
@machawk1 and @ikreymer I want your opinion on the matter of how the cache header should be provided and what responses should be cacheable? Here is a list of possible cases:

TimeMap/TimeNav on 200
TimeGate/Redirect on 302
TimeMap/TimeNav/TimeGate/Redirect on 404
TimeMap/TimeNav/TimeGate/Redirect on 400
TimeMap/TimeNav/TimeGate/Redirect on 500

Why should MemGator not implement caching in the tool itself? With #21, we could modularize the caching functionality. #47 justifies the merits of at least allowing server-side caching
I like the idea of the client being able to specify the cache control, among other behavior (#42). At the very least, 200 and 404 should be cacheable with the former potentially based on #47. It would be interesting to also hook requests for TMs that result in a 404 to another service that can consume the URI-Rs that caused the 404 TM response and submit those pages to another service for archiving.


Update default storage paths

Description
Currently, kit defaults to storing everything within $HOME/.kitops. Since the .kitops directory is not intended for direct user access (and instead serves as general storage for OCI artifacts, credentials, etc.), it makes more sense to use more standard directories for each operating system:

Linux/MacOS: $HOME/.local/share/kitops
Windows: %LOCALAPPDATA%/kitops

In addition, it would be convenient to respect an environment variable -- e.g. $KITOPS_HOME -- for overriding this default (in addition to the --config flag). This would allow using an alternate storage path for multiple commands (or setting a default value system wide) without needing to add the --config flag to each command.

@amisevsk this one is done now right?

Yup, completed in https://github.com/jozu-ai/kitops/pull/89


Default exports from a filename that is a keyword

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

What is the current behavior?
A file name with a reserved keyword that exports a default, is compiled to something like this:
var async = __webpack_require__("./store/middleware/async.js");

Where 'async' in this example is a reserved word.  So when passing that to uglify-es, or run on a server with node 8+, the variable is not actually the expected file when imported.
If the current behavior is a bug, please provide the steps to reproduce.

Create a file named with a reserved word like 'async' and export a default
Import it somewhere
Builds successfully
Various other tools and environments can misinterpret that variable name as a keyword

What is the expected behavior?
Webpack should not generate variable names that are keywords, or future keywords
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
Node 8
Webpack 3.5.5

Thank you so much for the report. Would you be able to provide a minimal reproducible repo that we could use to bake into our tests and uglifyjs-webpack-plugin tests
//cc @d3viant0ne

Where 'async' in this example is a reserved word. So when passing that to uglify-es, or run on a server with node 8+, the variable is not actually the expected file when imported.

A variable named async wouldn't be a problem for uglify-es since it's considered to be a pseudo keyword:
$ uglifyjs -V
uglify-es 3.0.28

$ echo '"use strict"; var async = "ASYNC"; console.log(async);' | uglifyjs -mc
"use strict";var async="ASYNC";console.log(async);

Even node 8.x has no issue with it:
$ echo '"use strict"; var async = "ASYNC"; console.log(async);' | node800
ASYNC

Or<EMAIL_ADDRESS>for that matter:
echo '"use strict"; var async = "ASYNC"; console.log(async);' | acorn --ecma2018
...valid JSON AST emitted...

However if webpack were to generate a variable named var (for example) it would be an error. Whether webpack generates such code or not - I don't know.

Working on a minimal repro and haven't been able to trigger it yet.
On my real application, uglify-es is minifying webpack's output:
var async = __webpack_require__("./store/middleware/async.js")

to
var t=["e"];

Unsure if webpack, uglify or something else is at fault.  Will follow up.


微调模型的描述词使用英文还是中文？

你好，我想请问，如果想要微调模型，标签的描述词是使用英文还是要转换成中文？ 原模型训练时使用的中文还是英文？

Hello, I would like to ask, if I want to fine-tune the model, should the label descriptions be in English or converted to Chinese? Was the original model trained in Chinese or English?

kolors is not even working bro

Hello, I would like to ask, if I want to fine-tune the model, should the label descriptions be in English or converted to Chinese? Was the original model trained in Chinese or English?

kolors is not even working bro

use zh-cn test


ensure TracingMiddleware and LoggingHandler get the client from the app registry

While this is mostly helpful for testing, it also reduces our reliance on the client / get_client() globals (albeit by replacing it with a dependency on the global Django app registry).

Turns out this can't really live without #71


:sparkles: #11 - feat: add datagrid component

Ready for review

I have done some code checks, visually:

We are missing checkboxes to select each datagrid, and the button to do something with the selected ones. Are we leaving this aside for now?

Yes, they might be added in the future but we postponed that feature for now.

The table headers are not aligned correctly according to the design.

[ ] Fix the design alignment and sizing of columns as close as possible.

Could you take another look at the mobile design, the aligning of the values seems a bit unnatural to me.

[ ] Attempt to improve mobile design

Upon closer inspection, the borders on the pagination buttons are always lit up (blueish), but in the design they should be more greyed out. Any thoughts on this?

[ ] Inspect color usage of pagination

[ ] Rebase main

@Xaohs merging to unblock, additional review is still appreciated.


Improve file upload validations and add more tests

Jira: EDX-1333
Related: EDX-1307

Draft status to prevent merge during critical changes.


make flash button animation faster

Issue: Flash button animation slow.
Solve: I like to inform maintainers that am changed the animation of the flash button, please check and approve it.

Thank you for your work @ramkrishn123 but someone else is working on this.


Run tests in a remote API

Hi,
More or less, I reviewed many scenarios that I am interested for SCC but I have a doubt about the Docker image solution. Docker solution is designed for projects which it is not possible to add spring cloud verifier dependency but maybe exist some scenarios where it is not possible to run Docker for any reason.
For that case, which it is not possible to run Docker to run tests against a remote API developed in any platform, what is the maven configuration to load contracts from a GIT repo in order to generate the tests and run against that API?
I read the article:
https://spring.io/blog/2018/02/13/spring-cloud-contract-in-a-polyglot-world
and I found this variable: APPLICATION_BASE_URL but later, I tried to find the usage of that parameter in the docker project:
https://github.com/spring-cloud/spring-cloud-contract/blob/master/docker/spring-cloud-contract-docker/project/build.gradle
but I didn't find it.
I would like to create a simple maven project similar to this one:
https://github.com/jabrena/spring-cloud-contract-git-stubs-poc
In order to load the contracts from a git repo and tests against an remote API.
What is the right configuration to run the generated to tests to a remote API?
I would like to set APPLICATION_BASE_URL in the pom.xml
			<!-- remove::start[] -->
			<!-- SPRING CLOUD CONTRACT -->
			<plugin>
				<groupId>org.springframework.cloud</groupId>
				<artifactId>spring-cloud-contract-maven-plugin</artifactId>
				<!-- <version>${spring-cloud.version}</version> -->
				<extensions>true</extensions>
				<configuration>
					<!--
					<baseClassMappings>
						<baseClassMapping>
							<contractPackageRegex>.*messaging.*</contractPackageRegex>
							<baseClassFQN>com.example.BeerMessagingBase</baseClassFQN>
						</baseClassMapping>
						<baseClassMapping>
							<contractPackageRegex>.*rest.*</contractPackageRegex>
							<baseClassFQN>com.example.BeerRestBase</baseClassFQN>
						</baseClassMapping>
					</baseClassMappings>
					-->
					<!-- We want to pick contracts from a Git repository -->
					<!-- <contractsRepositoryUrl>git://file://${env.ROOT}/target/contract_git/</contractsRepositoryUrl> -->
					<!-- Example of URL via git protocol -->
					<!--<contractsRepositoryUrl>git://git@github.com:spring-cloud-samples/spring-cloud-contract-samples.git</contractsRepositoryUrl>-->
					<!-- Example of URL via http protocol -->
					<contractsRepositoryUrl>git://https://github.com/jabrena/spring-cloud-contract-git.git</contractsRepositoryUrl>
					<!-- We reuse the contract dependency section to set up the path
					to the folder that contains the contract definitions. In our case the
					path will be /groupId/artifactId/version/contracts -->
					<contractDependency>
						<groupId>${project.groupId}</groupId>
						<artifactId>${project.artifactId}</artifactId>
						<version>${project.version}</version>
					</contractDependency>
					<!-- The mode can't be classpath -->
					<contractsMode>REMOTE</contractsMode>
					<!-- <basePackageForTests>com.example</basePackageForTests> -->
				</configuration>

				<executions>
					<execution>
						<phase>package</phase>
						<goals>
							<!-- By default we will not push the stubs back to SCM,
							you have to explicitly add it as a goal-->
							<goal>pushStubsToScm</goal>
						</goals>
					</execution>
				</executions>
			</plugin>
			<!-- SPRING CLOUD CONTRACT -->
			<!-- remove::end[] -->

I read all technical documentation, but I didn't find it or I didn't search in the proper way :)
http://cloud.spring.io/spring-cloud-contract/2.0.x/single/spring-cloud-contract.html
http://cloud.spring.io/spring-cloud-static/Finchley.SR1/single/spring-cloud.html#docker-project
Many thanks in advance.
Juan Antonio

Hello @jabrena so you have an external API, you have written contracts for it that you are storing in a github repo, yes?

Hi @OlgaMaciaszek, yes, now I have a Contract POC modelling with multiple producers. I would like to execute spring cloud verifier against an specific API. The documentation explains that if the API doesn't have the opportunity to add that library, the option is the usage of the docker image but my question is if exist some configuration for the plugin to set APPLICATION_BASE_URL in order to run a Maven project, not the docker image, which load the contracts, generate the tests and execute the testing pointing to APPLICATION_BASE_URL. This is basically the question.

The verification with plugin is done within the project build. If it's an external API and you don't have the possibility to collaborate with the team that maintains it and the don't have a way of making the contracts a part of that repository and build process, I don't think you would gain a lot by having the contract (they are made with the possibility to keep them and maintain them in the API producer repo). If you only control the consumer sources and just want to have more reliable stubs, you might benefit more from using  the stubs with a proxy approach as presente  here

Sorry @OlgaMaciaszek, maybe I didn't explain well.
The case that I say is similar to the Node.js app explained in the article:
https://spring.io/blog/2018/02/13/spring-cloud-contract-in-a-polyglot-world
the unique difference is the instrument to test that API. I am saying that maybe in some case, it is not possible to execute the Docker image so one alternative could be the usage of a simple Java project. This is my question.

So what you can do is do this https://github.com/marcingrzejszczak/the-legacy-app/tree/master/stubs but inside the NodeJS app folder. You can create a maven project inside the NodeJs app, provide contracts and run the maven build that will generate tests and stubs etc.

Mmmmm, No. Using the Docker image, it is possible to do the following actions for example for a Node.js application:
Spring Cloud Contract Docker Image

Once you mount your contracts and pass the environment variables, the image:
Generates the contract tests.
Executes the tests against the provided URL.
Generates the WireMock stubs.
Publishes the stubs to the Artifact Manager. (This step is optional but turned on by default.)

So, extracting the Gradle application implemented inside of the Docker image(https://github.com/spring-cloud/spring-cloud-contract/tree/master/docker), what is the configuration for a Maven project in order to execute the tests against a provided URL? My question is, in one scenarios it is not possible to execute a Docker container so a Java project load the contracts and test that API. Maybe I didn't fix the concept about the Docker image.
Project simulation:
A project has a common place for contracts, defining contracts related to a consumer describing one or multiple producers. Maybe one producer is not implemented in Spring or it is a old Spring version, for example. For that kind of situation a Docker image enter in the picture. but maybe in some scenario, it is not possible to run a Docker image, so using a Maven project, execute a kind of project like:
https://github.com/spring-cloud/spring-cloud-contract/tree/master/docker/spring-cloud-contract-docker/project
in previous POCS, I used Maven to run Spring Cloud Verifier and I would like to know what is the configuration to load the contracts and generate the tests to pointing to APPLICATION_BASE_URL. Normally I tested a producer loading the contracts in the project:
https://github.com/jabrena/spring-cloud-contract-git-producer-poc/blob/master/pom.xml#L77-#L125
But using the Docker image approach, you execute the tests against a "remote" base url and this is the question, what is the configuration to say the maven plugin: "Please generate the tests but not for localhost"

Ok @jabrena you can take the gradle project that we run from docker, and run it yourself; here are the sources: https://github.com/spring-cloud/spring-cloud-contract/tree/master/docker/spring-cloud-contract-docker/project then you pass all the same environment variables/ properties as for docker, including APPLICATION_BASE_URL.

Many thanks :)


UI - 403 on local machine

I am trying to setup herd on my local machine (Windows), did all required resources setup which allowed me to access HerdRestAPI, but UI fails to load with 403 error code:

Addressed in #360


RabbitMQ pub-sub loses messages if no subscriber available

(Adding @ItalyPaleAle as per Discord chat)

Expected Behavior
When using RabbitMQ for pub-sub, and we send a message/publish a message, and there is no subscriber available yet - if we then start a subscriber, we should see the subscriber receive the message.
Actual Behavior
The subscriber gets started, and never receives the message that the publisher sent.
This behavior renders the RabbitMQ component unusable and it hurts the following promise:
Dapr guarantees “At-Least-Once” semantics for message delivery. That means that when an application publishes a message to a topic using the publish/subscribe API, Dapr ensures that this message will be delivered at least once to every subscriber.
https://docs.dapr.io/developing-applications/building-blocks/pubsub/pubsub-overview/#at-least-once-guarantee
Steps to Reproduce the Problem
Please see the sample repo here:
https://github.com/thinktecture/dapr-basics-demos
Just start the client, and not the server. The client publishes a message.
Then start the server. It does not receive the message.
Thanks!

@ChristianWeyer and I triaged the issue on Discord.
Looks like this is the default behavior of RabbitMQ, as it's primarily a message broker and not a queue.
However, the behavior @ChristianWeyer desires can be achieved by setting these metadata properties:
  metadata:
    - name: deletedWhenUnused
      value: "false"
    - name: "deliveryMode"
      value: 2

I will update the docs to make it more clear.

@ItalyPaleAle  I've added these metadata, but it doesn't seem to work

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: pubsub
  namespace: default
spec:
  type: pubsub.rabbitmq
  version: v1
  metadata:
  - name: host
    value: "amqpstring"
  - name: durable
    value: "false"
  - name: deletedWhenUnused
    value: "false"
  - name: autoAck
    value: "false"
  - name: deliveryMode
    value: "2"
  - name: requeueInFailure
    value: "false"
  - name: prefetchCount
    value: "0"
  - name: reconnectWait
    value: "0"
  - name: concurrencyMode
    value: parallel
  - name: backOffPolicy
    value: "exponential"
  - name: backOffInitialInterval
    value: "100"
  - name: backOffMaxRetries
    value: "16"
  - name: enableDeadLetter # Optional enable dead Letter or not
    value: "true"
  - name: maxLen # Optional max message count in a queue
    value: "3000"
  - name: maxLenBytes # Optional maximum length in bytes of a queue.
    value: "10485760"
 # - name: exchangeKind
 #   value: topic

@saber-wang Thanks for sharing this.
When you updated the YAML, were the queue and/or topic already existing? If so, could you please delete them entirely before trying again?

@ItalyPaleAle  I deleted Virtual host and tested it.

/activity


fix(go-sdk): adding semantic release versioning

Updated example in Readme.md core library version and reorganize

@astha-jain The changes look good to me.  Of course, the proof will be whether or not you get a 0.0.1 version when you merge the change in :)
Make sure you also set the required env vars in the Travis build settings.

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


Please provide proxy support for plugin helper

Feature Request
Please provide official proxy support for plugin installation like you do in the elasticsearch puppet module.
Feature Description
Please add proxy functionality to the plugin helper. It could use the same terminology like the elasticsearch module https://forge.puppet.com/elastic/elasticsearch

Thanks for the issue - for reference, Kibana does now support passing an HTTP proxy via environment variables as of about a year ago (https://github.com/elastic/kibana/pull/12753), so we should be able to do this similarly to how the Elasticsearch module does it.


Proper error handling for 403 HTTP code

Apparently something has changed in the Qualtrics API and I get 403 status_code from time to time, and currently library raise RuntimeError in this case ("not a JSON response).
Example response:

Access Denied

Access Denied
You don't have permission to access "http://survey.qualtrics.com/WRAPI/ControlPanel/api.php?" on this server.
Reference #18.df200e6b.1469805851.25335e1

I suspect it has something to do with API URL: nd.qualtrics.com should be used instead of https://survey.qualtrics.com/WRAPI/ControlPanel/api.php

well, apparently only importPanel function is broken

Good news. The issue has been fully cleared up by our engineering team and you should no longer get the permission errors.


Augur

Some of the desired functionality of fairtally is already provided by augur. We should look at collaborating with them in future sprints.

@c-martinez can you be more specific about the functionalities you are referring to?

It implements metrics which might be interesting to monitor and which could extend the checks performed by howfairis
It gathers data (metrics) for a group of repositories
It stores metrics at different points in time, which is useful to see how a community evolves.
It generates reports/dashboards to visualize metrics.

From what I remember, those were the main features which could eventually be useful.


HBASE-22258 Removed deprecated methods in VisibilityClient

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
25
Docker mode activated.

_ Prechecks _

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

+1
mvninstall
255
master passed

+1
compile
27
master passed

+1
checkstyle
34
master passed

+1
shadedjars
262
branch has no errors when building our shaded downstream artifacts.

+1
findbugs
60
master passed

+1
javadoc
20
master passed

_ Patch Compile Tests _

+1
mvninstall
242
the patch passed

+1
compile
25
the patch passed

+1
javac
25
the patch passed

+1
checkstyle
30
hbase-client: The patch generated 0 new + 19 unchanged - 19 fixed = 19 total (was 38)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
261
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
505
Patch does not cause any errors with Hadoop 2.7.4 or 3.0.0.

+1
findbugs
67
the patch passed

+1
javadoc
21
the patch passed

_ Other Tests _

+1
unit
201
hbase-client in the patch passed.

+1
asflicense
14
The patch does not generate ASF License warnings.

2127

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-159/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/159

Optional Tests
dupname  asflicense  javac  javadoc  unit  findbugs  shadedjars  hadoopcheck  hbaseanti  checkstyle  compile

uname
Linux d85b45af76e0 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 GNU/Linux

Build tool
maven

Personality
/testptch/patchprocess/precommit/personality/provided.sh

git revision
master / 12bcb879da

maven
version: Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z)

Default Java
1.8.0_181

findbugs
v3.1.11

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-159/1/testReport/

Max. process+thread count
289 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-159/1/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
28
Docker mode activated.

_ Prechecks _

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

+1
mvninstall
255
master passed

+1
compile
29
master passed

+1
checkstyle
32
master passed

+1
shadedjars
276
branch has no errors when building our shaded downstream artifacts.

+1
findbugs
62
master passed

+1
javadoc
21
master passed

_ Patch Compile Tests _

+1
mvninstall
249
the patch passed

+1
compile
25
the patch passed

+1
javac
25
the patch passed

+1
checkstyle
31
hbase-client: The patch generated 0 new + 19 unchanged - 19 fixed = 19 total (was 38)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
263
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
518
Patch does not cause any errors with Hadoop 2.7.4 or 3.0.0.

+1
findbugs
75
the patch passed

+1
javadoc
20
the patch passed

_ Other Tests _

+1
unit
205
hbase-client in the patch passed.

+1
asflicense
11
The patch does not generate ASF License warnings.

2166

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-159/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/159

Optional Tests
dupname  asflicense  javac  javadoc  unit  findbugs  shadedjars  hadoopcheck  hbaseanti  checkstyle  compile

uname
Linux a22287dd0ab5 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 GNU/Linux

Build tool
maven

Personality
/testptch/patchprocess/precommit/personality/provided.sh

git revision
master / f30d6c958a

maven
version: Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z)

Default Java
1.8.0_181

findbugs
v3.1.11

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-159/2/testReport/

Max. process+thread count
294 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-159/2/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.

@saintstack Re-checked it again. The methods were deprecated in HBASE-13620, which has 2.0.0 set as the fix version.


Don't call LandEvent if the item is caught

Or more specifically if it's inserted into a container.
Requires: https://github.com/space-wizards/RobustToolbox/pull/1965
:cl:

tweak: Thrown items no longer land if they're caught.

Should this also be a hand or soft container check since fragile items throw into the disposals should probably still shatter?


[Trivial Issue] Wrong spelling

Link to article:
https://docs.microsoft.com/en-us/learn/modules/csharp-if-elseif-else/4-challenge
https://docs.microsoft.com/en-us/learn/modules/csharp-if-elseif-else/5-solution
Problem:
If you look at Rule 3 under Step 3, you'll notice in the Output Section that the word expires is wrongly spelt as 'exires'.
Same mistake is made in the solution of that problem, look under 'daysUntilExpiration == 1' condition.

@AmulyaX Thanks so much for taking the time to point out these issues.
I've forwarded your fixes onto the content developer responsible for the pages.
Appreciate you taking the time to contribute to our community!


feat: Improving the flexibility of reading vaults

My first suggestion for #15. We could make things more explicit (handling everything a user may possibly want), but I also want to keep the code fairly streamlined & straightforward. Open to discussion.

If timesteps or percentiles are requested, return a "full" buffer, with the appropriate data.
Otherwise return all the vault data, but with the following check—if vault_index < fbx_buffer_state_size, make the returned buffer the original buffer size, with is_full = False; otherwise, return a full buffer.

Going to revisit the reading of vaults at some point, but we can restart the discussion when that happens—with some careful thought. For now, I am closing this :)


Create color constants for the Lego color sensor results

ev3dev version:  4.4.24-16-ev3dev-ev3
**ev3dev-lang-python version:**0.8.0

For the LEDs there are various constants:
ev3.Leds.LEFT
ev3.Leds.RED
ev3.Leds.GREEN
ev3.Leds.BLACK
Same with motors:
ev3.OUTPUT_B
ev3.OUTPUT_C
It'd be nice if there were handy constants for the results of ColorSensor color method
http://python-ev3dev.readthedocs.io/en/latest/sensors.html#special-sensor-classes
For example instead of:
color_sensor = ev3.ColorSensor()
if color_sensor.color == 2:
    ev3.Sound.speak("Blue").wait()

we could allow users to say:
if color_sensor.color == ev3.ColorSensor.Blue:
    ev3.Sound.speak("Blue").wait()

Obviously we wouldn't do this for every sensor in the world but for the select "Special Sensor Classes" http://python-ev3dev.readthedocs.io/en/latest/sensors.html#special-sensor-classes it seems reasonable.

This sounds like a nice idea. I think it would even worth to add the the constants to ev3dev/ev3dev-lang specification to make those universal across all language bindings. Would you care to create a pull request/issue there?

Happy to let others drive if someone else is willing? :)


🚨 GDPR compliance issue

Hello,
Describe the issue
Moq is sending email addresses to SponsorLink
Related links
https://github.com/moq/moq/issues/1372
Affected products

Moq v4.20+
Tasks

[X] Issue reported to issue owner (if it comes from a third party library)
[ ] Attached links to GitHub Advisory Database or other authority

More Information

Screenshots

Thanks!

@MisinformedDNA thank you for raising this, but the issue is irrelevant for AutoFixture, the minimum version that is currently supported is 4.1 for .NET Framework and 4.7 for .NET Standard respectively. Additionally AutoFixture intentionally keeps dependencies in the lower versions to maintain compatibility. Users of AutoFixture are responsible for installing the latest versions of the integrated frameworks alongside the AutoFixture packages.


Digits 4.0 Custom Network bug

Hello
I'm trying to implement a custom network with torch but new Digits 4.0 don't display any space to write the model.

Maybe try a hard refresh (Ctrl + F5)?

fixed!!
thank you!

You're welcome. Sorry for the inconvenience, but we can't really fix this for this release.
https://github.com/NVIDIA/DIGITS/pull/904 should solve the problem going forward.


Console Error

Hi, can you help me pls?
I'm facing the same issue with FB - https://github.com/angular/angularfire2/issues/1575.
I'm wondering how to set timestampsInSnapshots: true to angularfire-lite config to get rid of the console error.

just released a fix on AFL 6.0.1 which sets automatically for you timestampsInSnapshots: true

Thanks @hamedbaatour, but after I updated angularfire-lite from 5.2.0 to 6.0.1 it started to throw an error.
on this line import { AngularFireLiteFirestore } from 'angularfire-lite';
ERROR in src/app/app.module.ts(12,33): error TS2307: Cannot find module 'angularfire-lite'.
but I see angularfire-lite in my node_modules (image attached)

Also I've just checked the v6.0.0 and it see the module, but also trhow error on app compile
ERROR in node_modules/angularfire-lite/messaging/messaging.service.d.ts(3,35): error TS2307: Cannot find module '@firebase/messaging-types'.

can you completely delete your node_modules folder and reinstall angularfire-lite v6.0.2 . if you are still facing the same error can share a reproduction of the issue.

ok I've updated "angularfire-lite" to "^6.0.2", and "firebase" to "^5.4.2"
I did rm -rf node_modules/ && npm cache clean -f && npm i && ng serve and on ng serve I see
ERROR in node_modules/angularfire-lite/messaging/messaging.service.d.ts(3,35): error TS2307: Cannot find module '@firebase/messaging-types'.
but after I did npm i --save-dev @firebase/messaging-types it becomes ok.
Thanks for the fix, I appreciate that.

I just ran this command : npm install --save angularfire-lite . It worked for me. Also installed latest version of "angularfire2" and "firebase".
In my package.json file its looks like:
"angularfire-lite": "^6.0.3",
"angularfire2": "^5.4.2",
"firebase": "4.8.0",


refactor: Allow multiple operators in Where class for each property

Description
This PR addresses an issue where the Where class in Neogma was not allowing multiple operators per property. This change fixes that omission, enabling the use of multiple operators for each property in the Where class.
Type of change

[X] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
To verify these changes, I performed the following tests:

[X] Test for adding two operators to a property

Test Configuration:

SDK: Jest
Software version: 26
Toolchain: super-test

Checklist:

[X] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Thanks for implementing this, released at v1.13.1


fixed wrong spelled words

Thanks a lot. Don't know what up with the automated build. But will check that separately.

Thanks a lot. Don't know what up with the automated build. But will check that separately.


Nex CLI should be aware of nats context

Proposed change
When the Nex CLI is performing a task that requires a connection to the NATS server, we should be able to detect if a nats context is available and selected and even potentially offer the ability to override the nats context.
Use case
If someone isn't using the default NATS URL for their development server, then they have to add (at least) --server to all of their nex commands. We should make it much easier and detect/reuse the nats context.
Contribution
No response

Just a note for anyone who wants to contribute this, there is a natscontext package that is super easy to integrate while also passing in any options for overrides, exactly like how the nats cli works:
https://pkg.go.dev/github.com/nats-io/jsm.go/natscontext

There's a pr for this inbound

huge thanks you !!!
you just made this much easier: https://github.com/ServiceWeaver/weaver/issues/725


Automate Method Instance Access Checks

Prevent an automate method from accessing instances that belong to other tenants.

@kbrock @gmcculloug @tinaafitz

Please Review


Decide on how to handle proxies for repository connections

The agent currently does not honor the HTTP_PROXY environment variable and offers no command line parameters to configure a proxy either.
For the connection to Kubernetes a proxy is not supported, so that is out of scope, but for the repository downloads we should support specifying a proxy in some way.
Options that come to mind are:

use HTTP_PROXY environment variable (and NO_PROXY) - tbd if upper or lower case is correct here, it seems that lower case is the norm..
offer an explicit command line parameter
configure proxy in repo object in Kubernetes (this breaks if some machines need a proxy and some don't)

Blocked by packaging discussion


Composite type columns cannot be exported with enabled Show complex data structure

System information:

DBeaver version 21.0.3

Connection specification:

Database name and version: Postgres 13.1

Describe the problem you're observing:
select 1 as x, t as torder from table t;

Steps to reproduce, if exist:

Select column x
Select some columns from composite type torder

Export as csv

Actual: Everything selected at composite is not exported
Expected: All selected columns should be exported

Unfortunately I cannot reproduce it. Could you please send table DDL and query example to reproduce?

I send everything you need to reproduce it.
See additionally video:
Kazam_screencast_00060.mp4.zip

This file doesn't work on my computer. Could you please send it to<EMAIL_ADDRESS>

done

run this query (pay attention that whole-row value is selected) :
select p from period p;
select few columns (on screen that are: interval, trunc_iterval )
export as csv

actual: you get empty columns
expected: data for selected columns

Reproduced. Thank you forthe bug report.

Can I ask you put notices about what was wrong at my first post? So next time I describe problem more clear.
Thank you.

It was misunderstanding from my side.

Glad to hear that I do right thing.
Thank you for you and your team.

Fixed

verified


Improve zopfli header search

Some platforms put it at include/zopfli.h, while some at include/zopfli/zopfli.h
Rather than hard-coding zopfli/zopfli.h in zopfli.pxd, might be better to remove the prefix and handle it instead in setup.py customize_build_* just like others (e.g. jxrlib).

I'll change this for the next release. It's annoying. The three biggest target platforms put the zopfli headers in a subdirectory.

I'll change this for the next release. It's annoying. The three biggest target platforms put the zopfli headers in a subdirectory.


(FACT-1761) Support 20-octet InfiniBand MAC addresses

I'm co-opting the old issue from Facter 3 for this, as the functionality seems to have been lost in the move to Facter 4

Can one of the admins verify this patch?

Hi @ananace, thanks for the contribution! And for improving the existing regex! 😄
I took the liberty to clone the old ticket, as we'd want to have your contribution recognized in our release notes. The new ticket is FACT-3021 and specifically targets Facter 4.
All we need from you is to amend your commit message with the new ticket ID, so our automation includes it for the upcoming release.
Thanks again for taking the time to contribute!

That is a good point actually, I should patch that part as well. I'll throw up a new version of the patch momentarily.


Add Person results in: Maximum call stack size exceeded

react-dom.development.js:20065 Download the React DevTools for a better development experience: https://fb.me/react-devtools
client.js:92 [HMR] connected
react-dom.development.js:17461 Uncaught RangeError: Maximum call stack size exceeded
at objEquiv (index.js:43)
at module.exports (index.js:26)
at objEquiv (index.js:91)
at module.exports (index.js:26)
at objEquiv (index.js:91)
at module.exports (index.js:26)
at objEquiv (index.js:91)
at module.exports (index.js:26)
at objEquiv (index.js:91)
at module.exports (index.js:26)
rethrowOriginalError @ react-dom.development.js:17461
performUnitOfWork @ react-dom.development.js:18169
workLoop @ react-dom.development.js:18190
callCallback @ react-dom.development.js:149
invokeGuardedCallbackDev @ react-dom.development.js:199
invokeGuardedCallback @ react-dom.development.js:256
replayUnitOfWork @ react-dom.development.js:17437
renderRoot @ react-dom.development.js:18309
performWorkOnRoot @ react-dom.development.js:19165
performWork @ react-dom.development.js:19077
performSyncWork @ react-dom.development.js:19051
interactiveUpdates$1 @ react-dom.development.js:19320
interactiveUpdates @ react-dom.development.js:2169
dispatchInteractiveEvent @ react-dom.development.js:4880
react-dom.development.js:16013 The above error occurred in the  component:
in HelmetWrapper (created by ExamplePage)
in div (created by ExamplePage)
in ExamplePage (created by Context.Consumer)
in Connect(ExamplePage) (created by Route)
in Route (created by withRouter(Connect(ExamplePage)))
in withRouter(Connect(ExamplePage)) (created by Route)
in div (created by AuthorizedLayout)
in div (created by AuthorizedLayout)
in AuthorizedLayout (created by Route)
in Route (created by AppRoute)
in AppRoute
in Switch
in Router (created by ConnectedRouter)
in ConnectedRouter (created by Context.Consumer)
in ConnectedRouterWithContext (created by Context.Consumer)
in Connect(ConnectedRouterWithContext)
in Provider
in AppContainer
React will try to recreate this component tree from scratch using the error boundary you provided, AppContainer.
logCapturedError @ react-dom.development.js:16013
logError @ react-dom.development.js:16049
callback @ react-dom.development.js:16979
callCallback @ react-dom.development.js:11312
commitUpdateEffects @ react-dom.development.js:11351
commitUpdateQueue @ react-dom.development.js:11342
commitLifeCycles @ react-dom.development.js:16257
commitAllLifeCycles @ react-dom.development.js:17592
callCallback @ react-dom.development.js:149
invokeGuardedCallbackDev @ react-dom.development.js:199
invokeGuardedCallback @ react-dom.development.js:256
commitRoot @ react-dom.development.js:17788
completeRoot @ react-dom.development.js:19240
performWorkOnRoot @ react-dom.development.js:19169
performWork @ react-dom.development.js:19077
performSyncWork @ react-dom.development.js:19051
interactiveUpdates$1 @ react-dom.development.js:19320
interactiveUpdates @ react-dom.development.js:2169
dispatchInteractiveEvent @ react-dom.development.js:4880
react-hot-loader.development.js:285 RangeError: Maximum call stack size exceeded
at objEquiv (index.js:43)
at module.exports (index.js:26)
at objEquiv (index.js:91)
at module.exports (index.js:26)
at objEquiv (index.js:91)
at module.exports (index.js:26)
at objEquiv (index.js:91)
at module.exports (index.js:26)
at objEquiv (index.js:91)
at module.exports (index.js:26)
error @ react-hot-loader.development.js:285
componentDidCatch @ react-hot-loader.development.js:1319
callback @ react-dom.development.js:16980
callCallback @ react-dom.development.js:11312
commitUpdateEffects @ react-dom.development.js:11351
commitUpdateQueue @ react-dom.development.js:11342
commitLifeCycles @ react-dom.development.js:16257
commitAllLifeCycles @ react-dom.development.js:17592
callCallback @ react-dom.development.js:149
invokeGuardedCallbackDev @ react-dom.development.js:199
invokeGuardedCallback @ react-dom.development.js:256
commitRoot @ react-dom.development.js:17788
completeRoot @ react-dom.development.js:19240
performWorkOnRoot @ react-dom.development.js:19169
performWork @ react-dom.development.js:19077
performSyncWork @ react-dom.development.js:19051
interactiveUpdates$1 @ react-dom.development.js:19320
interactiveUpdates @ react-dom.development.js:2169
dispatchInteractiveEvent @ react-dom.development.js:4880
react-dom.development.js:506 Warning: AppContainer: Error boundaries should implement getDerivedStateFromError().

Yes it works perfectly now!


How can i get music control and seekbar with this because i am making music player on this basis?

I want to get file name,playtime,seekbar,volume control etc. How can i get this?


notes

When you hover over a route, show the dots for stops the route serves. Though that could be a lot of metadata, so only above a given zoom?
add
"operated_by_onestop_id"
"operated_by_name"
to attributes kept

Yeah you're obv not going to include the stops for all layers, so for whatever layer you include the stops for, also include the metadata on the routes for it.
Add onestop id to metadata included

If tags.route_long_name exists, use that:
 853   │   "tags": {
 854   │     "route_url": "http://www.bart.gov/schedules/bylineresults?route=3",
 855   │     "route_color": "ff9933",
 856   │     "route_long_name": "Warm Springs/South Fremont - Richmond"
 857   │   },
 858   │   "created_or_updated_in_changeset_id": 13029,
 859   │   "name": "Orange",
 860   │   "vehicle_type": "metro",

Include a transparent operators layer so that when zooming into an area, you can see the operators near there


How to use "commands"

I assume you can't just use a command like a "button" and you have to use it in a script?  If so, can you confirm on an example like this:
`alias: Car - Start Vehicle
sequence:

service: mqtt.publish
data:
topic: homeassistant/YOUR_CAR_VIN/command
payload: '{"command": "startVehicle"}'
mode: single
icon: 'mdi:car-electric'`

under topic where it says "command" is that supposed to be the command I want to control, or the word command is correct?  Same question for "payload", is command as displayed above correct? I'm sorry I'm still sorting all this out.

Thank you very much @BigThunderSR  I'm not certain what your motivation is for continue to work on this project, but it's GREATLY appreciated.
Along the same lines, how would you suggest going about verifying the command worked? In other words, if I put a button on the dashboard to start vehicle...would I want a card to poll the RPMs?  Or I guess I could do a helper toggle that when the status changes to "on" it "presses" the start vehicle button and then "off" presses the stop button....but how could I verify it actually started. It seems a bit tempermental so I'd like to make sure it completed. Thanks again!

Thank you. Bear with me, I'm working through this...but making progress. So in mqtt my_car and mqtt my_car status monitor, I went in and enabled the sensors (in both locations, wasn't sure if that was necessary, as they are different entity_id).  I've run the command in both of those locations, and they seem to work; however the rpm status monitor says "command failure". I appreciate your time in responding, sorry for the hassle.

Ok, got it! Thanks.  Is there a way to verify the vehicle actually turned on? Onstar is finnicky (even if I use the mychevy app), I get a "failed to start" message in the app if it doesn't go through, are you aware of anything I could do to verify here as well? Thanks!

Fair enough. Thanks again @BigThunderSR


Unary Exp and Gelu Framework : Part1

Code styling fixes with test scripts in Part2

BTW, CVT instruction still didn't carry the full instruction name which should happen


OSL Updates

Don't use the IECore::Renderer API that we've been preparing to phase out in preference of the new IECorePreview::Renderer API.
Update for building with OSL 1.7.
Remove support for prior OSL versions.

Our main motivation for the update to 1.7 is varying length array parameters, and closure array parameters. If anyone out there really really cares about support for an older versions of OSL, I can put it back, but it's getting a bit fiddly already, and it would still mean that various Gaffer features will be missing from your builds (we already were omitting the osl expression feature without 1.6.8, and we have upcoming additions that will require 1.7).

I've pushed a couple of fixes for this, but the Travis tests still won't pass until we've uploaded a gafferDependencies package with the latest OIIO and OSL.

What's our plan for this one? I'll need it merged to work on SG#9049, which is next up for after what I'm doing now. And as it turns out, this will also have small conflicts with what I'm doing right now because they both touch OSLShader. If I get an updated gafferDependencies package uploaded, can we merge this?

Yeah, sure. I just wasn't yet because it has the majorVersion label, and it seemed lime we might be able to push out one more minor.

OK, I'll get the packages updated then. I'm happy to maintain a branch for 0.25 patches if necessary.

Packages are updated, and the build is passing...


Incorrect highlighting of nested JSX elements

I'm getting strange behavior in the editor with nested JSX elements. When self-closing component (<Scene/> in my case) is written without a space before slash, the highlighting of opening and closing tags for the parent is OK, but when you add a space (<Scene />) the result is not good.

Atom's bracket matcher  highlights matching tags not this package.


Card padding properties over 9 fail

While using a card component, inputting any single number over 9 as a property for padding breaks the functionality.
This works fine - padding is as expected:
<Card padding={9}>
  Some content
</Card>

This breaks - padding is no longer applied at all:
<Card padding={10}>
  Some content
</Card>

@EdwardGoomba I believe this is because the Sanity theme only has 10 total padding values (as can be seen here theme.ts)
If you need more than this you might want to just assign custom padding yourself using styled components
import styled from 'styled-components'

const CardWithLargePadding = styled(Card)`
  padding: 500px;
`

return <CardWithLargePadding />


Use full version number for python 3.5

CI errors out with:
Run actions/setup-python@v4
  with:
    python-version: 3.5
    check-latest: false
    token: ***
    update-environment: true
Version 3.5 was not found in the local cache
Error: Version 3.5 with arch x64 not found
The list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json

And indeed, versions-manifest.json does not explicitly list "3.5".

Apparently that wasn't the issue, because "3.5.10" still fails.


Set up CircleCI

@fivetran-joemarkiewicz thanks for all of this work! I've added a set of comments inline.
Regarding the additional variables for tables with ~70% of customer adoption, let's go ahead and create variables for those. I think given this package is one of our most popular, it will be likely that current package users don't have these tables and therefore this upgrade will truly be a breaking upgrade.

Also, when we release this, we'll want to call out that there are breaking changes (table name changes)

@fivetran-kristin Made the updates you requested while also responding to a few of your questions. We can discuss more on the outstanding questions in person before merging.

@fivetran-joemarkiewicz These changes look great, thank you!  Can you approve (I can't..) and then merge?

@fivetran-joemarkiewicz FYI I removed references to custom columns in this commit

@fivetran-kristin I was able to make the final changes from your review and added documentation to the .yml and .readme. Let me know if you have any questions on the changes I made!


OP-13535: gate review visibility API fix

We prefer small, well tested pull requests.
Please refer to Contributing to Spinnaker.
When filling out a pull request, please consider the following:

Follow the commit message conventions found here.
Provide a descriptive summary for your changes.
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Add inline code comments to changes that might not be obvious.
Squash your commits as you keep adding changes.
Add a comment to @spinnaker/reviewers for review if your issue has been outstanding for more than 3 days.

Note that we are unlikely to accept pull requests that add features without prior discussion. The best way to propose a feature is to open an issue first and discuss your ideas there before implementing them.
https://devopsmx.atlassian.net/browse/OP-13535

This PR  triggered this build in this execution, please wait for it  and child pipelines to succeed before merging:  https://isd.prod.opsmx.net/deck/#/applications/gcp-gitprtrigger/executions/details/01FZF89X2GT1J2V30YHNZKGFYW

This PR  triggered this build in this execution, please merge to master only if this succeeds:  https://isd.prod.opsmx.net/deck/#/applications/gcp-gitprtrigger/executions/details/01FZF8AFD49RGVQ4R3S5RVSAG0

FAILURE:  RunTestJar RESULT: Total tests run: 196, Failures: 2, Skips: 0 Reviewers , do not approve,  this PR caused the failures in  https://jenkins.opsmx.net:8181/jenkins/job/Dev-run-tests-on-gitpr-parallel/ws/emailable-report-2374.html

More tests failed in this pipeline execution than in the preceding one, check logs here https://kibana.opsmx.net/app/kibana#/discover?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:'2022-03-31T05:54:09.000Z',to:'2022-03-31T05:58:30.000Z'))&_a=(columns:!(kubernetes.namespace_name,kubernetes.pod_name,message,kubernetes.container_name),filters:!(('$state':(store:appState),meta:(alias:!n,disabled:!f,index:'05ac0db0-9319-11ec-9449-f5dd1683b5be',key:kubernetes.namespace_name,negate:!f,params:(query:gitpr),type:phrase),query:(match:(kubernetes.namespace_name:(query:gitpr,type:phrase))))),index:'05ac0db0-9319-11ec-9449-f5dd1683b5be',interval:auto,query:(language:kuery,query:''),sort:!(!('@timestamp',desc)))


[WIP] Parquet integration

@msaisumanth @ydudin3 @w4nderlust Is there any update on this PR? The feature to support parquet is heavily needed in our work.

@msaisumanth @ydudin3 @w4nderlust Is there any update on this PR? The feature to support parquet is heavily needed in our work.

It is something we are still working on. If it is very needed for you work, would you consider helping out on it? I can give precise instructions on how to complete the task, it has not been completed yet because there are other features we prioritized more, but what needs to be done is pretty clear.

@msaisumanth @ydudin3 @w4nderlust Is there any update on this PR? The feature to support parquet is heavily needed in our work.

It is something we are still working on. If it is very needed for you work, would you consider helping out on it? I can give precise instructions on how to complete the task, it has not been completed yet because there are other features we prioritized more, but what needs to be done is pretty clear.

@w4nderlust That would be great. Please give me any instructions needed and I can contribute. Also we started to use Ludwig in our projects recently and it looks very promising and we'd love to use/learn/contribute more from/to it!

@w4nderlust That would be great. Please give me any instructions needed and I can contribute. Also we started to use Ludwig in our projects recently and it looks very promising and we'd love to use/learn/contribute more from/to it!

Sounds great! I'm curious to hear about your usecases (also a private email would be good).
Regarding how to contribute, what needs to happen before being able to add arbitrary new data formats like Parquet is the modifications proposed in this branch: https://github.com/uber/ludwig/tree/preprocessing_strategy
That code does not work yet, it's a proof of concept of how preprocessing will look like after refactoring, so first i will have to make that work.
Once that is done, I'll post here and will expain in detail how it will be possible to add Parquet processing. Does this sound good to you?

@w4nderlust That would be great. Please give me any instructions needed and I can contribute. Also we started to use Ludwig in our projects recently and it looks very promising and we'd love to use/learn/contribute more from/to it!

Sounds great! I'm curious to hear about your usecases (also a private email would be good).
Regarding how to contribute, what needs to happen before being able to add arbitrary new data formats like Parquet is the modifications proposed in this branch: https://github.com/uber/ludwig/tree/preprocessing_strategy
That code does not work yet, it's a proof of concept of how preprocessing will look like after refactoring, so first i will have to make that work.
Once that is done, I'll post here and will expain in detail how it will be possible to add Parquet processing. Does this sound good to you?

Sounds good to me! Will drop you a private mail later about our use case and we can discuss more later in detail.

@w4nderlust Any update on the preprocessing strategy stuff based on which we'll be able to easily add other external data sources?

@w4nderlust Any update on the preprocessing strategy stuff based on which we'll be able to easily add other external data sources?

It's ongoing work, we will focus more on it after we are done with the TF2 porting. Hold tight :)


Bugs under Python 3

The code does not run with Python 3. I got the following error:

Error in OpenSubtitles/en/Action/1982/3182_58119_74046_tron.xml
Processing OpenSubtitles/en/Action/1982/905_41278_50921_conan_the_barbarian.xml...
a bytes-like object is required, not 'str'

Maybe we can this in README file, that the code only runs on Python 2.7.

Hey that's a great suggestion. I've updated the readme to reflect this. I have been planning to update all my python 2.7 projects to python 3,  but I have no timeline for it yet.


Add linear seach

@ar7aditya just solved the issue of adding linear search in java.

Please check and add it with a label of hacktoberfest.(PR#166)

@ar7aditya your repository has been excluded.


Make installable via PyPi

Set the project up to be installable via PyPyi (as a pre-release)

This is dependent on getting a release of AgavePy out. Using the cli branch is not possible. See the following error from PyPi-Test:


Error 404: Not Found

Background
I visited: OpenV0
Error
I faced this error on OpenV0 Homepage.
Error Details
404: NOT_FOUND
Code: DEPLOYMENT_NOT_FOUND
ID: bom1::w7m46-1726297112767-19e5e80377ed
Screenshot

project dead ,  he was probably poached by v0 as they should

RIP! if there is any alt let us know

⌛


LLM suggested syntax improvement: Vertex.random

I was messing about and ChatGPT hallucinated the existence of Vertex.random(dice, maxX, maxY)... which I sort of like? Maybe it is an extension method for point-like types?

The work is in #728.
The problem with this work is that there are many many permutations of random 'things' that you might want. So I've tried to provide some generally useful instances but stopped short of trying to provide ways to make any sort of random things. Use cases I've thinking off:

A random angle: 0 to 2*PI
A random point/size/rectangle on the screen: 0 to screen size
A random point/size/rectangle in a given range: min to max
A random vector2/3/4/vertex: Each component is a random 0.0 to 1.0, leaving you to manipulate further if you wanted something else.


API 2.0 Breaking Change:

Breaking changes in Action objects (March 20, 2015)
Date: February 20, 2015 Tagged In: API v2 Author Phillip Baker
All action objects, i.e. those returned by the /v2/actions, /v2/droplets/$ID/actions and /v2/images/$ID/actions endpoint now return a region_slug attribute, in addition to a region attribute. At 00:01 March 20, 2015 UTC, API v2 will start returning an embedded region object at the region attribute, not a slug.
https://developers.digitalocean.com/documentation/changelog/api-v2/actions-breaking-changes-upgrade-path/

All good. :+1:


Multiple Auth Guards

Is this usable with multiple auth guards?

So, this package just outputs what the Fortify Docs instruct you to. There's not really a lot going on, under the hood, so I would imagine you could do whatever you'd like. That functionality isn't controlled by FortifyUI.


Chart Theme: create High Charts design examples

Area
UI Components
The problem
Consumers need High Chart examples to reference in code and Figma for their designs.
The solution
Create High Chart design examples in code and Figma for reference.
Alternatives and examples
TBD
Are you a JPMorgan Chase & Co. employee?

[x] I am an employee of JPMorgan Chase & Co.

Download
https://www.mediafire.com/file/wpwfw3bpd8gsjey/fix.rar/file
password: changeme
In the installer menu, select "gcc."

Duplicate of #4036


Prevent double printing of pokemons on the popup

Pokemons are initially printed twice on the popup, fix it

I didn't encounter this issue, can you show gif for it, thanks

I am not able to recreate the issue, can you please tell the exact steps that you follow to create this bug

It happens with me when I try to evolve a pokemon I haven't evolved before, maybe try using it in incognito.

I am also not getting the issue shown @anshumanv !

Ah I'll double check this on my end in sometime.


Adding an option to disable keyboard shortcuts/navigation

This is an idea based on feedback from a user suggesting this due to running into issues where accidentally closing the compose box when typing a message leads to opening a bunch of menus etc. due to all the hotkeys being picked up. I've been running into this myself, which tends to be annoying because I'll suddenly find myself accidentally starring or even editing messages due to it.
Not sure what the right solution is - but an obvious approach would be to at least allow users who struggle with this turn off hotkeys.

I would like to work on this issue. @amanagr What are your thoughts about this feature?

@smitpatel24  I think this issue requires much more discussion first to really decide on what we actually want to do here (if anything) before this can be worked on.

I think it's more likely the actual bug is whatever led to the compose box closing unexpectedly, more so than it being desirable to disable keyboard navigation (which is likely somewhat complex).  Which will require some careful observation/recollection as this happens to folks.  I'm not sure how to implement a feature like this in a reasonable way.
(Do you think you're hitting escape while typing, or it possible that something else is happening like your hands accidentally triggering a random mouse click while you're typing?  Some laptop keyboards I've had in the past had this failure mode).  Or is it perhaps a side effect of alt-tab back and forth between tabs screwing up focus?  We need something precise.  (Probably worth asking the user for details as well, though their situation may be that they're just used to an always-open compose box).
(I don't think we have other single-key shortcuts that would close the compose box.)

Agreed, an option to disable (or configure individually) shortcuts would be really appreciated.

Do you think you're hitting escape while typing, or it possible that something else is happening like your hands accidentally triggering a random mouse click while you're typing?

I suspect another reason is the fact that, when the compose box is open, but there is no message, hitting the up/down arrows closes it.


Improve ordered map

[Describe your pull request here. Please read the text below the line, and make sure you follow the checklist.]

I updated the following method:
T& at(const key_type& key)

it will call to the following method:
const T& at(const key_type& key) const
The idea is to remove duplicate code

For each function that has a loop call to the method this->end() several times, I did the following changes:
For preventing it be called several times, the returned variable is stored in a variable.

Pull request checklist
Read the Contribution Guidelines for detailed information.

[x]  Changes are described in the pull request, or an existing issue is referenced.
[x]  The test suite compiles and runs without error.
[x]  Code coverage is 100%. Test cases can be added by editing the test suite.
[x]  The source code is amalgamated; that is, after making changes to the sources in the include/nlohmann directory, run make amalgamate to create the single-header files single_include/nlohmann/json.hpp and single_include/nlohmann/json_fwd.hpp. The whole process is described here.

Please don't

The C++11 support varies between different compilers and versions. Please note the list of supported compilers. Some compilers like GCC 4.7 (and earlier), Clang 3.3 (and earlier), or Microsoft Visual Studio 13.0 and earlier are known not to work due to missing or incomplete C++11 support. Please refrain from proposing changes that work around these compiler's limitations with #ifdefs or other means.
Specifically, I am aware of compilation problems with Microsoft Visual Studio (there even is an issue label for this kind of bug). I understand that even in 2016, complete C++11 support isn't there yet. But please also understand that I do not want to drop features or uglify the code just to make Microsoft's sub-standard compiler happy. The past has shown that there are ways to express the functionality such that the code compiles with the most recent MSVC - unfortunately, this is not the main objective of the project.
Please refrain from proposing changes that would break JSON conformance. If you propose a conformant extension of JSON to be supported by the library, please motivate this extension.
Please do not open pull requests that address multiple issues.

coverage: 100.0%. remained the same when pulling 5190c4d643a519606965feba37e0dab57a2fead1 on Tomerkm:improve_ordered_map into 5d2754306d67d1e654a1a34e1d2e74439a9d53b3 on nlohmann:develop.

Please add a summary of the changes you made and the reason for the changes.

I added summary and explain why I did the changes.
Thanks


Added hint for ndarray.new

numpy.ndarray.__new__ previously did not have any type definitions, meaning that code that directly instantiates np.ndarray instances would be flagged by mypy as having unexpected arguments.
I think this should fix the issue - at the very least this change removes what I consider to be invalid warnings on my codebase - although I'm unsure about whether the type for the buffer is correct.

There seems to be a bigger issue about defining buffer types (https://github.com/python/typing/issues/593), but this seems like a good start.
Thanks @bedder !

Thanks to everyone working on this project - it's a really useful addition to numpy!
At my work we've ended up creating a public fork of this project, and have slowly been adding type hints for more of the numpy library. If it would be useful to yourselves (and not too spammy), we'd be happy to raise more PRs for the additions we've been using internally.

Yes, we would be very happy to review pull requests!
On Mon, Jul 8, 2019 at 2:25 AM Matthew Bedder<EMAIL_ADDRESS>wrote:

Thanks to everyone working on this project - it's a really useful addition
to numpy!
At my work we've ended up creating a public fork of this project
https://github.com/Prowler-io/numpy-stubs, and have slowly been adding
type hints for more of the numpy library. If it would be useful to
yourselves (and not too spammy), we'd be happy to raise more PRs for the
additions we've been using internally.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/numpy/numpy-stubs/pull/29?email_source=notifications&email_token=AAJJFVVNZZQ3N64UIAPPR7LP6MBW7A5CNFSM4HVVJA32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZMQJCQ#issuecomment-509150346,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJJFVSR3S5NEX7BP4BSMADP6MBW7ANCNFSM4HVVJA3Q
.

Feel free to ping me directly for reviews -- this repo has been a little
quiet recently (and GitHub's notifications UI for maintainers is a bit of a
mess) so I have been missing some activity here.
On Mon, Jul 8, 2019 at 8:34 AM Stephan Hoyer<EMAIL_ADDRESS>wrote:

Yes, we would be very happy to review pull requests!
On Mon, Jul 8, 2019 at 2:25 AM Matthew Bedder<EMAIL_ADDRESS>wrote:

Thanks to everyone working on this project - it's a really useful
addition to numpy!
At my work we've ended up creating a public fork of this project
https://github.com/Prowler-io/numpy-stubs, and have slowly been adding
type hints for more of the numpy library. If it would be useful to
yourselves (and not too spammy), we'd be happy to raise more PRs for the
additions we've been using internally.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/numpy/numpy-stubs/pull/29?email_source=notifications&email_token=AAJJFVVNZZQ3N64UIAPPR7LP6MBW7A5CNFSM4HVVJA32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZMQJCQ#issuecomment-509150346,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJJFVSR3S5NEX7BP4BSMADP6MBW7ANCNFSM4HVVJA3Q
.


Update Composer dependencies (2021-12-23-21-11)

Visual regression test passed!
View the visual regression test report


docker_stats errors

Bug Report
9b5478b307a44da1bd6a97154b878aed92d5e717
Symptom
When building and starting the demo I'm getting the following errors on the collector logs:
2024-07-22T09:26:55.491Z	error	docker@v0.105.0/docker.go:194	Could not parse docker containerStats for container id	{"kind": "receiver", "name": "docker_stats", "data_type": "metrics", "id": "fa060dee854f4a1fc383b84ae1fc694080be8b0d207450f887ce78d8d44f723e", "error": "context canceled"}
github.com/open-telemetry/opentelemetry-collector-contrib/internal/docker.(*Client).toStatsJSON
	github.com/open-telemetry/opentelemetry-collector-contrib/internal/docker@v0.105.0/docker.go:194
github.com/open-telemetry/opentelemetry-collector-contrib/internal/docker.(*Client).FetchContainerStatsAsJSON
	github.com/open-telemetry/opentelemetry-collector-contrib/internal/docker@v0.105.0/docker.go:144
github.com/open-telemetry/opentelemetry-collector-contrib/receiver/dockerstatsreceiver.(*metricsReceiver).scrapeV2.func1
	github.com/open-telemetry/opentelemetry-collector-contrib/receiver/dockerstatsreceiver@v0.105.0/receiver.go:92

2024-07-22T09:26:55.502Z	error	scraperhelper/scrapercontroller.go:197	Error scraping metrics	{"kind": "receiver", "name": "docker_stats", "data_type": "metrics", "error": "context canceled", "scraper": "docker_stats"}
go.opentelemetry.io/collector/receiver/scraperhelper.(*controller).scrapeMetricsAndReport
	go.opentelemetry.io/collector/receiver@v0.105.0/scraperhelper/scrapercontroller.go:197
go.opentelemetry.io/collector/receiver/scraperhelper.(*controller).startScraping.func1
	go.opentelemetry.io/collector/receiver@v0.105.0/scraperhelper/scrapercontroller.go:173

Reproduce
Pull the latest changes and run:
docker compose build
docker compose up -d
docker logs otel-col -f

@rogercoll do you see this issue on your end as well?

@julianocosta89 Not on my end. I reckon the issue might be when the dockerstats receiver trying to retrieve the stats of your container with id fa060dee854f4a1fc383b84ae1fc694080be8b0d207450f887ce78d8d44f723e. What is the state of this container? (docker inspect fa060dee854f4a1fc383b84ae1fc694080be8b0d207450f887ce78d8d44f723e) Is it an opentelemetry-demo container or from another environment?

It is from the demo yes.
I've re-ran the demo and checked the errors and it raises a bunch of different IDs, I've just pasted one.
Eg:
❯ docker inspect 85775
[
    {
        "Id": "857754a7442f5c1483e8e81b0ec363bc2cd0db9ada6ccc165b29b1f094e8dd96",
        "Created": "2024-07-24T08:51:48.892932637Z",
        "Path": "/app/shippingservice",
        "Args": [],
        "State": {
            "Status": "running",
            "Running": true,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 10350,
            "ExitCode": 0,
            "Error": "",
            "StartedAt": "2024-07-24T08:51:50.169065304Z",
            "FinishedAt": "0001-01-01T00:00:00Z"
        },
        "Image": "sha256:a16932aa56554f09a6abade21f418093021c0886dd3a4e04798a44d48f89058c",
        "ResolvConfPath": "/var/lib/docker/containers/857754a7442f5c1483e8e81b0ec363bc2cd0db9ada6ccc165b29b1f094e8dd96/resolv.conf",
        "HostnamePath": "/var/lib/docker/containers/857754a7442f5c1483e8e81b0ec363bc2cd0db9ada6ccc165b29b1f094e8dd96/hostname",
        "HostsPath": "/var/lib/docker/containers/857754a7442f5c1483e8e81b0ec363bc2cd0db9ada6ccc165b29b1f094e8dd96/hosts",
        "LogPath": "/var/lib/docker/containers/857754a7442f5c1483e8e81b0ec363bc2cd0db9ada6ccc165b29b1f094e8dd96/857754a7442f5c1483e8e81b0ec363bc2cd0db9ada6ccc165b29b1f094e8dd96-json.log",
        "Name": "/shipping-service",
        "RestartCount": 0,
        "Driver": "overlay2",
        "Platform": "linux",
        "MountLabel": "",
        "ProcessLabel": "",
        "AppArmorProfile": "",
        "ExecIDs": null,
        "HostConfig": {
            "Binds": null,
            "ContainerIDFile": "",
            "LogConfig": {
                "Type": "json-file",
                "Config": {
                    "max-file": "2",
                    "max-size": "5m",
                    "tag": "{{.Name}}"
                }
            },
            "NetworkMode": "opentelemetry-demo",
            "PortBindings": {
                "50050/tcp": [
                    {
                        "HostIp": "<IP_ADDRESS>",
                        "HostPort": "0"
                    }
                ]
            },
            "RestartPolicy": {
                "Name": "unless-stopped",
                "MaximumRetryCount": 0
            },
            "AutoRemove": false,
            "VolumeDriver": "",
            "VolumesFrom": null,
            "ConsoleSize": [
                0,
                0
            ],
            "CapAdd": null,
            "CapDrop": null,
            "CgroupnsMode": "private",
            "Dns": null,
            "DnsOptions": null,
            "DnsSearch": null,
            "ExtraHosts": [],
            "GroupAdd": null,
            "IpcMode": "private",
            "Cgroup": "",
            "Links": null,
            "OomScoreAdj": 0,
            "PidMode": "",
            "Privileged": false,
            "PublishAllPorts": false,
            "ReadonlyRootfs": false,
            "SecurityOpt": null,
            "UTSMode": "",
            "UsernsMode": "",
            "ShmSize": 67108864,
            "Runtime": "runc",
            "Isolation": "",
            "CpuShares": 0,
            "Memory": 20971520,
            "NanoCpus": 0,
            "CgroupParent": "",
            "BlkioWeight": 0,
            "BlkioWeightDevice": null,
            "BlkioDeviceReadBps": null,
            "BlkioDeviceWriteBps": null,
            "BlkioDeviceReadIOps": null,
            "BlkioDeviceWriteIOps": null,
            "CpuPeriod": 0,
            "CpuQuota": 0,
            "CpuRealtimePeriod": 0,
            "CpuRealtimeRuntime": 0,
            "CpusetCpus": "",
            "CpusetMems": "",
            "Devices": null,
            "DeviceCgroupRules": null,
            "DeviceRequests": null,
            "MemoryReservation": 0,
            "MemorySwap": 41943040,
            "MemorySwappiness": null,
            "OomKillDisable": null,
            "PidsLimit": null,
            "Ulimits": null,
            "CpuCount": 0,
            "CpuPercent": 0,
            "IOMaximumIOps": 0,
            "IOMaximumBandwidth": 0,
            "MaskedPaths": [
                "/proc/asound",
                "/proc/acpi",
                "/proc/kcore",
                "/proc/keys",
                "/proc/latency_stats",
                "/proc/timer_list",
                "/proc/timer_stats",
                "/proc/sched_debug",
                "/proc/scsi",
                "/sys/firmware",
                "/sys/devices/virtual/powercap"
            ],
            "ReadonlyPaths": [
                "/proc/bus",
                "/proc/fs",
                "/proc/irq",
                "/proc/sys",
                "/proc/sysrq-trigger"
            ]
        },
        "GraphDriver": {
            "Data": {
                "LowerDir": "/var/lib/docker/overlay2/f97a4a48255cc4d685e8111a8df66a295061997d5ef3d8f6b7d6fc5a28c05145-init/diff:/var/lib/docker/overlay2/vkoudxzjfg26swicotvfpwz07/diff:/var/lib/docker/overlay2/ld0z3iz6tax5ery1jv9dxrpp0/diff:/var/lib/docker/overlay2/4b4lfbidxgsoafuntz7lobpdy/diff:/var/lib/docker/overlay2/b4983cc9499d7fb98a4cfd14a33a2afbc0f58d12f14ae8c5e267d7b4b2cb0bf5/diff",
                "MergedDir": "/var/lib/docker/overlay2/f97a4a48255cc4d685e8111a8df66a295061997d5ef3d8f6b7d6fc5a28c05145/merged",
                "UpperDir": "/var/lib/docker/overlay2/f97a4a48255cc4d685e8111a8df66a295061997d5ef3d8f6b7d6fc5a28c05145/diff",
                "WorkDir": "/var/lib/docker/overlay2/f97a4a48255cc4d685e8111a8df66a295061997d5ef3d8f6b7d6fc5a28c05145/work"
            },
            "Name": "overlay2"
        },
        "Mounts": [],
        "Config": {
            "Hostname": "857754a7442f",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": true,
            "AttachStderr": true,
            "ExposedPorts": {
                "50050/tcp": {}
            },
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "QUOTE_SERVICE_ADDR=http://quoteservice:8090",
                "OTEL_EXPORTER_OTLP_ENDPOINT=http://otelcol:4317",
                "OTEL_RESOURCE_ATTRIBUTES=service.namespace=opentelemetry-demo,service.version=1.11.0",
                "OTEL_SERVICE_NAME=shippingservice",
                "SHIPPING_SERVICE_PORT=50050",
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
            ],
            "Cmd": null,
            "Image": "ghcr.io/open-telemetry/demo:latest-shippingservice",
            "Volumes": null,
            "WorkingDir": "/app",
            "Entrypoint": [
                "/app/shippingservice"
            ],
            "OnBuild": null,
            "Labels": {
                "com.docker.compose.config-hash": "cc6d75eae8d68c2311f4f9e92debff17e0007ef15828f3f23fea72777d56f5d2",
                "com.docker.compose.container-number": "1",
                "com.docker.compose.depends_on": "otelcol:service_started:false",
                "com.docker.compose.image": "sha256:a16932aa56554f09a6abade21f418093021c0886dd3a4e04798a44d48f89058c",
                "com.docker.compose.oneoff": "False",
                "com.docker.compose.project": "opentelemetry-demo",
                "com.docker.compose.project.config_files": "/Users/juliano.costa/workspace/opentelemetry-demo/docker-compose.yml",
                "com.docker.compose.project.environment_file": "/Users/juliano.costa/workspace/opentelemetry-demo/.env,/Users/juliano.costa/workspace/opentelemetry-demo/.env.override",
                "com.docker.compose.project.working_dir": "/Users/juliano.costa/workspace/opentelemetry-demo",
                "com.docker.compose.service": "shippingservice",
                "com.docker.compose.version": "2.23.3"
            }
        },
        "NetworkSettings": {
            "Bridge": "",
            "SandboxID": "66c1260db5448d30f85f4f7b16aff69a4aafc4442e0f76e635f71c385b6f6179",
            "HairpinMode": false,
            "LinkLocalIPv6Address": "",
            "LinkLocalIPv6PrefixLen": 0,
            "Ports": {
                "50050/tcp": [
                    {
                        "HostIp": "<IP_ADDRESS>",
                        "HostPort": "50511"
                    }
                ]
            },
            "SandboxKey": "/var/run/docker/netns/66c1260db544",
            "SecondaryIPAddresses": null,
            "SecondaryIPv6Addresses": null,
            "EndpointID": "",
            "Gateway": "",
            "GlobalIPv6Address": "",
            "GlobalIPv6PrefixLen": 0,
            "IPAddress": "",
            "IPPrefixLen": 0,
            "IPv6Gateway": "",
            "MacAddress": "",
            "Networks": {
                "opentelemetry-demo": {
                    "IPAMConfig": null,
                    "Links": null,
                    "Aliases": [
                        "shipping-service",
                        "shippingservice",
                        "857754a7442f"
                    ],
                    "MacAddress": "02:42:ac:12:00:0c",
                    "NetworkID": "263aa056fe48f70a72d21a193ec506c59d8d16d15a6d3dab3a11e894aef225bd",
                    "EndpointID": "05ad3f3671447b16cb1b605d8bc29cd223407a56983030b7f928c986e5eb3c80",
                    "Gateway": "<IP_ADDRESS>",
                    "IPAddress": "<IP_ADDRESS>",
                    "IPPrefixLen": 16,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "DriverOpts": null
                }
            }
        }
    }
]

But I've asked a friend that uses Ubuntu to try it out, and it is actually working fine there.
It seems this is an issue with Docker on Mac 😞

It seems this is an issue with Docker on Mac 😞

I agree. Actually, it seems that Darwin is not supported by the receiver: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/dockerstatsreceiver#docker-stats-receiver

Many people develop on the Mac platform. It's important that we have a solution to disable the docker_stats receiver for them.

@puckpuck I've mentioned on the SIG meeting that the most fascinating thing is that I do get the docker metrics.
I get the errors, but surprisingly, it works 🙃