Automatically print spine info

Hello,
I have GA access for the SpineOMatic, which is great for modifying the way the info on the spine label is printed.  The issue I'm having is being able to automatically print the info once I scan the item without being asked to choose a template.  I'm having to manually type in the information for every item I scan.  I was able to do this before I was granted GA access, but not since.  Did I accidentally delete something on my end?

Hi @chilurean - thanks for your question. Not sure I understand 100% the issue. Can you perhaps add a screenshot which shows what you're seeing?
Thanks!

@chilurean, are you still experiencing this problem? If so, could you please provide a screenshot of what you are seeing?  Thanks.

Closing this issue. Please open a new issue if it is still a problem.


[stable/grafana] Default to empty clusterrole rules

What this PR does / why we need it: Clusterrole rules are undefined by default which causes an error with some versions of Kubernetes (1.9.2)
$ helm install --name grafana-tmp stable/grafana --version 1.11.4
Error: error validating "": error validating data: field rules for v1.ClusterRole is required

Which issue this PR fixes: The relevant change was introduced in PR https://github.com/kubernetes/charts/pull/5369
Special notes for your reviewer: Please confirm there are no unexpected consequences of setting rules: [], I can't find any relevant Kubernetes docs.

/assign @linki

/ok-to-test


Support finding a local yamlfmt config file named .yamlfmt.yaml

Add an additional filename that can be found (or maybe two, with both variations of the extension). It'd be nice if ~/code/foobar/.yamlfmt.yaml was loaded, as that would means editors will easily detect the file type.

Hi @nogweii,
v0.11.0 added support for calling the file yamlfmt.yml or yamlfmt.yaml. I opened a PR so those can be hidden as well.


remove superfluous src

This package-info.java is necessary for the idea-maven-plugin that adds assertions into the code for @NotNull.  I didn't notice that it had been disabled, we should re-enable it and this file will then be necessary.

Hm - that's ideauidesigner-maven-plugin (plugin provides the capability to convert *.form files into Java code).

You are correct that it supports compiling *.form files, but the same plugin runs the javac2 compiler which adds the Assertions for @NotNull.

Heh - can't believe that - but you're right. Crazy that a UI-plugin does such things...
The size of the class files differs with and without that plugin.
Will revert the meaning of this PR. Give me a few minutes.


Add a Gitter chat badge to README.md

skeleton-framework/skeleton-framework now has a Chat Room on Gitter
@gld1982ltd has just created a chat room. You can visit it here: https://gitter.im/skeleton-framework/skeleton-framework.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Just testing


Creating custom left handed copy/paste commands

I am left handed and it's always annoying to use a laptop and trackpad and copy and paste a bunch of stuff repeatedly. I've been using karbiiner for a while but never got the custom commands to work. I'm trying to make ⌘ + . copy and then ⌘ + / paste.
I've created a file ~/.config/karabiner/assets/complex_modifications/cp.json and here's what I have so far:
{
    "title": "Left handed copy/paste",
    "rules": [
        {
        "description": "⌘ + . | Copy",
        "manipulators": [
            {
                "type": "basic",
                "from": {
                    "key_code": "period",
                    "modifiers": {
                        "mandatory": [
                            "command"
                        ]
                    }
                },
                "to": [
                    {
                        "key_code": "copy"
                    }
                ]
            }
        ]
        },
        {
            "description": "⌘ + / | Paste",
            "manipulators": [
                {
                "type": "basic",
                "from": {
                    "key_code": "slash",
                    "modifiers": {
                        "mandatory": [
                            "command"
                        ]
                    }
                },
                "to": [
                    {
                        "key_code": "paste"
                    }
                ]
            }
            ]
        },
    ]
}

This isn't showing up when I try to add a new Complex Modification. Any suggestions?

an easier solution is to just use Ukulele and change those keys when the command key is pressed to ctrl+c and ctrl+v


Add cmd/gopherlings exercise runner

Thanks for starting this project! I had a lot of fun with Rustlings, and I'm excited to see the same kind of beginner content come to Go.
The rustlings command was a big part of what made that fun for me, so I wrote a small watcher for myself as I worked through Gopherlings. I saw that this helper program is in the roadmap for this project, so I tried to clean it up for general use.
I borrowed the Rustlings "I AM NOT DONE" comment (now with a Go pun!) for similar reasons:

It encourages learners to keep playing with finished exercises.
Identifying unfinished exercises by running them isn't always possible. For example, 024-method already runs without errors, and 010-forever is an infinite loop.

Go compiler output is generally terse, so I tried to separate gopherlings output from go output during the watch loop with spacing and colors. I saw some reports online that the usual screen-clearing escape sequence works on modern Windows, but I can't easily test it myself. I'd probably use github.com/inancgumus/screen otherwise.
There's a bunch of future work available here:

A hint subcommand or interactive hints during the watch command.
Allow run to take an argument that runs a specific exercise.
Add a subcommand to run all exercises and check them against expected output.
Catch errors that prevent gopherlings from running exercises (like an incomplete Go installation).

Last thing: I wrote a lot of text like help strings and the big success message. Since they may not fit with the flavor or personality you want for this project, I'll gladly rewrite or delete any of it that you point out.

Hey there-
First of all, big thanks for the help! I just tested your tool and it really is delightful to work through exercises with it. Overall I am pleased with it, colors, command help message+output and all. Great user experience feel to it.
I have but one qualm regarding running the exercises and that is that they currently run indefinitely (infinite loop for the forever problem) and can print out unlimited text, blowing up command line.

This could be helped modifying the Run method to pass a context.WithTimeout to execFile, 5 seconds ought to do it I think, we don't have any time exercises yet.
The latter could be fixed by io.LimitReader and Reader/Writer stream wrapping.

That said, these are not requirements to getting this PR merged. Far more important is adding instructions to the README.md. I'd remove the mention of air and replace it with installation instructions of gopherlings using something of the sort:
go install github.com/soypat/gopherlings/cmd/gopherlings@latest

So to recap:

Add gopherlings installation instructions to README.md and VERY basic usage example
Add exec timeout, 5 seconds?
Limit gopherling output to, say 10.000 bytes?

If you are not available for contributing these features let me know and I'll merge this gem and work on it sometime next week.

Add gopherlings installation instructions to README.md and VERY basic usage example

Done! I also updated the roadmap while I was here.

Add exec timeout, 5 seconds?

Done! That was a great idea :smile: It made the error handling a bit more complicated but also a bit more precise.

Limit gopherling output to, say 10.000 bytes?

This is the one I didn't do. I think it's also a great idea, but I ran out of time to work on it myself today!

Looks AWESOME to me! Merging!


nh: fix darwin build

Description of changes
Fix failing to build on Darwin due to missing dependency.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

I do not own a Darwin machine to test, also I never remember, whether we are moving away from or towards passing darwin instead of individual SDK members.
I will therefore neither approve nor request any changes, but feel free to ping me for a merge after approval has been given.

I don't have any macos machine to to aprove or request changes

More than 13 hours of waiting is totally unbearable, is there anyone who can confirm that this is building fine on aarch64-darwin ?

More than 13 hours of waiting is totally unbearable, is there anyone who can confirm that this is building fine on aarch64-darwin ?

Yes I can confirm it.

Thanks

Thanks!


Urgent review of ICS dose measure

trelegy elipta now changed BNF code - even more reason to check

https://github.com/ebmdatalab/openprescribing/pull/4757


Add version to ProgressBar object

ProgressBar.version should return current version

require('package.json') is possible but it would bloat the distributable with the whole json file. best option is probably regex replace in main.js

Workaround:
> var p = require('progressbar.js/package')
undefined
> p.version
'0.8.1'


Allow redirection and pipe operators in Dodo.run

