Client v3

-v3

Fixed some debug messages
Set default value for irange/drange
Re-use all the common code
Cache the uri protocol (and startswith() for that)
Decreased the buffers used on irange convertion
Fixed the license

-v2

Added url port in the nodes
Fix problems when encoding/decoding doubles
Remove commit with double_to_str_alloc
Added commit with comments about how to test server's nodes
Re-using more code between the client nodes
Using json boolean types

merged with the fixes. Thank you all involved.


support "load" function

+ load is already supported in 1.0.1

I think you removed this feature on 1.0.2, I double-checked it. The newest version 1.0.2 can't log out the "+load" functions.

BTW. Actually, we don't need to do anything in __sanitizer_cov_trace_pc_guard_init.  Just need to check and set the status in __sanitizer_cov_trace_pc_guard. This is enough. correct me if I'm wrong.


Fix setup info

Description
Fixes examples/demo.py and napari.yml.
Type of change
[Please delete options that are not relevant.]

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

How Has This Been Tested?
Tested locally on my MBP.

Hello @kne42! Thanks for submitting the PR.

In the file examples/demo.py, following                are the PEP8 issues :

Line 42:80: E501 line too long (90 > 79 characters)
Line 56:80: E501 line too long (93 > 79 characters)
Line 58:80: E501 line too long (99 > 79 characters)
Line 77:80: E501 line too long (92 > 79 characters)
Line 88:80: E501 line too long (93 > 79 characters)
Line 90:80: E501 line too long (101 > 79 characters)


[Bug] Wrong name on Noto Sans Japanese

Thank you for font updating! I really appreciate it.
However, I found the following a bug on the Noto Sans Japanese.
Unfortunately the wrong name "Noto Sans Javanese" is added on #206 . "Noto Sans Japanese" is the correct font name.

Of course! The font is correct, it is https://fonts.google.com/noto/specimen/Noto+Sans+Javanese. Noto Sans Japanese will be added. Follow #126 for updates


Glyphs source from v2.5b breaks

This is what I get when I run $ fontmake -g source.glyphs -o ufo -i on a source which has been saved from the latest version of Glyphs.
INFO:fontmake.font_project:Building master UFOs and designspace from Glyphs source
INFO:glyphsLib.parser:Parsing .glyphs file
Traceback (most recent call last):
  File "/usr/local/bin/fontmake", line 11, in <module>
    load_entry_point('fontmake==1.3.0', 'console_scripts', 'fontmake')()
  File "/usr/local/lib/python2.7/site-packages/fontmake/__main__.py", line 183, in main
    project.run_from_glyphs(glyphs_path, **args)
  File "/usr/local/lib/python2.7/site-packages/fontmake/font_project.py", line 376, in run_from_glyphs
    glyphs_path, family_name, mti_source=mti_source)
  File "/usr/local/lib/python2.7/site-packages/fontTools/misc/loggingTools.py", line 372, in wrapper
    return func(*args, **kwds)
  File "/usr/local/lib/python2.7/site-packages/fontmake/font_project.py", line 77, in build_master_ufos
    family_name=family_name)
  File "/usr/local/lib/python2.7/site-packages/glyphsLib/__init__.py", line 81, in build_masters
    propagate_anchors=propagate_anchors)
  File "/usr/local/lib/python2.7/site-packages/glyphsLib/__init__.py", line 55, in load_to_ufos
    font = load(ifile)
  File "/usr/local/lib/python2.7/site-packages/glyphsLib/parser.py", line 228, in load
    return loads(fp.read())
  File "/usr/local/lib/python2.7/site-packages/glyphsLib/parser.py", line 238, in loads
    data = p.parse(s)
  File "/usr/local/lib/python2.7/site-packages/glyphsLib/parser.py", line 51, in parse
    result, i = self._parse(text, 0)
  File "/usr/local/lib/python2.7/site-packages/glyphsLib/parser.py", line 95, in _parse
    return self._parse_dict(text, i)
  File "/usr/local/lib/python2.7/site-packages/glyphsLib/parser.py", line 137, in _parse_dict
    i = self._parse_dict_into_object(res, text, i)
  File "/usr/local/lib/python2.7/site-packages/glyphsLib/parser.py", line 152, in _parse_dict_into_object
    result = self._parse(text, i)
  File "/usr/local/lib/python2.7/site-packages/glyphsLib/parser.py", line 101, in _parse
    return self._parse_list(text, i)
  File "/usr/local/lib/python2.7/site-packages/glyphsLib/parser.py", line 179, in _parse_list
    list_item, i = self._parse(text, i)
  File "/usr/local/lib/python2.7/site-packages/glyphsLib/parser.py", line 95, in _parse
    return self._parse_dict(text, i)
  File "/usr/local/lib/python2.7/site-packages/glyphsLib/parser.py", line 137, in _parse_dict
    i = self._parse_dict_into_object(res, text, i)
  File "/usr/local/lib/python2.7/site-packages/glyphsLib/parser.py", line 152, in _parse_dict_into_object
    result = self._parse(text, i)
  File "/usr/local/lib/python2.7/site-packages/glyphsLib/parser.py", line 101, in _parse
    return self._parse_list(text, i)
  File "/usr/local/lib/python2.7/site-packages/glyphsLib/parser.py", line 179, in _parse_list
    list_item, i = self._parse(text, i)
  File "/usr/local/lib/python2.7/site-packages/glyphsLib/parser.py", line 120, in _parse
    value = self.current_type(value)
TypeError: __init__() takes exactly 1 argument (2 given)

Thanks David. We should make error messages from glyphsLib parser more meaningful to help debugging issues like this.
I’m away from laptop now, i’ll have a look later.
If you could install it in editable mode and put a try: except: around that line with a print(self.current_type, i), we could try to see what is the offending type and where it’s crashing.

Some attribute names have slightly changed in 2.5b, from titlecase to
lowercase I believe. It should be simple to support both.
On Sat, 11 Nov 2017, 10:53 Cosimo Lupo<EMAIL_ADDRESS>wrote:

Thanks David. We should make error messages from glyphsLib parser more
meaningful to help debugging issues like this.
I’m away from laptop now, i’ll have a look later.
If you could install it in editable mode and put a try: except: around
that line with a print(self.current_type, i), we could try to see what is
the offending type and where it’s crashing.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/googlei18n/fontmake/issues/374#issuecomment-343656480,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB1ao5EgIaBFSC-GRLbpGbyzKTbf4Qxmks5s1XyjgaJpZM4QacFW
.

Your commitment is admirable, amazing actually, but I don’t think anyone expects you to work on weekends!

On 11 Nov 2017, at 11:53, Cosimo Lupo<EMAIL_ADDRESS>wrote:
Thanks David. We should make error messages from glyphsLib parser more meaningful to help debugging issues like this.
I’m away from laptop now, i’ll have a look later.
If you could install it in editable mode and put a try: except: around that line with a print(self.current_type, i), we could try to see what is the offending type and where it’s crashing.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/googlei18n/fontmake/issues/374#issuecomment-343656480, or mute the thread https://github.com/notifications/unsubscribe-auth/AAdoYybiaTiuDVUOUlcQhywzEuckO7j4ks5s1XykgaJpZM4QacFW.

Some attribute names have slightly changed in 2.5b, from titlecase to lowercase

Could we please get a list of these? /cc @schriftgestalt

Can you give an example?

Can you give an example?

I haven't checked yet as I don't have the source files. @moyogo suggested something may have changed in the latest beta, leading to the above mentioned crash in glyphsLib parser.

After round-tripping GlyphsUnitTestSans.glyphs in 2.5b 1084 (https://github.com/moyogo/glyphslib/commit/9a07b1d5edfccc0916d37e0a11779687346e9315) I get the same error.

@moyogo could you try to insert print() or a debugger break point import pdb; pdb.set_trace() and get the value of self.current_type?

Perhaps this is the same problem. I'm getting this error when trying one of our Glyphs files while others are made with no errors.
INFO:fontmake.font_project:Building master UFOs and designspace from Glyphs source INFO:glyphsLib.parser:Parsing .glyphs file INFO:glyphsLib:Loading to UFOs Traceback (most recent call last):   File "/usr/local/bin/fontmake", line 11, in <module>     sys.exit(main())   File "/usr/local/lib/python2.7/site-packages/fontmake/__main__.py", line 183, in main     project.run_from_glyphs(glyphs_path, **args)   File "/usr/local/lib/python2.7/site-packages/fontmake/font_project.py", line 376, in run_from_glyphs     glyphs_path, family_name, mti_source=mti_source)   File "/usr/local/lib/python2.7/site-packages/fontTools/misc/loggingTools.py", line 372, in wrapper     return func(*args, **kwds)   File "/usr/local/lib/python2.7/site-packages/fontmake/font_project.py", line 77, in build_master_ufos     family_name=family_name)   File "/usr/local/lib/python2.7/site-packages/glyphsLib/__init__.py", line 81, in build_masters     propagate_anchors=propagate_anchors)   File "/usr/local/lib/python2.7/site-packages/glyphsLib/__init__.py", line 59, in load_to_ufos     propagate_anchors=propagate_anchors)   File "/usr/local/lib/python2.7/site-packages/glyphsLib/builder/__init__.py", line 43, in to_ufos     result = list(builder.masters)   File "/usr/local/lib/python2.7/site-packages/glyphsLib/builder/builders.py", line 133, in masters     self.to_ufo_glyph(ufo_glyph, layer, glyph)   File "/usr/local/lib/python2.7/site-packages/glyphsLib/builder/glyph.py", line 40, in to_ufo_glyph     ufo_glyph.lib[PUBLIC_PREFIX + 'markColor'] = GLYPHS_COLORS[color_index] IndexError: tuple index out of range

@MalcolmWooden Your issue looks like the file came from FontLab with the Glyphs export script. That issue is open here: https://github.com/googlei18n/glyphsLib/issues/116
I've seen that error before and just had to change or remove the colors in the font view in Glyphs. Then fontmake is fine.

Thanks Punchcutter. The file has not been near FontLab but there has been some color changes in the font view glyph cells. I set them all back to "no color" and it now works!!

hey Malcolm! I'm glad you too are using fontmake :)
Zachary is working on a fix for those color tuples https://github.com/googlei18n/glyphsLib/pull/285
back to the point of this issue, did anyone figure out what are these allegedly new or renamed attributes in 2.5b that make the glyphsLib parser crash?

this should be fixed by glyphsLib 2.1.0, please confirm
https://github.com/googlei18n/glyphsLib/releases/tag/v2.1.0

