Array of enum is not supported

const CustomerInfo = enum{
    profile,
    address,
};
const Application = struct {
  name: [] const u8,
  description: [] const u8,
  requirements: [] CustomerInfo,
}

error: cannot get value of type modules.application.types.CustomerInfo     @compileError("cannot get value of type " ++ @typeName(T));

Should be fixed in both the master and zig-0.13 branches.


How to fine-tune the pre-trained models?

I would like to fine-tune your pre-trained models with indoor datasets.
How to load both pose models and depth models checkpoints at training stages?

Are you familiar with how tensorflow fine-tuning works in general?


Chore fix partial

The problem is when using type a = Partial<b> typescript find that a is an alias for Partial with T generics,
then it parse this line and return Partial as the type name,
and then when we are calling tjs.createGenerator.createSchema to generate that schema it can't find Partial in our api.d.ts file and return the wrong schema
Review this without whitespaces

 TS Schema Validator issues


Modified host regex to match alternative syntax

The following host rule syntax is valid within traefik:
"Host(`subdomain.domain.com`,`subdomain2.domain.com`,`subdomain3.domain.com`)"

This configuration was incorrectly parsed previously, and the 'Host' portion
of regex is safe to remove based on the "if 'Host' in value:" check.

This is a good change. The same change also need to be applied to the check_service_t2 version btw.

Hi @dchidell - I waited too long to approve this. I just went through my tests now as I was initially resistant to this PR, but it is sound.
@mbjurstrom patched it up in a seperate PR to handle the pure python implementation of this image I brought forth in 6.0.0
Thanks for your work!


TypeError: init_process_group() got multiple values for keyword argument 'backend'

训练13b模型时，报这个错误，有人遇到过吗
WARNING:torch.distributed.run:

Setting OMP_NUM_THREADS environment variable for each process to be 1 in default, to avoid your system being overloaded, please further tune the variable for optimal performance in your application as needed.

Traceback (most recent call last):
File "src/train.py", line 393, in
main()
File "src/train.py", line 163, in main
model_args, data_args, training_args = parser.parse_args_into_dataclasses()
File "/opt/conda/lib/python3.8/site-packages/transformers/hf_argparser.py", line 332, in parse_args_into_dataclasses
obj = dtype(**inputs)
File "", line 114, in init
File "/opt/conda/lib/python3.8/site-packages/transformers/training_args.py", line 1255, in post_init
and (self.device.type != "cuda")
File "/opt/conda/lib/python3.8/site-packages/transformers/training_args.py", line 1618, in device
return self._setup_devices
File "/opt/conda/lib/python3.8/site-packages/transformers/utils/generic.py", line 54, in get
cached = self.fget(obj)
File "/opt/conda/lib/python3.8/site-packages/transformers/training_args.py", line 1550, in _setup_devices
self.distributed_state = PartialState(backend=self.xpu_backend)
File "/opt/conda/lib/python3.8/site-packages/accelerate/state.py", line 129, in init
torch.distributed.init_process_group(backend="nccl", **kwargs)
TypeError: init_process_group() got multiple values for keyword argument 'backend'
Traceback (most recent call last):
File "src/train.py", line 393, in
main()
File "src/train.py", line 163, in main
model_args, data_args, training_args = parser.parse_args_into_dataclasses()
File "/opt/conda/lib/python3.8/site-packages/transformers/hf_argparser.py", line 332, in parse_args_into_dataclasses
obj = dtype(**inputs)
File "", line 114, in init
File "/opt/conda/lib/python3.8/site-packages/transformers/training_args.py", line 1255, in post_init
and (self.device.type != "cuda")
File "/opt/conda/lib/python3.8/site-packages/transformers/training_args.py", line 1618, in device
return self._setup_devices
File "/opt/conda/lib/python3.8/site-packages/transformers/utils/generic.py", line 54, in get
cached = self.fget(obj)
File "/opt/conda/lib/python3.8/site-packages/transformers/training_args.py", line 1550, in _setup_devices
self.distributed_state = PartialState(backend=self.xpu_backend)
File "/opt/conda/lib/python3.8/site-packages/accelerate/state.py", line 129, in init
torch.distributed.init_process_group(backend="nccl", **kwargs)
TypeError: init_process_group() got multiple values for keyword argument 'backend'

训练13b模型时，报这个错误，有人遇到过吗 WARNING:torch.distributed.run:
Setting OMP_NUM_THREADS environment variable for each process to be 1 in default, to avoid your system being overloaded, please further tune the variable for optimal performance in your application as needed.
Traceback (most recent call last): File "src/train.py", line 393, in main() File "src/train.py", line 163, in main model_args, data_args, training_args = parser.parse_args_into_dataclasses() File "/opt/conda/lib/python3.8/site-packages/transformers/hf_argparser.py", line 332, in parse_args_into_dataclasses obj = dtype(**inputs) File "", line 114, in init File "/opt/conda/lib/python3.8/site-packages/transformers/training_args.py", line 1255, in post_init and (self.device.type != "cuda") File "/opt/conda/lib/python3.8/site-packages/transformers/training_args.py", line 1618, in device return self._setup_devices File "/opt/conda/lib/python3.8/site-packages/transformers/utils/generic.py", line 54, in get cached = self.fget(obj) File "/opt/conda/lib/python3.8/site-packages/transformers/training_args.py", line 1550, in _setup_devices self.distributed_state = PartialState(backend=self.xpu_backend) File "/opt/conda/lib/python3.8/site-packages/accelerate/state.py", line 129, in init torch.distributed.init_process_group(backend="nccl", **kwargs) TypeError: init_process_group() got multiple values for keyword argument 'backend' Traceback (most recent call last): File "src/train.py", line 393, in main() File "src/train.py", line 163, in main model_args, data_args, training_args = parser.parse_args_into_dataclasses() File "/opt/conda/lib/python3.8/site-packages/transformers/hf_argparser.py", line 332, in parse_args_into_dataclasses obj = dtype(**inputs) File "", line 114, in init File "/opt/conda/lib/python3.8/site-packages/transformers/training_args.py", line 1255, in post_init and (self.device.type != "cuda") File "/opt/conda/lib/python3.8/site-packages/transformers/training_args.py", line 1618, in device return self._setup_devices File "/opt/conda/lib/python3.8/site-packages/transformers/utils/generic.py", line 54, in get cached = self.fget(obj) File "/opt/conda/lib/python3.8/site-packages/transformers/training_args.py", line 1550, in _setup_devices self.distributed_state = PartialState(backend=self.xpu_backend) File "/opt/conda/lib/python3.8/site-packages/accelerate/state.py", line 129, in init torch.distributed.init_process_group(backend="nccl", **kwargs) TypeError: init_process_group() got multiple values for keyword argument 'backend'

有可能是transformers版本的问题
您是基于我们提供的docker环境运行的嘛，或者您的transformers和pytorch版本是什么

有可能是transformers版本的问题
您是基于我们提供的docker环境运行的嘛，或者您的transformers和pytorch版本是什么

基于官网docker镜像跑的

import torch
print(torch.version)
2.0.0+cu117
import transformers
print(transformers.version)
4.29.0.dev0

降低transformers和pytorch版本和train文件下的requirements.txt一样，就可以了，这个docker镜像有点坑呀

我降低了transformers和pytorch版本也不行，最后把train文件下的requirements.txt全部安装了才可以跑。


Arrows gets twice position:absolute

https://popper.js.org/docs/v2/tutorial/#arrow suggests this call:

  My tooltip

and
#arrow,
#arrow::before {
  position: absolute;
  width: 8px;
  height: 8px;
  background: inherit;
}

As far as I can see, the arrow modified assigns the element with id="arrow" to state.elements.arrow. The appyStyles modifier sets state.elements.arrow.style.position='absolute'.
This means, that by following the tutorial the position style for the arrow-element is set twice to absolute: once using CSS and once by Javascript.
Please adjust either the tutorial, not to recommend setting explictly #arrow, #arrow::before { position: absolute }, or the arrow/applyStyle modifiers not to set for the arrow-element position: absolute.
E.g. the example shall set position: absolute for #arrow::before, but not for #arrow itself.

Can you make this issue at https://github.com/floating-ui/popper.js.org? For documentation, issues in this repo should now pertain to Floating UI. Thanks!

I will prefer if the JavaScript code is modified not to set position: absolute.  This means deleting some code in applyStyles and (probably) arrow modifiers.
The rationale is, that the change to CSS would simplify the CSS evaluation, but not reduce the size of the transferred size.  Deleting code in the aforementioned modifiers will lead to less data transmitted to the browsers.

Can this be reopened?

We can't change Popper now, it'd be a breaking change and is getting only bugfixes atm. Floating UI doesn't have this issue though


How to do the navigation after state changed?

I have a very simple requirement for a Redux, React and Redux-Router application. That is a simple login page. After user input the username and password, I dispatch the the parameters to the loginAction.
              <LoginForm
                login={(username, password) =>
                  dispatch(login(username, password))
                } />

                export default connect(select)(Login);

In the loginAction, I do some validation by an async API. When the success callback is called, we should let location navigate to the home page. I have no idea, where should I put my 'change location' code, in action, reducer or container (smart react component)? Would you guys provide some detail examples?

