Hacker and security Alert!

PLEASE  note 50k coins have been stolen from my encrypted wallet. I would  like to know how this is possible. I will explain my loss in detail so  there is NO confusion.
In 2014, I  acquired dogecoin for around 2 months through various transactions on  ebay and other means. Up until last week, that laptop sat on a shelf  with a dead battery and no internet connection whatsoever.
At  the beginning of this month, I downloaded a new 64 bit wallet, overwrote the wallet.dat file and allowed the wallet to update and  download the blockchain.
As it  finished this morning, I realized that on 5/6/2021, a -50,000  transaction had occurred WITHOUT any knowledge whatsoever on my part. My  old and new wallets show as being fully locked and no passphrases were  EVER given out, printed or ever looked at.
UPDATE: I actually downloaded the new core wallet off of the official website on 5/10/2021 so this happened before I even had a wallet online at all.
Looking  into more detail into this "transaction", it is CLEAR someone STOLE my  coins by tracking down an older transaction and redirecting it into  THEIR wallet. This is the address of the thief:    DGoBxd82tyyhPBbd1qcmAdqJVsWyANnNsQ
By the looks of the wallet's activities, this one account has been doing this for a few weeks now:
https://dogechain.info/address/DGoBxd82tyyhPBbd1qcmAdqJVsWyANnNsQ
How  can something like this happen? I can prove the 50k transaction I  originally made because the addresses are clearly in the blockchain.
Here is the specific transaction of my STOLEN coins: https://dogechain.info/tx/759bb9e9ea8cc7d13053fa5376555150cd899f850d07124853d67d9717349857
The address the coins were taken from is a random RECEIVING address I gave the guy who I bought the coins from.. How is this possible?
 I would love some feedback on this from someone smarter than me.
Should a NEW doge wallet be updated (blockchain) BEFORE copying an old wallet.dat file over? I have so many questions now. Biggest one is - Can I get MY coins back??
PLEASE HELP I'm freaking out here...
..

"I downloaded a new 64 bit wallet" Where did you download it from? There's plenty of scams around.

From https://dogecoin.com/

Where do you keep your seed/recovery words?

Offline in a text file

I would guess what your PC is infected, your seed probably got leaked that way.

My PC is not infected. How did they do a transaction from my wallet to theirs through a address created to receive coins, 7 years ago?

No seeds or codes are on the machine with the wallet on it. Nothing.

From an encrypted locked wallet

Just an update. I double checked to see when I had downloaded the new wallet, which was on 5/10/2021 so I know for sure this was done before I even got a new wallet. This had to have been done on the blockchain directly (no?) before I had anything going on at all so we should be able to rule out this being a wallet issue.

This is where the stolen coins are going and being redirected, almost 2 million coins:
https://dogechain.info/address/DHCcURVnuBpsHVmeU9dqbvxPwwye4G2N4P

Is it just me or do all these transactions look automated? 3,506,922 confirmation??
https://dogechain.info/tx/3df383c41e58f506fb475ae0b0c2822fa678f86ee8401c60fc05f24f2572e2af
All these wallets are connected somehow. I just can't wrap my head around it.

It looks like my coins are still sitting there, is there a way for the development team to return them to me?
https://dogechain.info/tx/759bb9e9ea8cc7d13053fa5376555150cd899f850d07124853d67d9717349857

You kept it in a wallet online lime an exchange wallet? Or is a hardware wallet?

With all due respect, and I'm sorry for your loss - personally, in 2018 I
accidentally formatted over 150k of what I had left from the early days -
walked away for a bit after getting taken for  1.5m in the moolah debacle .

That said - this is not the appropriate forum for such issues.
Transactions are immutable. This is a central tenant of any cryptocurrency.
No one controls the blockchain, it's a public ledger. All that happens here
is how to make those transactions happen more efficiently.
No one has the ability to reverse anything other than the person with
access to the wallet where the coins now reside.
As to the security implications, would need you to provide those specifics

Occam's razor here dictates that, regardless how slim you feel the
chances are, there was security failure on your end that allowed someone to
steal your coins based on the info you have saved locally.

To raise the issue of it being a flaw in dogecoin's code itself you would
need to be able to provide your personal logs that demonstrate a
reproducible attack vector.
In absence of that, sorry for your loss, but nothing can be done, and this
isn't a proper issue.
Even if you could provide the above details & there was a hypothetical flaw
in the code itself - that vulnerability could be found and patched, but the
only person who would be able to return your coins would be the person who
took them.
This is by design.
Again, sorry for your loss, but unless you can identify the attack or
enough logs for someone curious to sus out what occured, it's a dead end,
and again, even if you can provide that... Transactions are immutable.
On Sun, May 16, 2021, 7:07 PM BigBlockDaddy @.***>
wrote:

It looks like my coins are still sitting there, is there a way for the
development team to return them to me?
https://dogechain.info/tx/759bb9e9ea8cc7d13053fa5376555150cd899f850d07124853d67d9717349857
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dogecoin/dogecoin/issues/1958#issuecomment-841890943,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE3WRFL3CX6EC2BZBD66IFLTOBF27ANCNFSM447HCP4A
.

I understand. I would be happy to provide any logs I have. I just need to know how to extract them and where to send them to.

What do you need to send them ?
On Sun, May 16, 2021, 5:13 PM BigBlockDaddy @.***>
wrote:

I understand. I would be happy to provide any logs I have. I just need to
know how to extract them and where to send them to.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dogecoin/dogecoin/issues/1958#issuecomment-841901773,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUDDZXPIUR6AGVUP32QD2KTTOBNTZANCNFSM447HCP4A
.

Sorry, but with everything going on right now with DOGE,Elon, BTC debacle.... Isn't it kind of odd this post comes up now.... And is a recommended news article on my Google feed.... And is assessing a "security for in DOGE's code".... Anyone else kind of sceptical of this?

I'm sorry I'm new to this I really dont know tht much about hacking but I
would love to learn how would that be possible
On Sun, May 16, 2021, 5:22 PM LayManCitizen @.***>
wrote:

Sorry, but with everything going on right now with DOGE,Elon, BTC
debacle.... Isn't it kind of odd this post comes up now.... And is a
recommended news article on my Google feed.... And is assessing a "security
for in DOGE's code".... Anyone else kind of sceptical of this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dogecoin/dogecoin/issues/1958#issuecomment-841903547,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUDDZXNHALY43WPVU3K7N2LTOBOUTANCNFSM447HCP4A
.

Please use the linked reddit & discord resources in the issue template if
you wish to continue to pursue this.
This is not the appropriate forum for the topic.
This is the code repository for dogecoin where developers volunteer their
time & work to work on the codebase.
There is no "dogecoin support" - that's the community - if you believe the
wallet that your coins were transferred to to be exploiting a vulnerability
in the core codebase and/or wish to understand the topics & mechanisms
further - post to the appropriate subreddits or join discord servers, etc,
and ask for help compiling evidence of this from the community. That is the
appropriate place to ask such questions.
The time to create an issue here would be if you can prove an exploit in
the dogecoin core code exists that allows for this & it's not some
circuitous hack based on user or 3rd party wallet security, along with
replication steps for how to trigger such (hypothetical) exploit.
Basically only come here to ask for a fix to an issue in the code kept here
that you've discovered & can describe in detail.
Again, genuinely sorry for your bad luck, but this is not the correct place
to post... and nothing can be done to revert the transaction, even if
fraudulent - it's the nature of the medium.
On Sun, May 16, 2021, 8:13 PM BigBlockDaddy @.***>
wrote:

I understand. I would be happy to provide any logs I have. I just need to
know how to extract them and where to send them to.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dogecoin/dogecoin/issues/1958#issuecomment-841901773,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE3WRFLXJZ6P3S2EXRYZTELTOBNSLANCNFSM447HCP4A
.

I appreciate your points and will pursue this as directed. I need to know what happened here.

Thanks for the understanding & I genuinely wish you well in either figuring
out what mistakes were made or uncovering & outing a scammer & their vector
of attack.  Especially when it's not "welp, I did
something stupid".
You have a much better chance of getting to the bottom of your situation on
the community side of things - if you made a mistake or scam - reddit or
discord will be the best avenue to either find others who say "hey me too &
I recognize that address!" or "here's where you screwed up and how".
Either is an answer - which seems to be most what you're after here. As
much as it sucks, make your peace with the fact that there's a 99.99%
chance you got scammed & it's just gone. Sorry :/
Doge is an open source project & unless someone is paying for devs to
research every support request or there is a demonstrable bug in the code
not much can be done here.
I've lurked/followed this project for years out of interest - the fact that
lately it's becoming the majority of my inbox shows that - need to be
friendly to people who are rightfully upset but wrong place, so even if
it's not code, starting to contribute a bit - the actual maintainers and
contributors must be overwhelmed right now, and rightfully so - it's been a
bit much & we all benefit from the board being orderly & organized.
It would be helpful if you closed out this issue to reduce clutter as it
(from a dev perspective) can't be meaningfully linked to a problem in the
codebase.
The reddit dogecoin community is just as friendly & helpful as it was back
in the days of bobsleds and NASCAR sponsorships - sincerely hope you can
find help & resolution there.
Best wishes & good luck to you.
On Sun, May 16, 2021, 9:41 PM BigBlockDaddy @.***>
wrote:

I appreciate your points and will pursue this as directed. I need to know
what happened here.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dogecoin/dogecoin/issues/1958#issuecomment-841921070,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE3WRFMH3SROHPLSZEENSJDTOBX5ZANCNFSM447HCP4A
.

I realized that Dogecoin is a coin that hackers love becaise they are dogecoin owners and know that no one will help .
I have been a victim too and have been told that  anyone scammed deserves to be scammed . Dogecoin  is not a poor mans coin .

@klawdarza i'm sorry for your losses and it sucks to be a victim
but, as with any other (decentralised) cryptocurrency, you're the one in control
if you are not confident or responsible enough to manage your asset, you should not be managing it
of course, nobody deserves to be scammed, but you should realise, that the scams are being targeted at certain types of individuals and from here on the best you can do is stop being that person
in other words, how can anybody help you other than you?
just my two dogecoins...

Check this reply on reddit: https://www.reddit.com/r/dogecoindev/comments/ndzcuw/hacker_security_alert/gydqgpg?utm_source=share&utm_medium=web2x&context=3
I remember the same scams going around from early 2014.
They were doing this with many cryptos, including Bitcoin.
People must understand that with any crypto YOU are responsible for your fund, nobody can help you retrieve them. If anybody could chime in and retrieve your funds, the blockchain would have no sense whatsoever.

