[CPDEV-96115]-Enabling_strong_crypto_support_by_default

Description
These cipher suites are configuring the server to support a selection of strong and secure cryptographic algorithms for secure communication over TLS (Transport Layer Security).
*
Fixes # (issue)
CPDEV-96115
Security Strength:
These cipher suites prioritize the use of strong cryptographic algorithms, enhancing the security strength of the TLS connections. They provide forward secrecy through the ECDHE key exchange.
Cipher Suite Diversity:
Including a mix of AES-GCM and ChaCha20-Poly1305 cipher suites ensures compatibility with a broader range of clients and provides alternatives in case certain algorithms are vulnerable or less secure.
Solution
Enhanced Security:
The configured cipher suites enhance the security of the TLS communication by using modern cryptographic algorithms and key exchange methods.
Forward Secrecy:
Ephemeral key exchange (ECDHE) ensures forward secrecy, meaning that even if the server's private key is compromised, past communications remain secure.
Compatibility:
The chosen cipher suites strike a balance between security and compatibility.
Performance:
ChaCha20-Poly1305 cipher suites are known for their good performance, which can be beneficial in resource-constrained environments.
*
Test Cases
TestCase 1
Test Configuration:

OS: Ubuntu-20.04

Steps:

Installed a miniha cluster
Installed kube-bench to make KubeMarine CIS aligned.
Run scan using command - kube-bench and check for identifier 1.2.31.

Results:

Before
After

Result used to be Warning
Result shows Pass

Checklist

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] Integration CI passed
[ ] Unit tests. If Yes list of new/changed tests with brief description
[ ] There is no merge conflicts

The another one case is Kubernetes upgrade.
Nothing was changed after upgrade scenario, the security report contains the same Warning
[WARN] 1.2.30 Ensure that the API Server only makes use of Strong Cryptographic Ciphers (Manual)

Ideally, we have to write patch that makes the cluster and new resolved inventory consistent.
https://github.com/Netcracker/KubeMarine/blob/v0.25.1/documentation/internal/Patches.md

Pretty good this time. Still, I suggest to postpone this PR. Coincidentally, new cluster reconfigure procedure is coming #592 that will allow to reconfigure kube-apiserver in one call kubemarine.kubernetes.component.reconfigure_components(kubernetes_nodes, ['kube-apiserver']). You may already test it, but please do not rebase, that PR is going to be forced updated.


mill version fails if buildfile can't be compiled

Reproduce with the following example:
$ echo "ERROR" >> build.sc
$ mill -i version
Compiling /tmp/test/build.sc
build.sc:249: not found: value ERROR
val res_14 = ERROR
             ^
Compilation Failed
$ echo $?
1

Of course, the upper example is trivial and easy to fix. In real life if might be more difficult. E.g. if the buildfile fails because of an mill API change, one might want to use mill version to check which version is used, but that wouldn't work.

As part of https://github.com/lihaoyi/mill/issues/502, we might make it possible to annotated certain entrypoint functions as not depending on the build file. I suspect we may have more of these in future, and it would be nice to be able to write them as a straightforward scala function rather than shoving more logic into the already-pretty-messy arg-parsing-and-initialization logic

There is now an alternative: mill --version


why there isn't a more popular training approach based on exl2.

I'm a bit confused about the basis of your training. Currently, the fastest inference solution is exllamav2, but besides using the original gptq model, it's possible to directly train using autogptq and alpaca_lora_4bit, although it seems there's no way to directly train with exl2.
From what I see, mainstream training either involves training with the original model and then converting it to gptq/exl2, or using bnb 4bit to load the original model. Then, the lora weights trained and the converted gptq/exl2 model are loaded together for inference with exllamav2.
However, loading with bnb4bit/gptq4bit should result in the more loss of original weights than exl2 5/6bits. If lora weights trained on these weights are loaded together with the more accurate exl2, there should be some discrepancies. So, I'm quite curious why there isn't a more popular training approach based on exl2.

The 53 GB vs 70 GB is just the difference in the weights. The 2-bit difference would be next to, say, 48 bits per parameter for gradients, and then you have large batches on top probably, maybe huge attention matrices if you're doing long-range finetuning.. that sort of thing.

"Indeed. That's why I'm puzzled by the lack of attention to training based on the EXL2 format. During training, the required memory can increase significantly. For instance, using a 4-bit quantized training method like GPTQ, and applying gradient checkpoint or LoRA, it's possible to train the basic LLaMa2 70B model with 8x 3090 GPUs (I haven't tried long contexts yet). However, if training is based on BNB 8-bit, the memory requirements explode.
That's why I've always opted for training with GPTQ models.
When I saw that EXL2 supports LoRA, but there isn't a specific training method based on EXL2 format, I was curious: what methods do people use to train LoRA? Is it Transformer+BNB, GPTQ, direct training with original weights, or is there some other, better method?
I'm not an algorithm engineer, but based on my understanding of LoRA, its basic algorithm is based on W+deltaW. Even if deltaW is trained very well, different quantizations will inevitably cause some variations in W, and thus in W+deltaW. Could it be that the level of these differences doesn't lead to significant degradation in the combined model's performance, and that's why there hasn't been a specific focus on developing training methods based on the EXL2 format?"

I do think the 4-8 bit range can have a big impact on the training VRAM and therefore what is even accessible, so it would be worth it IMO. QLora doesn't really offer variable precision. It's not the overall size but rather hitting the ideal breakpoints, and a few GB per card can help there.
@turboderp I'm also curious how hard it would be to implement native auto-differentiation and backpropagation in Exllama, at least for LORA layers, and for decoder-only models like Llama. The math doesn't sound more complicated than what you're already doing I think (heck, the quantization code with Cholesky and inverses sounds way more numerically nasty than auto-diff). If the focus is on Llama-style architectures, you wouldn't need to support arbitrary compute graphs like pytorch auto-diff does, and it can be specialized to LORA layers. Guess you'd need a simple optimizer too (or plain SGD).
It'd be nice to have a training loop independent of all the crap and bloat that transformers + PEFT + Qlora/bnb etc. introduces, not to mention wrapper packages like deepspeed. For instance, there is no pipeline parallel training in conjunction with quantization anywhere, but it could be implemented more easily if the building blocks were present in a more low-level implementation like Exllama, without mucking with a nightmare of dependencies. I think a lot of bloat exists because a lot of the packages are highly generalized, and Llama (and Yi, Mistral, etc.) training options therefore suffer.


Java SimpleDateFormat?

I've been experimenting with all of the "minimal" launchers on F-Droid the last several days.  Unlauncher is my favorite.
The one enhancement I would request is an option to use Java SimpleDateFormats to create both the time and date format on the home screen. Forecastie https://f-droid.org/en/packages/cz.martykan.forecastie/ as an example has a "Custom Date Format" option using SimpleDateFormats.
Currently my date displays as "Sun, M02 28" which is not a format I am accustomed to.
Thanks jkuester for your efforts in creating a clean and simple Android launcher experience.

Thank you for the kind words and for taking the time to log a helpful issue with an example!
Actually, this date format weirdness is caused by some locale changes that were made in Android 11.  A recent (but as of yet unreleased PR) has hopefully fixed this issue: https://github.com/jkuester/unlauncher/pull/35
As of that PR, the date format in Unlauncher should be set to the device's default local (via the SimpleDateFormat).  I hope to get that change released soon!

Closing this since it should have been resolved in v1.1.0.  Please reopen this issue if the problem still persists on the latest version of Unlauncher.


2.4.2 build on android error

Describe the bug
when i try to build my expo app with the latest release on android i get this:
> Task :datadog_mobile-react-native:compileDebugKotlin FAILED
e: file:///Volumes/dev/retails/node_modules/@datadog/mobile-react-native/android/src/main/kotlin/com/datadog/reactnative/FrameRateProvider.kt:43:24 Unresolved reference: postFrameCallback
e: file:///Volumes/dev/retails/node_modules/@datadog/mobile-react-native/android/src/main/kotlin/com/datadog/reactnative/FrameRateProvider.kt:48:49 Unresolved reference: getInstance
e: file:///Volumes/dev/retails/node_modules/@datadog/mobile-react-native/android/src/main/kotlin/com/datadog/reactnative/FrameRateProvider.kt:49:28 Unresolved reference: postFrameCallback
e: file:///Volumes/dev/retails/node_modules/@datadog/mobile-react-native/android/src/main/kotlin/com/datadog/reactnative/FrameRateProvider.kt:55:49 Unresolved reference: getInstance
e: file:///Volumes/dev/retails/node_modules/@datadog/mobile-react-native/android/src/main/kotlin/com/datadog/reactnative/FrameRateProvider.kt:56:28 Unresolved reference: removeFrameCallback

FAILURE: Build failed with an exception.

Reproduction steps
install "@datadog/mobile-react-native": "^2.4.2",
and try to build android app
SDK logs
No response
Expected behavior
be able to build the android app
Affected SDK versions
2.4.2
Latest working SDK version
2.4.1
Did you confirm if the latest SDK version fixes the bug?
No
Integration Methods
Source
React Native Version
0.73.3
Package.json Contents
No response
iOS Setup
No response
Android Setup
No response
Device Information
No response
Other relevant information
seems to be related to FramerateProvider added in 2.4.2

same error

Same here, using 2.4.1 works fine

@wcastand @RamboWasReal @AlbertHernandez
Hello 👋 Thank you for reaching out!
Can you please share your package.json? I am particularly interested in your Expo and React Native packages versions.

Same here, no expo RN v0.74

Same here with
    "expo": "^51.0.0",
    "react-native": "0.74.3",

any update?

Same issue

Same here, no expo, RN v0.74.3

We had to move to version 2.1.0 to resolve @wcastand

was working fine for me until 2.4.2, even 2.4.1
why did you go so far back?
we are on expo router so we don't use react-navigation packages directly at least.

Same issue. Downgrading to 2.4.1 worked for us, very grateful for this issue being raised!

Hi @marco-saia-datadog, I am using react native 0.74.3, expo 51.0.22

Thank you for reaching out, we are addressing the issue in v2.4.3. We can confirm that downgrading to 2.4.1 will solve the issue as for now. We apologise for the inconvenience!

Hey 👋 😃
Version v2.4.3 has been released! Thank you for your patience :)