@MrBrezina : is this still an issue?

nope


migrator: handle member variables change to global ones. rdar://41658300

@swift-ci please smoke test

@swift-ci please smoke test

@nathawes thank you for the feedbacks!


Support Plug & Play

https://channel9.msdn.com/Shows/Internet-of-Things-Show/Introduction-to-IoT-Plug-and-Play

We've already shipped the SDK with PnP feature from 1.9.9 version.
If you want to try the PnP feature with DevKit, please use this borad URL to download and install the package.


added tcp to the list of accepted schemes

Currently tcp scheme is not accepted. It is accepted with predis and others. For compatibility with other libraries, I suggest you include it as well.

Thank you for your contribution!
The redis:// URI scheme has been added not too long ago via https://github.com/clue/php-redis-react/pull/60 and the (previously supported) tcp:// scheme has been removed via https://github.com/clue/php-redis-react/pull/61/files#diff-8157a0d28a58887c0293ce14b4b0281fL112.
I'm not sure I follow what the motivation for bringing this back is, so maybe you can elaborate? It's my understanding that the redis[s]:// URI schemes are standardized via https://www.iana.org/assignments/uri-schemes/prov/redis and https://www.iana.org/assignments/uri-schemes/prov/rediss respectively and I would rather see these supported in all Redis client library, no?

@esokullu uniformity (rather than compatibility) is exactly the reason why the redis:// scheme was introduced and standardized, which also makes this is the main reason why libraries should support this scheme and its rules before anything else. Historically other libraries using tcp as a scheme always parsed and interpreted parameters in the URI in their own way because there were no defined and fixed rules, so simply allowing tcp:// doesn't actually mean anything in this context.

I'm closing this for now as it hasn't received any input in a while and I believe this has been answered. Please come back with more details if this problem persists and we can reopen this :+1:
Either way, thank you for looking into this @esokullu!


aes/asm/bsaes-armv7.pl: Replace adrl with add

"adrl" is a pseudo-instruction used to calculate an address relative to PC. It's not recognized by clang resulting in a compilation error. I've stumbled upon it when trying to integrate the bsaes-armv7 assmebly logic into FreeBSD kernel, which uses clang as it's default compiler. Note that this affect the build only if BSAES_ASM_EXTENDED_KEY is defined, which is not the default option in OpenSSL.
The solution here is to replace it with an add instruction. This mimics what has already been done in !BSAES_ASM_EXTENDED_KEY logic. Because of that I've marked this as trivial CLA.

@tom-cosgrove-arm if you approve, please remove approval: review pending and if there was already OTC approval, please add approval: done.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Merged, thanks for the contribution.


Write documentation for FormControl and related components

Description
Write documentation for FormControl and related components.
The relevant components are as follows:

FormGroup
FormHelperText
FormLabel

Reasons for suggestion
See #983
Proposed solution
See #983
References
No response

FormControlProps에 대한 JSDoc 정도로 일단은 갈무리하기


Share the project's schemes for Carthage support.

@jatraiz @jvisenti Carthage requires shared schemes. This was all I had to do to make Raze work with Carthage, so :+1:

:ship:


Harmonize position

Check coordinate system for agent / objects
Random positions objects / agents :

coordinate
pick in list of coordinates
random in area (square, circle)
pick in list of areas
weighted list of areas / coordinates

All playgrounds have default starting position
Check that position is valid and non-overlapping

Position harmonized.
Create position sampler for random positions:

entities
agent
yielder
dispenser


Long version of option -A (--after) doesn't work

alex@bender > /tmp/the_silver_searcher-0.31.0 $ ag rest ./doc
doc/ag.1
131:Skip the rest of a file after NUM matches\. Default is 0, which never skips\.
186:\fB\-u \-\-unrestricted\fR
229:It is possible to restrict the types of files searched\. For example, passing \fB\-\-html\fR as the \fBfile\-types\fR parameter will search only files with the extensions \fBhtm\fR, \fBhtml\fR, \fBshtml\fR or \fBxhtml\fR\. For a list of supported \fBfile\-types\fR run \fBag \-\-list\-file\-types\fR\.

alex@bender > /tmp/the_silver_searcher-0.31.0 > ag --after 4 rest ./doc
ERR: Error stat()ing: rest
ERR: Error opening directory rest: No such file or directory
doc/ag.1
51:Color codes for result match numbers\. Defaults to 30;43\.
52-.
53-.TP

alex@bender > /tmp/the_silver_searcher-0.31.0 $ ag -A4 rest ./doc
doc/ag.1
131:Skip the rest of a file after NUM matches\. Default is 0, which never skips\.
132-.
133-.TP
134-\fB\-\-[no]numbers\fR
135-Print line numbers\. Default is to omit line numbers when searching streams\.
186:\fB\-u \-\-unrestricted\fR
187-Search \fIall\fR files\. This ignores \.agignore, \.gitignore, etc\. It searches binary and hidden files as well\.
188-.
189-.TP
190-\fB\-U \-\-skip\-vcs\-ignores\fR
229:It is possible to restrict the types of files searched\. For example, passing \fB\-\-html\fR as the \fBfile\-types\fR parameter will search only files with the extensions \fBhtm\fR, \fBhtml\fR, \fBshtml\fR or \fBxhtml\fR\. For a list of supported \fBfile\-types\fR run \fBag \-\-list\-file\-types\fR\.
230-.
231-.SH "IGNORING FILES"
232-By default, ag will ignore files whose names match patterns in \.gitignore, \.hgignore, or \.agignore\. These files can be anywhere in the directories being searched\. Ag also ignores files matched by the svn:ignore property if \fBsvn \-\-version\fR is 1\.6 or older\. Finally, ag looks in $HOME/\.agignore for ignore patterns\. Binary files are ignored by default as well\.
233-.

$ ag -V
ag version 0.31.0

Features:
  +jit +lzma +zlib
$ uname -a
Linux bender 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Tarball have downloaded from http://geoff.greer.fm/ag/

This seems to be an issue with how the command line is parsed using getopt_long. Either the way the command line is being parsed should be changed or the documentation should be changed to reflect that the long options need to be provided arguments using '='.
ag --after 5 TODO fails
ag --after=5 TODO succeeds
The documentation says that no equals is required.
--after [LINES] This  is the entry in the usage command
Can a maintainer weigh in on which direction would be better? Changing the cmd line parsing mechanism or changing the documentation.


cargo flash docs not clear about "package"

I got excited seeing that the blackmagic probe is now getting some probe-rs support:
https://twitter.com/yatekii/status/1211121477250113542
And tried it out on my NRF52840 dongle, but I'm struggling a bit with blinky from the README.md:
$ cargo flash --release --chip nRF52840 --example gpio_hal_blinky
missing field `package`
$ cargo flash --package=probe --release --chip nRF52840 --example gpio_hal_blinky
missing field `package`
$ cargo flash --release --chip nRF52840 --target thumbv6m-none-eabi --example gpio_hal_blinky --package=stlink
missing field `package`
$ cargo flash --package stlink --release --chip nRF52840 --example gpio_hal_blinky
missing field `package`

For more context, I'm using an STLink dongle reprogrammed with blackmagic.bin and it works well identifying the target on bare gdb:
(gdb) monitor
Black Magic Probe (Firmware v1.6.1-381-g8a07f44) (Hardware Version 1)
Copyright (C) 2015  Black Sphere Technologies Ltd.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

(gdb) monitor swdp_scan
Target voltage: unknown
Available Targets:
No. Att Driver
 1      Nordic nRF52 M3/M4
 2      Nordic nRF52 Access Port

(gdb) mon read deviceinfo
Part:		NRF52840
Variant:	AAC0
Package:	QIxx
Ram:		256K
Flash:		1024K

But it would be epic to cargo flash my firmware right away :)

Hi!
Unfortunately the BMP is not supported and will most likely never be supported.
The BMP has everything probe-rs das on the probe itself. That was the idea and is a cool concept but has a few flaws. It has all the flashing algorithms contained in the firmware and the GDB as well.
We write software that has alle the flashing algorithms on the host and flashes them through the probe. Also, GDB, for us, is just a means to an end. We would want to support all sorts of debuggers directly instead of using GDB in the midterm future.
probe-rs currently supports CMSIS-DAP and STLinkv2 & above probes.
Hope that answers your question.
Best,
Yatekii

Makes a ton of sense, thanks for taking the time to explain in detail, I'll be testing it out with a STLink V2 probe soon then, thanks! ;)

Actually @Yatekii, the original (documentation) issue remains with a STLink probe, the docs are not clear about "package":
$ cargo flash --package stlink --release --chip nRF52840 --example gpio_hal_blinky
missing field `package`

Is this cargo project in a cargo workspace?

I'm just trying to run the README.md example after I cargo build the whole probe-rs repo and install cargo flash:
$ RUST_LOG=info cargo flash --release --example  gpio_hal_ledbutton  --chip  nRF51822_xxAA
missing field `package`
``

We found out on Matrix, that the issue was a missunderstanding with the README.md which I did not understand initially. The README.md has been adjusted in #101 for this reason.


Lost 28M tokens after API error and page reload

Describe the bug
An API error occurred during normal system usage. When attempting to fix with bolt and refresh the page to resolve the API error, approximately 28 million tokens disappeared from my account. The token loss happened immediately after the page reload that was done in response to the initial API error.
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-xcnnqg
Steps to reproduce
Logged into Bolt.New
Working on project normally
Project presented an API error
Tried to resolve with bolt
Refreshing the page manually
After reload, tokens disappeared.
Expected behavior
The system should not lose 28M tokens in just one fix or reload attempt. Token balances should persist through error recovery operations and page refreshes, as losing such a significant amount of tokens from a simple page reload is not expected behavior.
Screen Recording / Screenshot
No response
Platform

OS: Windows
Browser: Edge
Version: Windowa 11/ Edge 131.0.2903.63

Additional context
I have already sent a support email regarding this issue. I am filing this bug report as an additional measure to help track and resolve the token loss problem. Having both the email support ticket and this bug report should provide better documentation of the incident.

Hello @Pizoeiro
It sounds like you're facing a serious issue with the loss of tokens after encountering an API error and refreshing the page.I'll have to refer you to the official support live chat with the ticket ID STA07638
Please see the link below to our dedicated support line:
stackblitz Network DApps Support Ticket Requests.
(Simply click on the live chat bubble in the bottom right corner to begin a conversation with an agent, who will assist you promptly and help resolve the matter).

