[Suggestion] Logs channel option

I feel like this would bring a solid improvement to the (already great) mod.

Hello! Can you elaborate further on what logs channel option means?

Hi! My idea is to have a channel which receives the logs from the Minecraft server console, i.e. "Saving the game!" or "Is the server overloaded?" or when a command is run from the console

Ok, I'll look into how to implement this feature. Thanks!

Thank you!

Is this exactly what you have in mind?

Yes!

Any suggestion?

Is this the only suggestion? I'll look into it tomorrow.

That's the only thing I can think of. Thank you!

Ok, thanks a lot for your quick reply!

The feature has been implemented in the latest build version, but I have no plans to release a version in a short time.
(My desktop motherboard is under repair, and my laptop configuration is not enough to test the mod)
You can find the latest build JAR files at GitHub Actions and use those first.
Also, you can find the latest MCDC docs on my blog:
https://blog.xujiayao.top/posts/4ba0a17a/#Setup-MCDiscordChat

Ok. Thank you so much!

I installed this mod today and I actually came here specifically to request that this feature be turned off   xD   Perhaps it can be toggled true|false in the mcdiscordchat.json config file? I want discord members to see player chat, but I do not want them to see server console messages as this feature enables. The reason is so people don't know when admins/moderators/server ops are executing commands and what commands they're using. I clipped a screenshot as an example of server console messages I would like to be able to hide. or the ability to send them to a different channel.

@jdstankosky The feature you're talking about already exists, please read the docs.

Can you explain the correct settings?
Scenario 1:
channelId set
consoleLogChannelId empty
broadcastCommandExecution false
this results that join/leave messages etc, are sent, but player chats in game are not sent to channelId. no avatars
Scenario 2:
channelId set
consoleLogChannelId set
broadcastCommandExecution false
this results that player chats in game and server console (including commands) are sent to consoleLogChannelId, but no chats are send to channelId. also, no avatars.
Scenario 3:
channelId set
consoleLogChannelId set
broadcastCommandExecution true
this results that player chats in game and server console (including commands) are sent to consoleLogChannelId, but no chats are send to channelId. However, the typed / commands are sent to channelId with the player's avata

r

The operation of all scenarios is the same.
The server was not stopped at the time of the screenshot, so no [20:19:15] [INFO]: Stopping the server on Discord.

Scenario 1

channelId = 1234
consoleLogChannelId = 5678
broadcastCommandExecution = true

in-game-chat
console-log

Scenario 2

channelId = 1234
consoleLogChannelId = 5678
broadcastCommandExecution = false

in-game-chat
console-log

Scenario 3

channelId = 1234
consoleLogChannelId is empty, i.e. "consoleLogChannelId": ""
broadcastCommandExecution = true

in-game-chat
console-log

Nothing here

The test results of my scenarios are all as expected.

@jdstankosky If the problem still exists, please submit a new issue.


fix: js lang: parens/brackets and the default keyword

default keyword was red
some brackets, curly braces and commas was white (which are not "operator"), should be cyan
didn't recognize objects

(damn, will update the pics in a sec)
example for last bullet
sublime (notice brackets, commas and result.code)

before

after

There is one more thing that can't be fixed because the engine ;/
      return bundle.write(utils.extend({
        foo: 'bar',
        aaa: {
          bbb: 'c'
        }
      }, options, target))

props can be blue...

Last commit fixes

options.target.map() - target prop should be blue
result.map.toUrl() - map should be green because it is in template string

@silvestreh ping?

@tunnckoCore Pong!

Great! Thanks! :)


Wrong block size