hi @marco-saia-datadog! experiencing the same kotlin build error under:
"expo": "51.0.32",
"react-native": "0.75.2"

whats the recommended expo/RN version for v2.4.3?


Language client never sends selection range requests even if supported by server

I'm not sure if this is a bug, or it's not implemented, or if I'm just doing something wrong, but I set the selection range capability of my language server to true and added the appropriate callback only for it to never receive selection range requests. I then checked the client capabilities that my server receives and selectionRange is always undefined as well.
I was finally able to get everything working by going into my language client and copy/pasting the default provider implementation into it and then calling languages.registerSelectionRangeProvider(), so I guess it was just never registered?

Selection ranges are only available in the next version of the libraries (e.g. 5.3.0-next.6 for the client and 5.3.0-next.8 for the server)

Please ping if you already use the next version.

To opt into them you need to call client.registerProposedFeatures(); and create the server connection using let connection = createConnection(ProposedFeatures.all);
This is done that way since the API can still change for proposed features.

Yes, I just double checked and can confirm those are the versions being used.

Strange, it works for me:

I hit the breakpoint on my server with the latest version of the libs. Please note that it requires VS Code version 1.35. as well.

Just to clarify, I should have client.registerProposedFeatures() and createConnection(ProposedFeatures.all, ...) even when using the latest versions, right? As long as I add the first one, my server works with or without the second one. This is with the latest insiders.

@mattacosta Yes, it is a requirement because it is not official API yet.

My confusion must be around the finalization process then. In earlier versions, I would expect to need the proposed feature calls, but in the latest version the selection range stuff was moved out of the *.proposed.ts files, so I figured that the API was, well, no longer proposed.

It is still half proposed :-). Sorry for that. reason being is that it is not official in the LSP specification. This happens in August.


grammer changes meaning

This sentence: "Sync only copies the top-level files inside a directory if the recursive flag is false."
Should be: "Sync copies only the top-level files inside a directory if the recursive flag is false."
maybe pedantic, but the first sentence means sync will leave out top level files unless you set recursive to false.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c02ef818-5e53-4582-43a8-22f9f2b2872d
Version Independent ID: b8f45994-4ac2-f124-c613-b82316203b9f
Content: azcopy sync
Content Source: articles/storage/common/storage-ref-azcopy-sync.md
Service: storage
Sub-service: common
GitHub Login: @normesta
Microsoft Alias: normesta

@fdgit
Thanks for your feedback! We will investigate and update as appropriate.

@fdgit
Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.

#signoff


Object reference not set to an instance of an object

When trying to run salus on a go project and after Scan Manifest file I get the mentioned error. I tried with one of my own and another open source project, both fail.
I attach the scan files for you, just in case you need them to give me a hint
Thanks for looking into this
ScanManifest_20220714111446.txt
ScanManifest_20220714110630.txt
.

Sorry this was a known issue due to us trimming the binaries to save space. Please try out the new version 0.1.3 of the tool, that has the fix for this issue.
https://github.com/microsoft/sbom-tool/releases/tag/v0.1.3


Dynamic system prompt

Update the system prompt before generating responses, so that if a variable (such as date and time) is used in the system prompt, it will be kept up to date.
prompt.get_initial_prompt() was also renamed to prompt.build_initial_messages() to more accurately reflect its purpose.
prompt.get_system_prompt_message() was added that only returns the system prompt message string, which prompt.build_initial_messages() now uses.
prompt.get_system_prompt_message() is also used directly in handle_response() to refresh the first entry content of self.messages instead of rebuilding self.messages entirely.
Additionally, both built-in system prompts (default_prompt and chat_prompt) was updated to include the current date and time. I benchmarked it with Llama 3.1 8B, and it does not negatively affect system prompt adherence.

Another awesome improvement, thanks @Jobus0!


build: bump jest and ts-jest versions

Was testing something and bumped these dependencies along the way, so figured I'd push it up as a PR.

nit: is build: correct? Is test: better / more conventional?

Dunno?
https://github.com/pvdlg/conventional-commit-types#commit-types

???


using NSMutableURLRequest instead of NSURLRequest which causes a warning...

... under Xcode 6

This is a dupe of #5 so I'm closing it and will merge #5. Thanks!


Kernell wrong

I have installed a wrong kernell for my rockpro64. The commands line I type are:
`wget: https://github.com/ayufan-rock64/linux-mainline-kernel/releases/download/4.20.0-1083-ayufan/linux-headers-4.20.0-1083-ayufan-g686e1f1aa461_4.20.0-1083-ayufan_arm64.deb
#wget: https://github.com/ayufan-rock64/linux-mainline-kernel/releases/download/4.20.0-1081-ayufan/linux-image-4.20.0-1081-ayufan-ge8f6e497ec01-dbg_4.20.0-1081-ayufan_arm64.deb
#wget: https://github.com/ayufan-rock64/linux-mainline-kernel/releases/download/4.20.0-1083-ayufan/linux-image-4.20.0-1083-ayufan-g686e1f1aa461_4.20.0-1083-ayufan_arm64.deb
#sudo dpkg -i *.deb`
Yes, I hnow, sorry for it, the second command is not a same version than the others.
My question is how to revert to a linux kernel original (4.4) from the original version,
And what kernel are the best for my rock64 if I update a kernel? (for rockpro64 and mmc 32gb)
Thanks in advance and sorry for my english but is not my native language

change-default-kernel.sh or remove old kernels
The 4.4 is best for now.

ok thanks I'll try it


Data page design alignment and accessibility

https://recording-accessibility.ml-trainer.pages.dev/


withoutUndo with opt out

This fixes warnings that happened when the resizing of a row was being triggered by parent action.
In these cases it seems to make sense to just go ahead and record the resizing. The reason we didn't record it before because it could happen on document load and would result in a weird undo history.
The change really should just remove a warning that is printed in some cases. The adding of undo history events should behave exactly the same as when the warning was there.

I ran the failing cypress tests locally and they passed.

Good point @bgoldowsky I added some JSDoc.

Something weird happened with the regression tests here. The ran on the first commit when I added the run regression label. Then when I added a second commit and quickly force pushed a revision to that second commit, the regression tests did not run. Because my only change was to add a comment it doesn't seem worth getting the regression tests to run again.
@tejal-shah I don't think this needs QA review. It is just removing a warning message printed in the console.


Types properties confusion between has_default and allow_null

I am building out nested types and am using validators.Object(allow_null=True) to set properties on a type class. If I create a new instance of the type that uses one of these object validators, it automatically sets the property as one of the required fields, which seems to miss the point of the allow_null parameter.
The code in question where it compiles the list of required fields is here: https://github.com/encode/apistar/blob/0.5.4/apistar/types.py#L38
This calls out to the common validator method has_default, found here: https://github.com/encode/apistar/blob/0.5.4/apistar/validators.py#L54
In order to make this work, I have to set validators.Object(allow_null=True, default=None). Is this intended behavior? I spent quite a long time trying to understand this and tracking it down. It would make more sense to me that if allow_null = True, then it should automatically set default = None or otherwise skip making it a required field.

BTW, I upgraded to 0.5.7 and appreciate the change to allow for true nested types instead of validators.Object().

Not necessarily a given that allow_null=True ought to set default=None, but on balance I think it's almost always what users will actually want, so yup, let's go with this.


telluric_correction call to SIMBAD is fragile

The current call to astroquery SIMBAD in telluric_correction is very fragile, in that it requires a correct (SIMBAD) name for the source (not always provided by the user), and if it cannot find it it returns an empty astropy table which is a weird object.
I've added some code fixes in a queued pull request that raises an issue if no reliable standard name is provided, but this should be revisited to ensure we are making the right expectations of the user.

Just to add to this, telluric_correction takes as an input the name of the standard.  That is, it is this name that is passed to SIMBAD and not the one stored in the FITS header.
So if someone is pyspextool object by object, I am fine requiring them to pass the right name.
This then leaves the batch code.  We could put all the catches were discussed on the call in the batch code?