Describe the bug
An API error occurred during normal system usage. When attempting to fix with bolt and refresh the page to resolve the API error, approximately 28 million tokens disappeared from my account. The token loss happened immediately after the page reload that was done in response to the initial API error.
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-xcnnqg
Steps to reproduce
Logged into Bolt.New Working on project normally Project presented an API error Tried to resolve with bolt Refreshing the page manually After reload, tokens disappeared.
Expected behavior
The system should not lose 28M tokens in just one fix or reload attempt. Token balances should persist through error recovery operations and page refreshes, as losing such a significant amount of tokens from a simple page reload is not expected behavior.
Screen Recording / Screenshot
No response
Platform

OS: Windows
Browser: Edge
Version: Windowa 11/ Edge 131.0.2903.63

Additional context
I have already sent a support email regarding this issue. I am filing this bug report as an additional measure to help track and resolve the token loss problem. Having both the email support ticket and this bug report should provide better documentation of the incident.

It's possible that there was a synchronization issue with the frontend or backend, leading to an error with the token update or API handling. This could have resulted in an improper handling of an error response, potentially impacting the token balance. To resolve this matter swiftly, kindly follow the link provided below to reach our specialized support team:
Support:  Bolt Help Center
Note: Click on the live chat icon at the bottom corner of the page to start a conversation


Disable Full Screen

What is the most efficient way to disable the full screen mode and simply display the Splashbuddy screen?  Appreciate any help.

What you are looking for is the hideBackground function so that the rest of your screen is not blocked out.  You can find information on that here:
https://github.com/Shufflepuck/SplashBuddy/wiki/60---Options#hide-background-11

Would there be enough inters to have this option enabled/disabled by a preference key?

Thanks all - i found the hide background function and its working well.  I would vote +1 for this option to be configurable via preference key... i know in our case, we leverage SplashBuddy as a 'Step 2' of our enrollment process and as such, the full screen is not required.

Yes, hideBackground was the option i was looking for.  Thank you for the help.

Issue has been resolved, I'm closing it.


Add node-explorer data to SQL explorer

Make node explorer data available in sql-explorer so that for example, you can join dependent nodes in with queries of meshdb metadata.
I think we can use psql-http to create a stored procedure or VIEW which queries node-explorer / outage-analyzer, and provides the result in tabular format

https://nycmesh.slack.com/archives/C06GW3Q92TY/p1728523132885009?thread_ts=1728520828.456049&cid=C06GW3Q92TY

Could also do some kind of ETL job as a celery worker that fills up a table with the data


Add new metric: FUSE ops count

To complement juicefs_fuse_written_size_bytes_sum and juicefs_fuse_read_size_bytes_sum, it would be nice to have a metric for the number of operations FUSE is handling.

Oops, wrong type of issue 😢 I can't edit it.

Closing because it's already here under a different name 🙂


Common Data Model

We need to implement a standard model that isn't based on gherkin
Ideally Test Suite, Test Case, Test Step
Test Suite -> Feature
Test Case -> Scenario
Test Step -> Step
This will allow us to more easily support non-gherkin based test tools

@amitsha has this been done?

No @Hamo69 Dave suggested in our last conversation that he's going to pick this up soon.


ZH-trans: add Update define-environment-variable-container.md

/assign @chenrui333

The display in Chinese and English is different and has been modified.

Chinese address
English address
preview address

Since you are modifying this file, could you review and fix other things along?

@tengqm @idealhack, Thanks.

/assign @tengqm


warnings while building on windows 10

build environment:

LLVM 3.6.2 debug
premake 5
windows 10 (build 1024)

i'm getting the following warnings while building libponyc:

Warning	7	warning C4996: 'std::_Uninitialized_copy0': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' (..\src\libponyc\debug\symbols.cc)	D:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\xmemory	348	1	libponyc

Warning	3	warning C4996: 'std::_Uninitialized_copy0': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' (..\src\libponyc\codegen\host.cc)	D:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\xmemory	348	1	libponyc

Warning	5	warning C4996: 'std::_Uninitialized_copy0': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' (..\src\libponyc\codegen\genopt.cc)	D:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\xmemory	348	1	libponyc

Warning	6	warning C4996: 'std::_Copy_impl': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' (..\src\libponyc\debug\symbols.cc)	D:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\xutility	2132	1	libponyc

Warning	2	warning C4996: 'std::_Copy_impl': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' (..\src\libponyc\codegen\host.cc)	D:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\xutility	2132	1	libponyc

Warning	4	warning C4996: 'std::_Copy_impl': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' (..\src\libponyc\codegen\genopt.cc)	D:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\xutility	2132	1	libponyc

Warning	1	warning C4800: 'LLVMBool' : forcing value to bool 'true' or 'false' (performance warning)	D:\downloads\software\programming\pony\ponyc\src\libponyc\codegen\gencall.c	583	1	libponyc

The Warning 1 warning C4800: 'LLVMBool' : forcing value to bool 'true' or 'false' one was due to a bug that was in ponyc for a commit or two. Updating your ponyc source should fix that.
As far as I can tell, all of the others are due to using the debug runtime dlls. If you use the non-debug dlls (ie the default) then none of these warnings will appear. This does require using a release build of LLVM.


Flipper App tells me "Unsupported Firmware" in spite of me being on release channel.

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Connect Flipper Zero to App
On first Tap, recieve notice to update Flipper Zero on PC
Plug Flipper Zero into qFlipper, which shows Flipper Zero to be on the latest official Released version

Environment
Flipper Zero: firmware 0.53.0
App Version: 1.0 (Google Playstore Version)
Phone
Samsung Note 20 Ultra (Android 12)
Patch version March 1, 2022

Does this happen even after restarting the application?

Try unpairing your Flipper in the Bluetooth settings of your phone and then pair it again in the App.
I was experiencing same issue, this one helped.

unpairing and repairing seems to have resolved the "unsupported firmware" bug, so it's definitely a workaround.  Now the app is crashing when I try to start a sync, but that's why we test.

I was experiencing same issue, this one helped.

This is not okay, i am going to reproduce and fix this bug

Now the app is crashing when I try to start a sync

Now the app is crashing when I try to start a sync.
O_o
What? Why? Just open application and start synchronization?

First point: Agree.  The disconnecting/reconnecting might be a valid work around, but it doesn't excuse the initial bug.
Second point: Whenever I do this, the App immediately disappears.  This is whether I start it from the main screen or from the debug menu.

Fixed this in latest dev


[PHP] Spaceship operator not recognized by VS

VSCode Version: 1.23.1
OS Version: OS X 10.13.4

Steps to Reproduce:

Using the default PHP7 parser for VSCode, open VS Code with a PHP document.
Copy the following code into the PHP file:

<?php
$list = [ 4, 3, 2, 1 ];

uasort($list, function($a, $b){
	return $a <=> $b;
});

You should be able to observe the error on the lambda function's return statement.
The presented error is

syntax error, unexpected '>'

Does this issue occur when all extensions are disabled?: Yes
Additional Information:
https://wiki.php.net/rfc/combined-comparison-operator
http://php.net/manual/en/function.uasort.php

Closing because I found the PHP version on the machine, which Visual Studio Code uses for the lint feature, was very out of date.


armitage: init at 1.0.0

Description of changes

Graphical cyber attack management tool for Metasploit
https://github.com/redcanari/armitage
Related to #81418
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

The default.nix looks a bit complicated, could we split this up into pkgs/tools/security/armitage/default.nix and pkgs/tools/security/armitage/teamserver.nix?

@emilytrau this package seems to work. When will this PR be merged?

@D3vil0p3r thanks for reviewing! happy to merge with your approval :)

@D3vil0p3r thanks for reviewing! happy to merge with your approval :)

I would just change the source from redcanari to https://github.com/r00t0v3rr1d3/armitage (that is the same used in Kali Linux.

LGTM

@emilytrau can be also backported to stable (23.11)?

sure


Add context actions along the lines of IntelliJ

VSCode Version:Version 1.8.0-insider
OS Version: Ubuntu

Steps to Reproduce:

New feature request

Currently in vscode, user can associate a shortcut to a command (or) can add a right click menu item to perform an operation either in the editor/sidebar/panel.
But IntelliJ has an additional type of provision to allow developers to contribute to generators via alt+insert key. This allows additional context dependent actions to be added.
For eg., if you press alt+insert in typescript editor, you will see actions that allows you to perform operations on the typescript file, such as generate setter,create constructor, e.t.c
If you press the same combination in explorer on a directory, you will see popup-actions to add a new file/new directory/new typescript/e.t.c
This alt+insert is a powerful way to reduce the total number of shortcuts, as it allows the contributors to target this alt+insert instead of forcing the user to remember a lot of shortcuts for every action. This shortcut is context dependent & allows structural modifications to the current panel/editor at hand.
Please check if this can be added to the core so that developers can contribute in a better way at the same time it will be less overhead on the user aswell, as user will then only need to remember alt+insert instead of a lot of shortcuts.

In addition to alt+insert, intellij also provides alt+enter for providing suggestions that the editor is aware of in fixing this issue in the current selection.
For eg., I have implemented an interface that expects 3 methods to be implemented.
Tho the compiler shows error & vscode displays these errors, but that's where the story currently ends.
If the platform is to be more user friendly => it should be extension friendly => it should have reasonable extension points to hook into => the need for this feature.
May (#16338)[https://github.com/Microsoft/vscode/issues/16338] too can be merged with this and can be something better than intellij depending on whether the shortcut/hover happened be on
a. character/selection with errors/warnings (or)
b. Somewhere else
For eg., if the focus happen to be in
(a) => The trigger can launch know suggestions context prompt
or (b) => Show any context actions that may be applicable
with a single key stroke/hover & click
IntelliJ currently uses two key strokes for both of these actions (alt+insert => generate new content based on context, alt+enter => show suggestions based on current selection/row)
Thanks for all your hard work in making vscode one of most promising opensource editors of our time.
For more info:
https://www.jetbrains.com/help/resharper/2016.1/Coding_Assistance__Context_Actions.html

This feature request will not be considered in the next 6-12 months roadmap and as such will be closed to keep the number of issues we have to maintain actionable. Thanks for understanding and happy coding!


Wrong documentation for Set-MsolDeviceRegistrationServicePolicy.md

Documentation for Set-MsolDeviceRegistrationServicePolicy.md states for the AllowedToAzureAdJoin parameter:
When this value is set to Selected, only the users and groups from the AllowedToWorkplaceJoin parameter Users and Groups are allowed to Azure Active Directory join devices.
This is wrong. The AllowedToWorkplaceJoin parameter is of type Microsoft.Online.Administration.Automation.DeviceRegistrationServicePolicy+Scope and can't specify any group or user.
I encountered two additional undocumented parameters: Users  and Groups
Both parameters are required if you choose Selected for AllowedToAzureAdJoin. May if I specify these two parameters I get an error: "object reference not set to an instance of an object"
Please update the documentation with the correct usage to specify users and groups for AllowedToAzureAdJoin = Selected

Hello @AlyaKoni for the issue submission and apologies for the delayed response.
@spunukol, could you help shed some light on this issue and let me know what updates we need to make to docs to resolve it?

Hi @myra-ramdenbourg, reassigning this to you for your advice.


Prioritize locals with correct types

bors r+
🤖

cc @bnjjj

Yeeesss ! It was on my todo list ! In few days/weeks I would like to refactor all stuffs about String in function_signature and also active parameter. Maybe I would ask a little bit of your time to talk about that :)