I appreciate the input from everyone, whether or not I agree with certain opinions is besides the point, my coins are gone. Live and learn.

It's a sad experience to lose your money to these wallets...I lost mine to Paxful in Dec 2021. A huge amount was stolen but I was lucky to recover it back after weeks of mails with no positive response from Paxful.  If you have a similar issue, you can reach out: Jimfundsrecovery at consultant dot com.

I was left in shock and depression after being deceived by bitfinex investment where I lost about 395,000 USDT of my entire life savings which I was planning to get a company after my retirement as life investment for my kids but this nitwits stole it from me. However after weeks of my depression I finally met REMOTESPYTECH (at) gmailc0m through a close friend referral and he got back all my stolen assets instantly without hassle or hidden fees. He’s the only real deal out here as I’ve tried many but they failed. He was my final and last hope. I’m grateful Mr Romero delivered. Get in touch with him now!!!!
Email: REMOTESPYTECH (at) GMAILC0M
whatsapp: +1<PHONE_NUMBER>
Remarkable Assistance

^^^ @Jon1325 is a scammer, this is a known fake tactic to steal your money.  reported.

I will brief you how I was able to achieve this .. Acting nervous and suspicious was how I first noticed something was not right so I talked with a friend about it and she did introduced me to a hacker who helped me spy on his phone remotely for proof , I was able to get a remote access to his phone and believe me I really wish I had done this earlier .. but it’s never too late to know the truth .. so if you have a similar feeling about your partner , I will suggest you contact:
Hire a recovery expert today !
EMAIL<EMAIL_ADDRESS>Telegram: +1<PHONE_NUMBER>
WhatsApp/Text: +1<PHONE_NUMBER>


Policies: Request policies

BETTER: Change request parameters
BETTER: The request parameter is optional on CIRCULATION_POLICIES configuration
NEW: Introduce a new parameter CIRCULATION_POLICIES_ALLOW_REQUEST to allow/disallow circulation requests

Co-Authored-by: Aly Badr<EMAIL_ADDRESS>Signed-off-by: Bertrand Zuchuat<EMAIL_ADDRESS>

As general question, if I have to implement the method can_request(loan) with a loan like this:
{
    loan_pid: 1,
    document_pid: 3,
    item_pid: 22544,
}

I guess I would have to validate both document and item right?
I hope it is not confusing for people that don't know what to check exactly in that method...

The check logic must be implemented in the can_be_requested function like the other functions (e. g. get_default_loan_duration or get_default_extension_duration).


n-form validation status reactive

This function solves the problem (这个功能解决的问题)
Validation status of whole form that can be used for disabling submit buttons, etc
Expected API (期望的 API)
Currently n-form-item has a validationErrored reactive field to check if it passed validation or not.
It would be great to have analogical field for whole form.
However, if there is an alternative way to make disabled submit button whole it's not valid, point me please.
Concept example:
    <n-form ref="formRef" :model="model" :rules="rules">
      <n-form-item label="Label A" path="fieldA">
        <n-input v-model:value="model.fieldA" />
      </n-form-item>
      <n-form-item label="Label B" path="fieldB">
        <n-input v-model:value="model.fieldB" />
      </n-form-item>
     <n-button :disabled="formRef.validationErrored">Submit</n-button>
    </n-form>

Currently it would be very complex and you will need to take over form's validation.
I think we should somehow provide a way to achieve it.

You can use something like
// import {computedAsync} from "@vueuse/core"
const isValid = computedAsync(async () => {
  return formRef.value && formRef.value?.validate().then(o => true).catch(e => false)
}, false)

but that will always trigger validate state for you

For posterity's sake, the workaround I found was to use a computed property. I wanted to avoid this, but I really need the button to be triggered only if the form is valid, without having users to click validate each time.
Below is the code in question, and below that is a description of what it does.
Code
const formInvalid = ref(false)
computed(async () => {
  await formRefEMSA?.value?.validate((errors) => {
    if (!errors) {
      formInvalid.value = false
    } else {
      console.log(errors)
      formInvalid.value = true
    }
  })
})

AI Description of the code:

This code uses Vue 3 with the Naive UI framework to create a reactive form validation.
The variable formInvalid is created using the ref function, which creates a reactive reference that can be used in the Vue template to update the state of the application when it changes. Initially, formInvalid is set to false, indicating that the form is valid.
A computed property is then created using the computed function. Computed properties are functions that return a value based on the current state of the application. In this case, the computed property is an asynchronous function that awaits the validation of the form.
The form validation is triggered by calling the validate method on the formRefEMSA object, which should be a reference to the form element. The validate method takes a callback function as its argument, which is called when the validation is complete.
If there are no errors in the form, the errors parameter passed to the callback function will be undefined. In this case, the formInvalid value is set to false using the value property of the reactive reference.
If there are errors in the form, the errors parameter passed to the callback will be an array of error messages. In this case, the errors are logged to the console and the formInvalid value is set to true.
Overall, this code sets up a reactive form validation using Vue 3 and the Naive UI framework, updating the state of the application based on the validity of the form.
Share this explanation with colleagues: whatdoesthiscodedo.com/g/1aa5261

This code uses Vue 3 with the Naive UI framework to create a reactive form validation.
The variable formInvalid is created using the ref function, which creates a reactive reference that can be used in the Vue template to update the state of the application when it changes. Initially, formInvalid is set to false, indicating that the form is valid.
A computed property is then created using the computed function. Computed properties are functions that return a value based on the current state of the application. In this case, the computed property is an asynchronous function that awaits the validation of the form.
The form validation is triggered by calling the validate method on the formRefEMSA object, which should be a reference to the form element. The validate method takes a callback function as its argument, which is called when the validation is complete.
If there are no errors in the form, the errors parameter passed to the callback function will be undefined. In this case, the formInvalid value is set to false using the value property of the reactive reference.
If there are errors in the form, the errors parameter passed to the callback will be an array of error messages. In this case, the errors are logged to the console and the formInvalid value is set to true.
Overall, this code sets up a reactive form validation using Vue 3 and the Naive UI framework, updating the state of the application based on the validity of the form.
Share this explanation with colleagues: whatdoesthiscodedo.com/g/1aa5261

解决了吗
const isValid = computedAsync(async () => {
return formRef.value && formRef.value?.validate().then(o => true).catch(e => false)
}, false)
这个页面不自动更新啊

This issue does not have any recent activity. If you are still experiencing similar problems, open a new error, including a minimal copy of the problem


Removes detection of ruby versions in the Gemfile

after working a bit on the bundle-install CNB, it feel like it would
be better to move this code over there.

also replaces ContainSequence usage with ContainLines

While I agree that removing logic around parsing the Gemfile for a ruby version could be moved around. This buildpack no longer requires any ruby implementation as seen here, and here
This seems odd because bundler requires a ruby implementation in order to run.
Maybe the following pattern is reasonable?
Have this buildpack additionally 'require' the following:
    Name:   "ruby-bin",
        Version: "",
        Metadata: BuildPlanMetadata{
	VersionSource: BuildpackYMLSource,
		Build:         true,
	},
})

Here the ruby-bin is not the name of an actual dependency that another buildpack will provide, but just represent any ruby binary (jruby/mri/rubinius]. Any buildpack providing an actual ruby binary would also provide this ruby-bin dependency.
This way we don't have to care about actually parsing the Gemfile for versioning information about mri and have a way for bundler to express its dependency on a ruby binary

This buildpack does not run bundler though. It just installs it. So, it doesn't really "require" a ruby when you think about it.
The bundle-install buildpack is what actually ends up running bundler. So, this logic moving to that buildpack from here seems like the logical move to me.


Chinese garbled in output -> task

VSCode Version: 1.7.2
OS Version: Win7 zh-cn

Steps to Reproduce:

Run the task I created named "test"
Show below

How to solve this problem?  @dbaeumer

Dups #3550

As a work around you can use the terminal to run a command. This has proper output encoding handling.


Contains and Contains Words seem to have a limit on the length of what they can match

If I have a longish URL (~150 chars) in the title or description of a workitem, I cant find that url by exact matching using contains or contains words.  If I trim my search criteria down to < 100 chars the item starts returning in queries on the devops portal and when using the WIQL api

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

ID: 6859c579-3383-e4b7-366e-69f49a8bd1b6
Version Independent ID: 5b7af784-0698-b77a-342f-252986038e92
Content: Query by title, ID, or rich-text fields - Azure Boards
Content Source: docs/boards/queries/titles-ids-descriptions.md
Product: devops
Technology: devops-agile
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@StingyJack Thank you for the feedback, assigning this to the author for review.

Emailed product team for clarification.

@StingyJack good catch. I believe 100 is the limit. We will work with docs and engineering to get the limits updated in the docs accordingly


build(deps): update to Angular v19

Updates to Angular v19
Configures Renovate to just update Angular v19 minors. Plus keep dependencies compatible with it

#845  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


Authentication

Hello,
It would be nice to allow the configuration / check of an ACCESS_TOKEN or BASIC Authentication to secure the access to the service.
Do you consider to add such option?
Thanks

Hi,
That is out of scope for this project, I would suggest putting an NGINX or Apache in front of the clamav-rest container to handle basic authentication, or a project such as this oauth2-proxy in front of it.
It is not possible for this small project to maintain such a feature inside the project and as stated in the beginning, it's out of scope.

Hi,
That is out of scope for this project, I would suggest putting an NGINX or Apache in front of the clamav-rest container to handle basic authentication, or a project such as this oauth2-proxy in front of it.
It is not possible for this small project to maintain such a feature inside the project and as stated in the beginning, it's out of scope.

Hi,
That is out of scope for this project, I would suggest putting an NGINX or Apache in front of the clamav-rest container to handle basic authentication, or a project such as this oauth2-proxy in front of it.
It is not possible for this small project to maintain such a feature inside the project and as stated in the beginning, it's out of scope.


Fix for missing comment in header

Add a # to verify $CLIInstaller and $CLIArguments are not executed.
Also small fix to indentation.

Thanks!


clightd: 5.3 -> 5.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/FedeDP/Clightd/releases.
meta.description for clightd is: "Linux bus interface that changes screen brightness/temperature"
meta.homepage for clightd is: "https://github.com/FedeDP/Clightd"
meta.changelog for clightd is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/ynk660195jh9g506ngpjfwxd0xav5m1r-clightd-5.4/bin/clightd passed the binary check.

