[Feature request] Add parentheses/parentheses support to the standard calculator.

Problem Statement

Parentheses are common parts of simple calculations. Oddly enough, the standard calculator has exponents and a couple of other advanced tools but doesn't have parentheses or support for them being added by typing. Almost every time I go to do simple calculations, I find the need to calculate something additionally in the middle of the calculation by use of parentheses. On mobile platforms, it's simple enough because their calculator applications have parentheses in them. On Windows, I have to switch over to Scientific mode which makes me lose the current calculation that I'm working on, or I have to remember to start in Scientific, which is a slightly bloated environment for simple calculations in a small window.
Evidence or User Insights

Proposal

Goals

Non-Goals

Low-Fidelity Concept

Requested Assignment

I'm just suggesting this idea.  I don't want to implement it.

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.

I support this.


Trying to run in docker fails, possibly an issue with python3.8

⚠IMPORTANT⚠ if you do not fill this out, we will automatically delete your issue. We will not help anyone that cannot fill out this template.

[x] Have you read our Wiki page "Common Issues & Their Solutions"?

yes
Describe the bug
Not working with docker. Running the exact command referenced in the documentation:
docker run -it --rm remnux/ciphey "=MXazlHbh5WQgUmchdHbh1EIy9mZgQXarx2bvRFI4VnbpxEIBBiO4VnbNVkU"
Returns:
Traceback (most recent call last):
  File "/usr/local/bin/ciphey", line 8, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/ciphey/ciphey.py", line 221, in main
    config.complete_config()
  File "/usr/local/lib/python3.8/site-packages/ciphey/iface/_config.py", line 196, in complete_config
    self.load_objs()
  File "/usr/local/lib/python3.8/site-packages/ciphey/iface/_config.py", line 141, in load_objs
    self.objs["checker"] = self(_fwd.registry.get_named(self.checker, PolymorphicChecker))
  File "/usr/local/lib/python3.8/site-packages/ciphey/iface/_config.py", line 112, in __call__
    return self.instantiate(t)
  File "/usr/local/lib/python3.8/site-packages/ciphey/iface/_config.py", line 107, in instantiate
    ret = t(self)
  File "/usr/local/lib/python3.8/site-packages/ciphey/iface/_modules.py", line 163, in __init__
    self._base = cls(config)
  File "/usr/local/lib/python3.8/site-packages/ciphey/basemods/Checkers/ezcheck.py", line 50, in __init__
    self.checkers.append(config(Brandon))
  File "/usr/local/lib/python3.8/site-packages/ciphey/iface/_config.py", line 112, in __call__
    return self.instantiate(t)
  File "/usr/local/lib/python3.8/site-packages/ciphey/iface/_config.py", line 107, in instantiate
    ret = t(self)
  File "/usr/local/lib/python3.8/site-packages/ciphey/iface/_modules.py", line 163, in __init__
    self._base = cls(config)
  File "/usr/local/lib/python3.8/site-packages/ciphey/basemods/Checkers/brandon.py", line 191, in __init__
    self.top1000Words = config.get_resource(self._params().get("top1000"))
  File "/usr/local/lib/python3.8/site-packages/ciphey/iface/_config.py", line 206, in get_resource
    return self(_fwd.registry.get_named(loader, ResourceLoader))(name)
  File "/usr/local/lib/python3.8/site-packages/ciphey/iface/_modules.py", line 282, in __call__
    return self.getResource(*args)
  File "/usr/local/lib/python3.8/site-packages/ciphey/basemods/Resources/cipheydists.py", line 32, in getResource
    return self._getters[prefix](name)
  File "/usr/local/lib/python3.8/site-packages/cipheydists/__init__.py", line 19, in get_list
    return json.loads(pkgutil.get_data(__name__, os.path.join("list", name) + ".json"))
  File "/usr/local/lib/python3.8/json/__init__.py", line 357, in loads
    return _default_decoder.decode(s)
  File "/usr/local/lib/python3.8/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/local/lib/python3.8/json/decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Plaintext
⚠IMPORTANT⚠ The below code is non-negotiable for "Ciphey didn't decrypt...." problems. If you do not tell us your plaintext, we will not help you.
Not sure what the plaintext is, it was the example from the documentation

Version
⚠IMPORTANT⚠ We need this information because different environments will induce different bugs in Ciphey

OS/Distro: macOS Catalina
Python version: 3.8
Ciphey versions: Whatever version is in docker right now
Did you use Docker? Yes

Verbose Output
⚠IMPORTANT⚠ Verbose output will tell us why it's not working the way we expected it to be.
https://pastebin.com/TMVDnk4f
To Reproduce
Steps to reproduce the behavior:

What input did you use? docker run -it --rm remnux/ciphey "=MXazlHbh5WQgUmchdHbh1EIy9mZgQXarx2bvRFI4VnbpxEIBBiO4VnbNVkU"
What flags / arguments did you use? No extra flags or arguments

Expected behavior
To see ciphey decrypt or at least attempt to decrypt the input
Any other information?
Related to #398. But I actually filled out the template.

I found a workaround by using a different docker base image python:3.7.9-slim-buster
So the full dockerfile just looks like:
FROM python:3.7.9-slim-buster
LABEL version="1.1"
LABEL description="Ciphey - An Automated Decoding and Decryption Tool"
LABEL maintainer="Lenny Zeltser"
ENV LANG C.UTF-8
ENV LANGUAGE C.UTF-8
ENV LC_ALL C.UTF-8

USER root

RUN pip3 install --upgrade pip && \
  pip3 install --upgrade ciphey && \
  groupadd -r nonroot && \
  useradd -m -r -g nonroot -d /home/nonroot -s /usr/sbin/nologin -c "Nonroot User" nonroot && \
  mkdir -p /home/nonroot/workdir && \
  chown -R nonroot:nonroot /home/nonroot

USER nonroot
ENV HOME /home/nonroot
WORKDIR /home/nonroot/workdir
VOLUME ["/home/nonroot/workdir"]
ENV USER nonroot
ENTRYPOINT ["/usr/local/bin/ciphey"]
CMD ["--help"]

This doesn't fix the issue, since ciphey should be able to work with python3.8, but this is a possible temporary workaround

Hi!
I'm only just being drafted in to have a look at this. Thanks for raising the issue, I understand what the problem is here. As it stands, Ciphey relies on REMnux's DockerHub Repo. We can't do any CI/testing and issues such as caching (which is where I think this problem specifically lays within)
I'm going to be making Ciphey a little bit more self-sustainable in this regard over the next day or so.

This doesn't fix the issue, since Ciphey should be able to work with python3.8, but this is a possible temporary workaround