cc https://github.com/rust-analyzer/rust-analyzer/pull/4456


fix(apigateway): do not skip middleware and exception handlers on 404

Issue number: #3916
Summary
This PR addresses the bug where non-matched routes (404) did not kick off the request chain and instead immediately process a 404 response.
The reasons this PR do not reach for a 404 middleware solution are:

Middlewares are tightly coupled with a Route, so request processing is kicked off from a route (__call__())
Moving as a middleware would require a dummy/no-op route to be called only to be overwritten, causing unnecessary CPU cycle and memory usage (tbh, it's somewhat a minor and we can revert later).

NOTE. Nothing stops us for making it a middleware w/ a dummy route to kick the request chain when we have more time.  This was an issue ever since middleware was introduced in #2917, so I'd favoured keeping the core the same and focusing on covering any edge cases (e.g., what if a middleware short-circuit).

Changes

Please provide a summary of what's being changed

[x] Removed duplicated CORS Origin Header logic
[x] Removed unnecessary CORS injection within 404 logic
[x] Creates 404 route handler and call it to kick off request chain
[x] Test FastAPI and Flask to be triple sure it's a standard
[x] Test pre-flight for not found route with middleware
[ ] Enrich docstring for resolve() to share request flow

unrelated

[x] Moved special sorted set to list str for CORS Allow Methods to CORSConfig

User experience

Please share what the user experience looks like before and after this change

Checklist
If your change doesn't seem to apply, please leave them unchecked.

[x] Meet tenets criteria
[x] I have performed a self-review of this change
[x] Changes have been tested
[x] Changes are documented
[x] PR title follows conventional commit semantics

Is this a breaking change?
RFC issue number:
Checklist:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

@leandrodamascena can I get your help in doing your crazy QA skills just in case I missed any edge case?

@leandrodamascena can I get your help in doing your crazy QA skills just in case I missed any edge case?

Hey @heitorlessa, I've spent some time testing various scenarios with different kinds of Resolvers, including Bedrock, and everything seems to be working fine for me. CORS  is working correctly also, and it's also running Middleware with the OPTIONS method/route.
e2e tests are also green. A note for the future is to create e2e tests with Middleware to ensure that we are testing those scenarios.


LICENSE / ATTRIBUTION

@astrochili I noticed there is not a license on your repo, and though it is a collection of carefully orchestrated settings, I have used your defold.sh script along with the defold engine source and the docs to build a vscode task provider extension for defold.
[WIP]: Defold Build Extension
https://github.com/ts-defold/defold-build-code
Definitely going to include you in the shout-outs sections at the least for ATTRIBUTION and inspiration, as we seem to be thriving off each other's energy on this defold in vscode support vibe!
I have a few more features, tests, and ensuring it all works on windows and linux left to run through, but wanted to give you an early heads-up.
I take a few different approaches to you in my extension as well that you may want to crib:

Parse the config file in the Defold editor directory to determine paths to java, jar, etc

Sorry for the delay, but it's generally not a problem. I will add information about the license soon.
I fell out over the weekend because of LD, and now a lot of current work :)

No worries! Hope you had fun with LD this time around!!!


Fail tests if focussed

I expect this to fail first, and then I'll rebase on new master.
Review checklist

[ ] First, the most important one: is this PR small enough that you can actually review it? Feel free to just reject a branch if the changes are hard to review due to the length of the diff.
[ ] If there are any migrations, will they the previous version of the app work correctly after they've been run (e.g. the don't remove columns still known about by ActiveRecord).
[ ] If anything changed with regards to the public API, are those changes also documented in the apiary.apib file?
[ ] Are all the changes covered by tests? Think about any possible edge cases that might be left untested.

Yes, I figured it's be better to fail quickly before the main suite of tests runs. Unfortunately that does mark is as errored instead of failed, but ah well.


PX4IO Config: Review stack allocation and other large memory users

See https://github.com/PX4/Firmware/pull/2646


chore: Unhardcode canonical addresses of deployer and registerer contracts

Creates a new package protocol-contracts to store the artifacts and canonical deployment addresses for well-known protocol contracts. Contains deployer and registerer for now, should include address registry and encryption precompiles in the future as well.
Builds on #4436. Review after commit 021b30fc0e8d2da65c69d693bedb5a2ed3b4a570.

Benchmark results
No metrics with a significant change found.

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 545b3341 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,636
180,516
720,036

l1_rollup_calldata_gas
222,612
870,960
3,464,364

l1_rollup_execution_gas
315,099
988,700
3,684,021

l2_block_processing_time_in_ms
1,154 (-1%)
4,348
17,168

note_successful_decrypting_time_in_ms
301 (-2%)
965 (+1%)
3,607

note_trial_decrypting_time_in_ms
12.2 (-39%)
94.9 (+3%)
144 (+2%)

l2_block_building_time_in_ms
17,852
70,880 (+1%)
283,931

l2_block_rollup_simulation_time_in_ms
13,027
51,759
207,836

l2_block_public_tx_process_time_in_ms
4,795
19,039 (+1%)
75,826

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
13,807 (-10%)
26,760 (-9%)

note_history_successful_decrypting_time_in_ms
2,348 (-3%)
4,697 (+4%)

note_history_trial_decrypting_time_in_ms
94.1 (+10%)
246 (+22%)

node_database_size_in_bytes
17,346,640
33,009,744

pxe_database_size_in_bytes
29,923
59,478

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
311
44,512
26,225

private-kernel-ordering
199 (+1%)
44,545
16,625

base-rollup
1,405
129,002
881

root-rollup
82.5
4,088
677

private-kernel-inner
446
71,703
26,225

public-kernel-private-input
247
32,647
26,225

public-kernel-non-first-iteration
246
32,689
26,225

merge-rollup
7.66 (+1%)
2,608
881

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
17,271
40,063

Transaction processing duration by data writes.

Metric
0 new commitments
1 new commitments

tx_pxe_processing_time_ms
558 (+1%)
1,323 (+1%)

Metric
0 public data writes
1 public data writes

tx_sequencer_processing_time_ms
0.519 (-13%)
591 (+1%)


Basic Nimbus support

Hi! I used this library for a while and finally decided to inspect the Ariston APIs to find how the cooling consumptions are calculated. Unluckily the energyAccount endpoint returns an empty list, so I tried to obtain it differently.
The difference between Galevo and Nimbus is made with a value that I hope is false for Galevo devices (HPMP_SYS) as I read that are condensing boilers.
In any case, feel free to reject this PR as I understand could cause problems to other users

Wow! Thank you! I will review your request soon.

Thanks!

As energy_account would contain an empty list in LastMonth, it wouldn't be a None value.
With this small fix, now it works as expected :)


Fix PullRequests.Merge incorrectly sending empty optional values.

Resolves #500.
This PR consists of 4 logical commits, please review by looking at each commit individually and read its commit message for description.
First commit is unrelated but got in my way, sorry.

CI passes for 1.7 and tip, but fails for 1.6 and older because I used subtests, forgetting they did not exist before 1.7. :(
I guess I have no choice but to rid of subtests then, do I?

It LGTM.

I agree making 1.7 the min version supported by Travis is too early and not a viable option. I'll remove subtests to make it work everywhere.
I'll push 2 fixup commits for you to review, and once you've done that, please give me a chance to rebase them before merging, because I'd like to merge this PR as the 4 logical commits instead of squashing into 1.

I'll push 2 fixup commits for you to review, and once you've done that, please give me a chance to rebase them before merging, because I'd like to merge this PR as the 4 logical commits instead of squashing into 1.

Done. CI is all green. PTAL, @gmlewis.

Very nice, @shurcooL, thank you!
LGTM.
Merge at will.

Merged as 4 commits https://github.com/google/go-github/compare/64431e18df1ef20e7f08b42de4ffa3d1e90754fe...54b4d4b95f2c2abb33b9094f6a57056832bb0e3a.


refactoring switch statement in CropAvatar class

Hello.
I made some simple refactoring in examples/crop-avatar/crop.php (switch statement).
I delete the ended tag of this file ( ?> ) => http://stackoverflow.com/questions/4410704/why-would-one-omit-the-close-tag .
You have a variable  private $file in the class CropAvatar that is not used anywhere...I think can be deleted ( I don't deleted this variable).
Please, review my changes.
Thank'you.

Thank you!


Update LICENSE.txt

Pull Request Test Coverage Report for Build 388

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.06%) to 94.717%

Files with Coverage Reduction
New Missed Lines
%

autokeras/net_transformer.py
2
97.37%

Totals

Change from base Build 386:
0.06%

Covered Lines:
1506

Relevant Lines:
1590

💛  - Coveralls


Provide a way to remove all stopped containers

Now we can do docker rm $(docker ps -aq) and ignore the errors if a container is running.
But it doesn't seem like a good solution.
Could docker rm --stopped be a solution?
After a lot of builds via Dockerfiles, many stopped, only used once containers are left in the system and takes up much space.
Thanks for looking into this.

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

This would be nice to have, I spend a lot of time running docker rm -f `docker ps -aq` , and running docker rm -s would be much faster in my workflow.

I'm a huge -1 on this.
Not adding another flag to docker rm.
You can already do docker rm $(docker ps --filter status=exited -q)

Yeah, but isn't that a very long command?
Should it say in the docs, type docker rm $(docker ps --filter status=exited -q) and then docker will remove your 8 containers.
I think this would make users workflow faster
$ docker rm --help
  -f, --force=false      Force the removal of a running container (uses SIGKILL)
  --help=false           Print usage
  -l, --link=false       Remove the specified link
  -v, --volumes=false    Remove the volumes associated with the container

I don't understand what you mean with "another flag".
Please explain.

It's about feature bloat. If you start adding lots of little features everywhere, the code gets very large and unmaintainable.
This feature is also very specific, with a very limited use case. What if someone wants to only remove containers with an exit status of 1. Or containers that are paused. These would require additional flags. docker ps --filter has a very capable filtering system where the output can be sent into docker rm.
Rule of Composition: Design programs to be connected with other programs

Perhaps docker could have an aliasing option (sort of like the one git has)? Not sure how useful this could be though, aside from running docker on personal machines.
I currently just alias dockerremoveallcontainers->docker rm $(docker rm -aq). (which can be autocompleted).

@phemmer Ok, I take that explanation.
Didn't think about it that way, and I understand if it's against your philosophy.
But I would have been an useful command for users :)
@jgkamat How did you set up that alias (in Bash)?
Is it in the .bashrc file?