This can be achieved via `Dodo.runcmd(['/bin/bash', '-c', 'echo hello > /tmp/foo.txt'])


Unable to find package 'Microsoft.Azure.Management.ResourceManager'

Following instructions, I get this unable to find package error.  Nuget (https://www.nuget.org/packages/Microsoft.Azure.Management.ResourceManager) shows the one to get.
Install-Package Microsoft.Azure.Management.ResourceManager -Version 2.0.0-preview

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

ID: 1ebc0c44-b401-1f1f-2ed5-7928918e49b4
Version Independent ID: 52517770-de52-18b3-7bf6-078c18b70fe6
Content: Create an Azure data factory using .NET
Content Source: articles/data-factory/quickstart-create-data-factory-dot-net.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

@steveaf I'm able to install the package after creating the visual studio project.
PM> Install-Package Microsoft.Azure.Management.ResourceManager -Version 2.0.0-preview

Could you please share the screenshot of the error message, in order to understand the issue?

You are very quick  - thanks.
The instructions have the line below that fails for me in NuGet PM.
Install-Package Microsoft.Azure.Management.ResourceManager
I found the complete line, with version, that works and pasted that.  The instructions should update this line
Install-Package Microsoft.Azure.Management.ResourceManager
to
Install-Package Microsoft.Azure.Management.ResourceManager -Version 2.0.0-preview
[cid:61c22681-5390-416c-9caf-d7c88d2e18b3]

From: CHEEKATLAPRADEEP-MSFT<EMAIL_ADDRESS>Sent: Wednesday, March 6, 2019 5:42 AM
To: MicrosoftDocs/azure-docs
Cc: steveaf; Mention
Subject: Re: [MicrosoftDocs/azure-docs] Unable to find package 'Microsoft.Azure.Management.ResourceManager' (#26350)
@steveafhttps://github.com/steveaf I'm able to install the package after creating the visual studio project.
PM> Install-Package Microsoft.Azure.Management.ResourceManager -Version 2.0.0-preview
[image]https://user-images.githubusercontent.com/44426401/53878765-baeac000-4032-11e9-9227-64cc42f135fe.png
Could you please share the screenshot of the error message, in order to understand the issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/26350#issuecomment-470076911, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABoduNaV0KrOHbD9wkDy35pk9kCvo4PQks5vT6m7gaJpZM4bgqHz.

@steveaf I completely agree with you.
As you see the version keep on changing every month. If we mentioned
“Install-Package Microsoft.Azure.Management.ResourceManager -Version 2.0.0-preview” in the document, then other user say this document need to be updated with the latest version every month.
The documents has designed to long term use, that the reason they have not mentioned the version in the cmdlet.
Hope this helps.

@steveaf We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


Fix ONNX Runtime Execution in Native Executable

The ONNX Runtime, which relies on JNI, requires specific configuration for native image compilation due to its unique code structure. This commit adds the necessary JNI configurations to ensure native execution.
Additionally, it consolidates the native instructions related to the ONNX Runtime by moving them from being spread across core and base-parsers to solely within the core module. This change reflects the broader applicability of local / in-process embedding models (requiring the ONNX Runtime) beyond RAG use cases.

Next step is to update the CI build to run the native tests.


Remove modernizr.js, we are not using it

Also remove no longer needed classes from root html element.
Fixes #245.

I'd prefer to see this tested thoroughly on ie8 and ie9. I don't think it's fair to say that we are not using modernizr here, as this seems to be pulling out the actual modernizr test classes that were in use -- that is lt-ie9 and no-js.

Yes, I pulled out lt-ie9 because it was only defined, but not actually used.

The css classes aren't used, but I believe modernizr was added to support html5 in ie8, replacing html5shiv.

OK, I tested with IE8 and looks like my pull request breaks things. Let's return to it when IE8 is no longer supported :)

@agjohnson Now that Microsoft stopped supporting IE < 10 more than two months ago, will you be OK with merging this?

Microsoft's support of IE doesn't shouldn't concern our usage. Looking at RTD traffic, IE < 10 makes up .4% of our traffic. What is the upside to removing support for modernizr? The focus of this theme is cross platform/device support, dropping this for no good reason will give these users a broken experience. For that, I'm still -1 on removing modernizr unless there is good reason.

If you wanted to look at the usage, you need to look only at IE 8, IE 9 works fine without modernizr. I'm the Ubuntu packager and not having the modernizr dependency will make life a bit easier for us. But having it is also fine, we can workaround that in our packaging.

Roger. IE8 is a much smaller portion of our traffic. I'd want to compare html5 support against our traffic patterns before we call off support for modernizr. It's been a few years since the theme was created, so the html5 support landscape has certainly shifted. IE and mobile are probably my larger concerns, though browsers without html5 support there are also both a fraction of our traffic.
One option would be to deprecate modernizr here and move the dependency to RTD, where we're most concerned about cross-platform support.


Some optimism config/constants are missing

Created a PR here https://github.com/balancer/b-sdk/pull/168


does not have valid gemspec

ruby_mapnik at /Users/chaos/.rvm/gems/ruby-2.0.0-p353/bundler/gems/Ruby-Mapnik-0b44e4838d54 did not have a valid gemspec.

This prevents bundler from installing bins or native extensions, but that may not affect its functionality.
If you need to use this package without installing it from a gem repository, please contact<EMAIL_ADDRESS>and ask them to modify their .gemspec so it can work with `gem build`.
The validation message from Rubygems was:
  [".yardoc/checksums", ".yardoc/objects/root.dat", ".yardoc/proxy_types", "README.textile", "ext/ruby_mapnik/_mapnik_geometry.rb.cpp", "ext/ruby_mapnik/_mapnik_geometry.rb.h", "ext/ruby_mapnik/_mapnik_glyph_symbolizer.rb.cpp", "ext/ruby_mapnik/_mapnik_glyph_symbolizer.rb.h", "lib/ruby_mapnik/ruby_mapnik.bundle", "lib/ruby_mapnik_config.rb", "test/nemis.sublime-project", "test/nemis.sublime-workspace", "test/test_mapnik_geometry.rb", "test/test_mapnik_glyph_symbolizer.rb", "tmp/rundemo.png", ".gemtest"] are not files

As far as I can tell, these filenames aren't in the mapnik.gemspec file any more, so closing.


Implement JobCenter features

To be implemented:

Add LDM upload capability
Choose to hide/display info from account settings (à la LinkedIn)

Changes in #323


Failed at the<EMAIL_ADDRESS>install script 'node bin/install'

During npm install, I received the errors below. I attached the npm-debug.log file as well by generating it with npm run test. Hope this information is helpful. Thanks!
sh: 1: node: not found
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>npm ERR! Linux 4.4.0-62-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v4.2.6
npm ERR! npm  v3.5.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn

npm ERR<EMAIL_ADDRESS>install: `node bin/install`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node bin/install'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the git-validate package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node bin/install

npm-debug-log.txt

Seems like there might be a problem with your existing git hooks, where the install script tried to install over the existing hooks, but it doesn't have permission (most likely).
You should be able to delete/rename those hooks by going into your .git/hooks, and it should work after that when you try to re-install.

Got similair results so renamed .git/hooks to take that out of the equation and also tried in a freshly npm init
Both tries still failing so wondering if it maybe is something else than hooks?
$ npm install git-validate

><EMAIL_ADDRESS>install /home/kimi/vizceral-example/node_modules/git-validate
> node bin/install

sh: 1: node: not found
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>npm ERR! Linux 4.4.0-47-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "git-validate"
npm ERR! node v4.2.6
npm ERR! npm  v3.5.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn

npm ERR<EMAIL_ADDRESS>install: `node bin/install`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node bin/install'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the git-validate package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node bin/install
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs git-validate
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls git-validate
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/kimi/vizceral-example/npm-debug.log

147 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>148 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
149 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/share/npm/bin/node-gyp-bin:/home/kimi/vizceral-example/node_modules/git-validate/node_modules/.bin:/home/kimi/vizceral-example/node_modules/.bin:/home/kimi/bin:/home/kimi/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
150 verbose lifecycle<EMAIL_ADDRESS>CWD: /home/kimi/vizceral-example/node_modules/git-validate
151 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'node bin/install' ]
152 info lifecycle<EMAIL_ADDRESS>Failed to exec install script
153 verbose unlock done using /home/kimi/.npm/_locks/staging-2c9ab73f2d53a43f.lock for /home/kimi/vizceral-example/node_modules/.staging
154 silly rollbackFailedOptional Starting
155 silly rollbackFailedOptional Finishing
156 silly runTopLevelLifecycles Starting
157 silly runTopLevelLifecycles Finishing
158 silly install printInstalled
159 warn optional Skipping failed optional dependency /chokidar/fsevents:
160 warn notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>161 verbose stack Error<EMAIL_ADDRESS>install: `node bin/install`
161 verbose stack spawn ENOENT
161 verbose stack     at ChildProcess.<anonymous> (/usr/share/npm/lib/utils/spawn.js:17:16)
161 verbose stack     at emitTwo (events.js:87:13)
161 verbose stack     at ChildProcess.emit (events.js:172:7)
161 verbose stack     at maybeClose (internal/child_process.js:821:16)
161 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
162 verbose pkgid<EMAIL_ADDRESS>163 verbose cwd /home/kimi/vizceral-example
164 error Linux 4.4.0-47-generic
165 error argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "git-validate"
166 error node v4.2.6
167 error npm  v3.5.2
168 error file sh
169 error code ELIFECYCLE
170 error errno ENOENT
171 error syscall spawn
172 error<EMAIL_ADDRESS>install: `node bin/install`
172 error spawn ENOENT
173 error Failed at the<EMAIL_ADDRESS>install script 'node bin/install'.
173 error Make sure you have the latest version of node.js and npm installed.
173 error If you do, this is most likely a problem with the git-validate package,
173 error not with npm itself.
173 error Tell the author that this fails on your system:
173 error     node bin/install
173 error You can get information on how to open an issue for this project with:
173 error     npm bugs git-validate
173 error Or if that isn't available, you can get their info via:
173 error     npm owner ls git-validate
173 error There is likely additional logging output above.
174 verbose exit [ 1, true ]

$ ls -a .git/
.   branches  description  hooks_org  info  objects      refs

ahh, your node binary is named "nodejs" not "node", i'll see if i can figure out a fix. a temporary workaround would be to make a symlink

Default Ubuntu install from what I remember.
Symlink fixes that problem, on that machine at least.

Bump. I also hit this issue. This is on a vanilla Ubuntu 14.04 install. See also https://stackoverflow.com/questions/18130164/nodejs-vs-node-on-ubuntu-12-04

The symlink work-around is OK, but I haven't hit this issue with any other NPM packages, so maybe you should look at what other packages are doing to avoid this problem.


Update card-image height

Addresses #56
Updated card-image height in sponsor page

Updated card-image height in communities page

Signed-off-by: db118<EMAIL_ADDRESS>

✅ By submitting this PR, I have verified the following

[x] Checked to see if a similar PR has already been opened 🤔
[x] Reviewed the contributing guidelines 🔍
[x] Added my name to the bottom of the list under the Credits section in the README.md with a link to my website or GitHub profile 👥

The perspective is off now for images

@fvcproductions Oh I didn't check well enough., @db118  can you try a fix?

The images would have to be all be the same dimensions for them to all have same height unless we did background images which is why I didn't use the extra class.

Ya background image is defi te way to go

@dvidsilva Yeah I can fix  it 😄

@db118 	@dvidsilva 	I am going to revert this until it's fixed in another PR since I want to share the website with some other Latinx folks and don't want them to see the images like that! 😛 👍


Website Optimize

I don't think that moving the css from being locally hosted to being hosted on a CDN will optimise the performance of the site, @PeterDaveHello

@Jameskmonger use cloudflare/cdnjs cdn in most cases will be faster then github.io I think

Best way is to measure it, you'd want to measure locally compressed vs cdn compressed.
By looking at it at face value, this will be quicker than current since the file is compressed.

Happy to give it a go, thanks @PeterDaveHello.


Security issue in Code Igniter Loader.php file by using eval() method

In codeignite3 for Loader.php file, eval() is being used like this:
echo eval('?>'.preg_replace('/;*\s*\?>/', '; ?>', str_replace('<?=', '<?php echo ', file_get_contents($_ci_path))));
This call to eval() contains untrusted input. If this input could be modified by an attacker, arbitrary PHP code could be executed on the server. The first argument to phpeval() contains data from the incoming HTTP request. The data from the incoming HTTP request originated from an earlier call to file_get_contents.
Can we not use Eval and use any other mencahnism???

you reported this on hacker one already.
Did you not read the security guidelines - if you suspect a secutiry issue, DON'T EXPOSE IT, like you have done here.


@Tom requires filling completely

This might be more of a functional expectation than a bug specifically, but keen to get your thoughts.
Ideally when I type "@to" the suggester box should show both @Today, and @Tomorrow, and then subsequently "@Tom" should show @Tomorrow.
Would simply save a lot of time as I wouldn't have to type out @Tomorrow completely, and I wouldn't have to take my hands off the keyboard to navigate down twice to select tomorrow.

Nevertheless, thanks for an awesome plugin 🙏

It works when you're writing "@tom" instead of "@Tom".

I think it should not be case sensitive, though.

@eikowagenknecht have created a PR implementing case sensitive suggestions. "@tom" fills out "tomorrow".

@eikowagenknecht have created a https://github.com/argenos/nldates-obsidian/pull/156 implementing case sensitive suggestions. "@tom" fills out "tomorrow".


How to use GLFM in a real android project?

I have a couple of questions on building and using GLFM on android thought of making it into one issue since I couldn't find one single tutorial on how to use this.

What is happening in the CMakeLists.txt file in examples folder? Why there isn't the add_executable() function. ?

Can I include GLFM with add_subdirectory(path/to/glfm) and link it with my project with target_link_libraries(project glfm)?

What about in source build support?

How would I compile it with Gradle?

I am sorry if I missed something in the README file.
Anyway, Thanks in advance!

add_executable is called in the GLFMAppTarget.cmake file that's included here and uses the parameters set previously in that file.
Yes
Should work the same as with any CMake project
CMake doesn't have an Android generator, so you have to create a project yourself in Android Studio. Then follow the directions here.

Ok, Thanks!


Adding dynamic accessors and mutators from $uuidAttributes and customising uuid text attribute suffix

This PR references this PR by @westphalen and also this issue #45 and #33 . It also makes the default uuid text attribute suffix customizable with support for composite keys without breaking original code. Details are on README.md file on this PR branch.
Thanks in anticipation.

Good point, though the correct name would be binaryUuids, no?

It is unlikely that you store binary and string UUIDs at the same time in the model. So I would go with the shortest option for simplicity.

@brendt The only previously existing method in the HasBinaryUuid trait that was modified by this PR is toArray() and the modification was done transparently. The main aim of this modification was to provide for 2 things without changing the way toArray() originally worked before.

Adds support for other uuid columns in the table for any Model using HasBinaryUuid besides the primary key uuid to be decoded to their UUID textual representation.
Adds support for composite primary keys on any Model which happen to be uuids

All other code modifications are additions/insertions that do not interact with previously existing methods in a stateful way. In the event that a developer duplicates related or primary keys in the $uuids array or in a composite primary key, all duplicates are removed before decoding commences.

Yes there are @vpratfr

Any merge for this PR coming soon ?

Yes.

Released as 1.2.0: https://github.com/spatie/laravel-binary-uuid/releases/tag/1.2.0

Super!


ONNX only supports point prompts and box prompts. How to segment everything with onnxruntime?

Hi,
ONNX only supports point prompts and box prompts. How to segment everything with Onnxruntime or TensorRT?
By the way, is there a plan to add C++ inference demo?
Thank you!

We have supported segmenting everything with Onnxruntime/TensorRT. Please check the following README file:
https://github.com/mit-han-lab/efficientvit/blob/master/demo/sam/README.md

Thanks for your reply.
I have read this document and the codes. It uses the api of SAM to segment everything.
If I code with C++, how could I achieve this task?


enhancement: allow configuration for transport modules

Idea:

Especially when using stateful transport modules, i. e. those based on techniques like WebRTC, it might be reasonable to give them the opportunity to take configuration parameters.
Transport modules like WebRTC need to tunnel signalling messages through other peers. For that reason, they need to be able to dial peers by using other transport modules.

Implementation:

instantiate transport modules with given configuration object
pass internal switch instance to the newly created transport module instance

What's missing:

let transport modules specify their own configuration parameters and extend src/config.js at startup appropriately

Switch should really just get passed in with the options and interface-transport docs should get updated to document that that's the case, rather than being a secondary param.
const options = { ...this._config[Transport.name], switch: this._switch }
new Transport(options)

Also, Transport.name is not safe with minification, so that will need to change.

I think this is solved by b06ca1b 👍
Thanks :-)


I like your Alfred Theme! Could you share that?

Thanks!

Hei @qinix,
here you go https://github.com/michelegera/alfred-snazzy
I've done some slightly adjustments in font and margin sizes.


maxTime not working with showDateTimePicker

As the title suggests whatever maxTime I put it doesn't seem to matter, it gives option for any day.
The example I am using right now is:
onPressed: () {                     DatePickerBdaya.showDateTimePicker(context,                         showTitleActions: true,                         minTime: DateTime.now().add(Duration(days: -7)),                         maxTime: DateTime.now(),                         onChanged: (date) {}, onConfirm: (date) {                       print(date);                     }, currentTime: DateTime.now(), locale: LocaleType.en);                   },
the UI gives me option to select tomorrow, which should not be possible.

Fixed it by doing this small hack
maxTime: DateTime.now().add(Duration(milliseconds: 1)),

the problem is somewhere here https://github.com/Bdaya-Dev/flutter_datetime_picker/blob/deadb732608125bb9f91b63cf9e5c1c129f50e25/lib/src/date_model.dart#L520C43-L520C43, I will do some testing for this sometime at the weekend

Itss alright, as long as we have a workaround its not urget :)

Hi - this still appears to be a problem, any ideas why?
Thanks!


Fix-338

Related issues: https://github.com/apache/incubator-dubbo-admin/issues/338

Codecov Report

Merging #346 into develop will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop     #346   +/-   ##
==========================================
  Coverage      22.37%   22.37%
  Complexity       290      290
==========================================
  Files             76       76
  Lines           3142     3142
  Branches         526      526
==========================================
  Hits             703      703
  Misses          2364     2364
  Partials          75       75

Continue to review full report at Codecov.

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

@zhaoyuguang Thanks for your contribution


Cookbook fails to install GPG key

When depending on this cookbook on a CentOS 6 machine, I get an error that Chef 11.18.12 is unable to locate the GPG key file:
 Recipe: yum-docker::default
         * cookbook_file[/etc/pki/rpm-gpg/RPM-GPG-KEY-Docker] action create
           - create new file /etc/pki/rpm-gpg/RPM-GPG-KEY-Docker
           ================================================================================
           Error executing action `create` on resource 'cookbook_file[/etc/pki/rpm-gpg/RPM-GPG-KEY-Docker]'
           ================================================================================

           Chef::Exceptions::FileNotFound
           ------------------------------
           Cookbook 'yum-docker' (0.3.0) does not contain a file at any of these locations:
             files/centos-6.7/RPM-GPG-KEY-Docker
             files/centos/RPM-GPG-KEY-Docker
             files/default/RPM-GPG-KEY-Docker

           This cookbook _does_ contain: ['RPM-GPG-KEY-Docker']

           Resource Declaration:
           ---------------------
           # In /tmp/kitchen/cache/cookbooks/yum-docker/recipes/default.rb

            22: cookbook_file '/etc/pki/rpm-gpg/RPM-GPG-KEY-Docker' do
            23:   source 'RPM-GPG-KEY-Docker'
            24:   mode '644'
            25:   owner 'root'
            26:   group 'root'
            27: end
            28:

           Compiled Resource:
           ------------------
           # Declared in /tmp/kitchen/cache/cookbooks/yum-docker/recipes/default.rb:22:in `from_file'

           cookbook_file("/etc/pki/rpm-gpg/RPM-GPG-KEY-Docker") do
             provider Chef::Provider::CookbookFile
             action "create"
             retries 0
             retry_delay 2
             guard_interpreter :default
             path "/etc/pki/rpm-gpg/RPM-GPG-KEY-Docker"
             backup 5
             atomic_update true
             source "RPM-GPG-KEY-Docker"
             cookbook_name "yum-docker"
             mode "644"
             owner "root"
             group "root"
             recipe_name "default"
           end