1 of 1 passed binary check by having a zero exit code.

1 of 1 passed binary check by having the new version present in output.

found 5.4 with grep in /nix/store/ynk660195jh9g506ngpjfwxd0xav5m1r-clightd-5.4

found 5.4 in filename of file in /nix/store/ynk660195jh9g506ngpjfwxd0xav5m1r-clightd-5.4

directory tree listing: https://gist.github.com/22c9f76932fca80a9543a1070b9650ef

du listing: https://gist.github.com/adb0dc8244af120dacf8d2b713419a05

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
clight
clightd

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ynk660195jh9g506ngpjfwxd0xav5m1r-clightd-5.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A clightd https://github.com/r-ryantm/nixpkgs/archive/03d49ca09efa04e4f9e84b230146628cbc5074d2.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ynk660195jh9g506ngpjfwxd0xav5m1r-clightd-5.4
ls -la /nix/store/ynk660195jh9g506ngpjfwxd0xav5m1r-clightd-5.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

clight
clightd

Maintainer pings
cc @eadwu for testing.

Result of nixpkgs-review pr 130678 at 03d49ca0 run on x86_64-linux 1

2 packages built successfully:

clight
clightd

2 suggestions:

warning: build-tools-in-build-inputs
util-linux is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/applications/misc/clight/clightd.nix:47:3:
   |