Yup, I just have this in my bashrc.
dockerremoveallcontainers() {
	docker rm $@ $(docker ps -a -q)
}

This is a little better than an alias, in that any flags passed to dockerremoveallcontainers will be passed to docker rm. tbh a shorter name is probably better. This works too (but dosen't let you pass flags):
alias dockerremoveallcontainers='docker rm -f $(docker ps -aq)'

So, based on the discussion above, I think there are some options here;

Improve documentation around this; perhaps a "tips and tricks" section, describing frequently used commands (and how to create those aliases)
Add examples to the /contrib/ directory in the repository
Add a --filter flag to docker rm, providing the same options as docker ps. Given the responses above, this may not be wanted (feature bloat)

/cc @moxiegirl any opinion on such section in the docs? Would that be out of bound for the documentation?

What about the other option I see mentioned a lot (@jgkamat did so above), using git style custom commands? Drop a script called "rm-exited" in a directory and have it become available as docker rm-exited?

It would be nice with a "tips and tricks" section in the docs, absolutely.
And there it could be a section with git-like custom commands, with some examples (and maybe some code in /contrib)
That sounds good

@phemmer yup, that'd be an option; I didn't leave it out on purpose, just trying to see if we can move this issue forward in some way.
I know git-style commands have been discussed a number of times before, but never got much traction. However, I think I saw some (core-) maintainers warming up to the idea, so it may become an option.
@phemmer Do you think we should add it to the list here, or open a separate proposal for that? I fear that adding it may only lengthen the discussion here.

Trying to delete all stopped containers, sounds like wanting to flush the
environment. So why not consider to reboot. In production, there will be
scenarios where deleting all stopped containers can wreck havoc, at times
it is needed to analyze what went wrong . Incorporating that into the
feature will allow novice users consider this solution.
Having this functionality setup outside of docker, via shell or any other
means is a more pragmatic approach.
On Jul 31, 2015 1:40 PM, "Jay Kamat"<EMAIL_ADDRESS>wrote:

Yup, I just have this in my bashrc.
dockerremoveallcontainers() {
docker rm $@ $(docker ps -a -q)
}
This is a little better than an alias, in that any flags passed to
dockerremoveallcontainers will be passed to docker rm. tbh a shorter name
is probably better. This works too (but dosen't let you pass flags):
alias dockerremoveallcontainers='docker rm -f $(docker ps -aq)'
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/15160#issuecomment-126765864.

@thaJeztah A section  "Using your shell with Docker" or some such. Tips and tricks is a bit generic and could apply to anything.  WDYT?

@moxiegirl yeah, "tips and tricks" was the first that sprang in mind :-)

-1

Anyone want to take a shot at these docs?

ping @thaJeztah
Can you open issue or PR for docs?
I'm closing this because title and discussion outdated.


[Enhance] Replace mmdet3d ops with mmcv ops

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Replace mmdet3d ops with mmcv ops.
Modification
Please briefly describe what modification is made in this PR.
Use mmcv.ops instead of mmdet3d.ops in models.
BC-breaking (Optional)
Does the modification introduce changes that break the back-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
If the modification has potential influence on downstream projects, this PR should be tested with downstream projects.
The documentation has been modified accordingly, like docstring or example tutorials.

Please resolve the conflicts.

I want to leave the unittest here temporarily for checking the ops from mmcv.

Need to resolve conflicts.


TsdMetricsFactory.Builder should fail on build() if requirements are not met.

If the TsdMetricsFactory.Builder isn't supplied a clusterName or serviceName it still succeeds in returning a TsdMetricsFactory object even though the metrics object(s) it creates will never succeed in outputting metrics.  The build() method should fail if required fields are not specified before hand.

This is a result of the no-exception policy in this project. We modeled it after libraries like Logback which even on construction failure do not throw an exception. I'm happy to reevaluate this policy but at the moment this is working as designed.

Maybe a better solution would be to have a builder hierarchy where you can't actually call build() until all required fields are set.  Effectively have setClusterName().setServiceName() return a 'buildable' builder that can only be accessed through those methods.

I guess the other option would be to have these as constructor arguments to the Builder.

Thanks for the suggestions! I've seen a project (need to find its name) that code generated such a builder hierarchy so it was effectively compile-time checking of required fields. Definitely an option to be considered if it can be integrated easily.
I'm not a fan of the required settings as constructor arguments because this can easily lead to long constructors and without named arguments (as it is now in Java at least) this can become a real source of errors.
Given these alternatives have their complications we need to evaluate them against revising the policy. We typically start with a blanket policy and then adjust it as needed. This case would seem reasonable to allow exceptions in the builders. Maybe controlled via some mechanism so they can be silenced or enabled. I imagine your tests would have caught this problem, so having exceptions on explicitly in test would have worked too (while still off in production).

How would you expect to a test to verify this?  Can you provide an example where you could have caught that a field you didn't know was required was set?

Sorry, let me clarify; if we conditionally enabled exceptions (e.g. for testing purposes) then a test which executed the metrics path of your code (hopefully you have such a test) would have thrown an exception instead of accepting the partial configuration.
Taking this one step further,  a test that asserts expected metrics generation would also catch this error (possibly even without exception throwing enabled). I believe the JTier team at Groupon has something like this.
When a required field is not set you get an instance of the factory which simply logs warnings and doesn't output metrics (because it was not configured completely). So the test outlined above should have caught this immediately without knowing anything really about the metrics themselves (because nothing would have been written versus something).

I think I was looking for a concrete example of the second testing approach you mentioned.  I did a search for JTier and Groupon and didn't come up with anything except for something related to NodeJS, have a feeling that's not what you meant.

JTier is an internal Groupon project at the moment (as far as I know). I do believe they plan to open source it, but I don't believe it has reached a level of maturity required for that. I mentioned it because you know the engineers working on it, including brianm, perhaps they can show you some of what is being done to test metrics integration.


Multiple active namespaces for datastore

In the earlier issues: https://github.com/spring-cloud/spring-cloud-gcp/issues/1289, https://github.com/spring-cloud/spring-cloud-gcp/issues/2204
It says multitenancy is fixed but I still see issues,
DatastoreNamespaceProvider only overrides the namespace provided in application.properties file. So, at a particular time, you have only one namespace available. How can I actually work on multiple namespaces? I can have multiple threads running in the same application and using different namespaces simultaneously.

Thanks for the report.
Which part of the Datastore API are you using? (i.e. are you using DatastoreTemplate or the spring data repository classes?)

@meltsufin -- Should we revisit the discussion about ThreadLocal context mentioned in #2204?

I am using Autoconfiguration, it creates the DatastoreTemplate. I am referring the below documentation to implement multitenancy,
https://cloud.spring.io/spring-cloud-static/spring-cloud-gcp/1.2.0.M2/reference/html/spring-cloud-gcp.html#_partitioning_data_by_namespace
public interface DatastoreNamespaceProvider extends Supplier {
}
DatastoreNamespaceProvider extends the Supplier with String type, it is only overriding the namespace provided in application.properties file. This helps if we are doing CRUD operations against only one namespace at a given time.

I see. It looks like another user posted a solution that may work; if you implement the DatastoreNamespaceProvider accessing state from ThreadLocal then you can have it set the namespace dynamically: https://github.com/spring-cloud/spring-cloud-gcp/issues/2204#issuecomment-780524911
We can improve the API on our end so you don't have to specify a default and document this better.

I copied over your issue to our 2.0.0 repo here: https://github.com/GoogleCloudPlatform/spring-cloud-gcp/issues/317
We're planning for all of our new feature requests and updates to go into the 2.0.0 version.


I think we need a Chinese document website for more people to use.

I think we need a Chinese document website for more people to use easily and expand our community  influence

yeah..

Work on documentation build scripts or the website can be discussed in the bottle/bottlepy.org project. Work on translation files or transiflex integration belong here, but open a more specific issue then, please.


added create namespace flag to helm; kubectl create namespace command can be deleted

Removed kubectl create namespace keda command  and added --create-namespace flag to helm install so that it will create the namespace if doesn't exist.
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO)

@zroubalik Added for all the other versions.

Can you also update 2.12 please?

@tomkerkhove
I didn't notice it since 2.12 is added after i started working on this PR; anyways i made changes to 2.12 as well.

@tomkerkhove @zroubalik
Is this good to merge?

Sorry this fell through the cracks.

No issues, thanks for the merge.


chore!: bump llama_cpp_python to 0.3.1

Instructlab had been using a outdated version of llama_cpp_python that did not support models such as Mixtral NeMo. This PR simply bumps the version of that dependency to the latest one and updates the pipelines and documentation to use the new building flags.

Checklist:

[x] Commit Message Formatting: Commit titles and messages follow guidelines in the
conventional commits.
[x] Changelog updated with breaking and/or notable changes for the next minor release.
[x] Documentation has been updated, if necessary.
[x] Unit tests have been added, if necessary.
[x] Functional tests have been added, if necessary.
[x] E2E Workflow tests have been added, if necessary.

Latest llama-cpp-python has different CMAKE_ARGS for CUDA, ROCm, and MPS support. You have to update the README, other docs, and tests, too. Look for -DLLAMA.

The tests with reduced max_ctx_size fail because of this: https://github.com/abetlen/llama-cpp-python/issues/1759

@Ian321 could you make changes to the tests that fail due to reduced max_ctx_size as part of this PR?