The RPM-GPG-KEY-Docker needs to be moved into the default subfolder if this cookbook is intended to work on Chef 11 (which it states should be supported in the README). The ability to fetch files from the root of files (without 'default') is a new feature in Chef 12.


Introduce ChimeActivity class

I created a ChimeActivity class for managing activities in the application. This PR replaces every place we were creating an independent activity object with an instantiation of the class.
Part of the work towards completing #519

Looks like great progress. I like how much more clearly it expresses that certain code is closely related.


Feature easy setup

some features hopefully making the initial setup for new users easier

I'm very concerned about the way vdir discovery is done. A proper solution for vdir-discovery would be language independent and provide a stable interface -- using vdirsyncer's internal APIs for reading its configuration file is neither. I also think that khal currently depends too much on internal APIs of vdirsyncer. Yesterday I've tried to factor out the filesystem storage into its own package: https://github.com/vdirsyncer/python-vdir
In my mind there are two ways to provide vdir discovery:

vdirsyncer exposes a simple CLI command to list all vdir paths.
There are standard locations for tools to look for vdirs.

The first solution is much more flexible, but unfortunately requires the installation of vdirsyncer for any sensible use of vdirs, while khal would normally be perfectly able to run on its own, without sync.
The second solution comes with the problem that the user no longer explicitly defines where their data is stored. I think that's somewhat problematic from a UX perspective. It's also completely inflexible.