The action creator for the login action is good place to trigger the location change. Redux router provices an action for that in your case it could look like, dispatch(pushState(null, '/dashboard').

Thanks @ferdinandsalis , that makes sense. It will be better add this tip into the example.

My page, to which I do navigation, uses the state which is updated after receiving data from server. Therefore, emitting navigation from action creator races with actual state updating. The question title sounds very specific and it's super interesting what the standard solution without throwing effects from reducers or switching to Elm architecture.


26/stop watching blocks

close #26

Remove the balance and wallet components as they are currently not relevant for this application.
Stop logging on every block.
Remove some stuff that we do not use from App.js really I would like to remove everything we do not use, but I tried to contain myself since this was not really the issue, and also there seems like somebody likes to leave stuff in a "commented out state" instead of removing it.

I am a fan of keeping stuff as simple as possible and only keeping the stuff required for the currently implemented features.
Like:

not keeping something because we might need it later - instead, add it later if and when that times coms

also there seems like somebody likes to leave stuff in a "commented out state" instead of removing it.

Who is this somebody, let's punish them! haha.
Now seriously, I feel the same way. I think we should remove (instead of commenting out) everything we don't need.
If we need some scaffold-eth stuff in the future, we can just copy it from the source.

Tested and everything seems to be working as before.
Merging this will make sleep better this weekend :P


Resolve AddSensor and AddEffector config

Resolves useful parameters of implementations of the AddEffector and AddSensor entity initializers, meaning that their values can be sourced from DslComponents.
Affects:

SshCommandEffector's command and executionDir
SshCommandSensor's command and executionDir
CreatePasswordSensor's passwordLength and acceptableChars
JmxAttributeSensor's objectName, attribute and defaultValue

@sjcorbett One thing you should probably do here is move AddSensor to a different package, perhaps org.apache.brooklyn.core.sensor instead? Also, would there be any benefit gained by making the initializers be EntityAdjunct objects, supporting configuration properly etc.

@grkvlt @neykov Thanks for your comments. This whole approach is flawed because it doesn't survive rebind. Entity initialisers have been written to fire once, which is unfortunate because it's counterintuitive when used alongside everything else in a blueprint. I will explore the suggestion of using EntityAdjuncts.


[Bug] Leftover text on the "You can sleep now!" text

Not sure if i'm wording this right but there seems to be leftover text showing.

Thanks for the report, seems I made an oopsie and managed to miss it.
The screenshot helped understand the issue. ^-^
Closed by e14b837c048b7cd95869295571898cf828602c14


add xlsum_ja

Description
related: https://www.notion.so/stabilityai/Consider-XLSum-13e12b678c2b47408951d9e04515c056?pvs=4

Add a filtered Japanese subset of XLSum based on ROUGE-2, where PaLM 2 uses.

Introduce ROUGE-2 based on Mecab Tokenizer
Filtered data based on 15-gram overlap as PaLM 2 did.

link to dataset: https://huggingface.co/datasets/mkshing/xlsum_ja
link to the script: https://gist.github.com/mkshing/d6371cbfdd50d4f352cee247fd4dd86a

sample scripts
python main.py \
    --model hf-causal \
    --model_args $MODEL_ARGS \
    --tasks "xlsum_ja" \
    --num_fewshot "1" \
    --output_path "result.json"

About XLSum
From the original dataset

We present XLSum, a comprehensive and diverse dataset comprising 1.35 million professionally annotated article-summary pairs from BBC, extracted using a set of carefully designed heuristics. The dataset covers 45 languages ranging from low to high-resource, for many of which no public dataset is currently available. XL-Sum is highly abstractive, concise, and of high quality, as indicated by human and intrinsic evaluation.

From PaLM 2

XLSum (Hasan et al., 2021), which asks a model to summarize a news article in the same language in a single sentence, in Arabic, Bengali, English, Japanese, Indonesian, Swahili, Korean, Russian, Telugu, Thai, and Turkish.

TODO

[x] Add the filtered train set
[x] Add scores for existing models
[x] update readme

@polm-stability thank youu!

@mkshing if you don't mind, could you wait for my review before merging this PR?
I would finish the review and provide my comments tomorrow 🙏

@leemengtw sure! Thanks!


Setting shuffle mode on Sonos resets repeat mode

When using media_player.shuffle_set, the Sonos platform reset's the media player's repeat setting. This may be a bug in how it's utilizing SoCo's play mode API?
Repro
Player is playing with repeat set to ON. media_player.shuffle_set is called with shuffle set to true.
Expected:
Media player should then be set to repeat: on and shuffle: on.
Actual:
Media player is set to repeat: off and shuffle: on.
Tested with 0.67.0.

This is more of a "known limitation" than a bug. The simplistic code is here: https://github.com/home-assistant/home-assistant/blob/0.67.0/homeassistant/components/media_player/sonos.py#L795
Personally, I am not going to work on this before SoCo/SoCo#600 lands.

👍

If you turn on shuffle and then turn on repeat, is it the same problem but reversed?  Or is that a valid workaround for now?


WeakMap remove .clear()?

From Microsoft/TypeScript#10695, for some reason TSJS-lib-generator is picking up .clear() on WeakMap, though the ChakraCore team indicate it is not exposed to JavaScript land (see Microsoft/TypeScript#1539)

lib.es6.d.ts is not generated by the tool in this repo, it is hand-written instead. This issue should be fixed in the TS main repo.


Honour horizontal prop in exported FlatList

Pass the horizontal prop from the exported FlatList component down to the underlying React Native FlatList, in the same way the exported ScrollView does. Fixes #1

Could you change this to the tsx file? The js file is just a build file and should be gitignored.

Around like 444: https://github.com/nandorojo/react-native-anchors/blob/master/src/index.tsx

🤑 thanks!

Fixed in 0.2.2


API and Cookie Authentication in the same Application

If one want to use the bundle in an application where user can authenticate per API (responding with a JSON body containing the token) and per form login (sending token as Cookie) the Lexik\Bundle\JWTAuthenticationBundle\Security\Http\Authentication\AuthenticationSuccessHandler cannot be used.
The reason is that the token is removed from the JSON response if there are any cookie providers configured (see here).
It would be nice if this could be changed.

I think adding a boolean parameter to the AuthenticationSuccessHandler constructor would do the trick, so that one is able to modify/decorate/extend/replace the service definition and use it.
Would you be interested to work on this?

But the class is marked as @final.

@chalasr I have created a PR ;-)


done #1184

Pull Request
Description
Please include a summary of the changes and the related issue.
Closes #1184
Type of change

[ ] Adding a new Resource
[ ] Adding a new Category
[ ] Documentation enhancement or fixes
[x] Website enhancement or fixes

Checklist:

[x] I read carefully CONTRIBUTING.md
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation

Screenshots (if appropriate):
Please add screenshots to help explain your changes.

Additional

Just reduce the opacity of the links a little bit but not too much.

Can I see the result?

I mean any screenshot when hovered.

@jfmartinz please check now, thank you.

Provide the screenshot, we dont have preview it, thans


Avoid double callbacks in Rails >= 4.1

This PR provides the same solution like https://github.com/rails/protected_attributes/pull/78 but I've added a test.
I wasn't able to use any person model combination to reproduce the problem that's why I've added the NestedBattle model

Thanks

Do you think you could release version 1.1.4 with this fix?


What should I modify to work with PRO version?

I am using PRO and what should I modify to use it?
I can access the device and compile but got following error when I ran the test-viewer
frame_get_one: libusb_bulk_transfer returned -7

Hi, do you have a link to that "PRO version"?

@zougloub Yes : https://www.thermal.com/compact-series.html

At least there are modifications to perform for the 320 x 240 resolution, as dimensions are hard-coded in here. Who knows what else changed...


MWPW-142006 - Enable repo-sync for graybox

Enable CC repo-sync for CC graybox repo

Resolves: MWPW-142006

@arshadparwaiz If this ready to be merged to stage, can you add the "ready for stage" label, does it need verification or is a trivial change?
IF it needs verification, please add the label and ask someone to verify and they will add the "verified" label.
The process is mentioned in https://github.com/adobecom/cc/wiki

@salonijain3 This cannot be verified before merging as it runs within github. That said, it has been validated in bacom repo. A copy of that script is now being created in other repos. Hope that provides some context.
https://github.com/adobecom/bacom/pull/191

@sukamat Could you confirm if this PR can be merged in main or if it needs some verification to be done before merging to main?
If It can be merged in main could you add "Ready for main" label
CC: @salonijain3

@arshadparwaiz could you validate the action and set the label as requested ?

This github workflow is verified and working fine.
https://github.com/adobecom/cc/actions/runs/8653039191/job/23727321412
cc: @aishwaryamathuria @salonijain3 @sukamat


MB-12058 Remove usages of AuditableAppContextFromRequest

Jira ticket for this change
Summary
AuditableAppContextFromRequest is no longer being used, so it is being removed.
I didn't touch AppContextFromRequest since I saw it was being used inside of AuditableAppContextFromRequestWithErrors.
Did I remove the correct thing?
Did I update the comment correctly?
Setup to Run Your Code

💻 You will need to use two separate terminals to test this locally.
Terminal 1
Start the UI locally.
make client_run

Terminal 2
Start the Go server locally.
make server_run

Additional steps

Login to both the customer and the office app and make sure things work.
I would also check that the server tests pass ok for this PR.
Verification Steps for Author
These are to be checked by the author.

[x] Request review from a member of a different team.
[x] Have the Jira acceptance criteria been met for this change?

Messages

:book:
:link: MB-12058

  Generated by :no_entry_sign: dangerJS against 33b859566688e0272cbfb45f844efe4d6a36f2c8


Live: decide what to do about bind address

Now that we have a lot of addresses in some of our binaries, we should rename the address variable to bind. We also should support a full address as parameter for the Rosetta server.

@awfm9 Could you elaborate? What's with the bind address?
IMO regarding bind addresses, we always want to allow for specifying the host and port. IIRC currently we're only allowing to specify the port, and the host is always <IP_ADDRESS>.

Decided against this after all. Conflicting short flags make it less nice.

WDYM by Conflicting short flags? Isn't it better to have an address flag like for the other servers, for consistency? It also might be necessary for Coinbase to be able to bind on something else than <IP_ADDRESS>.


Can't save headings in Dojo details

Every time I try to add a heading whilst editing the Dojo details (tested on multiple Dojo pages) the heading appears in the text editor but when saved, saves as a paragraph.
This is also happening when any heading tag is added in the source editor of the 'edit Dojo' page.

I believe this is due to sanitize-html defaults tags that we use in cp-dojos-service's ´service.js´
https://github.com/CoderDojo/cp-dojos-service/blob/master/service.js#L23
https://github.com/apostrophecms/sanitize-html#what-are-the-default-options
Could you try with a h3 or lesser to confirm ?

Okay, h3 works but only in the text editor, not the source editor.

I can get h3 to work in source editor; but once the editor is opened again, it reverse the h4+ to p tags. At that point, it's a configuration discrepancy between the editor and the backend.
There is a reason why h1/h2 are not allowed, it's global consistency of the dojo page; however we shouldnt let users choose that options if that's the case.


Check for empty files when merging benchmarks

Fixes #189

@danielStrobl I've tested this locally and pretty sure it works but maybe you can double check before we merge.

Thanks, I'll take a look at that


Use opaque rendering pipeline for alpha hash materials

Note: Recommended to be merged after https://github.com/godotengine/godot/pull/61880, as shadows will look significantly better with that PR.
This has several benefits:

Transparency sorting issues inherent to alpha blending no longer occur.
Alpha hash materials can now cast shadows (also works with GeometryInstance3D Transparency's property for alpha hash materials).
Higher performance.

This closes https://github.com/godotengine/godot/issues/61882.
Testing project: test_alpha_hash_1.zip
Preview (with https://github.com/godotengine/godot/pull/61880 on top)

TODO

[ ] Figure out if a special shadow shader #ifdef can be used to compute the noise pattern in shadow texture space, rather than in view space. This would prevent the shadow map when flickering when the camera moves or rotates. In the meantime, enabling FXAA, TAA or increasing shadow blur can mitigate this flickering.

Is such an #ifdef currently available? See https://github.com/godotengine/godot-proposals/issues/4443.

Seems fine to me.
@Calinou How bad does it look on its own (i.e. without https://github.com/godotengine/godot/pull/61880)? As I commented their, I don't think we should replace the current hash with a screen-spaced hash. If this looks okay without a fix to the hashing, then I am okay to merge it now, otherwise we should wait

Thanks!


The Letter Y

So whenever I search for anything with the letter Y, it kicks me out of the storage terminal. It has made it very troublesome to grab dyes or other things with the letter Y. Any idea why this is?

Nevermind. It was a keybind I had. It was "searching nearby inventory for items." My bad.


Problems with latex files

Hi,
syntastic seems to be unable to find any .tex checker and thus I get the following error whenever one should be run:
"letter.tex" 156L, 5767C
Error detected while processing function <SNR>39_BufReadPostHook:
line    2:
E117: Unknown function: syntastic#log#debug
Error detected while processing function <SNR>39_BufEnterHook:
line    1:
E117: Unknown function: syntastic#log#debug

:SyntasticInfo output:
Syntastic version: 3.7.0-75 (Vim 704, Linux)
Info for filetype: tex
Global mode: active
Filetype tex is active
The current file will be checked automatically
Available checkers: -
Currently enabled checkers: -

However, both chktex as well as lacheck are in my $PATH:
$ which chktex
/usr/bin/chktex
$ which lacheck
/usr/bin/lacheck

No problems with other filetypes/checkers. I found this related (?) issue and disabled all other plugins and used a rather minimal .vimrc:
set nocompatible
call pathogen#infect()

" syntastic
set statusline+=%#warningmsg#
let g:syntastic_check_on_open = 1

To no effect. Thanks for any help!

Sorry, found the problem. Somehow a setlocal runtimepath found its way in a filetype plugin (those I did not disable..). Closed.


SPM install: crash on duplicate Firebase instances ('-[FBLPromise HTTPBody]: unrecognized selector sent to instance')

Step 1: Describe your environment

Xcode version: 13.2
Firebase SDK version: 8.9.1
Installation method: Swift Package Manager
Firebase Component: Analytics, Crashlytics
Target platform(s): iOS

Step 2: Describe the problem
We switched from CocoaPods to SPM, passing from Firebase 7.10.0 to 8.9.1 to support SPM installation.
Also, we added the SDK with 2 dependencies:

one from the main app, in "Project", adding Firebase as a package (exact version: 8.9.1)
the other from a local package that uses Firebase Crashlytics as a dependency, with the same version:

// swift-tools-version:5.3
// The swift-tools-version declares the minimum version of Swift required to build this package.

import PackageDescription

let package = Package(
    name: "Logger",
    platforms: [
        .iOS(.v13)
    ],
    products: [
        // Products define the executables and libraries a package produces, and make them visible to other packages.
        .library(
            name: "Logger",
            targets: ["Logger"]),
    ],
    dependencies: [
        // Dependencies declare other packages that this package depends on.
        .package(name: "Firebase",
                 url: "https://github.com/firebase/firebase-ios-sdk.git",
                 .exact("8.9.1")),
    ],
    targets: [
        // Targets are the basic building blocks of a package. A target can define a module or a test suite.
        // Targets can depend on other targets in this package, and on products in packages this package depends on.
        .target(
            name: "Logger",
            dependencies: [
                .product(name: "FirebaseCrashlytics", package: "Firebase"),
            ]),
        .testTarget(
            name: "LoggerTests",
            dependencies: ["Logger"]),
    ]
)

Steps to reproduce:
The crash occurs a few moments after launching the app (not immediately at startup).
We get the following stack in the console:
2022-01-24 18:21:05.806363+0200 fiverr[89505:1842636] -[FBLPromise HTTPBody]: unrecognized selector sent to instance 0x6000021f3a80
2022-01-24 18:21:05.808785+0200 fiverr[89505:1842219] Attempted to create a task in a session that has been invalidated
2022-01-24 18:21:05.814879+0200 fiverr[89505:1842636] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[FBLPromise HTTPBody]: unrecognized selector sent to instance 0x6000021f3a80'
*** First throw call stack:
(
	0   CoreFoundation                      0x0000000114f86ba4 __exceptionPreprocess + 242
	1   libobjc.A.dylib                     0x000000010ed76be7 objc_exception_throw + 48
	2   CoreFoundation                      0x0000000114f95811 +[NSObject(NSObject) instanceMethodSignatureForSelector:] + 0
	3   CoreFoundation                      0x0000000114f8b0ac ___forwarding___ + 1433
	4   CoreFoundation                      0x0000000114f8d1d8 _CF_forwarding_prep_0 + 120
	5   GoogleDataTransport                 0x000000010d7a4080 -[GDTCCTUploadOperation updateNextUploadTimeWithResponse:forTarget:] + 96
	6   GoogleDataTransport                 0x000000010d7a338a __64-[GDTCCTUploadOperation sendURLRequestWithBatch:target:storage:]_block_invoke + 74
	7   FBLPromises                         0x000000010d3e5345 __56-[FBLPromise chainOnQueue:chainedFulfill:chainedReject:]_block_invoke.63 + 85
	8   FBLPromises                         0x000000010d3e493a __44-[FBLPromise observeOnQueue:fulfill:reject:]_block_invoke_2 + 106
	9   libdispatch.dylib                   0x0000000116439848 _dispatch_call_block_and_release + 12
	10  libdispatch.dylib                   0x000000011643aa2c _dispatch_client_callout + 8
	11  libdispatch.dylib                   0x0000000116441530 _dispatch_lane_serial_drain + 1239
	12  libdispatch.dylib                   0x00000001164420bc _dispatch_lane_invoke + 436
	13  libdispatch.dylib                   0x000000011644e472 _dispatch_workloop_worker_thread + 900
	14  libsystem_pthread.dylib             0x0000000117038074 _pthread_wqthread + 326
	15  libsystem_pthread.dylib             0x0000000117036ffb start_wqthread + 15
)
libc++abi: terminating with uncaught exception of type NSException

and then:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[FBLPromise HTTPBody]: unrecognized selector sent to instance 0x6000021f3a80'
terminating with uncaught exception of type NSException
CoreSimulator 783.5 - Device: iPhone 13 (0056FD0E-7AD1-46B6-B968-AD7C85F5B48B) - Runtime: iOS 15.2 (19C51) - DeviceType: iPhone 13

I saw a bunch of tickets with the same crash, but not with the same implementation as ours (both in main app & dependency on a local package).
Also, we had a few warning about duplicate implementations:
objc[89505]: Class GDTCCTCompressionHelper is implemented in both /Users/frederic.adda/Library/Developer/CoreSimulator/Devices/0056FD0E-7AD1-46B6-B968-AD7C85F5B48B/data/Containers/Bundle/Application/77E71BB3-A379-46DE-B28C-58E1C42C3CAB/fiverr.app/Frameworks/GoogleDataTransport.framework/GoogleDataTransport (0x10d7ce000) and /Users/frederic.adda/Library/Developer/CoreSimulator/Devices/0056FD0E-7AD1-46B6-B968-AD7C85F5B48B/data/Containers/Bundle/Application/77E71BB3-A379-46DE-B28C-58E1C42C3CAB/fiverr.app/fiverr (0x109467320). One of the two will be used. Which one is undefined.

There are still a few pods remaining (not Firebase), maybe they have a common dependency with some Firebase / Google libs:
  pod 'Braintree/Core', '4.36.1'
  pod 'Braintree/Apple-Pay', '4.36.1'
  pod 'JSONModel', '1.8.0'
  pod 'MBProgressHUD', '~>0.9'
  pod 'UICircularProgressRing', '1.8.4'
  pod 'GoogleMLKit/LanguageID', '1.0.0'
  pod 'SwiftGen', '~> 6.0'
  pod 'Appboy-iOS-SDK', '4.3.2'

How could I avoid issues of duplicate Firebase instances?
Thanks for your help!

Yep, your suspicion is correct. If you look at the Podfile.lock, you'll see that MLKitCommon, a GoogleMLKit dependency, depends on GoogleDataTransport which Firebase also depends upon.
I'll close, but feel free to continue discussion here.

Thanks Paul.
So it means I can't have that lib GoogleMLKit (which is Cocoapods only) along with Firebase under SPM?

Right. GoogleMLKit will not work with a Firebase SPM distribution.  I don't quite follow the second question. What is the main app and what is the local package?  I suspect it should be fine as long as everything is defined in SPM and not mixed with other package managers.

The second question was about this, but I guess you answered it. Thanks!

we added the SDK with 2 dependencies:

one from the main app, in "Project", adding Firebase as a package (exact version: 8.9.1)
the other from a local package that uses Firebase Crashlytics as a dependency, with the same version


hwmv2: port STM32L5 SoCs and boards

CI is failing for nucleo_f722ze and another stm32 board, not part of this conversion but were converted previously

CI is failing for nucleo_f722ze and another stm32 board, not part of this conversion but were converted previously

It is actually failing on main branch as well. We'll fix it there.


Make propritary fields not indexed

Hi
I am trying to add some proprietary fields to the elastic serilog sink. But the fields should not be indexed.
I have created a template to use for this. But still the dynamic fields added with an enritcher using logEvent.AddOrUpdateProperty makes the fields indexed. Is there any way I can get this proprietary  fields into ES where they are not indexed ?
"mappings": {
"default": {
"dynamic_templates": [
{
"string_fields": {
"match": "*",
"match_mapping_type": "string",
"mapping": {
"type": "text",
"index": false,
"norms": false,
"fields": {
"raw": {
"type": "keyword",
"index": false,
"ignore_above": 256
}
}
}
}
}
],
"properties": {
"message": {
"type": "text",
"index": true
},
"subject": {
"type": "text",
"index": true
},
"logger": {
"type": "text",
"index": true
},
}
}

Do check that the mapping is applied successfully and take into account that it will only use it on a new index. If that is all the case, then check with maybe Elastic how to apply the correct mapping. This might have been changed with the different versions of ES. But first, check if it is there and applied correctly.


Use Material Icon Theme as default icon theme

The current file icon themes included with VS Code (Minimal and Seti) look dated and have fewer icons than Material Icon Theme. Including Material Icon Theme with VS Code and maybe even using it as the default File Icon Theme would be a good idea imo.

I vote for that too. But I think - better to install automatically most downloaded file icon theme plugin upon installing VS code

Sorry , we have no plans for that. It's easy for users to install the material icon theme if they prefer it over the seti theme.


Missing device configuration: Minoston Outdoor Dimmer Plug

Checklist

[X] It is not in the configuration DB

[X] It was not merged recently or has a pending PR

Which device is missing?
Minoston Outdoor Dimmer Plug
Manufacturer ID
0x0312
Product Type
0xff07
Product ID
0xff03
Firmware Version
1.0
Is the device listed on the Z-Wave Alliance website?
https://products.z-wavealliance.org/products/4254?selectedFrequencyId=2
Do you have a manual?
https://products.z-wavealliance.org/products/4254/pics

@zwave-js-bot import config 4254 from zwa

The bot has created a starter template, but that usually needs to be cleaned up and aligned to our style guide.
If you'd like to help, you can create a PR on the branch in the bot's PR.

Ok never mind. We do have a file, it just needs another fingerprint added.


remove ilmn-tes namespace when not used

Summary
Removed unnecessary ilmn-tes schema namespace in expressions.
Part B of superseding #115
Commits
1eb0e04d7fd1d76ef4002e6e70899a67c60ff652 @mr-c Removed ilmn-tes namespace when not used
6d07a57669cde3196f24d14d11aa1a4f3b7a0e3f @alexiswl updated dummy file tool to specify ilmn-tes resources that had not been added.

Thank you @alexiswl and @skanwal !
Though I still wonder about those Illumina extensions. Are they always required when running CWL on Illumina's platform? Or can the standard ResourceRequirement be used? If that is so, is there documentation on how that mapping works on their platform?

Are they always required when running CWL on Illumina's platform? Or can the standard ResourceRequirement be used? If that is so, is there documentation on how that mapping works on their platform?

For fpga boards, they're definitely a requirement.
The compute types can be found here: https://help.ica.illumina.com/project/p-flow/f-pipelines#compute-types. I don't know how it works when the ilmn resource requirement isn't specified and is not in the list of compute types provided, so I've generally just provided it to be safe but also added in the ramMin and coresMin to improve portability of other cpu tools.

Yeah, the extension for FPGA makes a lot of sense. Can you ask your ICA contact about the mapping?

Thank you @alexiswl and @skanwal !
Though I still wonder about those Illumina extensions. Are they always required when running CWL on Illumina's platform? Or can the standard ResourceRequirement be used? If that is so, is there documentation on how that mapping works on their platform?

the illumina extensions are not required. When CPU and Memory is specified, the engine will find the best matching instance for you that meets your cpu and/or memory requirements. If the default does not suite your needs then use the extensions to override the default.
When CPU and instance-type are both specified, the instance-type has higher priority.
You can also suppress the warning (from cwltool) about nested structure of the illumina extension by flattering it as described here

The tier extension allows a user to determine if a tool is allowed to run on a AWS spot instance right?


Upgrade react-transition-group to v2

Description of changes:
react-transition-group update from v1 to v2
Related issues (if any):
Not able to build a project if using the latest version of react-transition-group.
Checks:

[x] Please confirm yarn run lint ran successfully
[x] Please confirm that only /src and /examples/src are committed
[x] [if new feature] Please confirm that documentation was added to the README.md

I've run the app in your branch and for whatever reason the images are messed up when i run the demo app:

Sorry, that chance should have never touch master. Gonna revert.

i only checked out your branch to test it before merging and that's where I noticed the issue.

It's already reverted. Please feel free to merge whenever you can.

Getting errors after merging your PR with latest changes.  Do you have time to check on it?

Yes, let me try and let you know.
On Wed, 18 Jul 2018 at 11:31, Sandra<EMAIL_ADDRESS>wrote:

Getting errors after merging your PR with latest changes. Do you have time
to check on it?
[image: screen shot 2018-07-18 at 10 30 02 am]
https://user-images.githubusercontent.com/1676003/42872778-b9caae74-8a75-11e8-8b63-500c8710e9dc.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jossmac/react-images/pull/238#issuecomment-405870752,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACxVO15WKJHnHswRoQ4IXidkK0uNgEl7ks5uHwB0gaJpZM4Utbon
.

--
Cheers,
Filipe Costa
Software Engineer
MSc. in Computer Science - UFCG
BSc. in Computer Science - UFCG
Berlin - Germany
filipescosta.com http://www.filipescosta.com

I actually think I just needed to update my local repo, works fine for me now.

Ok.
On Wed, 18 Jul 2018 at 11:38, Sandra<EMAIL_ADDRESS>wrote:

I actually think I just needed to update my local repo, works fine for me
now.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jossmac/react-images/pull/238#issuecomment-405872601,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACxVOzuP-aTIy3v0dqAJuHoCYXswfCs8ks5uHwH5gaJpZM4Utbon
.

--
Cheers,
Filipe Costa
Software Engineer
MSc. in Computer Science - UFCG
BSc. in Computer Science - UFCG
Berlin - Germany
filipescosta.com http://www.filipescosta.com

is this a breaking change?

Thanks for the PR!
Can we release a new version with this changes? :pray:

yup, im just going over a few more changes so it can go out in one release.

What’s missing? Is there’s something related with this pr?

no, unrelated changes


[WIP] Order listing

Description
- As a: testDFC producer
- On page: new page /orders
- I want to be able to do: See a list of orders containing my products across all platform
If the order contains product from different products as well, I should not see other producers' data. Only mine.
WIP Mockups

Acceptance Criteria & Tests
TODO

@Alcoz @RaggedStaff @lecoqlibre I have a few questions about orderlines before I can finish this issue for the prototype.

an orderline can have a weight different than the weight displayed in the catalog (cases of products like cheese, meat...) : was this taken into account in v1.8?

I see sale sessions are linked to shipping and pickup methods  by quantities. Am I correct to say that quantity refers to the number of shipping options available through that sale session?

beside customer categories and addresses I don't see anything else describing the customer. Can we add the name, email and maybe phone number or was there a reason to leave it aside? I know OFN for example will hide these details from producers in some cases for privacy issues or competitive ones (some hubs don't want their producers to have direct contact with customers). But there is a setting in the platform to allow producers to see them. So when the permission is not given, OFN returns the field with "hidden" in value, otherwise info is shown. And in case of delivery it can be useful to be able to contact the customer.

An "Orderline" has a relation "hasQuantity" linked to a "QuantitativeValue" where a unit can be attached
I don't understand your comment as SaleSession are linked to "ShippingOption" by relation "hasOption". However, I don't understand why there is a relation "quantity" on "SaleSession" and on "ShippingOption". For me, it could be removed.
A customer is an agent that orders something. The class "Agent" have almost all the information you ask, I just see that an enterprise don't have a name.

@Alcoz @RaggedStaff @lecoqlibre @simonLouvet @sankarom My notes from our discussion yesterday:

we need to update the ontology to add weight on products
this affects both products sold by weight/volume and by unit/item as it can be usefull for logistics
@Alcoz will organize a meeting when he is back in August to organize this change
@simonLouvet will wait for this ontology update before updating the prototype

5J


Issue with react-tree-walker

i use material-ui + react-async-bootstrapper
implement react ssr, In the development environment, using react ssr to report an error, the production environment is normal

Warning: Rendering <Context.Consumer.Provider> is not supported and will be removed in a future major release. Did you mean to render <Context.Provider> instead?
Warning: Rendering <Context.Consumer.Consumer> is not supported and will be removed in a future major release. Did you mean to render <Context.Consumer> instead?
TypeError: Cannot read property 'dense' of undefined
    at Object.eval [as children] (webpack:///./node_modules/@material-ui/core/ListItem/MergeListContext.js?:27:31)
    at recursive (/Users/ender/learning/github/react-cnode/node_modules/react-tree-walker/dist/react-tree-walker.js:129:41)
    at /Users/ender/learning/github/react-cnode/node_modules/react-tree-walker/dist/react-tree-walker.js:153:26
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:189:7)

Your Environment 🌎

Tech
Version

Material-UI
v3.9.2

React
v16.8.3

Browser
chrome

react-async-bootstrapper
v2.1.1

I found that deleting the import List from '@material-ui/core/List' component will not give an error.

@chnliquan Do you have a minimal reproducible example?

@joshwooding https://github.com/chnliquan/react-cnode
This problem occurs in development mode. This problem does not occur after I delete the List component. The production environment will not go wrong whether or not it contains a List component.

@chnliquan You are using the react-tree-walker dependency. They don't support the new context API: https://github.com/ctrlplusb/react-tree-walker/issues/47. But more importantly, it's only advised for advanced users that know what they are doing: https://github.com/ctrlplusb/react-tree-walker#disclaimer. Since you are opening an issue on Material-UI side, I would guess that you are only interested in something that works. So I would advise you to remove this dependency.
We have no leverage over this problem. I'm closing.

@oliviertassinari this problem only exists with the development environment, the production environment is no problem, If there is a problem, the behavior of the development environment and the production environment should be the same?

I do react ssr need to use this package for data synchronization. If you suggest me to remove, are there any other solution suggestions?

@chnliquan react-tree-walker dependency is likely legacy, they don't support the context, probably not the hooks either 🤔. Have you tried Next.js? Apollo was using a strategy closed to react-tree-walker, they have stopped doing it for this very problem. They are now rendering the tree x times until they reach all the leaves.

@chnliquan Did you resolve this problem?


remove_auto_segment does not persist

Binary Ninja Version
2.4.2950-dev
Describe the bug
When I call bv.auto_remove_segment, save my bndb, and open it back up, the removed segment reappears.
Additionally the removed segment remains in the feature map, even after refreshing the feature map.
To Reproduce
Steps to reproduce the behavior:

Open a raw binary with “Open with Options.”
Manually put all the parts of the raw binary where they need to be with add_user_segment.
Remove the original segment with auto_remove_segment.
Save bndb
Close Binja
Reopen bndb

Expected behavior
The original segment is gone.
Observed Behavior
The original segment re-appears.
Screenshots
N/A
Version and Platform (required):

Binary Ninja: Dev 2.4.2950
OS: Ubuntu 20.04
Version [e.g. 20.04]

Additional context
Your issue template asks for binary ninja version twice :)

'auto' segments are created by the loader. When reopening a file or database the loader recreates the auto segments. This is why the API remove_auto_segment does not persist.
With the new MemoryMap API and Segment Model, we now provide a mechanism to disable segments. The new segment map, with the disabled segment persists as well through save/load. For example:
Show the current memory map and names for each object:

print(bv.memory_map)

Disable a segment by name:

bv.memory_map.set_memory_region_enabled('origin@0x9028', False)

Fixed in 4.2.5758.


DOTNET 2.1 with CockroachDB 2.1.1 using Npgsql 4.0.3

Just installed cockroachDB 2.1.1 and running .NET core 2.1 with the example code on:
https://www.cockroachlabs.com/docs/stable/build-a-csharp-app-with-cockroachdb.html
Cockroach itself appears fine as we imported a test mariaDB database into with ZERO issues (great job btw!), but trying out the C# code from above results in:
cockroachdb-test-app# dotnet run
Initial balances:
Unhandled Exception: System.InvalidCastException: Can't cast database type bigint to String
at Npgsql.NpgsqlDefaultDataReader.GetFieldValue[T](Int32 column) in C:\projects\npgsql\src\Npgsql\NpgsqlDefaultDataReader.cs:line 154
at Cockroach.MainClass.Simple(String connString) in /root/cockroachdb-test-app/Program.cs:line 45
at Cockroach.MainClass.Main(String[] args) in /root/cockroachdb-test-app/Program.cs:line 16

Exe
netcoreapp2.1
cockroachdb_test_app

Thank you!

I transferred this to the docs repo. @BramGruneir, can you validate this small change?

Yep, the change LGTM.


Invalid config for 'dohome_rgb' at configuration.yaml

I am aware of the issue and ensure that the syntax is latest for the yaml. Invalid config is still being encountered.
The main error log:

Followed by another two log entries:

Other info:

Running on Home Assistant OS
The custom component is downloaded via HACS
The config/configuration.yaml file shows the following, where 7ED0 is the last 4 chars of the MAC address of the device

# Loads default set of integrations. Do not remove.
default_config:

# Load frontend themes from the themes folder
frontend:
  themes: !include_dir_merge_named themes

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

light living_room:
  - platform: dohome_rgb
    sids:
      - 7ED0

Questions:

The device is connected but not in pairing model, is that a requirement?
From the error point of view looks like it is not because of variable/argument but rather some function/component calls isn't working? Any experience on this type of issue?
Let me know which direction I should be looking at to troubleshoot the issue?

I am quite new to custom components, especially the troubleshooting, thank you for your understand and help in advance

Hi! Regarding your first question, the device must be connected to wifi and configured. For the others, the configuration seems to be in a broken format:
light living_room:
  - platform: dohome_rgb
    sids:
      - 7ED0

should be
# remove living_room
light:
  - platform: dohome_rgb
    sids:
      - '7ed0' # lowercase is better

At the moment I haven't implemented entity naming through the configuration, I'll probably add it later. For now I can only recommend to configure without naming, and then set what via UI.

Checked it again and yes, you're right. There is an error in the code, I will fix it


the app not connect Bluetooth

Hi,I have a problem,my mobile phone can be paired bluetooth,but the app not connect Bluetooth.
Can you help me?

Hi.
If you want to connect a Bluetooth device,
you should pair your smartphone with the device first.
Did you pair a Bluetooth device?

Hi , I have a problem too , my mobile phone paired with Bluetooth ( HC-06) ...but not connect Bluetooth device . Can you help me ?

Hi, I'm so sorry for late reply.
The IRION-HID Commander finds a bluetooth connection which is named "Proxy".
Therefore, please change the name of bluetooth module to "Proxy" and try again.
Thank you.


Abandoned Project? Lacking Security Updates

Hi.
Doesn't look like this has been updated since February. And just this September, there were security updates to Python per https://pythoninsider.blogspot.com/2022/09/python-releases-3107-3914-3814-and-3714.html .
Looks like it's stuck at Python <IP_ADDRESS>694 and not the current 3.10.7 .
So is this project abandoned?
thanks.

Definitely not abandoned. Community support is key to maintaining projects like this. Please file a Pull Request for the impacted Python version/libraries to get this updated.

Yes, if you have the knowledge and concern please send a pull request. My priorities are not always going to be aligned with my ability to maintain projects that hundreds or thousands of users install.
it's untenable long term for one person to support projects like this without others helping.

I'll be addressing this soon.

https://github.com/macadmins/python/releases/tag/v<IP_ADDRESS>712
https://github.com/macadmins/python/releases/tag/v<IP_ADDRESS>716
https://github.com/macadmins/python/releases/tag/v<IP_ADDRESS>716


Ensure cdf/pdf/rvs works for non-scalar params

Codecov Report
Attention: Patch coverage is 85.00000% with 6 lines in your changes are missing coverage. Please review.

Project coverage is 83.66%.  Consider uploading reports for the commit b75d1fe to get more accurate results

Files
Patch %
Lines

preliz/distributions/studentt.py
71.42%
6 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #383      +/-   ##
==========================================
+ Coverage   83.65%   83.66%   +0.01%
==========================================
  Files          64       64
  Lines        5854     5842      -12
==========================================
- Hits         4897     4888       -9
+ Misses        957      954       -3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[BUG] I am getting below issue is there anything wrong i am doing here?

🐛 Bug Report

I am trying to understand how it works. i have created sample.js file for write operation and when i run i got below isssu please assit
Lib version: Latest
Steps To Reproduce

Code:
// construct a streaming XLSX workbook writer with styles and shared strings
const options = {
filename: './streamed-workbook.xlsx',
useStyles: true,
useSharedStrings: true
};
const workbook = new Excel.stream.xlsx.WorkbookWriter(options);
worksheet.addRow({
id: i,
name: theName,
etc: someOtherDetail
}).commit();

const workbook = new Excel.stream.xlsx.WorkbookWriter(options);
^
ReferenceError: Excel is not defined
at Object. (/home/prashant/VWork/write.js:7:20)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:12)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
at internal/main/run_main_module.js:17:47

you need to import the module.
for example,
const Excel = require('exceljs')


Fix: Text Overlaping Issue

Describe your changes
Removed h-full Property to Fix the Issue
Issue ticket number and link
Closed #696
Screenshots (if appropriate):

@rohit-rambade can you attach a before image so that we have it as reference after we merge this PR and the production site is changed?


critical dependency error on laravel mix

i got this error, can you explain me how to solve it?
thanks
WARNING in ./node_modules/jquery-easy-loading/dist/jquery.loading.min.js
9:147-174 Critical dependency: the request of a dependency is an expression
@ ./node_modules/jquery-easy-loading/dist/jquery.loading.min.js
@ ./resources/assets/js/app.js
@ multi ./resources/assets/js/app.js ./resources/assets/sass/app.scss

same here @jarloyz u have fixed?


Remove [was Bring back] AllAndCore target

This change broke the AllAndCore target that I added (it removed the lines that specify its requirements, so it is no-op). Was that intentional?
I think it is good idea to have a target that builds everything - plus I really need it so that I can reference latest Fable using Paket's git dependencies. Please please please :pray:

Oh, I see...

Cyclic dependency between FableCore and FableCompilerRelease

Looks like All now builds everything, including FableCore, so I changed the PR just to remove obsolete target that's no longer used :)
This makes my life even easier :+1:

Yeah, since we changed fable-core to typescript it must be compiled anyways most of the times, so I just added the FableCore target to the default build to make sure it works for any user cloning it for the first time :+1: (I still have FableCompilerDebug for quick development builds).
Besides that, probably it's because I'm dumb, but I don't have a complete understanding of how FAKE dependencies work, so I didn't know how to manage the ?==> operator :wink:

I also had only a vague idea about ?==> :baby:


enha: add stratus_version commit sha test case

PR Type
Enhancement, Tests

Description

Added new checks to validate the stratus_version API for both Leader and Follower nodes
Extended existing integration tests to include version validation
Ensured that the git commit hash is present in the version response and has the correct length (7 characters)
Updated test descriptions to reflect the addition of version checks
Improved test coverage for the Stratus node version information

Changes walkthrough 📝
Relevant filesEnhancement

leader-follower-change.test.tsAdd version validation to Leader-Follower integration tests

e2e/cloudwalk-contracts/integration/test/leader-follower-change.test.ts
Added version checks for both Leader and Follower nodes  Extended existing tests to validate stratus_version API  Ensured git commit hash is present and has correct length  Updated test descriptions to reflect new checks

+10/-2

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

Final benchmark:
Run ID: bench-1571175371
Git Info:

Branch: main
Commit: b5c497a
PR: #1900

Configuration:

Target Account Strategy: Default

RPS Stats: Max: 1271.00, Min: 906.00, Avg: 1118.46, StdDev: 61.86
TPS Stats: Max: 1247.00, Min: 962.00, Avg: 1084.05, StdDev: 71.75
Plot: View Plot


Broken service, connection reset by peer

Using Kubernetes v0.8.0, aws cluster, coreos instances, etc.
I noticed that after a few days, my private docker registry becomes unavailable, and I couldn't create new pods using that registry images.
I then started to debug the issue.
From the minion hosting the docker registry:
core@ip-10-136-110-220 ~ $ docker ps | grep registry
9220e376417c        registry:latest                                "docker-registry"      4 days ago          Up 4 days                                                                                k8s_main.f1dac1ea_docker-registry.default.etcd_2aa005ad-97a3-11e4-9654-22000b3b0a76_aa771c47
1eadd9b2ecd7        kubernetes/pause:go                            "/pause"               4 days ago          Up 4 days                                                                                k8s_net.53d8b123_docker-registry.default.etcd_2aa005ad-97a3-11e4-9654-22000b3b0a76_b0200448
core@ip-10-136-110-220 ~ $ docker exec -ti 9220e376417c curl localhost:5000
"\"docker-registry server\""
core@ip-10-136-110-220 ~ $ sudo iptables -t nat -L | grep registry
REDIRECT   tcp  --  anywhere             ip-172-16-131-169.ec2.internal  /* registry-service */ tcp dpt:5000 redir ports 49510
DNAT       tcp  --  anywhere             ip-172-16-131-169.ec2.internal  /* registry-service */ tcp dpt:5000 to:<IP_ADDRESS>:49510
core@ip-10-136-110-220 ~ $ curl ip-172-16-131-169.ec2.internal:5000
"\"docker-registry server\""
core@ip-10-136-110-220 ~ $ curl <IP_ADDRESS>:5000
"\"docker-registry server\""
core@ip-10-136-110-220 ~ $

From the master:
core@ip-10-165-115-237 ~ $ kubecfg -l="name=docker-registry" list services
Name                Labels                 Selector              IP                  Port
----------          ----------             ----------            ----------          ----------
registry-service    name=docker-registry   app=docker-registry   <IP_ADDRESS>      5000

core@ip-10-165-115-237 ~ $ curl <IP_ADDRESS>:5000
curl: (56) Recv failure: Connection reset by peer
core@ip-10-165-115-237 ~ $ curl <IP_ADDRESS>:49510  # from minion iptables
"\"docker-registry server\""
core@ip-10-165-115-237 ~ $

The kubernetes service fails to map <IP_ADDRESS>:5000 to <IP_ADDRESS>:49510.
Any idea on how to resolve that issue temporarily ?
Also, what information do you need to figure out why it eventually broke?

Can you run 'kubectl get endpoints registry-service' and put the output in here?

There is no endpoints resource available in v0.8.0:

Possible resources include pods (po), replication controllers (rc), services (se), minions (mi), or events (ev).

Did you want to see the service details ?
core@ip-10-165-115-237 ~ $ kubectl get -o yaml se registry-service
apiVersion: v1beta1
containerPort: registry-port
creationTimestamp: 2015-01-09T01:59:30Z
id: registry-service
kind: Service
labels:
  name: docker-registry
namespace: default
port: 5000
portalIP: <IP_ADDRESS>
protocol: TCP
resourceVersion: 115
selector:
  app: docker-registry
selfLink: /api/v1beta1/services/registry-service?namespace=default
sessionAffinity: None
uid: 266ac625-97a3-11e4-9654-22000b3b0a76
core@ip-10-165-115-237 ~ $

Can you check master's iptables?

core@ip-10-165-115-237 ~ $ fleetctl list-machines
MACHINE         IP              METADATA
02b8b139...     <IP_ADDRESS>     role=minion
65e50e34...     <IP_ADDRESS>  role=minion
f4f1901f...     <IP_ADDRESS>  role=master

core@ip-10-165-115-237 ~ $ sudo iptables -t nat -L | grep registry
REDIRECT   tcp  --  anywhere             ip-172-16-131-169.ec2.internal  /* registry-service */ tcp dpt:5000 redir ports 45695
DNAT       tcp  --  anywhere             ip-172-16-131-169.ec2.internal  /* registry-service */ tcp dpt:5000 to:<IP_ADDRESS>:45695

core@ip-10-165-115-237 ~ $ fleetctl ssh f sudo iptables -t nat -L | grep registry
REDIRECT   tcp  --  anywhere             ip-172-16-131-169.ec2.internal  /* registry-service */ tcp dpt:5000 redir ports 45695
DNAT       tcp  --  anywhere             ip-172-16-131-169.ec2.internal  /* registry-service */ tcp dpt:5000 to:<IP_ADDRESS>:45695

core@ip-10-165-115-237 ~ $ fleetctl ssh 6 sudo iptables -t nat -L | grep registry
REDIRECT   tcp  --  anywhere             ip-172-16-131-169.ec2.internal  /* registry-service */ tcp dpt:5000 redir ports 49510
DNAT       tcp  --  anywhere             ip-172-16-131-169.ec2.internal  /* registry-service */ tcp dpt:5000 to:<IP_ADDRESS>:49510

core@ip-10-165-115-237 ~ $ kubecfg -l="app=docker-registry" list pods
Name                Image(s)            Host                Labels                Status
----------          ----------          ----------          ----------            ----------
docker-registry     registry            <IP_ADDRESS>/     app=docker-registry   Running

core@ip-10-165-115-237 ~ $ kubecfg -l="name=docker-registry" list services
Name                Labels                 Selector              IP                  Port
----------          ----------             ----------            ----------          ----------
registry-service    name=docker-registry   app=docker-registry   <IP_ADDRESS>      5000

core@ip-10-165-115-237 ~ $

Maybe a few days ago, my docker-registry was on the minion <IP_ADDRESS>, then got moved to <IP_ADDRESS> but kubernetes forgot to change the master (and other minions) iptables with the new ip ?

I'm facing something similar.  But for me it is from the beginning of cluster not after a few days.  It seems the endpoint is wrongly registered in etcd.  kube-proxy with v=4 says this.
Jan 14 08:44:59 core-01 kube-proxy[17910]: I0114 08:44:59.566038   17910 proxier.go:105] Accepted TCP connection from <IP_ADDRESS>:45458 to <IP_ADDRESS>:34729
Jan 14 08:44:59 core-01 kube-proxy[17910]: I0114 08:44:59.566082   17910 roundrobin.go:101] NextEndpoint.  service: registry-service.  srcAddr: <IP_ADDRESS>:45458. Endpoints: map[kubernetes:[<IP_ADDRESS>:8080] registry-service:[1
Jan 14 08:44:59 core-01 kube-proxy[17910]: I0114 08:44:59.566145   17910 proxier.go:74] Mapped service "registry-service" to endpoint <IP_ADDRESS>:5000

core@core-01 ~ $ kubectl get endpoints registry-service
F0114 09:12:20.762528   25660 get.go:82] unable to output the provided object: error: unknown type &api.Endpoints{TypeMeta:api.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:api.ObjectMeta{Name:"registry-service", Namespace:"default", SelfLink:"/api/v1beta1/endpoints/registry-service?namespace=default", UID:"84fbfd85-9b55-11e4-8422-08002725bf01", ResourceVersion:"785", CreationTimestamp:util.Time{Time:time.Time{sec:63556772033, nsec:0x0, loc:(*time.Location)(0xc0b480)}}, Labels:map[string]string(nil), Annotations:map[string]string(nil)}, Endpoints:[]string{"<IP_ADDRESS>:5000"}}
core@core-01 ~ $ kubectl get endpoints kubernetes
F0114 09:12:27.777758   25701 get.go:82] unable to output the provided object: error: unknown type &api.Endpoints{TypeMeta:api.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:api.ObjectMeta{Name:"kubernetes", Namespace:"default", SelfLink:"/api/v1beta1/endpoints/kubernetes?namespace=default", UID:"", ResourceVersion:"11", CreationTimestamp:util.Time{Time:time.Time{sec:0, nsec:0x0, loc:(*time.Location)(nil)}}, Labels:map[string]string(nil), Annotations:map[string]string(nil)}, Endpoints:[]string{"<IP_ADDRESS>:8080"}}
core@core-01 ~ $ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 08:00:27:25:bf:01 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global dynamic eth0
       valid_lft 83648sec preferred_lft 83648sec
    inet6 fe80::a00:27ff:fe25:bf01/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 08:00:27:fa:c7:50 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::a00:27ff:fefa:c750/64 scope link
       valid_lft forever preferred_lft forever