47 |   buildInputs = with lib; [
   |   ^

warning: unclear-gpl
gpl3 is a deprecated license, please check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/applications/misc/clight/clightd.nix:73:5:
   |
73 |     license = licenses.gpl3;
   |     ^


Clarification about robot_obs in custom Gym environments

Hello,
Thanks a lot for sharing this amazing code!
I am looking at the instructions for creating a custom environment here and I noticed that the robot observations are generated as space vectors (for example gripper_pos-torso_pos).
robot_obs = np.concatenate([gripper_pos-torso_pos, gripper_pos-self.target_pos, robot_right_joint_positions, gripper_orient, head_orient, forces]).ravel()

Why are the robot observations created this way and not as a list of joint angle positions and velocities, which seems more intuitive to me? Is it more effective for training perhaps?
Also, why is self.target_pos used in the robot observation? The robot state does not depend on the target position. Should not self.target_pos be used in the computation of the reward only?
This seems to be the case in most Assistive-gym environments so there must be a good reason but I can't find it.
Thanks

Hi there,
Good question! The observation does include the robot's joint angles (for controllable actuators), which is stored in the variable robot_right_joint_positions  in this case above. As for the other elements in the observation, they help the robot infer the state of the world a bit easier. Technically all the robot needs to know about is its joint angles and a target goal, but then that requires the control model (in this case a neural network) to also learn how to do forward kinematics to compute how far the robot's end effector is from some goal. Instead, we just directly compute the forward kinematics to get the robot gripper position/orientation and provide that to the model to make learning a bit easier. For a quick validation of this, you could train simple controllers with and without this information in the observation and check how long it takes for them to learn the task.
self.target_pos is important to give the robot as an observation since that its the target goal for the robot to reach towards. If that information is not given to the robot, then the robot has no idea where it should move towards. Of course the reward will also be based on this target goal, but the robot only gets 'rewards' during training in simulation, not during test time. In practice, it is quite common for robots to know where their target goal is (otherwise they would just be moving around randomly!). For example, if helping someone eat food, the robot should know where the person's mouth is at each time step, which can be provided by off-the-shelf face detection software.
Hope this helps!

Thanks for the clarifications! I actually realised that Mujoco's reacher environment also uses the same forward kinematic trick.
And yes obviously, the robot must know the target position to be able to learn...
Thanks!


dart2js: CPS backend crashes because it doesn't always close over type variables

@asgerf do you want to take this one?
Standalone test case:
class A<T> {
  A() {
    [].forEach((T x) {});
  }
}

main() {
  new A();
  print(true.runtimeType);
}

The use of runtimeType means that the closure class for (T x) {} thinks it should have a field for T, but there is no T in scope in the constructor A().

https://codereview.chromium.org/1286113003/


feat: add stylelint rules for new color tokens

What I did

Testing Instructions

Notes to Reviewers

@bennypowers, will these stylelint rules create any errors or prevent people from using tokens 1.0 names when this PR is merged? I'm asking because Web Test Runner is showing a bunch of errors related to "Unknown rule rhds/no-unknown-token-value".

@bennypowers, I'm still getting errors. I've updated to tokens 2.0.0 using npm i. Running npm run lint was successful, but whenever I try using npx stylelint --fix, terminal gets stuck. Any ideas for how to fix this?

renderCodeDocs.cjs
copyCell tokens helper tries to access $value which isn't available when tokens are pulled from manifest getCssCustomProperties, they return with an object with a default property instead.
    const allCssProperties = this.manifest.getCssCustomProperties(this.packageTagName(kwargs)) ?? [];
   /**
    * returns object with following format
     * {
    * name: '--rh-color-text-primary-on-light',
    * description: 'Primary text color for light theme',
    * syntax: '<color>',
    * default: '#151515'
     * }
    **/

Suggestion to fall back to tokens.default when tokens.$value is undefined/null in getVariableSyntax in tokensHelper.cjs
function getVariableSyntax(token) {
  return `var(--${token.name}, ${escapeDoubleQuotes(token.$value ?? token.default)})`;
}

@zeroedin, would this replace the object with a default property?

that's a fine solution, but let's add a comment that the function takes either a css custom property declaration from a CEM, OR a token object from the token's map


Discussion: Ready for Use

Hey @sidorares and @dougwilson 🙋🏻♂

Current Status
From that point on, any change would be a new idea, so this is where I stop. The aim is to close this issue after the first version has been published on npmjs.

The current state can be seen as a dismemberment of this responsibility.

Discussion
My thought would be to unify the old and new certificates by default, to ensure that current users can continue using the 'Amazon RDS' option without errors for both mysqljs and node-mysql2. Then separate the certificates by period, so new users can use only the certificates they're interested in.
In practice:

The default import would bring in all the certificates (preventing major changes).
We would update the documentation for the new usage based on this dependency.
Next years, when there is a new update from AWS, it will be much easier to include the new certificates.

Topics from https://github.com/mysqljs/aws-ssl-profiles/issues/5#issuecomment-2047523361:

[...] I think the intention was to add later more profiles from other known services.

Apart the dependency name, there is no reason to restrict a certificate set from other instances apart from AWS.

Are the any other AWS services that have different cert bundle?

Initially, probably the AWS GovCloud.

Are there any other popular services that might benefit from a npm packaged cert distribution?

Maybe node-postgres and any Node.js driver for SQL compatible with RDS instances.

An example of how to use this dependency with other SQL drivers for Node.js:
const awsCaBundle = require('aws-ssl-profiles');

const ca = awsCaBundle.ca.join('');

Tests

Each certificate is parsed and checked for signatures.
Ensure that the array is correctly sized according to the number of certificates.

These tests ensure that the certificates aren't corrupted individually or that the array isn't properly populated.

Notes
Although the current certificates are based on the latest MySQL2 update, this dependency intended to work with both mysqljs and node-mysql2.
As a dependency that can be installed directly with mysqljs and node-mysql2, including other drivers, I opted to bring in all the common documents from the open-source community.

@wellwelwel do you want to continue with publishing? I'm not sure what are the optimal steps here, possible option:

you push first version from your local computer with your npm credentials
optionally: add myself and Doug to the list of npm owners
configure release-please secret in this repo with your token

Thank you for your trust 💙
Can I generate an NPM_TOKEN exclusive for this repository and send it to you?

These are the available settings:

Can I generate a NPM_TOKEN exclusive for this repository and send it to you?

I'm not sure, previously I'd use npm to generate the token, and it was scoped per account or package, yo can probably do the same ( token scoped to https://www.npmjs.com/package/aws-ssl-profiles package ) and add it to this repo as NPM_TOKEN secret. Probably no need to share it with me, I prefer release-please to publish changes for me but maybe add me as a co-owner to npm as a backup

@sidorares, sorry, I meant that I don't have the privileges to include secrets 🙋🏻♂
Also, the package is published on npm and I invited you and @dougwilson.

@wellwelwel try again, I think I accidentally made you a maintainer, now you an admin


Replace iris.co_realise_cubes with CubeList.realise_data.

Closes #3012
I have to say though, that I find this much less obvious both in the usage and the naming.
The problem is that wrapping a bunch of cubes in a cubelist "just" in order to co-realise them seems clunky and non-obvious.  It means also that the documentation now appears in a much more obscure place.
The new name also does not sing for me : it does not highlight  what is specifically useful about the operation.
See the example docstring change here : https://github.com/pp-mo/iris/blob/9b24050b92559b467984bd98b57c7aeadcf2f39e/lib/iris/cube.py#L612
I think this will be typical usage, and it is a bit obscure and horrible IMO.
So frankly,  I still preferred it the way it was.
Please think on? @pelson @dkillick

@ajdawson can we import just "iris._lazy_data" here, instead of specific named components ?

From https://github.com/SciTools/iris/pull/3013#discussion_r187965854
New commit attempts to do this...

Following https://github.com/SciTools/iris/pull/3013#discussion_r188306045
Latest looks neater + still addresses earlier concerns.

@pp-mo - suspect this just needs a rebase.

Rebased :crossed_fingers: ...

Thanks @pp-mo!


What is .fnb file in the Fonts folder and how to edit it?

I would like to make a mod that can convert the text to other language, it seems that I should replace these font files in the Fonts folder to support the new language. How can I achieve this?

I'm not familiar with fnb extensions unfortunately. I'm going to close this issue because it's not related to modlunky2 specifically. I'f recommend either leaving a comment on https://spelunky.fyi/mods/m/korean-patch-mod/ asking for information on how they did it or reaching out to the modding community in the #s2-modding channel over at http://discord.gg/spelunky-community


Updates your Jiotv in kodi

Now when I open kodi and play any channel it's saying update your jiotv aap from playstore any solution?

Same issue from morning

Yes, please fix this....no channel is playing....on every channel, a video is showing with jio tv update message

Yes same issue coming for me as well please someone resolve this issue

@iMro0t please look into this issue bro

@iMro0t please look into this bro.... Help us....

Yes . We are also facing the same issue. How to update the jio apk ? Can somebody throw solution?

@iMro0t please fix this

Is this issue now resolved ?

Is this issue now resolved ?

not yet solved...

meanwhile use this https://bdixtv24.tk/pd/ to view all channels of jio tv in hd

NOT RESOLVED

Some channels are working now.

@zeros13213 which channel? No channel is working

@zeros13213 which channel? No channel is working

Some sony liv channels like sony six hd, sony max

https://drive.google.com/drive/folders/1wGMkB5dzQuOm2IbycSjoUa-FAu71QNLE
Use this zip to install (no need to uninstall previous version)

Thanks  .Working now

https://drive.google.com/drive/folders/1wGMkB5dzQuOm2IbycSjoUa-FAu71QNLE
Use this zip to install (no need to uninstall previous version)

Thank you so much


Avalonia app is locked for quite some time so rebuilds are not possible

Describe the bug
Running a MVVM avalonia app from VS2022 seems to block the output files for quite a while even though the app isn't running anymore. When I try to build the application again, it can't override the main executable. If have to wait for some minutes to be able to rebuild the application in VS2022 with NET6. The message says "It is locked by system(4)". I tried to kill all processes which might be related without luck. Sometimes it helps to close all designers but not always.
There is no process in the task manager related to the app. It even happens when I am debugging and stop the debugger from VS. So the app is definitely closed.
To Reproduce
Build and start a MVVM app. Close the app. Change something and build the app again.
Expected behavior
Executable should not be locked if the app isn't running anymore.
Desktop:
Windows 7 64 Bit
VS2022 (17.0.5)
NET6

Does that happen with windows defender and any other AV software disabled?

Unfortunately yes. I can't delete the main executable or rebuild the project even with Windows Defender disabled. No other AV software installed.

Hm it happens with other applications as well so this is most likely some NET6 or VS2022 issue with Win7.


[Test] Introduce SPM test sample app

Manually created XCode sample test app project for swift package manager build test.

Manual xcode project reflects default app/xcode build settings as used by gRPC/iOS clients.
The ios app locally depends on grpc-ios/Package.swift and allows us to easily test local dev modification and in CI.
xcconfig build setting to customize and turn on the following flags

GCC_TREAT_WARNINGS_AS_ERRORS=YES  to treat warning as erros

Also introduce build_test_spm_samples.sh for command line build test via xcodebuild
Build and Verify
run build test script and verify success
./scripts/build_test_spm_samples.sh

May I ask why set GCC_TREAT_WARNINGS_AS_ERRORS = YES in both scripts/build_test_spm_samples.sh and tests/spm/gRPCSample/build.xcconfig?

May I ask why set GCC_TREAT_WARNINGS_AS_ERRORS = YES in both scripts/build_test_spm_samples.sh and tests/spm/gRPCSample/build.xcconfig?

[xcconfig])(https://help.apple.com/xcode/mac/11.4/#/dev745c5c974) can only be applied to project target (all sample app targets) but not to its dependencies (e.g. gRPC-Cpp). For that we need to pass the preprocessor macro via xcodebuild comamnd line and populate it upstream.


Improve spanish translation for what-is-serverless.md

Looks great. Thanks!
Btw just as a tip, this link lets you preview the PR you've made. In case you are making edits and you want to see what it'll look like when it's merged.


Version bump for 2.4

Ruby 2.4.8 tarball doesn't install: https://www.ruby-lang.org/en/news/2019/10/02/ruby-2-4-9-released/

Thanks @jamesdempsey!


[docs] clarify that categorical features will be converted to integers internally

Emphasizes that categorical features will be converted to int internally, to avoid the confusion that they should be provided as integers in the input data, as was asked in #4932. Also adds information on what will happen if negative values are found.
Here's how that section looks like:

Closes #4932.

I think there are more places where this clarification should be made for the consistency in docs. See #1567 for example.

Close and reopen to retrigger ci tests.

@jmoralez I'm very sorry, I just merged #5009 and only after doing that I noticed that these two PRs conflict with each other. Could you please resolve conflicts?

Haha no worries

@jmoralez Thank you for doing this. Could you please rerun this script (https://github.com/microsoft/LightGBM/blob/master/helpers/parameter_generator.py)
so that the changes in config.h can be reflected on the documentation files.
Changes in the documentation files should also be updated to this branch to pass the static checks.

Thanks @shiyu1994. I didin't know I had to change the config.h file. Done in 349f797.


Heroku - invalid byte sequence in US-ASCII

Hello
I'm trying to use simple_form with Twitter Bootstrap. I copied the Gemfile from this project
https://github.com/rafaelfranca/simple_form-bootstrap

After I added the simple_form gem, I'm getting this error
/usr/ruby1.9.2/lib/ruby/1.9.1/rubygems/specification.rb:519:in `normalize_yaml_input': invalid byte sequence in US-ASCII (ArgumentError)

matilde-2:bbtaxi(master>) pablo$ git push heroku master
Counting objects: 1245, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (1201/1201), done.
Writing objects: 100% (1245/1245), 2.24 MiB | 595 KiB/s, done.
Total 1245 (delta 576), reused 0 (delta 0)
-----> Heroku receiving push
-----> Ruby/Rails app detected
-----> Detected Rails is not set to serve static_assets
Installing rails3_serve_static_assets... done
-----> Configure Rails 3 to disable x-sendfile
Installing rails3_disable_x_sendfile... done
-----> Configure Rails to log to stdout
Installing rails_log_stdout... done
-----> Gemfile detected, running Bundler version 1.0.7
Unresolved dependencies detected; Installing...
Using --without development:test
Fetching source index for http://rubygems.org/
Fetching git://github.com/plataformatec/simple_form.git
Installing rake (<IP_ADDRESS>)
Installing abstract (1.0.0)
Installing activesupport (3.0.7)
Installing builder (2.1.2)
Installing i18n (0.5.0)
Installing activemodel (3.0.7)
Installing erubis (2.6.6)
Installing rack (1.2.4)
Installing rack-mount (0.6.14)
Installing rack-test (0.5.7)
Installing tzinfo (0.3.31)
Installing actionpack (3.0.7)
Installing mime-types (1.17.2)
Installing polyglot (0.3.3)
Installing treetop (1.4.10)
Installing mail (2.2.19)
Installing actionmailer (3.0.7)
Installing arel (2.0.10)
Installing activerecord (3.0.7)
Installing activeresource (3.0.7)
Installing bcrypt-ruby (3.0.1) with native extensions
Installing orm_adapter (0.0.5)
Installing warden (1.0.6)
Installing devise (1.4.9)
Installing thor (0.14.6)
Installing railties (3.0.7)
/usr/ruby1.9.2/lib/ruby/1.9.1/rubygems/specification.rb:519:in normalize_yaml_input': invalid byte sequence in US-ASCII (ArgumentError)  from /usr/ruby1.9.2/lib/ruby/1.9.1/rubygems/specification.rb:479:in from_yaml'
from /usr/ruby1.9.2/lib/ruby/1.9.1/rubygems/package/tar_input.rb:183:in load_gemspec'  from /usr/ruby1.9.2/lib/ruby/1.9.1/rubygems/package/tar_input.rb:51:in block in initialize'
from /usr/ruby1.9.2/lib/ruby/1.9.1/rubygems/package/tar_reader.rb:64:in block in each'  from /usr/ruby1.9.2/lib/ruby/1.9.1/rubygems/package/tar_reader.rb:55:in loop'
from /usr/ruby1.9.2/lib/ruby/1.9.1/rubygems/package/tar_reader.rb:55:in each'  from /usr/ruby1.9.2/lib/ruby/1.9.1/rubygems/package/tar_input.rb:32:in initialize'
from /usr/ruby1.9.2/lib/ruby/1.9.1/rubygems/package/tar_input.rb:17:in new'  from /usr/ruby1.9.2/lib/ruby/1.9.1/rubygems/package/tar_input.rb:17:in open'
from /usr/ruby1.9.2/lib/ruby/1.9.1/rubygems/package.rb:58:in open'  from /usr/ruby1.9.2/lib/ruby/1.9.1/rubygems/format.rb:63:in from_io'
from /usr/ruby1.9.2/lib/ruby/1.9.1/rubygems/format.rb:51:in block in from_file_by_path'  from /usr/ruby1.9.2/lib/ruby/1.9.1/open-uri.rb:35:in open'
from /usr/ruby1.9.2/lib/ruby/1.9.1/open-uri.rb:35:in open'  from /usr/ruby1.9.2/lib/ruby/1.9.1/rubygems/format.rb:50:in from_file_by_path'
from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/source.rb:72:in fetch'  from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/installer.rb:45:in block in run'
from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/spec_set.rb:12:in block in each'  from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/spec_set.rb:12:in each'
from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/spec_set.rb:12:in each'  from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/installer.rb:44:in run'
from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/installer.rb:8:in install'  from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/cli.rb:225:in install'
from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/vendor/thor/task.rb:22:in run'  from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/vendor/thor/invocation.rb:118:in invoke_task'
from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/vendor/thor.rb:246:in dispatch'  from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/vendor/thor/base.rb:389:in start'
from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/bin/bundle:13:in <top (required)>'  from /usr/ruby1.9.2/bin/bundle:19:in load'
from /usr/ruby1.9.2/bin/bundle:19:in `'
FAILED: http://devcenter.heroku.com/articles/bundler
! Heroku push rejected, failed to install gems via Bundler
To git@heroku.com:bbtaxi.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'git@heroku.com:bbtaxi.git'

I tried to add these lines
LANG="en_US.UTF-8"
LC_ALL="en_US.UTF-8"
(Following this post http://www.a.rnaud.net/2011/10/how-to-fix-invalid-byte-sequence-in-us-ascii-in-bundler-installation/)
But I'm still getting the same error. I can't deploy my application. :'(
I created a ticket on Heroku, they answered me

Hi Pablo,
The source of this error is a character encoding bug in the version of rubygems on this stack. It happens when there are unicode characters in the gemspec, as there are in simple_form:
https://github.com/plataformatec/simple_form/blob/master/simple_form.gemspec
Unfortunately, we may not be able to upgrade rubygems on this stack any time soon, because there are complications that might break a lot of apps. The only current workaround for this would be to fork the gem, remove the unicode characters from the gemspec, and then install from your fork. I'm sorry for the complication here. If you have any questions about doing this, I'd be happy to answer them.
Thanks,
Matt

Is there another workaround instead of remove the accents in gemspec?
Cheers,
Pablo Cantero

Wich heroku stack are you using? We are using heroku to serve this application without any problems as you can see here: http://simple-form-bootstrap.heroku.com/

It worked only when I migrated my stack to bamboo-ree-1.8.7. But I would like to use bamboo-mri-1.9.2. Is it possible?
Which stack are you using?

I'm using the Cedar stack http://devcenter.heroku.com/articles/cedar

Unfortunately I cant migrate to Cedar, Heroku doesn't allow it. Just from bamboo to bamboo and the simple_form isn't working with bamboo 1.9.2 just because the accents in the gemspec.
Is it a bad thing to the change
from:
s.authors     = ['José Valim', 'Carlos Antônio']
to:
s.authors     = ['Jose Valim', 'Carlos Antonio']
To make it compatibility with Heroku default stack (1.9.2)?

I don't want to change the gemspec because a limitation of one platform.
As you are using the master branch so I recommend that you make a fork, change the gemspec and point your GEMFILE to your SimpleForm Fork.

rafaelfranca,
I'm having the same problem in application and my system is running on rackspace. Is there any chance to have the main repo working instead of using a fork? (phstc: nothing personal but I don't know if your repo will be updated in the future so I prefer to stick to the main repo).
Cheers,

@jonas11235 I think that change it in the official repo is the best option.

maybe @ped or @fabiokung can offer some opinions on this on behalf of Heroku ;)

This is a RubyGems issue as you can see here, and here, and the solution of this issue is described here.
I don't think that is a good idea change our gemspec because a bug with rubygems.
Unfortunately we can't do anything about it, only recommend you to update the rubygems version.

Please remove the UTF-8 characters from your gemspec. For backwards compatibility with Rubygems, you need to limit your gemspec to US-ASCII characters. Otherwise, you're basically saying you have to use Rubygems >= 1.8.5 to use this gem.
Heroku uses Rubygems 1.3.7 which is why this doesn't work on Heroku.

@wuputah
[slytrade@slytrade01 ~]$ gem -v
1.8.11

And I have the same problem :(
As a temporary solution I using the fixed git repo.

The gemspec with accents is more important than make the gem compatible with environments? Everybody knows that it is a problem on Rubygems, but why not remove the accents in the gemspec to make it more compatible?

@jonas11235: interesting, I wasn't exactly sure when the patch made it in, but on second review I think it was supposed to be fixed in 1.8.10. Not sure why it's not working for you in 1.8.11...

I tried to reproduce this error at Heroku without success the simple_form was installed correctly.
[ree github]$ heroku apps:create simple-form-2
Creating simple-form-2... done, stack is bamboo-mri-1.9.2
http://simple-form-2.heroku.com/ | git@heroku.com:simple-form-2.git
[ree github]$ cd simple_form-bootstrap/
/Users/rafaelmfranca/Projects/github/simple_form-bootstrap
[ree simple_form-bootstrap (master)]$ git remote add heroku-2 git@heroku.com:simple-form-2.git
[ree simple_form-bootstrap (master)]$ gp heroku-2
Counting objects: 352, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (319/319), done.
Writing objects: 100% (352/352), 58.02 KiB, done.
Total 352 (delta 155), reused 0 (delta 0)

-----> Heroku receiving push
-----> Ruby/Rails app detected
-----> Configure Rails 3 to disable x-sendfile
       Installing rails3_disable_x_sendfile... done
-----> Configure Rails to log to stdout
       Installing rails_log_stdout... done
-----> Gemfile detected, running Bundler version 1.0.7
       Unresolved dependencies detected; Installing...
       Using --without development:test
       Fetching source index for http://rubygems.org/
       Fetching git://github.com/plataformatec/simple_form.git
       Installing rake (0.9.2)
       Installing multi_json (1.0.3)
       Installing activesupport (3.1.0)
       Installing bcrypt-ruby (3.0.0) with native extensions
       Installing builder (3.0.0)
       Installing i18n (0.6.0)
       Installing activemodel (3.1.0)
       Installing erubis (2.7.0)
       Installing rack (1.3.2)
       Installing rack-cache (1.0.3)
       Installing rack-mount (0.8.3)
       Installing rack-test (0.6.1)
       Installing hike (1.2.1)
       Installing tilt (1.3.3)
       Installing sprockets (2.0.0)
       Installing actionpack (3.1.0)
       Installing mime-types (1.16)
       Installing polyglot (0.3.2)
       Installing treetop (1.4.10)
       Installing mail (2.3.0)
       Installing actionmailer (3.1.0)
       Installing arel (2.2.1)
       Installing tzinfo (0.3.29)
       Installing activerecord (3.1.0)
       Installing activeresource (3.1.0)
       Installing coffee-script-source (1.1.2)
       Installing execjs (1.2.4)
       Installing coffee-script (2.2.0)
       Installing rack-ssl (1.3.2)
       Installing rdoc (3.9.4)
       Installing thor (0.14.6)
       Installing railties (3.1.0)
       Installing coffee-rails (3.1.0)
       Installing jquery-rails (1.0.14)
       Installing json (1.5.4) with native extensions
       Installing pg (0.11.0) with native extensions
       Using bundler (1.0.7)
       Installing rails (3.1.0)
       Installing sass (3.1.7)
       Installing sass-rails (3.1.0)
       Using simple_form (2.0.0.dev) from git://github.com/plataformatec/simple_form.git (at master)
       Installing uglifier (1.0.3)
       Your bundle is complete! It was installed into ./.bundle/gems/
-----> Compiled slug size is 7.1MB
-----> Launching... done, v4
       http://simple-form-2.heroku.com deployed to Heroku

To git@heroku.com:simple-form-2.git
 * [new branch]      HEAD -> master

Put in your Gemfile
  gem 'simple_form', :git => 'git://github.com/plataformatec/simple_form.git'

(the same configuration that you used in https://github.com/rafaelfranca/simple_form-bootstrap/blob/master/Gemfile)
And then bundle update.
After this change, try to push it again on Heroku.

As you can in my last comment I'm using the simple_form-bootstrap application, and I'm using the last version of SimpleForm, and bamboo-mri-1.9.2 stack.
I ran the bundle update only for sanity check and tried to push again to Heroku and everything went smoothly.

Interesting... I will try to investigate more, but I still don't have any evidence that this issue is with the simple_form gemspec. This gem, like Devise, always had UTF-8 characters in the gemspec and this is the first time that someone reported this kind of issue.
I'll appreciate if you guys can help us to reproduce it and if the error was confirmed we'll change the gemspec.

Devise is broken too, but in a similar not-all-the-time way.
I don't know why this sometimes happens and sometimes not. @hone may be able to contribute here.

I have same problem, when using
gem update --system 1.8.10 this problem is solved but the bundle give me a following,
NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01.
Gem.source_index called from /usr/local/rvm/gems/ruby-1.9.2-p290@global/gems/bundler-1.0.10/lib/bundler/shared_helpers.rb:3.
NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01.
Gem.source_index called from /usr/local/rvm/gems/ruby-1.9.2-p290@global/gems/bundler-1.0.10/lib/bundler/source.rb:162.
NOTE: Gem::SourceIndex#each is deprecated with no replacement. It will be removed on or after 2011-11-01.
Gem::SourceIndex#each called from /usr/local/rvm/gems/ruby-1.9.2-p290@global/gems/bundler-1.0.10/lib/bundler/source.rb:162.
NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01.
Gem.source_index called from /usr/local/rvm/gems/ruby-1.9.2-p290@global/gems/bundler-1.0.10/lib/bundler/source.rb:162.
NOTE: Gem::SourceIndex#each is deprecated with no replacement. It will be removed on or after 2011-11-01.
Gem::SourceIndex#each called from /usr/local/rvm/gems/ruby-1.9.2-p290@global/gems/bundler-1.0.10/lib/bundler/source.rb:162.
What is wrong?

This is only warnings that should be fixed with latest version of bundler

Maybe this solution resolve the problem for simple_form too: http://stackoverflow.com/questions/8252160/invalid-byte-sequence-error-in-normalize-yaml-input-being-thrown

shingonodie, "invalid byte sequence error" disappear in 1.8.10 but warning messages apper. Himm.. rafaelfranca  We will wait for latest bunler..

Here the same - this one helped me:
http://stackoverflow.com/questions/8252160/invalid-byte-sequence-error-in-normalize-yaml-input-being-thrown


Register NEOK as an IBC coin

[x] Draft proposal and submit it to the EVMOS Commonwealth forum https://commonwealth.im/evmos/discussion/11132-proposal-to-register-neok-token-an-ibc-token
[x] Submit the proposal and hope it gets accepted https://app.evmos.org/governance?id=144
[x] Update cosmostation registry for the ERC-20 token https://github.com/cosmostation/chainlist/pull/538
[x] Update cosmostation registry for the IBC coin https://github.com/cosmostation/chainlist/pull/541
[ ] Add NEOK to the EVMOS Token Registry https://github.com/evmos/chain-token-registry/pull/52
[ ] Ask Keplr why our coin doesn't show up https://github.com/chainapsis/keplr-wallet/issues/724
[ ] Ask Cosmostation why our coin doesn't show up https://github.com/cosmostation/cosmostation-chrome-extension/issues/182

Related issues:

https://github.com/evmos/apps/issues/247

Other docs:

https://academy.evmos.org/articles/advanced/automated-coin-conversion/

https://commonwealth.im/evmos/discussion/11132-proposal-to-register-neok-token-an-ibc-token

Hey @vrde feel free to open a PR on the Evmos academy repo if you want to share your experience about this. We could add a new article or improve the existing one. Would be very useful for other developers

Hey @vrde feel free to open a PR on the Evmos academy repo if you want to share your experience about this. We could add a new article or improve the existing one. Would be very useful for other developers

Sure thing, I'll work on it after we close the loop with Keplr or Cosmostation :)

@GAtom22 to keep you posted, we will work on the article once we have our token in a dex.

The integration of NEOK inside keplr mostly depend on their support for the EVMOS ERC20 tokens. We will close this issue and follow up with the EVMOS team.


[bug] Schedule action pre-submit tests fail due to missing badges

Schedule actions in this repo re-use the report success script from example-package. They fail because of the new badge logic in the script: https://github.com/slsa-framework/slsa-github-generator/actions/runs/5195861218/jobs/9368998750
cc @ianlewis

And in slsa-verifier: https://github.com/slsa-framework/slsa-verifier/actions/runs/5195266465/jobs/9367891708

I reverted this and made it so they are only updated in the example-package repo. These workflows should run successfully now.

detect-workflow-js: https://github.com/slsa-framework/slsa-github-generator/actions/runs/5206121066
slsa-verifier: I can't trigger it via workflow_dispatch because of a bug in the workflow. Fix: https://github.com/slsa-framework/slsa-verifier/pull/637. It should be ok the next time it is scheduled to run though.

The slsa-verifier test is also passing now: https://github.com/slsa-framework/slsa-verifier/actions/runs/5206658289


Terra Crashes when Workflow with Redacted Snapshot Present

A user posted that when they try to open a workspace in Terra that contains a redacted snapshot, the entire website/app crashes entirely with an error message they were unable to capture by screenshot since it was crashing. They did manage to get the below screenshot of what they see before the crash. I tried to find a workspace with a redacted snapshot already present but couldn't locate one and I tried to test by importing a redacted snapshot but since that isn't possible, I am not positive this is a bug or not but this is what the user seemed to notice about this workspace as anomalous.

@breilly2 do you think this is related to https://github.com/DataBiosphere/saturn-ui/issues/1212?

Somewhat similar concept but probably different. Snapshots (and their ability to be redacted) is on methods whereas #1212 is about method configurations. Both can be thought of as versioning of the artifact. These two issues are related to two different artifacts.

Seeing something redacted should not break the app. Can we reproduce this?

I can try and make some snapshots, import to a workspace, redact, and see if this happens.

Users now will see a warning with a tooltip explanation on redacted methods from the tools page. They won't be able to click into this redacted method.
If a user were to navigate to the tool via a direct link, they will receive a message notifying them that the method has been redacted with an OK button to navigate back to the tools list.


Hide Editor Transform Gizmo when View Gizmos is off

The transform gizmo is a gizmo too. There are scenarios where users want to be able to hide it, because it is distracting.
https://github.com/godotengine/godot/assets/105675984/50001706-1d13-471d-8d84-a32625271da6

Unsure if it should be hidden in the same toggle used by other gizmos, as it is arguably the most important gizmo, but it makes sense in theory.

I don't see why not. All the other Gizmos have their own toggle. I see that option as literal "I don't want to see ANY gizmos button."

I'd say this is a different kind of gizmo, hence why it isn't in that list (unless I'm mistaken)

You're correct. It's not on the list, but neither is the selection box "gizmo?" and that is considered part of the "Show Gizmos" functionality.  I suppose it all depends on the actual intended purpose of of the button.

I think it's a backwards compatibility change to use the same toggle. One way is to have a different toggle for it and rename the old one.

I think the toggle is to hide these specific ones, rather than the generic ones

If I'm understanding you correctly then hiding the selection box gizmo is a bug?

Mt bad didn't know it was hidden, I'm not sure about that one, but I'd rather say that's a bug and not this part

I think it's a backwards compatibility change to use the same toggle. One way is to have a different toggle for it and rename the old one.

Fair enough, I can look into doing that. I'll just need to understand if this is combined with the selection box, or should the selection box never hide, or if it's a separate thing all together?
I personally do think there is a utility to allowing users to hide everything.

Should be a separate setting as stated above, in that case, it breaks compatibility IMO

I was talking about the selection box. Although I suppose that's a separate issue all together. I can just leave it alone for now, and just have a separate option for hiding the transform gizmo.

Meant for the hiding of this, I'd say to combine both sides of it

Meant for the hiding of this, I'd say to combine both sides of it

I'll just open an issue for this and make a separate PR in the future, if that's fine.

Ok, I made a separate option to toggle the transform gizmo.

It's obviously not part of this PR, but will this option be eventually exposed to GdScript via EditorInterface?

I don't see why it should be. The best one could do without bloating EditorInterface is turn it into a action/shortcut, so that it can be at least triggered by other means.

I don't see why it should be. The best one could do without bloating EditorInterface is turn it into a action/shortcut, so that it can be at least triggered by other means.

That's a fair assessment. I could open a proposal if necessary, but in short: when an EditorPlugin implements some sort of edit mode that relies on a node selection, it's AFAICT not possible to hide the editor's built-in gizmos, though you can turn off the default input behaviour (it's been a while since I've worked on something like this, admittedly).

No I understand, I personally experienced the same issue. Still, that sounds like it could be something extra to custom Node3DGizmos. Something like a _is_transform_gizmo_visible overridable method, so that it doesn't interfere with the setting but can still be customized.
Outside the scope of this PR, though. Could use a proposal indeed.

Thanks!

Why is my proposal listed in this PR? It has nothing to do with my proposal. My proposal was specifically about not having gizmo just in the select mode, which is meant for selecting, and not transforming. Having a toggle for transform gizmo that is shared by all modes and nested deep in some menu has absolutely, I mean absolutely nothing to do with the proposal I made.

I wrote related, but not closes/implements (which is why your proposal is still open) because your proposal at the time was the only one at the time that had some relevancy to give credence to this PR. I agree it doesn't solve the issue, but it at least allows you to manually hide the transform gizmo while select mode is activated. My understanding is you want an option for this to happen automatically and completely disable transforming functionality. The code written for this PR could serve as a good reference point of how to implement that.

I wrote related, but not closes/implements (which is why your proposal is still open) because your proposal at the time was the only one that had some relevancy to give credence to this PR. I agree it doesn't solve the issue, but it at least allows you to manually hide the transform gizmo while select mode is activated. My understanding is you want an option for this to happen automatically and completely disable transforming functionality. The code written for this PR could serve as a good reference point of how to implement that.

Ok, you're right. I was just worried my proposal is gonna get closed because this PR was merged. If it's going to stay open then it's fine. I will try to make a PR myself soon. It should hopefully be easy.

I was just worried my proposal is gonna get closed because this PR was merged.

No worries, I link these things for myself as well in case I personally want to implement a related PR. I gave your proposal a thumb up, I just haven't run into the issue enough times to dedicate the time to it.

It's still a bit messy.

I agree. Not to add to whole relevancy thing, but I did create a proposal to move most the stuff in the view menu to the perspective menu and have all "gizmos" including the transform manipulator as you call it, be toggled there: https://github.com/godotengine/godot-proposals/issues/11363


Add metrics to BackupManager for backup and restore of the journal

Adding metrics for backup and restore from backup to track number of entries and time taken for backup.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/5961/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/5964/
Test FAILed.

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/5970/
Test PASSed.

alluxio-bot, merge this please.

alluxio-bot, cherry-pick this to branch-1.8 please


Switch from pycryptodomex to cryptography.io

cryptography.io wraps an existing well-known cryptography library (OpenSSL) instead of implementing routines itself, and it's already a dependency of Twisted, so this reduces the overall number of cryptography libraries needed.

I've done a little bit of unit testing by hand but let me try to make some real connections with this too, since I don't think there's much test coverage for this code. Also I'm open to feedback on whether this is a desirable thing at all.

OK, I've confirmed that this works in both of the cases that are affected, i.e., password auth (with Xtightvnc) and Apple Remote Desktop (with macOS 13.6), so I think I got the code right :)


Can not reach to the API service

I've been experiencing issues when trying to reach the API endpoint at api.coingecko.com while running the project. It appears that there might be a server-side issue.
Please review this issue.
Thank you!

Hey @rezazarchi , Thanks for your feedback! 🙌🏻
Would you like to work on issue?

According to status.coingecko.com the server is up now. It might be a temporary issue. Now is up and I can now work on my own issue 😇

Excellent! 🙌🏻


Support for define global constants from vite.config

Clear and concise description of the problem
In our webapp we are using vite's define for global constants. Unfortunately our tests using these constants are failing because the variables are not defined. Seems like vitest is ignoring everything included in the define context of the vite.config.js.
Do you plan to support that or did i miss something and its already working?
Suggested solution
Parse 'define' part of the vite.config and provide items as constants.
Alternative
Not use define in vite.config
Additional context
if there is anything i can do to support this awesome project please let me know. I'm happy to contribute
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Could you please provide a reproduce demo ? I tried it and everything was fine.
https://stackblitz.com/edit/vitest-dev-vitest-b31hwg?file=vite.config.ts

Seems like the issue occurs only when using the constant within a vue component:
https://stackblitz.com/edit/vitejs-vite-w5twrd?file=src/components/HelloWorld.test.ts

Seems like the issue occurs only when using the constant within a vue component: https://stackblitz.com/edit/vitejs-vite-w5twrd?file=src/components/HelloWorld.test.ts

I'm trying to solve this problem.
If you're desperate for a solution, try this
https://stackblitz.com/edit/vitejs-vite-y6gi6x?file=src%2Fcomponents%2FHelloWorld.vue


deps: integrate<EMAIL_ADDRESS>

This PR integrates latest FEEL linter changes and restores the 1.1.0 Behavior of overriding the supplied error message. The Detailes message will be shown in the editor:

related to https://github.com/camunda/camunda-modeler/issues/3991

In the error panel, the errors are grouped by Activity. When you have multiple Errors in the same Task, it should be clear that multiple properties are affected.

This is in line with all other Error messages. If we want to change the error message in the Properties panel, this should be done in the @camunda/linting repository. https://github.com/camunda/linting/blob/68c0d021de459f00a78ea9480ab3e8feec2acbc0/lib/utils/properties-panel.js#L317-L319

Let's follow up with the updates there then. Thanks for clarifying.

Follow-up here: https://github.com/camunda/linting/pull/97


Can not validate p tag is closed certainly.

Hi, @JonathanMagnan
Here is an issue with me that cased when I use HAP:
HAP 1.8.4
request.CustomCode = "
root div 1
child div
 1-1

root div 2
";
var htmlDoc = new HtmlDocument();
htmlDoc.LoadHtml(request.CustomCode);
HtmlDocument.DisableBehavaiorTagP = true;
var htmlNodes = htmlDoc.DocumentNode.Descendants().Where(s => s.NodeType == HtmlNodeType.Element);
foreach (var node in htmlNodes)
{
    if (!node.Closed)
    {
        // do something
        break;
    }
}

Look at the if (!node.Closed) block, when node is "p", expected that is Closed == false, but true. The p tag does not closed explicitly in the original html partial.
When I print the node.InnerHtml, the value is root div 1
child div
 1-1
.
So, that makes me confused.
THANKS

Hello @Aldin-Xia ,
Thank you for reporting, we will look at it as soon as we can (We are currently at the end of a big development)
Best Regards,
Jonathan

Performance Libraries
context.BulkInsert(list, options => options.BatchSize = 1000);
Entity Framework Extensions • Bulk Operations •  Dapper Plus •  LinqToSql Plus
Runtime Evaluation
Eval.Execute("x + y", new {x = 1, y = 2}); // return 3
C# Eval Function • SQL Eval Function

Thank you for replying  to me  during your busy schedule. @JonathanMagnan
I'll trying to solve it with other method. If I have any effective way, I will be happy share it.
Best Regards


IOU – Expense Report title field is missing in IOU for Gmail account

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.72-0
Reproducible in staging?: Y
Reproducible in production?: Y
**If this was caught during regression testing, add the test name, ID and link from TestRail:**https://expensify.testrail.io/index.php?/tests/view/4549008
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause - Internal Team
Action Performed:

Go to https://staging.new.expensify.com/
Log is with Gmail account
Open Workspace chat
Create 2 IOUs
Open IOU from the chat
Verify that there is no Expense Report title field

Expected Result:
Expense Report title field is present in IOU for Gmail account
Actual Result:
Expense Report title field is missing in IOU for Gmail account
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/3317c2b8-5008-4756-9951-cc9d7769aa2f

View all open jobs on GitHub

@jliexpensify  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #vip-vsp

Hmmm I feel like I should tag in @Expensify/design to review this one: I don't ever recall seeing a Report title like the ones in the above proposal. But Design should also weigh in on how/where we show it, if we want to show it.

Pretty sure this is 1) behind a beta still 2) only going to be made available on control workspaces. @caitlinwhite1 can hipcheck me on that, but I think this is expected that a rando Gmail account on a collect workspace doesn't see report fields.

Potentially, but I'll defer to @thienlnam & @caitlinwhite1 on the rollout consideration of that project. At some point we're going to move everyone using report fields on Collect to Control with @kevinksullivan's project.

behind a beta still  - Correct, the beta has not yet been removed
only going to be made available on control workspaces - Correct, so we're currently on HOLD until we upgrade Collect users to Control this summer. At this point, we also plan to prevent Collect users from adding report fields in OldDot. Then we can remove the beta.

@trjExpensify

Okay, so I don't think this issue is a bug then. @thienlnam can perhaps confirm if we're going to do this elsewhere before we close it out:

update the util function to only show those field when we have a control policy

Yeah this isn't a bug, let's update this test rail https://expensify.testrail.io/index.php?/tests/view/4549008 to indicate that it should only happen for control workspaces

Awesome, thanks everyone. Closing this out!


Error when loading bundle file

>>> bundle=unitypack.load(f)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/jack980517/python-modules/UnityPack/unitypack/__init__.py", line 11, in load
    return env.load(file)
  File "/home/jack980517/python-modules/UnityPack/unitypack/environment.py", line 21, in load
    ret.load(file)
  File "/home/jack980517/python-modules/UnityPack/unitypack/assetbundle.py", line 36, in load
    self.signature = buf.read_string()
  File "/home/jack980517/python-modules/UnityPack/unitypack/utils.py", line 70, in read_string
    ret = self.read_cstring()
  File "/home/jack980517/python-modules/UnityPack/unitypack/utils.py", line 83, in read_cstring
    c = self.read(1)
  File "/home/jack980517/python-modules/UnityPack/unitypack/utils.py", line 60, in read
    return self.buf.read(*args)
  File "/usr/lib64/python3.5/codecs.py", line 321, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x9d in position 37: invalid start byte

Solved: instead of open("example.unity3d") as written in the readme, open("example.unity3d",'rb') is required. Not specifying rb would result in the file being read as text rather than binary, and would have some weird issues like this one.


usage with conversations

This plugin use bot.api.config.use for configuration. Is it safe to use hydrateFiles(token) within conversation.run?

Closed in favor of https://github.com/grammyjs/conversations/issues/87


Bot buys coins, even though orderLimitMaxOpenTrades is exceeded

Today I ran into the situation where all open grid trades for my 3 traded coins fired their last grid trade. "Max. Open Trades" is set to 3 here. Shortly after, the bot tried to purchase three additional coins, that met the buy criteria.
Is this behaviour intentional? One can easily run into the situation, where you run out of coins on a big drop while the bot keeps buying new coins.
I now set my last grid trade to a ridiculously low percentage of 0.01 that will never be reached in order to (hopefully) overcome this issue.
Is there some other measure to prevent above described situation?
Thank you in advance.

I faced the same situation again this morning. Last night I had 3 open trades with "Max. Open Trades" set to 4 and
"Max. Buy Open Orders" set to 2.
This morning I suddenly had 6 open trades. If I had set "Max. Buy Open Orders" to 3 I could come up with a logical explanation why I ended up at 6. But with above setup I could only have gotten to 5.
When the bot creates a buy-order for a coin not yet in the wallet, does this count into "Max. Open Trades" already?
If not, then the bot would always be able to buy more coins than "Max. Open Trades" permits, when "Max. Buy Open Orders" is above 1.
Curiously, when one of the 6 coins dropped low enough, so the bot would trigger the next grid, it complained that the maximum number of open trades had been reached.
The behaviour seem odd, and I cannot quite fathom the cause of it. Could my installation be messed up?
Could there by an consistency in the mongodb?
How exactly is the bot to behave in a situation with "Max. Open Trades" at 4, "Max. Open Trades" at 2 and already 3 open trades?

@chrisleekr
I think the code does not handle what I think it should. If I understood this correctly then the code does not check whether or not "currently open trades" + "currently open orders" will exceed "max open trades".
I hope this is the right place to look at...
I found the function  isExceedingMaxOpenTrades() that seem to check whether or not it is allowed to buy more coins.
I don't comprehend why you deduct 1 from currentOpenTrades but I'd say the code should look similar to this:
  // get this value for currentBuyOpenOrders from logger passed to the function
  const currentBuyOpenOrders = await getNumberOfBuyOpenOrders(logger);

  // do this when the coin is already in your wallet
  if (lastBuyPrice) {
    currentOpenTrades -= 1;
  }
  // do this if you are about to buy a new coin, but don't want to exceed orderLimitMaxOpenTrades after coin is purchased
  else {
    if (currentBuyOpenOrders + currentOpenTrades >= orderLimitMaxOpenTrades) {
      return false;
    }
  }

PS: This is my first attempt doing anything in node.js.

My above code doesn't seem quite right.
I think this is closer to the truth:
  // If the last buy price is recorded, this is one of open trades.
  if (lastBuyPrice) {
    return false;
  }
  // If the last buy price is not recorded, this is a new trade.
  // Do not place additional open orders if the resulting number
  // of trades would exceed max open trades.
  else {
    const currentBuyOpenOrders = await getNumberOfBuyOpenOrders(logger);
    if (currentBuyOpenOrders + currentOpenTrades >= orderLimitMaxOpenTrades) {
      return true;
    }
  }

  return false;
};

This would be the corresponding diff against current head:
diff --git a/app/cronjob/trailingTrade/step/determine-action.js b/app/cronjob/trailingTrade/step/determine-action.js
index 2be1ca5..2454fe1 100644
--- a/app/cronjob/trailingTrade/step/determine-action.js
+++ b/app/cronjob/trailingTrade/step/determine-action.js
@@ -149,13 +149,17 @@ const isExceedingMaxOpenTrades = async (logger, data) => {
   let currentOpenTrades = await getNumberOfOpenTrades(logger);

   // If the last buy price is recorded, this is one of open trades.
-  // Deduct 1 from the current open trades and calculate it.
   if (lastBuyPrice) {
-    currentOpenTrades -= 1;
+    return false;
   }
-
-  if (currentOpenTrades >= orderLimitMaxOpenTrades) {
-    return true;
+  // If the last buy price is not recorded, this is a new trade.
+  // Do not place additional open orders if the resulting number
+  // of trades would exceed max open trades.
+  else {
+    const currentBuyOpenOrders = await getNumberOfBuyOpenOrders(logger);
+    if (currentBuyOpenOrders + currentOpenTrades >= orderLimitMaxOpenTrades) {
+      return true;
+    }
   }

   return false;

Comments are greatly appreciated.

I found a case where above code did not do what it should. So here is a new version:
  // If the last buy price is recorded, this is one of open trades.
  if (lastBuyPrice) {
    // Usually it should always be allowed to buy more coins once the bot initially purchased them
    // and there are grid trades left.
    // If you lower your orderLimitMaxOpenTrades or if you manually add a buy price to a coin you already own,
    // we must still check whether or not we have reached orderLimitMaxOpenTrades.
    if (currentOpenTrades >= orderLimitMaxOpenTrades) {
      return true;
    }
  }
  // If the last buy price is not recorded, this is a new trade.
  // Do not place additional open orders if the resulting number
  // of trades would exceed max open trades.
  else {
    const currentBuyOpenOrders = await getNumberOfBuyOpenOrders(logger);
    if (currentBuyOpenOrders + currentOpenTrades >= orderLimitMaxOpenTrades) {
      return true;
    }
  }
  // In all other cases return false
  return false;
};

This is the diff again:
diff --git a/app/cronjob/trailingTrade/step/determine-action.js b/app/cronjob/trailingTrade/step/determine-action.js
index 598110a..f54e50d 100644
--- a/app/cronjob/trailingTrade/step/determine-action.js
+++ b/app/cronjob/trailingTrade/step/determine-action.js
@@ -149,9 +149,14 @@ const isExceedingMaxOpenTrades = async (logger, data) => {
   let currentOpenTrades = await getNumberOfOpenTrades(logger);

   // If the last buy price is recorded, this is one of open trades.
-  // Deduct 1 from the current open trades and calculate it.
   if (lastBuyPrice) {
-    return false;
+    // Usually it should always be allowed to buy more coins once the bot initially purchased them
+    // and there are grid trades left.
+    // If you lower your orderLimitMaxOpenTrades or if you manually add a buy price to a coin you already own,
+    // we must still check whether or not we have reached orderLimitMaxOpenTrades.
+    if (currentOpenTrades >= orderLimitMaxOpenTrades) {
+      return true;
+    }
   }
   // If the last buy price is not recorded, this is a new trade.
   // Do not place additional open orders if the resulting number
@@ -162,7 +167,7 @@ const isExceedingMaxOpenTrades = async (logger, data) => {
       return true;
     }
   }
-
+  // In all other cases return false
   return false;
 };

This condition will prevent the bot from opening number of trades greater than orderLimitMaxOpenTrades,
    if (currentBuyOpenOrders + currentOpenTrades > orderLimitMaxOpenTrades) {
      return true;
    }

but it will not completely solve the problem.
If you currentOpenTrades  < orderLimitMaxOpenTrades but currentBuyOpenOrders > orderLimitMaxOpenTrades - currentOpenTrades  then you won't be able to by a new coin even though orderLimitMaxOpenTrades is not reached.
For this to work correctly, we must be able to lower orderLimitMaxBuyOpenOrders to orderLimitMaxOpenTrades - currentOpenTrades .
I think this should done in isExceedingMaxOpenTrades.
I'll see if I can come up with an idea.

Could this already do the trick:
const isExceedingMaxBuyOpenOrders = async (logger, data) => {
  const {
    symbolConfiguration: {
      botOptions: {
        orderLimit: {
          enabled: orderLimitEnabled,
          maxBuyOpenOrders: orderLimitMaxBuyOpenOrders
          maxOpenTrades: orderLimitMaxOpenTrades
        }
      }
    }
  } = data;

  if (orderLimitEnabled === false) {
    return false;
  }

  const currentBuyOpenOrders = await getNumberOfBuyOpenOrders(logger);
  const currentOpenTrades = await getNumberOfOpenTrades(logger);

  if (currentBuyOpenOrders >= orderLimitMaxBuyOpenOrders) {
    return true;
  }
  if (currentBuyOpenOrders > orderLimitMaxOpenTrades - currentOpenTrades){
    return true;
  }

  return false;
};

?
diff --git a/app/cronjob/trailingTrade/step/determine-action.js b/app/cronjob/trailingTrade/step/determine-action.js
index 598110a..54a2d60 100644
--- a/app/cronjob/trailingTrade/step/determine-action.js
+++ b/app/cronjob/trailingTrade/step/determine-action.js
@@ -104,6 +104,7 @@ const isExceedingMaxBuyOpenOrders = async (logger, data) => {
         orderLimit: {
           enabled: orderLimitEnabled,
           maxBuyOpenOrders: orderLimitMaxBuyOpenOrders
+          maxOpenTrades: orderLimitMaxOpenTrades
         }
       }
     }
@@ -114,10 +115,14 @@ const isExceedingMaxBuyOpenOrders = async (logger, data) => {
   }

   const currentBuyOpenOrders = await getNumberOfBuyOpenOrders(logger);
+  const currentOpenTrades = await getNumberOfOpenTrades(logger);

   if (currentBuyOpenOrders >= orderLimitMaxBuyOpenOrders) {
     return true;
   }
+  if (currentBuyOpenOrders > orderLimitMaxOpenTrades - currentOpenTrades){
+    return true;
+  }

   return false;
 };