I agree that using khal for vdir access isn't great and I do welcome the vdir package.
But for this setup helper I do not see much harm. Worst case: user need to configure by hand is is the case now. We might want to wrap it in some more try/except blocks.
My approach here is this: it works (for now), it won't delete any data and lets worry about the future (i.e. when vdirsyncer changes its internals) when its here.
Furthermore I would suggest telling the user the standard place for calendars (which is to be determined) and suggest they use that and have khal's setup function searching that by default, too.

There are standard locations for tools to look for vdirs.

Furthermore I would suggest telling the user the standard place for calendars (which is to be determined) and suggest they use that and have khal's setup function searching that by default, too.

~/.local/share/calendars seems like a sensible location for placing calendars, which could be the default.
Maybe the "default" or "recommended" location could also be mentioned in the vdir spec?

I like multi better than multi-calendar, even though multi-calendar is more explicit


ARM64 support

I'm pretty sure that the project just needs to be rebuilt with the latest Xcode to support ARM64 natively.

It works on my M1 Mac Mini. Just download the project, import it to XCode and build it.

It works on my M1 Mac Mini. Just download the project, import it to XCode and build it.

Works perfectly fine if you manually re-build the project.
For the laziest here, I uploaded some native binaries in my fork here.
@Cyberbeni wanna try them out to tell me if they works fine for you?

@iwa Could you help me troubleshoot the following? I rebuilt the project, but I wanted to export the binary the proper way by choosing Product > Archive in Xcode and then choosing the Distribute option to place the binary in some folder. When I do this the supposed universal binary does not appear in the Activity Monitor after I try to run it. If I simply run the Debug build in Xcode it does run and function properly. Did you put the debug binaries or the distribution binaries in your fork? I would like to compile new ones and put them in this repository as well.

I included universal binaries in release v0.1.1u.

@emreyolcu sry!!! I didn't see the mention notification and didn't check the issue till now 😭
I had some troubles when testing the new version, I had to totally uninstall the old one and install the new universal, then restart, to make it works properly
anyways, it seems fixed for you now, I'll be locking my fork and redirect the download link to yours now

@emreyolcu sry!!! I didn't see the mention notification and didn't check the issue till now 😭 I had some troubles when testing the new version, I had to totally uninstall the old one and install the new universal, then restart, to make it work properly
anyways, it seems to bed fixed for you now, I'll be locking my fork and redirect the download link to yours now

Thanks a lot for testing it!


Split Iris course into multiple notebooks and improve first 2 sections

This is to replace #148 and pull together various changes from @lbdreyer and myself
On feature branch, I will self-merge !!

Need a beta tester?

@mo-g Need a beta tester?

Maybe soon ...
But first I need to pull together a bunch of ideas on several different branches of mine and @lbdreyer, then I will make a proper first-step-forward proposal.
Currently mired in tooling problems + confusion over the merge !!
Notebooks are still awful for version control.
I wish jupyter could input from a simpler plaintext format ...
Apparently there is https://github.com/mwouts/jupytext.  Hmmm ....

Beware, beware of scope creeeeeep! :wink:


Proxy requests

What's the Lightning way of proxying API requests during development?
I'm looking for something like this.
Also, is there a way to run/bundle Lightning with Webpack or Vite?

Hi @smercadova, you can use the Lightning-CLI to build and serve your project.
The Lightning-CLI has an environment variable (LNG_SERVE_PROXY) that might be exactly what you are looking for.


test(skip): add test against breaking unsubscription chain

For issue #875.

Merged with d2bd860, thanks @staltz


remove unused icloud argument cracw that cause parse failure in orche…

…stration mode run
Description
Include a summary of the change and which issue is fixed. Please also include
relevant motivation and context. List any dependencies that are required for
this change.
Fixes # (issue)
If this is a hotfix to a released version, please specify it
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also note
any relevant details for your test configuration (e.g. compiler, OS).  Include
enough information so someone can reproduce your tests.
Checklist:

[y] My code follows the style guidelines of this project
[y] I have performed a self-review of my own code
[y] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] Any dependent changes have been merged and published in downstream modules
[y] New check tests, if applicable, are included
[ ] Targeted model, if this change was triggered by a model need/shortcoming

It makes sense to consolidate into a single PR.  @xyuan - can you redirect this PR into the same source branch as #15?

close this PR to add this to PR#15


Consolidate bit_indices as a circuit property

I'm wondering if it makes sense to carry this around in the circuit object itself (maybe as a private). Pretty much anything that is going from a circuit to something else is now building this dict.
Originally posted by @mtreinish in https://github.com/Qiskit/qiskit-terra/pull/5504#discussion_r583153333

There were also a few with warnings.catch_warnings(): added in #6069 that should be resolved here.


[RFC]: refactor blas/ext/base/sdsapxsum to follow current project conventions

Description
This RFC proposes refactoring @stdlib/blas/ext/base/sdsapxsum to follow current project conventions.
These conventions are outlined in more detail in https://github.com/stdlib-js/stdlib/issues/788. Namely, we want to migrate from C++ add-on interfaces to C add-on interfaces and then make various style and simplification changes.
Some example commits which perform most, if not all, of the requested changes include https://github.com/stdlib-js/stdlib/commit/d66d80cfcbab1da95cb5ae8cfae4a1fc4c5129d1 (saxpy),  https://github.com/stdlib-js/stdlib/commit/3c82fe7b6c0f9fd6ef02c86d6e2024d708ac8c14 (cswap), and https://github.com/stdlib-js/stdlib/commit/5b15c9675be434c0e11b1ec1e1f78d7b089abbcd (dasum).
Related Issues
Related issues #788, #1152.
Questions
No.
Other
No.
Checklist

[X] I have read and understood the Code of Conduct.
[X] Searched for existing issues and pull requests.
[X] The issue name begins with RFC:.

@Planeshifter, Excited to work on this issue, can I get assign?


Does --is-full-object have to come before --properties ?

I got this error:
--is-full-object: command not found
from this command:
az resource create \
    --resource-group $imageResourceGroup \
    --properties @helloImageTemplateWin.json \
    --is-full-object \
    --resource-type Microsoft.VirtualMachineImages/imageTemplates \
    -n helloImageTemplateWin01

This could be a problem with the bash shell treating --is-full-object as a separate command.  I solved it by moving --is-full-object before the --properties line.  The other examples and docs show --is-full-object preceeding the --properties argument.

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

ID: cd4c4f41-2050-234e-e35b-750158cfba54
Version Independent ID: 09c0145e-fa2b-210d-d1a0-4acb8c790bc3
Content: Create a Windows VM by using Azure VM Image Builder - Azure Virtual Machines
Content Source: articles/virtual-machines/windows/image-builder.md
Service: virtual-machines
Sub-service: image-builder
GitHub Login: @kof-f
Microsoft Alias: kofiforson

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

@dwschulze
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly
@kof-f
Can you please check and add your comments on this doc update request as applicable.


[UI] Inconsistency in Recovery seed recovery phrase backup phrase

Hey guys, love the wallet, been a while since I last used it, major improvements since the early releases.
I've tasked myself to look into the UI of Phoenix and I've teared down screens in Figma.
One of the first things that caught my eye is inconsistency in naming of Recovery phrase.
If you go to > Settings > Recovery Phrase the screen you see refers to the same thing with different names. Naming these inconsistently may lead to user-confusion, so I would like to propose the unification of the term.

In the Bitcoin Design Guide, we've named it Recovery phrase but I think Backup phrase is also great. If in the future there's  multilingual option to the wallet, phrase is easier to translate.
What do you think, would this be something you'd like to unify thought the wallet?

By the way if these sort of suggestions are useful to you guys, I can post a few more as a separate issues.

Hey, thanks for reporting those issues and also for the review on Figma. I think Recovery phrase works well but it's a bit long and descriptive, and it does not really convey the fact that it is private and secret. Lately I've been using private key or simply key, because it's a short word, and everyone knows what a key is and that it must be kept safe.
So I think we should unify the naming and use key as the shorthand (not seed) and recovery phrase to describe what that is.


Belch cannot be selected if the Pokemon has not eaten a berry

https://www.youtube.com/watch?v=paMtFIVWRkQ&t=6m33s

Should I remove Belch's TryHit handler? It shouldn't ever be called now since the move can't be selected normally, and it can't be called by Metronome or Assist.