4: flannel0: <POINTOPOINT,UP,LOWER_UP> mtu 1472 qdisc pfifo_fast state UNKNOWN qlen 500
    link/none
    inet <IP_ADDRESS>/16 scope global flannel0
       valid_lft forever preferred_lft forever
5: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1472 qdisc noqueue state UP
    link/ether 56:84:7a:fe:97:99 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::5484:7aff:fefe:9799/64 scope link
       valid_lft forever preferred_lft forever
7: vethf7cbb79: <BROADCAST,UP,LOWER_UP> mtu 1472 qdisc pfifo_fast master docker0 state UP qlen 1000
    link/ether d6:11:58:96:a1:0d brd ff:ff:ff:ff:ff:ff
    inet6 fe80::d411:58ff:fe96:a10d/64 scope link
       valid_lft forever preferred_lft forever
9: veth98c56fa: <BROADCAST,UP,LOWER_UP> mtu 1472 qdisc pfifo_fast master docker0 state UP qlen 1000
    link/ether 6a:76:f7:33:60:d9 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::6876:f7ff:fe33:60d9/64 scope link
       valid_lft forever preferred_lft forever

<IP_ADDRESS>:5000 is probably wrong.  My question is: why and how was this messed up?

For some reason this ip is on docker0 range.  I think it is supposed to be in flannel0.
core@core-01 ~ $ ip route
default via <IP_ADDRESS> dev eth0  metric 1024
<IP_ADDRESS>/24 dev eth0  proto kernel  scope link  src <IP_ADDRESS>
<IP_ADDRESS> dev eth0  scope link  metric 1024
<IP_ADDRESS>/24 dev eth1  proto kernel  scope link  src <IP_ADDRESS>
<IP_ADDRESS>/16 dev flannel0  proto kernel  scope link  src <IP_ADDRESS>
<IP_ADDRESS>/24 dev docker0  proto kernel  scope link  src <IP_ADDRESS>