I think this could work.
I'm not sure how to use NOT correctly with lastBuyPrice. So this may not do what I expect.
Any help is very much appreciated.
const isExceedingMaxBuyOpenOrders = async (logger, data) => {
  const {
    symbolConfiguration: {
      botOptions: {
        orderLimit: {
          enabled: orderLimitEnabled,
          maxBuyOpenOrders: orderLimitMaxBuyOpenOrders,
          maxOpenTrades: orderLimitMaxOpenTrades
        }
      }
    },
    sell: { lastBuyPrice }
  } = data;

  if (orderLimitEnabled === false) {
    return false;
  }

  const currentBuyOpenOrders = await getNumberOfBuyOpenOrders(logger);
  const currentOpenTrades = await getNumberOfOpenTrades(logger);

  if (currentBuyOpenOrders < orderLimitMaxBuyOpenOrders) {
    if (!lastBuyPrice) {
      if (currentBuyOpenOrders > orderLimitMaxOpenTrades - currentOpenTrades) {
        return true;
      }
    }
  else {
     return true;
  }

  return false;
};

I have put everything into a separate branch for testing: https://github.com/Rayn0r/binance-trading-bot/commits/max_open_trades_fix
Let me know what you think.

Thank you @Rayn0r
I have the same issue
Will find time to try it and let u know

I have pushed another little fix, but I don't think all is yet working the way it should.
If two coins drop simultaneously, then there is still a probability that both are bought. I have not been able to figure out why.
I believe that someone with more in-depth knowledge of how node-js works and this here code is required.
With my current code the occasion on when it bought more coins than it was allowed has decreased, but it still happens from time to time.

I think the better idea will be to keep opening orders without change but as soon as max. open trades is reached when buy order is executed then all other buy orders at Grid Trade #1 have to be cancelled immediatelly. I'll create PR for this.


auctex: 11.89 -> 11.90

See http://lists.gnu.org/archive/html/info-gnu/2017-01/msg00003.html
for release announcement
Motivation for this change
Things done

[X] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] Linux