Exactly this for the time being! (:
I've pushed a working build to cmnatic/ciphey in lieu of creating a Ciphey organisation tomorrow, in the mean while, you can see example usage below:
docker run -it --rm cmnatic/ciphey =MXazlHbh5WQgUmchdHbh1EIy9mZgQXarx2bvRFI4VnbpxEIBBiO4VnbNVkU
Result on a brand new DO Droplet:

replace "=MXazlHbh5WQgUmchdHbh1EIy9mZgQXarx2bvRFI4VnbpxEIBBiO4VnbNVkU" with your value appropriately

As it stands, files cannot be parsed to Ciphey i.e. ciphey -f input.txt as I wasn't quite expecting to be anywhere near publishing yet.
The Dockerfile that this is created from is a "band-aid" until I can afford the time to implement all of the above ^^ (note how there are minuscule changes made from the REMnux Dockerfile, where it's accredited nonetheless)


Single node Pythia 14M training on ngc pytorch 24.02 container

Swapped the raw cuda container for the ngc pytorch 24.02 container.
This one has OpenMPI, PyTorch and Apex already installed, so those setup steps can be removed.
flash-attn was recently hotfixed for that container version, so 2.5.6 is a hard requirement.
To validate the setups, I ran a few training steps of Pythia 14M on 8xA100 and a 22B model on 8xA100 and 8xH100 w/ TP8.
For multi node tests I will have to adapt the launcher first.

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

Yep this LGTM. Agree on the requirements cleanup, but let's leave that for a followup.


Build failure

[INFO] Finished at: 2021-11-16T02:05:36Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.springframework.boot:spring-boot-maven-plugin:2.6.0-SNAPSHOT:repackage (default) on project spring-cloud-kubernetes-example-reload: Execution default of goal org.springframework.boot:spring-boot-maven-plugin:2.6.0-SNAPSHOT:repackage failed: A required class was missing while executing org.springframework.boot:spring-boot-maven-plugin:2.6.0-SNAPSHOT:repackage: org/apache/maven/shared/artifact/filter/collection/ArtifactFilterException
[ERROR] -----------------------------------------------------
[ERROR] realm =    plugin>org.springframework.boot:spring-boot-maven-plugin:2.6.0-SNAPSHOT
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/home/circleci/.m2/repository/org/springframework/boot/spring-boot-maven-plugin/2.6.0-SNAPSHOT/spring-boot-maven-plugin-2.6.0-SNAPSHOT.jar
[ERROR] urls[1] = file:/home/circleci/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import  from realm ClassRealm[maven.api, parent: null]]

Need to look and understand why it fails

@wind57 that's a temporary glitch that can happen when a snapshot jar is unfortunately corrupted. This is a problem we're having with our repository that we haven't been able to track down.

I see, thank you and sorry for commenting in that issue also, was not aware I should not.

sorry for commenting in that issue also, was not aware I should not.

No worries. If you comment in two different projects, there is a chance that different persons are going to spend time trying to understand, leading to duplicated efforts.


Refactoring/pado local hero

try to tackle down some problems such as #73

I'll test it tomorrow. As for the lombok thing: did you tell it to use local profile? Not all param are set in the default profile (maybe that would be a good idea...)

yes I used the local profile. Problem seems to be for me/on my machine that lombock checks these params in the constructor but spring sets the values from the application-local.properties file later (after the construction) using the setters

That's weird, never seen this behaviour before and used it like this for quite a while in other projects. Anyway, it doesn't really hurt if we're not using them for now.


Missing support for direct JavaScript payloads

Rouge-jndi currently only allows the execution of OS commands. Until Java 17, it was possible to execute directly JavaScript code, a feature that is currently used by the Tomcat controller.
String payload = ("{" +
            "\"\".getClass().forName(\"javax.script.ScriptEngineManager\")" +
            ".newInstance().getEngineByName(\"JavaScript\")" +
            ".eval(\"java.lang.Runtime.getRuntime().exec(${command})\")" +
            "}")
            .replace("${command}", makeJavaScriptString(Config.command));

Instead of passing a OS command, it should be possible to pass a file with JavaScript code that would be executed directly.
TODOs:

Update the Tomcat controller, so that it passes the content of the JavaScript file to the ScriptEngineManager
Check the other controllers, if they can be modified to support this as well. In case of the Groovy Controller, it might be possible to pass a Groovy script
Update the HTTP Server, so that the class file that is downloaded includes the content of the JavaScript file.

Implemented with ac433484d135087194b75683f6d4b335e13e2ca3.


Generalizing the functionality for adding members in the members tab for organizations.

Feature Description
I propose the ability to add members in the org directly from the the Members tab.
Currently, the Members tab simply enumerates all members across all teams, and it could get confusing because you may not know why those users are there (or which team they're in) or how/where to add them.
I do believe that Instead, teams should function more like roles assigned to users rather than being the primary criteria for their inclusion in the organization. it should be solely based off their presence in the default members team.
The Add members dialog could have the optional step to add them to a team(s)
Screenshots

('Add member' button added for illustrative purposes)

I think maybe an org member who doesn't belong to any team has meaning because of private/limit organizations that exist.


bench: init tasks benchmark

init 4 tasks benchmark

archived project detection and prediction
bot detection
behavior data completion and prediction
opensource sentiment analysis

Great~


Update Winning Positions of finalized Market after proceeds claimed

Currently after a winning position is finalized and claimed, we remove Order Type and change data fields to 0.  User cannot tell what they had on. So if user had short position (like shorting "Yes" and Outcome "No" was the market winner - (the short "yes" is a winner also) see screenshot....

We only remove data for finalized and claimed winning resolved positions, but not losing resolved positions so looks confusing....

Changes suggested to make:
Remove (Current Value), Add in Status (which would include claim, or closed)
Outcome /   Status  /   Type  /  Quantity /   Avg Price   /   Total Cost   /    Last Price   /    Total Returns
Yes          /    Closed /   Short/     100      /      .5            /           50       /             0       /                $50

K this is updating correctly...will be improved with rc2 update


Create ocsb

Domain for Ottawa Catholic School Board educators, staff, and teachers. see #1694 for students
Example e-mail<EMAIL_ADDRESS>

@ErikHumphrey I am sorry, I am closing this request with no merging due to reasons discussed in https://github.com/JetBrains/swot/issues/1694. Also, I have to mention that free licenses available to all people with email domains listed in this repository are for educational purposes only, thus if not just students and teachers of the schools can use such addresses, I can not encourage you to reopen the request.
As it was mentioned in https://github.com/JetBrains/swot/issues/1694, all teachers who would like to use JetBrains tools in their courses are welcome to request Classroom licenses by emailing to<EMAIL_ADDRESS>Thank you for your understanding.


Release proposal: v5.0.4

This is the same as the #1892 but without the lone apparent semver-major: #1818. See thread in https://github.com/nodejs/node-gyp/issues/1791#issuecomment-535169433 for more discussion on this approach.
Will take advice on what else this needs, I don't have any strong opinions other than "let's get this stuff out".

[f753c167c5] - gyp: decode stdout on Python 3 (cclauss) #1890
[60a4083523] - doc: update xcode install instructions to match Node's BUILDING (Nhan Khong) #1884
[19dbc9ac32] - deps: update tar to 4.4.12 (Matheus Marchini) #1889
[5f3ed92181] - bin: fix the usage instructions (Halit Ogunc) #1888
[aab118edf1] - lib: adding keep-alive header to download requests (Milad Farazmand) #1863
[1186e89326] - lib: ignore non-critical os.userInfo() failures (Rod Vagg) #1835
[785e527c3d] - doc: fix missing argument for setting python path (lagorsse) #1802
[a97615196c] - gyp: rm semicolons (Python != JavaScript) (MattIPv4) #1858
[06019bac24] - gyp: assorted typo fixes (XhmikosR) #1853
[3f4972c1ca] - gyp: use "is" when comparing to None (Vladyslav Burzakovskyy) #1860
[1cb4708073] - src,win: improve unmanaged handling (Peter Sabath) #1852
[5553cd910e] - gyp: improve Windows+Cygwin compatibility (Jose Quijada) #1817
[8bcb1fbb43] - gyp: Python 3 Windows fixes (João Reis) #1843
[2e24d0a326] - test: accept Python 3 in test-find-python.js (João Reis) #1843
[1267b4dc1c] - build: add test run Python 3.7 on macOS (Christian Clauss) #1843
[da1b031aa3] - build: import StringIO on Python 2 and Python 3 (Christian Clauss) #1836
[fa0ed4aa42] - build: more Python 3 compat, replace compile with ast (cclauss) #1820
[18d5c7c9d0] - win,src: update win_delay_load_hook.cc to work with /clr (Ivan Petrovic) #1819

This PR isn't meant to be merged into master, it will establish a v5.x branch that we'll maintain like we do in nodejs/node for as long as we need a v5.x release line to live (as yet undetermined).

hm, I'm not sure why this isn't showing properly, I've only removed that one commit which makes this the only meaningful diff when doing a git diff v5.x master locally:
diff --git a/lib/find-python.js b/lib/find-python.js
index 30bb25f..1a4390d 100644
--- a/lib/find-python.js
+++ b/lib/find-python.js
@@ -19,7 +19,7 @@ PythonFinder.prototype = {
   argsExecutable: [ '-c', 'import sys; print(sys.executable);' ],
   argsVersion: [ '-c', 'import sys; print("%s.%s.%s" % sys.version_info[:3]);' ],
   semverRange: process.env.EXPERIMENTAL_NODE_GYP_PYTHON3 ? '2.7.x || >=3.5.0'
-    : '>=2.7.0 <3.0.0',
+    : '>=2.6.0 <3.0.0',

   // These can be overridden for testing:
   execFile: cp.execFile,

The "files changed" isn't correct, at least according to my diff. I suppose it's because this PR is adding one HEAD commit (changelog and version bump) but removing a commit way back in history, and for some reason it's getting confused?
@cclauss the changes you're commenting on are on master so maybe they need a PR to address them?

@rvagg This LGTM.  @cclauss's comments are addressed in https://github.com/nodejs/node-gyp/pull/1894 -- could you land that, and then cherry-pick it into 5.x? That will fix the known py3 issues (and as for unknown issues, we don't know :-).

done, I suppose I'll push this out then!

Included #1895 too and published as v5.0.4. Closing this PR but this branch, v5.x, will live on as our branch to maintain the v5.x series while we also move on to 6.0.0.


Order by aggregation

I have this .yml file:
measure:
  key: adherence_top_five_bottom_five
  name: Percent Adherence to ACOG Guidelines
  aggregation: percent_correct_steps
dimensions:
- key: session_date_time
  granularity: month
  label: Month
- key: site
filters:
- branch
- session_date_time
- site
chart:
  type: line
  datasets:
    fill: false
    lineTension: 0
  options:
    legend:
        position: right

I need to display the top 5 results in the chart.  In order to do so, I need to order DESC by the aggregation "percent_correct_steps" and then limit the results.  Is there currently a way to do this?
Thanks!

Hi
I think the best way to go about this is to create your own custom data method and use which will offer you more flexibility in the future or set up a limit_filter in .yml file
filters:
  - take_five

And then limit the return to 5 top results in the model, for example
User.limit(5)

and then in your view, add a limit filter, which is set to true
<%= label_tag :take_five do %>
    <%= f.check_box :take_five, :checked => true, :style => 'visibility: hidden' %>
<% end %>


Header and photos broken at https://crimethinc.com/2016/10/26/work-speaking-tour-on-the-iberian-peninsula

Lots of photos are broken, really. Maybe it doesn't make sense for me to list every URL?

True. It's on my radar to fix all broken images. In the meantime, I'm closing this issue.


Changed license to Apache 2

Resolves #196.

We need to change it here as well:
https://github.com/typelevel/grackle/blob/78c9e76fe9257db48e4606516057dc9617190b18/build.sbt#L36

Yup, I found that while porting to sbt-typelevel-site. Fix in progress.


Option to include More Distribution

Included in this PR is an option to use LogNormal distribution for Monte-Carlo simulation.
There was an issue with the MinMax scaler, which was supposed to scale the samples between 0-1, but it has some overlap up to 0.0000000002 which was why I used a feature range argument.
The option was changed for Distribution, Chaospy LogNormal uses Camel case. Applying a .title method on the string wouldnt work.

@ekatef I have added more options for more distribution. The distribution now covers Uniform, Normal, LogNormal, Triangular, Beta and Gamma distribution. I have also handled the option for variables.
Happy to have you review it.

Hello @GbotemiB! Very nice work and sorry for the late review.
Have added some comments to your code. My feeling is that it would be great to setup a convenient way to set distribution parameters keeping in mind that a user may want to use different distributions.
Regarding the issue with 0.0000000002, have you tried to investigate that? Using range(0,0.99) may work as a quick fix, but it would be great to better understand the reason behind this discrepancy to be sure that we understand everything properly.

@GbotemiB looks great!
My feeling is that the only part missing is a short block calculating the third parameter for triangular distribution, in case only two parameters have been supplied in the config.
Agree that it may be worth to have some validity checks for the parameters supplied to create distribution. However, I suppose sklearn may still have some internal checks and meaningful error messages. Could you please do quick testing on that?

@GbotemiB looks great!
My feeling is that the only part missing is a short block calculating the third parameter for triangular distribution, in case only two parameters have been supplied in the config.
Agree that it may be worth to have some validity checks for the parameters supplied to create distribution. However, I suppose sklearn may still have some internal checks and meaningful error messages. Could you please do quick testing on that?

I have added a fix for handling the errors for Triangular distribution. I also handled likely errors for the other distributions.
Btw I am using chaospy to handle the creation of the distribution not sklearn.

@GbotemiB great additions!
Checks are usually not very easy to implement, but they make life much easier.
Have added a couple of suggestions to the code on the implementation details of the checks. Apart of them, my general feeling is that it could make sense to wrap the checks into a dedicated function. Another general point is keeping comments focused on the reasons of the code behaviour, not on the implementation itself. Would be great if you could please revise the comments to make them more precise.

Thanks @ekatef. I will work on the comments and get back to you.

Hello @ekatef, I have added an additional functionality to verify the parameters.
I also have not figured out how to handle the string formatting for the different distributions. I am open to suggestions.

Hello @ekatef, I have added an additional functionality to verify the parameters.
I also have not figured out how to handle the string formatting for the different distributions. I am open to suggestions.

@GbotemiB great, thanks for introducing the changes! My feeling is that code readability has been improved significantly thanks to wrapping-up validity checks into validate_parameters() function.
A general comment: please, revise comments in the code according to what we have discussed recently. Comments in the code should answer on the questions What for?/Why?, not What does the line does?. E.g. seeing if SAMPLING_STRATEGY not in valid_strategy, a reader understands that that is a validity check for a SAMPLING_STRATEGY, so a comment Check if the sampling strategy is valid just distracts.
Not sure what do you mean with string formatting for distributions. Could you please elaborate a bit?

Thanks for the review.
Regarding, string formatting for distribution, the current inputs are in title case while LogNormal is having an improper case https://github.com/GbotemiB/uncertainty-esm/blob/dev/config.yaml#L22. I think it is cleaner if the inputs were in lower case, that way users dont have to both about string cases. What are your thoughts?

Thanks for the review.
Regarding, string formatting for distribution, the current inputs are in title case while LogNormal is having an improper case https://github.com/GbotemiB/uncertainty-esm/blob/dev/config.yaml#L22. I think it is cleaner if the inputs were in lower case, that way users dont have to both about string cases. What are your thoughts?

Hey @GbotemiB!
Do you have any updates regarding OOP implementation? If this way doesn't feel straight enough, let's probably finalise this PR as is, an add an issue on possible OOP re-implementation? What do you think?
Regarding the formatting, I'd assume that it's a proper camel case :) So, no fixes are needed, in my opinion.

@ekatef Awesome. Adding the OOP implementation later sounds great.
We can conclude this PR with just the chaospy implementation. Then I can include implementation with scipy and pydoe2 in another PR.

@GbotemiB Look great 😄 Merging!


010editor: init at 15.0

Description of changes
Add 010editor, a professional text and hex editor.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review run on x86_64-linux 1

1 package built:

_010editor

Thanks for the review @nbraud. Hope I properly addressed your suggestions.

Oh, I think the commit message should technically start with "_010editor" too.

Thanks for the review!


New version for Scala 2.12.11

Would be nice to get this cross-published for newly released Scala 2.12.11. Pretty please

1.4.2 released for all versions.
On Sat, 21 Mar 2020 at 14:48, Greg Oledzki<EMAIL_ADDRESS>wrote:

Assigned #316 https://github.com/sksamuel/scapegoat/issues/316 to
@sksamuel https://github.com/sksamuel.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/sksamuel/scapegoat/issues/316#event-3152036496, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFVSGVIWMVHY4IEP6PCUMLRIUKYHANCNFSM4LNV5JRA
.

Doesn't look like 2.12.11 made it to all versions

I confirm I see the same as you do at https://search.maven.org/search?q=g:com.sksamuel.scapegoat
@sksamuel did you release for 2.12.11?

I did a full release so I thought.
On Fri, 27 Mar 2020 at 00:18, Greg Oledzki<EMAIL_ADDRESS>wrote:

Reopened #316 https://github.com/sksamuel/scapegoat/issues/316.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sksamuel/scapegoat/issues/316#event-3171006001, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFVSGVNREH6Z6CMCJCIYNLRJQZIRANCNFSM4LNV5JRA
.

After the recent changes where do we specify the list of cross versions ?

Since I removed travis config and the travis sbt plugin you need to manually release for each version - I know it's a pain and I'll try to automate all this in the next day or so.

I guess a simple shell script would be enough for now.

hey folks, any help is needed to push this forward?

We have a new release pipeline now, we should try it out 😉

OK. I am trying although I don't know if I am doing the right thing here.
I went to Releases, took the private Draft, named it 1.4.3 with v1.4.3 tag and clicked Publish release.

Failed with
 [info] Nexus repository URL: https://oss.sonatype.org/service/local
[info] sonatypeProfileName = com.***.scapegoat
[info] Preparing a new staging repository for [sbt-sonatype] scalac-scapegoat-plugin 1.4.3
[info] Reading staging repository profiles...
[info] Reading staging profiles...
[info] No previous staging repository for [sbt-sonatype] scalac-scapegoat-plugin 1.4.3 was found
[error] java.lang.IllegalArgumentException: Profile com.***.scapegoat is not found. Check your sonatypeProfileName setting in build.sbt
[error] Use 'last' for the full log.
##[error]Process completed with exit cod

The triple asterisk (***) looks fishy

sbt-sonatypes says:

sonatypeProfileName
This is your Sonatype acount profile name, e.g. org.xerial. If you do not set this value, it will be the same with the organization value.

Trying https://github.com/sksamuel/scapegoat/commit/af19c8ad47b3e3856c12df8632cb42e8dcb6136e#diff-45ac75879221b921f35800b2421aa728

Didn't work, reverting.

Nah. After moving the tag it failed with:
- Your workflow file was invalid: The workflow is not valid. .github/workflows/master-release.yml (Line: 38, Col: 14): Unrecognized named-value: 'SONATYPE_USERNAME'. Located at position 1 within expression: SONATYPE_USERNAME

With fixing the variable name it fails with the previous message:
[error] java.lang.IllegalArgumentException: Profile com.***.scapegoat is not found. Check your sonatypeProfileName setting in build.sbt

Reverting the workflow change.
I guess we might try simply adding this variable to build.sbt (a bit unclean solution, but I guess it might work).

Now the changes seems to have taken effect, but they weren't good either:
[error] java.lang.IllegalArgumentException: Profile *** is not found. Check your sonatypeProfileName setting in build.sbt

Another guess is to specify the profile name to com.sksamuel, an idea inspired by https://issues.sonatype.org/browse/OSSRH-54525?focusedCommentId=896956&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-896956

And that worked!
Sam has event received an email ;)

[info]      email<EMAIL_ADDRESS>
Let's see if the versions have landed in Maven in a few hours.

Those sonatype emails never ever get sent FYI. Not that it matters.
On Thu, 9 Apr 2020 at 16:25, Greg Oledzki<EMAIL_ADDRESS>wrote:

And that worked!
Sam has event received an email ;)
[info] email<EMAIL_ADDRESS>Let's see if the versions have landed in Maven in a few hours.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sksamuel/scapegoat/issues/316#issuecomment-611759910,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFVSGX62PL2TEH75USV72TRLY4LFANCNFSM4LNV5JRA
.