But I'm still missing how kubelet returns this magical IP address.

Just for the record, I found kubelet creates a network container and this guy has NetworkSettings when inspecting.
It seems my issue is that docker0 has the same subnet range between master and minion.

Yeah, you need to make sure that the CIDR for your services and for your
worker nodes are distinct from each other and distinct from the overall
network of your host machines.
We need to provide a better tool for diagnosing network problems.  It's
been stated, but there is still work to do there.
Brendan
On Jan 14, 2015 3:08 AM, "Hitoshi Harada"<EMAIL_ADDRESS>wrote:

Just for the record, I found kubelet creates a network container and this
guy has NetworkSettings when inspecting.
It seems my issue is that docker0 has the same subnet range between master
and minion.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/3422#issuecomment-69901297
.

Issue is still occurring, the docker registry suddenly stopped working a few hours ago:
core@ip-10-67-168-16 ~ $ kubectl get services | grep registry
registry-service       name=docker-registry                      app=docker-registry     <IP_ADDRESS>        5000

core@ip-10-67-168-16 ~ $ sudo iptables -L -t nat | grep <IP_ADDRESS>
REDIRECT   tcp  --  anywhere             ip-172-16-5-110.ec2.internal  /* registry-service */ tcp dpt:5000 redir ports 55035
DNAT       tcp  --  anywhere             ip-172-16-5-110.ec2.internal  /* registry-service */ tcp dpt:5000 to:<IP_ADDRESS>:55035