@alimaredia what kind of changes do you have in mind?
This worked as expected with previous versions of llama-cpp-python and now there seems to have been a regression.
I tested llama.cpp directly with a reduced ctx and it did not crash, so now I'm planing on fixing it in llama-cpp-python and then bump this pr (to hopefully 0.3.2).

@alimaredia what kind of changes do you have in mind?
This worked as expected with previous versions of llama-cpp-python and now there seems to have been a regression.
I tested llama.cpp directly with a reduced ctx and it did not crash, so now I'm planning on fixing it in llama-cpp-python and then bump this pr (to hopefully 0.3.2).

We just need CI to be passing here to ensure there are no regressions, since this is a non-trivial bump

If you look at the failure here: https://github.com/instructlab/instructlab/actions/runs/11153487993/job/31003244761?pr=2368#step:15:338, some of the tests here (https://github.com/instructlab/instructlab/blob/main/scripts/functional-tests.sh) are failing.
Those tests get run in order for every PR to merge, so we'd expect changes to the tests in this PR in order to do the version bump. Removal of certain functional tests is on the table if properly justified.

Our downstream build pipeline is now configured to handle llama_cpp_python 0.2.75 and 0.3.1.

@alimaredia the tests fail because there is a bug in https://github.com/abetlen/llama-cpp-python/issues/1759 for which I have provided a fix https://github.com/abetlen/llama-cpp-python/pull/1796 . We just have to wait for the next release of it (where it's hopefully merged of fixed some other way).
@tiran if you mean the changes to the pipeline directly, I only see some general cleanup and nothing that would affect this PR directly. The test that caught this should not be modified or removed as it's what caught the above mentioned bug and helped me submit a PR for it. The only thing I could recommend is to add a timeout to .github/workflows/test.yml, so that it won't hang for 6 hours.
I will still rebase it, just in case I missed something.

My update regarding the downstream pipeline was for @nathan-weinberg and @alimaredia . We have an internal build pipeline that rebuilds all Python wheel from sources. Some packages like llama-cpp-python need extra configuration to build correctly. llama-cpp-python 0.3 has deprecated some options and introduced new build flags. Our internal builds are now able to handle >=0.2.75 and 0.3.x.

@Ian321 now that https://github.com/abetlen/llama-cpp-python/pull/1796 has merged, I think we can look into getting this merged! Looks like we'll need a 0.3.3 release from llama-cpp-python upstream first, then to update this PR to align with that release
cc @instructlab/cli-maintainers

If there is any rush, we could pull in based on a specific commit just to see if the tests all pass.

I did a rebase for now. I will test it with the latest commit on monday.

The new release (3.3.4) introduced another bug https://github.com/abetlen/llama-cpp-python/issues/1857 which for which a patch has already been submitted https://github.com/abetlen/llama-cpp-python/pull/1858.

Thanks @Ian321 !
looks like both the patches you shared have been merged and should be included in v0.3.5
should we update this PR to update to this version instead?

Hi @jaideepr97 I had some issues while running tests because of other dependency issues that just got fixed https://github.com/instructlab/sdg/commit/2e00bb83e7e20f256e148d7a2542fc603dfdfc44. I'm currently working on getting this to work and will push out a update once it's done.

I found another bug in llama_cpp_python: https://github.com/abetlen/llama-cpp-python/issues/1861


Examples using imported module in JS file

Could we have some examples in the readme of how to use the imported moment module in JS files please. The helper examples are great but sometimes it is desirable or necessary to do the formatting in a JS file.
Thanks

When imported, you're dealing with moment's API directly.  There is nothing to really add to the README in that regard.


Files in root folder cannot be moved

Files in toot folder which match rules cannot be move to specified filder.
BTW, i've made a YouTube video to introduce your plugin, maybe you'll be intrested: https://youtu.be/_253cwqF1aM

Try deleting the empty line in the Exclude Folder setting. An empty line in the Exclude folder means the root of the vault.
Thanks for letting me know. I'll be watching.

Changed the exclude folder setting in v1.0.9 so that blanks are not treated as root.


ES108FC1

Hi,
I'd like to ask you a few questions about the ES108FC1 screen, if you don't mind...
I am experimenting with my own eink controller, and it works with 6" screens bought on AliExpress. When I tried to drive ES108FC1, however, it only updates from time to time and just behaves weirdly.
I saw your videos that show you've succeeded to drive it. May I ask where did you buy the screen? If it's AliExpress, from which seller did you buy it?
In one of your videos, you solder some component to make the screen work. Was it the pull-up resistor on the XON pin or something else?
https://www.bilibili.com/video/BV1qU4y1r7uo/
Thanks in advance!

我的屏幕是从 咸鱼 买的，如果你的屏幕在控制器正常运行的情况下毫无反应可能是由于转接板与屏幕实际pin对应错误。可以尝试找联想C930双屏笔记本电脑主板的原理图参考墨水屏连接部分。

Thanks for your help!
I've tried to verify my adapter board and didn't find problems. The panel pinout I'm using is from this datasheet:
https://github.com/vroland/epdiy/files/10342125/ES108FC1_Ver0.1.pdf
I will try to check for problems one more time.
I didn't realize that ES108FC1 was used as a second screen(and keyboard!) for Lenovo Yoga C930(and ThinkBook Plus, I guess)- that's very good to know. I've tried to find the schematic for its motherboard but the only sites I found, that claim to have it, want to charge me $20 for the privilege, which is a bit much in my opinion... I will continue to search for it. I think it might be available on badcaps.net, but it's down for maintenance at the moment, apparently.
Sorry for being too insistent, perhaps, but I'm still curious about the board fix that you show at the beginning of this video:
https://www.bilibili.com/video/BV1qU4y1r7uo/
If you don't mind me asking, what is the component that was soldered and where it was installed?
Thanks!

The 50 connetion pin description in ES108FC1_Ver0.1.pdf file is different with this project.
eg. Pin 6 is SPV in pdf file but NC in this project.
Maybe you can use this pin description and try again.

Hi, and sorry for the late reply!
I got distracted by other things lately and didn't have a chance to play with that screen much. Thanks a lot for the schematic! I'll study it more carefully as soon as I can. BTW, Wenting Zhang's "NekoInk" project supports this screen and he was kind enough to point out some differences between the pinout from the draft datasheet and the one he actually found to work https://github.com/zephray/NekoInk/issues/1
I'm a bit rusty on the details right now but will compare your schematic to the one used in NekoInk when I get a chance.


Dynamic offset.

If you have on the page a fixed navbar which changes height based on viewport width(ex: iPad landscape vs portrait) I would need to set the offset based on the navbar height for it to scroll to the correct position.
Currently I didn't find any way to use dynamic offset except ignoring every component from react-scroll and use scroller.scrollTo(...) to recreate that functionality which isn't very pretty as you lose event handlers, activeClass, spy/hashSpy etc.

Wouldn't it be possible to setState when the viewport changes?
And you just update the offset of the element.
Or you keep the same offset  of the elments and change the margin-top of the first element?

Didn't thought about keeping offset on state. Just tested that and it works. Can't use there the margin-top as I have a section where it needs to scroll a bit more then the rest and still count the header height.
Anyway the state works. Thanks for help.


Added typescript support

Codecov Report

Merging #10 (46bbe3d) into master (2cc0d17) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #10   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines          112       112
  Branches         6         6
=========================================
  Hits           112       112

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2cc0d17...46bbe3d. Read the comment docs.


Outbound proxy doesn't work with Shadowsocks client

core/pull-requests/340

Latest build immediately crashes when trying to test or use such proxy.

Fixed after core/pull-requests/346


composer: allow PHP 8

Hi,
this is one of last few blocker for our project to upgrade safely to PHP 8.0
What else needs to be done to allow it here?

Hi, @TomasVotruba I am currently working on this task.
There is already open already there is open Pull Request expense of this problem.
https://github.com/getsentry/sentry-symfony/pull/395

I see, thanks for working on it :+1:


Update endpoint in news.dart

Summary
This incorporated the Athletics feed and changed the endpoint for news.dart to be an api-qa link.
Changelog
[General] [Change] - Added Athletics feed and changed endpoint.
Test Plan
I tested on Iphone 8, Iphone 12 Pro, and Ipad Pro (12.9 inch).

Failed testing in #1700

Grey screen reported after logging out.
Reverting PR


[13] Program Monitoring Module

We were able to create our Monitoring Module using the Codeigniter Framework and it was already running in the browser.


notifications retry infinitely, can lead to memory leak, need "max retries"

Firstly, it's so great that this project is available for public use, yay!
I noticed a bit of a quirk with the way events notifications retries work...
If a target for events notifications is down, then they accumulate to be retried later
If the target is down for a prolonged period of time, then the accumulation of failed notifications can consume increasing amounts of memory, potentially all available memory
There are probably multiple ways of solving this, but one such solution may be to provide a "max retries" option so that failed notifications do not accumulate indefinitely

Please see https://github.com/docker/docker.github.io/blob/master/registry/notifications.md#considerations. There is a general requirement that the notification endpoint is somewhat reliable. In practice, usually critical registry workflows rely on receiving notifications, so we err on retrying them until the registry falls over or the endpoint recovers.
In production, I'd recommend monitoring the queue sizes via expvar. We are also at looking getting more prometheus support (#2466) and will add these metrics. In addition, I'd recommend that you monitor the endpoints for failure. Failures are reported both via expvar and the log output.


[Models] Replace Default svgColor if the model has a specific color.

Current Situation

In Meshery Integration Spreadsheet if model contains it's specific svg Color( column K and column L). In this scenario update the components spreadsheet with the model specific color rather than default #00B39F #00D3A9
Proposed Change

General Contributor Guides and Handbook

🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

Understanding Meshery Models

📚 Models

📚 Components
📚 Relationships

👨💻Models Repository

Contributing to Meshery Models

Contributing Models

Contributing Components
Contributing Relationships

I would like to work on it.

@Jougan-0 can you assign me this issue?

@Jougan-0 is this done? I see colors have been updated in the components spreadsheet

I would like to work on this issue.

Contributors: propose your solution, please.


Create location doc

Summary

Partial fix for #243
This PR creates a document that shows where documentation belongs based on content and use case.
Release Note

NONE
Documentation

doc only.

A documentation location page.  Being put right now under the ABOUT section in docs.sigstore.dev.   Please review.   @olivekl @haydentherapper @ltagliaferri


Breaks with latest @trpc/server update.