Use Hamcrest assertions instead of JUnit in tests/integration/config/hocon-mp (#1749)

Part of #1749
Backport 2.x

/trigger


Remove testId property from the public component API

Self Checklist

[ ] I wrote a PR title in English and added an appropriate label to the PR.
[ ] I wrote the commit message in English and to follow the Conventional Commits specification.
[ ] I added the changeset about the changes that needed to be released. (or didn't have to)
[ ] I wrote or updated documentation related to the changes. (or didn't have to)
[ ] I wrote or updated tests related to the changes. (or didn't have to)
[ ] I tested the changes in various browsers. (or didn't have to)

Windows: Chrome, Edge, (Optional) Firefox
macOS: Chrome, Edge, Safari, (Optional) Firefox

Related Issue

Fixes #1959

Summary

Details

Breaking change? (Yes/No)

Yes
References

TODO: Rm additional testId props


How to build and use own version of ToastAPI for submodule?

as per title.
made changes to the api and I want to test them out
basically just need to know the correct way to change the maven dependency to a local one
I tried a direct compile files( "dir/../../Toast-<version>.jar")  but that didn't work

If you build and use your own version of ToastAPI, all modules loaded will use the same, modified version.
You will have to run 2 commands to do a clean build of Toast:
gradlew build generateExternalPatches
and gradlew build.
The resulting file will be under build/libs. Don't forget to change the Toast Version in build.settings before building to avoid conflicts.
What changes did you make to the API? Some changes you can make without a rebuild through a module API call

I was attempting to use avahi instead of dns-sd, since there is no bonjour for linux

the module is still definitely using the maven dependency, not the local build

You can disable Toast's dns-sd from the Toast configuration file under run/toast/config. If you're looking to tunnel a Driver Station instance, you can either configure an Avahi service on your linux system as usual avahi.service (you shouldn't need to rebuild Toast for this, you can do it in your normal userspace), or you can setup a dns-sd proxy on your Driver Station computer with the instructions here.
To change your maven dependency to a local one, use compile fileTree(include: '*.jar', dir: '<ToastDir>'), substituting <ToastDir> for the build/libs directory of your local Toast instance. You will, however, need to add the other following compile dependencies to your build.gradle that Toast itself depends on:
compile 'jaci.openrio.delegate:NetworkDelegate:1.2.1'
compile 'com.grack:nanojson:+'

The buildscript {} portion of your config file should resemble this.
(for your module)
Run ./gradlew clean cleanIdea cleanEclipse.
To build, run ./gradlew build --refresh-dependencies
To get eclipse running, run ./gradlew eclipse --refresh-dependencies. This same step applies for IntelliJ, replacing eclipse with idea

okay, cool. have no experience with this kind of stuff, good to know! thanks

NOTE: Ignore the buildscript {} part of the previous comment. The buildscript {} block present in your existing build.gradle should be file, my apologies

No problem, feel free to reopen the issue if you have any more issues


Adds empty medkits to medical lathe

About the PR
Adds recipes for all the medkits to the medical lathe locked behind biological tech. Wanted to add this so people could make their own medkits to store their meds for better organization. Each cost 300 plastic (3 sheets) and you can craft every kind of medkit.
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl:

add: added medical lathe recipes for all the medkits, they cost 300 plastic, are locked behind biological tech, and are empty

Are these filled?

Are these filled?

No, they are empty

Maybe add suffix so people would understand that this is just container?

Maybe add suffix so people would understand that this is just container?

I'll take a look into adding that

Maybe add suffix so people would understand that this is just container?

I just renamed all the recipes to have "(empty)" at the end, don't know if there is a better way of going about it.

Nah, this is fine.


Add St. Dominic's Sixth Form College to JetBrains

@akhilallamraju First stage of verification passed, official domain for St. Dominic's Sixth Form College is stdoms.ac.uk as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@akhilallamraju Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


PR TEST

PR TEST

[Template] PR Description
In general, github system automatically copies your commit message for your convenience.
Please remove unused part of the template after writing your own PR description with this template.
$ git commit -s filename1 filename2 ... [enter]

Summarize changes in around 50 characters or less

More detailed explanatory text, if necessary. Wrap it to about 72
characters or so. In some contexts, the first line is treated as the
subject of the commit and the rest of the text as the body. The
blank line separating the summary from the body is critical;
various tools like `log`, `shortlog` and `rebase` can get confused
if you run the two together.

Further paragraphs come after blank lines.

**Changes proposed in this PR:**
- Bullet points are okay, too
- Typically a hyphen or asterisk is used for the bullet, preceded
  by a single space, with blank lines in between, but conventions vary here.

Resolves: #123
See also: #456, #789

**Self evaluation:**
1. Build test: [ ]Passed [ ]Failed [*]Skipped
2. Run test: [ ]Passed [ ]Failed [* ]Skipped

**How to evaluate:**
1. Describe how to evaluate in order to be reproduced by reviewer(s).

Add signed-off message automatically by running **$git commit -s ...** command.

$ git push origin <your_branch_name>

:memo: Version: 1.20180820. Thank you for submitting PR #321. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://invain.mooo.com/.

To contributor, We have used 'Signed-off-by:' notation by default to handle the license issues, that result from contributors. Note that 'Is there a Signed-off-by line?' is important because lawyers tell us we must have to it to cleanly maintain the open-source license issues even though it has nothing to do with the code itself.

INFO: You can read if there are misspelled characters at our misspelling check report. Please read http://invain.mooo.com/TAOS-CI/ci/repo-workers/pr-checker/201810250932400.84492611885071-321-1f94d0be669e3bd1194f9f801a57d886595779a1/report/misspelling_result.txt.

:octocat: cibot: @jongpuls, One of the format checkers is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnsuite/TAOS-CI/wiki/.


Date Nanos implementation

Add nanosecond field mapper
https://github.com/elastic/elasticsearch/issues/37755

@codebrain this needs some tests too, similar to https://github.com/elastic/elasticsearch-net/blob/9f0d285904d4c2dc523b8bbc835535662d83f547/src/Tests/Tests/Mapping/Types/Core/Date/DatePropertyTests.cs


postcss.config.js is not resolved correctly unless config: {} is given in options

In https://github.com/postcss/postcss-loader/blob/39638602/lib/index.js#L63, rc.path is only set if options.config is given by the user, instead of defaulting to path.dirname(file) as it seems was the original intent.
This means postcss-loader by default can only find a postcss.config.js relative to process.cwd() instead of one relative to the currently processed file; unless (at least) an empty config object is given in the options.
This is a regression relative to pre-2.0 behavior.

Sloppy.. 😛 I fix asap

Released in https://github.com/postcss/postcss-loader/releases/tag/v2.0.4


Recompilation of entire bundle after each change takes too long.

Recompiling the test bundle after every change and rerunning the entire suite is taking a long time.
The majority of the time taken is recompiling the entire test bundle again from scratch. Would it be a lot of work to implement some sort of webpack-dev-server hot compilation? That way, we could just recompile what is needed as opposed to recompiling from scratch.

I too badly need this. I've tried many schemes but they are very slow.

Can you provide a sample repo with your configuration if possible? Theoretically if each of your test files is an entry it shouldn’t recompile them all on save, only the charged files. An example would be a good start to look at why it isn’t working as expected.

For me, it's "commons.js" that takes forever to build; which I'm guessing is the code being tested.

My recompilation times with Webpack alone are much faster than with Karma, which leads me to believe that the performance loss is due to this plugin.

@stevenvachon are you compiling your tests in a single bundle? or are they different entries in terms of webpack?

@fa-hmad all entries come from karma. I exclude chunking configs while testing.

@fa-hmad Single bundle

I have decided to run webpack-dev-server and karma processes concurrently as opposed to using karma-webpack. Recompilation on file save has gone from 20seconds to 0.2seconds.

For me deleting the cache option from webpack config caused a very significant speedup (12 sec -> 0.8sec)

As karma is now deprecated and coming up on EOL, we are no longer planning on any significant enhancements to this project and are instead going to focus on security updates, stability, and a migration path forward as karma's lifecycle comes to an end.
Thank you for supporting and using this project!


compile error

I'm not sure why laton is unable to handle this repo. (Tikz is named in the error though.) The repo compiles fine on several machines.
http://latex.aslushnikov.com/compile?git=http://github.com/kbeserra/Thesis&target=main.tex

This might happen due to the old version of LiveTex which is currently used on the service (atm it's LiveTex 2012).
I'll update the docker file as I'll have some spare time - but this is unlikely to happen before weekend. I appreciate any help though :)

Thank you! This is not a hurry, I am just happy you have a public deployment so I don't have to bother trying to create my own. So thanks for that!

Great news!
With the new version of Latex-Online, your link compiles successfully!

You da man! Thanks for all your work on this project.
On Thu, May 5, 2016 at 06:01 Andrey Lushnikov<EMAIL_ADDRESS>wrote:

Great news!
With the new version of Latex-Online, your link compiles successfully!
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/aslushnikov/latex-online/issues/11#issuecomment-217136381


Reference documentation is needed for new 1.3 APIs

As far as I can tell, resource definitions and APIs for the new 1.3 API groups are not available in the reference docs. Specifically, I am looking for the resource definitions for the RBAC API.

1.4 is out and this still hasn't happened. :{

https://kubernetes.github.io/docs/api-reference/rbac.authorization.k8s.io/v1alpha1/definitions/


Create Linked list

Program of polynomial addition using linked list.

congratulations on your hactoberfest contribution. if you like this repo then give it a star. Happy hacking..


hack/scripts-dev: share docker image between test cases, clean up DNS SRV tests

Clean up existing certs so that they can share the same docker image.
And address https://github.com/coreos/etcd/issues/8502.
Separate out from https://github.com/coreos/etcd/pull/8954.
/cc @fanminshi

some nits. then lgtm


feat: hashable lockfile

I want to tell when the lockfile has changed.

@bartlomieju I can't request reviews for some reason so just pinging you.


Has the Intelligent Order Management Data Transformer connection been abandoned. I couldn't find the created entrance

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 37308970-09b7-a0ee-7dcc-5abbc12ce690
Version Independent ID: 1a2c257a-56bf-fedb-d72c-e0cb3f25462d
Content: Create and configure connections
Content Source: topics/lab-create-configure-connections.md
Service: dynamics-365-intelligent-order-management
GitHub Login: @josaw1
Microsoft Alias: josaw

@zdhzhongtao Yes, I have received a request to remove that section, and have done so. Thank you for letting us know it was still included.


Fix the mutation rules in NSObject's mutableArrayValueForKeyPath: adapter.

Previously, we would mutate a field if it was accessed via
ivar (instead of via getter or valueForKey:).
On the reference platform, instance variables accessed directly
are not copied and mutated.
This pull request also splits the tests into more fine-grained units, all of which pass on both platforms.

Fixes #759.

:shipit:

Don't forget to add 'Fixes #759' to the actual commit message.

:shipit:

Passed CI build!


Please provide the command to intstall in colab

which command do I have use to install "VAuLT" in Google Colab?

I'm also having some trouble setting up VAuLT in Google Colab's environment, I'm trying to figure this out. Apologies for the inconvenience!

You can now successfully install using !pip install git+https://github.com/gchochla/VAuLT.git@main. Thanks for bringing this to my attention!


V0.0.33

Since we want to enable the creation of custom step definition we should add some instruction on the error message found when the step definition is not found.
https://github.com/restqa/restqa/blob/master/src/restqa-snippet.js#L15


quiver requires model to have one-hot output of 1000 classes

imagenet_utils.py contains decode_predictions() which is hardcoded for 1000 classes and one-hot output.  Should support arbitrary model output.  Recommend test on mnist dataset for verification.

Duplicate of https://github.com/jakebian/quiver/issues/12 0 - see the comment there and this task, the decoding is only meant to work for imagenet atm.
Right now iff the model fails to be that the prediction endpoint will fail, but the other parts of the dashboard should function correctly.


Modules not found: XMLHttpRequest (child_process, fs)

> npm run test
...
ERROR in ./~/xmlhttprequest/lib/XMLHttpRequest.js
Module not found: Error: Cannot resolve module 'child_process' in /home/krikun/dev/react-mindmap/node_modules/xmlhttprequest/lib
 @ ./~/xmlhttprequest/lib/XMLHttpRequest.js 15:12-36

ERROR in ./~/xmlhttprequest/lib/XMLHttpRequest.js
Module not found: Error: Cannot resolve module 'fs' in /home/krikun/dev/react-mindmap/node_modules/xmlhttprequest/lib
 @ ./~/xmlhttprequest/lib/XMLHttpRequest.js 16:9-22

Is this normal situation? Try to read about this issue, but not found fast ways around.
I use:
Linux 4.11.9-1-ARCH
node v8.3.0
npm 5.3.0
webpack 2.7.0

npm install returns "added 114 packages in 22.083s" and some warnings:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

@kriku
Yeah man! I have the same issue in that example project offered by this repository.

Hey @kriku, try to get https://raw.githubusercontent.com/nodejs/node-v0.x-archive/master/lib/child_process.js and add inside your node_modules/child_process as child_process.js

Hey @kriku, this is the output I get :
$ npm run test

><EMAIL_ADDRESS>test /home/mnbv/projects/learn-anything/react-mindmap
> start-storybook -p 3000 -c .storybook

@kadira/storybook v2.35.3

=> Loading custom .babelrc
=> Loading custom webpack config.

React Storybook started on => http://localhost:3000/

If it can be useful for debugging I'm using
Linux 4.12.8-2-ARCH
node v8.4.0
npm 5.3.0

Those warnings when running npm install are normal. Basically npm is telling you that it didn't install fsevents which is an optional dependency used when running the project on MacOS. I also get that one and everything works fine.


Support for postgres 13 HA

PostgreSQL 13 has been released since 2020-09-24. Some of the applications already has that database version as preferred version, will there be a release that will include a PostgreSQL 13 soon?
https://www.postgresql.org/about/news/postgresql-13-released-2077/

Please Respond to the issues, this could have been closed months ago!


Dat-Links for tests and development

I think need below.

[ ] Normal
[ ] Large
[ ] Will be Error
[ ] 0 byte Dat
[ ] Only have "Author"
[ ] Only have "Description"
[ ] Have "Author" and "Description"

If can be creation the below, LGTM.

[ ] Scheduled

changing file. (it is automatically

@AtuyL , how do you define "Normal" and "Large"? What would be a good size in your opinion? Shall we also take into account the number of files?

@AtuyL @martinheidegger , what would be a good example for a corrupted Dat (one with an error)?

@dkastl san, Thank you for creating. I'll try it for development.

@AtuyL , maybe the "dynamic" test will not work as I expected. And the URL will be only read-only on any device but where I created the archive.
So any "static" Dat archive should be OK, but adding .dat directory probably doesn't make much sense... except for myself ;-)


Add custom permissions to allow/prevent user from exporting data

I propose adding a per-model permission that would control which users can export data. Import should already be controlled by "create" permission, but at the moment there's no mechanic in place to prevent the user from exporting all data to a file.

How about edit?

Sorry, can you be more specific with your response?

Yes, sorry. how about the change (not edit, sorry) permission. Won't that do the job?

No, it controls whether user can edit the object. Export is much too different. Anyway, I think I will implement this as it's a requirement on my project, and submit a PR.

Hey there, I had a similar case where I needed to control which users were allowed to import data. One solution to this is to override the modelAdmin's changelist_view method (which has access to the request object) to pass the necessary information to the extra_context dict . Then you can point the change_list_template attribute to a template where you can render the import/export buttons only if the required conditions are met.
{% extends 'admin/import_export/change_list.html' %}
{% block object-tools-items %}
	{% if import_allowed %}
		{% comment %}
			Should probably be
			{% include "admin/import_export/change_list_import_item.html" %}
			but doesnt add the right class to the button so I do it myself
		{% endcomment %}
		{% trans "Import" %}
	{% endif %}
	{{ block.super }}
{% endblock %}

Anyway, it'd be so much better to have has_(import|export)_permission methods instead!

ñjñlkj


[issue] write function doesn't support unicode characters

Expected behavior
write('Testüöşığ123') function's output is Testüöşığ123
Actual behavior
write('text') function's output is Test and stopping when reach to charü and gives error Error Message: Error: Unknown key: "ü"
Versions
Version: 1.0.3 (Chromium:81.0.3994.0)

Try updating taiko to 1.0.4 which has a fix for this

you right, i am closing the issue. thank you @NivedhaSenthil


Page not responding if status code != 200 and gzip enabled

1. What version of Caddy are you using (caddy -version)?
v0.10.2
2. What are you trying to do?
Use Caddy as a proxy to gin-gonic router. Any pages with status code != 200 (4xx, 5xx) not responding. If I remove gzip, works fine.
3. What is your entire Caddyfile?
http://<IP_ADDRESS>:8000 {
    proxy / dev_main:8001
    gzip
}

4.
Run in a Docker. Same problem on server and local machine.

What do you mean by "not responding"? (I wish you had followed the issue template, so we could clearly understand the problem...)

Have you some example code, etc. so people here can reproduce the issue?

Sorry it was on my production server, I didn't have time to figure out where is exactly a problem. I just can say I used caddy as a proxy server to Gin web framework. 200 status served ok, but 4xx, 5xx errors not. Server seems to not send enything. Browers said no data. Gin without Caddy worked fine and on previous versions of Caddy was fine. May be problem with gzip module, cause turning it off helped.

That's really not enough information to go by. If you run into it again and can provide more info, we can re-open this issue.

Has anyone tried reproducing this with the info given, though, even if without gin-gonic or Docker? I haven't had a chance.

Yeah, I proxy to some sites with a Caddy backend serving PHP via fastcgi, and I definitely get errors correctly, with gzip on both the backend and the proxy, in Docker. So based on that, I think the only difference between my environment and @alehano is gin-gonic.


[ShouldBeDiscussed] Pickle BaseForwardModel

implement save_pickle, load_pickle and added test

Could you check the result of Travis?

Please write unit tests for failed case, that is, DummyForwardModel correctly raises errors when a picklable object is serialized with save and a corrupted file is unpickled with load.

DummyForwardModel correctly raises errors when a picklable object is serialized with save and a corrupted file is unpickled with load.

What do we want to support?
I would say the error handling when "corrupted file is unpickled with load" is pickle's work, and not our library's work, what do you think?

Writing a test means we will define a spec to show some error message in the case of load.
But I think it is ok to let pickle to handle these case, not our library's scope.

Codecov Report

Merging #139 into master will increase coverage by 0.32%.
The diff coverage is 92.3%.

@@            Coverage Diff             @@
##           master     #139      +/-   ##
==========================================
+ Coverage   74.59%   74.92%   +0.32%
==========================================
  Files          75       76       +1
  Lines        3098     3150      +52
==========================================
+ Hits         2311     2360      +49
- Misses        787      790       +3

Updated.

I would say the error handling when "corrupted file is unpickled with load" is pickle's work, and not our library's work, what do you think?

I know we do not have to test pickle itself, assuming  that pickle works correctly. I wanted to specify how to deal with errors raised by pickle in the save/load methods. For example, currently we leave the pickle errors as they are. But one of alternative choices we can take is to grasp the pickle error.

LGTM.
However, I feel we need to improve documentation.

load_pickle function is a bit tricky. It is kind that there is a example in document.
We need to stress that load_pickle sometimes fails because of version issue and more.
Additionally, I can understand @delta2323's suggestion. But all of them are not critical. So I would like to merge first and I'm going to make issues and solve them by other PRs.

Comments on @mottodora 's latest suggestion:

I'm for careful documenting. Especially, I think we should note that we assume users save and load models with a same version and that we do not guarantee model compatibility across different ones, that is, a pickled model saved in an older version may not be loaded newer one and vice versa. If we adopt this policy, I think it would be better to add it to the [compatibility policy]. Also, it would be better to add version number to saved model. If we would apply this policy strictly, we can forbid load models that have different version number. But it seems too much to me.

One concern is that this restriction might motivate users to remain older versions, which may be the opposite direction to our aggressive version-increment policy.

It is acceptable to write the test afterwards.

Added documents. Please merge if it is ok.

LGTM except the comments.


Release 0.13.5

Taking a stab at the tests but this is a pretty old release branch
/test-e2e

/test-all

/test-all

/test-e2e
/test-conformance

Codecov Report

Merging #2477 (c440e47) into release-0.13 (20cf1fd) will decrease coverage by 2.55%.
The diff coverage is n/a.

@@               Coverage Diff                @@
##           release-0.13    #2477      +/-   ##
================================================
- Coverage         56.00%   53.44%   -2.56%
================================================
  Files               201      201
  Lines             17286    19704    +2418
================================================
+ Hits               9681    10531     +850
- Misses             6565     8053    +1488
- Partials           1040     1120      +80

Flag
Coverage Δ

e2e-tests
24.54% <ø> (?)

kind-e2e-tests
40.94% <ø> (-0.20%)
:arrow_down:

unit-tests
40.94% <ø> (-0.03%)
:arrow_down:

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

Impacted Files
Coverage Δ

pkg/ipfix/ipfix_registry.go
50.00% <0.00%> (-50.00%)
:arrow_down:

pkg/ovs/ovsctl/ovsctl_others.go
50.00% <0.00%> (-50.00%)
:arrow_down:

pkg/controller/types/networkpolicy.go
50.00% <0.00%> (-50.00%)
:arrow_down:

pkg/antctl/transform/appliedtogroup/transform.go
0.00% <0.00%> (-43.48%)
:arrow_down:

pkg/ipfix/ipfix_set.go
57.14% <0.00%> (-42.86%)
:arrow_down:

...g/agent/apiserver/handlers/podinterface/handler.go
60.97% <0.00%> (-29.65%)
:arrow_down:

pkg/antctl/transform/networkpolicy/transform.go
0.00% <0.00%> (-28.31%)
:arrow_down:

pkg/ipfix/ipfix_process.go
60.00% <0.00%> (-21.82%)
:arrow_down:

pkg/agent/flowexporter/utils.go
83.33% <0.00%> (-16.67%)
:arrow_down:

pkg/agent/controller/networkpolicy/cache.go
71.13% <0.00%> (-14.85%)
:arrow_down:

... and 180 more

As expected there are some problems when running the tests, but given that conformance and networkpolicy succeeded, and given that all tests passed on main for the upgrade to OVS 2.14.2, I will go ahead and merge.


Preview doesn't work

Describe the bug
The preview does not render the app at url: https://stackblitz.com/edit/stackblitz-starters-bc3yhh?file=script.js,index.html,styles.css
Link to the blitz that caused the error
https://stackblitz.com/edit/stackblitz-starters-bc3yhh?file=script.js,index.html,styles.css
Steps to reproduce
Open preview
Expected behavior
App rendered in the preview
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
No response
Platform
Browser name  = Chrome
Full version  = <IP_ADDRESS>
Major version = 125
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 91596649,
  "usedJSHeapSize": 86764101,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Hash = 12d46890

Additional context
No response

Hey @RonaldBoyd 👋 ! Thanks for reaching out.
You can read more information regarding this in the comment right here.
tldr; we don't automatically serve static index.html files. If you want to show serve the index.html, you could type npx servor which will spin up a small server and serves the static assets in your project.


[BACKLOG-28593] - spelling error

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'plugins/streaming/impls/mqtt' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'plugins/streaming/impls/mqtt' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  plugins/streaming/impls/mqtt/src/main/resources/org/pentaho/di/trans/step/mqtt/messages/messages_en_US.properties

Newly Broken Tests:
org.pentaho.di.trans.step.mqtt.MQTTProducerTest.testErrorOnPublishStopsAll:
:red_circle: org.mockito.exceptions.verification.junit.ArgumentsAreDifferent
org.mockito.exceptions.verification.junit.ArgumentsAreDifferent:

Argument(s) are different! Wanted:
logChannelInterface.logError(
    "MQTT Producer - Recieved an exception publishing the message.  Check that Quality of Service level ${qos} is supported by your MQTT Broker"
);
-> at org.pentaho.di.trans.step.mqtt.MQTTProducerTest.testErrorOnPublishStopsAll(MQTTProducerTest.java:200)
Actual invocation has different arguments:
logChannelInterface.logError(
    "MQTT Producer - Received an except

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'plugins/streaming/impls/mqtt' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'plugins/streaming/impls/mqtt' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  plugins/streaming/impls/mqtt/src/main/resources/org/pentaho/di/trans/step/mqtt/messages/messages_en_US.properties
  plugins/streaming/impls/mqtt/src/test/java/org/pentaho/di/trans/step/mqtt/MQTTProducerTest.java


Replace Some and None variants with the exact value and null accordingly

As I see Some and None are needed for Sophia's strict typing. JS is not so strict, so it can't be converted in a native way. For developer convenience, I propose to make it look native by omitting Sophia's variants in this case by replacing Some and None variants with the exact value and null accordingly.

Internal representation
Public interface

{ variant: 'Some', values: [123] }
123

{ variant: 'None', values: [] }
null

in the past undefined was used for None in the js-sdk as far as I know

However I wonder can we do a general revamp of the interface?

I think it would be too expensive to integrate calldata library into SDK without breaking changes, so propose to introduce all reasonable changes that we have in mind

in the past undefined was used for None in the js-sdk as far as I know

More correct to return null in this case (as far we already making breaking changes), would be good to accept both null and undefined as None(some type)

At first I somehow missed the point of this request/issue, however after I clearly understand the request now - I strongly disagree with it the proposal.
I would not argue on it but refer to the datatype description from https://en.wikipedia.org/wiki/Tagged_union

Tagged unions are most important in functional languages such as ML and Haskell, where they are called datatypes (see algebraic data type) and the compiler is able to verify that all cases of a tagged union are always handled, avoiding many types of errors.

Also https://rescript-lang.org/docs/manual/latest/variant#design-decisions

Variants, in their many forms (polymorphic variant, open variant, GADT, etc.), are likely the feature of a type system such as ReScript's. The aforementioned option variant, for example, obliterates the need for nullable types, a major source of bugs in other languages. Philosophically speaking, a problem is composed of many possible branches/conditions. Mishandling these conditions is the majority of what we call bugs. A type system doesn't magically eliminate bugs; it points out the unhandled conditions and asks you to cover them*. The ability to model "this or that" correctly is crucial.

While because of the lack of pattern matching in Javascript it is significantly verbose and "harder" to handle this it's not enough argument to introduce nullable data. In general my option is that null is one of the worst mistake in programming languages which is nicely handled by tagged unions/variants and with optional in Sophia in particular and libs should not magically defeat that. Given that one can get nulls in JS for various reasons is also significant decision factor.
Moreover I'm always for explicitly over implicitly thus handling special cases would be out of scope of this library.

@mradkov @marc0olo @thepiwo what do you think about it?

If we can agree on this premise: We need to keep Sophia types and its JS representations semantically as close as possible for delivering developers something that naturally makes sense.
..then the conclusion cannot can not be we reject using null  (not undefined, as that would be given for some accidentally mistyped var name, too, for example) for None or Some because of academic reasons. At least until somebody proposes semantically matching alternative that is also native to JS, using null would be the way to go for now.

You're free to implement that mapping in the SDK then, this library prefers to work in a more reasonably way.

(not undefined, as that would be given for some accidentally mistyped var name, too, for example)

exactly the same applies to null as well

I should stop replying to this one but, the library is a 1to1 encoder to Sophia data types, there is no "null" there, Some and None are variants of optional, once the Sophia adds a null type I'll be more than happy to implement it.

You're free to implement that mapping in the SDK then

Splitting the implementation would make it more difficult to maintain. I don't want to do this recursive replacing by ACI on SDK side just because we can't agree here. Different interfaces in SDK and calldata would complicate switching between them (is calldata intended to be used separately?).

not undefined, as that would be given for some accidentally mistyped var name, too, for example

Actually, modern environments would throw a ReferenceError (something is not defined) in that case. I don't think that
let foo; // undefined
contract.methods.bar(foo);

should be forbidden. Also, in TS optional function parameters are defined as <type> | undefined, so null even won't work there. 🤔
@dincho have you tried to find some third-party None/Some implementation for JS? This would make calldata compatible with them, otherwise, it may be like
const t = libraryA.foo();
libraryB.bar(t === libraryA.None ? libraryB.None : t)
// instead of just
libraryB.bar(libraryA.foo())

or even recursive replacement may be needed if there are complex structure 😄
I agree that nulls are error-prone in JS, but TS compiler (with strictNullChecks flag) will ask the developer to check if the optional value is present or not, the same can do an IDE with TS support in JS project. This would be more obvious and natural for the usual JS developer: "Object is possibly 'null/undefined'" than "Object is possibly doesn't have 'Some' property"(?).

is calldata intended to be used separately?

I don't really think so. it could be used separately but probably nobody will do it.
fact is we need to decide as quickly as possible how to proceed here in general. seems like currently it's not easy to get aligned on that.
I would like to have some feedback of @thepiwo and @mradkov about this again.
personally I am a fan of typescript but I am more interested in moving the way the majority thinks we should go. this shouldn't block us from moving forward.

for call-data lib I don't mind as long as in sdk we map it logically without need for additional libs
I also like the typescript approach with value | undefined

@davidyuk what's the exact issue to do it on SDK side?

(is calldata intended to be used separately?).

actually yes in my master plan, this library could evolve to a general encoder/serializer and to be eventually used in a JS compiler, client-side only decoder etc.
I definitely want to keep this library standalone, Vanilla JS in browser.

@davidyuk what's the exact issue to do it on SDK side? I think we should move forward asap here 😅

Isn't it already implemented like that in the SDK, I pointed to a source code above sorry if I misunderstood that

@dincho have you tried to find some third-party None/Some implementation for JS? This would make calldata compatible with them, otherwise, it may be like

I don't like the idea to introduce additional lib for types interop, interfaces should be POJO of a given standalone lib or library provided datatype, that's general library (good) practice IMO

FYI: I've clarified the library purpose and goals in 4a8babaf24506411b6aafcccc1dc5efc658b3766

Also https://rescript-lang.org/docs/manual/latest/variant#design-decisions

While Rescript doesn't implement nullable types as a source of bugs they don't force JS to adopt that, e.g. the transpiled code uses undefined instead of None: example.
If you have chosen Rescript instead of JavaScript then we would be able to transpile it to JS without this issue. But calldata is written in JavaScript so it should be consistent with decisions made in this language (even if they are wrong).

what's the exact issue to do it on SDK side?

It should do most of the work that already calldata does to wrap and unwrap optional values in nested structures, more maintainable would be to do these changes on calldata side.

OK @davidyuk, looks like it's something quite important to you, I'll reconsider it.

However, the lib will keep accepting {None: []} and {Some: []} (the generic variant format) as well.

difficult topic for me as I don't have a strong opinion here. would be nice to get this sorted out. thanks @dincho, really appreciated! :-)

I think if we keep supporting both we probably should make this configurable in the lib. or how is this supposed to work or be used otherwise?

Will it decode as { None: [] } or null then? I'm proposing my implementation in #85

Null perhaps ? Does it break the current implementation somehow ?

we are breaking lots of the current implementation anyway now, so we can also change it.

I see that we want to solve this topic and somehow it seems feedback is required but I am struggling to understand what I can do in this case or how I can support here.
the discussion in this PR https://github.com/aeternity/aepp-calldata-js/pull/85#discussion_r752462276 seems to be related.

However, the lib will keep accepting {None: []} and {Some: []} (the generic variant format) as well.

@dincho so you would like to keep accepting both ways in the public interface - do I understand that correctly?
sorry @davidyuk, I am somehow still struggling with this topic in general 😅

@dincho so you would like to keep accepting both ways in the public interface - do I understand that correctly?

exactly, no less, no more

so we have now multiple options:

only support one way (@thepiwo)

which one doesn't matter

support both ways (@dincho)

initially only one way that is not favored by SDK devs

implementation in #85 (@davidyuk and @mradkov)

not sure how this right now aligns with Dinchos request

my humble opinion right now is that I just want to take a decision here. maybe we should set up a call to sort this out. from what I heard from @davidyuk it would be quite an overhead (not sure how much right now) to tackle the SDK favored approach directly in the SDK instead of the lib and it would also increase maintenance costs in case we face changes in that area (probably unlikely, but you never know 😅)
I know that we want to have a standalone lib in general. we can leave like is and do cover the desired functionality in SDK. personally I am wondering and thinking about what other tools & SDKs might make use of this library except our official javascript sdk.
anyway, we need to take a decision here and I think will leave that up to you @dincho as you maintain this library. in the call today we agreed that we don't want to fork this library and maintain a separate version of it. fact is that the current state of the sdk that aims to include this calldata relies on the implementation included in #85.

I know that we want to have a standalone lib in general. we can leave like is and cover the desired functionality in SDK. personally I am just wondering and thinking about what other tools & SDKs might make use of this library except our official javascript sdk.

A JS compiler would use this as well. Also a JS blockchain explorer would benefit by decoding call results. This is just in the top of my head, but I'm sure it would find some more uses.
One the lib get's it's full serialization support, it could be used in the blockchain explorer to show a FATE VM assembly as well, that of course needs an additional lib to traslate the binary to FASM, but still you get the idea.
In the call we agreed to support both undefined/null/T/canonical structure and decode to undefined. (option variant only)


Issues on OpenUPM site

I've noticed the following on https://openupm.com/packages/com.marijnzwemmer.unity-toolbar-extender/
#20 might fix it, or maybe a new release (possibly with bump to 1.3.1) might be required, I'm not familiar with how it works.
Screenshot:

Heya. I created another new version and it's no longer conflicted.


chore: Use GitHub Actions to build Docker Images to allow publishing Windows Images

As mentioned in #2747 Docker Hub Automated Build Hooks don't allow to build Windows images. As v2.9.0 comes with Windows support for argoexec and as you migrated CI to GitHub Actions also, it would make sense to use GitHub Actions also for building the Docker images.
I added a workflow file which builds and pushes the images for Linux (workflow-controller, argoexec, argocli) and Windows (argoexec only) whenever a new tag v* is pushed. I used the existing Docker Hub Hooks (https://github.com/argoproj/argo/blob/master/hooks/build) as a base for the scripts. The jobs building and pushing the images are appending -linux or -windows to the tag, a third job is creating a Manifest and pushes it to allow for multiarch. Example:

Tag v2.9.0 is pushed
Job build-linux is building and pushing argoproj/workflow-controller:v2.9.0-linux, argoproj/argoexec:v2.9.0-linux argoproj/argocli:v2.9.0-linux
Job build-windows is building and pushing argoproj/argoexec:v2.9.0-windows
Job push-images is creating and pushing the following image manifest:

argoproj/workflow-controller:v2.9.0 referencing argoproj/workflow-controller:v2.9.0-linux
argoproj/argoexec:v2.9.0 referencing argoproj/argoexec:v2.9.0-linux and argoproj/argoexec:v2.9.0-windows (multiarch)
argoproj/argocli:v2.9.0 referencing argoproj/argocli:v2.9.0-linux

You can find an example run for a tag vtest17 here: https://github.com/lippertmarkus/argo/runs/804344322
Resulting image, e.g. for argoexec: https://hub.docker.com/repository/docker/lippertmarkus/argoexec/tags
You only need to add the following two secrets like described in the GitHub Actions Help before merging:

DOCKERIO_USERNAME = argoproj
DOCKERIO_PASSWORD = <a-docker-hub-pat-token>

Checklist:

[x] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
[x] The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
[x] I've signed the CLA.
[x] I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.

not needed

[x] My builds are green. Try syncing with master if they are not.

Let me get this right, would this save us building this locally? Just tag and push tag?

Yes, correct.

What do you think? Would also help to make the builds more reproducable.

We still need to build binaries. Any thoughts on how that might be possible? Maybe another PR?

This would be possible with the following steps:

Automatically create a release: https://github.com/marketplace/actions/create-a-release
Upload assets to the newly created release: https://github.com/marketplace/actions/upload-a-release-asset (binaries can be build with another job)

Afterwards you could add your release description manually or you also automate that.
Could look into that in another PR, but this PR would already help a lot with getting "official" Windows Images for argoexec :)

any updates on this PR?

For pushing new images we would always need to store credentials. Those are stored securely by GitHub (symmetric encryption, see here). This is done this way by a lot of other projects on GitHub so there shouldn't be a problem.
And you don't use your normal Docker Hub password, you would instead create a new Access Token on Docker Hub and use this for authentication. This token can be revoked at anytime if needed.

I have now set-up the secrets for this.

Thanks! I added the master branch and tested again. You can view an example run here and resulting latest docker images e.g. for argoexec here.

Lets see if this works.

https://github.com/argoproj/argo/actions/runs/163542666
But where are the images?

hmm, push seems to be successful. What did you specify as Docker username?

my username: alexcollinsintuit

ah
https://hub.docker.com/repository/registry-1.docker.io/alexcollinsintuit/argocli/tags?page=1

can you try them out to see if they work?

I tested the images, they work fine. We need to use a different repository than the Docker Hub username you log-in with. I created a new PR: #3442.


feat: accept HTMLElement or string on the constructor

Hi! This PR allow you to insert an HTML Element or string in the component constructor.

@Masth0 Can we get this merged?


[NuGet.org Bug]: Cannot sign-in

Impact
I'm unable to use NuGet.org
Describe the bug
My username is bwakabats
My email address is<EMAIL_ADDRESS>(I do not have access to this email anymore but can sign-in to it using MS)
My new email address is<EMAIL_ADDRESS>I cannot sign-in to my bwakabats account
Repro Steps
When I sign in as<EMAIL_ADDRESS>(using MS) it says "The account with the email<EMAIL_ADDRESS>is linked to another Microsoft account."
When I sign in to as<EMAIL_ADDRESS>(using MS) I am told "Looks like we don't have an account with this email address<EMAIL_ADDRESS>in our records." and asks me to sign-up, but I cant use the username "bwakabats" because its already taken.
When using the "Need assistance signing in" link, I enter the username "bwakabats" and the email address<EMAIL_ADDRESS>and get an email saying "Our records indicate the associated Microsoft login(s): Shane Whitehead<EMAIL_ADDRESS>Expected Behavior
I sign-in to my bwakabats account using one of the email addresses
Screenshots
No response
Additional Context and logs
No response

Hello, @bwakabats. Please contact<EMAIL_ADDRESS>about this problem. We don't use the GitHub issue tracker for this type of problem since it contains personally identifiable information.


Automatically disable some features on large PRs

A few times people reported some features being slow on large PRs.
I wonder if, like GitHub does for large comparison, we could disable some/all features on large PRs and show a notice like "Some RG features were disabled because this page is gargantuan."
However, this need your help. Please post links to such large PRs. No real-life examples, no chances of this being fixed.

Is #1783 large enough?

Not for me, it's buttery smooth on my 2013 laptop. We need the users who report slowdowns to post their slow URLs.

https://github.com/RudiDeVos/UltraVNC/commit/4fbe8afcacc9cf181413402c1441d17ea79fdf25
With RH can barley get past the first file without chopping up. This is on a solid desktop computer.
Without RH freezes bus it moves.

Is my 2013 mac suddenly a super computer? That page also loads without a hitch. It does flash white for ~300ms but that happens even without RG.

That gif was recorded inside npm run start, so no other extensions running.

@fregante I should have recorded it... maybe next week

What's your CPU? Also try it in npm run start

RudiDeVos/UltraVNC@4fbe8af

It does lag a bit, but after a few seconds it's totally fine. I guess it's because GitHub folded most of the files so RGH doesn't really need to process a huge amount of lines. We probably need a PR that consists of lots of files that aren't long enough to be folded by GitHub.

@fregante maybe it was not a fair test. I did it on my work computer (in middle of work shhh). I did have about 45 (if not more) other chrome tabs open and work items too. I will test again next week with only that one page open and only RH enabled.
When I posted the link I incorrectly assumed that you would see the same results so I did not bother recording.


WatsonTcpClient.Send() with stream disconnects if contentLength is not equal to the stream's capacity.

Given a byte[] buffer, I'd like to send a portion of it - moreover, I'd like to use my own Stream instances which may be pooled and recycled.
The WatsonTcpClient.Send (long contentLength, Stream stream) is the closest overload to my purposes as I can provide my own Stream and coincidentally my buffer's data always starts at the zeroth index (although it'd be nice to also be able to define the starting position).
To my understanding, contentLength defines how much of my Stream should be read and sent.
However, if I choose a contentLength that is not equal to the buffer's capacity, what happens is that the data is sent/received correctly as expected (it respects the contentLength that I chose), but the client will be disconnected afterwards.
The only instance in which the client doesn't get disconnected is if contentLength is set equal to the buffer capacity, but then of course that'd defeat the point for my purposes.
The workaround for me so far is to copy the desired data into a new buffer of the exact size required, or create a new MemoryStream and write() to it what I need, but minimizing copies/allocations is exactly what I'm trying to do.
Below is the program I use to reproduce it. I've been using .NET 6.0 and tested this on Windows 10 and macOS Monterey.

using WatsonTcp;

internal class Sandbox
{

    public static void Main(string[] args)
    {
        if (args[0].ToLower().Equals("server"))
            StartServer();
        else
            StartClient();

        Console.ReadLine();
    }

    static void StartServer ()
    {
        WatsonTcpServer server = new WatsonTcpServer("<IP_ADDRESS>", 9001);

        server.Events.ClientConnected += (sender, args) =>
            Console.WriteLine("Server: a client has connected.");

        server.Events.ClientDisconnected += (sender, args) =>
            Console.WriteLine("Server: a client has disconnected: " + args.Reason);

        server.Events.MessageReceived += (sender, args) =>
            Console.WriteLine($"Server: received {args.Data.Length} bytes from client");

        server.Start();

        Console.WriteLine("Server has started.");
    }

    static void StartClient ()
    {
        WatsonTcpClient client = new WatsonTcpClient("<IP_ADDRESS>", 9001);

        client.Events.ServerConnected += (sender, args) => {
            Console.WriteLine("Client: connected to server. Will send a message...");

            //                       VVVVVVVVV Only want to send the first 5 bytes
            var buffer = new byte[] {1,2,3,4,5,6,7,8,9,10};

            using (var stream = new MemoryStream(buffer))
                client.Send(contentLength:5, stream); //    <-- will disconnect unless you use 10

        };

        client.Events.ServerDisconnected += (sender, args) =>
            Console.WriteLine("Client: disconnected from server.");

        client.Events.MessageReceived += (sender,args) =>
            Console.WriteLine($"Client: received {args.Data.Length} bytes from server.");

        Console.WriteLine("Client attempting connection...");
        client.Connect();
    }
}

I noticed that my server was not using StreamReceived as it should in this scenario. However the problem does persist anyway even if you replace MessageReceived for that.

Copied and reproduced it on my end. Seems to derive from WatsonMessage, this section specifically:
                    if ((int)endCheck[3] == 0
                       && (int)endCheck[2] == 0
                       && (int)endCheck[1] == 0
                       && (int)endCheck[0] == 0)
                    {
                        _Logger?.Invoke(Severity.Debug, _Header + "null header data, peer disconnect detected");
                        return false;
                    }

Haven't been able to figure out why this is, yet, though. Content length must at least be the message's length provided, or else header reading fails.
private async Task DataReceiver() (WatsonTcpClient.cs) would then exit out its while loop here:
                    bool buildSuccess = await msg.BuildFromStream(_Token).ConfigureAwait(false);
                    if (!buildSuccess)

.. with a default disconnect reason of Normal.

Hi, sorry for the delay on this.  I'm looking into it now.

I believe I have a fix ready for this.  Example using your test code (I added it as project Test.PartialStream):

The client isn't disconnected, and the server receives the appropriate number of bytes.

Could you give this a try?
NuGet: https://www.nuget.org/packages/WatsonTcp/<IP_ADDRESS>
Commit: https://github.com/jchristn/WatsonTcp/commit/022eab13360c786b5f9e3c3d7798f44c509ef686
Also updating deps, there will be a .13 version shortly.

Closing just to clean up my inbox, please re-open if this does not solve the issue!

Works on my end. =)

Thanks for letting me know @eatyouroats !!


Request the complete code

Dear Authors:
l am honored to read your paper "MIXED TRANSFORMER U-NET FOR MEDICAL IMAGE SEGMENTATION". This paper has inspired my research and guided my next plan,but I found that you did not provide The complete code , so I sincerely hope that you can provide the complete code. my mail address is<EMAIL_ADDRESS>Or send me directly， I will be very grateful.

Dear Authors: l am honored to read your paper "MIXED TRANSFORMER U-NET FOR MEDICAL IMAGE SEGMENTATION". This paper has inspired my research and guided my next plan,but I found that you did not provide The complete code , so I sincerely hope that you can provide the complete code. my mail address is<EMAIL_ADDRESS>Or send me directly， I will be very grateful.

The code has been sent. Please check your mailbox.


Test settings: fix test settings, add warnings and FIXME's

Please ensure that FIXME is fixed before merging! Especially djangocms-helper version contains a fix for https://github.com/nephila/djangocms-helper/issues/46

LGTM


HXCPP debug does not start

I've configured my environment to debug hxcpp application following wiki instructions, but when I press debug button, nothing happens. Is debugging using IntelliJ possible at all?

Yes, it is possible and working for members of our team.
Are you sure that your application compiled correctly?  Depending upon what "nothing happens" means to you, it may be that your compilation didn't succeed, or that you haven't set up the proper Debug configuration (in IDEA, via the Run->Debug... menu item.  We've also seen improper/missing SDK configuration (File->Project Settings...) silently fail to execute.  Make sure that the Run... configuration works, then debugging should start correctly.  If Run... doesn't work, Debug... won't either.
If Run... works and Debug... does not, did you add the required code to your application's Main function?  See https://github.com/TiVo/intellij-haxe#use-the-hxcpp-debugger.

My app compiles correctly (I can click "Run" and it starts correctly). My debug settings are these:

I'm using debug calling on main function:
public function new()
	{
		super();
		new debugger.HaxeRemote(true, "localhost", 6972);
		addChild(new FlxGame(gameWidth, gameHeight, initialState, zoom, framerate, framerate, skipSplash, startFullscreen));
	}

Program starts debug and tries to connect (and never succeed).
When I say "nothing happens", I mean exactly that. Literally nothing happens (as if I never clicked the button).
I'm using IntelliJ Idea CE 15.0.6 on OSX.

I'm confused by the antinomy caused by these two mutually exclusive statements: "Program starts debug and tries to connect..." and "Literally nothing happens..."
So... it sounds like when you press the Debug button your app does start, but IDEA doesn't show either the logging panel or the debug panel.
Have you set any breakpoints??  It may be that your app is just running and having no reason to break, the debugger doesn't bring up the debug window.  (The debugger does NOT stop the program just because you started it.  A breakpoint must be hit.  (There is a bug -- in the hxcpp debugger -- where a program won't stop when the pause button is pressed unless a breakpoint was hit first.)
And another thought just occurred: You are using the C++ target for your project, right?  Because that's the only target (that I know of) that works right now.  (Flash used to -- a looooong time ago.)

Another thought: When "nothing happens," look at the status bar at the bottom of the IDEA window.  Sometimes, warnings are displayed there and are easily missed.

Sorry for the confusion: When I press "Run", program runs and debug library tries to connect. When I press "Debug", nothing happens. Nothing really. No console message, no program trying to run... nothing.
Shouldn't start debugger with new debugger.HaxeRemote(true, "localhost", 6972); start the debugger paused?
Yes, I'm using C++ target.
Just to be sure: I need to just press "Debug" button to debug the program or "Run" and then "Debug" buttons?

Shouldn't start debugger with new debugger.HaxeRemote(true, "localhost", 6972); start the debugger paused?

Yes, it should; it's a known bug that it doesn't.  The workaround is simple: set a breakpoint on the line after new debugger.HaxeRemote.

Just to be sure: I need to just press "Debug" button...

That is the correct workflow.  The debug launcher should start up a listener and then wait for your program to connect.  You should have a console pane (normally gets obscured by the debug pane) pop up that shows basically the same thing as when you press 'Run'. (e.g. Lime starts and then runs your program.)
All of that said, you can't just use the latest hxcpp-debug library either.  It has been upgraded to v1.2, and the plugin still only talks the protocol from 1.1.  Be sure you're running the right version.  (See the first paragraph of the debugger section of our main page: https://github.com/TiVo/intellij-haxe#use-the-hxcpp-debugger for how to do that.)
You can test that the debugger is working from your program without using IDEA.  There is a command-line debugger shipped with hxcpp-debugger that can connect to your program.  It's a lot like running gdb, but can verify that the debugging code in your program is working correctly and isolates the issues to IDEA. (https://github.com/HaxeFoundation/hxcpp-debugger/wiki/Getting-started.)
Finally, (and I'm not sure of this at all - I was unable to test it quickly because of my environment) it may be that you can't start the debugger in your app's new function.  Try placing the debugger startup in the static 'main' function of your app class.

  Did you have any issues with getting the debugger to run?

Just a suggestion: should I do a downgrade on IntelliJ IDEA? I'm trying with version 15.0.6

@arthurferrai @EBatTiVo seems like we have 1.1 protocol and other versions of hxcpp-debugger throw exceptions. Just for test I've created ExeRunningState to run debugger from hxml file. After downgrading hxcpp-debugger to protocol_v1.1, debugger is successfully connected, but breakpoints don't work. Should we upgrade protocol version?

@eliasku My hxcpp-debugger is on 1.1 version. My problem is that debug doesn't start on IntelliJ when I click "Debug" button (terminal debug works as expected).

@arthurferrai: I wouldn't necessarily downgrade, but it might be a useful test.  You can't pick up Mac builds of previous versions (e.g. 15.0.4, 15.0.3) on the web, but you can pick up the latest 14.1.  In the end, though, it's not likely the issue.  More likely, that you've got to pick up the github build at the proper tag.  But, then again, @eliasku says that breakpoints aren't working.  We will have to take a look.
@eliasku: I think we should upgrade the debugger to the new protocol.  It's not super-simple, though, for two reasons:  1) The protocol code (in Haxe) isn't compiling to Java correctly, so we're using a checked-in version of the generated code; the UCSC guys fixed it (look for a PR from @tekgek) but I haven't pulled their changes yet because it requires that the compiler guys take a few changes as well.  2) The way that data is passed changed between protocol versions 1.1 and 1.2 from a recursive structure to an array structure (which I find more understandable).  So, we've not only got to update the Haxe code generation, but we've got to rewrite the data parsing.  It will take several days worth of effort, but it's very doable, provided we get the time.

@EBatTiVo Installed IntelliJ Idea 14.1. Exactly same behavior, "Debug" button does absolutely nothing. Do I need special configuration for this to work?

No, you should not need a special configuration.  Your app should be running even if the debugger doesn't connect.  You don't even seem to have that, so I'm trying to think of why an app might not run from the Debug menu when it runs just fine from the Run menu.  (And, I'm not much of a Mac user, so I don't know the platform specifics.)  If you remove the HaxeDebug.Remote line from your app, does it execute?
Other random thoughts:
If the app is starting, it is most likely that the plugin and the debugger are not completing the startup handshake.  That can happen if the protocols don't match, but it can also happen if there are socket issues.
(You don't have a firewall keeping processes from talking to localhost, do you?  And DNS -- nslookup -- resolves localhost to <IP_ADDRESS>, right?   You can try substituting <IP_ADDRESS> for localhost in the HaxeDebug.Remote() call.)

@arthurferrai:  If the app will run from the "Debug..." menu without HaxeDebug.Remote(), you will want to check your git branch (as opposed to haxelib).
git branch should give you:
   master
 * protocol_v1.1

If it does not:
  $ cd <your_local_git_clone>
  $ git pull origin protocol_v1.1
  From https://github.com/HaxeFoundation/hxcpp-debugger
   * branch            protocol_v1.1 -> FETCH_HEAD
  Already up-to-date.
  $ git checkout protocol_v1.1
  Branch protocol_v1.1 set up to track remote branch protocol_v1.1 from origin.
  Switched to a new branch 'protocol_v1.1'
  $ haxelib git hxcpp-debugger <your_local_git_clone> protocol_v1.1

Then you will definitely have the proper version of the debugger.

Ok, all details:
My OS X is 10.11.6.
My IntelliJ IDEA is on version 14.1.7.
(Just to note, I'm using HaxeFlixel, but since it runs on top of OpenFL, it should work as expected)
My "Run/Debug Configurations" is as follows:

Name is default, Share is unmarked and Single Instance Only is unmarked
Module has the name of my project (and it's the only available option)
Alternative Executable is unmarked
Custom file to run is unmarked
Debugger Listen Port is 6972, with Remote Debugging marked
Before Launch is empty
Show this page is unmarked

My "Project Structure/Module" settings are as follows:

Sources tab has all my project files
Dependencies tab has all my project libraries (no one is marked to Export) and Dependencies storage format has option IntelliJ IDEA (.iml) marked
Haxe tab has:

Compile with marked with OpenFL
Target marked with Mac OS
Project Macros empty
OpenFL arguments has "-debug"
OpenFL Project XML has the path of my "Project.xml" file
Skip compilation is unmarked

Using entry-point as follows:
	public function new()
	{
		super();
		new debugger.Local(true);
		addChild(new FlxGame(gameWidth, gameHeight, initialState, zoom, framerate, framerate, skipSplash, startFullscreen));
	}

When I click on "Run", IDEA shows me the "Run" output window with this content (excluding Lime stuff):
Running command: RUN
 - Changing directory: export/mac64/cpp/bin/spjam2016.app/Contents/MacOS
 - Running command: ./spjam2016 -verbose -livereload
2016-09-28 09:41:02.881 spjam2016[7225:526708] 09:41:02.880 WARNING:  140: This application, or a library it uses, is using the deprecated Carbon Component Manager for hosting Audio Units. Support for this will be removed in a future release. Also, this makes the host incompatible with version 3 audio units. Please transition to the API's in AudioComponent.h.
2016-09-28 09:41:03.057 spjam2016[7225:526708] ApplePersistenceIgnoreState: Existing state will not be touched. New state will be written to /var/folders/22/w3drmwfn4mg_m4g8h32wn2vr0000gn/T/com.example.myapp.savedState

-=- hxcpp built-in debugger in command line mode -=-
-=-      Use 'help' for help if you need it.     -=-
-=-                  Have fun!                   -=-

Thread 0 stopped in Main.new() at Main.hx:22.

1>

Which indicates me that local debug works as expected.
When I click "Debug", nothing happens (my app doesn't run and there's no log report on IDEA event log window, nor any other window).
Now, I changed my entry point to this:
	public function new()
	{
		super();
		new debugger.HaxeRemote(true, "<IP_ADDRESS>", 6972);
		addChild(new FlxGame(gameWidth, gameHeight, initialState, zoom, framerate, framerate, skipSplash, startFullscreen));
	}

When I click on "Run", IDEA shows me the "Run" output window with this content (again, excluding Lime stuff):
Running command: RUN
 - Changing directory: export/mac64/cpp/bin/spjam2016.app/Contents/MacOS
 - Running command: ./spjam2016 -verbose -livereload
2016-09-28 10:07:25.345 spjam2016[7451:540415] 10:07:25.345 WARNING:  140: This application, or a library it uses, is using the deprecated Carbon Component Manager for hosting Audio Units. Support for this will be removed in a future release. Also, this makes the host incompatible with version 3 audio units. Please transition to the API's in AudioComponent.h.
2016-09-28 10:07:25.451 spjam2016[7451:540415] ApplePersistenceIgnoreState: Existing state will not be touched. New state will be written to /var/folders/22/w3drmwfn4mg_m4g8h32wn2vr0000gn/T/com.example.myapp.savedState
Debugger:Starting App side debugger support.
Debugger:Failed to connect to debugging server at <IP_ADDRESS>:6972 : EOF
Debugger:Trying again in 3 seconds.
Debugger:Failed to connect to debugging server at <IP_ADDRESS>:6972 : EOF
Debugger:Trying again in 3 seconds.

(Debugger failure keeps repeating while program is running)
When I click "Debug", nothing happens again.

My current suspicion is that you are getting an exception that is stopping the whole debug process from running.  Can you please open your Java console (I believe, on a mac, that you do that by opening the Java Control Panel "System Preferences->Java->(opens new window)->Advanced->Show console"), and post any exceptions that occur when you press the Debug button?

@EBatTiVo I've activated Java console as you said, but it won't open when I start IntelliJ IDEA. On IDEA log (~/Library/Logs/IdeaIC14), there are no changes when I press debug button.

@arthurferrai I'm at a loss.  I can't think of any other reasons why you might be getting this behavior.  I'll keep thinking about it.
It's looking like a debugging session is in order, but in order to do that somebody is going to have to duplicate the behavior you're seeing.  I do have a mac that I could try on; it's the time I don't have much of.
In the mean-time, if you feel particularly inclined, you could set up a dev environment for the plugin and try it yourself.  See the CONTRIBUTING page for how to do that (https://github.com/TiVo/intellij-haxe/blob/master/CONTRIBUTING.md).  If you do, the classes you want to look at are in https://github.com/TiVo/intellij-haxe/tree/master/src/14.1/com/intellij/plugins/haxe/runner/debugger.  If you have questions about that code, we'll try and answer them.
(This isn't to put you off, rather to get you help from more knowledgeable folks that may be out there:)
There is an #IRC channel that has (should have) a lot more traffic: http://old.haxe.org/com/meeting/irc
You may also get more informed help (about IDEA anyway) from the IDEA forums: http://blog.jetbrains.com/idea/2012/05/get-involved-into-intellij-idea-community/

@EBatTiVo I'll try to debug plugin to see if I can discover anything. Should I try on "master" branch?

@EBatTiVo Is it really necessary to install flex sdk?

Yes, the master branch is the most up-to-date and has all of the approved changes.  If you find you want to make new changes, then make yourself a work branch.  The CONTRIBUTING.md doc has the workflow instructions.
From: arthurferrai<EMAIL_ADDRESS>Sent: Thursday, September 29, 2016 5:47 AM
To: TiVo/intellij-haxe
Cc: Eric Bishton; Mention
Subject: Re: [TiVo/intellij-haxe] HXCPP debug does not start (#483)
@EBatTiVohttps://github.com/EBatTiVo I'll try to debug plugin to see if I can discover anything. Should I try on "master" branch?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/TiVo/intellij-haxe/issues/483#issuecomment-250455801, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AG5Z6T_HuTSARCRBl-UR_s1w-z_vm4Kpks5qu7NIgaJpZM4KEUQZ.

This email and any attachments may contain confidential and privileged material for the sole use of the intended recipient. Any review, copying, or distribution of this email (or any attachments) by others is prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete this email and any attachments. No employee or agent of TiVo Inc. is authorized to conclude any binding agreement on behalf of TiVo Inc. by email. Binding agreements with TiVo Inc. may only be made by a signed written agreement.

Not unless you are going to mess with the BNF or parsing.
From: arthurferrai<EMAIL_ADDRESS>Sent: Thursday, September 29, 2016 6:57 AM
To: TiVo/intellij-haxe
Cc: Eric Bishton; Mention
Subject: Re: [TiVo/intellij-haxe] HXCPP debug does not start (#483)
@EBatTiVohttps://github.com/EBatTiVo Is it really necessary to install flex sdk?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/TiVo/intellij-haxe/issues/483#issuecomment-250473306, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AG5Z6UGgoBRVYkSWPvwj25n61e92bbrrks5qu8PAgaJpZM4KEUQZ.

This email and any attachments may contain confidential and privileged material for the sole use of the intended recipient. Any review, copying, or distribution of this email (or any attachments) by others is prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete this email and any attachments. No employee or agent of TiVo Inc. is authorized to conclude any binding agreement on behalf of TiVo Inc. by email. Binding agreements with TiVo Inc. may only be made by a signed written agreement.

@EBatTiVo I had problems trying to debug plugin using CE, but worked when using Ultimate.
After that, I downloaded jar file from IDEA site and installed on Ultimate edition, and it kinda works as expected. Is it incompatible with CE?

You mean the Haxe debugger is working correctly for you, now that you're using Ultimate and the 0.9.10 released jar file?  Or do you mean that you can debug the plugin, but you still haven't solved your problem of debugging your app?
Some community folks use the IDEA-CE, but none of the developers of the plugin do.  We all use Ultimate.  At one time, we were using some classes that were only available on Ultimate, so those features would break on CE, but I thought some folks removed those dependencies -- at least so that they could build the plugin using CE.  I did not expect that debugging was a feature that depends upon Ultimate.

The Haxe debugger seems to work correctly using 0.9.10 release and Ultimate.
Also, I can debug the plugin itself using CE since I use the Ultimate .app as reference to sdk folders (it ends up debugging Ultimate, but works as expected).

@arthurferrai I'm closing this since you've got everything working.

@EBatTiVo I expected to use debug on CE, but I understand that it only works with Ultimate. :)

@arthurferrai I actually haven't tried debugging on CE, and I don't know why it wouldn't work.  It may be one of the features of Ultimate that just isn't implemented on CE (missing support classes or somesuch)?  If you have the time, and since you have the environment set up to debug the plugin, if you wanted to figure it out, we would be happy to include that support.


Unable to import pygame

When I run a game in pygame the init.py file is created(the pygame module) and I get the following error:
Traceback (most recent call last):
  File "C:\Users\User\Desktop\Γιάννης\python\race\A bit racey.py", line 1, in <module>
    import pygame
  File "C:\Users\User\AppData\Roaming\Python\Python36\site-packages\pygame\__init__.py", line 133, in <module>
    from pygame.base import *
ModuleNotFoundError: No module named 'pygame.base'

The pygame is installed, so the 'pygame.base' should exist.

You should try to start it from the command line, outside of Visual Studio to see if that works any better.
I just installed pygame (using pip) into a 32-bit and also 64-bit Python 3.6 virtual environment, and ran import pygame successfully on both using F5 to start debugging from Visual Studio 2017.

I did it by uninstalling and reinstalling pygame using pip. Thanks

I also encountered similar error, though I have uninstalled and reinstalled pygame multiple time (in the correct path and correct version), can anyone help?

@rrraj I had the same issue as you and couldn't find anything to help me anywhere. I tried out many things and for me the issue was that my python was 32 bit and it couldn't work with pygame. I uninstalled python and installed a 64 bit version and now everything works well.
Hope this helps.


a error

When loading the graph, the following node types were not found:
Moore-AnimateAnyone Image Encoder
Moore-AnimateAnyone Reference Unet
Moore-AnimateAnyone Denoising Unet
Moore-AnimateAnyone Pose Guider
VHS_LoadVideo
Moore-AnimateAnyone Pipeline Loader
VHS_VideoCombine
Moore-AnimateAnyone Simple
Moore-AnimateAnyone VAE
Nodes that have failed to load will show as red on the graph.

显卡不够，运行不了


[CSL-883] Tests/csl883 chrono

I think it makes sense two squash all four commits. Or at least the first two.