core@ip-10-67-168-16 ~ $ kubectl get pods | grep registry
docker-registry                        <IP_ADDRESS>         main                registry                               <IP_ADDRESS>/     app=docker-registry                  Running

core@ip-10-67-168-16 ~ $ fleetctl list-machines
MACHINE         IP              METADATA
593411b0...     <IP_ADDRESS>  role=minion
7dd5cba6...     <IP_ADDRESS>  role=minion
fad196e4...     <IP_ADDRESS>    role=master

core@ip-10-67-168-16 ~ $

iptables record has not been updated after the pod switched minion.

the iptables shouldn't change when a pod moves.  iptables maps you to the
kube-proxy, which is responsible for keeping track of where the pod is.  Is
kube-proxy running?  Can you dump its logs and see what it thinks is going
on?
What happens if you hit  <IP_ADDRESS>:55035 directly?
--brendan
On Thu, Jan 29, 2015 at 9:15 PM, Adrien Lemaire<EMAIL_ADDRESS>wrote:

Issue is still occurring, the docker registry suddenly stopped working a
few hours ago:
core@ip-10-67-168-16 ~ $ kubectl get services | grep registry
registry-service       name=docker-registry                      app=docker-registry     <IP_ADDRESS>        5000
core@ip-10-67-168-16 ~ $ sudo iptables -L -t nat | grep <IP_ADDRESS>
REDIRECT   tcp  --  anywhere             ip-172-16-5-110.ec2.internal  /* registry-service / tcp dpt:5000 redir ports 55035
DNAT       tcp  --  anywhere             ip-172-16-5-110.ec2.internal  / registry-service */ tcp dpt:5000 to:<IP_ADDRESS>:55035
core@ip-10-67-168-16 ~ $ kubectl get pods | grep registry
docker-registry                        <IP_ADDRESS>         main                registry                               <IP_ADDRESS>/     app=docker-registry                  Running
core@ip-10-67-168-16 ~ $ fleetctl list-machines
MACHINE         IP              METADATA
593411b0...     <IP_ADDRESS>  role=minion
7dd5cba6...     <IP_ADDRESS>  role=minion
fad196e4...     <IP_ADDRESS>    role=master
core@ip-10-67-168-16 ~ $
iptables record has not been updated after the pod switched minion.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/3422#issuecomment-72155316
.