[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

@lsix, are you using the auctex tex package ? I would be glad to know if it works for other guys.

@layus actually no (I am a vim user). I have propagated here the release announcement I received, checked it builds properly but I do not use it.

I am asking this because some time ago I turned this package into a tex package. The preview package provided by auctex is used by qtikz (ktikz on Kde). I would like to know if there are more ktikz users around here :-). Anyway, thanks for the update.


Pivot Chart Range

Hi,
Was using excel2img for saving pivot charts in excel to image .png format. My doubt is my pivot table and pivot charts both are on the same sheets. When I execute below statement:
ex.export_img('foo.xlsm', 'customer.png', 'customer_pivot', None)
An image is generated with only pivot table. Pivot chart is not saved as image. So kindly help we with this as I want to know how I can loop over above code to save different charts in my xlsx file.
Thanks in advance.
Regards,
Husain. S.

Just an edit...I have used import excel2img as ex


Add paginated commit display to the CLI interface

Looks good to me! CI test is failing but it's a test issue so not a problem here.


Add support for custom attributes rather than [inject]

I have a scenario where I am trying to decouple Zenject wherever possible behind abstractions (as consumers of my lib can use other DI frameworks if they wish, I just provide Zenject as the default).
I have managed to separate out most stuff but the [inject] attribute is one that I cannot work around and ideally need a way to tell zenject to inject into MBs without them knowing about Zenject.
So to this end it would be great if I could tell zenject to use other attributes too, i.e:
// Somewhere
DiContainer.RegisterCustomInjectAttribute<MyInjectAttribute>();

