slow, but possibly due to errors in compiling??

Hi,
I just tried to switch to zgenom from zgen because I was trying to hunt down slow shell startups.
Slow here means >1.1s. Reading many other people's comments, I was under the impression to be able to get it down to about 0.5s which would be fine for me.
So I tried the migration and so on also did a zgenom reset and there I was presented with the following errors:
zgenom reset
-- zgenom: Deleting `/Users/myuserid/.zgenom/sources/init.zsh` ...

zsh
-- zgenom: Creating `/Users/myuserid/.zgenom/sources/init.zsh` ...
-- zgenom: Initializing completions ...
-- zgenom: Compiling files ...
zgen-save:89: parse error: condition expected: /Users/myuserid/.zcompdump
zgen-save:89: parse error: condition expected: /Users/myuserid/.zcompdump-mylaptop-5.8
zgen-save:89: parse error: condition expected: /Users/myuserid/.zcompdump-mylaptop-5.8.zwc
-zgen-compile:1: parse error near `)'
-zgen-compile:zcompile:3: can't read file: /Users/myuserid/.zcompdump-mylaptop-5.8.zwc
zgen-save:89: parse error: condition expected: /Users/myuserid/.zcompdump.zwc
-zgen-compile:1: parse error near `)'
-zgen-compile:zcompile:3: can't read file: /Users/myuserid/.zcompdump.zwc
-- zgenom: Creating `/Users/myuserid/.zgenom/sources/init.zsh` ...
-- zgenom: Initializing completions ...
-- zgenom: Compiling files ...
zgen-save:89: parse error: condition expected: /Users/myuserid/.zcompdump
zgen-save:89: parse error: condition expected: /Users/myuserid/.zcompdump-mylaptop-5.8
zgen-save:89: parse error: condition expected: /Users/myuserid/.zcompdump-mylaptop.zwc
-zgen-compile:1: parse error near `)'
-zgen-compile:zcompile:3: can't read file: /Users/myuserid/.zcompdump-mylaptop-5.8.zwc
zgen-save:89: parse error: condition expected: /Users/myuserid/.zcompdump.zwc
-zgen-compile:1: parse error near `)'
-zgen-compile:zcompile:3: can't read file: /Users/myuserid/.zcompdump.zwc

I don't know enough about this compiling step, but could that mean that compiling actually fails and therefore my startup times remain high?
And if so - do you have an idea on how to hunt down the actual problem?

Hi @svenXY
I found an issue that might have affected you. Could you please checkout the branch Fix-compiling-HOME-.zcompdump and try again?

As for the slowness.
zgen-init is very fast by itself as it just source $ZGEN_INIT. (Plus checking if the file exists).
When this takes longer it is due to the plugins sourced in this script.
If you want to investigate this further you can do vim $ZGEN_INIT.
Then find the section # ### General modules and comment out some of the source statements and profile again.

I just played a bit with your config:
On my machine commenting out any source statement results in ~10ms of runtime of zgen-init.
Just running zgenom ohmyzsh adds about 110ms to the load time.
Of course the config doesn't work without zgenom ohmyzsh but it adds a lot of startup penalty.
You can reduce the penalty to 90ms by setting DISABLE_AUTO_UPDATE=true before you start zgenom.
The other plugins add about 10ms of startup time each when sourced, which results in about 360ms.
Some other plugins add even more startup time by adding hooks which run before the first prompt as well.
For example _alias_tips__preexec (djui/alias-tips) added about 55ms to the startup time.
If you want your prompt mainly to feel snappy have a look at powerlevel10k which is able to render the prompt before every plugin is fully loaded.
Unfortunately there isn't much zgenom can do if a plugin takes some time to load it will take this time.
The main reason why zgen[om] is considered fast is because it doesn't have to execute (much) code to source your plugins. Some other plugin manager calculate which/how to source plugins on every start of a new shell. This has some advantages since they can conditionally load plugins.