kube-proxy logs: http://sprunge.us/jgaZ
one of the minion was inaccessible (couldn't ssh), so I stopped it, and the aws autoscaling group restarted another minion. None of the pods running on the previous minion got updated, and their status switched to Unknown.
I had to stop & create the registry pod and service (kubectl update wouldn't do anything)
The service got a new ip assigned, but the new iptables record made is again using the old minion ip, which doesn't exist anymore.
systemctl restart kube-proxy doesn't seem to change.

@brendandburns happened again:
core@ip-10-233-140-125 ~ $ kubectl get services | grep registry
registry-service       name=docker-registry                      app=docker-registry     <IP_ADDRESS>      5000

core@ip-10-233-140-125 ~ $ sudo iptables -L -t nat | grep <IP_ADDRESS>
REDIRECT   tcp  --  anywhere             ip-172-16-193-196.ec2.internal  /* registry-service */ tcp dpt:5000 redir ports 44601
DNAT       tcp  --  anywhere             ip-172-16-193-196.ec2.internal  /* registry-service */ tcp dpt:5000 to:<IP_ADDRESS>:44601

core@ip-10-233-140-125 ~ $ curl <IP_ADDRESS>:44601
curl: (56) Recv failure: Connection reset by peer

core@ip-10-233-140-125 ~ $ fleetctl ssh c 'sudo iptables -L -t nat | grep registry'
REDIRECT   tcp  --  anywhere             ip-172-16-193-196.ec2.internal  /* registry-service */ tcp dpt:5000 redir ports 42694
DNAT       tcp  --  anywhere             ip-172-16-193-196.ec2.internal  /* registry-service */ tcp dpt:5000 to:<IP_ADDRESS>:42694

core@ip-10-233-140-125 ~ $ curl <IP_ADDRESS>:42694
"\"docker-registry server\""

core@ip-10-233-140-125 ~ $

We’re going through old support issues and asking everyone to direct your questions to stackoverflow.
We are trying to consolidate the channels to which questions for help/support are posted so that we can improve our efficiency in responding to your requests, and to make it easier for you to find answers to frequently asked questions and how to address common use cases.
We regularly see messages posted in multiple forums, with the full response thread only in one place or, worse, spread across multiple forums. Also, the large volume of support issues on github is making it difficult for us to use issues to identify real bugs.
The Kubernetes team scans stackoverflow on a regular basis, and will try to ensure your questions don't go unanswered.


Access to all pybind from root package

Description of Changes
This makes it so everything exported by pybind is accessible from the root python module.
Test Plan
Built, installed, and verified everything was importable.

This was ez

This was ez


stored xss in code editor

des: your demo website write title is vulnerable to stored cross site scripting.
steps:
visit:https://www.wondercms.com/demo/
and  incode  add this payload
impect:
XSS

@takshal seems you might have found an unsanitized field in the demo.
Generally, we allow admins to execute JS anywhere, but it should be disabled in the demo.
Can you please share a valid image/screenshot? The above doesn't seem to work.
Thanks!

hello team as per your requirement i will attached an image so you can
check it.
On Sat, Nov 28, 2020 at 8:00 PM Robert Isoski<EMAIL_ADDRESS>wrote:

@takshal https://github.com/takshal seems you might have found an
unsanitized field in the demo.
Generally, we allow admins to execute JS anywhere, but it should be
disabled in the demo.
Can you please share a valid image/screenshot? The above doesn't seem to
work.
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/robiso/wondercms/issues/224#issuecomment-735237719,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANCDULRMWBBTTTNJU57ZFA3SSECRJANCNFSM4UFRR4VQ
.

@takshal there is no image attached?

hello
i attached a image of xss please check and if you have another way where i
can send a poc or video please let me know
On Sat, Nov 28, 2020 at 10:09 PM Robert Isoski<EMAIL_ADDRESS>wrote:

@takshal https://github.com/takshal there is no image attached?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/robiso/wondercms/issues/224#issuecomment-735253750,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANCDULT4EUL7GV56TW5B6QDSSERU5ANCNFSM4UFRR4VQ
.

@takshal, please re-check as there is no image.
You can try attaching the image again or sending it to<EMAIL_ADDRESS>

please check your<EMAIL_ADDRESS>mail
On Sun, Nov 29, 2020 at 4:49 PM Robert Isoski<EMAIL_ADDRESS>wrote:

@takshal https://github.com/takshal, please re-check as there is no
image.
You can try attaching the image again or sending it to
<EMAIL_ADDRESS>—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/robiso/wondercms/issues/224#issuecomment-735377393,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANCDULUVC5PZCB26NCBFHUDSSIU5TANCNFSM4UFRR4VQ
.

We communicated through email as this seemed to be an already fixed issue (already reported by two security researchers in the prior days).


Remove deprecated references to categories and fix paths.

These were removed when the API went GA. Also fix a couple typos, we refer to "info types" as InfoTypes in all formal documentation.

@dpebot merge when green


Uploading CSV file fails to load

Please check that this issue hasn't been reported before.

[X] I searched previous Bug Reports didn't find any similar reports.

Expected Behavior
Upload csv file, ask for head, bot prints code results.
Current behaviour
Upload file, ask for head, spins, nothing.
Steps to reproduce
See above.
Possible solution
No response
Which Operating Systems are you using?

[ ] Android
[ ] iPhone/iPad
[ ] Linux
[ ] macOS
[X] Windows

Programming Version
Python 3.10
gpt-code-ui Version
Latest
Acknowledgements

[X] My issue title is concise, descriptive, and in title casing.
[X] I have searched the existing issues to make sure this bug has not been reported yet.
[X] I am using the latest version of gpt-code-ui.
[X] I have provided enough information for the maintainers to reproduce and diagnose the issue.

Works fine for me. Please add some more details and re-open if needed.


Fix NSDictionary <-> metadata codec

This was making the C library to silently drop all our request headers. Which prevented auth :)

Assign metadata->value_length, to prevent all request headers from being dropped :)
Add the "-bin" suffix to the key of binary metadata (and strip it when it's received).
Initialize NSStrings from metadata with ASCII encoding instead of Unicode.

@marcwan This is the fix to the auth issue.

I'm unsure about this automatic handling of binary fields. What if two incoming (from the server) metadata items have the same key, one with -bin and one without? What if our user gives us a string with the key key-bin and a NSData object with the key key? It seems like they'll effectively be coalesced at the other end.

What if two incoming (from the server) metadata items have the same key, one with -bin and one without?

You end up with @{@"key": @[<NSString value>, <NSData value>]}.

What if our user gives us a string with the key key-bin

Ah, right, we have to prevent that, or it'll fool the C library into encoding and decoding the value as base-64.

and a NSData object with the key key?

For this we need to add the "-bin" suffix, per the contract of the C library.
I don't know of a better way to do it without inflicting on the user the pain of turning NSStrings into NSDatas and adding suffixes. The most common case by far will be non-repeated header names, none of which end in "-bin".

This now raises an exception when the user tries to make a call with a header @{@"something-bin": <NSString value>}. If they really really need such a header, they can dump the string into a NSData and set @{@"something-bin": <NSData equivalent value>}. The server would see the same in both cases.


Rethink deploment/releasing

This was one of the first Actions available afaik, the releasing strategy suggested by GitHub was in the beginning to create a v4 branch and then a v4 tag. Since tags are connected to the GitHub Actions marketplace. This is confusing and causes Git to not function probably (shows a warning and is confused), since there is a tag and a branch with the same name.
Not sure which way we should go, open to hear your thoughts in it.
@dscho

Hmm. I would not name the branch e.g. "v4", which would suggest that it won't change. That's the role of a tag, I'd think.
On the other hand, if there are bugs, it could be desirable to update "v4" transparently. I.e. if an existing workflow uses "v4", the user might want to have that refer to a repaired Action.
However, this is more an issue for workflows that are expected to be unchanged. That's distinctly not the case for action-tmate, which is intended to be used to debug non-working workflows, and removed as soon as things are debugged enough.
Therefore, it is my gut feeling that a good strategy would be to develop this Action in a single main branch, every once in a while tagging official versions.

Yeah makes sense, let's stay with version v3, and hold master in sync with v3 so we don't confuse other users even more. Maybe even mark v3 as our default branch, what do you think?
The whole system as you pointed out of reproducible builds, is for us not fully relevant, because this Action never stays in a workflow file forever.

Updated the v3 branch again, for the records and the future:
git checkout v3
git pull origin master
git push origin heads/v3


Review if Conference Sections should have unique slugs

The Review section throws an error if multiple Conference Sections exist with the same slug:
https://github.com/caktus/pycon/blob/develop/symposion/reviews/views.py#L89

That field is a Django models.SlugField and it looks like Django now correctly enforces uniqueness on the slug — when I try creating a new Section with the same slug as an existing Section, I get the error message in the Django admin interface:
Section with this Conference and Slug already exists

I am therefore closing this issue in the hopes that this will not recur!


bugfix: mysql insert on update duplicate sensitive case not matched

… matched

[ ] I have registered the PR changes.

Ⅰ. Describe what this PR did

当数据库column为大写，而sql为小写时，读取parameter时匹配不上，造成了前镜像的sql为select * from table导致了全表扫描，后镜像也进行了一次全表扫描的bug

Ⅱ. Does this pull request fix one issue?

fixes #4909
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #4912 (bdb6ee6) into develop (8ec5ccd) will increase coverage by 0.00%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##             develop    #4912   +/-   ##
==========================================
  Coverage      49.03%   49.03%
  Complexity      4087     4087
==========================================
  Files            736      736
  Lines          25784    25785    +1
  Branches        3180     3180
==========================================
+ Hits           12642    12643    +1
- Misses         11799    11800    +1
+ Partials        1343     1342    -1

Impacted Files
Coverage Δ

...ava/io/seata/common/util/LowerCaseLinkHashMap.java
0.00% <0.00%> (ø)

...source/exec/mysql/MySQLInsertOrUpdateExecutor.java
31.49% <55.55%> (+0.93%)
:arrow_up:

...very/registry/zk/ZookeeperRegisterServiceImpl.java
61.02% <0.00%> (-0.74%)
:arrow_down:

seata-go: https://github.com/apache/incubator-seata-go/issues/700


Improved test coverage of printf()

This PR improves slightly test coverage of the printf() function.

Codecov Report

Merging #3691 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3691      +/-   ##
==========================================
+ Coverage   77.38%   77.38%   +<.01%
==========================================
  Files         100      100
  Lines      139953   139953
==========================================
+ Hits       108297   108303       +6
+ Misses      31656    31650       -6

Impacted Files
Coverage Δ

src/gui_gtk_x11.c
47.69% <0%> (-0.5%)
:arrow_down:

src/ex_cmds2.c
84.49% <0%> (-0.1%)
:arrow_down:

src/undo.c
83.11% <0%> (-0.07%)
:arrow_down:

src/terminal.c
74.41% <0%> (-0.05%)
:arrow_down:

src/channel.c
83.2% <0%> (-0.04%)
:arrow_down:

src/os_unix.c
57.3% <0%> (+0.04%)
:arrow_up:

src/message.c
75.52% <0%> (+0.24%)
:arrow_up:

src/if_xcmdsrv.c
84.35% <0%> (+0.35%)
:arrow_up:

src/gui.c
58.14% <0%> (+0.66%)
:arrow_up:

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 6c8dd39...5b83584. Read the comment docs.


[FALSE-POSITIVE]

Domains or links
Please list any domains and links listed here which you believe are a false positive.

amormisericordioso.cl
berceuse.cl
donaggio.cl
elmejorplato.cl

quickly eliminate this false positive since the mentioned sites are free of malicious files, checked with imunify360 centos server thanks
More Information
How did you discover your web site or domain was listed here?

Website was hacked
Incorrectly marked as Phishing on Phishtank or OpenPhish?
2
Have you requested removal from other sources?
Please include all relevant links to your existing removals / whitelistings.

Additional context
Add any other context about the problem here.
:exclamation:
We understand being listed on a Phishing Database like this can be frustrating and embarrassing for many web site owners. The first step is to remain calm. The second step is to rest assured one of our maintainers will address your issue as soon as possible. Please make sure you have provided as much information as possible to help speed up the process.
Send a Pull Request for faster removal
Users who understand github and creating Pull Requests can assist us with faster removals by sending a PR to mitchellkrogza/phishing repository, on the falsepositive.list file

https://github.com/mitchellkrogza/phishing/blob/main/falsepositive.list
Please include the same above information to help speed up the whitelisting process.

this one showed up on virustotal.com with false positives or income from a long time ago, but these sites are totally clean and secured.


Rename *Context types to *State

KeyboardKit 8.8 renames some service types from Provider to Service. For instance, KeyboardLayoutProvider is now called KeyboardLayoutService.
KeyboardKit 8.9 will rename the remaining service types (KeyboardActionHandler & KeyboardStyleProvider) the same way, to make the naming convention a bit consistent when talking about services.
With this in place, I find it confusing to have Keyboard.Services and Keyboard.State, where Keyboard.State has properties of types named *Context, e.g. KeyboardContext, AutocompleteContext, etc.
So: POLL TIME! Do you think the context types should be renamed from Context to State, which for instance would mean that KeyboardContext would be renamed to KeyboardState?
Leave a 👍 if you do or 👎 if you think the context name convention is better.

Seems like this renaming is the way to go, but OMG the mere thought of it stresses me out.
Renaming the context types would both involve renaming all types with deprecation typealiases, renaming all the references to these types, including in all functions and initializers, with proper deprecations for these as well, etc. Then finally making sure that the docs are all updated, etc.
After renaming the various services, I think this will have to do for now, otherwise people will receive a wall of changes when going from 8 to 9. While I think state is a better name than context, at least all the contexts are consistently named, unlike how the various service types all had different names.
SO...thank you for indicating that this is the way to go. I will however aim for 9.0 to 9.9 to reduce the amount of init arguments, after which this renaming will be easier to perform.

I have given this some thought, and I believe that moving to 10.0 in a year shouldn't involve as many renaming changes as the 8.0 and 9.0 did involve.
I still think "state" is a better name than "context", but the context concept has been used for so long and I don't think keeping it around will be that confusing to people.
Feel free to comment on this if you really think I should change it, and I may reconsider this decision. Changing one's mind isn't such a big deal :)