// in some MonoBehaviour
[MyInjectAttribute]
public ISomethingToGetInjected something;

This would make it easier for people to decouple Zenject further if needed in their projects while still retaining all the features that Zenject offers.

Fixed on lts branch.  Usage:  TypeAnalyzer.AddCustomInjectAttribute(typeof(InjectCustomAttribute))

My hero!


analysis.getNavigation will return non-empty results for whitespace locations

This was caught by a (yet-to-be-committed) integration test. Will update once that lands.

https://github.com/dart-lang/sdk/blob/master/pkg/analysis_server/test/integration/analysis/get_navigation_test.dart#L44

I removed the @failingTest annotation on the test here as it was fixed along with a related issue I found while testing LSP (invoking Go-to-Def on a comment would navigate to a definition for a reference elsewhere in the same comment).


OneOf validation issue

What version of Ajv are you using? Does the issue happen if you use the latest version?
ajv: "8.12.0"
Ajv options object
  const ajv = new Ajv({
    allErrors: true,
    multipleOfPrecision: 1,
  });

JSON Schema
const eventSchema = {
  type: 'object',
  properties: {
    oneProperty: {
      oneOf: [
        {
          type: 'object',
          properties: {
            absolute: {
              type: 'number',
              minimum: 1,
              maximum: 16,
              multipleOf: 1,
            },
          },
        },
        {
          type: 'object',
          properties: {
            relative: {
              type: 'number',
              minimum: -8,
              maximum: 8,
              multipleOf: 1,
            },
          },
        },
      ],
    },
  },
  required: ['oneProperty'],
};