@jozic there it is

Also the need to specify sonatypeProfileName - I guess it's a bug in sbt-release - most likely due to incompatibility with what sbt-sonatype expects as input.

Nice.
On Fri, 10 Apr 2020, 02:34 Greg Oledzki<EMAIL_ADDRESS>wrote:

Also the need to specify sonatypeProfileName - I guess it's a bug in
sbt-release - most likely due to incompatibility with what sbt-sonatype
expects as input.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sksamuel/scapegoat/issues/316#issuecomment-611918080,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFVSGXT72CBROJGEU3GLCLRL3D2FANCNFSM4LNV5JRA
.

Just catching up with this thread, well done @mccartney for fixing this.

Also the need to specify sonatypeProfileName - I guess it's a bug in sbt-release - most likely due to incompatibility with what sbt-sonatype expects as input.

It's not a bug - you need to specify the profile name explicitly if it doesn't match the organisation name (com.sksamuel.scapegoat in this case). Sorry, it's something I missed - I didn't realise that Sam was using com.sksamuel as the profile, which obviously makes perfect sense now 😄


More isolation problems

I'm seeing new problems with the latest MSBuild APIs and .NET Core SDK. It looks like this is another case of isolation: if Buildalyzer is used to build a project that pins an older SDK version and then tries to build one that uses a newer SDK, the older SDK's assemblies are already loaded and incompatibilities arise. Likewise building from the VS build tools and then building an SDK project (or vise versa). I'm wondering if stale static state and assemblies is also responsible for some of the other problems we've been seeing.
I think I'm going to have to address this permanently, though it will be a significant change.
I've got two ideas right now:

Continue to use the MSBuild APIs, but set up separate AppDomains for each build. I'll have to figure out how to marshal data from the MSBuild API back to Buildalyzer and we'll still be subject to MSBuild API compatibility with the build tools.
Stop using the MSBuild API altogether and instead fork out to MSBuild directly, capturing and parsing output. Unclear if I can get everything we need directly from MSBuild output though.

In both these approaches, we'll loose the ability to get the raw MSBuild API objects. If the AppDomain approach, I'm pretty sure I can't marshal everything in the MSBuild API. If the forking approach, there won't be an MSBuild API object to get.

Buildalyzer 2.0 out now with out-of-process MSBuild gathering data via an MSBuild logger that sends log events through pipes.


Suggestion: Update regex pattern for validating file paths

Maybe it's a good idea to update the regex pattern for validating filepaths which for example is used in New-IntuneWin32AppIcon.
The current pattern used is "^[A-Za-z]{1}:\\w+\\w+" which doesn't account for dashes in paths. Was pulling my hair out for the last 30 minutes figuring out why the cmdlet didn't accept the path because it is perfectly valid ;).

Just been hitting the same thing.
It's worse than not accepting punctuation, you also have to use a folder on the disk not the root, and you can't have spaces in the folder path anywhere.

This makes total sense, I'll look into fixing that. If any of you have a better regex, I'm all ears.

The same for me - I had the same issues, when tried to run these commandlets from Linux machine and one of big issues is regex rules for checking paths - because on WSL I don't have paths like "C:....". So my suggestion to change somehow these validating rules.

Out of curiosity, why are you not running this module in a PowerShell console directly in Windows, but in WSL? Although it's not stated anywhere for the module, it's not a scenario that I'm testing at all when developing this module.

I'm going to with the following regex, if nobody has a better one or objections:
$Pattern = '^[a-z]:\\(?:[^\\/:*?"<>|\r\n]+\\)*[^\\/:*?"<>|\r\n]*$'
"C:\Folder" -match $Pattern
"C:\Folder\SubFolder" -match $Pattern
"C:\Folder\SubFolder\File.intunewin" -match $Pattern
"C:\Folder\SubFolder\File.png" -match $Pattern
"C:\Folder Space" -match $Pattern
"C:\Folder Space\SubFolder" -match $Pattern
"C:\Folder Space\SubFolder\File.intunewin" -match $Pattern
"C:\Folder Space\SubFolder\File.png" -match $Pattern
"C:\Folder.Dot" -match $Pattern
"C:\Folder.Dot\SubFolder" -match $Pattern
"C:\Folder.Dot\SubFolder\File.intunewin" -match $Pattern
"C:\Folder.Dot\SubFolder\File.png" -match $Pattern

All of the above renders True.

Including UNC paths would be much appreciated. https://github.com/MSEndpointMgr/IntuneWin32App/issues/17

Including UNC paths would be much appreciated. #17

While I'm not a fan of it, as it potentially brings new issues into the mix (since the code has never been tested with UNC paths), wouldn't it be easier for you to simply mount your network share instead?

The same for me - I had the same issues, when tried to run these commandlets from Linux machine and one of big issues is regex rules for checking paths - because on WSL I don't have paths like "C:....". So my suggestion to change somehow these validating rules.

Out of curiosity, why are you not running this module in a PowerShell console directly in Windows, but in WSL? Although it's not stated anywhere for the module, it's not a scenario that I'm testing at all when developing this module.

Just because I want to put it into pipelines (Jenkins) and as for me better will be to run these scripts from Linux.
I can say, that almost all comandlets from this repo is cross platform (good job, really, I can run it on Powershell 7 in Linux), except part with regex. On my system I just commented sections with regex, as workaround, but I can't say that is good way to solve this.

Could it be moved from a rexex to using test-path?

That makes total sense, although I've used it in Pipelines on a Windows host as I don't really know Linux that much. I'm leaning towards simply just scrapping the regex validation, and only keep the Test-Path piece of the code. Would you be able to validate a pre-release of 1.4.0 that it works as expected in a cross-platform scenario, if I made it available?

Yes, I'll try to check it as soon as possible and will provide results in this issue, thanks for your help 😄 👍

1.4.0 (RC) source code is now in the repo. Regex validation has been replaced with Test-Path detection instead. Please test it out to see if it works :)

Hello, @NickolajA!
1.4.0 works like a charm (tested on Windows Powershell and Linux Powershell) - I also fixed other issues, with requirements, many thanks for your support :)
Name                           Value
----                           -----
PSVersion                      7.3.2
PSEdition                      Core
GitCommitId                    7.3.2
OS                             Linux <IP_ADDRESS>-microsoft-standard-WSL2 #1 SMP Wed Mar 2 00:30:59 UTC 2022
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