thank you very much for your detailed support, that helped a lot. I was able to bring startup time down to 0.84 seconds which feels good enough for me now (especially compared to almost 2 secs before...).
I also understood a lot more about zsh startup and how to profile it.
In my .zshrc, there is also the following code:
# Make it easy to append your own customizations that override the above by
# loading all files from the ~/.zshrc.d directory
mkdir -p ~/.zshrc.d
if [ -n "$(/bin/ls ~/.zshrc.d)" ]; then
  for dotfile in ~/.zshrc.d/*.zsh
  do
    if [ -r "${dotfile}" ]; then
      # uncomment for  profiling script sourcing
      # echo $(gdate "+%S.%4N") sourcing $dotfile
      source $dotfile
    fi
  done
fi

where I source some files for my own aliases, functions etc. There was e.g. pyenv init - , which eats about 0.6s and can either be improved with pyenv init - --no-rehash or even better by lazy-loading it (erikced/zsh-pyenv-lazy-load).
Uncommenting the echo in the snippet helped me a lot to identify where most time was consumed.
Thanks again, closing!
Sven

Ah, forgot something:
Your patch removed the problem with compinit, but there is another one that happens when using the zsh-syntax-highlighting:
- zgenom: Compiling files ...
-zgen-compile:33: defining function based on alias `ls'
-zgen-compile:33: parse error near `()'
-zgen-compile:zcompile:3: can't read file: /Users/Sven/.zgenom/sources/zsh-users/zsh-syntax-highlighting-___/highlighters/main/test-data/function.zsh
-zgen-compile:33: defining function based on alias `ls'
-zgen-compile:33: parse error near `()'
-zgen-compile:zcompile:3: can't read file: /Users/Sven/.zgenom/sources/zsh-users/zsh-syntax-highlighting-___/highlighters/main/test-data/function.zsh
-- zgenom: Creating `/Users/Sven/.zgenom/sources/init.zsh` ...
-- zgenom: Initializing completions ...
-- zgenom: Compiling files ...
-zgen-compile:33: defining function based on alias `ls'
-zgen-compile:33: parse error near `()'
-zgen-compile:zcompile:3: can't read file: /Users/Sven/.zgenom/sources/zsh-users/zsh-syntax-highlighting-___/highlighters/main/test-data/function.zsh
-zgen-compile:33: defining function based on alias `ls'
-zgen-compile:33: parse error near `()'
-zgen-compile:zcompile:3: can't read file: /Users/Sven/.zgenom/sources/zsh-users/zsh-syntax-highlighting-___/highlighters/main/test-data/function.zsh

Any idea? And why 3 times?
Thanks again

It's generally not advisable to call executables in your .zshrc as it will slow execution down.
I use rbenv which is quite similar to pynenv and use it like this:
if ! zgenom saved; then
        # ...
	rbenv init - > path/rbenv.zsh
fi
source path/rbenv.zsh

So whenever I run zgenom reset rbenv will reinit itself. Otherwise a "cached" version is used.

From what I've seen so far zsh cannot compile files which overwrite builtin commands.
The file you mention is a test file so it shouldn't be an issue. I could silence the errors produced while compiling but this would also silence correct errors (like the one you reported).
I'll see if I can find a good solution.

I'm not really sure why it happens four times. Especially weird is that it happens before creating init.zsh.

Because the default steps are:

Create init.zsh
Initialize completions
Compiling files
And you have the compiling step twice and then two errors each time.

@svenXY I found the issue why the file generates two errors when compiling.
Still not sure why you see the compile step twice 🤔

oops, found it myself:
I had
# if the init script doesn't exist
if ! zgenom saved; then

  # specify plugins here
  source $HOME/.zgenom-plugins

  # generate the init script from plugins above
  zgenom save
fi
# end zgenom

and in .zgenom-plugins, as last line, I had another zgenom save.
Sorry, that was my mistake. No more wondering necessary on your site ;-)

Awesome 👏
I'll add another PR and then both issues should be fixed.
Still not sure why compiling the one file doesn't work.
I'll see what I can do 👍

I found out why the issue with ~/.zgenom/sources/zsh-users/zsh-syntax-highlighting-___/highlighters/main/test-data/function.zsh occurs.
You (or one of your plugins) probably define an alias ls before the compiling does happen.
Since compiling runs on zgenom save it runs after each plugin is sourced.
I think I can fix this by using a sub-shell 👍


🐛 Fix NPE checking is ready on FTP on OCP

sorry, my bad cry

I don't think so, the FTP service has already the issue, I just aligned the SFTP one

I introduced the NPE in https://github.com/tnb-software/TNB/pull/455 :grin:
previously there was only
        return ResourceFunctions.areExactlyNPodsReady(1)
            .apply(OpenshiftClient.get().getLabeledPods(OpenshiftConfiguration.openshiftDeploymentLabel(), name()))
            && OpenshiftClient.get().getLogs(OpenshiftClient.get().getAnyPod(OpenshiftConfiguration.openshiftDeploymentLabel(), name()))
            .contains("FtpServer started");


allow 'late' attributes in declaration section

AFAICT, there's no reason at all why a late field must be declared in the initializer section of a class body. So in determining the extent of the initializer, we should ignore late fields. This potentially makes Ceylon's rather heavy-handed initialization checking a fair bit more manageable!

Pfff. In fact this is already what the spec says and what the typechecker does. Closing.

I have now completely relaxed checking of uninitialized late attributes, which makes things even more flexible.


unable to create temporary repository path: exec: WaitDelay expired before I/O complete

Seen this multiple times now...
unable to create temporary repository path: exec: WaitDelay expired before I/O complete

Hmmm, I run the commands in docker with screen right one after another, maybe I should have waited a little bit longer after each run.
Anyway I guess it is better if we are able to fix this within the code.

i saw this a long time ago without docker as well... :thinking:

This should already be fixed with #260 where we move to docker-volumes and #273 where we add a number to the result-directory to make it unique.


libgnurx: output libgnurx.a when static

Motivation for this change
When building statically, file looks for libgnurx.a, but we only output libgnurx.dll.a and libregex.a. I arbitrarily chose to link libgnurx.dll.a to libgnurx.a and it seems to have worked. I didn't try it with libregex.a
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] 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 nixpkgs-review --run "nixpkgs-review wip"
[ ] 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)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Oh, I should mention in order to build file statically for windows, one also needs https://github.com/NixOS/nixpkgs/pull/121032


Mypy Syntax Error Python 3.8

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
The issue is explained in https://github.com/python/mypy/issues/17768, but the author closed the issue with no indication it had been resolved or even reported.
Error Message: error: X | Y syntax for unions requires Python 3.10
Example Code
See related issue

Python, Pydantic & OS Version
OS: Ubuntu 20.04
Python: 3.8.10 (Version that ships with Ubuntu 20.04)
Pydantic: 2.9.2

Well the error message is pretty clear? You are on Python 3.8, and this syntax was introduced in 3.10.
Pydantic will still be able to evaluate such expressions thanks to the eval_type_backport package, which needs to be manually installed.


Integrate Font-Awesome library and update icons used in rewrite version

Currently, each profile page has an SVG icon that we use to represent each entity.
As there will be other icons that we will want to use (e.g. on the homepage), it was suggested that we instead make use of Font Awesome's official React component and the 1500+ free icons.
Can we please integrate Font Awesome into the React rewrite version using their component? If, however, there is a better, more maintained component library, please feel free to use it.
Once integrated, can we replace the following SVG icons with the free solid icons from Font Awesome?

Entity
Icon
Icon link

target
dna
https://fontawesome.com/icons/dna?style=solid

disease
stethoscope
https://fontawesome.com/icons/stethoscope?style=solid

drug
prescription-bottle-alt
https://fontawesome.com/icons/prescription-bottle-alt?style=solid

Ticket moved to next sprint to account for work on updating data tables

Ticket closed as work merged into alpha

Search filters still using old icons:

Doh! Well spotted @d0choa - the icons have now been updated in the code (not yet merged).

Ticket closed as work completed and pushed to alpha branch


LuckPerms does not work on 1.7.10

Stacktrace: https://pastebin.com/YAhMTN2y
Problem: LuckPerms fails to load on 1.7.10 PaperSpigot and Spigot
Server Java version:

java version "1.8.0_60"
Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)

GroupManager and PermissionsEx both load correctly but LuckPerms does not.

Use the legacy version.
https://ci.lucko.me/job/LuckPerms/

Thanks :)


Why 'vehicle_pose' must be defined?

Sorry, I don't understant this setup.
My application scene is for warehouse that support a lot of robots(like vehicle)'s movement,does they  confict?

Is there any example that show several vechicles at the same time?

@hookex great question.  The problem was one of use-case exposure.  Originally we had a hero-vehicle or ego-vehicle and didn't operation with multi-vehicles in mind.
The good news is that we have been making changes to expand and support this use-cases in a much more general fashion.  This includes no vehicle and multiple vehicles.
Not everything is in place to make this as easy as it should be.  If you can provide more info for your use-case I can offer up some options in the meantime.
Specifically, the structure of your data relative to the vehicles.  in streetscape.gl the camera by default tracks the pose defined by /vehicle_pose.  Also, if the coordinate system is VEHICLE_RELATIVE, it is relative to the /vehicle_pose.
Is your data described in a shared/global references frame, or relative to each individual vehicle?
Do you need the camera to track vehicles?

Here's a recording of our app.
warehouse.zip
Now, our use-case use global camera to observe  overall warehouse.
Previously, we developed out application inspired by deck.gl and XVIZ, but not use these two module directly. And now, we plan use XVIZ module as our data layer. This is because data protocal and service is so import and difficlut. If XVIZ don't  support our use-case,  we will clone and modify it.
But i seem to have found way(data) to meet our use-case.
For example:
Per pose streamID path contains robotID.  I know this does not conform to the XVIZ spcification, but it is solution maybe. Each robot have one pose stream， and It just solved my problem of  drawing some signs（primary、text, etc） around it.
          "/agv/pose/274030929645667111": {
            "timestamp": 1656000,
            "map_origin": {
              "longitude": 0,
              "latitude": 0,
              "altitude": 0
            },
            "position": [
              6500,
              0,
              3500
            ],
            "orientation": [
              0,
              0,
              0
            ]
          },
          "/agv/pose/274030929645732647": {
            "timestamp": 1660000,
            "map_origin": {
              "longitude": 0,
              "latitude": 0,
              "altitude": 0
            },
            "position": [
              5500,
              0,
              3500
            ],
            "orientation": [
              0,
              0,
              0
            ]
          },

 {
            "timestamp": 1288000,
            "streams": [
              "/agv/pose/274030929646125863/velocity"
            ],
            "values": {
              "doubles": [
                0
              ]
            }
          },
          {
            "timestamp": 1292000,
            "streams": [
              "/agv/pose/274030929646191399/velocity"
            ],
            "values": {
              "doubles": [
                0
              ]
            }
          }
        ]
      }

I generated data-frame successly. but in @xviz/parser model,  only support one  PRIMARY_POSE_STREAM, I plan to change it to support POSE_STREAM_LIST.


Revert pose_cov_ops to 0.2.1 in melodic

While it seems to work, it actually tries to install files to /opt/ros/melodic/.catkin, which then causes downstream packages to fail.  Revert back to 0.2.1, which is the last known working version.  @jlblancoc FYI

Thanks, I'll take a look at it.

This was due to my "misbehavior" setting <build_type>cmake</build_type> in package.xml while trying to avoid what eventually was confirmed as a bug in catkin_pkg. Now that it's fixed, I can fix package.xml and make a new release. Sorry for the noise!


How can i fill svg after animation ?

Hey all !
My svg animation work with vivus.js but after animation is complete, how can i fill my svg ?
Thanks for reply :)

Hi,
If you're using inline SVG (:where the entire SVG is defined in your HTML) you can use the trick mentioned in the hacks.md

Thank for reply Maxwellito.
Yes but in the descriptions of Vivus.js it is written :
• All elements must have a stroke property and cannot be filled. This is because the animation only looks to progressively draw strokes and will not check for filled colours. For example: fill: "none"; stroke: "#FFF";
So where can i set the color of my path ?

Well, except here.
In this case you can keep the fill property in your SVG. The little hacks consist to make it transparent from the start, then make it appear once the animation over.

Any luck?
If you want some help, just create a jsfiddle and post the link :)

Thanks Maxwellito, it's work fine :) But finally i've use an other jQuery plugin. But i think i use this one for my personal projects :)

Ok, if you need any help join the conversation on Gitter :)


tests: socket: select: Non-blocking select can still preempted

The original test assumed that non-blocking select call would return
immediately, but actually it can be preempted by higher-priority
thread. So, we can account that it may possibly be delayed by a
scheduler quant of time (but otherwise we assume that testing
environment is light on other threads and their work, and one
quant is the most we can be delayed by).
Also, enable CONFIG_QEMU_TICKLESS_WORKAROUND. Most other
timing-related tests have this enabled, and it may affect
stability of QEMU testing too.
Fixes: #12994
Signed-off-by: Paul Sokolovsky<EMAIL_ADDRESS>

but actually it can be preempted by higher-priority
thread

BTW this is not actually what I think is happening. We're not scheduling another thread, we're just getting a timer interrupt during the call which advances the system clock by whatever granularity the timer interrupt runs at (10ms)

we're just getting a timer interrupt during the call which advances the system clock by whatever granularity the timer interrupt runs at (10ms)

Ok, now I got it. I thought I account for this using "1" (not 0) in zassert_true(tstamp <= 1, ""); I might imagine that we "long enough" scheduling quantum, to avoid scheduling overheads, but somehow it didn't occur to me that we might have "pretty low resolution" timing source too, though in retrospect it's indeed pretty obvious to tie both to the same timer interrupt.
Ok, let me update the commit message.

Ok, updated both description and the test itself, to use <= FUZZ instead of magic <= 1+ FUZZ, hope it won't start to fail again due to that ;-). Also did the same for tests/net/socket/poll, which used exactly the same code patterns.
And I guess we should explicitly document that k_uptime_get/k_uptime_get_32 even though returns time in milliseconds, doesn't have to have millisecond resolution.


[IOS] on pusher swift 8.0, the users are duplicating

Steps to reproduce
Turn on-and-off wifi on an iOS device with ios 14 or 15, and disconnect-and-recconect multiple times on a presence channel.
Expected behavior
The PusherPresenceChannel.members list should not duplicate users.
Actual behavior
The PusherPresenceChannel.members is duplicating users, making users appear two or three times upon each reconnection.
Any improvements you suggest
ps.version 8.0 is relevant because its the last one that supports ios 10.

seems to be wha this dude is all about:
https://github.com/pusher/pusher-websocket-swift/pull/363/commits/215c7775d34c047b859e0b1bc93c788a537c26eb

If anyone wants, I pushed a version with the fix from https://github.com/pusher/pusher-websocket-swift/commit/215c7775d34c047b859e0b1bc93c788a537c26eb
pod 'PusherSwift', :git => 'https://github.com/mirrorlink/pusher-websocket-swift.git', :branch => '8.0.1'
(if you have a podspec)
s.dependency 'PusherSwift'
8.0.1 this is the version that god himself bestowed upon us


Skrollr error on iOS / iPad

I am facing a weird issue with skrollr and it is rendering the mobile version on iPad / iOS utterly useless... Although I am still unsure what might be causing it I am writing here because I closely followed both the classic example in my first attempt (now even slimmer markup) as well as omitting any "fixed"-values inside the skrollr-body according to your notes.
This demo isn't for the looks, if just edited the CSS to allow for a sufficient height:
http://geyersbach.com/development/ueber-geyersbach
If you compare the desktop-version with the mobile-version then you'll see that the footer is completely cut off. Either I am making a huge mistake regarding my styling or it is a genuine error with skrollr...
Of course I can disable the mobile functionality (this hack) but then again that is what skrollr is supposed to be great for – working on mobile devices :)
Thanks for looking into this!

Shouldn't the footer be inside skrollr-body?
Also did you take a look at the source of the page (which is probably auto generated). Looks weird. There's a

 before the doctype which causes all kind of weirdness like <meta> tags inside your body and an empty .

Hi Alexander,
yeah, guess the footer should be inside skrollr-body and that was at least a symptom of the problem, I doubt that

 could really have been causing the issue... Anyhow, I managed to somehow work around the footer-issue and now it is working as intended (well, more or less).
Many thanks for a great script and keep up the good work!
Cheers,
Henning


[Snyk] Security upgrade firebase from 7.24.0 to 8.0.1

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

package.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

601/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 5.6
Prototype Pollution SNYK-JS-FIREBASEUTIL-1038324
Yes
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Can't update this as it contains a breaking change. Will fix manually.


Fix incompatible method signature in VisitorServiceProvider

This commit resolves the issue with the incompatible method signature in the Webkul\Core\Providers\VisitorServiceProvider class. The boot and register methods in this class have been updated to include the void return type, ensuring compatibility with the parent class Shetabit\Visitor\Provider\VisitorServiceProvider.
Specifically, the following changes have been made:

Added void return type to the boot method: ```php public function boot(): void ....
public function register(): void

Run pint command. vendor/bin/pint

Thanks for the contribution!


[SPARK-44758][K8S] Support memory limits configurable

What changes were proposed in this pull request?
Add conf spark.kubernetes.driver.limit.memory and spark.kubernetes.executor.limit.memory to config memory limits.
Why are the changes needed?
Supporting memory limits configurable can bring some benefits. For example, use unfixed memory to use page cache, reduce disk IO of shuffle read to improve performance.
Does this PR introduce any user-facing change?
No
How was this patch tested?
UT

Do you aim to de-couple request and limit simply?

Do you aim to de-couple request and limit simply?
Yes, I wish could de-couple request and limit. Limit can be appropriately greater than request(memory + overhead), used for pagecache, and can be released.

Do you aim to de-couple request and limit simply?

Yes, I wish could de-couple request and limit. Limit can be appropriately greater than request(memory + overhead), used for pagecache, and can be released.

Could we please reopen this?


Helm101

Added intro to Helm charts, installing helm charts, deep dive to helm charts.

@collabnix This PR is now ready to merge


Make --models-to-run use names of models instead of deployments

I think we should be able to specify the deployment specifically, not just the model, since there could be more than one deployment per model, and I think we should have a default.

There's already a mechanism for this. e.g.
helm-run -r boolq:model=meta/llama-2-7b,model_deployment=together/llama-2-7b -m 5 --suite debug --models-to-run meta/llama-2-7b

The deployment selection mechanism is orthogonal to --models-to-run.

To give another example:
helm-run -r boolq:model=text -m 5 --suite debug --models-to-run meta/llama-2-7b

only runs the default deployment which is currently Together.

Sorry, I meant to write that we shouldn't have a default; I think people should be aware of which deployment they are using.  Could we add a --model-deployments-to-run flag that has the current functionality along with your change?

Sure, but can we do this in another PR? As explained earlier, deployment selection is an orthogonal concept.
I filed #2082 for this.


Error Translating to sbJSON 2.4.5 Not Supported

I've downloaded a JSON file from ScienceBase, run it through the mdTranslator, and output an mdJSON file. I successfully loaded the file into mdEditor and repaired any noted errors. Upon attempting to publish to ScienceBase I get the following 400 error:
"Error transforming to sbJson. mdJson schema version '2.4.5' is not supported. mdJson versions '2.0.0' to '2.3.2' are supported"
Is this an mdTranslator issue or an mdEditor issue? Can I output a file from mdTranslator with an older schema?
I've attached both files as a Zip
Thanks,
Joe
Pennsylvania_Watersheds_sbJSON_and_mdJSON.zip

This is a result of ScienceBase using an older version of the mdTranslator in their application stack. I believe they are in the process of updating to the latest version. @jllong-usgs do you have any info on the timeframe for this?

Thanks Josh. I'll await jllong's reply.
<EMAIL_ADDRESS>Phone:<PHONE_NUMBER>
On Wed, Mar 21, 2018 at 12:16 PM, Josh Bradley<EMAIL_ADDRESS>wrote:

This is a result of ScienceBase using an older version of the mdTranslator
in their application stack. I believe they are in the process of updating
to the latest version. @jllong-usgs https://github.com/jllong-usgs do
you have any info on the timeframe for this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/adiwg/mdTranslator/issues/188#issuecomment-375045338,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aee5xKM04hpdQLBUolryC8cIxCiHsGkRks5tgpjxgaJpZM4S0uI4
.

This can't possibly still be an issue, we're on mdJson schema version 2.8.2 and I have seen this issue when mdEditor and mdTranslator have a version mismatch with mdJson-schemas which at the moment should be fixed.


Xcode - adding it to library

Using XCode and Cmake for my project.

I am stuck on how to get json to be added to the library.
What I want to do is:
I have my codes inside work/src/ folder and have json files inside work/vendor.
Inside build I have done the cmake commands. (cmake -G Xcode ../work)
after it builds I run my code in XCode but the
#include <nlohmann/json.hpp> is not found and I get heaps of errors in the json file.
I think this occurs because I am not adding a 'Link Binary with Libraries' for XCode but it's weird how I don't have that in 'Build Phase'

Any help would be appreciated!

Okay.. I've finally added #include <nlohmann/json.hpp> and it doesn't throw an error on that but not I am getting endless errors on the actual json.hpp file

I think I'm the only one with this kind of issue but I really hope to fix this...
Any help would be appreciated thanks..

That is really strange, because we can compile and run the unit tests with Xcode. Could you try to compile the unit tests?

This looks like a too-early version of C++. What version of C++ are you compiling with? (Eg, can you copy-paste the command line that is being executed to compile this?)

FWIW: The library is tested with Xcode 6.4-10.0, see https://github.com/nlohmann/json#supported-compilers.

Apple LLVM version 9.0.0 (clang-9<IP_ADDRESS>)
Target: x86_64-apple-darwin16.7.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
I did update my mac 2 days ago with Xcode because it wouldn't update the build, also my lecturer has updated that because of the same reason.
So what I've tried is:

If I use cmake browse source just on the json-3.3.0 and compile, it generates no errors whereas if I do the browse source on my work folder and generates it, it generates heaps of errors as you can see for the second image.
I went into the 'build -> vendor -> json-3.3.0' and opened the project folder then built it, generates just hundreds of errors. Weird how this one looks the same with step 1) with no error version but still generates errors.

Maybe it's not the version of the Xcode or the c++ version, I may be missing out a step since it did generate no errors for the first step.
Cheers.

Maybe the c++ or the Xcode version.. I've tried heaps of other way but getting same error.
Tried only building using json and it thought it wouldn't generate any errors but after making a main.cpp and #include <nlohmann/json.hpp> then using json=nlohman::json it generated same errors as before.
Any suggestions for this issue?

Can you copy-paste the command line invocation used? The fact that you're getting a failure around "enable_if_t" suggests that you probably don't have C++14 turned on. Or just look in your Build Settings to see what the version of C++ you have enabled.

I used
cmake -G Xcode (filename)
Couldn't find anything to allow c++ 14 or similar to my build setting

I did find enabling c++14 but still generates same errors...

Any news on this?


General issue fixes

As suggested by #75. By default when the player dies the event drops is cleared. This can be disabled in the configuration file.

Thank you for the pr, it is looking great!
I think it would be better to loop over the drops on death events and remove all items that are QR Items instead of clearing all of them, including non-2fa-related ones.
It can be done by using the #isQRItem method in AuthHandler.
Once it's done, we can merge to master :)

I think it would be better to loop over the drops on death events and remove all items that are QR Items instead of clearing all of them, including non-2fa-related ones.
It can be done by using the #isQRItem method in AuthHandler.

Done, I used the removeIf method instead of looping over for a bit cleaner look.


UtUtils has region without name

Description
Not every UtUtils region has name.
To Reproduce
Steps to reproduce the behavior:

Open utbot project
Generate tests for org.utbot.examples.collections.QueueUsages class
Open generated org.utbot.runtime.utils.java.UtUtils file

Expected behavior
All regions have names
Actual behavior
The first region has no name
...
/**
 * This is a regular UtUtils class (without mock framework usage)
 * UtUtils class version: 2.0
 */