Yeah, the TryHit bit is unnecessary now. This is a lot better than the ugly hardcoded way I was going to fix it last year (in BattlePokemon#update)! :+1:

Well, I can't think of any hardcode way that would even be different from what I'm doing now, it'd just be the same thing but near the ModifyPokemon event, right? After all, disabling moves used to be handled there before I refactored it.

At any rate, this is basically ready to merge, yes?

la la la


Deprecate godep in favor of Go Modules (new official dep. mgmt. tool)

Please switch and document for developers how to use/build with "Go Modules"; see
https://github.com/golang/go/wiki/Modules
https://levelup.gitconnected.com/switch-to-go-modules-from-go-dep-fcdd4aa41bd5
Please note that client-go chose to use govendor which has numerous problems: for reference: https://github.com/apache/openwhisk-client-go/pull/113/files

Why not go modules? All other golang dependency management tools are afaik deprecated in favor of it.

I also have felt the project structure of OpenWhisk cli families(client-go, cli, wskdeploy) is somewhat different from the other Go projects and I have wondered the reasons.

@markusthoemmes i am open to whatever the "approved" toolchain from GoLang... I will read up on go modules, but had seen other Google lead projects using "dep" and had only read blogs indicating "dep" was the latest/approved dep. generator/updater for Go.  Thanks for the info!

@style95 @markusthoemmes my main concern was that ALL our clients that are based on GoLang (CLI, client-go and wskdeploy) all use the same (and latest approved dependency tooling) and each did not each use different ones that were chose "ad hoc" and had different pitfalls.  This was a direct response to a PR in go-client that I merged that had a bogus vendor.json file with tons of invalid dependencies and was dismayed to see no uniformity.

Go modules is definitely the way to go. All projects still on dep are only there because they have some legacy considerations and/or don't want to switch yet cause it has an impact.
If you need to switch tools anyway, definitely go with go modules.

Any PR should be coordinated with similar Issue/requirement in wskdeploy:
https://github.com/apache/openwhisk-wskdeploy/issues/1082


Feature/nbpkg build

extension requeired by nbpkg-build (basepkg distribution system).

new command line options added.
_mk_depend() and _mk_pkg() enhanced to reflect dependence specified by nbpkg-build.

@fmlorg
It seems to happen a lot of conflicts without basepkg.sh. Did you track the changes of upstream?

Thank you. Merged it.


Start python bindings

Hi @andrewyatz,
I'm a grad student in @nsheff's lab, and he said he's using the checksum calculator in one of the sequence collections pipelines. He pointed me at the implementation, and it looks like its using subprocess calls because this crate is only offered as a cli. I thought this was a great opportunity for some python bindings using pyo3.
I implemented basic Python bindings for just checksum calculation. I did a few things to achieve this:

Converted your core binary crate to a library + binary crate to abstract away the process_sequence function.
Change the checksumseq binary crate to import this new library crate.
I added a new bindings folder, which contains a new library crate following the maturin docs.
The bindings crate now imports the original library crate.
Fixed some things where I saw clippy warnings.

The bindings don't change any implementation of the core code, it just imports it and uses it.
To install and use in python
There are several ways to achieve this but the easiest is probably:

Create a new python environment

python -m venv venv
source venv/bin/activate

Install maturin, the companion package to pyo3.

pip install maturin

Navigate to rust_gc_count/bindings
Install the package:

maturin build

Use!

from gc_count import checksum

results = checksum("path/to/seqs.fasta")
for result in results:
    print(result.sha512)

This is fantastic to read and review. Very happy to bring this in as a library especially as it supports your work. My only additional request on top of what you've done here is to add the details above about installing the library in Python to README.md. Is that okay?

yeah! I will definitely add some python installation details. It will depend on how you want to distribute it. Theres a continuous integration yaml file that will auto-build wheels for all sorts of architectures and upload to pypi so one can just pip install...
... but that might be overkill. I don't want to add something that's going to eat into your GitHub actions minutes. @nsheff might be able to weigh in if he's got any requirements for how he builds/runs those pipelines.

Yeah, if that's ok with you. I'll still remove some of the obscure architectures it builds for (armv7, s390x, ppc64le) to save time and resource usage (unless you want those). Also, you might not need an API token for this. According to their docs, I believe this workflow supports using the PyPi trusted publisher workflow. So it's just a matter of linking the repo to the PyPi project.
Steps are probably:

make new pypi package, name it whatever you want
Link to this repo
Run the workflow?

I think we just need to make sure the names are consistent. I called the python package gc_count because import rust_gc_count didn't feel right for python 😵💫

Sounds good to me. Just created one called gc_count which is now in my pypi as the trusted environment. As for the architectures I did wonder about ARM but that's covered by aarch64. Otherwise I think we're good
Thank you

Okay going to merge and make a release. Wish us luck

One thing I just realised, the repo is currently licensed to EMBL. I believe your contributions should be linked to yourself or to UVA. Can you let me know what it should be and we'll add it to NOTICE and flag the appropriate bits of code

FYI I just realised the bindings are in a sub-directory so GitHub won't pick up on the CI right away. Will take a look later on today and see what I need to prod

FYI I just realised the bindings are in a sub-directory

Ah shoot, I recognized this too and moved it the project root. I committed the changes but never actually pushed them 🙃 Sorry about that. I can do another PR if you'd like or just let you take over. I pasted the most recent workflow file below. I got it setup to run each action inside the bindings directory.
Re:

believe your contributions should be linked to yourself or to UVA

I can get back to you on this one ASAP..
# This file is autogenerated by maturin v1.2.3
# To update, run
#
#    maturin generate-ci github
#
name: CI

on:
  release:
    types: [created]
  workflow_dispatch:

permissions:
  contents: read

jobs:
  linux:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        target: [x86_64, x86, aarch64]
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-python@v4
        with:
          python-version: '3.10'
      - name: Build wheels
        uses: PyO3/maturin-action@v1
        with:
          target: ${{ matrix.target }}
          args: --release --out dist --find-interpreter
          sccache: 'true'
          manylinux: auto
          working-directory: ./bindings
      - name: Upload wheels
        uses: actions/upload-artifact@v3
        with:
          name: wheels
          path: ./bindings/dist

  windows:
    runs-on: windows-latest
    strategy:
      matrix:
        target: [x64, x86]
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-python@v4
        with:
          python-version: '3.10'
          architecture: ${{ matrix.target }}
      - name: Build wheels
        uses: PyO3/maturin-action@v1
        with:
          target: ${{ matrix.target }}
          args: --release --out dist --find-interpreter
          sccache: 'true'
          working-directory: ./bindings
      - name: Upload wheels
        uses: actions/upload-artifact@v3
        with:
          name: wheels
          path: ./bindings/dist

  macos:
    runs-on: macos-latest
    strategy:
      matrix:
        target: [x86_64, aarch64]
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-python@v4
        with:
          python-version: '3.10'
      - name: Build wheels
        uses: PyO3/maturin-action@v1
        with:
          target: ${{ matrix.target }}
          args: --release --out dist --find-interpreter
          sccache: 'true'
          working-directory: ./bindings
      - name: Upload wheels
        uses: actions/upload-artifact@v3
        with:
          name: wheels
          path: ./bindings/dist

  sdist:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - name: Build sdist
        uses: PyO3/maturin-action@v1
        with:
          command: sdist
          args: --out dist
          working-directory: ./bindings
      - name: Upload sdist
        uses: actions/upload-artifact@v3
        with:
          name: wheels
          path: ./bindings/dist

  release:
    name: Release
    runs-on: ubuntu-latest
    environment: release
    permissions:
      id-token: write
    if: "startsWith(github.ref, 'refs/tags/')"
    needs: [linux, windows, macos, sdist]
    steps:
      - uses: actions/download-artifact@v3
        with:
          name: wheels
          path: ./bindings/dist
      - name: Publish to PyPI
        uses: PyO3/maturin-action@v1
        with:
          command: upload
          args: --non-interactive --skip-existing ./bindings/dist/*

I think start up a fresh PR with the changes and with your contributions too and let's build on these that you've done. Thanks for being so understanding


feat: update initial screen

WID-433

added common polymorphic component for typography
updated common button component

@michaelfurutin Can you also remove the bottom padding on the layout on md+ screens? to make the grid shrink to the bottom? Currently, it looks a bit off.

Screenshot

Not relevant due design updates


It's possible to move cursor off the chart in on the left side

Hi,
When scrubbing on the chart using the cursor, it's possible to scrub off the chart.
https://user-images.githubusercontent.com/768052/155680288-1ba18928-957f-475f-adc8-ea363dd900d6.mp4

Temporarily released under @sallar/react-native-wagmi-charts until this PR is merged.

Patch-package of the PR if anyone else has this problem
https://gist.github.com/cam-shaw/ac800e8abfdff13f2e5617e4bdf5fedc
Good work @sallar


Unexpected behaviour with variants

I wanted clarification on transitive package inclusion when using variants.  I have the following use case:

Package B package.py is:
name = "package_b"

version = "0.1.0"

requires = ["package_a"]

variants = [
   ["package_c"],
   ["package_d"]
]

...

With the following rez command:
rez-env package_b
I would expect package_b to bring in package_a which by requirement would include package_a and the package_a variant of package_b would be resolved.
Instead, both variants of package_b are being resolved such that:
rez-env package_b
...
resolved packages:
package_a-0.1.0  /dev/packages/package_a/0.1.0            (local)
package_b-0.1.0  /dev/packages/package_b/0.1.0/package_d  (local)
package_c-0.1.0  /dev/packages/package_c/0.1.0            (local)
package_d-0.1.0  /dev/packages/package_d/0.1.0            (local)

Am I misunderstanding how this should work?

This is effectively a demonstration of the mutual exclusivity issue.
package_b expresses that it is valid to resolve with package_c, and d via variants. Therefore, solving with either is valid.
package_b also expresses a requirement that it must solve with package_a. package_a in turn requires package_c, so the solve must have c. But nothing expresses that package_b's variant is invalid if package_d is selected when c is also present. All packages can co-exist, so effectively you are subject to the specific determinism of the solver.
The behavior you're looking for is expressed more like this (though is only valid with hashed variants because "!" in filepaths is generally a bad time for FS/OS/shell reasons):
name = "package_b"

version = "0.1.0"

requires = ["package_a"]

variants = [
   ["package_c", "!package_d"],
   ["package_d", "!package_c"]
]

Addressing this issue in a broader scope is an interesting discussion, but I wanted to post this explanation to give food for thought for the moment.

(I should add that if either package_a or package_c expressed a negation on package_d in their requirements, you would also get the expected result.)

This seems to fail on making the ["package_d", "!package_c"] variant as it's running:
rez-env package_a package_d '!package_c

Which results in:
Traceback (most recent call last):
  File "/apps/rez/bin/rez/rez-env", line 8, in <module>
    sys.exit(run_rez_env())
  File "/apps/rez/lib/python3.6/site-packages/rez/cli/_entry_points.py", line 144, in run_rez_env
    return run("env")
  File "/apps/rez/lib/python3.6/site-packages/rez/cli/_main.py", line 184, in run
    returncode = run_cmd()
  File "/apps/rez/lib/python3.6/site-packages/rez/cli/_main.py", line 176, in run_cmd
    return func(opts, opts.parser, extra_arg_groups)
  File "/apps/rez/lib/python3.6/site-packages/rez/cli/env.py", line 212, in command
    package_caching=(not opts.no_pkg_cache)
  File "/apps/rez/lib/python3.6/site-packages/rez/resolved_context.py", line 308, in __init__
    resolver.solve()
  File "/apps/rez/lib/python3.6/site-packages/rez/utils/memcached.py", line 267, in wrapper
    return func(*nargs, **kwargs)
  File "/apps/rez/lib/python3.6/site-packages/rez/resolver.py", line 120, in solve
    solver_dict = self._solver_to_dict(solver)
  File "/apps/rez/lib/python3.6/site-packages/rez/resolver.py", line 432, in _solver_to_dict
    graph_ = solver.get_graph()
  File "/apps/rez/lib/python3.6/site-packages/rez/solver.py", line 2258, in get_graph
    return self.get_fail_graph()
  File "/apps/rez/lib/python3.6/site-packages/rez/solver.py", line 2270, in get_fail_graph
    return phase.get_graph()
  File "/apps/rez/lib/python3.6/site-packages/rez/solver.py", line 1748, in get_graph
    and scope_r.conflicts_with(conflicting_request):
AttributeError: 'NoneType' object has no attribute 'conflicts_with'

I'm on an older version of rez (2.88.4) - has this been resolved in newer versions?

I agree, and this specific type of scenario is one that has produced a great deal of confusion that I have had to resolve with many colleagues over the years. I don't think that I consider the behavior a bug, as it's a clear result of a rather strict determinism and there are ways to address it by being more explicit in a rez request or in package definitions, but I do feel strongly that there is a solution that would remove confusion and make more explicit what is happening.
I specifically encounter the example of having a package that is varianted something like this:
variants = [
    [python-3.7],
    [python-3.7, maya-2050],
    [python-3.7, houdini-50],
]

The first variant is the "command line tool variant" that runs with a rezified python interpreter. The other two are built with their respective DCC-vendored interpreters. When asking for the package in a context without either of the other two, I would want the CLI one with a standard interpreter. But instead, I could get any of them. And I sure don't want to use maya's python interpreter when I don't need to.
The solution to my example is basically having "features" implemented completely, which would allow package definitions to be constructed with, say, a "cli" feature that can be requested, and is only present in the variant that I want to use via CLI.
In spite of not being completely intuitive at first, have you encountered any situation where having to be more explicit is causing an issue?
[...]
That stack trace sure looks like a bug though. :) I'm not sure if a newer rez fixes that issue, but if it's not difficult to update, it would be a very useful report. My intuition says probably, as I feel like I dealt with a similar issue that was eventually resolved, but I can't say for certain.

I have always considered this as a "bug". To me it's pretty non intuitive. We could make the solver a little bit more strict and limit itself to what matches (in this case C was requested by A, so pick that variant).
This has bitten soo many people. Yes "features" would help in some cases, but that's kind of the "expert" in the sense that features shouldn't be used to "fix" that behavior, but to do help the solver take decisions, which is kind of an advanced use case IMO.
That behavior is probably one of the features of rez that I dislike the most. I'd be worth having a discussion on what could be done to improve the experience of using variants, making them easier to use and understand, etc.

I think that even in the best-case scenario, you will still find people getting bitten unknowingly.
Let's pretend that the solver had a directive to "minimize the number of selected packages", in other words, not to pick the variant of anything that otherwise wasn't required.
Everything will be working just fine, until something that the user probably expected to produce a conflict. But suddenly, an entire other alternate resolve via the excess variant is an option, and would be selected, potentially wildly changing behavior while not presenting the user with a clear conflict when they may have been expecting that original solve. The lack of a conflict might be just as difficult to troubleshoot. And a conflict is rez primary feedback mechanism to let you know that your solve is not a good state.
I think that if mutual exclusivity is to be expected, that it needs to be expressed. The question to me is, is there a better way to express that than we have currently via negations, because ultimately maintaining negations in variants becomes a problem of exponential permutations and unmaintainable the more variants are in the mix.
(To be clear, I am not arguing that we shouldn't perhaps do as above, ensure solves solve with a minimum of packages required, but simply expressing that attempting to constrain mutual exclusivity has other "intuitive faults" as well.)

There are many possible things you may want to add in such a scenario. From order of requests over preferring the latest version over fewer packages or the other way round. I would also like to add that more transparency would likely be helpful to make it clear to the user why certain packages were choosen by the solver. While the stacktrace is possibly still a bug is there a typo in the request (the single quote prior to the negation request)?

@maxnbk

That stack trace sure looks like a bug though. :) I'm not sure if a newer rez fixes that issue, but if it's not difficult to update, it would be a very useful report. My intuition says probably, as I feel like I dealt with a similar issue that was eventually resolved, but I can't say for certain.

Tried with Rez 2.111.4 and got a different error:
================================================================================
Building variant 1 (2/2)...
================================================================================
Resolving build environment: package_a package_d '!package_c'
resolve failed, by<EMAIL_ADDRESS>on Fri Mar 10 16:26:34 2023, using Rez v2.111.2

requested packages:
package_a
package_d
!package_c
~platform==osx   (implicit)
~arch==x86_64    (implicit)
~os==osx-13.0.1  (implicit)

The context failed to resolve:
The following package conflicts occurred: (package_c <--!--> !package_c)

Resolve paths starting from initial requests to conflict:
  package_a --> package_a-0.1.0 --> package_c
  !package_c --> package_c

To see a graph of the failed resolution, add --fail-graph in your rez-env or rez-build command.

The build environment could not be resolved:
The following package conflicts occurred: (package_c <--!--> !package_c)

So looks like the workaround you stated does not work.

Hmm. Yeah, apologies - I hadn't realized it would become impossible to solve for package_c, ever, even during build, with that definition...

Okay, I have refined my use case and looks like the not requires (!) will solve my use case.  I redefine my use case as:

Defining the package_b package.py as:
name = "package_b"

version = "0.1.0"

variants = [
    ["package_d"],
    ["!package_d"]
]

Now the resolve works as expected:
rez-env package_b package_a

resolved packages:
package_a-0.1.0  /dev/packages/package_a/0.1.0             (local)
package_b-0.1.0  /dev/packages/package_b/0.1.0/!package_d  (local)
package_c-0.1.0  /dev/packages/package_c/0.1.0             (local)

And:
rez-env package_b package_d

resolved packages:
package_b-0.1.0  /dev/packages/package_b/0.1.0/package_d  (local)
package_d-0.1.0  /dev/packages/package_d/0.1.0            (local)
package_e-0.1.0  /dev/packages/package_e/0.1.0            (local)

I found where the bug you reported was fixed: https://github.com/AcademySoftwareFoundation/rez/pull/1184


Add chime switch to Honeywell

This PR adds a chime switch to Honeywell and a NotImplementedError to the base client. I’ve modified EnvisalinkSwitch to be more precise for bypasses, so I can add a separate chime switch.
On Honeywell, there is only one chime for all partitions (like the implemented panic), how would you like me to proceed?

Hi, thanks for the PR.  It looks good and I'll add similar support for the DSC once the changes are merged.
If you can fix the DCO error then I can merge the PR.

Done


Occasional memory corruption

There is an occasional memory corruption which cause an application using gltext to crash when loading a truetype font.
It can be reproduce it by running the gltext example at https://github.com/go-gl/examples/blob/master/gltext/truetype/main.go with DejaVuSans font instead, usually located at "/usr/share/fonts/truetype/dejavu/DejaVuSans.ttf" in ubuntu systems. It doesn't always happen, you may need to run it a couple of times until the problem occurs.

How is the memory corruption manifesting? What messages do you see? What platform are you on? I don't have much time for this right now, can you investigate further? If there is any specific way I can help let me know.

I found a fix for the problem, I will send a pull request soon.


Button coordination mobile/UI lib

I was trying to work with the Button component from the UI library, but it appears the one I needed to use is actually in the mobile code. It seems like the one in the UI lib needs to be updated, and the one in the mobile code needs to be removed?

Nvm here, I didn't realize there was already an issue bc opened in the wrong repo. https://github.com/leather-io/issues/issues/289


add *.iml in <project_root> and <sub_package_root> files to make ide like IntelliJ / WebStorm faster

Describe the feature you'd like to request
For huge monorepo, ide like IntelliJ / WebStorm will because slow, specifically in typescript monorepo.
we could add *.iml file for each sub packages like
<module type="WEB_MODULE" version="4">
  <component name="NewModuleRootManager" inherit-compiler-output="true">
    <exclude-output />
    <content url="file://$MODULE_DIR$">
      <sourceFolder url="file://$MODULE_DIR$" isTestSource="false" />
      <excludeFolder url="file://$MODULE_DIR$/.turbo" />
      <excludeFolder url="file://$MODULE_DIR$/node_modules" />
      <excludeFolder url="file://$MODULE_DIR$/dist" />
    </content>
    <orderEntry type="sourceFolder" forTests="false" />
  </component>
</module>

the excludeFolder list could from pipeline.build.outputs.
Then updates all *.iml into .idea/modules.xml
<?xml version="1.0" encoding="UTF-8"?>
<project version="4">
    <component name="ProjectModuleManager">
        <modules>
            <module fileurl="file://$PROJECT_DIR$/project.iml" filepath="$PROJECT_DIR$/project.iml"/>
            <module fileurl="file://$PROJECT_DIR$/packages/a/a.iml" filepath="$PROJECT_DIR$/packages/a/a.iml"/>
            <module fileurl="file://$PROJECT_DIR$/packages/b/b.iml" filepath="$PROJECT_DIR$/packages/b/b.iml"/>
        </modules>
    </component>
</project>

Final files added.
.idea/
   modules.xml
packages/
   a/
     a.iml
   b/
     b.iml
project.iml

*.iml could added into .gitignore too.
Describe the solution you'd like
Like melos from flutter did https://github.com/invertase/melos/blob/main/melos.yaml
We could add option { ide: { intellij: true } } in turbo.json to enable this feature.
Describe alternatives you've considered

I used put tsconfig.json in project root.
But when i start to use turbo, I prefer put tsconfig.json to  each sub package, which will slow down IDE, until I added *.iml files.

I have more than 10 sub-projects in my project. Starting with the latest version of WebStorm is slow, taking about a minute. I hope to solve the slow startup problem by enabling ide intellij: true.

I have more than 10 sub-projects in my project. Starting with WebStorm is slow, taking about a minute. I hope to solve the slow startup problem by enabling ide intellij: true.

if you use pnpm, here is another sollution to resolve this issue.
add node-linker = hoisted into .npmrc, and remove tsconfig.json in each sub project (or rename for building).
then set paths in tsconfig.json in workspace root like https://github.com/innoai-tech/nodekit/blob/main/tsconfig.json#L5-L10


site_config_dir is added split to each character

https://github.com/mcurlej/joft/blob/70eac8517b375bea51bbdabe01b007c971054944/joft/utils.py#L22
This adds each letter separately:
>>> import platformdirs
>>> possible_paths = set()
>>> possible_paths.add(platformdirs.user_config_dir())
>>> possible_paths.update(*platformdirs.site_config_dir(multipath=True).split(":"))
>>> possible_paths
{'g', 'x', '/home/churchyard/.config', 'e', '/', 't', 'c', 'd'}

set.update takes one or more iterables to add from one by one, not individual items to add. The * is unnecessary.

This was already fixed today in https://github.com/mcurlej/joft/pull/35


Vulnerability roundup 103: nss-3.44.4: 1 advisory [9.1]

search, files

[ ] CVE-2020-12403 CVSSv3=9.1 (nixos-20.09)

Scanned versions: nixos-20.09: 86d3781c390.

NixOS 20.09 is EOL, so this issue isn't actionable anymore (but fixed in 21.05+).


[Linux] install.sh: make the IsPackageInstalled function definition consistent

Description
According to the bash manual the function keyword is not really mandatory, other functions defined in the file have no this keyword as well.

Related issue: n/a
Check list

[n/a ] Related issue / work item is attached
[n/a ] Tests are written (if applicable)
[n/a ] Documentation is updated (if applicable)
[n/a ] Changes are tested and related VM images are successfully generated

/azp run ubuntu1804, ubuntu2004


async-storage is not working after importing as '@react-native-comiunity/async-storage

if I import async storage from react-native it only works in ios but can't import as react-native-community/async-storage.error is
Failed to load bundle(http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false) with error:(Unable to resolve module react-native-community/async-storage from /Users/conconsolutions1/Documents/projects/venture-trading-app/src/Screens/Login/LogInScreen.js: Module react-native-community/async-storage does not exist in the Haste module map

Hi @MalinPramoditha 	,
Did you follow getting started instructions ? Have you restarted Metro after installing new modules?

Hi @Krizzu
yes I restarted the metro bundler.y code is simple
class LogInScreen extends Component {     constructor(props){         super(props);         this.state= {           username: '',           password: '',         }       }       userInfo = {username: 'admin',password: 'admin'}       _login = async() => {         if(this.userInfo.username === this.state.username && this.userInfo.password === this.state.password){           await AsyncStorage.setItem('isLoggedIn', '1');           this.props.navigation.navigate('DashboardTab')         } else {           alert('wrong password')             }         }         _logout = async() => {           await AsyncStorage.clear();           this.props.navigation.navigate('Auth');         }     render() {         return (             <SafeAreaView style={{flex: 1, }}>                 <View style={{flex:1,justifyContent: 'center',}}>                     <MainInput  onChangeText={(username)=>this.setState({username})}  placeholder="Mobile Number"></MainInput>                     <MainInput onChangeText={(password)=> this.setState({password})} secureTextEntry={true} placeholder="Password"></MainInput>                 </View>                 <MainButtonColor onPress={this._login} style={{bottom: 0,position: 'absolute'}}>LOGIN</MainButtonColor>                 <Button title="logOut" onPress={this._logout}/>             </SafeAreaView>         )     } } export default LogInScreen;

class LogInScreen extends Component {
constructor(props){
super(props);
this.state= {
username: '',
password: '',
}
}
userInfo = {username: 'admin',password: 'admin'}
_login = async() => {
if(this.userInfo.username === this.state.username && this.userInfo.password === this.state.password){
await AsyncStorage.setItem('isLoggedIn', '1');
this.props.navigation.navigate('DashboardTab')
} else {
alert('wrong password')
}
}
_logout = async() => {
await AsyncStorage.clear();
this.props.navigation.navigate('Auth');
}
render() {
return (
<SafeAreaView style={{flex: 1, }}>
<View style={{flex:1,justifyContent: 'center',}}>
<MainInput  onChangeText={(username)=>this.setState({username})}  placeholder="Mobile Number">
<MainInput onChangeText={(password)=> this.setState({password})} secureTextEntry={true} placeholder="Password">

<MainButtonColor onPress={this._login} style={{bottom: 0,position: 'absolute'}}>LOGIN

)
}
}
export default LogInScreen;

Can you check if you have node_modules/@react-native-community/async-storage dir available?

Hi @Krizzu
yes node_modules/@react-native-community/async-storage dir is available

What version of Async Storage are you using?
Clean your transform caches with react-native start --clearCache

@MalinPramoditha How did you import it? What does the import/require statement look like? Did you include the @ symbol as well?

I'm using this package when I upgrade the storage of redux-persist
See issue here https://github.com/rt2zz/redux-persist/
When I use
import AsyncStorage from '@react-native-community/async-storage';
const persistConfig = {
  key: 'root',
  storage: AsyncStorage,
  ...
};

I got error saying [@RNC/AsyncStorage]: NativeModule: AsyncStorage is null.
My app is a react native app. Do I have to have access to native layer to use this package?

Same here :(

@stacywang0601 	@dante8300 Yes, you have to link the library, before you can use it. Please refer to docs or main README to learn how to do it. Remember to re-build your application after you link it.
And make sure you're not using Expo, as this won't work with it.

I am also having the same issue. I have reinstalled packages multiple times and linked them all. I can also see it inside my node_modules folder. I have reset cache with react-native start --reset-cache and removed build folder.
package.json
"react-native": "^0.59.10",
"@react-native-community/async-storage": "^1.5.0",

However, I have another project W using exactly the same version (1.5.0) and it works (I copy and paste the import statement from W to my project). The only difference is that W is using react native 0.59.9. It might be related to how I setup my packages because I haven't touched that project (not working one) for a while.

What platform are you having problems with? If it's Android, please manually check your main application for AsyncStorage instance (you can refer to my comment here).
Are you using React Native Navigation by any chance?

@Krizzu You are absolutely right. There is no new AsyncStoragePackage() there in my MainApplication.java (it worked before with only react-native link). I am using react native router flux which I believe is a wrapper around react navigation (not the wix one). Thanks for your help.

Closing this down. If you need more help, reopen it.

issue with netinfo and async storage :
"@react-native-community/async-storage": "^1.6.1",
"@react-native-community/netinfo": "^4.1.4",
"react-native": "0.59.9",
i had added new AsyncStoragePackage() and new NetInfoPackage() to mainApplication.java, when i run android the build is getting succeeded but app crashes on launch, please help

@diljithvandanam
Please check your adb logcat output and see where the crash is coming from.


I am getting new issue

Hello, everyone.
I ran this project, but I am getting this error.
<h4 style={color: red}>10:22:21:680 Agora-SDK [ERROR]: [4A5DB] Get server node failed [DYNAMIC_USE_STATIC_KEY] https://webrtc2-ap-web-1.agora.io/api/v1 DYNAMIC_USE_STATIC_KEY

has this issue been resolved ?

has this issue been resolved ?

@streamix-io are you having similar issue? this error means you have turned on token on agora dashboard, while using appid only while running your app

@streamix-io are you having similar issue? this error means you have turned on token on agora dashboard, while using appid only while running your app


KBR - KBR.PY

ENVIROMENT: production
URL: https://dev.laurentiumarian.ro/scraper/based_scraper_py/
Browser: Chrome
Device: laptop
OS: Windows 10
STEPS TO REPRODUCE:

Open API URL in browser
Type {"file": "KBR.py"} in "Content:" box
Click on the button "Post"
Check the result ( take a screenshot)
Open the careers section of the company website : https://careers.kbr.com/us/en/search-results?keywords=&p=ChIJw3aJlSb_sUARlLEEqJJP74Q&location=Romania
Check the number of jobs available for Romania
Compare it with the number of jobs from the API URL

EXPECTED RESULTS:
The number of jobs returned by the API URL for KBR should be the same like the number of jobs posted on the company website on the careers section .
ACTUAL RESULTS:
The number of jobs RETURNED by the API  URL for KBR is void,  the number of jobs posted on the company website on the careers section for Romania is 3.

Fixed!


Set up support on stackexchange for various CMSs

What happened (or feature request):
Stackexchange is probably one of the absolutely best support vehicles in the world: Good solutions are properly highlighted and live on and are easily searchable on google.
I'd suggest that we move our primary support channel to drupal.stackexchange.com (for Drupal) and similar venues for Wordpress and TYPO3. That means we'll need tags, and we'll need people to subscribe to the tags.
I was thinking about this in regard to the idea of a Freshdesk FAQ, and I think Stackexchange is ever-so-much better than that. And if we focus our support there, the quality of responses will rapidly rise.
What you expected to happen:
How to reproduce this:
Version: Please include the output of ddev version, docker version and the project's .ddev/config.yaml.
Anything else do we need to know:
Related source links or issues:
Please use a complexity rating of 1-5 (5 is high) for a feature request. (High complexity implies more PR planning)

We now have

A tag on Stack Overflow
Notifications in Slack when questions are created
I get email notifications from Stack Overflow as well.

#779 PR adds Stack Overflow to our support offerings and will close this out when it goes in.

LGTM and looks like the PR is ready to merge/close as well. Thanks!


Cant Use Different Arrows

Describe your bug here. If you are modding, try testing your bug in a clean version of the engine instead. Also, if you're using an older version of JSE, please try the latest version/action build. Also, be sure to check the pinned 'JS Engine: Known Issues' issue, to check if your issue hasn't already been found!
https://github.com/user-attachments/assets/01bce5ef-c04b-4b39-b7f2-8721cd09dc54
Command Prompt/Terminal/Crash logs (if existing)
No response
Have you identified any steps to reproduce the bug? If so, please describe them below in as much detail as possible. Use images if possible.
No

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
Nope.
If you use 1.12.0 or earlier, did you have Optimized Chart Loading turned on?
None
Did you check for any similar issues to what you're reporting? Check, then come back here. If there is a similar issue, then do not report the issue, otherwise it will be marked as a duplicate.
Yes

have you checked that the song doesn't just force a certain noteskin

closed due to no activity


dynparquet: Use parquet-go's copy rows

I think previously the only thing that was wrong was our usage ... we never called .Close(), which caused the goroutine opened by .Rows() to leak.
Roughly ~30% of the ingest path of Parca/Polar Signals Cloud is spent in this code, so hopefully this improves that.

Nevermind, looks like it's still leaking (leak tests detected it).

🤦♂ Managed to create exactly the same leak again by passing .Rows() in directly. Now not leaking anymore according to tests.

Waiting for https://github.com/segmentio/parquet-go/pull/420 to merge first.


The way to add pagination in both [top and down]

Hi there
This is not a issue as well, is just a comment for cases that you want to have pagination in top and down, go to DatatablesBuilder.php and  search  line  176  where start $output and add this lines
                           \"pagingType\": \"full_numbers\",
	        	\"sDom\": '<\"top\"lfprtip><\"bottom\"><\"clear\">',

Thank you for your contribution, I am going to add this to the documentation

You're welcome!

resolved a83eeab


[AutoDiff] Fix variedness propagation for apply inout arguments.

Propagate variedness from apply argument operands to apply inout arguments
(representing results). apply inout arguments are now correctly marked as
active, triggering non-differentiability errors.
Add ApplyInstBase::getInoutArguments for iterating over @inout and
@inout_aliasable arguments.
Add non-differentiability diagnostics and activity info tests.
Resolves TF-974.

@swift-ci Please test tensorflow


Added forceRender as an param also to Jotted

An option for #23 using Jotted's own forceRender

Closing in favor of https://github.com/ghinda/jotted/issues/23#issuecomment-252488430


Possibly helpful correlation in docs for class names + multiple chunk builds

Hey everyone (awesome) at MUI!
I just finished successfully troubleshooting a JSS styling issue largely in thanks to a lot of the existing discussion and documentation provided in this repo.
There was one facet of my issue that wasn't covered however that I feel like the docs could be expanded which is to include a mention about the runtimeChunk option in WebPack.
Briefly -- my scenario is that I'm producing a collection of components-per-chunk scripts that all rely on a common chunk.  All normal functionality in WebPack, but I realized that I was running the bootstrap stub multiple times.  Which of course for MUI meant I was getting multiple instances of the JSS css name generator (oops!).
What I think would be great is to link to this page in the docs somewhere near the FAQ item I linked above: https://webpack.js.org/configuration/optimization/#optimization-runtimechunk

@atrauzzi Oh yes! I think that we should be documenting the fact that bundlers might duplicate modules when code splitting 👍. Thanks for raising the issue.

Do you want to update the docs?

I can try!  What do I have to do? 😄

I believe we can add this other source of potential issue in the documentation section you linked: https://material-ui.com/getting-started/faq/#how-to-fix-a-class-names-conflict-in-production-

On it!  Stay tuned.


support for .ajax?

this library needs support for .ajax?

This is out of this library's scope as Sprint.js focuses exclusively on the DOM.


wslay: Sync with upstream 0e7d106ff

https://github.com/tatsuhiro-t/wslay/commit/0e7d106ff89ad6638090fd811a9b2e4c5dda8d40
Just a couple style fixes. Updating only so we know we don't have to review changes since upstream development seems dormant.

Cherry-picked for 4.0.4.

Cherry-picked for 3.6.


New tutorials

.NET Core
Objective-C
React Native
Swift

Docs Build status updates of commit 7570ba1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

breadcrumb/toc.yml
:white_check_mark:Succeeded

docfx.json
:white_check_mark:Succeeded

tutorials/dotnet-core.yml
:white_check_mark:Succeeded

tutorials/ios-objectivec.yml
:white_check_mark:Succeeded

tutorials/ios-swift.yml
:white_check_mark:Succeeded

tutorials/react-native.yml
:white_check_mark:Succeeded

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


feign.hystrix.enabled=true

I can't use Yaml or even set this property on a application.properties, it must be on the bootstrap.properties, is the only way to turn on the fallback. Took me some hours to figure this out.
Is this a bug or a expected behavior?

It doesn't sound like it should be a problem. It is not expected behavior.

I am unable to duplicate the problem (it works fine in application.properties). Can you provide a sample that recreates the problem?

You're right, it works on application.properties, I should have done something wrong. But still does not work on yml files.

Works fine in application.yml for me as well.

Oh God!  The error was a space character...
Thanks for being patient and my apologies for wasting your time.


Work Timeline - Default View

As a User
I want to be able to see the work information in a timeline representation
so that I can do strategic planning
Acceptance Criteria
Scenario 1:
GIVEN User with IDIR logged in the system
WHEN My Workplans is loaded
THEN Next to 'Name' Workplans I can see two buttons:

Grid button (selected)
Timeline button (default)

Screenshot

link to prototype - https://www.figma.com/file/GsrDa5tsU1xWj8MGPfylCs/Development-(Issues_Status_Dashboard)-(Copy)?type=design&node-id=3738-34955&mode=design


chore(main): release core-js 1.2.2-experimental

:robot: I have created a release beep boop
1.2.2-experimental (2024-11-06)
🧹 Chore

release main (f7b36f3)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/open-socket/js-sdk/releases/tag/core-js-v1.2.2-experimental :sunflower:


3D CNN model using transfer learning

I'm now trying to build specific model such as in paper
https://pubs.acs.org/doi/10.1021/acs.jcim.8b00350
rather than model using crossdock or PDB_bind
to make specifc model, I'm now trying to do transfer learning as in above paper
Can I use the train.py script in https://github.com/gnina/scripts with
previously trained snapshot with crossdock or PDB_bind as an argument in option '-c'
?

one another question is that
for in built model in gnina , I found that
*.caffemodel file can be retrived using command dumpmodel
Can we retrieve *.solverstate file for gnina in built model?

I'm now trying to build specific model such as in paper
https://pubs.acs.org/doi/10.1021/acs.jcim.8b00350
rather than model using crossdock or PDB_bind
to make specifc model, I'm now trying to do transfer learning as in above paper
Can I use the train.py script in https://github.com/gnina/scripts with
previously trained snapshot with crossdock or PDB_bind as an argument in option '-c'
?

Can I try transfer learning  as shown above with '-c' option in train.py script?

Thanks for your reply, then  can I try transfer learning with simple modification of train.py in your repository github.com/gnina/scripts ?

The -c argument takes an integer specifying an iteration and assumes file naming conventions follow what is in train.py.  You can certainly modify train.py to train models however you want.


Opening random file erases editor state

Issue Type: Bug
Say you've been working on a project and have a multiple editors active, some split vertically, some pinned, etc. If you restart using the icon in the dock / TaskBar the editor state is maintained for that project, aka everything remains the same with regard to open editors, layout, and so on.
Now quite VS Code and open a random file using VS Code as the target.
Instead of VS code opening that file within the conetxt of the project it
maintains the EXPLORER window showing your projects folder contents, but every editor window has been closed and only the file you've just opened is displayed.
What should happen is the application asks before it closes your custom layout, or it simply opens this new file as a new tab in say.
VS Code version: Code 1.65.2 (c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1, 2022-03-10T14:33:49.188Z)
OS version: Darwin x64 19.6.0
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz (16 x 2900)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
1, 1, 1

Memory (System)
32.00GB (16.66GB free)

Process Argv
-psn_0_520319 --crash-reporter-id 003c8b33-7671-417a-832e-8c09d7f0354c

Screen Reader
no

VM
0%

Extensions (5)

Extension
Author (truncated)
Version

Bookmarks
ale
13.2.4

vscode-intelephense-client
bme
1.8.2

xml
Dot
2.5.1

vscode-great-icons
emm
2.1.84

php-debug
xde
1.25.0

(1 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vsclayoutctrt:30451275
dsvsc009:30452663
pythonvsnew555:30457759
vscscmwlcmt:30438805
pynewfile477cf:30450039

Try: window.restoreWindows: "preserve"

From that settings' description it sounds like it's exactly what I'm after, so thank you for that!
If I had to nit the Restore Windows option names of all (default) and preserve are a bit intuitive. If the option names can't be revisited I'd say a much safer option would be to default to preserve.


add ShadowView to include the real view,and warp onClick

add ShadowView to include the real view,and warp onClick, when click mask's height light Widget,it call this.onTap

After careful consideration, I think there is no need to add a click event response to the highlighted area.