That's awesome, thanks for validating!

I'll mark this as fixed now, as this will be added to 1.4.0 that should come out in the next few days.


[Question] Mediator sample code not working

Hi, I have been following the documentation to setup a mediator, and after that I tried simply to open the http url http://localhost:3001/?oob=eyJAd... and I got a Cannot GET /
I thought maybe there is something wrong with that example code and then, I got to the mediator sample in the repo: samples/mediator.ts. I added the required dependencies, and no luck, same issue: Cannot GET /
I am sure I am missing something, but no clue what.

Ok, just ignore me... This is the expected way it works. Sorry.


Unable to import other python modules in called scripts

I have created a simple HTTP trigger-based azure function in python which is calling another python script to create a sample file in azure data lake gen 1. My solution structure is given below: -
FunctionApp
|_ HttpTrigger
|_____ init.py
|_____ Test.py
|_____ function.json
Requirements.txt contains the following imports: -

azure-functions
azure-mgmt-resource
azure-mgmt-datalake-store
azure-datalake-store

init.py
import logging, os, sys

import azure.functions as func
import json

def main(req: func.HttpRequest) -> func.HttpResponse:
    logging.info('Python HTTP trigger function processed a request.')
    name = req.params.get('name')
    if not name:
        try:
            req_body = req.get_json()
        except ValueError:
            pass
        else:
            name = req_body.get('name')

    if name:
        full_path_to_script = os.path.join(os.path.dirname( __file__ ) + '/Test.py')
        logging.info(f"Path: - {full_path_to_script}")
        os.system(f"python {full_path_to_script}")
        return func.HttpResponse(f"Hello {name}!")
    else:
        return func.HttpResponse(
             "Please pass a name on the query string or in the request body",
             status_code=400
        )

Test.py
import json
from azure.datalake.store import core, lib, multithread

directoryId = ''
applicationKey = ''
applicationId = ''
adlsCredentials = lib.auth(tenant_id = directoryId, client_secret = applicationKey, client_id = applicationId)
adlsClient = core.AzureDLFileSystem(adlsCredentials, store_name = '')

with adlsClient.open('stage1/largeFiles/File_256_KB.json', 'rb') as input_file:
    data = json.load(input_file)
    with adlsClient.open('stage1/largeFiles/File_256_KB_Result.json', 'wb') as responseFile:
        responseFile.write(data)

Test.py is failing with an error that no module found azure.datalake.store
Why other required modules are not working for Test.py since it is inside the same directory?

What IDE are you using to deploy?when you upload the code to the function app, you can click on 'OUTPUT' to see if you have successfully installed the azure.datalake.store package. Before doing so, make sure your requirements.txt contains "azure-datalake-store".
Downloading https://files.pythonhosted.org/packages/27/9a/e7140775b3f8f011ef5d001c12a3519310094375671950105519e30bb12b/azure_datalake_store-0.0.48-py2.py3-none-any.whl

Yes, I am able to successfully install azure.datalake,.store.package. I am using visual studio code.

First, two points need to be distinguished: the packages in requirement.txt file will eventually be installed in Azure function's environment; but the azure.datalake package is not installed locally.
So, we can hit this problem when I run test.py locally in visual studio code.
ERROR:
ModuleNotFoundError: No module named 'azure.datalake'

If we want test.py to run successfully locally, we need to install "azure-datalake-store" package in terminal locally, such as:
(.venv) PS D:\code\CS> pip install azure-datalake-store

Hi @imsiddsingh，
Has your issue been resolved after installing the  'azure-datalake-store' package locally?


Possible to create a StackBlitz/Plunker example?

Thanks for stopping by to let us know something could be better!
Is your feature request related to a problem? Please describe.
I'm not sure how to "approach" (i.e., build and run) the examples in your examples directory. I'm sure its trivial, but where do I get started?!
For instance your ReadMe has:
sample.component.ts as:
import { MarkerClusterer } from "@googlemaps/markerclusterer";

// use default algorithm and renderer
const markerCluster = new MarkerClusterer({ map, markers });

Obviously there is a lot more to producing a simple map than this...
Describe the solution you'd like
It would be nice to have a StackBlitz (or other easy isolated dev environment, like Plunker or CodePen) examples to ensure I'm setting up my environment correctly, have the right versions of related packages, and haven't made any typos...
Describe alternatives you've considered
I'm just browsing for full code examples to insert into my project as a starting point...
Additional context
Add any other context or screenshots about the feature request here.

At least add a link to this:
https://developers.google.com/maps/documentation/javascript/marker-clustering
which provides much more detail!

Oh, here is a sample to refer to...
https://stackblitz.com/github/googlemaps/js-samples/tree/sample-marker-clustering

https://developers.google.com/maps/documentation/javascript/marker-clustering#try-sample should have different playgrounds to test out this library.

Stackblitz is failing with the error
Google Maps JavaScript API error: RefererNotAllowedMapError https://developers.google.com/maps/documentation/javascript/error-messages#referer-not-allowed-map-error Your site URL to be authorized: https://zzmirxyza--github--3000.local-corp.webcontainer.io/


New secrets hook

Build a secrets hook that gets executed for genesis secret management.  Possible invocations:
./hooks/secrets add <env> <prefix>
./hooks/secrets check <env> <prefix>
./hooks/secrets rotate <env> <prefix>

These will currently only be responsible for rotating in the Vault, not credhub.

👍

This has been implemented int he v2.6 line.


Redundancy of optimiser.zero_grad()?

There are two calls of optimizer.zero_grad()
https://github.com/intel-isl/MultiObjectiveOptimization/blob/5d8e8343c56cf3184081f71cc4a661af64e7cf7e/multi_task/train_multi_task.py#L114
https://github.com/intel-isl/MultiObjectiveOptimization/blob/5d8e8343c56cf3184081f71cc4a661af64e7cf7e/multi_task/train_multi_task.py#L146
before optimizer.zero_grad() is called finally in line:
https://github.com/intel-isl/MultiObjectiveOptimization/blob/5d8e8343c56cf3184081f71cc4a661af64e7cf7e/multi_task/train_multi_task.py#L173
and optimizer.step() is applied.
Are the first two calls of optimizer.zero_grad() necessary or redundant?
Thx

In the current implementation, both are necessary. You can see that the loss is modified in between those two.
However, there is a way to implement it with using only one zero_grad by modifying the gradients directly. If the computation is an issue, you can compute the gradients, then compute the weights and finally replace gradients with weighted gradients and call the step.

Thank you very much for your swift response.


The new asset "themes", broke the components page.

I don't know if it's planned. But some css styles seem to have started to mix with styles from 'themes' page. E.g. almost all of the border radious are set to 0. (but not when I e.g. open menubar)

Fixed in https://github.com/shadcn-ui/ui/pull/1265. Thank you.


”Făurești”, ”Mănicea”, ”Mecea”, ”Oltețu”, ”Sășcioara” are listed in the drop-down menu

Description:
When user writes ”Făurești”, ”Mănicea”, ”Mecea”, ”Oltețu”, ”Sășcioara” the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Făurești"

Expected results
The location appears in the drop-down menu as "Sat Făurești, VÂLCEA (Zătreni)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Mănicea"

Expected results
The location appears in the drop-down menu as "Sat Mănicea, VÂLCEA (Zătreni)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Mecea"

Expected results
The location appears in the drop-down menu as "Sat Mecea, VÂLCEA (Zătreni)".

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Write in the search bar "Oltețu"

Expected results
The location appears in the drop-down menu as "Sat Oltețu, VÂLCEA (Zătreni)".

Step 8
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 9
Write in the search bar "Sășcioara"

Expected results
The location appears in the drop-down menu as "Sat Sășcioara, VÂLCEA (Zătreni)".


add extra steps for RHEL machines

Which issue this PR addresses:

Fixes
What this PR does / why we need it:
Quick nit to add the extra steps needed to get a working dev setup on a RHEL box.

Test plan for issue:

Is there any documentation that needs to be updated for this PR?

/azp run ci

/azp run ci


propose retiring arcalog

Changes introduced with this PR
Proposal to retire the Arcalog project from the Arcalot org.

By contributing to this repository, I agree to the contribution guidelines.

dustinblack force-pushed the retire-arcalog branch from ac06d1e to 4306c04
20 minutes ago

@dustinblack, what did you change?

Given Arcalog is based on (or inspired by?) a preprint academic paper, is this a safe thing to do with input from the authors? For example, if I were to submit a paper for peer review and the project it inspired (or was based on) was archived I would have preconceptions about that paper before even reviewing it.
Maybe this isn't worth considering and perhaps the fact that the project has gone undeveloped and unmaintained in that long has a higher weight.

Given Arcalog is based on (or inspired by?) a preprint academic paper, is this a safe thing to do with input from the authors? For example, if I were to submit a paper for peer review and the project it inspired (or was based on) was archived I would have preconceptions about that paper before even reviewing it.
Maybe this isn't worth considering and perhaps the fact that the project has gone undeveloped and unmaintained in that long has a higher weight.

We will be archiving Arcalog, not removing it entirely, and the main author and stakeholder has stopped being involved in the community and in Arcalog for more than year.


chore: tox equivalent CI

Thank you for the quick review.

I expect more expressive title or description nest time.

Understood. :ok_woman:


Enhancement: Ensure Recipient is set for specific actions

refactored the GroupsClient

Ready to merge from my side

Rebased

Would you mind to merge master into this one please?

I rebased master again


Add parameter validation for ECP module

Summary: Based on #1643, this PR adds parameter validation for the ECP module.

Thanks @mpg for your review. I believe I have addressed your comments. Could you please re-review?

@mpg I rebased this on top of the current #1643 and removed a few 'no-op's which @sbutcher-arm requested we shouldn't use.

@mpg Please ignore the first fauly rebase, and see https://github.com/ARMmbed/mbedtls/compare/b993ee4d65372b37cd26c68e487c23648724f239..486f1b33d72f960f7cb8b9fbd36d992a26697692 for the diff between the state before the two forced pushes and now.

Missing null check in mbedtls_ecp_restart_init,

Fixed.

Missing null check in mbedtls_ecp_check_budget.

The function only needs to check the group context, which it does.

Missing null check in mbedtls_ecp_curve_info_from_name.

The current parameter validation macros don't support functions returning pointers. I added an unconditional check. This might be preferable in any case, since strcmp() is undefined for NULL inputs.

Missing test cases for mbedtls_ecp_check_budget, mbedtls_ecp_group_init, mbedtls_gen_privkey, mbedtls_ecp_check_pub_priv

Fixed.

plus mbedtls_ecp_curve_info_from_name

No test added because the added check is unconditional and doesn't use parameter validation.

@hanno-arm Did you forget to push after the latest fixes? I can see you replied to Gilles that some things were fixed, but I can't see any new commits since his review, and the first issue does not appear to be fixed in the tip of the branch as I see it.

@mpg Yes, sorry for that, and thanks for noticing.

CI only failed in the known flaky timing test, so as good as a pass.

Reviewed, approved, passes CI, but needs rebasing.
Removing the 'needs: preceding PR' label, as PR #1643 has now been merged.