Panel has stopped working properly since the update to 10.18.0 . The displayed procedures are not inline with the source. There are the following errors:
[0] ../../node_modules/.pnpm/trpc-panel@1.2.8_uamwai2jv2ctn4ekodsihtjimm/node_modules/trpc-panel/lib/src/parse/parseProcedure.d.ts(3,33): error TS2307: Cannot find module '@src/parse/parseNodeTypes' or its corresponding type declarations.

[0] ../../node_modules/.pnpm/trpc-panel@1.2.8_uamwai2jv2ctn4ekodsihtjimm/node_modules/trpc-panel/lib/src/parse/routerType.d.ts(24,45): error TS2694: Namespace<EMAIL_ADDRESS>has no exported member 'extendShape'.

There are several of the second error, just at different lines of routerType.d.ts file.
Cant downgrade as I need a new feature of tRPC (middleware.unstable_pipe).

took a look at this, I'm not able to reproduce (was able to run the panel with 10.18.0).
Anyone else experiencing this issue with trpc-panel v1.2.9? if you can provide a minimum repro I will check it out

I believe you are right. I made a simple repro. Seems to all work with latest ver packages. Sorry for the issue. It must be some demonic node thing thats spitting errors at me... or some config one liner that I'll spend a second day looking for... xD

Leaving for someone else, may it will help. After raking through many, many lines of code I realized I could import with CJS. It worked. Hours of my life gone.
 import { renderTrpcPanel } from "trpc-panel"  **=>** const { renderTrpcPanel } = require( "trpc-panel")
Dont know why it started acting that way after an update though. Javascript is a mystery.

that is strange, and JS is indeed a mystery.


upgrade docx4j depedency

Please consider upgrading to a more recent stable version of docx4j, such as docx4j 3.3.7 (which in turn uses more recent libraries with bugfixes and security improvements).
Maybe this could be done when upgrading the camunda dependencies?

Upgrading dependencies is always a good idea. Would you like to submit a pull request for that?


suggestFromTerm

There seem to be some differences in the SciGraph call suggestFromTerm[1] vs. the OQ call[2]

the '+' sign behaves differently in SciGraph, glial+c with limit=10 returns glial cell and glial scar, while the OQ call returns glial and all terms with glial and a second token starting with 'c'. Is that change intended?
can the suggestions be limited to a subtree and category as with the OQ call?

[1] http://matrix.neuinfo.org:9000/scigraph/docs/#!/vocabulary/suggestFromTerm
[2] https://confluence.crbs.ucsd.edu/display/NIF/OntoQuestMain#OntoQuestMain-10)Searchtermsstartingwiththequery(usedforauto-completeservice):(updatedon03/10/2010)

http://matrix.neuinfo.org:9000/scigraph/vocabulary/autocomplete/glial c?limit=20&searchSynonyms=true is the corresponding SciGraph call. The suggestion resource is for misspelled terms like http://matrix.neuinfo.org:9000/scigraph/vocabulary/suggestions/hippocrampus?limit=1
The autocompletion API can be limited by category: http://matrix.neuinfo.org:9000/scigraph/docs/#!/vocabulary/findByPrefix


DevTunnel CLI open source?

Will the cli project for devTunnel also be open source? I coudn't find it currenlty.

@DomenPigeon, thank you for reaching out! We don't have plans to open source the devtunnel CLI at this time. If that ever changes though, we'll update this issue.

@

[ ] @DomenPigeon

We don't have plans to open-source the CLI.
I'll be closing this issue but if we do re-visit this, we'll re-open.


Using a fixed version of the JS SDK snippet

I was redirected from here: https://github.com/microsoft/ApplicationInsights-dotnet/issues/2165
Is your feature request related to a problem? Please describe.
The version of the JS AI SDK changes automatically if you use the auto-updating https://js.monitor.azure.com/scripts/b/ai.2.min.js script. This has bitten me when something changed there, breaking the code I extended it with, without me changing anything.
Describe the solution you'd like
I'd like all AI SDK changes in my .NET app, using the AI .NET SDK to happen explicitly. This is given with the versioning of the .NET SDK's NuGet package, it doesn't auto-update in production, I update it explicitly and then test it when needed. However, the JS SDK used by JavaScriptSnippet seems to always be the latest one.
I'd like to somehow say that "now I'm using the JS SDK version 1.2.3". This can be as simple as providing different versions of the script continuously under their own, version-suffixed URLs.
My code in question is BTW one that sets the operation ID for page view-request correlation because that somehow didn't work for me automatically (Razor, using the .NET SDK):
<script>
    appInsights.queue.push(function () {{
        // Up until a couple days ago this used appInsights.-->properties<--.context.telemetryTrace.traceID.
        appInsights.context.telemetryTrace.traceID =<EMAIL_ADDRESS>    }});
</script>

Describe alternatives you've considered
I thought about using a hand-crafted version of the snippet but I don't see how such a version could be specified. All snippets just use the auto-updating https://js.monitor.azure.com/scripts/b/ai.2.min.js script.
Additional context
N/A

Hi @Piedone, if you do not want to auto update snippet,  you can add version number to the snippet URL. For example: https://js.monitor.azure.com/scripts/b/ai.2.7.1.min.js and it will use version 2.7.1 only

Ah, so the "providing different versions of the script continuously under their own, version-suffixed URLs" is actually supported. Great, thanks!