OS
Your OS:
Versions
The db-sync version: <IP_ADDRESS>
PostgreSQL version: 15.3
Build/Install Method
inputoutput/cardano-db-sync:<IP_ADDRESS>-docker
Run method
Docker
Additional context
Snapshot: 13.1/db-sync-snapshot-schema-13.1-block-8883740-x86_64.tgz
  cardano-db-sync:
    image: inputoutput/cardano-db-sync:<IP_ADDRESS>-docker
    environment:
      - NETWORK=${NETWORK:-mainnet}
      - POSTGRES_HOST=postgres
      - POSTGRES_PORT=5432
      - RESTORE_SNAPSHOT=${RESTORE_SNAPSHOT:-https://update-cardano-mainnet.iohk.io/cardano-db-sync/13.1/db-sync-snapshot-schema-13.1-block-8883740-x86_64.tgz}
      - RESTORE_RECREATE_DB=N
      - EXTRA_DB_SYNC_ARGS=--consumed-tx-out

Problem Report
All blocks after 8883740 (last of loaded snapshot) contain a wrong block size. Don't know if its because incompatible PSQL version or db-sync issue.


Move some assets to pool prices (#1029)

Some assets weren't displaying proper fiat prices. Moved to utilize pool prices. Should solve ( #1029)
Assets in question:

[x] JKL
[x] stOSMO
[x] stJUNO
[x] stSTARS
[x] IST
[x] LUMEN
[x] GKEY
[x] GLTO
[x] MEME
[x] LVN

Unique problem:

GEO coingecko price was causing the Liquidity in the 787 pool to reflect 18k when in reality it is around 12k.
Updated to utilize pool as reference point.

@JeremyParish69 please review

You can remove the comment markers on prices.ts, as I've uncommented it all: https://github.com/osmosis-labs/osmosis-frontend/pull/1032

FYI seen some user complaints that pool detail page shows half prices; excluding the assets above from total calcs


Rename NSO data -> admin_level_data

This was meant to be done a while ago (as noted here ) but we didn't get around to it yet. Simply speaking, NSO stands for national statistical office. The type of data we are referring to could come from multiple sources. The definition of this data is that it describes a measurement at the administrative level.

@JorgeMartinezG - assigning this and a few other NSO layer issues to you to begin reviewing


Hooks

@bilal-fazlani here's a spike of implementing pre & post-hooks functionality for design review.  I think this would solve #55 for the most part.  All hook params have to be IArgumentModel.  I'm not familiar enough with the internal mapping code to support more than that.

Thanks @drewburlingame for all the effort you are making on this library. I will take a look at these during the weekend

I need to reread the docs.  I didn't digest what Inherited did the first time through.  I'll be using that a lot more.  And it makes the pre & post hook seem mostly unnecessary.  The reason a pre hook may still be useful is to prevent throwing exceptions in the ctor.  But, as long as the library returns the real exception instead of the TypeInitializationException, I don't think there's a need for these hooks at all.

This is my fault. I dont think I have done a good job documenting 'Inherited' enough and with examples. I will do that.

I think there's just a lot to take in.  Examples would be helpful.  Now that you have ctor & dispose, it would be helpful to call out that pattern.


Unable to start Kafka server on Azure VMs using Terraform

Is there an existing issue for this?

[X] I have searched the existing issues

Where would you like this feature added?
Other/Unknown
Is this feature ask due to a problem that you are encountering?
While working to deploy Kafka cluster on Azure VMs using Terraform and Ansible, I am facing issues while creating a topic, I have checked and found that all three Zookeeper servers are running in cluster but one of the Kafka servers is not getting started in  cluster.
VMs used: Dpsv5 series
OS: Ubuntu 20.04
Architecture: amd64 and arm64
The error which I am getting is:
[2023-05-30 08:35:45,623] INFO [Controller id=1, targetBrokerId=1] Node 1 disconnected. (org.apache.kafka.clients.NetworkClient)

[2023-05-30 08:35:45,623] WARN [Controller id=1, targetBrokerId=1] Connection to node 1 (myvm.internal.cloudapp.net/<IP_ADDRESS>:9093) could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)

[2023-05-30 08:35:45,623] INFO [Controller id=1, targetBrokerId=1] Client requested connection close from node 1 (org.apache.kafka.clients.NetworkClient)

The code written to create the resources through terraform in main.tf file:
main.txt
providers.txt
variables.txt
zookeeper_cluster.txt
kafka_cluster.txt
Steps followed to deploy the kafka cluster.
Run the following commands to create resources through terraform:

terraform init

terraform apply

To know the ip of kafka servers:

cat /tmp/inventery

To install the Zookeeper and the required dependencies and start zookeeper server:

ansible-playbook zookeeper_cluster.yaml -i /tmp/inventory

To install the Kafka and the required dependencies:

ansible-playbook kafka_cluster.yaml -i /tmp/inventory

To start kafka on all three server first do ssh on all three machines on which kafka is installed and run below command:

bin/kafka-server-start.sh config/server.properties

However, When I have created virtual machines manually(not through Terraform) and installed zookeeper and kafka in them with the same configuration and tried running Kafka cluster and it is running fine.
It will be really helpful if you share pointers on the above mentioned issue.
Describe potential solutions.
When I have created virtual machines manually(not through Terraform) and installed zookeeper and kafka in them with the same configuration and tried running Kafka cluster and it is running fine.
Anything else?
No response

Did you try connecting to the broker 1?


haskell.packages.ghc822/844: Fix configuration and build of GHC822/844

Motivation for this change
nix-env -qaP -A haskell.packages.ghc8xx for GHC822 and 844 fails with:
nix called without required argument 'ghc-heap'

Adding ghc-heap = null to respective configuration files leads to further failures due to missing attributes (specific version of haskell packages).
Furthermore, when all configuration problems are resolved the ghc build itself fails due to sphinx.
I'm new to nix, so if there's a way to avoid copy-paste or version-pinning, please let me know!
Things done

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

[ ] NixOS
[x] macOS
[x] Manjaro Linux 18.0.2

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@peti thanks, I see from @dotlambda 's suggestion how to change version/sha256 without creating new attributes in hackage-packages. I'll make the change.

@peti looks like after all I haven't completely figured it out. A couple things:

Unfortunately,  I couldn't figure out how to call overrideAttrs within configuration-ghc-xx, so I just moved relevant definitions to respective configuration files out of hackage-packages. Even then, it's not particularly clear why we need some special version-pinned packages in a specific ghc configuration (for instance yaml_0_11_.. is no longer a thing in 844 config) or if overrideAttrs is any clearer than just dropping a full derivation.
Cabal_1_24_2_0 in 822 compiles with one more patch for dependency constraint.
hackage-db-2_0_1 fails during compilation --- for some reason aeson doesn't have a dependency on contravarian in hackage-packages which it should have.
stack and hpack_0_31_1 in 844 (after removing non-working yaml dep) started to compile... and still are compiling after several hours. Will update later.

nix-env -qaP -A haskell.packages.ghc8xx works.
ghc844 builds just fine.
sphinx_1_7_9 moved under pyhon_packages.
Old version pinned derivations in 822/844 configurations are removed.

@peti looks good?

Merged to haskell-updates as a251d91d2a0d1d5007bdbd13a40803ecc8abd3b0. I'll merge to master once the test builds at https://hydra.nixos.org/jobset/nixpkgs/haskell-updates have come back successfully.


Jenkins ocp templates

Due to the nature of ansible-stacks repo, we can't use ansible-galaxy install. So I made this work with a single run.sh which clones stacks down to run the example.

looks good to me!
Please open an issue upstream for the namespace being hardcoded and specified in two places (jenkins.json, jenskins.yml).

@mdanter done. ticket opened: https://github.com/rht-labs/ansible-stacks/issues/103


Adding optional arguments to generate signed URI method.

Allows customization of the experience for end users of the signed URI.

I noticed https://github.com/GoogleCloudPlatform/gcloud-node/pull/1058 and thought we should implement as well, at which point I realized we didn't support the response content type/disposition either.

LGTM

@jgeewax I'm going to merge but still would like to hear what you have to say.


Move time constants into storage

The time constants that we have for defining the waiting periods should be moved into storage so they can be manipulated in the tests.

This can be parked


Step assist message Bug and doesn’t disappear. And Padding Sound Bugs with dynsurroundings

Issue Description:
The Step assist may be disabled by other mod messages keeps popping up infinitely overlapping with itself. Even thought step assist isn’t even disabled and the boots work fine but the moment you put them on you end up with this.
Also the Padding add-on still makes the game sound completely go insane. Can’t you implement a option to disable certain add-ons? For the armors?
What happens:
The Step assist may be disabled by other mod messages keeps popping up infinitely overlapping with itself. Even thought step assist isn’t even disabled and the boots work fine but the moment you put them on you end up with this.
Also the Padding add-on still makes the game sound completely go insane. Can’t you implement a option to disable certain add-ons? For the armors?
What you expected to happen:
The message to pop up once after boots equipping and then disappearing or not popping up at all!
Steps to reproduce:

Go into creative mode
Grab the armor
Put it on

...

Affected Versions (Do not use "latest"):

EnderIO: Ender IO - 5.0.43
EnderCore: EnderCore - 1.12.2-0.5.52
Minecraft: 1.12.2
Forge: <IP_ADDRESS>22
Optifine? with and witouth
Server and Singleplayer

Your most recent log file where the issue was present:
[pastebin/gist/etc link here]

If the message pops up all the time, that is because some other mod interferes with it all the time. It only gets send to the status line when the step height is set, either because step assist was turned on or because some other mod changed it, and a mod is installed that is known to forcefully disable it.

m ok but is there an option to disable the message? Since there isn’t actually a conflict and the step up works fine I would like to disable the message for my Modpack.
Same as an option to disable certain add-ons the incompatibility for padding and any mod that tweaks around sounds or adds custom noises is game breaking as there isn’t even a toggle button for padding like there is for other things like nigh vision. You basically have to throw away your helmet if you add it. As it will always turn the game sounds into crossfire of noises like you are in the middle of a war zone.

@HenryLoenwind I’m having the same issue with the step assist.
I updated from version 5.0.40 of Ender IO to 5.0.43 and from version 0.5.45 of EnderCore to 0.5.45 and updated, added, or removed no other mods (aside from updating JEI and two of its add-ons), and this started happening.
Here’s a video of what it looks like. The message keeps appearing and is, as SirAron111 described, infinitely overlapping. And just like for him, step assist is working perfectly fine for me. The message is extremely distracting, though, as it never goes away.
This did not happen before I updated to the latest versions of Ender IO and EnderCore. There has to be something wrong in the latest update of either mod, considering I didn’t update, add, or remove any other mod (other than JEI and a couple add-ons, as mentioned).

Posting comment here (and in the other step assist topic) instead of creating a new issue
I am using another mod for step assist in my pack, so there is constantly a message on the screen saying, "Step Assist may be disabled by another mod." until I toggle step assist of the DarkSteel armor (after every world load, which is often for me) I would ask for there at least to be an option to disable this error message.

No. If the error message is displayed, some mod is breaking the step height value. We don't have a way to know which, though it sounds like you have a good idea. Maybe report it to them.

Step assist still works fine. The message keeps appearing and never goes away, yet step assist isn’t broken.
Some mod may be interfering with how step assist works in Ender IO, but as previously mentioned, this didn’t start happening until I updated to version 5.0.43 of Ender IO. There has to be a change in version 5.0.43 of Ender IO (or a change in version 0.5.45 of EnderCore) that affects step assist.

The change was that msg was added... after several reports about it being broken with X Mod

Oh. So, whatever error is occurring was there all along, then; it just wasn’t being shown.
Still, for me and many other people, step assist isn’t broken. The message says “Step Assist may be disabled by another mod,” but it’s not disabled. Step assist is working just fine. It’s a non-issue. The real issue is Ender IO’s message itself, as it’s distracting and never goes away. Even if there were a problem with the step assist, I wouldn’t want to see it constantly appearing on my screen and never going away. I also have no way to tell what mod is causing the “conflict” as I’ve seen no errors in the console.
Currently, I have no option but to either downgrade to the previous version of Ender IO (which I don’t want to do since the latest version fixed a bug related to the vacuum chest) and never update the mod again or to live with a never-ending stream of “Step Assist may be disabled by another mod.”
I really love Ender IO; it’s one of the best mods out there, but I’d love a config option to disable the message, as it’s pretty annoying to deal with. 😄

I have isolated the conflict to this mod:
https://minecraft.curseforge.com/projects/client-tweaks
Minecraft 1.12.2 with only this mods loaded:
Forge Mod Loader version <IP_ADDRESS>25
ClientTweaks_1.12.2-3.1.11
EnderCore-1.12.2-0.5.53
EnderIO-1.12.2-5.0.43
This happens:

But step assist is actually working fine. When I disable step assist I cannot climb steps:

The clienttweaks mod config is the default one:

And I assigned a hotkey to step assist:

And MC auto-jump is set to OFF:

So it seems that Ender IO is determining that step-assist is disabled when it is actually not disabled, or the clienttweaks mod is setting some value in a wrong way.

That makes sense, as I, too, have Client Tweaks installed.

That makes sense, as I, too, have Client Tweaks installed.
Hopefully, this bug can be fixed, whether it’s on Client Tweaks’ end or on Ender IO’s end.

EnderIO's condition for resetting the step height is broken.
https://github.com/SleepyTrousers/EnderIO/blob/release/1.12.2/enderio-base/src/main/java/crazypants/enderio/base/handler/darksteel/DarkSteelController.java#L234-L241
The code posting the message and setting the stepHeight for step-assist runs if stepHeight is below MAGIC_STEP_HEIGHT (etc.).
Next tick, stepHeight will still be equal to MAGIC_STEP_HEIGHT - causing the else if-block to run, which resets the stepHeight back to 0.6, even if the player is wearing Dark Steel Armor. Repeat from there.

There are many mods that mess with step assist for example I have client tweaks and everlasting abilities as well as ice and fire mod they all do something to step assist. But the assist still works fine and the option for the darksteel boots step assist and the toggle on/off work fine as well it’s just that the message pops up. If it ever didn’t work for some people making modpacks or the like and they complained they didn’t bother to check the config of the mods messing with step height etc.
But I still would like to have a config option to enable/disable this message on the ender io part. Since for a Modpack maker it’s hard to fix something that works fine but adding in a option to disable a display of a message shouldn’t be too hard to implement in the next update of ender io/ ender core.
Of course you could go to every mod dev that messes with step height and step assist in the future and now and tell them to make it fit the Ender io mod so the message doesn’t pop up even thought their step assist function works fine. But that doesn’t sound as easy as this config option implementation. Is what I think at least?

It looks like this was fixed in version 5.0.44 of Ender IO.
The changelog says “Fixed step assist logic.”

If you add ProjectE to Omnifactory, the message keeps popping up. It's very annoying.

This bug still exists and is so annoying.

well, you found thios report, why don't you read it then?
how do you expect it to work? A) report a message to let you know there is an issue or b) silently fail, creating the same issue about the upgrade not working?!

Playing on Stoneblock 1.0.37 on a small multiplayer server. EnderIO version 5.1.55 on the server and client side. Experiencing this issue again.

make a new proper report or read the rotting one you just commented on please


Building using Windows Linux Subsystem, fsevents

Hi all,
I was using the Windows Linux Subsystem, I installed that, npm, git, nodejs, everything fine. Cloned the directory and went to build with NPM install and got:
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>npm ERR! Linux 4.4.0-43-Microsoft
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v4.2.6
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the pty.js package,
npm ERR! not with npm itself.

Is this an error that I could potentially work around?
npm version 3.5.2
nodejs version 4.6.2

Issue was nodejs was not installed using apt-get but without these steps:
https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions
I installed the latest from the instructions, re-ran and was successful!


VSCode Version: 1.13.1
OS Version: Windows 7

Steps to Reproduce:

Run the command "Git: Checkout to...".
Enter a commit id (e.g. "6e2d156") in the "Select a ref to checkout" box.

VSCode does not move ahead.

Can't reproduce this, working for me.

@jens1o Did you try with a value that is a commit id and not the name of a branch / tag?

Okay, I should consider thinking about my reading skills. Now I can reproduce. Sorry. :/

To keep the number of issues in our inbox on a manageable level, we're closing issues that have been on the backlog for a long time but haven't gained traction: We look at the number of votes the issue has received and the number of duplicates issues filed.
Thanks for your understanding. Happy coding!


add "deprecated" as an allowable status

consider adding "deprecated" as an allowable status in the Alaska profiles/schema. I just wanted to use it because there is a large data set where I have discovered a large number of errors and have cleaned up. I still need a record of this data as the source for my new product and for historical reasons, but I don't want people to think it is what should be used. Seems like "deprecated" is the most correct status.