@sbutcher-arm I don't think this branch needs rebasing, it has no conflicts and was based on a recent enough version to pass CI.

@mpg - Yes, you're right. Thanks for changing the base - it has removed any commits from PR #1643.
Jenkins CI fails only with the BSD timing test, which is a known problem. The PR has been reviewed and approved and passed CI, so labelling as 'ready to merge'.


Fix: tvOS framework deployment target

The podspec states that the deployment_target for tvOS is 9.0, while the build settings for the framework specify it should be 10.0.
This means that installing through CocoaPods would allow the framework to be used against tvOS 9.0, while installing it with Carthage would require 10.0.
The tests ran without errors on tvOS 9.0 simulator.
fix #419

Good catch, thanks!


az Command does not output anything and returns errorcode 1

Describe the bug
The az command suddenly stopped working.
I get no console output whatsoever, only errorcode 1.
I tried uninstalling and re-installing the current version 2.53.1, but this did not help.
Related command
az
Errors
The command does not output anything. Error code on the console is 1.
Issue script & Debug output
Can't provide, I don't get any output at all.
Expected behavior
If az has a problem, it should at least output an error message.
Environment Summary
Can't provide, I don't get any output at all.
Additional context
No response

Thank you for opening this issue, we will look into it.

It could be possible that the az command is broken.

Where are you running Azure CLI, Windows, Linux or MacOS?
Which shell are you using?
Could you share a screenshot of what you are seeing?

I had the same issue.
I reinstalled Azure CLI, tried different PowerShell consoles, and updated PowerShell to the latest version.
However, the problem persisted.

There was nothing related in the EventLog.
OS: Windows 11 with the latest updates.
The issue, as it turns out, was with my system (cmd.exe). After some Windows updates, it stopped working as it should have (CMD exited immediately after running).
I fixed it by executing the following command:
%SystemRoot%\System32\reg.exe DELETE "HKCU\Software\Microsoft\Command Processor" /v AutoRun /f


Documenting local build

It was a little tricky to find how to run all the tests in the build. This is what I could tease out of your travis build.
Please let me know if this is good enough and if it's the appropriate place for it.

You don't need  -DtravisEnv=true if you are running the test locally.
 -DtravisEnv=true is a flag to trigger the surefire to stop redis server and redisson instance at the end of each single test case and start a fresh instance before starts the next test case. With out the flag, the surefire will just do a db flush to reset the redis back to initial state.
This is necessary in travis environment because flush db seems to take really long time and may cause timeout exception randomly.
I apologies not have included any info in a document.

I was wondering what that did - thanks for clarifying. Removed.

Thank you!


Xamarin Studio templates don't work

Operating System: OS X
Xamarin Studio Version: 5.9.5
MonoGame Addin Version: <IP_ADDRESS>5
CocosSharp Project Templates Version: <IP_ADDRESS>
I am trying to start a CocosSharp project for the first time. I installed the CocosSharp extension in Xamarin Studio, and then attempted to create a new empty CocosSharp solution using the solution template. However, all I get is a "common" project, no Android or iOS projects. When I look on the file system, the folders for Android and iOS are there, but there are no files in them.
If I try to add a new CocosSharp iPad project to an empty solution, when I enter a project name and then hit the Create button, nothing happens. If I hit Create again, I am warned that the project already exists. The Create button is apparently creating the directory on disk, but then failing silently.
Does anyone know what is going on, or how I can figure out what is going on? Was really excited about trying out a new idea with CocosSharp this weekend, but this initial experience has kind of let the air out of my balloon.

Have just tried this as well myself.
Removed the templates, shutdown XS, open XS, Added templates again, create a new blank project and it all seems to be working.  Can you give anymore information here as to what the error could be?
Operating System: OS X
Xamarin Studio Version: 5.9.5
CocosSharp Project Templates Version: <IP_ADDRESS>
Are you trying this with a Starter license maybe?

Yes I am using the Starter license. I'm not sure why CocosSharp would care though.

Hey @eatdrinksleepcode
That would be the reason.  We are in the process of getting MonoGame and thus CocosSharp whitelisted to be used with Starter and Indie.
This will be very soon and is in testing right now with the support just around the corner.
Until then, unfortunately, there is no way to work with CocosSharp.

Well that's disappointing.
What does whitelisting mean? I thought these were just project templates; but you are implying that even if I add CocosSharp to a project myself, I can't use it because of my Xamarin Studio license? That doesn't make any sense to me; it's just a library, right? I thought the only restriction of the Starter license was the size of the compiled application.
On a related note, it would be really nice if I had gotten a message warning me that my license is not supported. I don't know if that needs to be done in Xamarin Studio or in CocosSharp.
(Not directed at you, but Xamarin seems to be following the old Microsoft model of making it really difficult to get started on their platform...)

@eatdrinksleepcode it is based on the size of the application.  MonoGame is a very large code base and it counts as part of the overall application size right now.  Whitelisting mean that MonoGame and thus CocosSharp will not longer be counted as part of that size.

Also, just like I said this is right around the corner.  The pieces are being tested now.  ETA is still not available at this time though.

Thanks for the explanation. It still doesn't really explain why the project templates don't work, and don't give any kind of messaging. I would expect the project to be created, and then the build to fail (with an appropriate error message).

@eatdrinksleepcode Awkward question, but do you have Xamarin.Android and Xamarin.iOS installed? It's possible that the Xamarin Studio template engine to not know what kind of project to create if the target platform modules are not loaded.

@Therzok fair question. According to the Xamarin Studio Add-In Manager, I do in fact have both Xamarin.Android and Xamarin.iOS installed. I actually was having a problem where the manager claimed that I had Xamarin.Mac installed, but I was getting a message saying it wasn't. So I downloaded a new copy of Xamarin Studio Starter Edition and installed it along with all of the platform plugins. So theoretically I should have everything I need (although, if I didn't, I would still expect some kind of messaging to that effect).

@eatdrinksleepcode Can you attach the Xamarin Studio Log files under Help -> Open Log Directory? Specifically the Ide.* logs are what I'm interested in.

@Therzok Interestingly, "Open Log Directory" does nothing. Can you tell me where the logs typically are?

@kjpou1 Where should I be watching for information about when MonoGame and CocosSharp are officially whitelisted?

@eatdrinksleepcode ugh, that is weird.
The logs are usually at ~/Library/Logs/XamarinStudio-5.0

@eatdrinksleepcode Xamarin will have an official announcement.


Add podcast dashboard

Either with simple static Github page
or
Enhancing the podcast generator streamlit app

Use the REST API to interact with artifacts in GitHub Actions
https://docs.github.com/en/rest/actions/artifacts?apiVersion=2022-11-28


amazon/dynamodb-local:2.5.0 fails to start

https://github.com/amazonlinux/container-images/issues/108
Product
Not Specific / Don't Know
What is your question?
I noticed this new version of amazon/dynamodb-local v2.5.0 (18 hours ago).
This version fails to start on Apple Silicone (and other OS apparently) with the following error in the container:
2024-05-29 17:05:23 Initializing DynamoDB Local with the following configuration:
2024-05-29 17:05:23 Port:       8000
2024-05-29 17:05:23 InMemory:   false
2024-05-29 17:05:23 Version:    2.5.0
2024-05-29 17:05:23 DbPath:     ./data
2024-05-29 17:05:23 SharedDb:   true
2024-05-29 17:05:23 shouldDelayTransientStatuses:       false
2024-05-29 17:05:23 CorsParams: null
2024-05-29 17:05:23
2024-05-29 17:05:39 May 29, 2024 7:05:38 AM com.almworks.sqlite4java.Internal log
2024-05-29 17:05:39 WARNING: [sqlite] SQLiteDBAccess$1@21e7144f: job exception
2024-05-29 17:05:39 com.almworks.sqlite4java.SQLiteException: [1] DB[1] prepare() ALTER TABLE dm ADD COLUMN MaxReadRequestUnits INTEGER DEFAULT 0ADD COLUMN MaxWriteRequestUnits INTEGER DEFAULT 0; [unrecognized token: "0ADD"]
2024-05-29 17:05:39     at com.almworks.sqlite4java.SQLiteConnection.throwResult(SQLiteConnection.java:1436)
2024-05-29 17:05:39     at com.almworks.sqlite4java.SQLiteConnection.prepare(SQLiteConnection.java:580)
2024-05-29 17:05:39     at com.almworks.sqlite4java.SQLiteConnection.prepare(SQLiteConnection.java:635)
2024-05-29 17:05:39     at com.almworks.sqlite4java.SQLiteConnection.prepare(SQLiteConnection.java:622)
2024-05-29 17:05:39     at com.amazonaws.services.dynamodbv2.local.shared.access.sqlite.AmazonDynamoDBOfflineSQLiteJob.getPreparedStatement(AmazonDynamoDBOfflineSQLiteJob.java:159)
2024-05-29 17:05:39     at com.amazonaws.services.dynamodbv2.local.shared.access.sqlite.SQLiteDBAccess$1.doWork(SQLiteDBAccess.java:531)
2024-05-29 17:05:39     at com.amazonaws.services.dynamodbv2.local.shared.access.sqlite.SQLiteDBAccess$1.doWork(SQLiteDBAccess.java:406)
2024-05-29 17:05:39     at com.amazonaws.services.dynamodbv2.local.shared.access.sqlite.AmazonDynamoDBOfflineSQLiteJob.job(AmazonDynamoDBOfflineSQLiteJob.java:117)
2024-05-29 17:05:39     at com.almworks.sqlite4java.SQLiteJob.execute(SQLiteJob.java:372)
2024-05-29 17:05:39     at com.almworks.sqlite4java.SQLiteQueue.executeJob(SQLiteQueue.java:534)
2024-05-29 17:05:39     at com.almworks.sqlite4java.SQLiteQueue.queueFunction(SQLiteQueue.java:667)
2024-05-29 17:05:39     at com.almworks.sqlite4java.SQLiteQueue.runQueue(SQLiteQueue.java:623)
2024-05-29 17:05:39     at com.almworks.sqlite4java.SQLiteQueue.access$000(SQLiteQueue.java:77)
2024-05-29 17:05:39     at com.almworks.sqlite4java.SQLiteQueue$1.run(SQLiteQueue.java:205)
2024-05-29 17:05:39     at java.base/java.lang.Thread.run(Thread.java:840)
2024-05-29 17:05:39

version 2.4.0 has no problem, starts without errors:
2024-05-29 17:19:26 Initializing DynamoDB Local with the following configuration:
2024-05-29 17:19:26 Port:       8000
2024-05-29 17:19:26 InMemory:   false
2024-05-29 17:19:26 Version:    2.4.0
2024-05-29 17:19:26 DbPath:     ./data
2024-05-29 17:19:26 SharedDb:   true
2024-05-29 17:19:26 shouldDelayTransientStatuses:       false
2024-05-29 17:19:26 CorsParams: null
2024-05-29 17:19:26

Faced the same issue on linux as well. Changing the version to 2.4.0 resolved the issue.

Thank you for reporting this bug. We are currently trying to replicate this issue on our end and looking for the bug. We will get back to you with our investigation. In the meantime, I assume you are using the DynamoDB Local Docker Image setup and have used the -sharedDboption with a database that was already created on a DbPath from a previous version. @Maxwell2022 @pradeep-maira