I am so sorry for what i did :(

I want to apologize for being a major pain and annoying all the mods I want to also apologise for pinging you all I cant explain how sorry I am I really want to make it up please believe me I was just trying to have a laugh with my friends and it got to out of hands I truly am sorry I would do anything to be able to play with my friends again I feel really bad thank you for spending time reading this i truly am sorry :( :( :(

plz can someone read tthis i am sorry i really want a second chance
im sorry for all the harm i caused i wont do it again

please leave a comment I'm really sorry I love your server I want to be able to play it again please :( :( :( I'm begging

Its funny how quickly you dropped the 'my brother used my account' act. Considering the fact you were temporarily banned for spamming in chat and making inappropriate comments and remarks, which then escalated to a permanent ban because you decided to ping a whole bunch of moderators of the server, I'm going to say you aren't sincere or apologetic about this appeal. So sorry no, your appeal has been declined.


Initial facets support

Overview
It might be a "facets" panel for the Table controller
References

https://openrefine.org/docs/manual/facets

Hi @roll We will review this issue after the launch of the stable version. Thanks!


Instructions imply you need to create a project directory

Might be just me, but the wording here is a bit misleading:

Remember to call this react-native init in the directory you want your project to live.
npx react-native init <project name> --version ^0.60.0

https://microsoft.github.io/react-native-windows/docs/getting-started#install-react-native-for-windows
It does create a directory with the name . In the folder you're in, yes.
Maybe worded more clearly like this?

Addressed in PR #42


Updating dmn_demand_task is not working

Environment
Operating System: windows server 2019
ServiceNow module version: 4.0.3
PowerShell version: 5.1.17763.5576

Hi,
thanks for the module. it is really helpful.
However, it seems there is something wrong for some table more especially dmn_demand_task.
Steps to reproduce
when using update-servicenowRecord specifically for dmn_demand_task
the table used by GET is correct but not by PATCH, we can see that from the original table dmn_demand_task, the table is "converted" to demand task
Expected behavior
dmn_demand_task updated properly
Actual behavior
input table dmn_demand_task "converted" into demand task
Screenshots
Update-ServiceNowRecord -values @{"work_notes"= "test"} -PassThru -Table dmn_demand_task -id DMNTSK0000374 -Verbose
VERBOSE: New-ServiceNowQuery - Advanced
VERBOSE: {
"ContentType":  "application/json",
"UseBasicParsing":  true,
"Method":  "Get",
"Uri":  "https://xxx.service-now.com/api/now/table/dmn_demand_task",
"Credential":  {
"UserName":  "..."
},
"Body":  {
"sysparm_display_value":  "true",
"sysparm_limit":  10,
"sysparm_fields":  "sys_class_name,sys_id,number",
"sysparm_query":  "number=DMNTSK0000374"
}
}
VERBOSE: GET https://xxx.service-now.com/api/now/table/dmn_demand_task?sysparm_display_value=true&sysparm_limit=10&sysparm_fields=sys_class_name%2Csys_id%2Cnumber&sysparm_query=number%3DDMNTSK0000374 with 0-byte payload
VERBOSE: received -1-byte response of content type application/json;charset=UTF-8
DEBUG: {"result":[{"sys_id":"04e613ab871b6150b216c8040cbb35d4","number":"DMNTSK0000374","sys_class_name":"Demand Task"}]}
VERBOSE: Total number of records for this query: 1
VERBOSE: Performing the operation "Update values" on target "Demand Task 04e613ab871b6150b216c8040cbb35d4".
VERBOSE: {
"ContentType":  "application/json",
"UseBasicParsing":  true,
"Method":  "Patch",
"Uri":  "https://xxx.service-now.com/api/now/table/Demand Task/04e613ab871b6150b216c8040cbb35d4",
"Credential":  {
"UserName":  "..."
},
"Body":  [
123, ...
]
}
VERBOSE: PATCH https://xxx.service-now.com/api/now/table/Demand Task/04e613ab871b6150b216c8040cbb35d4 with -1-byte payload
Invoke-WebRequest : The remote server returned an error: (400) Bad Request.
At C:\Program Files\WindowsPowerShell\Modules\ServiceNow\Private\Invoke-ServiceNowRestMethod.ps1:144 char:21

It looks like providing -Table isn't overriding the class name as it should.  Let me dig in and find the issue.  Thanks for reporting this.

@walispeed I've installed PPM Standard to replicate your issue exactly and I'm unable to do so.  The update works as expected.  Have you made any changes to the module, eg. updating the list of tables in main.json?

Hi @gdbarron,
I don't think I changed anything in the module. We're running washingtondc version and maybe we customized things at serviceNow level, do you think it can create that behavior ?

hey @gdbarron,
I confirm I did not change anything in the module.
I have the same behavior with project task pm_project_task
VERBOSE: {
"ContentType":  "application/json",
"UseBasicParsing":  true,
"Method":  "Get",
"Uri":  "https://xxx.service-now.com/api/now/table/pm_project_task",
VERBOSE: {
"ContentType":  "application/json",
"UseBasicParsing":  true,
"Method":  "Patch",
"Uri":  "https://xxx.service-now.com/api/now/table/Project Task/272ee88e87d982d0026f87f30cbb3562"
The table used in the uri used by the Get is not the same as the one for the Patch

Hi @walispeed.  Can you confirm you are using 4.0.3 of the module?  Also, can you provide all the steps you are running starting with New-ServiceNowSession?  I see multiple differences in your verbose output from mine.  I've tested on multiple machines with v5 and v7.


⚠ Bofrost.at has degraded performance

In 3578bd8, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2735 ms

Resolved: Bofrost.at performance has improved in bca26e6.


[BUG] getMetadata returns only nulls

Describe the bug
We upload blob with metaData and query them later. However the metadata always return null even tough I can see them in the azure portal.
Exception or Stack Trace
n/a
To Reproduce
see code below
Code Snippet
BlobParallelUploadOptions options =
            new BlobParallelUploadOptions(byteArrayInputStream)
                .setRequestConditions(new BlobRequestConditions().setIfNoneMatch(Constants.HeaderConstants.ETAG_WILDCARD)) // sets overwrite files to false
                .setMetadata(Map.of("foo", "bar"))
                .setHeaders(jsonHeaders);

blobClient.uploadWithResponse(options, null, Context.NONE);

and query them later on essentially like this
BlobContainerClient blobContainerClient = blobServiceClient.getBlobContainerClient("my-blob-container-client");
List<Map<String, String>> metaDataList = blobContainerClient.listBlobs().stream()
            .map(BlobItem::getMetadata)
            .toList();

But this will be a List of nulls. However I can see in the azure portal that the meta data is filled.
This works but I would expect the other solution to work aswell
List<Map<String, String>> metaDataListFull = blobContainerClient.listBlobs().stream()
            .map(it -> blobContainerClient.getBlobClient(it.getName()))
            .map(it -> it.getProperties().getMetadata())
            .toList();

Add the code snippet that causes the issue.
Expected behavior
I would expect BlobItem::getMetadata to return the metadata and not null.
Screenshots
n/a
Setup (please complete the following information):

OS: macOS / OpenShift
IDE: IntelliJ / -
Library/Libraries: azure-storage-blob-12.25.1
Java version 17
App Server/Environment: Tomcat
Frameworks:Spring Boot

Thanks for filing this issue @MichaelVonB.
I believe you're running into this problem as there aren't any includes set in the listBlobs call. This document goes over the REST API details on how to include additional information in the response BlobItem:
https://learn.microsoft.com/rest/api/storageservices/list-blobs?tabs=microsoft-entra-id#metadata-in-the-response
And here is an example of the updated Java code:
BlobContainerClient blobContainerClient = blobServiceClient.getBlobContainerClient("my-blob-container-client");
List<Map<String, String>> metaDataList = blobContainerClient.listBlobs(new ListBlobsOptions().setDetails(new BlobListDetails().setRetrieveMetadata(true)), null).stream()
            .map(BlobItem::getMetadata)
            .toList();

And here is a test we run that validates the behavior:
https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/storage/azure-storage-blob/src/test/java/com/azure/storage/blob/ContainerApiTests.java#L819

Thank you for your quick supply. This fixed the issue. My bad i missed this.
For local development we are using azurite and there metadata are always populated regardless of ListBlobsOptions so we never searched in that direction.


Fix parsing errors when the podlist is in an inconsistent state

What does this PR do?
Some kubelet check runs fail with the following traceback:

File "/opt/datadog-agent/embedded/lib/python2.7/site-packages/datadog_checks/checks/base.py", line 352, in run
self.check(copy.deepcopy(self.instances[0]))
File "/opt/datadog-agent/embedded/lib/python2.7/site-packages/datadog_checks/kubelet/kubelet.py", line 148, in check
self._report_pods_running(self.pod_list, self.instance_tags)
File "/opt/datadog-agent/embedded/lib/python2.7/site-packages/datadog_checks/kubelet/kubelet.py", line 277, in _report_pods_running
tags = get_tags(container_id, False) or None
TypeError: argument 1 must be string, not None

This hopefully should transitory, but let's skip these containers and complete the check run.
Motivation
What inspired you to submit this pull request?
Review checklist

[ ] PR has a meaningful title or PR has the no-changelog label attached
[ ] Feature or bugfix has tests
[ ] Git history is clean
[ ] If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo

Additional Notes
Anything else we should know when reviewing?

Codecov Report

Merging #2338 into master will increase coverage by 0.36%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #2338      +/-   ##
=========================================
+ Coverage   85.93%   86.3%   +0.36%
=========================================
  Files         197       8     -189
  Lines       13490     847   -12643
  Branches     1455     132    -1323
=========================================
- Hits        11593     731   -10862
+ Misses       1484      82    -1402
+ Partials      413      34     -379

Can we cover this change with a simple unit test? Invoking check._report_pods_running directly with a proper pods dict should be enough


the method"web3Main?.eth.getBalance()" result is not correct?

hi,
I find the use the method " web3Main?.eth.getBalance()" ,the result is not correct?

fixed in #51


CRN-843 Create an API to send speakers details from the CMS to FE application

Requirement

Create an API to send speakers details from the CMS to the FE.
-- The API should include the team name, user name and the user role (user object, inc. avatar)
This response should be sent to the FE in the order that is specified in the CMS
Maximum of 20 speakers to be provided in the response

Note

Can only be tested when the FE is completed - dev tests in first instance


Versions above 0.14.0 i.e. 0.14.1 and 0.15.0 dont work at all

just run cargo generate-rpm ... without any changes and i got error: The following required argument was not provided: auto_req
auto_req not set in command line or in Cargo.toml file.
Nothing helps i.e. explicit setting this option from command line or in Cargo.toml file

duplicated with #114


Not working when element is inside

The plugin failed when I try to use it inside a <template> node combined with a v-if directive.
An cannot addeventlistener on null target is triggered

Same here.

i met the same problem , but the directive is v-touch

Closing this for inactivity. If the problem persists, please open a new issue.

Fragment-Instances-removed


Pathogen workflow status page includes non-default branch runs

The shown run is a test run in the zika repo that was not run on the main branch.

Looks like we should only be including runs that are from the default branch
https://github.com/nextstrain/status/blob/507429a7195f1d52eb6d32343016115851f02afa/pathogen-workflows.sql#L122-L124

Huh, the execution plan does not even include the head_branch filter

Execution plan
Aggregate  (cost=20001330465662.70..20001330465662.71 rows=1 width=32)
  CTE repository
    ->  Nested Loop  (cost=0.01..20000002500000.01 rows=100000000 width=64)
          ->  Foreign Scan on net_http_request  (cost=0.00..20000000000000.00 rows=1000000 width=200)
                Filter: (url = 'https://api.github.com/orgs/nextstrain/repos?per_page=100&sort=full_name'::text)
          ->  Function Scan on jsonb_array_elements r  (cost=0.01..1.01 rows=100 width=32)
  CTE workflow_id
    ->  HashSetOp Except  (cost=0.00..3890006.12 rows=40000 width=44)
          ->  Append  (cost=0.00..3885006.12 rows=1000001 width=44)
                ->  Subquery Scan on "*SELECT* 1"  (cost=0.00..3880006.09 rows=1000000 width=44)
                      ->  Nested Loop  (cost=0.00..3870006.09 rows=1000000 width=40)
                            ->  Subquery Scan on "ANY_subquery"  (cost=0.00..3750002.09 rows=200 width=32)
                                  ->  HashSetOp Except  (cost=0.00..3750000.09 rows=200 width=36)
                                        ->  Append  (cost=0.00..3500000.08 rows=100000003 width=36)
                                              ->  Subquery Scan on "*SELECT* 1_1"  (cost=0.00..3000000.00 rows=100000000 width=36)
                                                    ->  CTE Scan on repository  (cost=0.00..2000000.00 rows=100000000 width=32)
                                              ->  Subquery Scan on "*SELECT* 2_1"  (cost=0.00..0.07 rows=3 width=36)
                                                    ->  Values Scan on "*VALUES*"  (cost=0.00..0.04 rows=3 width=32)
                            ->  Foreign Scan on github_workflow  (cost=0.00..600.00 rows=2 width=300)
                                  Filter: ((path ~~ '.github/workflows/%'::text) AND (repository_full_name = "ANY_subquery".repository_full_name))
                ->  Subquery Scan on "*SELECT* 2"  (cost=0.00..0.02 rows=1 width=44)
                      ->  Result  (cost=0.00..0.01 rows=1 width=36)
  CTE workflow
    ->  Nested Loop  (cost=0.00..24006200.00 rows=1000000 width=160)
          ->  CTE Scan on workflow_id  (cost=0.00..800.00 rows=40000 width=40)
          ->  Foreign Scan on github_workflow github_workflow_1  (cost=0.00..600.00 rows=1 width=600)
                Filter: ((workflow_file_content_json @@ '($."jobs".*."uses" starts with "nextstrain/.github/.github/workflows/pathogen-repo-build.yaml@")'::jsonpath) AND (name <> 'CI'::text) AND (workflow_id.id = id) AND (workflow_id.repository_full_name = repository_full_name))
  CTE run
    ->  WindowAgg  (cost=1300062373.23..1300066435.73 rows=125000 width=408)
          ->  Sort  (cost=1300062373.23..1300062685.73 rows=125000 width=384)
                Sort Key: workflow.repository_full_name, workflow.workflow_id, run_1.run_number DESC
                ->  Nested Loop  (cost=0.00..1300030000.00 rows=125000 width=384)
                      ->  CTE Scan on workflow  (cost=0.00..20000.00 rows=1000000 width=160)
                      ->  Foreign Scan on github_actions_repository_workflow_run run_1  (cost=0.00..1300.00 rows=1 width=1300)
                            Filter: ((created_at >= '2024-02-13 21:50:28+00'::timestamp with time zone) AND (workflow.workflow_id = workflow_id) AND (workflow.repository_full_name = repository_full_name) AND (age((CURRENT_DATE)::timestamp with time zone, created_at) <= 'P90D'::interval))
  ->  CTE Scan on run  (cost=0.00..2812.50 rows=41667 width=24)
        Filter: (relative_workflow_run_number <= 30)

Hmm, when I try to add a join with the repository CTE, I get an error
ERROR:  rpc error: code = Internal desc = github: rpc error: code = Internal desc = 'List' call for table 'github_actions_repository_workflow_run' is missing 1 required qual: column:'repository_full_name' operator: =

I don't understand what's going on under the hood in steampipe, so I'm just going to work around it with an additional CTE that filters to the default branch.

Odd! It definitely worked as a filter when I committed it. I'd bet some Steampipe change between versions broke it. It was treading on unstable ground a bit as a hack to work around a joining issue (which I never followed up with and wrote up…). I wonder if the join approach would work now. Hmm.

Maybe also a reason to pin the Steampipe version.