Merge upstream

Change-Id: I84f234c6c5bbf4d318893166943de62fb87fff69

@0x5b, please bump version in specfile to 2.5.0.


Picture in picture mode

https://developer.android.com/guide/topics/ui/picture-in-picture

This was fixed in v3.0.0

But the native PiP from oreo and above is not resizable, right?

@SebiderSushi On my system (Android P) PiP can have two different sizes. Furthermore Zapp does use resizeable activities and can be used side by side with other apps (if the system does support this feature).


Only include dependencies used for specified targets

We need to fix so we only include and attribute crates that we actually use for the target platforms we ship on. Right now all dependencies are included even if they are for fairly exotic targets that we do not use nor ship (redox, fuchsia).
Would be good to keep the current behavior and include dependencies from all targets, but add being able to specify which targets to include and filter for, including supporting multiple targets.
Could have such a config in about.toml of supported targets, as Cargo doesn't have it itself anywhere yet (though really should have). But would also be useful to be able to specify target to generate for with a --target parameter so one can quickly test a specific target or in CI generate target-specific correct output.
In Rust 1.41 the lockfile should contain the target information also so should then add this support together with the target-filtering in cargo-deny (https://github.com/EmbarkStudios/cargo-deny/issues/63).

Oops, this was fixed in #41


feat: add screen view event after session start

Description

add screen view event after session start

General Checklist

[x] Added new tests to cover change, if needed
[x] Build succeeds using Swift Package Manager
[x] All unit tests pass
[ ] Security oriented best practices and standards are followed (e.g. using input sanitization, principle of least privilege, etc)
[ ] Documentation update for the change if required
[x] PR title conforms to conventional commit style
[ ] If breaking change, documentation/changelog update with migration instructions

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 95.61%. Comparing base (3f3239b) to head (0980f47).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #53      +/-   ##
==========================================
+ Coverage   95.59%   95.61%   +0.02%
==========================================
  Files          35       35
  Lines        1973     1986      +13
==========================================
+ Hits         1886     1899      +13
  Misses         87       87

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Typo in author name (you typed 'N' instead of 'M')

https://github.com/marisabrantley/portfolio/blob/3dfef5db9ab1f13b28f31b5330c45f697561579b/package.json#L7

Good catch! I'm going to make the change and close the issue - thank you!


New examples are missing in the Playground catalog

Expiration time added to redis catalog cache (5 minutes)
Tests updated
resolves #23927
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @TSultanov

R: @damccorm


yAxis no longer accept objects

After upgrading to 0.0.9 this no longer works:
yAxis: {
    title: {
        text: null,
    },
    labels: {
        format: "{value}%"
    },
    max: 100,
    tickInterval: 20
}

If I add it to yAxis as an array it does work, but according to Highcharts docs this should only be needed if there are multiple axes. http://api.highcharts.com/highcharts#yAxis

I have the same issue. It seems to work by moving yAxis configuration in chartConfig.options :
chartConfig = {
    options: {
        yAxis: {
            title: {
                text: null,
            },
            labels: {
                format: "{value}%"
            },
            max: 100,
            tickInterval: 20
        }
    }
}

ok I'll have a look at this. Suggest sticking with 0.0.8 for now.

It seems there is an error in function
deepExtend(destination, source)

error occurs when source var is an object and destination is undefined

I didn't see this ticket when I created a PR... so I'll put this information here which better documents the issue:
TypeError: Cannot read property '<PROPERTY>' of undefined
where the destination is undefined.
this recent change from 0.8 to 0.9 which uses deepExtend instead of angular.copy is what is triggering the issue in the recent change (since deepExtend did not change).
Breaking it down:
This recent change adds a default for xAxis, but no default for yAxis was added.  Not supplying one in the config.options will cause mergedOptions[axisName] to be undefined when axisName is 'yAxis' (which it gets from this array). When it tries to deepExtend the config.yAxis on to that, this issue occurs.

This broke us automatically. Why are we rolling our own deepExtend here? That functionality exists in so many more stable libraries (angular.merge, for example).

Close see #369


Add constructors for concatinating multiple arrays of TornadoNativeType instances

Description
This pull request introduces a new constructor to TornadoNativeTypes, enabling the creation of a single instance by concatenating the contents of multiple array instances.
Backend/s tested
Mark the backends affected by this PR.

[x] OpenCL
[x] PTX
[] SPIRV

OS tested
Mark the OS where this PR is tested.

[x] Linux
[ ] OSx
[ ] Windows

Did you check on FPGAs?
If it is applicable, check your changes on FPGAs.

[ ] Yes
[x] No

How to test the new patch?
The functioality is already tests with the:
tornado-test -V --fast uk.ac.manchester.tornado.unittests.api.TestConcat

Great. i am merging this PR.


Add GroundStateSolver.is_variational() check

What is the expected enhancement?
As discussed in https://github.com/Qiskit/qiskit-nature/pull/510#discussion_r789429305 a utility to check whether the solver used within GroundStateSolver is variational or not could pose useful for the implementation of the BOPESSampler and potentially other scenarios, too.
Such a check should be able to also handle the MinimumEigensolverFactory case in a general approach. For that it may be necessary to combine the implementation of this with #384.
@iuliazidaru would you be interested in tackling this as a follow-up to your other PR?

@mrossinek yes, I'll implement this.

Given #570 returning the minimum_eigensolver from the factory any user of a factory, like the BopesSampler now can, can get this from the factory and do the same Variational instance check that it would do if directly supplied a VQE instance. In this regard maybe such a method is not really necessary - in my mind it would be better for the check to be consistent where you are either given the min_eigsolver directly, or you can get it from the factory and then do the exact same test if its variational. In that regard I don;t think this is needed any more.

I agree with Steve! I have linked this issue to be automatically closed by the PR which refactors the VQE factories accordingly :+1:


Stop directly depending on upstream's peer deps

npm 5.2.0 stops flattening peer dependencies, so our hack of directly depending on eslint-config-airbnb's peer deps won't work anymore. 😢
We should remove those dependencies and switch back to using this install method for consumers.
See: npm/npm#17678

This change was reverted in npm 5.3.0. We are safe... for now.


Make glTFs display well

While we technically have the gLTFs rendering, they look like garbage. Read the threlte to actually get a good understanding of how to insert lights and control the camera in a loaded gLTF, because it's confusing that gLTFs can actually be entire scenes unto themselves.

This was resolved as a part of #92. There are now both fixed lights and lights that move with the camera, and the material of every model is made our brand green before rendering.
https://github.com/KittyCAD/text-to-cad-ui/assets/23481541/bbb52c48-a90f-4b93-b937-973f186a02d6


Add linters and use ament_lint_auto

I still left TODOs for enabling ament_copyright linter once that is able to handle the copyright notices in RViz.

Since this is just a small change to the linters run (and they should be run as part of the Rpr CI), I'm going to skip testing on other platforms.