yes, sorry this is the docker compose config:
  datastore-dynamodb:
    image: amazon/dynamodb-local:2.5.0
    ports: [8000:8000]
    working_dir: /home/dynamodblocal
    user: root
    command: '-jar DynamoDBLocal.jar -sharedDb -dbPath ./data'
    volumes:
      - dynamodb-volume:/home/dynamodblocal/data

Thank you for reporting this bug. We are currently trying to replicate this issue on our end and looking for the bug. We will get back to you with our investigation. In the meantime, I assume you are using the DynamoDB Local Docker Image setup and have used the -sharedDboption with a database that was already created on a DbPath from a previous version. @Maxwell2022 @pradeep-maira

Thanks @shetsa-amzn!
Deleting the local volume solved the issue for us. So, in your case @Maxwell2022 you should delete your local docker volume (docker/dynamodb) folder.

Yes, this assumption seems correct. It's the pre-existent volume that trigger this error.
I'm guessing it would be fine for most of us to remove the old volume and create a new one.
The following command is working fine for me:
docker run -v ./tmp:/home/dynamodblocal/data -w /home/dynamodblocal amazon/dynamodb-local:2.5.0 -jar DynamoDBLocal.jar -sharedDb -dbPath ./data

I have released the fix in the latest release version 2.5.1 of DynamoDB Local @Maxwell2022 @asitmoharna @pradeep-maira
Sorry for the inconvenience!


Sprint3/filter

Added functionality to filter videos based on upload status and flag. Also switched to Webpack for module bundler.

You the man!


MIME4J-326 Adopt Mime4J 0.8.11-SNAPSHOT

Thought should never use snapshots in production code? That could create issues if something unstable gets merged later in mime4j project no?

I have no idea about that. But in case we want to override the mime4j version just on tmail for example:
mvn clean install -DskipTests -Dmaven.skip.doc=true -Dapache-mime4j.version=0.8.11-SNAPSHOT

Thought should never use snapshots in production code?

Well we are in for a release in MIME4J ^^


webpack build fails on v2.2.2

Hello,
I recently cleaned out my node_modules folder and reinstalled them via npm install.  Prior to the update I had v2.2.0. After the update I was provided v2.2.2.
I'm now unable to build my project which utilizes leaflet v1.0.3.
Here's my dependency block:
"dependencies": {
    "leaflet": "=1.0.3",
    "leaflet-easybutton": "^2.2.0"
}

And the output of npm ls -depth 0 leaflet leaflet-easybutton:
<EMAIL_ADDRESS>/Users/me/Code/myapp
├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
And here are the build errors:
ERROR in [at-loader] ./node_modules/leaflet-easybutton/src/easy-button.d.ts:24:51
    TS2694: Namespace<EMAIL_ADDRESS>has no exported member 'Map'.
ERROR in [at-loader] ./node_modules/leaflet-easybutton/src/easy-button.d.ts:29:20
    TS2304: Cannot find name 'ControlPosition'.
ERROR in [at-loader] ./node_modules/leaflet-easybutton/src/easy-button.d.ts:35:20
    TS2304: Cannot find name 'ControlPosition'.
ERROR in [at-loader] ./node_modules/leaflet-easybutton/src/easy-button.d.ts:45:53
    TS2694: Namespace<EMAIL_ADDRESS>has no exported member 'Map'.
ERROR in [at-loader] ./node_modules/leaflet-easybutton/src/easy-button.d.ts:51:34
    TS2507: Type 'typeof Control' is not a constructor function type.
ERROR in [at-loader] ./node_modules/leaflet-easybutton/src/easy-button.d.ts:55:31
    TS2507: Type 'typeof Control' is not a constructor function type.

If I lock leaflet-easybutton to v2.2.0, everything works fine.
Any thoughts on what would be the issue?

The only change introduced in 2.2.2 is the addition of typescript bindings (the .d.ts file that is mentioned in your errors).
Are you using typescript in your project?

@atstp yep, we are using typescript v2.3.4

Have you tried using leaflet 1.2.0 ?

let me take that back - your type definition file doesn't working with latest leaflet 1.2.0 - works with 1.0.66

@sgentile, are you referring to the EasyButton type definitions?
EasyButton's .d.ts file was contributed by the community (pinging @teyc); I'm not a typescript user myself.  However, I'd like to make sure that it all works smoothly.  It seems like the best workaround right now to pin at 2.2.0, just before the typescript definitions were added — not ideal.
As typescript users, do you guys have any hints as to why these errors are showing up?

@atstp These errors are showing up because Typescript is a strongly typed language, and if it spots incompatible function definitions etc, it will complain ahead of time. Sounds like leaflet typings 1.2.0 has made significant changes to the API. https://github.com/DefinitelyTyped/DefinitelyTyped/commit/b5eaa88e9effe4eebf076951217bdaf3be861721#diff-e215c0498649a65783e8d1347a88e640L1308
This is going to be somewhat painful to resolve. Any suggestions what to do with such big changes?

Thanks teyc.
For now, I'll add a note to the readme. From what you guys have seen, is it correct to say that:

EasyButon's type definitons work with<EMAIL_ADDRESS>and below; for compatibility with the latest leaflet pin leaflet-easybutton to 2.2.0 (for which aren't type definitions)

after that, we can address updating EasyButton's bindings at whatever speed works well for us.  All of my typed js work right now is through bucklescript, but if i get the chance to do some typescript work i'll take the opportunity and update EasyButton.
In the meantime, if anyone from the community can updated the type definitions, I, along with the ret of the community, would appreciate it!

should be fixed with release v2.2.3


Failed to start profiling: Operation not permitted (os error 1)

$ sudo /sbin/setcap 'cap_perfmon+ep' which samply
$ sudo /sbin/sysctl kernel.perf_event_paranoid=-1
kernel.perf_event_paranoid = -1
$ sudo /sbin/sysctl kernel.perf_event_mlock_kb=2048
kernel.perf_event_mlock_kb = 2048
$ samply record --save-only -o prof.json -- ./myapp
Failed to start profiling: Operation not permitted (os error 1)
$ uname -a
Linux idev03 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86_64 GNU/Linux
what is wrong, please?

I think this might be the case that I fixed in https://github.com/mstange/samply/commit/67798e4c44cfd3faa41c1a839c8fc46cf7cc880b:

If the HW_CPU_CYCLES counter doesn't work, we fall back to the
SW_CPU_CLOCK counter. This makes profiling work in more VMs.

Can you check if it's fixed on the main branch? You can clone this repo, run cargo build --release, and then run ./target/release/samply.

it works.  thank you.

I just got the same issue trying to run samply on a GCP VM. It’d be great to have a release, so that the simple instructions actually work :)


Please support gcc-13

Lots of nice changes ...
https://gcc.gnu.org/gcc-13/changes.html

Looks like this project is dead? I also would like support for gcc-13 and clang-16|17 ...

I switched to pkgx, which works for many compilers including gcc-13, clang-16, and clang-17.

GCC 13 is already supported by the master of this repo. There is no need for code change.

When I posted here before, I did because it not work at all with gcc13 nor with clang-16 (I had the logs online but they were obviously lost as it was a long time ago and github doesnt cache them very long).
I can try again but I'm not confident at the moment, and need to find the time. It would help if an actual passing test for gcc13 and clang-16 to 18 were on the ci.

I just tested gcc 13 and it works like a charm on both ubuntu 22.04 and 23.04


Add JSONLD output support

Signed-off-by: Gary O'Neall<EMAIL_ADDRESS>

This was (accidentally) merged already


adding groq model

Addition of Groq model.
Related to issue "Groq model implementation #93"

Hi @gioCarBo, thank you so much for you contribution, the code lgtm, only one thing, can you redirect the merge to the dev/beta branch instead of main, we have recently changed our ci/cd workflow in this way, in the next days we will update also the contributing.md in order to have this clear 😁😁😁

Hii @gioCarBo
We have messed up a little bith this pull request ahhahaha, can you make another one following this steps:

Create a branch from pre/beta
Copy the code you have already developed, included the dependencies in requirement.txt and toml file
commit with: "feat: adding groq base model"
merge into dev/beta

Sorry for the inconvenience 😬😬😬😬

Hi @lurenss
I'm sorry for this. Should I close this PR?

Hei @gioCarBo I added you as co-author in this PR ae2971c. Thank you!


Remove Cake.Graph from Cake.Recipe execution

Having documentation for build script tasks makes only sense for Recipe like NuGet packages, but not for all other projects using Cake.Recipe. To have this disabled by default and explicitely enabled for Cake.Recipe would make more sense therefore.

Initially, we were hoping to only disable Cake.Graph from being enabled by default, however, we ran into a number of problems with getting the build to work when a dependency brought in by Cake.Graph was being used.  In the end, we had to remove Cake.Graph completely, which was done as part of this commit:
https://github.com/cake-contrib/Cake.Recipe/commit/b451ede6d929fe4770b259e53eb757d82e5e07ee
We may look at bringing this back in the future, but for now, it has been removed.


Examples: cleanup

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 1 file pending identification.

Protex Server Path: /home/blackduck/github/ThunderNanoServices/823/rdkcentral/ThunderNanoServices

Commit: cd93495fb9485206ee502e45bb9ea76c0a6a0c80

Report detail: gist

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 1 file pending identification.

Protex Server Path: /home/blackduck/github/ThunderNanoServices/823/rdkcentral/ThunderNanoServices

Commit: cd93495fb9485206ee502e45bb9ea76c0a6a0c80

Report detail: gist

WARNING: A Blackduck scan failure has been waived
A prior failure has been upvoted

Upvote reason: Not a problem

Commit: cd93495fb9485206ee502e45bb9ea76c0a6a0c80


SyntaxError: Invalid state Error in lightningcss-loader