Sample data
{
    "oneProperty": {
        "absolute": "-1"
    }
}

Your code
const validateRequestParams = (
  requestParams,
  eventSchema
) => {
  const ajv = new Ajv({
    allErrors: true,
    multipleOfPrecision: 1,
  });
  const validate = ajv.compile(eventSchema);
  const valid = validate(requestParams ?? {});
  if (!valid) {
    return false;
  }
  return true;
};

Validation result, data AFTER validation, error messages
true
What results did you expect?
false

The problem is that the second schema you have defined does not prevent additionalProperties, nor does it "require" a property of relative. Therefore it passes as true for the second schema in the oneOf. If you want this to fail either make additionalProperties false or add required.
These are common mistakes when working with JSON Schema.


Move generation of code_max_resolved to early position in the pipeline - needed in 02-artis-pipeline.R

https://github.com/Seafood-Globalization-Lab/artis-model/blob/c209c1c572a97202fd86f0b51975e8f68b23a0c7/04-create-metadata.R#L491

Move entire 04-create-metadata.R script to position 2 in pipeline. Possible to contain script into function to create attribute tables.


Browserproblem? Maybe Caching when setting up visibility of actions

Hello Team, we have experienced following problem:
To follow the problem we do following steps:
1: PageExtension with one Action that we want to make "Visible" on a certain condition of a tablerecord (Setuptable)

PageAction with a Visible Parameter

Code in OnOpenPage for setting the global bool var.
`   trigger OnOpenPage()
begin
  if EngSetup.Get() then
      ShowKumPrice := EngSetup."Accumulated pricing";

end;
`

If you first start the Application, all seems correct, with the correct visibility. But if you change the field in the Setuptable and go back on this page, the old Visibility is taken. Although the code in "OnOpenPage" is running correct with correct setting of the global var.
If you "Reload" the Page (in Edge STRG-R) the Action has the correct state.
So it must be a Cacheproblem somehow.

Hi! Please take a minute to read the guidelines for this repository https://github.com/microsoft/AL and our collection of frequently asked questions https://github.com/Microsoft/AL/wiki/frequently-Asked-Questions .
As this repository is only for issues related to the AL compiler in latest developer preview environment for Dynamics 365 Business Central. We suggest that you open a support case or file a bug in Collaborate, to ensure that all Business Central users benefit from your catch as soon as possible.
To open a support case, you can:

Open a support request to CSS through the PartnerSource portal
Contact your Service Account Manager (SAM) in your local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also direct you "step by step" how to open a support request or how to get credentials, if this is the first time for you or your company

If you file the bug in Collaborate, remember to include steps to reproduce the issue, and the Business Central build number and country version you're using.


crypto not found

npm WARN deprecated<EMAIL_ADDRESS>This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.
Is it correct? Can you just use inbuilt crypto? @19h @JBaczuk JBaczuk @Kagami @ea2973929 @englercj @JBaczuk

Since you're working in a react-native context you might be able to just patch out or straight up remove any use of the nodeCrypto declarations.
That said, I definitely urge you to look into more recent and audited projects if you actually intend to use cryptographic primitives in your application.

related https://github.com/bitchan/eccrypto/issues/45