@eosnas I would just ignore the errors and go about your day (isn't that our standard operating procedure anyway?)
I wouldn't look at the profiles as an absolute standard, but more as guidelines to help initiate quality metadata records as part of an ideal project planning an approval workflow. The @USFWS/ak-data-managers can discuss incorporating this into the next update of the profiles.


Add disk status to diagnostic report.

Closes #887

Mine shows Unavailable, but it hasn't got the firmware update yet. One other question for you.

Yeah, the hotspot update will go out with the next GA release.


Extends config plugin API to customize the default OAuth success html

Why are the changes needed?

This PR allows configuration plugins to return a customized default OAuth success HTML page.
What changes were proposed in this pull request?

This PR extends the configuration plugin API to change the default OAuth success HTML.
How was this patch tested?

Unit tests was added to check the behavior.

disregard the readthedocs preview build failure


Document parameters in tooltips

Added tooltip extension method to the base processing algorithm, applied it in all processing algorithms.

Needs translation, probably the corresponding tr-methods need to be added first.


html/mediasource_test supported and failing on Firefox

The new version 42 of Firefox supports mediasource, and so the test
html/mediasource_test/supported is passing, and the test
html/mediasource_test/functional is failing with a runtime error.
This is currently happening on Windows, since the linux bots are on version 41.
The error is

                             3	                                                            FAIL
Expectation:                                                                     functional media types                                 .

Expected: <true>                       Actual: <false>

Also, according to the status file,
"# Firefox Feature support statuses-"
"# All changes should be accompanied by platform support annotation changes."
There is no info about where these annotations are, that should be changed.

Presumably the annotations refers to the @SupportedBrowser class annotations, e.g. https://api.dartlang.org/1.12.2/dart-html/MediaSource-class.html


From private repo

@Taojunshen : Thanks for your contribution! The author, @NathBarn, has been notified to review your proposed change.


Time Zone

Allow to change the Time Zone. GMT +2

How was this fixed?
I want to do GMT -5

How was this fixed? I want to do GMT -5
Sorry I never got an answer,

In logging.py, I made some changes to datetime_string() to adjust for the timezone.
dt = machine.RTC().datetime()
timezone = -4
hour = dt[4] + timezone
if hour < 0:
hour += 24
if hour > 24:
hour -= 24
return str(dt[0])+'-'+str(dt[1])+'-'+str(dt[2])+' '+str(hour)+':'+str(dt[5])+':'+str(dt[6])
#return "{0:04d}-{1:02d}-{2:02d} {4:02d}:{5:02d}:{6:02d}".format(*dt)
I'm sure there's a better way than this, but it seems to work.


docs: add PZU (Poland) to ADOPTERS.md

PZU uses CloudNativePG for their PostgreSQL on-premise cloud solution/DBaaS.

/ok-to-merge adding new adopter


Allow different Username/Password for each URLs

Currently, Username/Password for BasicAuth is common for all urls.
But it seems better to allow different username/password for each urls.
For example, it allow us graceful password update like following process(Currently, we must stop client before update the password):

First we start with following configulations:

there is a elasicsearch cluster on example.com:9200 and it accept Username=elastic, Password=xxxxxxxx
Our client setting is like: Config1: URL=example.com:9200, Username=elastic, Password=xxxxxxxx

Update configulation like:

Config1: URL=example.com:9200, Username=elastic, Password=xxxxxxxx
Config2: URL=example.com:9200, Username=elastic, Password=yyyyyyyy // add this config

Deploy it.

it will occur error on Config2 but Config1 so it's continue connected.

Change password config of our elasticsearch cluster on example.com:9200 from xxxxxxxx to yyyyyyyy.

it will occur error on Config1 but Config2 so it's continue connected.

Delete configulation for password=xxxxxxxx

If you want to store the two passwords for the same user I would recommend to create two clients with the relevant configurations.
You could then control which client you decide to use or implement fallback on error if the first client fails, allowing you to gracefully update your credentials.
An easier way would be to create a new user, propagate the change to your application and then remove the old user on the cluster.


It is unclear how to use the disabled flag

The documentation for the Delete operation states that you can control whether or not deleted users should be returned using the disabled flag. There does not appear to be any other reference to this disabled flag or how to use it.

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

ID: 95e40952-bca9-9860-c1c5-1f422d2fc7fd
Version Independent ID: f5dfb442-27fc-1d5f-a79c-d446e703b728
Content: Users (VSTS Graph)
Content Source: docs-ref-autogen/5.0/graph/Users.yml
Product: devops
GitHub Login: @wnjenkin
Microsoft Alias: whjenkin

@justmarks to help with this issue

@smithtad thanks for calling this out.  We'll update the docs to be clearer here.  The correct way to see if a user is deleted is to check their membership (GetMembershipStateAsync - https://docs.microsoft.com/en-us/rest/api/azure/devops/graph/membership states/get?view=azure-devops-rest-5.0) and if they are deleted, active will be equal to false

@justmarks Thanks for the response. This is only useful, however, if you already have the subjectDescriptor. I can't get that for deleted/inactive users.
Ultimately what I'm trying to do is return a list of all users, including deleted users. The documentation for the users - delete endpoint here indicates that "Other GET calls, which may return multiple users, can control whether or not deleted users should be returned using the disabled flag, which defaults to false." The users - list endpoint doesn't appear to support this, however.


[#1554] Add flags to advancements

Adds flags and the getFlag, setFlag, unsetFlag methods to Advancement.
Resolves #1554

In principle this makes sense to do, but once we open the floodgates, there's no closing them. My concern here is that we're leaning too hard into 'Advancements are Documents' without them actually being Documents. It's convenient to use familiar APIs, but ultimately Advancements cannot be updated atomically, they propagate their updates up to the parent Item, and I don't want to be left with another mini-unlinked-token situation on our hands again.
I think I would have more confidence here if we had some concrete use-cases of what Advancement flags would be needed for. It would allow us to weigh the costs of attempting to accommodate those use-cases in some other way.


Fix infinite loop if variable can't be found in outer scope

This is hard to fix without an example, do we know how to reproduce this bug?
Both of these raised a compilation error so I don't know where to look:
f := fn {
    b := a
}

{
    b := a
}

Closing since no repro


multiple task lists false claims

In the readme, you mention "multiple task lists" are supported and the screenshot supports that. But when I install the app, the left sidebar only shows "Deleted tasks".
I am using Errands with Nextcloud sync. Am I missing anything?

Added in 45.1.

That's great! Thank you! Has it been published on flathub?

@madhums I've pushed it on flathub. Will be available in a couple of hours.


Add support for other themes

Transferring https://github.com/jtpio/jupyterlab-theme-toggle/issues/3 here in this repo.
For now the theme toggle extension only support the dark and light themes:
https://github.com/jupyterlab-contrib/jupyterlab-topbar/blob/4eb59bc966d099f39d1aadad8bd47c63899b7d89/packages/theme-toggler-extension/src/index.tsx#L90-L93
However this could be made configurable via the settings system.

How do you envision this? Changing to sort of dropdown component and letting users to configure more than two themes or still use toggler component where users can configure two themes at a given time?

Since there is already the possibility to choose from a list of themes via the Settings menu, maybe limiting the toggle to 2 options would make sense?
End users would go to the settings editor to enter the names of the two themes they would like to use.


Parameter mismatch warning when type-casting parameters

I'm not entirely sure if this is a bug or not, but it's an undocumented change in behaviour that was introduced in v20190215. Newer versions also produce the warning.
This particular syntax of type casting arguments is not mentioned in the docs, but evidently it works.
My examples are artificial and redundant, but we had real code that required type casts in params.
I know workarounds and ways to fix this, but please still advise on the underlying issue.
Running Java version on MacOS.
Example
param-cast.js:
/**
 * @enum {string}
 */
const Item = {
	FOO: 'foo',
	BAR: 'bar',
	BAZ: 'baz'
};

/**
 * @type {!Object<Item, number>}
 */
const a = {
	'foo': 1,
	'bar': 2,
	'baz': 3
};

Object.keys(a).forEach((/** @type {Item} */ maybeItem) => {
	/**
	 * @type {Item}
	 */
	const strictlyItem = maybeItem;
});

Old behaviour
npm i google-closure-compiler@20190121

npx google-closure-compiler --js param-cast.js --compilation_level ADVANCED_OPTIMIZATIONS --checks-only

Result: No warnings
New behaviour
npm i google-closure-compiler@20190215

npx google-closure-compiler --js param-cast.js --compilation_level ADVANCED_OPTIMIZATIONS --checks-only

Result:
param-cast.js:25: WARNING - actual parameter 1 of Array.prototype.forEach does not match formal parameter
found   : function(Item<string>): undefined
required: (function(string, number, Array<string>): ?|null)
Object.keys(a).forEach((/** @type {Item} */ item) => {
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

0 error(s), 1 warning(s), 100.0% typed

Notes
It seems like the previous behaviour of this:
(/** @type {FOO} */ param) => {
	// ...
}

Was the equivalent of this:
(param) => {
	param = /** @type {FOO} */ (param);
	// ...
}

But the new is the equivalent of this:
/**
 * @param {FOO} param
 */
(param) => {
	// ...
}

I believe the old behaviour was more correct since type casting notation casted the parameter and did not change the function signature.
Was this an intended change?

This is intended, and this particular syntax was never intended to work as a type cast. Writing (/** @type {string} */ s) => {} has always been equivalent to (/** string */ s) => {}. See the documentation of 'inline parameter annotations' here
v20190215 fixed a type inference bug around inline parameter annotations on function literals passed  as arguments to a function. This bug made
someFunction((/** @type {FOO} */ param) => {
	// ...
})

equivalent to
someFunction((originalParam) => {
	var param = /** @type {FOO} */ (/** @type {?} */ (originalParam));
	// ...
})

Note that this was more unsafe than a regular type cast. The compiler validates that normal type casts are to a supertype or a subtype. However, this bug let you 'cast' the parameter to any unrelated type, like number -> string.
The bug only affected function literals passed as parameters. For example, this seemingly equivalent code threw a type error even before v20190215.
/**
 * @enum {string}
 */
const Item = {
	FOO: 'foo',
	BAR: 'bar',
	BAZ: 'baz'
};

/**
 * @type {!Object<Item, number>}
 */
const a = {
	'foo': 1,
	'bar': 2,
	'baz': 3
};

const callback = (/** @type {Item} */ maybeItem) => {
	/**
	 * @type {Item}
	 */
	const strictlyItem = maybeItem;
};

Object.keys(a).forEach(callback);

This change should have been in the v201090215 release notes. I apologize for forgetting to include it.


Support ARM Macs?

Any plans to support Macs with the ARM chipset?

I don't have any Apple hardware, but it hopefully just works! I think building from source shouldn't run into any issues, but please follow up if it does.
In case there's a problem that requires patching the code, please open a PR, so that I can integrate it in the codebase.
A PR to set up a Github workflow for building Mac binaries is also welcome!

I followed the build instructions for the project and I got the following error:
cc -o pty -std=gnu99 -O2 -fPIC -lutil pty.c minivt.c -I. -L.
pty.c:1:10: fatal error: 'pty.h' file not found
#include <pty.h>
         ^~~~~~~
1 error generated.
make: *** [pty] Error 1

Is there a dependency I need to install?
This is my version of make :
GNU Make 3.81
Copyright (C) 2006  Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.

This program built for i386-apple-darwin11.3.0

A quick online search suggested replacing pty.h with util.h (or if that doesn't work, maybe libutil.h). Can you let me know if that works?
If yes, I'll try to get it in the main source, if necessary with some ifdef gates around it.

I did change pty.h to util.h in the pty.c file, and it did finish the build. And I now have a pty executable in the folder.
However, I can't get it to activate when I am in Lite-XL. (Either doing CTRL-T or CTRL-`)
My folder path is /Users/user/.config/lite-xl/plugins/tmt
Is there something else I need to be aware of?

Is the problem that Lite does not pick up the plugin at all? (If you do Core: Open Log or Log: Open as Doc there should be an entry Loaded plugin "tmt".)
If not, you probably installed the plugin in the wrong folder. I'm not sure what the proper path is on macOS, but you need to put it in Lite XL's USERDIR. On Linux that is ~/.config/lite-xl (where you put it), but I'm not sure what it is on Mac.

This is the error I get when I do Core: Open Log
Sat Apr  8 13:05:49 2023 [ERROR] /Users/user/.config/lite-xl/plugins/tmt/init.lua:10: module 'plugins.tmt.tmt' not found:
	no field package.preload['plugins.tmt.tmt']
	no file '/Users/user/.config/lite-xl/plugins/tmt/tmt/init.lua'
	no file '/Users/user/.config/lite-xl/plugins/tmt/tmt.lua'
	no file '/Applications/Lite XL.app/Contents/Resources/plugins/tmt/tmt/init.lua'
	no file '/Applications/Lite XL.app/Contents/Resources/plugins/tmt/tmt.lua'
	no file '' at /Applications/Lite XL.app/Contents/Resources/core/init.lua:1226

stack traceback:
[C]: in function 'require'
/Users/user/.config/lite-xl/plugins/tmt/init.lua:10: in main chunk
[C]: in function 'require'
[C]: in function 'xpcall'
/Applications/Lite XL.app/Contents/Resources/core/init.lua:1225: in function 'core.try'
/Applications/Lite XL.app/Contents/Resources/core/init.lua:1013: in function 'core.load_plugins'
/Applications/Lite XL.app/Contents/Resources/core/init.lua:793: in function 'core.init'
[string "local core..."]:8: in function <[string "local core..."]:2>
[C]: in function 'xpcall'
[string "local core..."]:2: in main chunk

Here is the path I am using for the plugin:
➜  tmt pwd
/Users/user/.config/lite-xl/plugins/tmt

Here are the contents of the tmt folder:
➜  tmt tree
.
├── LICENSE
├── Makefile
├── README.md
├── init.lua
├── lite_xl_plugin_api.h
├── lua_tmt.c
├── minivt.c
├── minivt.h
├── pty
├── pty.c
├── pty.win.c
├── tmt.c
├── tmt.h
├── tmt.so
├── winpty
│   ├── winpty.h
│   └── winpty_constants.h
├── winpty-agent.exe
└── winpty.dll

Seems like it's not picking up tmt.so as it's only looking for Lua libraries, and not native ones (/Users/user/.config/lite-xl/plugins/tmt/tmt.lua rather than /Users/user/.config/lite-xl/plugins/tmt/tmt.so).
Are you running a current version of Lite XL? I believe only recent ones have good enough support for native libraries, namely 2.1.1 and up. I'm not sure if pre-2.1 versions have support for native libraries at all. (2.1.0 has some issues that also prevent tmt from working.)
If you're running a recent version but it's not picking up the native library still, check if putting
package.cpath = USERDIR .. "?.so"

before require "plugins.tmt.tmt" in TMT's init.lua helps.
If it doesn't, I'd ask the Lite XL developers about how loading native libraries works on macOS. It's possible there's some issues with them that I'm not aware of.


Interpret changes

Hi,
Please review the changes and approve them. Changes were done to generate the global importance rank of the features used in the model. Also, to allow the user to choose whether to run the interpretation of model on  Training data or Test Data.
Thanks!
Karthik

Changes are good to go.


.

I am used to the C-bindings and wonder if ImportName is / will be available too.
I see it is mentioned here https://github.com/golang-auth/go-gssapi/wiki/Golang-GSSAPI-bindings-specification, but it is not clear to me what it means.
Thank you

It will be available in the next release.. we are working on a version with
a standardized interface that works with the C bindings and natively.
Jake
On Thu, Aug 1, 2024, 13:42 huaraz @.***> wrote:

I am used to the C-bindings and wonder if ImportName is / will be
available too.
I see it is mentioned here
https://github.com/golang-auth/go-gssapi/wiki/Golang-GSSAPI-bindings-specification,
but it is not clear to me what it means.
Thank you
—
Reply to this email directly, view it on GitHub
https://github.com/golang-auth/go-gssapi/issues/7, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACMWSU3GBOHRCLOG62N3GGLZPJXPHAVCNFSM6AAAAABL3A5GE6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ2DGMBRHAZTOMQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Submit/avidemux 2.8.1 fix

Description of changes
Change LD_LIBRARY_PATH prefix for wrapper.
Things done
Change LD_LIBRARY_PATH prefix for wrapper from "${libXext}/lib" to "$out/lib" so that connected libraries can be found again. No Idea, why ${libXext}/lib was sufficient in prior versions. I check binaries from 23.05 and they had $out/lib in their rpath.

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[X] Fits CONTRIBUTING.md.

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

Remove pull request since similar fix it's already requested by jerith666 last month


Adds switch for PivotDataToColumn

By default, calculated values for PivotTable data appears on rows.  This switch changes that behavior so the calculated values appear on columns instead.

Very cool! Just to confirm. This is the expected result
$f="c:\temp\test.xlsx"

rm $f -ErrorAction Ignore

ps |
    ? Company |
    select Company, Handles, PM |
    Export-Excel $f -Show `
        -IncludePivotTable `
        -PivotRows Company `
        -PivotData @{Handles='sum'; PM='sum'} `
        -PivotDataToColumn

Yes, that's what I was going for.  If you run it without the switch, do you get paged memory and virt memory as sub-rows of each company?  That was the behavior I was seeing before implementing the switch.

Yes. This is great! I've wanted to add this feature and did not have time to research it. I should have time to merge it today.
Thanks!
Doug

Glad I could help!  Yeah, I was just fixing it manually but decided there had to be a way to fix it programmatically.


add information somewhere in docs about unlocking postgres db

we have potential use-case when DB is locked during upgrade/restart/termination etc.
Appropriate steps should be published in documention howto solve the problem:
// login into the container and remove lock:
docker exec -ti postgres bash
psql -d postgres -U postgres -c "delete from zafira.databasechangeloglock"
and restart everything
exception in reporting logs:
2020-10-28 06:30:28.034 INFO [zafira] [main] liquibase.executor.jvm.JdbcExecutor: SELECT LOCKED FROM zafira.databasechangeloglock WHERE ID=1 2020-10-28 06:30:28.035 INFO [zafira] [main] l.lockservice.StandardLockService: Waiting for changelog lock.... 2020-10-28 06:30:38.036 INFO [zafira] [main] liquibase.executor.jvm.JdbcExecutor: SELECT LOCKED FROM zafira.databasechangeloglock WHERE ID=1 2020-10-28 06:30:38.040 INFO [zafira] [main] l.lockservice.StandardLockService: Waiting for changelog lock.... 2020-10-28 06:30:48.040 INFO [zafira] [main] liquibase.executor.jvm.JdbcExecutor: SELECT LOCKED FROM zafira.databasechangeloglock WHERE ID=1 2020-10-28 06:30:48.042 INFO [zafira] [main] l.lockservice.StandardLockService: Waiting for changelog lock.... 2020-10-28 06:30:58.044 INFO [zafira] [main] liquibase.executor.jvm.JdbcExecutor: SELECT ID,LOCKED,LOCKGRANTED,LOCKEDBY FROM zafira.databasechangeloglock WHERE ID=1 2020-10-28 06:30:58.068 ERROR [zafira] [main] c.q.z.d.state.DatabaseStateManager: Could not acquire change log lock.  Currently locked by 114e7a89206c (<IP_ADDRESS>) since 9/4/20, 12:03 PM liquibase.exception.LockException: Could not acquire change log lock.  Currently locked by 114e7a89206c (<IP_ADDRESS>) since 9/4/20, 12:03 PM 	at liquibase.lockservice.StandardLockService.waitForLock(StandardLockService.java:236) 	at liquibase.Liquibase.update(Liquibase.java:184)

If we could add the ability to see the logs of the service that is actually locking the database to be able to know when the process really is done. That way we would be able to know when to delete the lock if the process did not unlock it by itself.

unlock db forcibly using native postgres advisory locks service. in this case after stop we focibly unclock db for the next attempt.


Navigator index multi-language render JSON support

Bug/issue #, if applicable: rdar://83398083
Summary
Adds support for the navigator index to process render JSON that contains variant overrides by applying patches for the languages in which the page is available.

Testing
Verify that when building a navigator index that contains multi-language render JSON, the content gets curated under each language tree.
Checklist

[x] Added tests
[x] Ran the ./bin/test script and it succeeded
[x] Updated documentation if necessary

@swift-ci please test this

@swift-ci please test

@swift-ci please test


Add path_accessor key to react table transformer

The code comment in reacttable.py explains why this is useful to have

Coverage increased (+0.06%) to 93.197% when pulling bb79043a03db5f19c17e9e238ce39c10893cba8a on mikeengland:fix-nested-access into 157b150c9f4593b309ff2daa39f23bb0fe7a2352 on kayak:master.


How to use TensorBoard during training?

Hi there!
How to use TensorBoard during training?
Thanks in advance!

Hi! Yes, it worked! I was missing TensorFlow in my environment.
Thanks!

Hi,
I want to ask have you ever used the tensorboard to save and visualize the details of layers, weights, and biases of the model? If so, could you please give me some hints because I have stuck in how to visualize the model by tensorboard.
Thanks in advance!

@yaxi333: https://wandb.ai is better suited for that :wink:

@yaxi333: https://wandb.ai is better suited for that 😉

Could you please provide a tutorial on how to integrate W&B into OpenPCdet? Thank you!


Tree shaking not working with webpack 4.5

Do you want to request a feature or report a bug?
I'd like to report a bug

What is the current behavior?
Tree shaking does not appear to be working. Dead code should be identified in the output bundle with a comment such as
/* unused harmony export _functionname_ */
If the current behavior is a bug, please provide the steps to reproduce.
Refer to the basic configuration in https://github.com/cdhgee/webpack-tree-shaking.

Run npm install
Run npm run build
Examine the output in dist/bundle.js. Around line 83, the exports from another-module.js should be shown.

What is the expected behavior?
Functions c and d are not used anywhere in the project and should be identified with a comment such as
/* unused harmony export c */
Because these comments are missing, I conclude that either (a) tree shaking is not running, or (b) tree shaking is running but is not identifying c and d as dead code.
If this is a feature request, what is motivation or use case for changing the behavior?
n/a
Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.
NodeJS version: 9.11.1 (64-bit)
Webpack version: 4.5.0
OS: Windows 10 1709 (64-bit)
These versions are all the most recent available as of today (2018-04-08).

I am not sure, I guess sideEffects is for library devs only..??
I just git cloned your example and
extracted another-module to node_modules and
added a package.json with sideEffects:false,
build it with --mode production but still no treeshaking.
It works in any way if you add:
optimization: {
    minimizer: [
      new UglifyJsPlugin({ // https://github.com/webpack-contrib/uglifyjs-webpack-plugin
        sourceMap: false,
        uglifyOptions: {
          ecma: 5,
          warnings: true,
          comments: true,
          beautify: true
        },
      })
    ]
  }

@sokra Shouldn't it work without explicitly adding the UglifyJsPlugin, just by adding --mode production, at least when another-module.js would be a regular npm package with sideEffects:false ?

Tried your repo @cdhgee and it works fine. Note that tree shaking is only enabled in production mode:
$ npm run build -- --mode production --display-used-exports
Hash: c665586af0bb888f4551
Version: webpack 4.5.0
Time: 529ms
Built at: 2018-4-9 09:46:10
    Asset       Size  Chunks             Chunk Names
bundle.js  599 bytes       0  [emitted]  main
Entrypoint main = bundle.js
   [0] ./index.js + 1 modules 264 bytes {0} [built]
       | ./index.js 48 bytes [built]
       | ./another-module.js 216 bytes [built]
       |    [only some exports used: a]

@sokra It is only enable in production mode via a plugin or something internal? Want to document it in Tree shaking guide https://webpack.js.org/guides/tree-shaking/

@montogeek
There is also a  sideEffects?: boolean; in the Optimization Interface.
If you set sideEffects in package.json and under optimization, which one has higher priority?
At least this should be documented..

No it works, without explicitly adding the plugin, just --mode production

@sokra Thanks for the update. Can I suggest updating the Tree Shaking Documentation page on webpack.js.org?
The current documentation states that dead code will be identified without production mode (the dist/bundle.js output part of section Add a Utility. This doesn't seem to be the case.

webpack: 4.5.0.
I also have the same problem.
webpack --mode production take effects, but when I use mode in webpack config, tree-shaking do not work (I had setted sideEffects on package.json).
I followed the steps in Tree Shaking Documentation:

Use ES2015 module syntax (i.e. import and export).
Add a "sideEffects" entry to your project's package.json file.
Include a minifier that supports dead code removal (e.g. the UglifyJSPlugin).

what's the problem? @Legends

@sokra I can also confirm that /* unused harmony export */ comments are missing from the production output when optimizations.minimize=false. Using the same repo @cdhgee provided above, given:
module.exports = {
  mode: "production",
  devtool: "none",
  entry: "./index",
  output: {
    filename: "bundle.js",
    path: path.resolve(__dirname, "dist"),
  },
  optimization: {
    minimize: false,
    sideEffects: false,
  }
};

I get the following output:
/******/ ([
/* 0 */
/***/ (function(module, __webpack_exports__, __webpack_require__) {

"use strict";
__webpack_require__.r(__webpack_exports__);

// CONCATENATED MODULE: ./another-module.js
function a(i) {
  console.log("a is " + i);
}

function b(i) {
  console.log("b is " + i);
}

function c(i) {
  console.log("c is " + i);
}

function d(i) {
  console.log("d is " + i);
}

// CONCATENATED MODULE: ./index.js

a(3);

/***/ })
/******/ ]);

I have a babel-minify step in my gulp pipeline to which I want to delegate all minimization and dead code removal. Is such a setup currently possible outside the Webpack realm?

@zhongds I follow the Tree Shaking guide document and do exactly what it inform. My code work like a charm without UglifyJsPlugin.

@zhongds like a charm ?
So you solved your problem?

As @sokra said above, tree shaking is only enabled in production mode.
Doc here needs improvements because it's not only UglifyJsPlugin but a bunch of plugins are needed for tree shaking to work. See the mode doc here.

Also, check if you're using babel-loader. That was my problem, it was transpiling ES6 modules into CommonJS, thus breaking tree shaking.

@AndrewSouthpaw Which versions of babel-core/babel-loader are you using? I'm using babel-core==6.26.3 and babel-loader==7.1.5 and using modules: false in my root .babelrc gives me an error:
Using removed Babel 5 option: [path-to-config].modules - Use the corresponding module transform plugin in the `plugins` option.

Any idea how to avoid module transpiling on the newer babel-core?

@AndrewSouthpaw Thanks that seems to make a difference.
Still not getting any improvements on ramda, which I'm importing using import * as R from 'ramda';. Does anyone know if tree-shaking should be able to optimize these imports?

IIRC you need to use the ramda-es version, which is optimized for ES6 imports.
We could never get it to work (because we didn't know about the modules issue from before), so we solved it this way: we created a ramda_loader.js file which just grabs all the exports from Ramda in their cherry-picked format, comment them all, then incrementally uncomment them as they're needed. It took an hour or two to set it up, but now auto-imports work a lot better through our IDE as an added benefit.
export const any = require('ramda/src/any')
// export const anyPass = require('ramda/src/anyPass')

YMMV. You can also just check out the ramda docs about ramda-es and that may work for you.

Thanks mate I'll have a look at ramda-es. I just realized I already ran into your post on Ramda, Webpack and Tree shaking when googling the issue :sweat_smile:

Hahaha. Yeah that's why I wrote it, because it caused us so much pain figuring it out. 😆

For mine I do this:
{ "presets": ["env", { "modules": false }] } – @AndrewSouthpaw

Thanks for this hint! I was facing the same problem and setting modules to false in my .babelrc did fix it!

"@babel/core": "^7.0.0-rc.1",     "@babel/preset-env": "^7.0.0-rc.1",     "@babel/preset-react": "^7.0.0-rc.1",     "antd": "^3.8.0",     "babel-core": "^6.26.3",     "babel-loader": "^8.0.0-beta.4",     "babel-plugin-import": "^1.8.0",     "babel-preset-env": "^1.7.0",
with these devDependencies, how should i set my .babelrc
{   "presets": [     [       "@babel/preset-env",       {         "targets": {           "node": "current"         }       }     ],     "@babel/preset-react"   ] }

@Vsion After reading the docs, it seems you just have to put "sourceType": "module" in your .babelrc file (it is the default value btw). It still doesnt work for me :/
my webpack.config.js:
optimization: {     usedExports: true,     sideEffects: true   },
in my package.json (seems not important ):"sideEffects": false,
I m using webpack 4.17.1, babel 7.0.0-rc.2, babel-loader 8.0.0-beta.3 and i run webapck with --mode production
What am i missing ?
FYI, i have a math.js file:
export const add = (a, b) => a + b; export const sub = (a, b) => a - b;
and a main.js file:
import { add } from './math'; console.log('4 + 2 = ', add(4, 2));
I can still see the sub method declaration in my bundle.

@webpack/documentation-team the updated Tree Shaking instructions worked perfectly for me, big thanks to whoever did that update!
 Adding "sideEffects": false to the package's package.json file cut the production build size for the main project in half (shaved hundreds of kbs). Double checked the build stats on webpack visualizer and tested the output bundles.
🎉 🎉 🎉

Does tree shaking work with mode: development and ModuleConcatenationPlugin only?
I've tried and was not successful. Only the production mode made it work.
Is there a detailed way how to setup tree shaking in development mode?
The current documentation makes it look easy and working with the development mode by default, but it is not the case.
Thank you,

@GuillaumeCisco tree shaking does not work in development mode per the docs here


whole image vs single quadrant transform

This issue follows on from a previous # that may have been closed, but I have further information. This is FYI, I will investigate further:
(1) I constructed a function to generate a pseudo O- photoelectron spectrum. O- photodetachment has well defined fine-structure transition positions and intensity ratios. The spectrum consists of 6 Gaussian transitions, very similar to abel.tools.analytical.sample_image_dribinski(). In my new-branch fork, the "_dribinski" name has been dropped, and added as a parameter, sample_image(n=361, name="dribinski", sigma=2) and
for O- sample_image(n=1001, name="Ominus", sigma=3, temperature=200).
(2) The speed distribution of the raw simulated spectrum agrees pretty well with an experimental measurement, for both the whole image, and single quadrant, from calculate_speeds(). Middle panel of figure.
(3) The speed distribution of raw Q0 quadrant (green line, thickened) -> fabel_hansenlaw_transform() -> iabel_hansenlaw_transform() (red line) agrees exactly. Right side panel.
(4) There is a persistent issue with the full quadrant analysis which slightly broadens the speed distribution. Blue line right panel.

@stgg, Thanks for making the new sample image! That looks really cool.
Are you using the get_ and put_image_quadrants() functions? I think that they may cause a one-pixel shift for the left quadrants in the case of a odd-sized image:
In [54]: z = np.zeros((5,5)); z[1,1]=1; z[1,-2]=1; z[-2,1]=1; z[-2,-2]=1; print z
[[ 0.  0.  0.  0.  0.]
 [ 0.  1.  0.  1.  0.]
 [ 0.  0.  0.  0.  0.]
 [ 0.  1.  0.  1.  0.]
 [ 0.  0.  0.  0.  0.]]

In [55]: q = abel.tools.symmetry.get_image_quadrants(z, reorient=True)

In [56]: for quad in q: print quad
[[ 0.  0.  0.]
 [ 0.  1.  0.]
 [ 0.  0.  0.]]
[[ 0.  0.  0.]
 [ 0.  1.  0.]
 [ 0.  0.  0.]]
[[ 0.  0.  0.]
 [ 0.  1.  0.]
 [ 0.  0.  0.]]
[[ 0.  0.  0.]
 [ 0.  1.  0.]
 [ 0.  0.  0.]]

In [57]: r = abel.tools.symmetry.put_image_quadrants(q); print r
[[ 0.  0.  0.  0.  0.]
 [ 1.  0.  0.  1.  0.]
 [ 0.  0.  0.  0.  0.]
 [ 1.  0.  0.  1.  0.]
 [ 0.  0.  0.  0.  0.]]

Well done @DanHickstein, the bug was that I was trimming the left-half quadrants , before flipping, when the trim should be after the flip:
else:
        # odd size image remove extra row/column added in get_image_quadrant()
        Top    = np.concatenate((np.fliplr(Q[1])[:-1,:-1], Q[0][:-1,:]), axis=1)
        Bottom = np.flipud(np.concatenate((np.fliplr(Q[2])[:,:-1], Q[3]), axis=1))

In [2]: z = np.zeros((5,5)); z[1,1]=1; z[1,-2]=1; z[-2,1]=1; z[-2,-2]=1; print z[[ 0.  0.  0.  0.  0.]
 [ 0.  1.  0.  1.  0.]
 [ 0.  0.  0.  0.  0.]
 [ 0.  1.  0.  1.  0.]
 [ 0.  0.  0.  0.  0.]]

In [4]: q = get_image_quadrants(z, reorient=True)

In [5]: put_image_quadrants(q, odd_size=True)
Out[5]:
array([[ 0.,  0.,  0.,  0.,  0.],
       [ 0.,  1.,  0.,  1.,  0.],
       [ 0.,  0.,  0.,  0.,  0.],
       [ 0.,  1.,  0.,  1.,  0.],
       [ 0.,  0.,  0.,  0.,  0.]])

Issue closed, solved by @DanHickstein


Self-supervised learning loss doesn't come down

Hi Wan,
Thanks for your great work. I am running your code with command
python3 network/run_engine.py --initial_model ./pretrained/synthetic.pth --mode Train --model_dir ./output --tag self-supervised  --lr 0.0001
I've noticed this triggers joint training of real and synthetic dataset. I have this problem that during each epoch, the metric keeps going back and forth and is basically over 40mm. Here's the log example during training:
[12-2900]: metric: avg_joint_error: 60.2542 , loss: synt_uv: 15.4588 synt_d: 26.9756 mv_projection: 9740.4551 mv_consistency: 0.4032 uv_hm_mean: 0.0002 pose_prior: 0.6047 collision: 4.4668 bone_length: 122.4030 domain_loss: 0.0000 , lr: 0.0001, time: 39.56s

Did I do someting wrong or miss anything? It would be help a lot if you could help me figure it out!
Best wishes

Hi,
Thank you for your interest! As a reference, here is the training log by running the self-supervised option. Each loss term, except bone_length and uv_hm_mean are much higher than my run.


General quality of android+iBeacons bundle

I have the one and only question: why is it so bad?
We got out Estimote beacons finally and it's quite a disappointment: our iPhone gets beacons pretty fast (approx. from 1 to 7 seconds it takes to find all that are currently in range), while android (I'm talking about that Estimote applications of yours - iOS and Android) usually takes 10-15 seconds to find at least one of them (we're taking the distance same as for iOS ± 1m).
Sometimes it can not find a thing for a minute, sometimes it finds one but in a second it disappears...
Am I the only one experiencing such behaviour?
Are there possible reasons for that (EstimoteSDK for android is not a final and of low quality/BluetoothAdapter from AndroidSDK is bad and buggy/Hardware of android devices is low-quality/other reasons)?
We used Nexus4 (API 21) and iPhone 5C (some 8.x iOS) for these tests?
Please respond - because it's important: we've planned iBeacons to be killer-feature for our shopping app (there's none or just several of those in our region so far) and now it turns to a huge headache.
P. S.: please don't treat this as an unsatisfied customer's angry letter :)
I'm just trying to investigate the reasons and possible workarounds - to give some feedback for project owner so they could decide whether we keep up with iBeacons idea or drop it.

It is mainly due to Nexus 4 (search for "nexus 4 bluetooth problem"). It has hardware problems because of the way Bluetooth and WiFi share antenna. Disabling WiFi helps which is a bummer. Other devices are much better.
Note that Android has bugs in BLE support:
https://code.google.com/p/android/issues/detail?id=67272
http://stackoverflow.com/questions/22048721/bluetooth-share-has-stopped-working-when-performing-lescan
http://stackoverflow.com/questions/22476951/bluetooth-share-has-stopped-alert-when-detecting-ibeacons-on-android
Please reopen if you have further questions.

Me again. I wonder - have you faced similar problems (like Nex4 has) with some other Android devices?
I mean some widely-used vendors and models like Samsungs or HTC's (leaving different Chinese 'no-name' devices and similar out of scope)...
Maybe you would even want to add such info to repo readme - to prevent possible future threads like this.

This has been a concern for me as well. Like sometimes the time taken by the Estimotes to get detected is way too long whereas the iPhone seems to detect them pretty fast every time. I have tried the tests on a Nexus 5 & Oneplus One.

Samsung, HTC, Moto, Nexus devices are very good (with exception of Nexus 4).
Bluetooth stack on Android can causes delays especially when there are lots of Bluetooth devices around (more than 50). Hiccups can occur (as @adnan-SM) described and we are aware of those. Trying our best to overcome this problem.


[STREAMING][DOCS][EXAMPLES] Minor fixes

Can one of the admins verify this patch?

Test build #2333 has started for PR 10603 at commit 07cdc9e.

Test build #2333 has finished for PR 10603 at commit 07cdc9e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Other than that one line, rest LGTM.

Test build #2344 has started for PR 10603 at commit 7f215fc.

Test build #2344 has finished for PR 10603 at commit 7f215fc.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

I've merged this.


editing stores in web ui do not set the previous state of checkboxes

.e.g if skip ssl validation was set and you edit in the web UI, the skip ssl validation checkbox is not set already.

This should be fixed in the 8.1.0 release, which should be out the door by next week (just in time for CF Summit Philly!)

Fixed in v8.1.0 (https://github.com/starkandwayne/shield/releases/tag/v8.1.0)


Error sending DALI message: Send timeout

When we boot our system, at first everything works fine.
However after not sending any commands to DALI at night, when we start sending them again the next day, we see this in the logs :
Sep 14 18:59:33 dex daliserver: Error sending DALI message: Send timeout
Restarting daliserver doesn't help. Only restarting the machine works.
Any ideas ?

I remember having some problems with daliserver running in a KVM virtual machine.
After running for a long time, the USB adapter would suddenly drop off the bus and not come back.
But that was a bug in KVM's USB passthrough code and I haven't seen it since the last OS update.
Can you run lsusb after these errors appear and see if this isn't a similar issue?
Does disconnecting and reconnecting the adapter help?

We're not running it in KVM. It's running on a Raspberry Pi 3 with Raspbian.
lsusb produces this output when the problem occurs :
Bus 001 Device 004: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
So I'm guessing it's still ok ? But it doesn't respond anymore.

Small update. When I do this :
echo 0 > /sys/bus/usb/devices/1-1.4/authorized
echo 1 > /sys/bus/usb/devices/1-1.4/authorized
It works again right away.

Well strike that, I guess it was a fluke. Still doesn't work.

Bus 001 Device 004: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR

I'm positive this is not the DALIUSB adapter.
Looks like it vanishes from the bus and doesn't come back without a reboot.
Can you make sure it's not a hardware problem?
For example, try connecting the adapter to a powered USB hub, and see if dmesg reports anything.
Also, please test it on a different host. Perhaps the adapter is defective.

The complete list (when operational) is :
pi@dex:~ $ lsusb
Bus 001 Device 006: ID 17b5:0020
Bus 001 Device 005: ID 04d9:a01c Holtek Semiconductor, Inc.
Bus 001 Device 004: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@dex:~ $
So I'm thinking it's the one that says 'mySmartUSB light'... nothing else is plugged in that has to do with lights.

I'll try to plug it in through a USB hub on Monday. It's at our office and it's weekend now ;-)

That's not it.
The DALIUSB adapter is the device with vendor ID 17b5 and product ID 0020. The one that doesn't have a description.


format y axis values using toFixed(2) breaks the chart

I want to format the values of the y axis on the multiBarChart.
I have used
y: function (d) {
return (Math.round(d.value*100)/100).toFixed(2);
},
Of course using toFixed() converts the value to a string and this seems to break the chart. It will display the value but the bars on the chart display at the same level.

As you can see, the values have been formatted to two decimals places. But the chart displays the bars only to the height of the lower value(55).
Any help with getting this to work would be greatly appreciated.

Hello @sarahmorley , Is this what you are trying to achieve?


change for local testing

closing this since already stale for some time, please raise another one if still needed


Fix type creation failure issue

Purpose
Sending the fix https://github.com/ballerina-platform/ballerina-lang/pull/18985 to the patch release branch

Codecov Report

Merging #19094 into ballerina-1.0.x will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff                @@
##           ballerina-1.0.x   #19094   +/-   ##
================================================
  Coverage            15.73%   15.73%
================================================
  Files                   47       47
  Lines                 1265     1265
  Branches               197      197
================================================
  Hits                   199      199
  Misses                1053     1053
  Partials                13       13

Continue to review full report at Codecov.

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


Connection count badge on Activity Bar doesn't clear upon disconnect

Type: Bug

Connect to a server and observe a (1) badge appear on the Activity Bar icon.
Disconnect. :bug: The badge remains.

Extension version: 0.28.3
VS Code version: Code 1.88.1 (e170252f762678dec6ca2cc69aba1570769a5d39, 2024-04-10T17:41:02.734Z)
OS version: Windows_NT x64 10.0.22631
Modes:
Remote OS version: Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

https://github.com/microsoft/vscode/issues/210640

Now fixed in 1.89 Insiders, which will become Stable in early May.


Something seems broken, not sure what

Hi, seems like something is breaking. Might be my lavalink. I have no idea.
Error
It happens immediately upon starting the process.
error: Uncaught (in promise) TypeError: Cannot convert undefined to a BigInt
                const player = this.node.players.get(BigInt(payload.guildId));
                                                     ^
    at BigInt (<anonymous>)
    at Connection._onmessage (https://deno.land/x/lavadeno@3.3.0/src/connection.ts:242:54)
    at Connection._onopen (https://deno.land/x/lavadeno@3.3.0/src/connection.ts:217:24)

Minimal repro code
import { Cluster } from<EMAIL_ADDRESS>
const cluster = new Cluster({
  nodes: [
    {
      id: "main",
      host: "host.docker.internal",
      password: "lavalink",
      port: 2333,
      secure: false,
    },
  ],
  sendGatewayPayload: (id, payload) => console.log("Send to discord", id, payload),
});

await cluster.init(870267613635309618n); // This is the id from your README. I am using the id of my own bot.

Using lavalink via this docker image: fredboat/lavalink:latest.

Deno version
deno 1.31.0 (release, x86_64-unknown-linux-gnu)
v8 <IP_ADDRESS>
typescript 4.9.4

Lavalink logs, they do not really seem helpful though
lavalink-lavalink-1  | 2023-03-04T18:15:59.621035300Z 2023-03-04 18:15:59.620  INFO 1 --- [  XNIO-1 task-1] l.server.io.HandshakeInterceptorImpl     : Incoming connection from /<IP_ADDRESS>:60438
lavalink-lavalink-1  | 2023-03-04T18:15:59.624255900Z 2023-03-04 18:15:59.623  INFO 1 --- [  XNIO-1 task-1] lavalink.server.io.SocketServer          : Connection successfully established from lavadeno (https://github.com/lavaclient/lavadeno, Deno v1.31.0)
lavalink-lavalink-1  | 2023-03-04T18:15:59.630129400Z 2023-03-04 18:15:59.629  INFO 1 --- [   XNIO-1 I/O-2] lavalink.server.io.SocketServer          : Connection closed from /<IP_ADDRESS>:60438 -- CloseStatus[code=1006, reason=]
lavalink-lavalink-1  | 2023-03-04T18:15:59.630242300Z 2023-03-04 18:15:59.630  INFO 1 --- [   XNIO-1 I/O-2] lavalink.server.io.SocketContext         : Shutting down 0 playing players.

Any idea if I am doing something wrong? :)
Thanks

It is crashing on this op.
{
  data: '{"resumed":false,"sessionId":"censored","op":"ready"}',
  type: "message"
}

I forgot to add the closing action thing, but that commit should fix this :)


Add VK_EXT_shader_object sample

This PR adds a new sample named shader_object which demonstrates common use cases of the VK_EXT_shader_object extension:

Linked graphics shaders
Unlinked graphics shaders
Passthrough geometry shaders
Arbitrarily changing state
Arbitrarily changing render target formats
Interoperability with pipelines
Emulation layer integration

The PR also updates the "vulkan" submodule to the sdk-<IP_ADDRESS> tag, which is required for VK_EXT_shader_object support in the Vulkan headers.

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

Hey @daniel-story, I have updated the copyright check to work with Copyright YYYY. The test now fails on a json file
If you add .json to https://github.com/KhronosGroup/Vulkan-Samples/blob/main/.copyrightignore this should resolve this issue. Feel free to ping me if you need any further help with this check :)

I tried to test this, as agreed at the samples meeting. Unfortunately, the sample uses geometry shaders, which we don't currently support, so I can't actually test it I'm afraid.

Thank you for the review, and for pointing out the resizing bug. Both comments should be addressed now, along with a few minor grammar and clarity edits to the documentation.

@marty-johnson59 : Can we merge as per what we discussed in the last call?
@asuessenbach: We can copy your comments over to a new issue then and see how and who fixes them.

This will require some additional work beyond the scope of this PR.  MoltenVK currently doesn't have support for this extension and the sample crashes on account of it.  Resizing windows also seems to be a problem but that likely can be better fixed elsewhere.
Thanks for the heroic effort in getting us this sample Daniel!   I'm approving this PR as is.

I made a suggested PR targeting your PR with suggested fixes.  With the suggested fixes, Linux Windows and Android seem to work.  I also fixed 3 validation layer issues on sample destruction.  Please consider my suggested edits as public domain, accept or reject as necessary.  Please note, I didn't bother with checking if the copyright years are updated or if the style requirements will be accepted by CI.  Let me know if that would be helpful.


The return type of waitForSelector is Promise<ElementHandle | null> even when hidden is false

With the new built-in TypeScript definitions, the type of the waitForSelector method is
waitForSelector(selector: string, options?: WaitForSelectorOptions): Promise<ElementHandle | null>;

which means that the type of the returned value is Promise<ElementHandle | null>. But according to the documentation, if the hidden option is set to false (which is the default), then waitForSelector is always going to return a non-null value (or throw an exception). By unconditionally including null in the return type, users have to either perform a check for nullness at runtime, or use a type assertion which reduces type safety. Both solutions are not ideal.

Relevant @types/puppeteer type definitions: https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/puppeteer/v3/index.d.ts#L1265-L1272

Bump.

This should be fixed with #7942

Based on @jespertheend's PR, this type signature is not something we'd like to support. In particular, someone could manually write true and since hidden can be undefined, the return type would be lying to the developer. And even if we fixed this, the type signature would almost never be used since an options object will generally genericize the boolean attribute of hidden, so when passed into the function, it would go back to using boolean. Unless the options object manually types true for the hidden attribute, this type is meaningless.

@jrandolf-zz
I want to revisit this issue.
You closed @jespertheend's PR (#7942) because they used generics to solve the problem. I agree with you, in that generics can sometimes be unreliable and awkward to use, but what about implementing an overload instead?
Here's an example from DefinitelyTyped's Puppeteer definitions:
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/puppeteer/index.d.ts#L1341-L1342
If you or the team will allow this type of change, I'll write the PR to implement it on all the relevant waitFor... methods.
Just looking for the "okay" before wasting time.


Adjust indexing parallelism (DB connection pool size, indexing queue count)

The DB connection pool size was too small, it failed in staging :x

I think it didn't fail when I tested locally because indexing ended before we reached the DB connection acquisition timeout. But my laptop is more powerful than the VMs on staging/prod, so it's slower there.


[AutoRelease] t2-policyinsights-2022-10-07-66471(Do not merge)

https://github.com/Azure/sdk-release-request/issues/3245
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=1018

issue link:https://github.com/Azure/sdk-release-request/issues/3245

/check-enforcer override


Wrong result for \\ in the label in the dot file

I used joern to parse the code in the  attachment，but the plotDotPdg didn't work.I found the reason was that the code "{\\"  became \"{\\\\" in the label in the dot string,missing a \.Could you please fix the problem?
void test()
{
printf("{\\");
}

This should work now since the latest joern release. Please try again after updating.

ok,thanks


Extremely Slow Startup

It takes it well over a minute to start up on my database - I suspect it is due to the inefficiency of iterating over all the tables and then issuing separate selects to pull in column names. (I am seeing boatloads of queries like SELECT column_name FROM information_schema.columns WHERE\n    table_name ='')
Would likely be faster to do a single select table_name, column_name from information_schema.columns.

That's an awesome idea. Thanks for the suggestion. I'll add that to the next ver.


documentation of apply: mention how $_ is used in BLOCK

Hi,
I'd like to propose this change of documentation of apply function that I think improves two points:

$_ is used in BLOCK
The returned list is a list of new $_ but not a list of return values of BLOCK

The current documentation requires users to learn the conventional $_ variable, but IMHO it'd be much friendly to new comers to mention $_ in here, just like it is in the documentation of map.
Also, for users who are familiar with map, there are 2 differences but not just 1. map gathers the return values BLOCK while apply gathers the updated value of $_ . It would also be nice to mentioned such behaviour expliictly instead of letting users to deduct from the example code.

Since the lack of response, I'm just  closing this PR.


Visualstudio is released to Linux clusters

My Service Fabric environment is a local Linux cluster, using Visual studio to build a serviceless Web API project, which is published directly to the Linux cluster via VS
Error event: SourceId='System.Hosting', Property='CodePackageActivation:Code:EntryPoint'.
There was an error during CodePackage activation.The service host terminated with exit code:6

My code was developed in a Windows environment, how do I deploy to the Service Fabric cluster in Linux？


Attempts to fix an issue where mouse input under PuTTy is not recognized

tcell.Screen exposes an EnableMouse with the option to specify which type of mouse events to capture (click, drag, all).  Unfortunately putty doesn't currently support "all", which is the default, so we need to specify either click or drag.
This problem is further compounded by tview.Application not exposing the underlying Screen directly.  It does however use a Screen if we provide it; allowing us to create one, configure the mouse, and then use it.  We don't call Application.EnableMouse because that will override the setting we've used.
This is probably going to cause a conflict in the README.md of #79, but I'll clean it up after this or that is merged).
Fixes #77

thanks


cannot use pre-generated interface dll

While looking for a workaround for the admin rights issue (#40 ), I found that I could NOT generate a dll as an admin_user within one checkout of matlabneuroninterface, then move that dll to another checkout, and use it there as non-admin user.
This needs a little more investigation to be sure, but it would mean that we cannot provide a pre-generated dll, which was considered to be an option once matlabneuroninterface is stable enough. Which in turn would mean that users will run into #40 then still.

Do need to check again, to make sure the two checkouts were indeed using the same underlying matlabneuroninterface source code etc.


removal of xmltodict import and others

xmltodict was not installed by default and as a consequence it made the config flow fail in my env. As the library was not used, I removed it and took the opportunity to clean up some other unused imports

Thanks for the feedback and enhancements !


Hello, I would like to ask how to use the final 'feature_importance' value inside the 'federatedscope.vertical_fl.tree_based_models.trainer.feature_order_protected_trainer.py' file?

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Hello, sorry for the late response.
The values in feature_importance evaluate the relative importance of each feature in the model's predictions. By analyzing feature importance, clients can identify which features contribute the most to the model's predictive ability. This information can be used for feature selection or dimensionality reduction to simplify the model and improve performance.


luci-app-statistics: nut: Voltage graph split into AC/DC, cosmetic change to battery/load and temperature graphs

The big difference between AC and DC voltage is masking changes in Input/Output voltages over time. This patch splits the graphs into 2 graphs like in apcups. This makes it possible to see variations in AC Input/Output voltages.
Battery charge and load are indepentent variables, this patch change overlays them and display them as simply two lines.
Battery temperature is also displayed as a line now, as an area under a temperature line makes no sense.
Removed some empty lines.
Signed-off-by: Fabian Schmid-Michels<EMAIL_ADDRESS>

Looks interested, I'll try it soonish and see how my UPS fares with the changes.

Hi! Not to annoy anyone, but I put a lot of effort into my first pull request and its a bit sad that nothing happened here for 2 months.

Hi! Not to annoy anyone, but I put a lot of effort into my first pull request and its a bit sad that nothing happened here for 2 months.

Inform the package maitainer with an '@' to ping him

Hi! Not to annoy anyone, but I put a lot of effort into my first pull request and its a bit sad that nothing happened here for 2 months.

Inform the package maitainer with an '@' to ping him

There is no mainatainer mentioned in the makefile...

I'm also waiting for feedback, because I've also mad some changes in luci-app-statistics.
Maybe @hnyman could help us there :-)

@jow I could not test this because I do not have an environment to verify this. But the code LGTM.
So I think we could merge this and give them a try.
@JamesT42 for the future split this pull request in more then one commit. Maybe

whitespace fixes
AC/DC change
area to line changes

But this is only I would prefer to see the changes.

@JamesT42 ping please fix the whitespace issues.  Use tab instead of whitespace.

@JamesT42 ping please fix the whitespace issues. Use tab instead of whitespace.

Since I have no idea how to do that it will take me more time than I have currently available so I will do it when I have the time to read through tutorials.

@JamesT42 I have update the requested changes from my side thanks for you contribution :-)

Thank you! I just did not have the time to learn how to update a commit etc.

No problem
https://github.com/edx/edx-platform/wiki/How-to-Rebase-a-Pull-Request
maybe this helps ;-)


config: Add a check if custom param name is empty

Until this commit, it was possible to receive an empty string as a valid custom parameter name.
Add a check if a custom parameter name is empty, and fail if it is.
Signed-off-by: Orel Misan<EMAIL_ADDRESS>

Change: Edited commit message.

Change: Added emptyParamName constant to make the test more explicit.


Add last_message_timestamp support

Add last_message_timestamp support for one to one and group conversations.
Close #264

Thanks for the PR.

I'm sorry about being late on this, I've been sick for the last week.


Record deleting is not queue-able

I'm trying to use soft delete feature and have configured scout to queue tasks.
Adding and updating ($model->save() and $model->update()) models are being queued without any problem but when I try to soft delete ($model->delete() using Illuminate\Database\Eloquent\SoftDeletestrait) a model, it's not being queued.
Because of the issue, if for any reason elasticsearch service get disabled, it'll throw Elasticsearch\Common\Exceptions\NoNodesAvailableException exception (which is reasonable, only if not being queued) upon calling delete method.
Note that record is being deleted, it's just throwing the exception after database transaction but still a problem; we need to queue elasticsearch record deleting tasks.
I should emphsize that no exception is thrown by calling save() or update() methods; problem is only with delete() method.

scout does not have that. There is a recent ticket about it and it should be added soon as it is work in progress. (https://github.com/laravel/scout/issues/331)

Great! please keep this issue updated.


More Robust User Registration Checks

Right now we just check for matching email, but we should probably have more robust soft-matching checks. Right now both Claire and I have duplicate users in the database because we ended up using different emails when we registered.

@NoisyFlowers
As an addition to this, should we add support for multiple emails per person node?
Should we separate out account/user tracking to a totally separate node type that get attached to a person node?

@aazaff @NoisyFlowers Should this be addressed before we get formal new registered users at HackAThon? That way if they change their mind and try to mess things up after the HackAThon, we don't have to clean it up. Maybe even something like search for similar user names, tell user similar names exist...Are any of these you? Then they can go back and log into their existing account? I was hoping maybe there was "canned" code for something like this, but probably wishful thinking.

I believe this is done and can be closed?


Protolathes/Circuit Imprinters have duplicate entries

Description

Each time someone pushes sync in the UI, and there has been tech researched that's applicable to that machine, it adds all of the previous researched entries again. Resulting in quite a few duplicates over time. I would assume sec techfab is also affected.
Reproduction

Research new circuit/protolathe tech, sync. Rinse, repeat.
Screenshots

Additional context

fixed a minute ago with #17473


Update LogicalType enum and EmbeddingDataType enum

What problem does this PR solve?
update LogicalType enum
update EmbeddingDataType enum
Type of change

[x] Refactoring

LGTM


Update configure-spring-boot-starter-java-app-with-cosmos-db.md

I just went through this tutorial. Very easy to follow and many thanks. Found a typo (the missing semi-colon and added a suggestion in the application.properties section)

Docs Build status updates of commit ef30637:
:clock10: Full build: the average full build time is 72 min(s) 24 sec(s), this is based on the last 337 build(s) for this repository.

Docs Build status updates of commit ef30637:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/spring-framework/configure-spring-boot-starter-java-app-with-cosmos-db.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Update sqlclient-driver-support-lifecycle.md

Update with latest releases

@David-Engel
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@ErikEJ - Can you respond to the requested changes or let us know if you would like us to commit them?
@ David-Engel - When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

Please commit them.


fix: normal user can access workspace upgrade page

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/47904
PROPOSAL: https://github.com/Expensify/App/issues/47904#issuecomment-2306837701
Tests

As a COLLECT workspace's NORMAL user (neither admin nor auditor), go to workspace settings page
Go to workspace upgrade page by adding /upgrade/report-fields to the URL (eg., /settings/workspaces/:workspaceID/upgrade/report-fields)
Verify not found page shows

[x] Verify that no errors appear in the JS console

Offline tests

NA
QA Steps

Same as Tests

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

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

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

https://github.com/user-attachments/assets/2bcc76c4-37dd-43ec-8263-bb7f3c1ef387

iOS: Native

iOS: mWeb Safari

https://github.com/user-attachments/assets/f98d3fe2-3cfd-414e-857d-e6084e85db40

MacOS: Chrome / Safari

MacOS: Desktop

Updated!

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/tgolen in version: 9.0.27-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/roryabraham in version: 9.0.27-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


=AJ instead =PY

In my excel, is not appearing the function =PY, instead of that, to use de py function I need type =AJ function.
My excel is on brazillian portuguese version and I'm using the 365 beta insider.
Is it a wrong translation for the Portuguese versions or is there a way to fix it to use "=py" instead of "=aj"?

Hi there, this is known issue we have with an incorrect localization in Portuguese. Can you please share the Excel version number under File > Account?

Internal bug #8265741

@keyur32 , sure, here:
"Microsoft® Excel® para Microsoft 365 MSO (Versão 2310 Build 16.0.16907.20000) 64 bits "

Hi, it appears is still active. We're still investigating.

Hi folks, this should be fixed in version 17106. Please let us know if this is still happening.

It's still happening...

Hi folks, can you let us know if you are still seeing this happening even with the latest version of the beta?

Still happening  :(

What version are you seeing this under?

[image: image.png]
On Fri, Mar 15, 2024 at 1:45 AM Keyur Patel - MSFT @.***>
wrote:

What version are you seeing this under?
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/python-in-excel/issues/31#issuecomment-1998927770,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJIDULT3K4MKRFPZ4OLUA53YYJ4FVAVCNFSM6AAAAAA4WRBH72VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJYHEZDONZXGA
.
You are receiving this because you commented.Message ID:
@.***>

Hey there, the image didn’t seem to come through. Can you please try again? Thanks

The image shows: Version 2301 (build 16026-20200).
On Sun, Mar 17, 2024, 15:17 Sergio Ricardo de Freitas Oliveira <
@.***> wrote:

[image: image.png]
On Fri, Mar 15, 2024 at 1:45 AM Keyur Patel - MSFT <
@.***> wrote:

What version are you seeing this under?
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/python-in-excel/issues/31#issuecomment-1998927770,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJIDULT3K4MKRFPZ4OLUA53YYJ4FVAVCNFSM6AAAAAA4WRBH72VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJYHEZDONZXGA
.
You are receiving this because you commented.Message ID:
@.***>

Believe this was already addressed. Please let me know if it is not the case.