Describe the bug
I am trying to replace postcss, postcss-loaderandautoprefixer` in my webpack application
this is my current config
{
      loader: "css-loader",
      options: {
        importLoaders: isSass ? 2 : 1,
        modules: {
          localIdentName: "[name]__[local]",
          exportOnlyLocals: !isWeb,
        },
      },
    },
    { loader: "postcss-loader" },

This is the new config where I replaced postcss with loghtningcss
{ loader: "lightningcss-loader", options: { implementation: LightningCSS } },

And this is the error I am getting
SyntaxError: Invalid state Error in lightningcss-loader

Reproduction
https://github.com/jainChetan81/lightningcss-error
System Info
System:
    OS: macOS 14.2
    CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
    Memory: 37.68 MB / 8.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.18.2 - ~/.nvm/versions/node/v18.18.2/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.8.1 - ~/.nvm/versions/node/v18.18.2/bin/npm
    pnpm: 8.5.1 - /usr/local/bin/pnpm
    bun: 1.0.22 - ~/.nvm/versions/node/v18.18.2/bin/bun
  Browsers:
    Chrome: 120.0.6099.234
    Safari: 17.2

Used Package Manager
yarn
Validations

[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

Check your src/components/Form/styles.scss file syntax errors, or give me a minimal reproduction that will work

there isn't a syntax error, it works fine with postcss-loader though, I am unable to recreate this without exposing source code


I tried to follow the steps to install Reinvent, but can't create the environment, it shows "ResolvePackageNotFound:"

Collecting package metadata (repodata.json): done
Solving environment: failed
ResolvePackageNotFound:

ld_impl_linux-64=2.33.1
secretstorage=3.2.0
libgcc-ng=9.1.0
gstreamer=1.14.0
libedit=3.1.20181209
libuuid=1.0.3
ncurses=6.2
glib=2.63.1
libstdcxx-ng=9.1.0
libgfortran-ng=7.3.0
gst-plugins-base=1.14.0
readline=8.0
dbus=1.13.12

I followed some suggestion from here, https://github.com/datitran/object_detector_app/issues/41
But, it resulted in "Found conflicts! Looking for incompatible packages."
Thanks for your help.

I am very sorry for the very late reply but I have taken over the project just recently.
Were you able to resolve this issue? What where the steps to install the software?  I would need more details to fix this.


Update template for docs issues

Description
Update template for auto-creating Docs Issues to include:

Link to originating issue (ie the one that's using the user_docs label
Add label dbt-core v1.9 -- this should be updated / incremented at the end/start of the next version

Checklist

[ ] I have read the contributing guide and understand what's expected of me.
[ ] I have run this code in development, and it appears to resolve the stated issue.
[ ] This PR includes tests, or tests are not required or relevant for this PR.
[ ] This PR has no interface changes (e.g., macros, CLI, logs, JSON artifacts, config files, adapter interface, etc.) or this PR has already received feedback and approval from Product or DX.
[ ] This PR includes type annotations for new and modified functions.

hmm, i did sign and submit the CLA. not sure why i'm still getting this error https://github.com/dbt-labs/dbt-core/pull/10731#issuecomment-2357002933

@cla-bot check


Error: Unsupported type: '/injective.types.v1beta1.EthAccount

I encountered an error while trying to sign with the INJ using the Keplr wallet. Could you share how you resolved this?
I have a question to ask. I didn't encounter this error when creating a trading pair between JUNO and OSMO. However, when I tried creating a trading pair between OSMO and Injective, I encountered an error.

import { MsgExecuteContractEncodeObject } from '@cosmjs/cosmwasm-stargate';
import { toUtf8 } from '@cosmjs/encoding';
import { Coin } from '@cosmjs/stargate';
import { MsgExecuteContract } from 'cosmjs-types/cosmwasm/wasm/v1/tx';

type CreateExecuteMessageArgs = {
  senderAddress: string;
  message: any;
  contractAddress: string;
  funds?: Array<Coin>;
};

export const createExecuteMessage = ({
  senderAddress,
  contractAddress,
  message,
  funds,
}: CreateExecuteMessageArgs): MsgExecuteContractEncodeObject => ({
  typeUrl: '/cosmwasm.wasm.v1.MsgExecuteContract',
  value: MsgExecuteContract.fromPartial({
    sender: senderAddress,
    contract: contractAddress,
    msg: toUtf8(JSON.stringify(message)),
    funds: funds || [],
  }),
});

You can't use cosmjs to sign transactions on Injective. Read more here -> https://docs.ts.injective.network/readme/getting-started-cosmjs


Web client intl

I didn't edit the deploy script, so make sure the i18n folder gets deployed and that the cdn handles stuff appropriately.
Make sure my go code is up to snuff, I did a lot of trial and error to try to get it to do what I wanted it to do

Other than those issues, it works, the server injects the messages json object into the html, and the client uses that as the strings for the locale.

I fixed the globbing issue and pulled in @BluePhoenix changes allowing me to test for time formatting. Other than code review, this seems to be good to go @nictuku .


Test that headers are passed to the guzzle client

Should allow #9 to be merged? Let me know if this is insufficient or you'd like it done differently.

Cool will look at it when I get home. Looks good at first glance 👍.  (Completely forgot about #9 😳)


fix: update test ids

:tada: This PR is included in version 1.0.0-beta.10 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


release: build proto metadata plugin from source

The c++ code generated by the plugin #includes some headers from the
protobuf "runtime", which is required to be of the same protobuf version
as the generated code. Previously, we shipped the plugin in binary form,
which required clients to use the same version of protobuf as our
release was compiled at. This version constraint ended up being a
hassle, so we're shipping the plugin in source form instead so it will
be built against the same version of protobuf as the client project.
This unfortunately requires editing the client WORKSPACE file to add the
kythe_release repository and run an included bazel macro for retrieving
dependencies.
local_repository(
    name="kythe_release",
    path="/path/to/kythe/kythe-v0.0.35",
)

load("@kythe_release//:external.bzl", "kythe_release_dependencies")
kythe_release_dependencies()

Can you add a script to our release that adds those lines to a workspace file?

They should only need to run that if they don't already depend on com_google_protobuf (which they will if they're using proto) and absl (I think protobuf should go this dependency as well in the not too distant future). I can remove the glog dependency easily enough (although, again, I think that's being moved to absl in the not too distant future).

I spent some more time on this hoping to find a way around having clients modify their WORKSPACEs in order to run extraction. I'm not really seeing any good solutions here though. I went ahead and removed the glog dependency so it's slightly lighter.
As @shahms points out, client projects only need to modify their WORKSPACE if they don't already have the abseil and protobuf as dependencies. With the gvisor project for example, no changes are needed to the extract command or the WORKSPACE file since they already have those dependencies.
Additionally, extracting bazel projects that don't use protobuf will not require adding these deps.

Looking into this a bit more, I think #4234 is another possible solution

Closing in favor of https://github.com/kythe/kythe/pull/4234.


Fix/end height detection

Identify end height by using received status code instead of whole status.

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


When scrolling back up broken in Demo

When I view the demo (I'm in chrome) scrolling down works fine. But then when I scroll back up the position of the headers shifts to the right and down and gets more messed up with every pass. Is this a bug in your code or maybe a change within one of the dependencies?

Yeah I took a pull request and it had a bug in it.  I still haven't got around to fixing it.  I'll try to get to it tonight.

Okay cool, thanks. I have another 'issue' but it's more something I'm curious about. I"m trying to use this with ng-repeat. I'll create a new ticket.

Is scrolling back up triggering the wrong function?

I just pushed a change to fix it... Hopefully it works for you, it should as long as your are placing your header via relative positioning.


set up collection of / extend utility functions

Using the neo structure can be quite cumbersome in some cases, eg like slicing objects based on an epoch array (#525). To improve on this we could A) extend the methods neo objects offer and B) start an object-independent collection of utility functions in a separate file.
Most likely a combination of both is necessary to achieve best usability of the neo structure.
Here are some suggestions for helpful utility functions:

[ ] create a neo.Epoch based on a  neo.Event object (or maybe two neo.Event objects)
[ ] implement a time_slice function for neo.Segment that also slices child objects accordingly
[ ] slicing a neo.Segment based on a neo.Epoch
[ ] add shift methods for neo Data objects, which move timescale of the object (including t_start and t_stop adjustment, etc)
[ ] support inplace slicing to avoid data duplication and keep original neo structure.

Any thoughts on this? Additional suggestions?

I support a combination of (A) and (B). In general I prefer adding functionality as new methods on the Neo classes, but by making some of this functionality also accessible as utility functions we improve the discoverability (NumPy does this a lot (e.g. arr.min() and np.min(arr)))

For this utils functions/methods, I think it could be good to take proxy object in account.
Here are two possible slicing without/with proxy object.
Having the same function/method that autodetect proxyobject and do the slicing could be good.
No ?
With Standard neo objects
lim0, lim1 = -500*pq.ms, +1500*pq.ms
seg = reader.read_segment(lazy=False)
triggers = seg.events[0]
anasig = seg.analogsignals[0]  # here anasig contain the whole recording in memory
all_sig_chunks = []
for t in triggers.times:
    t0, t1 = (t + lim0), (t + lim1)
    anasig_chunk = anasig.time_slice(t0, t1)
    all_sig_chunks.append(anasig_chunk)
apply_my_fancy_average(all_sig_chunks)

With proxy neo object
lim0, lim1 = -500*pq.ms, +1500*pq.ms
seg = reader.read_segment(lazy=True)
triggers = seg.events[0].load(time_slice=None)  # this load all trigers in memory
anasigproxy = seg.analogsignals[0]  # this is a proxy
all_sig_chunks = []
for t in triggers.times:
    t0, t1 = (t + lim0), (t + lim1)
    anasig_chunk = anasigproxy.load(time_slice=(t0, t1))  # here real data are loaded
    all_sig_chunks.append(anasig_chunk)
apply_my_fancy_average(all_sig_chunks)

@JuliaSprenger what do you think about making a PR to add your
neo_utils.py to Neo as neo/utils.py?


LMS/Spotty/Spotify-Connect usage: Last song stops playing 10 seconds before end

When I select a single song in the Spotify mobile or desktop application and play it with Spotify Connect (the devices icon in the bottom) on my Squeezebox Classic using LMS/Spotty, it always stops playing exactly 10 seconds before the end of the song. This does not happen when there are multiple songs in the queue, except for with the last one. Seems the playback gets stopped before the playback buffer is empty. My LMS/spotty server is an Ubuntu 22.04 LTS machine.
I have been searching for a solution for quite a while, but didn't find anything

Are you saying that the last song in a queue would always end 10s early, no matter how many tracks are queued up? Would the same happen eg. with an album?

I will check that when I'm home. It's easier to reproduce something when it's happening at the start than at the beginning :-)

I just tried it with a very short album (https://open.spotify.com/album/4ZmvKvBVOcsZgT9QDG3Q0G?si=-EYJ34qmR-WHUq-ce9240A) and yes: all songs play in full length except for the last one: the last song stop playing about 10 seconds before the end


Changeset.cast uses String.to_atom

Knowledge of this fact will allow attackers to overflow the atom table fairly quickly (the only mitigation is rate limiting and IP blocking, but in absence of restarts, the attacker will eventually succeed).
Is this a reasonable concern for Ecto developers? If yes, then the most reasonable thing to do would be to prepare a list of accepted fields as strings compile-time and to_atom part of cast should check whether the key belongs to that list. If this is an agreeable solution, I can spend some time preparing a PR.

We only call String.to_atom on the fields that you pass as required and optional fields. That's exactly why we ask the list of fields. Furthermore, those fields must exist in the model before we cast. We could make this clearer in the doc but I think the protection mechanism is already in there.

You are right. My fault, was a quick glance
On Wednesday, January 28, 2015, José Valim<EMAIL_ADDRESS>wrote:

We only call String.to_atom on the fields that you pass as required and
optional fields. That's exactly why we ask the list of fields. Furthermore,
those fields must exist in the model before we cast. We could make this
clearer in the doc but I think the protection mechanism is already in there.
—
Reply to this email directly or view it on GitHub
https://github.com/elixir-lang/ecto/issues/414#issuecomment-71793591.

--
Y.
My company is hiring: https://trustatom.com/jobs


Headers Timeout Error when deploying large contracts

Problem:
The Axelar team is encountering a consistent HeadersTimeoutError when deploying large contracts. This issue occurs across various RPC providers, including QuickNode, ValidationCloud, the public RPC and when using their own relay.
Details:
Despite the timeout error, the contract still deploys successfully.
Example of deployed contract: contract deploy success
Example bytecode: AxelarGateawayData.txt
Impact:
This issue affects the deployment process by causing unnecessary errors, which could mislead developers into thinking the deployment failed when it really succeeded. Resolving this issue would also allow Axelar to not need custom configs for their rpc which would be more in parity with other evms they have integrated.

I have tried reproducing this issue on the local Relay pointing to testnet, as well as on the HashIO relay, using the same bytecode from AxelarGateWayData.txt. However, I was unable to reproduce the timeout issue on either instance.

As shown in the screenshot above, it takes around 25 seconds to complete the deployment job, and no timeout error was thrown. Here is an example of the deployed contract: https://hashscan.io/testnet/transaction/1723656880.276860003.
Is it possible for you to show what the log says when a timeout error is thrown? Additionally, a list of the Relay's configuration settings would be helpful to review as well.

Hi @mgarbs, I might know what's happening if you're using hardhat. When we create a contract deployment, the relay under the hood executes 1xFileCreate + N*FileAppends which takes some time. After the file (with the contract's content) has been created, the relay passes the main signed Ethereum contract deploy transaction to the services for further execution. If we're waiting for the receipt to be populated in the mirror node, the entire process might take up to 30 seconds against testnet for the bytecode you have posted above.
By default, hardhat-ethers set the HeadersTimeoutError to 20 seconds, so if we exceed these seconds, the error is thrown but the request has been already sent for execution and that's why the contract is deployed but the end-user receives an error for timeout.
The flow might be described as follows:

hardhat user sends eth_sendRawTransaction for contract deployment and starts waiting for its receipt - the timeout timer is started here and has 20 seconds to receive the receipt
our relay handles that request and creates 1xFileCreate and N*FileAppends txs - this step can take a while (more than 20 seconds)
hardhat user is waiting for the receipt but the timeframe of 20 seconds is reached and a timeout error is thrown
the relay finally executes all of the transactions and receives the receipt from the mirror node but it's already too late because

:point_up: results in successful contract deployment but in timeout error for the hardhat user.

Here is an example of my hardhat.config.js.
  ...
  defaultNetwork: 'testnet',
  networks: {
    testnet: {
      timeout: 50_000, // ran some tests with different values and > 30 secs is enough for your contract
      url: 'https://testnet.hashio.io/',
      accounts: [
          '0x...'
      ],
      chainId: 296,
      ...
  }
  ...

The core problem is not related to RPC relays and it lies in the hardhat-ethers default timeout which can be overridden easily IMO. Hope that's useful for you and also kinda resolves your issue. Feel free to share all of your concerns.

I faced the same issue when deplying EAS, and using timeout: 50_000 in hardhat configuration solved the issue!

@mgarbs I believe @natanasow 's explanation and solution should resolve this issue.  I am closing it for now.  Please feel free to open it or create a new issue if it does not resolve the problem.

Thanks @ebadiere


Deprecated annotations cause Gradle to fail when using strict options

Hello!
The Gradle compiling task with the option -Werror enabled is failing, because it detectes as deprecated the IdempotentResource and IdempotentRequestPayload
Build Gradle file: https://github.com/apache/fineract/blob/develop/build.gradle
Full error log https://paste.apache.org/xcnvp
It works commenting the -Werror option, but it is not the best way to do it, because the Apache Fineract Community is expecting to keep the code free of deprecated classes/methods
options.compilerArgs += [
"-Xlint:unchecked",
"-Xlint:cast",
"-Xlint:auxiliaryclass",
"-Xlint:deprecation",
"-Xlint:dep-ann",
"-Xlint:divzero",
"-Xlint:empty",
"-Xlint:exports",
"-Xlint:fallthrough",
"-Xlint:finally",
"-Xlint:module",
"-Xlint:opens",
"-Xlint:options",
"-Xlint:overloads",
"-Xlint:overrides",
"-Xlint:path",
"-Xlint:processing",
"-Xlint:removal",
"-Xlint:requires-automatic",
"-Xlint:requires-transitive-automatic",
"-Xlint:try",
"-Xlint:varargs",
"-Xlint:preview",
"-Xlint:static"
//,"-Werror"
]

Hmm, I will be out a new version soon.

i pushed new version but maven central sync a little time consumes. I think you can use it after about 10 hours


Using a wrapper + mutation to "implicitly" update scheduled parameters?

This is to write down a thought which came from #34 and https://github.com/FluxML/Optimisers.jl/pull/89. Presently, we rely on mutably/immutably updating any objects which depend on the schedule value after each step. This is simple and easy to understand, but it could get unwieldy with more complex optimizer state trees.
What if we instead created a stateful type or wrapper which keeps track of the current schedule value? Then, we make this or some type which contains a reference to it subclass a number type (maybe Real? Could make it parametric on the value type). This proxy number can then be manipulated directly by Optimisers.jl rules, but will appear to update automatically whenever the schedule is ticked.
Some pseudocode for the above:
Option 1: wrapper itself is mutable number proxy
mutable struct ScheduleValue{T<:Real} <: Real
  inner::T
end

# Overload basic math operations (much like Flux.Nil)
Base.:+(sv::ScheduleValue, x::Number) = sv.inner + x
....

eta = ScheduleValue(0f0)
d = Descent(eta)
schedule = Exp(...)

for s in schedule
  eta.inner = s  # probably want a proper function for this
  ...
end

Option 2: number proxy is derived from wrapper
struct ScheduleValue{S<:Stateful} <: Real
  iter::S
end

_getval(sv::ScheduleValue) = sv.iter.schedule(sv.iter.state)

# Overload basic math operations (much like Flux.Nil)
Base.:+(sv::ScheduleValue, x::Number) = _getval(sv.inner) + x
...

schedule = Stateful(Exp(...))

eta = ScheduleValue(schedule)
d = Descent(eta)

for _ in schedule  # no need for value here, just next! on the Stateful
  ...
end

Too magic? Perhaps. I could also see serialization being an issue because of the mutable references, but BSON/JLD2 at least should work. However, this does seem more ergonomic than wrapping optimization rules when it comes to scheduling multiple hyperparameters simultaneously.

Sorry, I had a thought here, but I forgot to write it down.
I could see Option 2 being the more attractive one. We could even go one step further and merge the behavior into Stateful instead of wrapping it. I see this as a feature for people who like "magic" and will probably want the self-mutating iterator.
Note that the solution presented in #34 takes a different approach from this and https://github.com/FluxML/Optimisers.jl/pull/89. I see adjust as a very low-level function for the most stripped down version of Optimisers.jl. Appropriate for a package that might have its own opinions about scheduling. In contrast, Scheduler from #34 avoids adjust entirely. The "rule" at each leaf in the tree does not store the underlying optimization rule (e.g. Descent) at all. As such, we don't have stale hyper-parameters that we need to update in the tree. Tree-based functions like update are applied to a tree of Schedulers, and only when we reach a leaf do we construct the underlying optimization rule then call apply! directly (assuming this is cheap to do). This is akin to how OptimiserChain calls apply! directly.
My thought is that both could be offered as options, since they co-exist peacefully, and people have opinions on mutability.

Sounds good. I'll defer to you on which of these options are worthwhile then, since it seems like we have no shortage of choice :)


Fixed error with null values

Fixed error with null values, because of assignObjectToKeys function not checking for null.

Thanks :+1:
Just as a note, next time please don't check in the built files (dist) as this makes it quite hard to see the changes performed


Update golangci-lint and fix lints

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Update the linter and apply new fixes.
Which issue(s) this PR fixes:

None
Does this PR have test?
None

Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

Codecov Report
Attention: Patch coverage is 33.33333% with 48 lines in your changes missing coverage. Please review.

Project coverage is 42.04%. Comparing base (11d77f4) to head (cdbbc6a).
Report is 325 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2339      +/-   ##
==========================================
- Coverage   45.50%   42.04%   -3.46%
==========================================
  Files          79      109      +30
  Lines        7782    15848    +8066
==========================================
+ Hits         3541     6664    +3123
- Misses       4099     8693    +4594
- Partials      142      491     +349


[doc] fix url links in documentation

Purpose

Fix the link url in the documentation.

Tests

API and Format

Documentation

docs/content/concepts/table-types.md
docs/content/engines/doris.md
docs/content/engines/starrocks.md
docs/content/primary-key-table/overview.md

Hi, @JingsongLi ,thanks for your review🙏


Verbosity not respected

I.e., -verbosity 30 is still showing INFO level

Hello!
INFO messages will be shown on INFO verbosity level or greater. If verbosity level is greater than INFO, INFO messages will not be shown. That's normal.

user@hp:~> windscribe-proxy -bind-address <IP_ADDRESS>:80
MAIN    : 2023/03/18 14:49:45 main.go:130: INFO     windscribe-proxy client version v1.3.0 is starting...
MAIN    : 2023/03/18 14:49:45 main.go:257: INFO     Endpoint: ro-014.whiskergalaxy.com:443
MAIN    : 2023/03/18 14:49:45 main.go:258: INFO     Starting proxy server...
MAIN    : 2023/03/18 14:49:45 main.go:260: INFO     Init complete.
MAIN    : 2023/03/18 14:49:45 main.go:262: CRITICAL Server terminated with a reason: listen tcp <IP_ADDRESS>:80: bind: permission denied
MAIN    : 2023/03/18 14:49:45 main.go:263: INFO     Shutting down...
user@hp:~> windscribe-proxy -bind-address <IP_ADDRESS>:80 -verbosity 30
MAIN    : 2023/03/18 14:49:53 main.go:262: CRITICAL Server terminated with a reason: listen tcp <IP_ADDRESS>:80: bind: permission denied

It works as expected. Maybe I'm missing something?

user@hp:~> windscribe-proxy -bind-address <IP_ADDRESS>:80
MAIN    : 2023/03/18 14:49:45 main.go:130: INFO     windscribe-proxy client version v1.3.0 is starting...
MAIN    : 2023/03/18 14:49:45 main.go:257: INFO     Endpoint: ro-014.whiskergalaxy.com:443
MAIN    : 2023/03/18 14:49:45 main.go:258: INFO     Starting proxy server...
MAIN    : 2023/03/18 14:49:45 main.go:260: INFO     Init complete.
MAIN    : 2023/03/18 14:49:45 main.go:262: CRITICAL Server terminated with a reason: listen tcp <IP_ADDRESS>:80: bind: permission denied
MAIN    : 2023/03/18 14:49:45 main.go:263: INFO     Shutting down...
user@hp:~> windscribe-proxy -bind-address <IP_ADDRESS>:80 -verbosity 30
MAIN    : 2023/03/18 14:49:53 main.go:262: CRITICAL Server terminated with a reason: listen tcp <IP_ADDRESS>:80: bind: permission denied

It works as expected. Maybe I'm missing something?

I'm talking about the verbosity param that's supposed to turn down logging, which you didn't even pass. I.e. I don't want all those proxy connection lines, which are INFO level

See the bottom of the output. It shows second launch with verbosity param, leaving only WARN and greater severity level.