public final class UtUtils {
    ///region

    /**
     * This class represents the {@code type} and {@code value} of a value captured by lambda.
     * Captured values are represented as arguments of a synthetic method that lambda is compiled into,
     * hence the name of the class.
     */
    public static class CapturedArgument {
        private Class<?> type;
        private Object value;

        public CapturedArgument(Class<?> type, Object value) {
            this.type = type;
            this.value = value;
        }
    }
    ///endregion
...

Additional context
That seems quite old issue, not related to recent changes.

@EgorkaKulikov I could help with the review


[PDI-2607] - Text File Input - 1 extra line read when using wrapped l…

…ines and 1 header line

force reading from input when breaks' buffer is empty
add a test for scenario of wrapped input with no headers

@mattyb149, @brosander, review it please

@mattyb149, @brosander, review it please

@mattyb149, @brosander, review it please

@mattyb149, @brosander, @deinspanjer, review it please

@akhayrutdinov please verify that unit tests pass and there are no checkstyle violations in files you've touched

@brosander, I confirm there is no checkstyle violations.
As for tests, I ran those in modules (no problems), but it is impossible ti verify integration tests now, as after master had been merged with future-develop, kettle hangs on startup. You can see it here: http://ci.pentaho.com/view/Data Integration/job/Kettle-integration-tests/
(the job has been executing for 2 days). I wrote a letter to @pentaho-nbaker indicating the problem with osgi-bridge, but haven't got any feedback yet.
Before I sent this PR I had run integration tests and they were passing at that moment


Feature support for Floating point extensions(FD).

fcsr & rm in coverpoints - The current coverpoints define effective rm fields i.e insts always have 7 and fcsr has the necessary rm. Future coverpoints will try to test the frm and rm fields individually to see if the rm field of the instruction over-rides the frm value at run time. To support this and the highlighted issue with fflags, the coverpoints will be modified to have conditions defined on the fcsr value along with the rm field of the instruction.
Nan prefix in coverpoints - Add a new variable in the coverpoints which is defined as the 32 bit msb(in FD) of the value in the register. This is relevant because for most of the floating-point instructions if this prefix is not all 1's, the input is a canonical NaN. Hence the coverpoints should capture this particular aspect while describing cases for fadd.s in RV*FD. Current coverpoints will just have a condition(nan_prefix == 0xffffffff) appended to it.
DPR update - Current DPRs only test whether 1 signature update per instruction which hits coverpoints is present. This will be modified to vary from instruction to instruction by maintaining a mapping which tells the number of stores to the memory for each case.
fcvt.*.* coverpoints (Caught by @davidharrishmc) - The coverpoints for the fcvt.a.b instructions currently assume that the target format is b whereas the target format is a. These need to be reworked. The current tests have a wrong coverage definition and hence provide no value. All outputs are NaNs.

Added support in #47


model converter code cleanup

what are the changes we apply on the model in order to convert it to tflite flatbuffer? currently its a dozen of if-else statements impossible to read and modify! can we encapsulate each of these graph transformations in separate functions and map the graph trans. on the graph separately? (this is how the TF lite TOCO graph transformation  operates)
at which stage we apply these changes? how we make sure we set the right node attributes before the conversion (see here)?
It seems to me we apply the changes before the conversion -> how we know whether our changes are breaking the conversion process or the original model (without our custom op) is not convertible with TF lite converter tool?

the issue is address in the new MLIR converter.


NetworkFence: Explicitly mentioned Fenced and Unfenced state

Currently, the assumption is that, the resource by default
strives to ensure that the CIDRs mentioned in the spec are
fenced. Deletion of the resource makes those CIDRs to have
been unfenced.
This has some issues when fencing is consumed for operations
such as Disaster Recovery. Hence, changed the CR to have
explicit state as either fence or unfence.
Co-authored-by: Raghavendra Talur<EMAIL_ADDRESS>Signed-off-by: Raghavendra M<EMAIL_ADDRESS>

@yati1998 , this pr is waiting for your review, ptal


Model Viewer Asset Screenshots

Loom Demo:
https://www.loom.com/share/1df692086af24e1aa36eae08e3fa6e03

I assume there's nothing we can do about assets that load side ways right @vivianliu0?
Ie. this sunframe3

I assume there's nothing we can do about assets that load side ways right @vivianliu0?
Ie. this sunframe3

Yeah :/ not sure we can do anything about that


Remove seed phase backup from onboarding

Child of #460

there were thoughts to only show this to the user once tokens are received


Decouple Dataset and MapDataPipe

🚀 The feature
As we just decoupled IterDataPipe and IterableDataset, we should do the same for map-style
Motivation, pitch
As the description.
Alternatives
No response
Additional context
No response

Closing the PR as https://github.com/pytorch/pytorch/pull/70991 is landed


Idea14.1 + jdk1.7.0_75 + springloaded-1.2.3.RELEASE do not work!

Hi all!
First, i run  mvn spring-boot:run to start my project, then i change some controller parameters, last i compile the changed the controller file dependently.  the terminal also show the reloading progress and no error meet , but when i open the swagger ui to see the change , nothing happens, i don't know why
last i watch carefully the terminal log, i found that
objc[95939]: Class JavaLaunchHelper is implemented in both/Library/Java/JavaVirtualMachines/jdk1.7.0_75.jdk/Contents/Home/jre/bin/java and /Library/Java/JavaVirtualMachines/jdk1.7.0_75.jdk/Contents/Home/jre/lib/libinstrument.dylib. One of the two will be used. Which one is undefined.
what's this mean?  i add the agent fail? but i can see the reloading the class file

I'm getting the same error using JDK 1.8.0_92 on OSX El Capitan.  Any ideas?


promisify is not a function

Uncaught TypeError: promisify is not a function
at node_modules/better-sqlite3/lib/methods/backup.js (refine-sqlite.js?v=e0b491c1:423:20)
at __require2 (chunk-AUZ3RYOM.js?v=47f26262:18:50)
at node_modules/better-sqlite3/lib/database.js (refine-sqlite.js?v=e0b491c1:842:33)
at __require2 (chunk-AUZ3RYOM.js?v=47f26262:18:50)
at node_modules/better-sqlite3/lib/index.js (refine-sqlite.js?v=e0b491c1:861:22)
at __require2 (chunk-AUZ3RYOM.js?v=47f26262:18:50)
at refine-sqlite.js?v=e0b491c1:867:37
When adding it as an dataprovider

Hello there!
Sorry about that, could you please provide a code snippet showing how you're importing and calling the dataProvider() function?

`
<Refine
dataProvider={customDataProvider}
dataProvider.tsx:
import { DataProvider } from "@refinedev/core";
import { dataProvider as sqliteDataProvider } from "refine-sqlite";
import dataProvider from "@refinedev/simple-rest";

const customDataProvider: DataProvider = {
  getList: async ({ resource, pagination, sorters, filters, meta }) => {
    if (resource === "MessageTemplates") {
      const { data, total } = sqliteDataProvider("database.db").getList({
        resource,
        pagination,
        sorters,
        filters,
      });
      return Promise.resolve({ data: data as any[], total });
    }
    return dataProvider("https://api.example.com").getList({
      resource,
      pagination,
      sorters,
      filters,
      meta: meta as any,
    });
  },
  getMany: async ({ resource, ids, meta }) => {
    if (resource === "MessageTemplates") {
      const { data } = sqliteDataProvider("database.db").getMany({
        resource,
        ids,
      });
      return Promise.resolve({ data: data as any[] });
    }
    return dataProvider("https://api.example.com").getMany({
      resource,
      ids,
      meta: meta as any,
    });
  },
  create: async ({ resource, variables, meta }) => {
    if (resource === "MessageTemplates") {
      const { data } = sqliteDataProvider("database.db").create({
        resource,
        variables: variables as any,
      });
      return Promise.resolve({ data: data as any });
    }
    return dataProvider("https://api.example.com").create({
      resource,
      variables: variables as any,
      meta: meta as any,
    });
  },
  update: async ({ resource, id, variables, meta }) => {
    if (resource === "MessageTemplates") {
      const { data } = sqliteDataProvider("database.db").update({
        resource,
        id,
        variables: variables as any,
      });
      return Promise.resolve({ data: data as any });
    }
    return dataProvider("https://api.example.com").update({
      resource,
      id,
      variables: variables as any,
      meta: meta as any,
    });
  },
  deleteOne: async ({ resource, id, meta }) => {
    if (resource === "MessageTemplates") {
      const { data } = sqliteDataProvider("database.db").getList({
        resource,
        filters: [{ field: "id", operator: "eq", value: id }],
        pagination: { current: 1, pageSize: 1 },
      });
      sqliteDataProvider("database.db").deleteOne({ resource, id });
      return Promise.resolve({ data: data[0] as any });
    }
    return dataProvider("https://api.example.com").deleteOne({
      resource,
      id,
      meta: meta as any,
    });
  },
  getOne: async ({ resource, id, meta }) => {
    if (resource === "MessageTemplates") {
      const { data } = sqliteDataProvider("database.db").getList({
        resource,
        filters: [{ field: "id", operator: "eq", value: id }],
        pagination: { current: 1, pageSize: 1 },
      });
      return Promise.resolve({ data: data[0] as any });
    }
    return dataProvider("https://api.example.com").getOne({
      resource,
      id,
      meta: meta as any,
    });
  },
  getApiUrl: () => {
    return dataProvider("https://api.example.com").getApiUrl();
  },
  custom: async ({ url, method, filters, sorters, payload, query, headers, meta }) => {
    return dataProvider("https://api.example.com").custom({
      url,
      method,
      filters,
      sorters,
      payload,
      query,
      headers,
      meta: meta as any,
    });
  },
};

export default customDataProvider;

I see, the support for client side apps was dropped prior the release of version 1.0
If you're running a plain React template with Vite that could be the cause, I haven't tested yet but I think you could use this provider in React Server Components.

I see, the support for client side apps was dropped prior the release of version 1.0 If you're running a plain React template with Vite that could be the cause, I haven't tested yet but I think you could use this provider in React Server Components.

Thank you alot !!

Im using nextjs and i cant add it as an dataprovider . Can you add an example ?

Im using nextjs and i cant add it as an dataprovider . Can you add an example ?

Sure, I've created a new nextjs project with npm create next-app@latest then I installed the data provider package, downloaded the test.db database and placed on the root of the project.
It worked on a server component from next-app and should work on refine as well, as long as you run it server-side.

code
import { dataProvider } from "refine-sqlite";

export default function Home() {
  const response = dataProvider("test.db")
    .getList({ resource: "posts" });

  const { data } = response

  return (

            ID
            TITLE
            CATEGORY ID

          {data.map((entry) => (

              {entry.id}
              {entry.title}
              {entry.category_id}

          ))}

  );
}

I solved it by just writing a wrapper dataprovider around it .


debug/pe: attempt to allocate giant slice

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version go1.7 linux/amd64
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN="xxxxxxxxxxxxxxxxxxxxxx"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/xxxxxxxxxxxxxxxx"
GORACE=""
GOROOT="/home/quentin/.gvm/gos/go1.7"
GOTOOLDIR="/home/quentin/.gvm/gos/go1.7/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build542001008=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
What did you do?
I triggered a bug in the debug/pe golang package.
I tried to attach the file which triggered the bug but neither EXE nor ZIP are allowed to be attached. So if you want it, please reach me by email.
When I open the file I get a panic with an error message: fatal error: runtime: out of memory
The bug is located at debug/pe/symbol.go:33 syms := make([]COFFSymbol, fh.NumberOfSymbols) because the NumberOfSymbols is too big:
In gdb:
print fh.NumberOfSymbols
$1 =<PHONE_NUMBER>
This is probably due to a bad parsing of the FileHeader of the Coff file at debug/pe/file.go:84 or errors in previous structures parsed.
I also identified a logic problem in the package that may be link to the problem. In debug/pe/pe.go the field NumberOfSymbols of struct FileHeader is type uint32. However, in debug/pe/symbol.go, a check is done on NumberOfSymbols as if it could be lower than 0 (line 26: if fh.NumberOfSymbols <= 0) which can happen only when NumberOfSymbols is 0.
I loaded the binary into another PE parser (radare2) and the NUMBER_OF_SYMBOLS field is actually (numberOfSymbols : 0x00000010 = 0x000000b8) which is far from what it is parsed by the package. I did not dig further but I guess it is enough for you to patch the package.
What did you expect to see?
No bug :)
What did you see instead?
A file not being able to be opened !

cc @alexbrainman

I tried to attach the file which triggered the bug but neither EXE nor ZIP are allowed to be attached. So if you want it, please reach me by email.

Thank you for the offer, but I do not know your email address. You can try and send it to me (alex dot brainman at gmail dot com), but I suspect we might have trouble emailing executable. Alternatively maybe just encode the executable in some way (for example https://play.golang.org/p/1DgIEd2H3C) and attach it to this issue.

When I open the file I get a panic with an error message: fatal error: runtime: out of memory

That is not good. I will try and fix this once I see the file.

This is probably due to a bad parsing of the FileHeader of the Coff file at debug/pe/file.go:84 or errors in previous structures parsed.

I will wait to see the file before deciding.

I also identified a logic problem in the package that may be link to the problem. In debug/pe/pe.go the field NumberOfSymbols of struct FileHeader is type uint32. However, in debug/pe/symbol.go, a check is done on NumberOfSymbols as if it could be lower than 0 (line 26: if fh.NumberOfSymbols <= 0) which can happen only when NumberOfSymbols is 0.

I am not worried about that. It just a pointless extra check.
Thank you for good report.
Alex

@qjerome got your file in the mail. I will investigate this properly when I have some free time, and report back here.
If you know how to fix this and would like to do it yourself, here https://golang.org/doc/contribute.html is how to send your change.
Thank you.
Alex

Here https://go-review.googlesource.com/33170 is the fixes. It is simple enough, and fixes library crash. I think CL should go in go1.8.
Alex


Change Dark prismarine to use black dye.

Just changing the Dark prismarine recipe to use black dye instead of inc sacs to make it consistent with other "dyeing" recipes.

As far as I'm aware the only other recipe that uses dye is purpur (outside of the literal "Dye terracotta" recipes), which is an end block so doesn't immediately have anything analogous. I kind of like prismarine needing sea items to make, but that's also just my immediate opinion. I'd be interested to see what others think.

 But it's just more handy for the recipe to have black dye than raw inc since there's no way to turn the dye back into inc.  Basically a quality of life change.
Just my reasoning there.

I've seen many people complain now about the lack of squids primarily because they need ink for dark prismarine. since upping the amount of squids is not really an option, I feel this small change would make sense.

I'm fine with this, not really something I think is worth fighting a lot over. Especially since vanilla Minecraft allows crafting dark prismarine with black dye as well. I'll merge unless there's any objections

#183


Doc about createClient?

Any docs about the createClient option?

Hi @weilinzung, could you explain a little more about what you are trying to achieve with wanting to use this?

We have a backend app that using Express and also some pubsub functions, and both of them hosted in Firebase.
Express side is using the plugin as middleware, and pubsub functions are not under the Express, so ideally we would need to use ‘createClient’ and export it for both of them.
We want to see the instruction what/why/how about using ‘createClient’, with examples would be even better.
thanks!

Hi @weilinzung
There shouldn't be any need to use createClient. We'd recommend using Bugsnag.start which automatically creates a client internally and will safely ignore and carry on using the existing client if you call it twice:
https://github.com/bugsnag/bugsnag-js/blob/c013924bc17ada497b0fb7c4f026fe67c50b79c5/packages/node/src/notifier.js#L67-L74
So we'd recommend just using Bugsnag.start as described in our documentation:
https://docs.bugsnag.com/platforms/javascript/express/#basic-configuration
If you wanted you could have one file that calls Bugsnag.start and import it in both your Express and pubsub code.
Provided Bugsnag.start has already been called, any calls to Bugsnag.notify or other Bugsnag. methods with just use the client that's been created internally.


some improvements (speed, plugin.zsh, fallback if fzf is not installed)

I changed the code to use the fc command directly instead of the history alias. Furthermore the reverse sort will be done directly in fc so that fzf won't scroll on large histories

Wow - these are excellent improvements. I must say, I am embarrassed that I misspelled "search" in the function naming. Thanks for all of these updates!


feat: support ZodDate type

#48

@heivo The PR looks good. However the build checks are failing - presumably because of prettier. Please run npm run lint (it checks for errors) and npm run prettier (fixes them automatically) and finally npm test to verify everything is working fine. I assume there are styling changes that should be made. After that I'll merge your PR

@heivo The PR looks good. However the build checks are failing - presumably because of prettier. Please run npm run lint (it checks for errors) and npm run prettier (fixes them automatically) and finally npm test to verify everything is working fine. I assume there are styling changes that should be made. After that I'll merge your PR

The build fails because of a type error but I think it's not related to my changes, the same happens for me in master branch as well

@heivo you are right. It must have happened when the latest PRs have been merged (especially the one for the upgrade of openapi3-ts). I opened a PR with the fix that seemed best suited to me. I'll check with @georgyangelov if we can agree on it. Sorry for the inconvenience. Will let you know once a fix is merged.

Well that was quick :smile: .... @heivo we merged the PR so you should be able to fix the issues once you pull master into your branch.

Well that was quick smile .... @heivo we merged the PR so you should be able to fix the issues once you pull master into your branch.

@AGalabov I merged the master branch


Bugfix dtypes

I just noticed that the flux and error dtypes are "object" in the light curve dataframe. I'm not aware of any problems this currently causes, but it might in the future. These really should be floats. This is happening because the pandas explode method returns columns with "object" dtypes. So, this PR sets the correct dtypes right after every explode.

I think this is all that's needed, but I haven't tested it fully. I plan to get back to it next week after the User Panel.

@jkrick the figure at the end of lc_classifier.md section 2.5 looks good to me (comparing with main branch), but I'm less familiar with this notebook. Will you check it?

This bug fix works as intended in the lc_classifier.md notebook.  I don't get it to run through to a plot, another bug has come up with NaN's in the data frame, but that should be a separate PR (for me).  Ok to merge.


Use dmidecode to check available RAM in preflight checks

Problem:
The current implementation of the preflight memory check uses MemTotal from /proc/meminfo to try to figure out how much RAM there is.  This number will always be a little bit low, which is confusing ("Why is it reporting only 60GiB when I know I have 64GiB?!?") and means we have to allow a certain amount of wiggle room when determining whether or not the system meets the minimum production requirements.
Solution:
This commit makes the following changes:

We use dmidecode -t 19 to get the exact amount of memory installed in the system.  No weird low values, no need for wiggle room.
In case the above fails and we have to fall back to /proc/meminfo, increase the wiggle room from 5% to 10%.
For really low RAM scenarios (e.g. tiny test VMs with <1GiB RAM), report available memory in MiB rather than KiB (nobody thinks in KiB anymore, right?)

Related Issue:
https://github.com/harvester/harvester/issues/5599
Test plan:

Boot a system with <64GiB RAM. Verify that the warning message gives the exact amount of RAM you actually have (e.g. 16GiB, 32GiB), vs. undercounting like it used to do (e.g. 7GiB on an 8GiB system).

@Mergifyio backport v1.3


Option to move Recycle Bin outside Favorites to the main navigation on the bottom

What feature or improvement do you think would benefit Files?
The default windows file explorer has the Recycle Bin in the main navigation on the bottom:

While Files has it inside the favorites section:

Requirements
It just annoys me a little that it is a "Favorite", to me it is better placed somewhere else (e.g. like the original windows file explorer on the main navigation on the bottom.
Files Version
Version: <IP_ADDRESS> OS Version: 10.0.19045.2251
Windows Version
Edition: Windows 10 Pro, Version: 22H2, OS build: 19045.2251, Experience: Windows Feature Experience Pack 120.2212.4180.0
Comments
No response

Files isn't File Explorer, not against this change but we'd need a good reason to do it.

Thank you! Definitely open to discussion. I just realized there's a context menu to enable "groups" of the navigation, wouldn't sound too bad to me to be there. The question is though, are there other "special folders" or is it really "only" the recycle bin we talk here about (just thinking forward)

We treat Recycle Bin the same as any other pinned favorite, for what it's worth, you can pin other shell pages to the favorites section as well. With the current design, we'd only create a new group in the sidebar if there are items to group under it.

Closing for now but feel free to continue the discussion and I'll try to respond.


Add more query params to GET /api/v1/attack

Add more query params to GET /api/v1/attack endpoint, to filter attacks based on different attributes, like status=completed or status=failed to list successful vs failed attacks.
Another query-able param would be to list attacks within a certain date/time range using the createdAt and modifiedAt fields.
The Target as a collective should also be query-able based on the endpoint like GET http://xyz.com
There should be more params that would make sense, and I am open to suggestions, but we need to track all that work in this ticket.

[x] Created query param for filtering by status.
[ ] Need query params for listing attacks in specified date range.

I'm on it !

[x] Created query param for filtering by status.
[x] Need query params for listing attacks in specified date range.


Upgrade Fast-DDS, add new build script, add GitHub workflows

Changes

Upgrade Fast-DDS 2.6.0 -> Fast-DDS 2.14.3, 623 new commits in upstream
Add github workflow for compiling the native binaries on all platforms (Linux x86_64, Linux arm64, macOS x86_64, macOS arm64, Windows x86_64)
Add github workflow for gradle tests
Deprecate Intraprocess implementation (in favor of Fast-DDS intraprocess)
Accommodate API changes from fastRTPS_profiles.xsd

API changes from fastRTPS_profiles.xsd:

ParticipantAttributes->ParticipantProfile
Remove TopicKindType
PublishModeQosKindType->PublishModeQosKindPolicyType
ReliabilityQosKindType->ReliabilityQosKindPolicyType
DurabilityQosKindType->DurabilityQosKindPolicyType
HistoryQosKindType->HistoryQosKindPolicyType

I was able to replicate the CI issue locally. Working on a fix.

I was able to replicate the CI issue locally. Working on a fix.

The gradle tests will not run on github's runners. I added a workflow for a self-hosted runner and it passes.

TODO

document how to generate xsd patch file
more extensive testing


FolderExplorer doesn't explore folders with ' in the name

Category
[ ] Enhancement
[X] Bug
[ ] Question
Version
Version: [3.13.0]
Expected / Desired Behavior / Question
The desired behaviour is that with the control FolderExplorer the folders with the char ' should be explorable
Observed Behavior
If you try to explore a folder with the char ' contained in the name, it results to have no subfolders.

Steps to Reproduce
In a SharePoint document library, create a folder with the char ' in the name, then a subfolder inside that.
Try to use the FolderExplorer to select the subfolder.
Thanks!

Hello @abertoletti, This issue seems to be with FolderExplorerService.ts where it fetches the folders in the folder relative url. I have tried to solve the issue now, and it seems to be working in my local.
Below is the screen from my workbench,

Below is the folder structure,

I will be submitting the PR soon after final checks.
Thanks,
Nishkalank


Does this bundle support Symfony 5?

Hello!
I'm trying to use this bundle with Symfony 5.
What do I have:
php -v:
PHP 7.3.14 (cli) (built: Jan 27 2020 21:55:23) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.14, Copyright (c) 1998-2018 Zend Technologies
    with Zend OPcache v7.3.14, Copyright (c) 1999-2018, by Zend Technologies
    with Xdebug v2.7.2, Copyright (c) 2002-2019, by Derick Rethans

composer.json
"require": {
        "php": "^7.2.5",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "easycorp/easyadmin-bundle": "^2.3",
        "myclabs/php-enum": "^1.7",
        "sensiolabs-de/rich-model-forms-bundle": "^0.4.0",
        "symfony/console": "5.0.*",
        "symfony/dotenv": "5.0.*",
        "symfony/flex": "^1.3.1",
        "symfony/form": "5.0.*",
        "symfony/framework-bundle": "5.0.*",
        "symfony/http-client": "5.0.*",
        "symfony/monolog-bundle": "^3.1",
        "symfony/orm-pack": "*",
        "symfony/security-bundle": "5.0.*",
        "symfony/twig-pack": "*",
        "symfony/validator": "5.0.*",
        "symfony/yaml": "5.0.*"
    }

I've set up a simple config:
easy_admin:
    entities:
        User:
            class: App\Entity\User

            new:
                fields:
                    - { property: name }

                form_options:
                    factory: App\Entity\User

I have an issue entering new view:

Argument 2 passed to SensioLabs\RichModelForms\ExceptionHandling\FormExceptionHandler::__construct() must be an instance of Symfony\Component\Translation\TranslatorInterface or null, instance of Symfony\Component\Translation\DataCollectorTranslator given

Seems like its related to https://github.com/sensiolabs-de/rich-model-forms-bundle/commit/27d67bb98edbb9eb163d550eeef17fe1aed7123a
Ping me, if you would like to get a repository with reproducable example.
Thanks in advance!

Does it work if you change the constraint to ^0.5@dev and update the package?

@xabbuh sorry, can't tel you exactly, because right after installing new version I'm getting

Could not resolve argument $authenticationUtils of "App\Controller\SecurityController:login()", maybe you forgot to register the controller as a service or missed tagging it with the "controller.service_arguments"?

My services.yaml left untouched:
services:
    _defaults:
        autowire: true
        autoconfigure: true
    App\:
        resource: '../src/*'
        exclude: '../src/{DependencyInjection,Entity,Migrations,Tests,Kernel.php}'

    App\Controller\:
        resource: '../src/Controller'
        tags: ['controller.service_arguments']

an my controller is as it is in the documentation:
class SecurityController extends AbstractController
{
    public function login(AuthenticationUtils $authenticationUtils): Response
    {
        $error = $authenticationUtils->getLastAuthenticationError();

        $lastUsername = $authenticationUtils->getLastUsername();

        return $this->render(
            'security/login.html.twig',
            [
                'last_username' => $lastUsername,
                'error' => $error
            ]
        );
    }

    public function logout(): void
    {
        return;
    }
}

I cannot help you with this problem here, but I can tell you for sure that's it's not related to updating this bundle.

Do you need some help with 0.5 release? Any TODOs I could help with?

I decided to tag 0.5.0. You could give it a try.
If you would like to contribute in general, you can a look at the things that are part of the 0.6 milestone.


OCI Resource Manager Form Problem

Hi Rishi,
I am trying to install hyperion on Oracle cloud using your terraform script. (https://github.com/oracle-quickstart/oci-hyperion) but I cant do it beacuse of some parameters that I cant edit it.

@emrahmete - I could not reproduce this issue. Can you follow these steps to re-create zip file and confirm if this renders the form properly?
https://github.com/oracle-quickstart/oci-hyperion/tree/master/orm


My branch

in order to connect the camera you have to write the serial number in config.yaml file.  So if you want to connect multiple cameras you would need multiple config files.

in order to connect the camera you have to write the serial number in config.yaml file. So if you want to connect multiple cameras you would need multiple config files.

driver only needs serial number and does not require full configuration file. Please update driver.rst in docs with examples how to use and test driver module.


Naming reducers for combineReducers

This may not be an issue actually. Is the name of the imported reference equals to the property name of "state" when I call mapStateToProps? e.g. I need to use "state.someReducers". I am still new to redux, perhaps I missed something in documentation.
import someReducers from './someReducers';

const rootReducer = combineReducers({
  someReducers
});

Why don't we do it more explicit?
import someReducers from './someReducers';

const rootReducer = combineReducers({
  items: someReducers
});

Yes, the shape of the object passed into combineReducers matches the store state that those reducers will operate on. If we do { itemsReducers }, that desugars to { itemsReducers: itemsReducers }, which is probably not what you want. I normally do something like this:
import items from './someReducers';

const rootReducer = combineReducers({
  items
});

Your import name can be whatever you want it to be, so you can match it to your state shape.

There's a balance between being explicit in examples and showing what we believe to be best practices. We don't really want to encourage people to name reducer files someReducers; the convention we encourage is to match reducer name to the state field name. But then writing { something: something } is redundant in ES6 so we don't do that either.


Support Xamarin.Forms on macOS

Add support of Xamarin.Forms on macOS platform.

I'm interested in contributing. Will look into what's involved.


i18n(zh-tw): update layouts.mdx translation

Description

Updates src/content/docs/zh-tw/basics/layouts.mdx

Related issues & labels

Closes #
Suggested label: i18n

As there are still some differences between Traditional Chinese and Simplified Chinese. So I'll wait for the other maintainer to look at it before merging it.

Hey @dreyfus92 Cloud you help to double-check this PR?


Portal Upload fails due to pre-update plug-in

Recently, when uploading a portal to an environment with a community portal installed, the upload failed due to a pre-update plugin. This cause the site setting to NOT be associated with the website.
The plugin is:
Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate: Update of adx_sitesetting
With the error:

Exception Message: Object reference not set to an instance of an object.
ErrorCode: -2147220891
HexErrorCode: 0x80040265
ErrorDetails:
ApiExceptionSourceKey: Plugin/Microsoft.Crm.ObjectModel.CustomBusinessEntityService
ApiStepKey: 41952d10-4e53-ea11-a814-000d3a3b1e97
ApiDepthKey: 1
ApiActivityIdKey: 2147f1bc-dc07-48b4-86bf-279b2e74e528
ApiPluginSolutionNameKey: System
ApiStepSolutionNameKey: System
ApiExceptionCategory: ClientError
ApiExceptionMessageName: IsvAborted
ApiExceptionHttpStatusCode: 400
OperationStatus: 0
SubErrorCode: -2146233088
Plugin:
PluginTrace: [Microsoft.Dynamics.Community.Plugins: Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate]
[68a2d42a-8bf1-eb11-bad6-000d3af6d0a1: Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate: Update of adx_sitesetting]
CorrelationId:78e3514a-7ede-4327-bcff-376667b2b006  Entered Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate.Execute()
CorrelationId:78e3514a-7ede-4327-bcff-376667b2b006  Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate.ExecuteCrmPlugin(LocalPluginContext context)
at Microsoft.Dynamics.Community.Plugins.PluginBase.Execute(IServiceProvider serviceProvider)
CorrelationId:78e3514a-7ede-4327-bcff-376667b2b006  Exiting Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate.Execute()
TraceText:
[Microsoft.Dynamics.Community.Plugins: Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate]
[68a2d42a-8bf1-eb11-bad6-000d3af6d0a1: Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate: Update of adx_sitesetting]
CorrelationId:78e3514a-7ede-4327-bcff-376667b2b006  Entered Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate.Execute()
CorrelationId:78e3514a-7ede-4327-bcff-376667b2b006  Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate.ExecuteCrmPlugin(LocalPluginContext context)
at Microsoft.Dynamics.Community.Plugins.PluginBase.Execute(IServiceProvider serviceProvider)
CorrelationId:78e3514a-7ede-4327-bcff-376667b2b006  Exiting Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate.Execute()

Turned off the plugin and the upload worked great.
Would be great to know if turning off plugins is available now or will be in the future.

@ameyaapte1 please comment

This sounds like a feature ask, will have to work with the Community portal team to work this out as currently the platform does not support disabling first party plugins although this can be done with using plugin parameters which can control the plugin logic. @ashishchoudhary001 @neerajnandwana-msft

@neerajnandwana-msft  Can you comment on this?

Closing because this is not build tools issue


add function to get current user

Sometimes I want to get the current user, to write a log file or named something based on the name of the current user, to do this I've add the 'getCurrentUser()' function to the Shield class

Thanks for your pull request. Could you describe a use case for this?

Of couse,
If I want to use the Laravel\Guard for example, knowing wich user is logged, I can block or allow some areas of my application. Example: admin\user credentials.
Another one is for logging, knowing wich user is, I can log each action and after that separate per user, so if something get wrong I know exactly wich user was on that time.
I thing the key of the array in config/shield.php is a simple and good way to nominate the user

@vinkla everything updated :+1:

@jaschweder Good work :+1: Now please squash your commits and then I'll merge this in.

finished

Thanks!

Released it as 0.3.2


migrate .tld files

The migration guide is unclear on what should be done with .tld files in web-app/WEB-INF/tld. It says:

Removed, can be restored in src/main/webapp

I'm confused by the "can be restored" wording. It seems like this may not be necessary, but it's not clear under what circumstances. If it's simply the case that all .tld files should be copied to webapp - but where exactly (e.g. webapp/tld) - then the plugin should be enhanced to perform this task

TLD files can be added to src/main/webapp/WEB-INF/tld . However TLD file scanning is disabled by default.
https://github.com/grails/grails-core/blob/5728b2b/grails-web-jsp/src/main/groovy/org/grails/gsp/jsp/TagLibraryResolverImpl.groovy#L51 is the location where the configuration is read.
Currently it should be possible to enable TLD file scanning with this config:
---
grails:
    gsp:
        tldScanPattern: /WEB-INF/*.tld

I'm not sure if we want to do TLD scanning by default in Grails 3. Please add a Jira issue for doing that by default if you think so.

@lhotari thanks for the feedback. In my experience most Grails app have these 4 TLDs. Am I right in assuming that there's no reason why these should be migrated?
If so, then any other TLDs found in the Grails 2.x project under web-app/WEB-INF/tld will be copied into src/main/webapp/WEB-INF in the Grails 3.x project, does that make sense?
I'll also add this TLD scanning pattern into application.yml.
grails:
    gsp:
        tldScanPattern: /WEB-INF/*.tld

Can you recommend a Groovy/Java library that I use for reading/writing YML?


Renaming the app causes the app to crash at startup

If you rename the app, you get a "No cloudant service found" error at app startup.
This is due to the nodeRed application code making an assumption that the Cloudant servicename will always contain the name of the original application name. So, if the app name changes, it means that the nodeRED application fails as it attempts to find Cloudant service.
The problem seems to be in the following lines of the bluemix-settings.js file:
settings.couchAppname = VCAP_APPLICATION['application_name'];
var storageServiceName = process.env.NODE_RED_STORAGE_NAME || new RegExp("^"+settings.couchAppname+".cloudantNoSQLDB");
var couchService = appEnv.getService(storageServiceName);

Hi,
The solution is in that same bit of code. If you rename the app, you must create an environment variable called NODE_RED_STORAGE_NAME set to the name of the cloudant instance it should be using.
Nick


Physics: collision pass through between StaticBody3D w/ ConcaveCollisionShape3D and RigidBody3D with ConvexPolygonShape3D

Tested versions
Reproducible in 4.3 and 4.4dev5.
System information
W11
Issue description
As per the issue description, a rigid body with two ConvexCollisionShape3D registers an initial collision with a static body with a ConcaveCollisionShape3D that is actually convex, but then fails to register the second collision when both "legs" are supposed to be on the ground.
https://github.com/user-attachments/assets/599e5e92-ef46-4bfe-bbfb-868f1bf66139
Unfortunately not fixed by #99895.
Steps to reproduce
Download MRP, make sure to have visible collision shapes, press play and watch the collision fail to happen! Should happen consistently.
Minimal reproduction project (MRP)
MRP.zip

I am almost certain that when I reported the original issue, I had continuous collision detection turned on for the RigidBody3D. Might have to do with the velocity on impact. I will try to turn the setting on and see if I can find a configuration that causes this issue.
I did double-check the sizes for the shapes. In blender, the height of the collision shape is 0.16m, so above the suggested minimum size for Jolt at least.

I did double-check the sizes for the shapes. In blender, the height of the collision shape is 0.16m, so above the suggested minimum size for Jolt at least.

This is not relevant in this case. Without CCD, the simulation moves in discrete steps, so if speed * step delta time > height of shape, then objects can tunnel through geometry. See e.g.: https://jrouwe.github.io/JoltPhysics/#continuous-collision-detection.


Optimize custom all reduce

remove volatile keywords (they have a different meaning on CUDA than HIP)
optimize and scope locking
increase cutoff for custom all reduce to 16 MB (based on perf data)
tune block number for MI300X
roughly 10% performance increase for non-latency bound sizes, cutoff vis-a-vis RCCL at 16 MB
while there, add missing MPI_Finalize() to test

Looks good. Just need to fix the linters

Hey Folks..wanted to make a quick comment. This CAR will require rocm 6.2 to compile.  the scoping intrinsics are introduced in LLVM in the 6.2 release. So we may see compile errors on __MEMORY_SCOPE_DEVICE etc.

Hey Folks..wanted to make a quick comment. This CAR will require rocm 6.2 to compile.  the scoping intrinsics are introduced in LLVM in the 6.2 release. So we may see compile errors on __MEMORY_SCOPE_DEVICE etc.

We should not push out releases where the default settings (ROCm 6.1) do not compile. Again, I understand this is already fixed by #137 but hotfixes should be kept to a minimum. Especially when this issue is so readily detectable.


Custom Dispatcher / Serial Execution of tasks .

What kind of issue is this?

How can I change the execution strategy  of multiple tasks to be executed on the fly ,  How to execute requests serially or parallely on the fly  ? I know we can do it by implementing our own custom dispatcher and setting it to client but I found Call.Async class to be not exposed so i am stuck with the problem .

Please use stack overflow for questions.


Add remote MQTT connection as a failover

Not sure if this code would be wanted, given the integrations suffix, but it works for the Vis Nav #142

@Sean-StarLabs this is wonderful, thanks so much for the PR!
As you mentioned, it doesn't totally jive with the integration's suffix. I do have a few reservations about adding cloud control here. The biggest reason is simply that I absolutely want to minimize what Dyson may consider "unauthorized access" to its AWS services. There's been a significant recent uptick in Home Assistant integration projects getting shot down by corporate lawyers, especially when it comes to what companies see as abuse of their APIs.

https://community.home-assistant.io/t/haier-hits-home-assistant-plugin-dev-with-takedown-notice-lets-fork/675784
https://www.home-assistant.io/blog/2023/10/13/removal-of-mazda-connected-services-integration/
https://www.home-assistant.io/blog/2023/11/06/removal-of-myq-integration/

It costs Dyson money to support the cloud connectivity, and no doubt they've done their cost modeling and baked that all into the price, firmware, and the implementation of connectivity through the mobile apps. As soon as some third party (you or me) starts pinging the MQTT topics on AWS IOT, suddenly that cost model changes in a way that they can't control like their product managers have planned.
So for the time being, I've been avoiding adding the capability to connect to AWS. If future devices or future firmware versions wind up having no local connectivity, I might have to make a more solid decision one way or another.
What are your thoughts? Hope this isn't too disappointing.

Does it ping though? I thought MQTT was just listening.

@codyc1515 a really good question, and a poor choice of words on my part. Strictly speaking, we also send control messages from this integration over MQTT as well, so it's not strictly listen-only.
But that's secondary - with AWS IOT, the cost is the same either way:

There's no differentiation between "message sent" or "message received"

If there's one message sent and two clients/listeners receive it, AWS charges for three messages. (1 sent + 2 received)

Additionally, AWS charges for connection time on top of messages.

For every device/listener connected, that's incurring extra charges that get charged to Dyson.
If the fan is connected 24/7 for a month, that's about 44,000 minutes per month. If the fan AND your Home Assistant instance are both connected 24/7 for a month, that's about 88,000 minutes per month.

While AWS IOT is pretty cheap overall, those little numbers can start to add up. Dyson has committed to supporting these devices long-term, and they've baked the cost of supporting those cloud connections into the device rather than charging a monthly subscription.
I don't know how many users I have here, and I don't want to presume that I'm anything more than a small fish in a big pond. In fact, as a small fish, Dyson (and its lawyers) is a big scary bear that I want to avoid drawing the attention of!

That’s very fair.

What are your thoughts? Hope this isn't too disappointing.

Personally, it doesn't bother me either way, but in terms of merging...
Have they ever said anything before to you or any of the other third-party integrations (I'm assuming you've had some contact with them in the past from maintaining this?)? Or do they have any documents we can use to check the legalities?
One could assume a company that's just spent a tonne on R&D on a product that got an absolute kicking for the first 6 months would want any "help" they can get - particularly trying to get feature parity with its competitors. That's probably not the case, but for costs, I doubt that's a factor, as we'd just be using the AWS budget intended for Google Assistant or Alexa in HA.

Does it ping though? I thought MQTT was just listening.

You can start a clean on a Vis Nav, haven't done more than that (fan isn't even plugged in atm)

@Sean-StarLabs
I really wish I had happier answers to your questions :sweat_smile:. I'm grateful for you going to the effort of opening this PR, really. And I'm also excited to have another person so willing to share their thoughts here. But I'm not in a position to merge any PRs which add active cloud connectivity right now. I am making a serious effort to stay on my best behavior, and stay on my side of the line - even though I don't really know where the line is.
The Dyson integration was part of Home Assistant Core before 2021, and perhaps some day it'll be merged back into the core project.  It would also add a lot of legitimacy to the ha-dyson project to be part under the Open Home Foundation.
If that happens - and that's a big if - it might give some room to add cloud connectivity features without worrying as much. When it's just a guy on Github - even though I'm not accepting sponsorship or donations - the folks at Dyson don't have any real incentive to do anything other than ...

follow the status quo or
just send Github a DMCA takedown.

If it's a nonprofit foundation supported by hundreds of thousands of people, maybe the DMCA from a lawyer becomes a good-behavior request from a product manager. Maybe we'd even be able to actively collaborate (that would be awesome) But even some of the takedown examples I linked above were part of Home Assistant Core (even if they were Pre-Foundation) so it's not a golden ticket either.
But sadly, it's unclear if any of that can happen. It's been a transformative couple of years in the Home Assistant and FOSS Home Automation communities. Our work is scrutinized a lot more and standards are considerably higher. Getting to be a part of Home Assistant Core rightfully requires reaching higher than it did in the past. Meanwhile, companies are actively shooting down projects which cross lines drawn in the sand, and "unauthorized access to API/cloud" is by far the most commonly cited line, as you can read in the links I shared earlier in the thread.
But now to answer your questions directly:

Have they ever said anything before to you or any of the other third-party integrations (I'm assuming you've had some contact with them in the past from maintaining this?)?

I've actually had zero contract with any Dyson employees for anything regarding this project. One person who has contributed in the comments is purportedly a former employee, and some other users have reached out to Dyson via customer support channels (as you've seen over in #142 for example). But everything I've here has been one of two things:

Stuff I just inherited from @shenxn and the other previous contributors.

I'm really standing on their shoulders here!

Stuff I learned by inspecting the MQTT messages and API calls through my home network.

Or, crucially, by working with other commenters and contributors to do the same on devices that I don't personally own.

do they have any documents we can use to check the legalities?

Strictly speaking, yes. The MyDyson App Terms of Service, which says (trimmed down for brevity):

You must not . . . reverse-engineer, decompile, . . . or otherwise tamper with any . . . technology that forms part of the App.

Dyson is almost certainly in their rights to tell any of us to pack up and pound sand at any time. This is the nature of the vast majority of community/FOSS home automation projects, and probably even the majority of official built-in Home Assistant core integrations. That Terms of Service section is default boilerplate legalese and is used for every app, cloud connection, API, or website that exists in the English-speaking world. Whether our use here is legally defensible, or whether the contract is enforceable, is moot. I'm not in a position to lawyer up, I'm not a big enough deal for the EFF to come in and save, and honestly I just want to make a helpful nerdy tool for people to use. I feel like offering regular access to Dyson's AWS IOT setup would go against the spirit of the integration as a local-first solution, on top of inviting unwanted attention.
This is the (usually unspoken) understanding between us in the open-source community and the industry that makes connected things we hack on.

I really wish I had happier answers to your questions

I think I wrote that badly, but I'm good either way—after all, mine's working now (after I figured out the expiration of the tokens)!
All I'd say is don't rule out contacting them - maybe that's because I'm from a different section(?) of the FOSS world. We speak to companies all the time, and most quickly come around to working with us (quickly, being 10-15 emails!). When they don't, people band together and write them letters :)

@Sean-StarLabs Glad your setup is working well! I don't intend to lay any burden of support upon your shoulders here, but I'd at least like to let some other users know your fork is out there if they want to use the Vis Nav. Feel free to let me know if you'd rather I don't.
And yeah, I'll try to keep an open mind to enabling cloud connectivity for sure. Thanks for the discussion here, and feel free to stick around and comment/contribute as long as you like!


Add finalizer to osephemeralheat

When the configmap in osplaybookgenerator changes, the
ephemeralheat gets recreated, but there is no finalizer used
yet to wait that all resource got deleted. When the resource
get not cleaned up correct, the password in the still running
mariadb pod and the heat pods can be different and the
playbookgeneration is broken.
This introduce a finalizer on osephemeralheat to cleanup all
resources properly when the osplaybookgenerator triggers a
recreate of the ephemeral heat stack.

I added two thoughts, but really I think it's fine to merge as-is.


Persist clockwork manager start-time for first-time interval-based events

Adresses https://github.com/cargomedia/sk/issues/1152

please review @fauvel
Some explanations regarding the unit-tests (mocking clockwork is rather complicated):
The return-value of CM_Process::fork() (normally the forked process' pid) is used to identify the event executed in that process and is the key of the corresponding workload-result in the array returned by CM_Process::listenForChildren()

The app code looks good, but I don't understand the unit tests to 100%  – maybe split it up into different test cases, so that others can better understand which behaviors exactly are being tested?

please review @fauvel
The tests I added all cover exactly one behaviour (but multiple aspects of this behaviour) :)
I could split it up a bit further, but the amount of setup-code required is just too much. I would be copying 30 lines and only changing 2 of them.

Lgtm!

Tagged 1.104.3

over 100 :D


adding Washington Preparatory School

https://waprep.org/

@KurthaTheBurtha I have to close this request without merging, because you requested to add a non-existent domain to this repository: Host waprep.edu not found: 3(NXDOMAIN) Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!

Just added another pull request under .org folder, which should be a valid domain

From: Philip Torchinsky @.>
Sent: Friday, September 29, 2023 8:33 PM
To: JetBrains/swot @.>
Cc: Kurt Schimmel @.>; Mention @.>
Subject: Re: [JetBrains/swot] adding Washington Preparatory School (PR #18868)
Closed #18868https://github.com/JetBrains/swot/pull/18868.
—
Reply to this email directly, view it on GitHubhttps://github.com/JetBrains/swot/pull/18868#event-10516409679, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AV2ULC23CFX3JKNXC6FFBHTX46HIHANCNFSM6AAAAAA5M2T4SU.
You are receiving this because you were mentioned.Message ID: @.***>


Security & Compliance Center

Re that section, to be consistent with the rest of the page (and to not trigger a login prompt), use $credential instead of $UserCredential.
Also, to be consistent, -Authentication "Basic" instead of -Authentication Basic
And finally, leaving off "-Prefix cc" from the second line leads to a long list of yellow warnings. As was mentioned before, "Since cmdlts in Exchange Online and Compliance Center collide, we add a prefix 'CC' to all commands that refer to Compliance Center."
So, in summary, I'm sticking with:
$SccSession = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.compliance.protection.outlook.com/powershell-liveid/ -Credential $credential -Authentication "Basic" -AllowRedirection
Import-PSSession $SccSession -Prefix cc

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

ID: 0c551eb1-7ac5-cb02-cd1b-d67ca3886d85
Version Independent ID: fb690e2e-420e-f697-60f2-39520283d385
Content: Connect to all Office 365 services in a single Windows PowerShell window
Content Source: Enterprise/powershell/connect-to-all-office-365-services-in-a-single-windows-powershell-window.md
Service: o365-administration
GitHub Login: @JoeDavies-MSFT
Microsoft Alias: josephd

@rpodric, PowerShell commands updated with your suggestions. Thanks for letting us know. Joe


rpc: replace go-wire based jsonRPC with probuf based grpc and  grpc_gateway

#70

有的路径是chain/proto 有的是gemmill/proto，特意分开的？


Cms that you use

Can we know what cms do you use?
I want to test your kutr integration.
Thank you

I'm using my own CMS. Basically, it's using its own domain name and cookies to set up its own session so care must be taken when creating Kutr's JWT Token.
What is your CMS ?

i tried to integrate with a laravel cms wich works with Sentinel.
i placed my cms_login.php in the public folder.
Then i call Sentinel:

use Sentinel;

Then bootstrap:

require_once("/../***/bootstrap/autoload.php");

about checking the session, i don't know how to do it, maybe a simple:

if Sentinel::check { }

Then i get the current user username:

$login = Sentinel::getUser()->username;

I set the secret key.
But when i visit mycmsdomain.com/cms_login.php , i just get a blank page.


[3.x] Physics Interpolation 2D - change transform API to use const ref

Notes

I must have missed this on the original PR, const ref should be slightly better.

Thanks!


Deleting translation and redirect

After confirming deletion you are redirected to "admin:changelist" page, maybe "admin:change" is more obvious choice?

Fully agreed! Fixed in 3be68c2e82d0db5e43c4ebb7956b5d05a2a2d0dd


Simple transfers from contracts should be paged

Description
simple_transfers from smart contracts should be paged similarly to how regular transactions are paged.
The unpaged behaviour becomes an issue for contracts with large action trees that produce simple transfers.
Example of current behaviour:

A small addition, I think it should not just be for simple-transfers, because you can in principle have large sequences of update events inside one smart contract transaction call.


Discourse thread should be displayed below tab container

Currently we embed the discourse discussion for an entry at the bottom of the info tab. I think it may make more sense to have the embed exist below the tab holder, that way no matter the tab you are on you can see the discussion.
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Issue Number: DOCK-325

Let's chat about getting discourse working on staging

On staging it looks like it is within all tabs, not just info tabs.

Fixed on:
DockstoreAPI - 1.6.0-rc.4
DockstoreUI - 2.3.0-rc.4


Tests: Coverage improvements for newer endpoints

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 40.00000% with 3 lines in your changes missing coverage. Please review.

Project coverage is 83.25%. Comparing base (943a8b3) to head (35345e1).

Files
Patch %
Lines

src/controllers/users/updateUserMeta.ts
33.33%
2 Missing :warning:

src/controllers/auth/refreshToken.ts
50.00%
0 Missing and 1 partial :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #69      +/-   ##
==========================================
+ Coverage   80.51%   83.25%   +2.74%
==========================================
  Files          73       73
  Lines        1057     1057
  Branches      138      139       +1
==========================================
+ Hits          851      880      +29
+ Misses        177      150      -27
+ Partials       29       27       -2

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


Storing ecosystem libraries

Hi! I took the liberty of creating a repository called effectful-contrib where I stored my bindings to libraries like time and cache.

Thanks for letting me know :slightly_smiling_face:
As I already described in https://github.com/arybczak/effectful/pull/25#issuecomment-887091564, I'd like to avoid a situation in which I have too much code to maintain, so I'm leaning towards simply having this repository for the core, i.e. effectful-core, effectful and effectful-resourcet, while letting people store their effectful contrib libraries where they see fit.
That's the approach taken by optics and it seems to work well.
You suggested an effectful organization for storing the core and contrib libraries, but I suppose that would require me to coordinate access rights, which is the burden I'm not quite keen on taking :thinking:

Absolutely understandable! Focus on the lib, I'll take care of upgrading the bindings every once in a while until stable releases. ;)


Firebase - Page Not Found

In the browser, this link not works: https://flutter-neumorphic.firebaseapp.com/
Demo:

still not working

still not working...

any news about this @Idean?


specialHandling compiler "backdoor" works for models

This PR extends the “backdoor” or “specialHandling” system to models.  This system allows experimentation with rewriting C++ code and seeing if it will compile within the nimble workflow.  The compiled objects would be dangerous to use (could break if meaningful changes have been made), but it is useful to see if C++ compilation is successful in order to experiment with redesigning C++ model code.
Documentation

:+1:

We are now timing out on Travis-CI due to tests running > 3 hours.  Let's discuss.

I think it's safe to merge this if time-limit is the reason for build failure.


chore: Dependency updates NestJs v9, @aws-sdk/client-qldb, and others

Leaving support for NestJs v8

:tada: This PR is included in version 3.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add search bar for rpc docs

This PR is addressing the problem of finding docs for one specific rpc command by its name. In the website one can not simply find his/her desired command in the menu. One should open all the parent categories (Blockchain, Control, etc) and then use Ctrl+F to find the command.
I have added a little javascript code to handle the string search between all commands and make this process much easier.

Concept ACK.  This is very nice and a much smaller amount of code than I would've expected.  Thanks!  Two comments:

Can you use <noscript> (or whatever) to hide the search box if JS is disabled?

I think it's a little hard to see the search box.  Do you or anyone else have any suggestions for making it more visible?  Maybe just give it a grey background instead of white?

Your comments are addressed in https://github.com/bitcoin-core/bitcoincore.org/pull/722/commits/caee34dbf4c452c334a364f873fb447c4f24783b @harding

Tested ACK caee34dbf4c452c334a364f873fb447c4f24783b Reviewed code, tested with Chromium, Firefox with NoJS, and Firefox with JS enabled.  Made several searches and didn't see anything odd.  Ran all repository tests.
I'll leave this open for the rest of the weekend in case anyone else wants to review; if there are no problems, I hope to merge Monday.  Thanks @n1rna!

Thanks @n1rna!

Thanks @harding ! Hope it helps other developers find what they're looking for faster xD

Note.  I don't have the ability to merge this because the Travis check hasn't passed (it's stuck on "Expected---waiting for status to be reported"; the tests pass for me locally).  I don't have access to kick Travis or push a merge anyway.  I asked for help on #bitcoin-core-dev but nobody responded, so this PR is stuck.  :-(

I'll let you know when I hear back from travis. It is their faulty abuse detection: https://travis-ci.org/github/bitcoin-core/bitcoincore.org/requests

@MarcoFalke thank you!

I think the best would be to disable the ci requirement long term.
Not sure if close-open does help now, but you could try.

Our system automatically flagged your account for possible abuse, but after further review, we were able to clear that up. You should be all set to build as normal, though please feel free to contact us should you have any questions or concerns arise.

Thanks @MarcoFalke


✅ Add basic unit testing (next)

Should cover the basics for the time being

[x] Classes
[ ] Theming
[ ] Get customer
[ ] Messages added
[ ] Get previous messages
[ ] Update customer
[ ] Socket creation
[ ] Channel joining

Any others?

I'll pick this up

Great, assigned!


How to save a state of the pagination

In my situation I have an array of links with details. When I go by a link and than return back, my previous pagination state is reset. Any idea how I could fix it?

Check ngCookies.

Basically you need some method of saving state in your app. As mentioned above, cookies could be one option. Other options would be to store the state in a parent controller (e.g. and app-wide controller), or use a service to save and restore the pagination state.


Serial terminal is buggy in recent version

I've noticed that in the recent version the serial terminal seems buggy, it used to work in previous versions (5 July).
Is there a way to run old versions of v86 in your website? this would help to compare and detect code regressions.
You can check this issue by running FiwixOS, then edit /etc/inittab with vi and change the line:
#S0:2345:respawn:/sbin/mingetty --autologin=root ttyS0
by
S0:2345:respawn:/sbin/agetty -L 9600 ttyS0
Save the file with :wq, and under the system prompt type telinit q.
You'll see the login message appear in the COM1 window below. So far so good.
Try to log in with user root and when it prompts for the password you'll notice that you won't be able to type anything or whatever you type it will be sent as garbage.
If you prefer test this issue using a more trusted kernel like Linux, no problem. I've prepared a bootable floppy disk with the Linux kernel 2.2.6 with support for serial:
linux-2.2.26+serial-ext2.img.zip
Just boot the FiwixOS image with that floppy and then change the GRUB line to say:
kernel /boot/vmlinuz-2.2.26 ro root=/dev/hda2
Then proceed with the same instructions as in FiwixOS above.

Do you think that it is related to #899?

Did you try the git version, or just the one on the website?

Do you think that it is related to https://github.com/copy/v86/issues/899?

There have been several bugfixes related to the serial console recently, I think https://github.com/copy/v86/pull/923 might be related.

Did you try the git version, or just the one on the website?

The one on the website.

In current master I can't reproduce the issue, so I'll assume it has been fixed in one of the recent bug fixes (most likely #923). Will push a new version to the website soon.

OK, then I'll check it again as soon as you push the new version.
Thanks.

The fix should be online now, could you check again?

After update, serial terminal work correctly in FiwixOS 3.2:

@copy, yes serial terminal is working back again.
Thank you very much!


Should fix GET requests.

Support for GET requests.
Issue described also here. https://github.com/skevy/graphiql-app/issues/8

Thanks!