deleted Reaction class

@turbomam Can you review my comments

Is this still being reviewed?  @turbomam @mslarae13
I'm going to move to the next sprint against my better judgement

@turbomam what's the status of this one?  Are you waiting on Montana?

status of this one

double checking now with the intent to merge

@set I would like for at least two people to look at these issues before I merge this PR:

https://github.com/microbiomedata/nmdc-schema/issues/1838
https://github.com/microbiomedata/nmdc-schema/issues/1839

@set I would like for at least two people to look at these issues before I merge this PR:

Followup from deletion of Reaction class  nmdc-schema#1838
Deprecate, don't delete Reaction? nmdc-schema#1839

ok which 2 p

@set I would like for at least two people to look at these issues before I merge this PR:

Followup from deletion of Reaction class  nmdc-schema#1838
Deprecate, don't delete Reaction? nmdc-schema#1839

ok I'll move this to the next sprint for @sierra-moxon @brynnz22 @mslarae13 to review

I reviewed.
@sierra-moxon , @brynnz22  .. can you check out @turbomam 's comments

I made a comment in the https://github.com/microbiomedata/nmdc-schema/issues/1839 PR about deletion/deprecation.

moving to next sprint @brynnz22

also deleting these Reaction-only slots:

direction
is_balanced
is_diastereoselective
is_fully_characterized
is_stereo
is_transport
has_participants
left_participants
right_participants

and related classes/slots

ReactionParticipant

chemical
stoichiometry


Added edition page and component

Description
Added edition page and component
Fixes #735
Type of change

New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Need to sync first


ImportError: cannot import name 'Newscatcher' from partially initialized module 'newscatcher'

Hi team,
I face with this issue after do pip install newscatcher. I use python 3.8.10. Would you please update to fix this.
from newscatcher import Newscatcher
ImportError: cannot import name 'Newscatcher' from partially initialized module 'newscatcher'
Thank you.

Same problem. Python 3.9.


Universe Subscription Speed Review

Make universe smarter to not include its data in the slice.
Move universe selection to the data stack, removing stateful option selections.
Removing ZipEntry universes and replacing with CSV versions for speed.

Possibly related: (https://www.quantconnect.com/forum/discussion/10071/increasing-slowness-with-large-universe-option-backtests/p1)

Revisit the decision of keeping delisted securities in the Securities collection. When trading options the security count can grow significantly for a long running backtest causing a CPU/RAM overhead

Completed by https://github.com/QuantConnect/Lean/pull/7573


Update baseline to skip ogre conflicts

Since  there are some file conflicts between ogre and ogre-next, set all triplets of ogre to skip.
Related: #9255 #9301.

Ping @dan-shaw


Update prop.ts

Nested schema in arrays were incorrectly handled

@daanrutten when you are still working with typegoose: is this problem still a problem with the latest changes? when yes could you squash to one commit & rebase to master?

this can be closed, because it got already implemented in d2c00c4dac7e981d0932dd70a25eabc5d9107de4
@Ben305


Merge fix/aitor/spotless_and_codestyle into develop

Task/Issue URL: https://app.asana.com/0/414730916066338/1201536188592163/f
Description
In one of the latest PRs spotless was disabled by mistake when we removed the target '**/*.kt' line.
We've got another asana task that is currently dealing with code style, but doesn't re-enable spotless.
This PR:

takes the .editorconfig file from https://app.asana.com/0/1157893581871903/1201531481555667
re-enables spotless
runs spotlessApply to correctly format the codebase

Steps to test this PR
Just verify all compiles and checks pass

Current dependencies on/for this PR:

develop

PR #1635  (this PR)

This comment was auto-generated by Graphite.


Build eks-anywhere-packages during release.

Issue #, if available:
Description of changes: Adding EKS-A Curated Packages components to the release.
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

tests are broken

tests are broken

Fixed

/approve


Vanilla CSS support

Description
Hi! This PR adds Vanilla CSS support, like said above. That's it.
Additional Notes
The reason for this is that GTK CSS has its own quirks SCSS can't handle. It is not grass fault per se. I haven't read all the gtk docs, but one thing I've faced is how it declares color variables using this little @ char that breaks the SCSS compilation.
Checklist

[x] I added my changes to CHANGELOG.md, if appropriate.
[x] The documentation in the docs/content/main directory has been adjusted to reflect my changes.
[x] I used cargo fmt to automatically format all code before committing

I ran into the exact same issue, so I am looking forward to seeing this PR merged into main. I would really like to use use vanilla CSS alone for using @define-color declarations.

No problem! 😁 there it is.


Swiftlint not installed

I followed the instructions on the README, but I'm getting this message:
swiftlint is not in the user's PATH, or it failed to install

I checked Eigen's repo and I couldn't find a place where swiftlint is installed manually. Am I missing a step?

Hey there, sorry about that! Good thinking to check eigen, the SwiftLint tool is installed by this plugin itself. Here's the code that tries to run brew install swiftlint if it's already not installed. Do you have homebrew installed? We use it to install SwiftLint. If you do, try running brew install swiftlint and see what happens.

I'm using circle-ci with linux. So that's the problem. :( it only supports ci on osx then.

Yikes, good point. Sorry about that, you reckon a mention about only working on macOS should be added to the readme?

I haven't been able to verify this myself yet (working on it), but my understanding is that it should now work on Linux too. You need swiftlint, swift, and sourcekit installed on linux.
The SwiftLint README mentions Linux at the end of this section: https://github.com/realm/SwiftLint/blob/master/README.md#working-with-multiple-swift-versions


Rails configuration not loaded on rake tasks

[x] I have tried upgrading by running bundle update vite_ruby.
[x] I have read the troubleshooting section before opening an issue.

Description 📖
When you run a vite rake task, the rails configuration overrides are not properly loaded.
Reproduction 🐞
Consider the case where the rails assets host is set: Rails.application.config.asset_host = "http://assets.lvh.me:3000"
And a foobar rake task is defined:
task foobar: :environment do
  puts "-- ViteRuby.config.asset_host: #{ViteRuby.config.asset_host.inspect}"
end

If you run rake foobar you get the expected outcome:
$ bundle exec rake foobar
-- ViteRuby.config.asset_host: http://assets.lvh.me:3000

However, if you prefix the command with any vite rake task, the rails configuration is not properly loaded:
$ bundle exec rake vite:clean foobar
-- ViteRuby.config.asset_host: nil

Vite Ruby Info
Run bin/rake vite:info and provide the output:
bin/vite present?: true
vite_ruby: 3.0.9
vite_rails: 3.0.6
rails: <IP_ADDRESS>
vite_plugin_legacy: 3.0.2
rack: 2.2.3
node: v16.13.1
npm: 8.1.2
yarn: 1.22.17
pnpm: 6.24.1
ruby: ruby 2.7.5p203 (2021-11-24 revision f69aeb8314) [x86_64-darwin20]

installed packages:
xxx
│ ├─┬<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>deduped
│ └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
└──<EMAIL_ADDRESS>

Logs 📜
If not providing a reproduction:

Output
Run DEBUG=vite-plugin-ruby:* bin/vite dev or DEBUG=vite-plugin-ruby:* bin/vite build and provide the output:

Screenshots 📷
Provide console or browser screenshots of the problem.

Hi Stef, thanks for reporting!
I think a reasonable fix would be to have vite_rails extend the vite:verify_install rake task to depend on the environment rake task defined by Rails.
That would ensure the Rails application is loaded before Vite Ruby resolves the config.
PRs are welcome!

Released a fix in<EMAIL_ADDRESS>

@ElMassimo thanks again! I tried writing a test for it but that wasn't easy.
But nice that the fix is out 😊


many vaadin addons not working with vaadin flow 24.3.3

I cannot include in my vaadin projects many addons, certified for vaadin 24, because they are not visible in web pages.
I noticed this problem for addons that wrap javascript component, like ace editor.
I do not know if the javascript error showed in the image below could be related with this issue or i missed some build step.

 Vaadin Production mode is activated using -Pproduction -->
      <id>prod</id>
      <build>
        <plugins>
          <plugin>
            <groupId>com.vaadin</groupId>
            <artifactId>vaadin-maven-plugin</artifactId>
            <version>${vaadin.version}</version>
            <executions>
              <execution>
                <goals>
                  <goal>prepare-frontend</goal>
                  <goal>build-frontend</goal>
                </goals>
                <phase>compile</phase>
              </execution>
            </executions>
          </plugin>
        </plugins>
      </build>
    </profile>
  </profiles>
</project>

We are talking about this component? https://vaadin.com/directory/component/ace-widget1 if so, it is better to report this issue in the component repository at https://github.com/Sergio70/AceEditorV14/issues
Looking at the release notes, it might be marked "14+" without actually testing it on 24, but problem can also be in the integrated JS.

I am not talking only about ace-widget1 component.
The full list of addons i tried to integrate with the same problem is the following:
https://vaadin.com/directory/component/full-calendar-flow
https://vaadin.com/directory/component/full-calendar-scheduler-flow
https://vaadin.com/directory/component/grid-exporter-add-on
https://vaadin.com/directory/component/year-month-calendar-add-on
https://vaadin.com/directory/component/ace
https://vaadin.com/directory/component/ace-widget1

Ok, I see. I made a PR to ace-widget1 with the necessary V24 updates to see what what might be the issue. From 14 to 24 the biggest change is to Jakarta EE which is not compatible, but in this case I think it is the @Id from Polymer that causes the problems. It would make sense to upgrade from Polymer to Lit altogether, but with these changes it should work.

Hello. As a maintainer of grid-exporter-add-on and year-month-calendar-add-on, I can confirm that both of them should work with Vaadin 24.3 (indeed, our demo site was at 24.3 until a few weeks ago when we upgraded to 24.4.alpha).
Please note that you have to add com.flowingcode to the whitelist of your application (see note in README).
If that doesn't fix the issue, please create a new one in any of the add-on repositories, since vaadin/directory is intended for issues with the Directory itself, and we add-on authors don't monitor it actively:

https://github.com/FlowingCode/GridExporterAddon
https://github.com/FlowingCode/YearMonthCalendarAddon

An update.
The problem seems to be connected with Quarkus vaadin integration.
With spring it works.

Thanks for the update! this this likely two different problems: general compatibility with Quarkus and add-on compatibility with Vaadin versions.

I have the same problem Vaadin 24.3.5, quarkus integration, ace-widget 2.0.0 same error message as in the opening post.

Tested quickly with the ace add-on and it looks like the "dev mode" can't handle add-on components that have client-side extensions (add-ons that trigger npm build) properly. Running in production mode works though. So the workaround is (if you don't need anything else from the dev-mode):

Make sure you hava a production profile in your project, like here: https://github.com/vaadin/base-starter-flow-quarkus/blob/8027c2d307e2d0489506da19b6915ae9f0767936/pom.xml#L102
Run with mvn quarkus:dev -Pproduction

I guess this is the issue: https://vaadin.com/docs/latest/integrations/quarkus#quarkus.vaadin.addons

Verified, with e.g. ace widget, adding these to application.properties everything seems to work fine for me:
quarkus.index-dependency.hilerio.group-id=com.hilerio
quarkus.index-dependency.hilerio.artifact-id=ace-widget

I confirm that works fine

Thanks for letting us know! Looks like we need some extra information for Quarkus users. The errors are really misleading.
I created https://github.com/vaadin/directory/issues/68 We can continue discussing the solutions there.

Verified, with e.g. ace widget, adding these to application.properties everything seems to work fine for me:
quarkus.index-dependency.hilerio.group-id=com.hilerio
quarkus.index-dependency.hilerio.artifact-id=ace-widget

Just for my understanding with this solution, do we still need the production profile?

Yes, you should use production build when building a production artifact. This way the front-end bundle is optimised and the final artifact is slimmer (and doesn't need npm). For example in your CI pipeline your build should be mvn install -Pproduction instead of just mvn install.

Okay my question was obviously ambiguous. I was wondering if i need the production profile for Dev mode when I want the ace editor to work. I use the dev mode a lot because of the automatic recompile and restart.

Ah :-) I don't think it is needed then. At least my dev mode started just fine and the ace add-on was shown once the jandex index was there. I guess we could encourige add-on developers to generate jandex index automatically. Like making OSGi bunde, it is pretty much one time job and then makes the jar file more compatible 🤷♂

Ah :-) I don't think it is needed then. At least my dev mode started just fine and the ace add-on was shown once the jandex index was there. I guess we could encourige add-on developers to generate jandex index automatically. Like making OSGi bunde, it is pretty much one time job and then makes the jar file more compatible 🤷♂

Awesome that worked for me! Thanks a lot.


closeButton doesn't work on individual toasts via toastOptions

Describe the feature / bug 📝:
The documentation shows closeButton as an option under API Reference for toast() and says it's default value is false
https://sonner.emilkowal.ski/toast#api-reference
However if I try to add closeButton in the toast options, I get a TypeScript error saying it's not an available option, and when the toasts show up there's no close button.
the closeButton does show up when I make it a prop on the Toaster. But  I don't want all of my toasts to have it, only my error toasts, or some specific toasts with long messages.
Steps to reproduce the bug 🔁:
toast.error('example that does not work', { closeButton: true  })

This has been fixed in #296, thank you for reporting.


Build link/id is not created when used with 2 tests suites

Current behavior
I'm running 2 tests suite within 1 in virtual, 1 in real devices, but sometimes the virtual suite is not triggering any builds IDs because i can't retrieving the build when i try to reach this API https://api.eu-central-1.saucelabs.com/v2/builds/vdc?
Before, we were not using real devices test suite, and it was working fine.
Saucectl is also reporting me this:

So it seems, no builds were creating for this job test.
Desired behavior
I would like to have a build id because this is what we use afterwards to assert that everything that we needed within our job passed. it seems to appears only when you have 2 tests suites running.
Config to reproduce
I used this config
 - name: "Android UI Tests"
    testOptions:
      notClass:
        - "com.example.only.one.test.package" # Note: I use notClass because notPackage seems not working
        - "com.example.class2"
    emulators:
      - name: "Google Pixel 4 XL GoogleAPI Emulator"
        platformVersions:
          - "12.0"
  - name: "Android UI Tests in Real device"
    testOptions:
      package: "com.example.only.one.test.package"
    devices:
      - name: "Google Pixel 4 XL"
        platformVersions: "12.0"

Versions
saucectl Version: 0.105.1
Docker version: Docker version 19.03.4, build 9013bf583a
CI Used: Jenkins

Indeed! I was able to replicate this behavior and created a bug ticket for the team 👍

Perfect, currently, im working around using the jobs API to retrieve the JOB within the job list with

The bug is fixed now.

Hey @krzysieksulejczak, i can't see in the changelog the fix, which one is the resolving commit ?

This was not a bug in saucectl itself. The bug existed in one of sauce internal services.


[flutter_tools] Improve emulator error based on machine architecture

Improving emulator error message based on machine architecture
Update the android emulator image from 27 to 31

#105544
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] All existing and new tests are passing.

Thank you for contributing! As you have not responded within 3 weeks, I will be closing this PR as stale. If you are still interested in landing this, feel free to rebase this PR upstream, address code review feedback, and re-open this PR.


Update supported frameworks and integrate local and CI build processes

Maybe the check format task can be run using .NET 6 until they fix this issue.

Are you done with this PR @wo-roberts? If so we will merge and push a first release to nuget.

Yes I think I'm done with this version. Notably this removes the netstandard version. Controversially and while it is amazing that it works at all I think netstandard should now die and I don't think makes sense after net5.0. Moving to framework specific allows consistency of package restore etc.

Let's merge this and push it to nuget.


Adopt gitea-checks-plugin

Link to GitHub repository

https://github.com/jenkinsci/gitea-checks-plugin
When modifying release permission
List the GitHub usernames of the users who should have commit permissions below:

@flozzone
@viceice

This is needed in order to cut releases of the plugin or component.
If you are modifying the release permission of your plugin or component, fill out the following checklist:

### Release permission checklist (for submitters)
- [x] The usernames of the users added to the "developers" section in the .yml file are the same the users use to log in to [accounts.jenkins.io](https://accounts.jenkins.io/).
- [x] All users added have logged in to [Artifactory](https://repo.jenkins-ci.org/) and [Jira](https://issues.jenkins.io/) once.
- [x] I have mentioned an [existing team member](https://github.com/orgs/jenkinsci/teams) of the plugin or component team to approve this request.

When enabling automated releases (cd: true)
Follow the documentation to ensure, your pull request is set up properly. Don't merge it yet.
In case of changes requested by the hosting team, an open PR facilitates future reviews, without derailing work across multiple PRs.
Link to the PR enabling CD in your plugin

### CD checklist (for submitters)
- [ ] I have provided a link to the pull request in my plugin, which enables CD according to the documentation.

### Reviewer checklist
- [ ] Check that the `$pluginId Developers` team has `Admin` permissions while granting the access.
- [ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
- [ ] If security contacts are changed (this includes add/remove), ping the security officer (currently `@Wadeck`) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it.

@flozzone Please approve


On master build: Execution failed for task ':printSignedPluginZipPath'

https://app.circleci.com/pipelines/github/VirtusLab/git-machete-intellij-plugin/7776/workflows/ca7bd676-008d-41cf-9db0-76670533e63c/jobs/8200

As a workaround, we can suspend passing the plugin zip as artifact to GitHub release for a moment 🤔

I've created the v3.2.1 release manually btw

Okay, trivial to repro locally...

What's weird is that on CI, buildPlugin is executed before the release hmmm 🤔

You mean that it should have failed before, right? even before merge to master (riliz)

Nope, I'd just expect printSignedPluginZipPath not to fail at all, given the circumstances... anyway, lemme provide a workaround as for now, #1357 1⃣ 3⃣ 5⃣ 7⃣


Replace gradle enterprise with develocity

Sorry, I think I missed the motivation behind this. I saw some stuff in upstream maybe changing around this, but wasn't sure if/how it might impact our distro. What's up?

Sorry, I think I missed the motivation behind this. I saw some stuff in upstream maybe changing around this, but wasn't sure if/how it might impact our distro. What's up?

gradle enterprise is now called develocity, gradle enterprise plugin is deprecated

Got it. Thanks!


Switch to pytest?

Are you open to switching to pytest rather than nosetests?
The main advantages are:

Better assertion errors: https://docs.pytest.org/en/latest/assert.html
Simpler skipping tests: https://docs.pytest.org/en/latest/skipping.html
Parametrized tests: https://docs.pytest.org/en/latest/parametrize.html

If so, then I can probably provide a PR.

Hi, sorry for no response yet. This is a good idea. I am traging older issues, and see that pytest is now actually being used instead of nosetests. Ref https://github.com/slundberg/shap/blob/45b85c1837283fdaeed7440ec6365a886af4a333/.github/workflows/run_tests.yml#L33
So this issue can be closed. CC @slundberg


Feat: Need to Add dark theme

Describe the feature
There is a need to add a dark theme for website.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Can you assign this issue to me under GSSOC 24


Fix #459 - properly support remote SPI with pigpio

Sorry! Dave's messing around with the pin implementations again.
Hopefully the last time. The pin_factory is now really a factory object
which can be asked to produce individual pins or pin-based interfaces
like SPI (which can be supported properly via pigpio).

Wow ... passing on everything but pypy. I was honestly expecting more of a horror show here. And the pypy stuff just looks like the new reservation system whinging because of longer object lifespan on pypy, which I was half expecting. Let's see if I can get this passing quickly...

Current coverage is 78.74% (diff: 74.14%)

Merging #468 into master will increase coverage by 0.48%

@@             master       #468   diff @@
==========================================
  Files            31         34     +3
  Lines          7213       7524   +311
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           5645       5925   +280
- Misses         1568       1599    +31
  Partials          0          0

Powered by Codecov. Last update cc85135...9dfc838

Yay! Passing on all variants. I'm not too bothered about the patch failure; given this is pins based stuff (which Travis can't directly test), and that it's expanding the implementation (so I'm adding a fair bit of stuff that can't be tested away from a Pi), it's not bad.

Okay, the patches are separated. This PR should now be just the remote SPI (and minor auxilliary stuff). I'll open a separate PR for the pin numbering stuff tomorrow.

Sorry, hadn't noticed this needed rebasing - done now, along with the dependent pin-numbering PR. Anybody got any time to look at reviewing this? I know it's horrid but we ought to get this in for 1.4

Seems there's a few files that have had import weakref added, but then not actually use it?

Just a few selected comments for now, rather than a full 'review', but it's a start... ;-)

Just a few selected comments for now, rather than a full 'review', but it's a start... ;-)

Much appreciated!

Seems there's a few files that have had import weakref added, but then not actually use it?

Ah, I'll see what I can find. I'll push an additional commit in a bit to avoid wiping out the existing comments (I'll have to rebase the pin-numbering branch at some point but that can wait until this is done).

Just a few selected comments for now, rather than a full 'review', but it's a start... ;-)

Much appreciated!

Done a more thorough read-through, and added some more comments :-)  In case it's not obvious, I've only been reading the code online on github.com, I haven't actually tried running any of it on a real Pi yet. Something for Sunday perhaps... ;)
Always nice to see that my comments are actually useful :-)

Okay, Travis seems to playing nice again ... I've no idea why it was skipping the mock pin tests before but it's okay now. I'm pretty much happy with the PR at this point -- so unless anyone has any objections I'll squish and merge it later this week (got Hack Mcr Jr tomorrow and Tuesday so it'll be at least Wednesday before I get back to this).

unless anyone has any objections I'll squish and merge it later this week

I'd still like to try experimenting with this code on a real Pi - hopefully I'll be able to squeeze that in on Monday or Tuesday evening.

unless anyone has any objections I'll squish and merge it later this week

I'd still like to try experimenting with this code on a real Pi - hopefully I'll be able to squeeze that in on Monday or Tuesday evening.

No prob - my major goal is to get this into 1.4. I've been running tests on a Pi fairly regularly, but I've only tried remote SPI a few times (and not recently - had my Pi's all unplugged for Hack Manchester Jr - will give it a go now that most are back online).

I've been busy all this week, and I'm away all this weekend, so hopefully I'll get a chance to experiment with this next week...
Did Hack Mcr go well?

I've been busy all this week, and I'm away all this weekend, so hopefully I'll get a chance to experiment with this next week...

Here too - in the midst of a house extension at the moment, so things are a little chaotic!

Did Hack Mcr go well?

It certainly did (well, the junior event; the senior event is this weekend but I can't make that unfortunately). The video coverage of the event is somewhere on the intertubes but I'm proud to say a couple of the kids I was mentoring won one of the challenges (with some Scratch-based robotics) and there were some interesting steganography attempts from the teams doing the GCHQ challenge.

:fireworks:

I tried this on a Mac talking to a PiZeroW running JessieLite.     Obviously had to apt install pigpio on Jessie lite.
One thing that wasn't in the example but was something I had to specify was the pin factory, so raising this just in case it's unexpected:
GPIOZERO_PIN_FACTORY=pigpio PIGPIO_ADDR=<IP_ADDRESS> python
from gpiozero import PWMLED
led = PWMLED(17)
led.value=0.5

Without GPIOZERO_PIN_FACTORY this occurs:
(gpiozero-env) shinytoo:python-gpiozero wayne$ PIGPIO_ADDR=<IP_ADDRESS> python
Python 3.6.1 (default, Apr  4 2017, 09:40:21)
[GCC 4.2.1 Compatible Apple LLVM 8.1.0 (clang-802.0.38)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import gpiozero
/Users/wayne/local.projects/python-gpiozero/gpiozero/devices.py:520: PinFactoryFallback: Failed to load factory rpigpio: No module named 'RPi'
  'Failed to load factory %s: %s' % (name, str(e))))
/Users/wayne/local.projects/python-gpiozero/gpiozero/devices.py:520: PinFactoryFallback: Failed to load factory rpio: No module named 'RPIO'
  'Failed to load factory %s: %s' % (name, str(e))))

I originally tried to use the activity LED as this Zero had no header. Apologies if this is actually a separate issue, but when running the following:
On the pi:
echo none | sudo tee /sys/class/leds/led0/trigger
echo gpio | sudo tee /sys/class/leds/led1/trigger

On the Mac:
GPIOZERO_PIN_FACTORY=pigpio PIGPIO_ADDR=<IP_ADDRESS> python
from signal import pause
from gpiozero import LED

activity = LED(47)
activity.blink()

pause()

This error occurs:
>>> activity = LED(47)
/Users/wayne/local.projects/python-gpiozero/gpiozero/pins/pi.py:228: PinNonPhysical: no physical pins exist for GPIO47
  'no physical pins exist for %s' % self.address[-1]))
Traceback (most recent call last):
  File "/Users/wayne/local.projects/python-gpiozero/gpiozero/pins/pi.py", line 59, in pin
    pin = self.pins[n]
KeyError: 47

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/wayne/local.projects/python-gpiozero/gpiozero/pins/pigpiod.py", line 175, in __init__
    self.factory.connection.set_mode(self.number, pigpio.INPUT)
  File "/Users/wayne/local.projects/gpiozero-env/lib/python3.6/site-packages/pigpio.py", line 1291, in set_mode
    return _u2i(_pigpio_command(self.sl, _PI_CMD_MODES, gpio, mode))
  File "/Users/wayne/local.projects/gpiozero-env/lib/python3.6/site-packages/pigpio.py", line 964, in _u2i
    raise error(error_text(v))
pigpio.error: 'no permission to update GPIO'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/wayne/local.projects/python-gpiozero/gpiozero/devices.py", line 96, in __call__
    self = super(GPIOMeta, cls).__call__(*args, **kwargs)
  File "/Users/wayne/local.projects/python-gpiozero/gpiozero/output_devices.py", line 132, in __init__
    super(DigitalOutputDevice, self).__init__(pin, active_high, initial_value)
  File "/Users/wayne/local.projects/python-gpiozero/gpiozero/output_devices.py", line 41, in __init__
    super(OutputDevice, self).__init__(pin)
  File "/Users/wayne/local.projects/python-gpiozero/gpiozero/mixins.py", line 69, in __init__
    super(SourceMixin, self).__init__(*args, **kwargs)
  File "/Users/wayne/local.projects/python-gpiozero/gpiozero/devices.py", line 443, in __init__
    pin = Device._pin_factory.pin(pin)
  File "/Users/wayne/local.projects/python-gpiozero/gpiozero/pins/pi.py", line 61, in pin
    pin = self.pin_class(self, n)
  File "/Users/wayne/local.projects/python-gpiozero/gpiozero/pins/pigpiod.py", line 177, in __init__
    raise ValueError(e)

The above blinks an LED, but without GPIOZERO_PIN_FACTORY this occurs:...

Those warnings are actually expected (though for some utterly bizarre reason I haven't yet fathomed they don't occur on Ben's laptop!). Anyway, they're normal: by way of explanation there's four pin implementations underlying GPIO Zero which, in the absence of an explicit specification via the GPIOZERO_PIN_FACTORY env-var, the library attempts to load in the following order: RPi.GPIO, RPIO, pigpio, and "native" (a hacky implementation I threw together as a back-stop, which I ought to revise at some point). You got two warnings because it tried (and failed) to load RPi.GPIO, then RPIO, then succeeded when it reached pigpio.
The reason the warnings are there is that it's quite common for more advanced Python developers to work in a virtualenv; GPIO Zero doesn't directly depend on any of the pin implementations (after all it could be installed on a non-Pi, or someone might actually want to use "native" ... for some strange reason :) so installing GPIO Zero in the virtualenv doesn't pull in any of the other implementations. At that point the developer fires up Python, tries it out and wonders why it works ... sort of, but all the PWM fails. The reason is that GPIO Zero (in the absence of any pin libraries) has fallen back to the hacky native implementation which doesn't do PWM. So, the warnings were added to make it more obvious to people working in a virtualenv that they've probably forgotten to install whichever pin implementation they want.
Now ... in future the plan is eventually to switch pigpio to the top of the list so the warnings would disappear in your particular scenario, but we're not quite there yet.
@bennuttall aha! Are you sure there's nothing weird in your Python config? ;)

I originally tried to use the activity LED as this Zero had no header. Apologies if this is actually a separate issue...

Ahh, that's interesting. I hadn't tried using activity LEDs remotely yet. The first bit there ("PinNonPhysical") isn't actually an exception; it's just another warning that we fire off when a GPIO is specified that isn't present on any known header. However, after that it appears something rather more serious goes wrong. A quick guess is that the pigpio daemon might refuse to serve GPIOs outside the normal range, which would be an upstream issue but we ought to have some better error handling there.

ah, I thought the warnings were fatal errors and so I stopped, I should have just pressed ahead, it works ok, as expected.  My excuse is the usual: it was early and pre-coffee :)
Although this may soon to be a moot point when pigpio becomes king, but, perhaps change the wording to output something like logger.info("Optional library XXX not found.") - I did this in one of my libraries to lower end user confusion.


geo_e4cv nbsphinx error:  module 'jinja2.utils' has no attribute 'escape'

Since switching to nbsphinx, the workflow that publishes documentation has failed (https://github.com/bluesky/hklpy/runs/6995106866?check_suite_focus=true, https://github.com/bluesky/hklpy/runs/6995279669?check_suite_focus=true) with this error:
Notebook error:
AttributeError in examples/notebooks/geo_e4cv.ipynb:
module 'jinja2.utils' has no attribute 'escape'
make[1]: *** [Makefile:60: html] Error 2
make[1]: Leaving directory '/home/runner/work/hklpy/hklpy/docs'
make: *** [Makefile:14: html] Error 2
Error: Process completed with exit code 2.

This error might not be limited to this one notebook.  The workflow stops on the first error:
make -C docs html
make[1]: Entering directory '/home/runner/work/hklpy/hklpy/docs'
sphinx-build -b html -d build/doctrees   source build/html
Running Sphinx v4.4.0
making output directory... done
[autosummary] generating autosummary for: api.rst, calc.rst, context.rst, diffract.rst, engine.rst, examples/index.rst, examples/notebooks/geo_e4cv.ipynb, examples/notebooks/geo_e6c.ipynb, examples/notebooks/geo_k4cv.ipynb, examples/notebooks/how_additional_parameters.ipynb, ..., geometries.rst, geometry_tables.rst, index.rst, install.rst, overview.rst, ready_to_use.rst, release_notes.rst, sample.rst, user.rst, util.rst
loading intersphinx inventory from https://docs.python.org/3/objects.inv...
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 28 source files that are out of date
updating environment: [new config] 28 added, 0 changed, 0 removed
reading sources... [  3%] api
reading sources... [  7%] calc
reading sources... [ 10%] context
reading sources... [ 14%] diffract
reading sources... [ 17%] engine
reading sources... [ 21%] examples/index
reading sources... [ 25%] examples/notebooks/geo_e4cv
Notebook error:
AttributeError in examples/notebooks/geo_e4cv.ipynb:
module 'jinja2.utils' has no attribute 'escape'
make[1]: *** [Makefile:60: html] Error 2
make[1]: Leaving directory '/home/runner/work/hklpy/hklpy/docs'
make: *** [Makefile:14: html] Error 2
Error: Process completed with exit code 2.

Aha! Swap the order of the channels here. https://github.com/bluesky/hklpy/blob/de21ead8c784ea4257a209c0cc9cd47864bc3637/.github/workflows/publish-docs.yml#L59

Trying to replicate, so far cannot reproduce locally:
micromamba create -n dev-hklpy python=3.8
micromamba install -n dev-hklpy -f environment.yml
micromamba install -n dev-hklpy jupyter nbconvert "sphinx=4.4.0" sphinx-rtd-theme nbsphinx sphinxcontrib-napoleon make flake8 black pandoc -c conda-forge -c defaults
micromamba activate dev-hklpy
make -C docs clean html

Locally, no problem building with either Py 3.8 or 3.9.  Need to get a list of the specific packages installed in the Actions workflow run.
Note Sphinx version 5.0.2 is available but the workflow installs 4.4.0.  Curious, that.

Good time to switch the workflow to micromamba (#231).

I'm not convinced that module 'jinja2.utils' has no attribute 'escape' is the real problem here.

It's a miracle, with commit 11fa1ad (for #231), the documentation builds without error.


How to send and receive images with Falcon Framework?

Hello
I am trying to send and receive images with requests library but I can't seem to succeed.
What Is the easiest way to send and receive an image?.
This is How I tried:
import requests
import base64
with open("test.png", "rb") as image_file:
     encoded_image = base64.b64encode(image_file.read())
r = requests.post("http://localhost:8000/image", data={'image_data':encoded_image}, headers={'content-type': 'image/png'})

and the server
json_data = json.loads(req.bounded_stream.read().decode('utf8'))
base64encoded_image = json_data['image_data']

with open('pic.png', "wb") as fh:
     fh.write(base64encoded_image)
resp.status = falcon.HTTP_200

How ever I am getting a Json error I'm not sure why, I cannot send JSON data because encoded_image is in bytes

Hello @Mice948.
You can just send it as the request data, something along the lines of the Streaming Uploads recipe from the requests docs.
You can consume it on the application side as demonstrated in our "Look" tutorial, see the on_post handler.
In contrast to that example, depending on the WSGI server you use, you may want to use the req.bounded_stream instead of req.stream.
Hope this helps. Closing this issue.


3/31/2020 Publish

Docs Build status updates of commit 1d80294:
:clock10: Full build: the average full build time is 7 min(s) 20 sec(s), this is based on the last 524 build(s) for this repository.

Docs Build status updates of commit 1d80294:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

2017-03-09-profile/docs-ref-autogen/ext/front-door/network/front-door/routing-rule.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2018-03-01-hybrid/docs-ref-autogen/ext/front-door/network/front-door/routing-rule.yml
:white_check_mark:Succeeded
View (azure-cli-2018-03-01-hybrid)

2019-03-01-hybrid/docs-ref-autogen/ext/front-door/network/front-door/routing-rule.yml
:white_check_mark:Succeeded

latest/docs-ref-autogen/acr/scope-map.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-autogen/acr/token.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-autogen/ams/asset.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-autogen/ext/front-door/network/front-door/routing-rule.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

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.


Add Baserow

Project Information

Project Name: Baserow

Project URL: https://gitlab.com/baserow/baserow

Description:
Baserow is a free and open-source no-code database tool and Airtable alternative. Built with Django and Vue.js, it provides a user-friendly interface for creating and managing databases without coding knowledge while maintaining the flexibility and power of a professional database system.

Criteria

Is the project new?

[x] No (Project started in 2019)

How long has the project been maintained?
Active development for over 4 years with regular updates and strong community engagement.

How many releases has it had if it's a library or package?
Multiple stable releases with version 1.19.1 being the latest as of early 2024. Regular release cycle with both feature updates and bug fixes.

Are you the author or are you submitting the project on behalf of a company?

[x] Other (Community submission for an established open-source project)

What makes it awesome?

Full-featured alternative to Airtable with self-hosting capability
Built with Django and Vue.js, showcasing Django's capabilities in modern web applications
Enterprise-grade features including user management, real-time collaboration, and API access
Regular updates and maintenance
Comprehensive documentation and growing ecosystem

Additional Information
Baserow demonstrates Django's capability to power modern, complex web applications. Key features include:

Real-time collaboration
REST API for integration
Multiple view options (Grid, Gallery, Kanban)
User management and permissions
File handling and image support
Formula fields
Import/Export functionality
Self-hosting capability
Active community and commercial support options

The project maintains high code quality standards, extensive documentation, and has a growing ecosystem of plugins and integrations. It's particularly notable for combining Django's robust backend capabilities with modern frontend technologies.
Thank you for considering Baserow for inclusion in the Awesome Django list!

@daway0 thank you for the suggestion!


There is no code to show/hide Text pane of the SmartArt Graphic in Powerpoint!!

How do I show text pane of SmartArt graphics in PowerPoint (VSTO addin)?
I can't find any code for text pane, and then only I can show/hide it.
`using core = Microsoft.Office.Core;
using pp = Microsoft.Office.Interop.PowerPoint;
public static void CreateOrgChart()
{
pp.Application app;
pp.Presentation pres;
core.SmartArt sa;
core.SmartArtLayout layout;
app = Globals.ThisAddIn.Application;
pres = app.ActivePresentation;

layout = app.SmartArtLayouts[97]; // 97 - stands for org chart
sa = pres.Slides[1].Shapes.AddSmartArt(layout).SmartArt;

//sa.textpane.show(); // does not exists

}`

Also to clarify, My objective is not to get the Text from the Shape.
Problem is, Initially when the user clicks that arrow to show the text pane for first time, the text pane is kind of messed up, only when i hide again and reshow again, this gets solved.

I need to show or hide the text pane for SmartArt in PowerPoint (by code).

@frozenprakash Thanks for your feedback. However, we use Github issues for documentation bugs, not for developer support. Please try the VBA developer community on Stack Overflow where you can get help from actual developers. If you find a bug in our documentation, please let us know. Thanks!


request to https://api.openai.com/v1/chat/completions failed, reason: Invalid SOCKS proxy details were provided

我部署在我的nas，科学上网，能够正常访问外网，且也单独添加了API.openai.com网址到强制代理，但在Chat GPT Web中对话仍提示：
request to https://api.openai.com/v1/chat/completions failed, reason: Invalid SOCKS proxy details were provided
求助各位大神，谢谢

我也是这样，同求解法


add Spin 3 support

This adds support for<EMAIL_ADDRESS>worlds, while still using the 2.0.0 worlds by default.  Apps may opt-in to using a 3.0.0 world by specifying e.g. --world<EMAIL_ADDRESS>as part of their componentize-py command in their spin.toml file.
This also updates to componentize-py v0.16.0 (which includes https://github.com/bytecodealliance/componentize-py/pull/128, a feature required for compatibility with earlier SDK releases).

Leaving this as a draft until componentize-py v0.16.0 is available.

99.9% of the changes here are in generated code and docs.  The main things to note are the newly-added WIT files and the componentize-py version updates.

The PR looks great. Do we also want to add some wrapping code in the SDK for postgres v3 like we have been doing? https://github.com/fermyon/spin-python-sdk/blob/main/src/spin_sdk/postgres.py

Yeah, but let's leave that for a separate PR.  This one's big enough already.


Add build step to workflow

Please delete checklist items and sections that are not relevant
Checklist

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Please check if the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Storybook or docs have been added / updated (for bug fixes / features)

What is the ticket / issue associated with this change? (Link to the ticket or issue)
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information:
Storybook Link (Link to a local storybook url to review new functionality)

@stevejcox I was looking at the code of the changesets action and this will not work as we expect because the action does a git reset --hard and discard the changes introduced by the build step


sentinel-go middleware need cgo

Ask your question here
Sentinel-go relies on gopsutil for system information. For example, CPU load, etc. The dapr compiler disables cgo by default . This causes sentinel-go to not work properly.  Will all plugins that rely on cgo be affected? I think it is possible to turn on the cgo option at compile time?

Do you meet that dapr run into crash since sentinel-go, dapr does not depend on it directly.

I'm just curious if there is other middleware that uses cgo. I haven't had any crashes due to sentinel-go. I just think that the absence of cgo might affect the proper functioning of sentinel-go. It's just the warnings that are printed out that might be confusing to me. Not a big problem

My understanding is that Dapr tries hard to avoid any dependency on cgo for portability reasons. The only previous instance of a cgo dependency I've come across was in a test.
@yaron2, thoughts on this?


Runtime API Selection

Would it make sense to be able to select the graphics API to use at runtime, instead of at compile time?
For instance, on Linux, if I wanted to use Vulkan when possible, but to switch to OpenGL when Vulkan is not supported.
If this would require drastic changes I can understand it being a non-goal, and for my use-case, for distributing PC games, I wouldn't mind terribly if there was a separate build that would be downloaded if OpenGL support was required, but I was curious as to the potential.

Add the feature flags you want (such as rafx-vulkan,rafx-gles3) and use the API-specific init functions such as RafxApi::new_vulkan or RafxApi::new_gles3. RafxApi::new demonstrates this and probably does what you want by default.
https://github.com/aclysma/rafx/blob/0a495460e0ee0c3c0d320565b3e86087f940ef96/rafx-api/src/api.rs#L63-L88
Long term, API selection could be made by having a config file that explicitly pairs PCI device IDs/driver versions with APIs (for example to ban an old GPU from vulkan if it is known to have a buggy driver). This could also be used to enable/disable rendering settings based on the performance of that particular GPU. This is outside the scope of this project for the time being and is a fairly opinionated thing.

Oh, cool, I didn't realize it would work with multiple backends enabled at the same time. Perfect!


[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
alpine-3.18.0
Other Software
Docker Desktop 4.12.0 (85629)
Repro Steps

download alpine-3.18.0.tar , wsl.exe --import it
start docker desktop , enable wsl engine , use distro from  setup 1
enter wsl environment , exec docker cli , and display cli not find .

Expected Behavior
can exec docker cli
Actual Behavior
can't exec docker cli.    error:  no such file or directory
Diagnostic Logs
No response

This would really be an issue to file against Docker, of course.
It's been a while since I used Docker Desktop with Alpine, but I thought the binaries used to be statically linked.  However, if that was the case, it doesn't appear to be any longer.
Keep in mind that Alpine does not provide standard glibc support like most distributions, so binaries that are dynamically linked against it will fall on Alpine.
See this Stack Overflow answer for some background, and potential solutions, e.g.:
su -
apk add libc6-compat
exit
docker

nice ,  big thanks


fix: experiments

What problem does this PR solve?

Optimized UI
Typesafe code
Support delete a single experiment
Display alert message when creating experiment error
Add form validation
Limit pod-kill and container-kill only immediate job

Does this PR introduce a user-facing change?
NONE

Codecov Report

Merging #582 into master will decrease coverage by 0.20%.
The diff coverage is 54.43%.

@@            Coverage Diff             @@
##           master     #582      +/-   ##
==========================================
- Coverage   55.98%   55.78%   -0.21%
==========================================
  Files          67       68       +1
  Lines        4324     4383      +59
==========================================
+ Hits         2421     2445      +24
- Misses       1733     1768      +35
  Partials      170      170

Impacted Files
Coverage Δ

api/v1alpha1/iochaos_types.go
40.00% <ø> (ø)

controllers/iochaos_controller.go
85.71% <ø> (ø)

pkg/chaosdaemon/time_server.go
88.23% <ø> (ø)

pkg/webhook/config/config.go
17.14% <ø> (ø)

pkg/utils/selector.go
52.24% <40.00%> (-0.24%)
:arrow_down:

pkg/store/experiment/experiment.go
38.77% <45.23%> (ø)

controllers/twophase/types.go
55.88% <74.07%> (+0.09%)
:arrow_up:

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 3be4666...d9be635. Read the comment docs.

/merge


Remove the LoWRA LORA from recommended starter models

What type of PR is this? (check all applicable)

[ ] Refactor
[ ] Feature
[X] Bug Fix
[ ] Optimization
[ ] Documentation Update
[ ] Community Node Submission

Have you discussed this change with the InvokeAI team?

[X] Yes
[ ] No, because:

Have you updated all relevant documentation?

[X] Yes
[ ] No

Description
This PR removes the low lighting LORA, LowRA, from the list of recommended models in INITIAL_MODELS.yaml. This LoWRA has been deleted from Civitai and is no longer accessible.

This seems to be a dupe of #5016 ?


Allow for more flexible (escaped) variable names in CLI options

Will merge after tests if no other action.


Support checkbox form component description

Checkbox lists do support descriptions, but separate checkbox components don't yet.

Have no need for this anymore right now.
Reopening if someone needs this.


Customize allocation of ephemeral disk space on DC/OS

Is this a request for help?:
Yes

Is this an ISSUE or FEATURE REQUEST? (choose one):

FEATURE REQUEST - It would be nice to have a way to customize the allocation of the ephemeral disk to /var/lib/mesos, /var/lib/docker, and /tmp.
Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
DC/OS 1.9
What happened:
On DC/OS, the ephemeral disk is split proportionally between /var/lib/docker, /var/lib/mesos, and /tmp. The proportions are 45%, 45%, and 10%, respectively.
What you expected to happen:
I'd like a way to customize the proportions of the ephemeral disk that are allocated to /var/lib/docker and /var/lib/mesos.
How to reproduce it (as minimally and precisely as possible):

Deploy a DC/OS ACS template
ssh to master node
run sudo fdisk -l and see /dev/sdb[1|2|3] and allocated sizes

Anything else we need to know:
No.

Ideally this could be defined per agent pool.  The rational for this request is that in discussions with a customer (I've heard it from another in passing as well) they are using something like Cassandra on AWS with ephemeral disk only.
The current work around is to modify the generated azuredeploy.json file.

It looks like this is actually a dupe of https://github.com/Azure/acs-engine/issues/133

It is a dupe. If we were to do this we would want something similar to how we have kubernetesConfig on the orchestratorProfile that would allow us to do things like this.

@JackQuincy I'm actually not finding that the volumes are necessarily landing on the ephemeral disks as well. It's trivial enough to edit these splits, but it seems like, based on the agent pool, only one of the 3 ephemeral allocations is actually assigned. E.g.,

only /var/lib/mesos is on ephemeral on private agents
only /var/lib/docker is on ephemeral on master

That means that 55% of the ephemeral disk is not being used on nodes in these pools...

hmm... that would be strange as we specify all three in the same way. can you copy the output that makes you think that is true?

azureuser@dcos-master-83165892-0:~$ df -h /var/lib/mesos
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1        30G  3.1G   26G  11% /

azureuser@dcos-master-83165892-0:~$ df -h /var/lib/docker
Filesystem      Size  Used Avail Use% Mounted on
/dev/sdb2        45G   52M   42G   1% /var/lib/docker

I recommend filing this as an upstream issue for https://github.com/dcos/dcos.  Basically Mesosphere has built these templates and added that ratio and logic.
This is a duplicate of #133.

Anthony -
See the email I sent you.  I'll talk with Mesosphere about this next week.  I'm also thinking a PR that allows for customization via acs-engine makes sense on a per agent pool basis and I'll do this work.
We can chat here or email about such.
I understand your point, but control on resource allocation given different vm skus (L-series up to 600+gig ephemeral SSD) and different workloads makes sense as something we should enable.
Sent from my iThingy

On Jun 22, 2017, at 19:50, Anthony Howe<EMAIL_ADDRESS>wrote:
I recommend filing this as an upstream issue for https://github.com/dcos/dcos. Basically Mesosphere has built these templates and added that ratio and logic.
This is a duplicate of #133.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


Adding Changesets

Describe what feature you'd like. Pseudo-code, mockups, or screenshots of similar solutions are encouraged!
I'm going to try to layout all of my thoughts so that we're all on the same page on some of the technical reasonings behind some of these ideas.
We're still very much in the experimental/exploratory/planning phase of Changesets, so nothing has been implemented and definitely not set in stone. It's still going to take a bit of time to get everything in order and make things completely fool-proof - that's when we'll be satisfied enough to start opening PRs and begin implementation.
Differences in each approach:
Approach 1: Maintaining a master and dev branch on a time-based release cycle
The idea here is that we have a dev branch that we'll merge all of our PRs into and a master branch that represents the latest release of all of our packages. When a new PR is merged into dev, a new "dev/preview/nightly" package will be built and published under the dev dist-tag on npm. This will provide users an easy way to install and test out all of the latest features just by running npm i @skeletonlabs/skeleton@dev in their project.
PROS

Maintains the our current 2 week release cycle
When PRs are merged into dev, the package will be built and published with the dev dist-tag. Users will be able to install the package by adding it into the project like so: npm i @skeletonlabs/skeleton@dev.

CONS

We have to make sure that the master and dev branches are always in-sync with each other after releases. That means that when we merge dev into master, we have to select the "merge with all commits" option instead of squashing or rebasing. If we don't, and the two branches are out of sync of each other directly after a release, things are going to get messy in future releases if we don't correct it before the next one. (i.e. changesets that were applied in a previous release won't be deleted and will double up and apply again in the next release). Essentially, we have the be very careful with how we merge dev into master.

Perhaps there's a way to always sync them after releases with GH Actions? I'm not aware of a way how, but maybe some judo magic with git is required to do so, avoiding this issue altogether. Maybe deleting dev and re-branching from master after every release?

This approach will also block the release of other packages if one of them needs an update to be published immediately. For example, say that we have a couple of updates already merged and ready to go on the dev branch and they're just waiting until the end of the release cycle to be merged into master. Now say that we need to push out and release an update to create-skeleton-app immediately. We won't be able to do it because we can't publish a package without affecting the other packages that have pending changesets. If there are any pending changesets, they will be published together.

NOTE: it may be possible to configure GH Actions to account for this scenario, but it's going to greatly complicate the build scripts and our github action workflows, so I'm really not in favor of it

We can't have create-skeleton-app in the monorepo due to the reason above.

Approach 2: Maintaining just a master branch and publish a new release whenever a PR is merged
In this approach, we will just have one branch to maintain - no syncing to others is required. Whenever a PR is merged into master, the package will be built and published with the latest dist-tag on npm. Users will be able to use the latest features as soon as they are merged. This is approach is similar to how SvelteKit handles their releases.
PROS

Very simple and easy to maintain CI/CD.
Users will get the latest features as soon as they are merged.
Publishing packages that need to be released immediately won't be blocked anymore.
We'll be able to add create-skeleton-app to the monorepo.
No need to worry about the small details on how we merge into master since there's no syncing required.

CONS

Not having a ongoing "dev/preview/nightly" release for testing newly merged PRs.

To make up for this, I've written a GH Action that will generate a preview release on PRs that contain a certain label. For example, say we that have a test release label for PRs. Once that label is added to a PR, the GH Action will run, building and publishing packages under the dev (we can also change it to preview) dist-tag. That way, we can still have a way to easily install the PR's package test features before they're officially merged into master.

We have to be more thorough in what we merge into master making sure that they're ready.

In short, I believe the first approach is a lot more fragile and is more prone to errors. The simplicity of the second approach is certainly what makes it more fool-proof with less overall downsides.
What type of pull request would this be?
Enhancement
Any links to similar examples or other references we should review?
No response

This was an interesting read: https://github.com/storybookjs/storybook/issues/22242 - the only problem with the new branch per release is that it is going to make it harder for non core contributors to send stuff in.


No syntax highlighting for Markdown when Treesitter is enabled.

I think this used to work, and I don't know of anything in my configuration that might have changed anything, other than perhaps a Treesitter update.
If I disable Treesitter on a Markdown buffer, the syntax highlighting is working correctly.
If I run this command on the open buffer when Treesitter is enabled, I get back this list of captures.
:lua =vim.treesitter.highlighter.active[vim.api.nvim_get_current_buf()]

captures = <2>{ "markup.heading.1", "markup.heading.1.marker", "markup.heading.2", "markup.heading.2.marker", "markup.heading.3.marker", "ma
rkup.heading.3", "markup.heading.4.marker", "markup.heading.4", "markup.heading.5.marker", "markup.heading.5", "markup.heading.6.marker", "markup.he
ading.6", "label", "markup.heading", "punctuation.special", "markup.raw.block", "markup.raw.delimiter", "conceal", "markup.link.url", "markup.link.l
abel", "markup.list", "markup.list.unchecked", "markup.list.checked", "markup.quote", "string.escape", "spell" },

I'm not sure if that means anything, tho I did find another theme with similar highlights defined for them:
https://github.com/bluz71/vim-moonfly-colors/blob/a1a0dfc621f41ffb4e98a813e021ba41e8199adc/lua/moonfly/init.lua#L443-L463
I noticed there are no similar highlights in Mellow. Perhaps the issue?
NVIM v0.9.5
:checkhealth shows no issues

Hi there! Thanks for reporting this issue with links to other implementations. Will try and address it soon.


Compare BigInt's performance to GMP's Mpz

I have a little program that calculates the discrete logarithm via brute force. The results:
With num:
► perf stat -B cargo run --release
     Running `target/release/discrete-log`
375374217830

 Performance counter stats for 'cargo run --release':

<PHONE_NUMBER>19      task-clock (msec)         #    1.000 CPUs utilized
               594      context-switches          #    0.002 K/sec
               135      cpu-migrations            #    0.000 K/sec
            17,286      page-faults               #    0.051 K/sec
 1,094,406,976,444      cycles                    #    3.251 GHz
   <not supported>      stalled-cycles-frontend
   <not supported>      stalled-cycles-backend
 2,237,328,931,573      instructions              #    2.04  insns per cycle
   412,172,025,081      branches                  # 1224.351 M/sec
       561,225,355      branch-misses             #    0.14% of all branches

<PHONE_NUMBER>04 seconds time elapsed

With rust-gmp:
► perf stat -B cargo run --release
     Running `target/release/discrete-log`
375374217830

 Performance counter stats for 'cargo run --release':

       9474.006527      task-clock (msec)         #    1.000 CPUs utilized
               218      context-switches          #    0.023 K/sec
               140      cpu-migrations            #    0.015 K/sec
            17,246      page-faults               #    0.002 M/sec
    31,284,339,928      cycles                    #    3.302 GHz
   <not supported>      stalled-cycles-frontend
   <not supported>      stalled-cycles-backend
    67,187,213,256      instructions              #    2.15  insns per cycle
     5,517,801,557      branches                  #  582.415 M/sec
        17,635,988      branch-misses             #    0.32% of all branches

       9.472818425 seconds time elapsed

Can you share the code?  I don't expect to be fully as fast as GMP, but that's a pretty large gap.  There may be some specific places we could do better.

I pushed the code to https://github.com/vks/discrete-log.

See vks/discrete-log#1 -- by tweaking your discrete_log I reduced the difference to ~6x.  That's the sort of range I'm more comfortable with, compared to gmp's optimized assembly code.

num-bigint is migrating to its own repo... please open a new issue if you have concrete suggestions.
https://github.com/rust-num/num-bigint/issues


Heat Trace: Circuit Diagram (Frontend)

Description
Need more
from:
#207
equinor/lighthouse#29
Acceptance criteria
How to test
(hint from devs)

done. https://github.com/equinor/cc-components/commit/1cf3b033cadba6d684870c671499f25792ebd903


SE: validationClockInstant in Testdata

@martin-lindstrom is there a special reason for validationClockInstant? I saw thisin other country files  as well .

@SchulzeStTSI Oops, it must be a mistake in the test generation code. I'll make sure to fix it.
And the reason that you see it in other countries testfiles are most likely that they have copied Swedens solution. I think that this is highly questionable, and only makes sense if the countries in question use the dgc-java library in the exact way as SE is (which I doubt).

See PR https://github.com/eu-digital-green-certificates/dgc-testdata/pull/174

@SchulzeStTSI You seem to have incorporated some sort of check at check-in that fails. https://github.com/eu-digital-green-certificates/dgc-testdata/actions/runs/863709420
Honestly. We need to keep this simple. Nowhere can I find what is failing. The python code that is checking stuff is NOT necessarily correct (which I have proven a couple of times).

@martin-lindstrom the check is still a WIP - I'll remove it from PRs for now, as we have failing files already in the repo. Your checks all passed (a test report is available as workflow artifact), I'll merge the pr.


Cant connect to Project or cluster key not accepting

I have  given key details on the terminal and also try define as env variable  but none working
Note : ip white listed
$ echo $ATLAS_PUBLIC_KEY
SxxxxWxxxx
$ echo $ATLAS_PRIVATE_KEY
xc4xxxxxxxx-4xxxxx1-xxxxx-xxxxxxxx6xx
$ atlascli --publickey xxxxxxxxxu --privatekey fcx9xxxxxxxx-4xxxx1-8xxxx-4xxxxxx

Traceback (most recent call last):
  File "/usr/local/bin/atlascli", line 11, in <module>
    load_entry_point('mongodbatlas==0.2.3b2', 'console_scripts', 'atlascli')()
  File "/usr/local/lib/python3.7/site-packages/mongodbatlas-0.2.3b2-py3.7.egg/mongodbatlas/atlascli.py", line 192, in main
  File "/usr/local/lib/python3.7/site-packages/mongodbatlas-0.2.3b2-py3.7.egg/mongodbatlas/api.py", line 50, in get_this_organization
  File "/usr/local/lib/python3.7/site-packages/mongodbatlas-0.2.3b2-py3.7.egg/mongodbatlas/atlasorganization.py", line 9, in __init__
  File "/usr/local/lib/python3.7/site-packages/mongodbatlas-0.2.3b2-py3.7.egg/mongodbatlas/atlasresource.py", line 22, in __init__
  File "/usr/local/lib/python3.7/site-packages/mongodbatlas-0.2.3b2-py3.7.egg/mongodbatlas/apimixin.py", line 62, in __init__
  File "/usr/local/lib/python3.7/site-packages/mongodbatlas-0.2.3b2-py3.7.egg/mongodbatlas/atlaskey.py", line 35, in get_from_env
  File "/usr/local/lib/python3.7/site-packages/mongodbatlas-0.2.3b2-py3.7.egg/mongodbatlas/atlaskey.py", line 30, in getenv
 `mongodbatlas.errors.AtlasEnvironmentError: Private key environment variable 'ATLAS_PUBLIC_KEY' is not set`

I think this is working in the latest release. Can you give it another try?
https://pypi.org/project/mongodbatlas/


[CELEBORN-1200][CORE][WIP] Scheduler Spark Reduce Task Locality with Celeborn Worker

What changes were proposed in this pull request?
For now, Spark submit job with Celeborn can’t schedule Reduce Task to correct node, due to following parts:
Celeborn Shuffle Write submit MapStatus with Executor Info, but all shuffle data is store in Celeborn Worker
Spark Framework only call MapOutputTrackerMaster to get ShuffledRDD or ShuffledRowRDD prefer location.
Based on the above issues, we modified Celeborn and small part of Spark:
Make Celeborn Master aware Celeborn Worker Topology Location(for now Topology Location means which node to be deployed)
Make Celeborn LifecycleManager aware spark Executor Topology Location
Spark Framework should open the interface to allow the custom shuffle service to provide prefer location info
See mode detail in design doc: CELEBORN-1200 Spark Reduce Task aware locality with Celeborn Cluster
sequenceDiagram
Celeborn Worker->>Celeborn Master : Register self with TopologyLocation

Celeborn Master->>LifecycleManager: Reply Request Slots with TopologyLocation

LifecycleManager->>LifecycleManager: Handle Commit File to Build PartitionLocation with TopologyLocation

CelebornShuffleClient->>LifecycleManager:  Register Shuffle Client with TopologyLocation and Client Address when set up LifecycleManagerRef

SparkDAGScheduler->> MapOutputTrackerMaster: Call to get Seq of host to allocate reduce task

MapOutputTrackerMaster->>ShuffleHandler(CelebornShuffleHandler): Get Seq of host

CelebornShuffleHandler->>LifecycleManager: Get Seq of host

LifecycleManager->>LifecycleManager: Get Partition File TopologyLocation and Find Corresponding Shuffle Client Address

Why are the changes needed?
Based on production practices, when Celeborn Worker and Spark Executor operate on the same batch of Kubernetes nodes and both mount disks using hostPath, we have observed that under limited network IO, the Shuffle Fetch Wait Time is significantly extended.
We expect the Spark Reduce Task to be scheduled to the executor on the corresponding node holding the partition data by simply moving the computing rather than moving the data idea.
So, we propose this PR to make the Celeborn cluster running on Kubernetes aware of the Topology Info (node information for the current implementation) of the Celeborn Worker, Then, simply depend the Spark RDD Prefer Location feature to schedule Reduce tasks to nodes with data.
Does this PR introduce any user-facing change?
No, the specific task assignment logic change is not perceived by the user, but the Task Locality Level change is clearly visible on the spark UI.
How was this patch tested?

✅ Pass CI & Unit Test
✅ Functional Test
🚧 Performance Test

In general, let us move away from making changes to spark (or any other supported compute platform)  to use Celeborn.
If there is required, missing functionality - we should work with those communities to add required support: there might be reasons why it does not make sense to do so, and the relevant community is the best judge to evaluate it

In general, let us move away from making changes to spark (or any other supported compute platform) to use Celeborn. If there is required, missing functionality - we should work with those communities to add required support: there might be reasons why it does not make sense to do so, and the relevant community is the best judge to evaluate it

@mridulm Thank you for noticing this feature. When designing this function, we tried to reduce the modification of Spark.
The Shuffle Manager serves as an adaptable plug-in for Spark. Presently, the Spark framework exclusively supports the shuffle handler and corresponding shuffle writer/reader for extension implementation. However, it lacks an interface for the Preferred Location crucial for scheduling processes.
It is both rational and pivotal for the Spark framework to expose essential methods to plug-ins without altering its own logic. The ideal scenario would involve persuading the upstream community (Spark) to embrace the minor adjustments required.
At present, we are doing some functional and performance verification of this PR. If there is a good improvement, it will be listed in detail in PR and cooperate with the upstream community.
Finally, thanks for your attention! :) The changes to Spark are small and reasonable.
Also FYI @waitinfuture


extraTags support in custom generators

Extended to add extraTags (--validationKeywords option in ts-json-schema-generator) when using custom generators.
This is intended for use with ajv-sanitaizer,  etc.

Thanks

Release https://github.com/azu/create-validator-ts/releases/tag/v1.1.0 🎉


Separate OpenCL Headers and Improve the Installation Script

Separate OpenCL Headers and Improve the Installation Script to automatically download the OpenCL C Headers.
Currently, TornadoVM has a copy of the OpenCL 3.0 headers in the repo. This task is to decouple a hard copy and clone the headers from the official repo during the installation process.

This has been merged: https://github.com/beehive-lab/TornadoVM/pull/294


Boundary Event on a Receive Task following an Event based Gateway

I'm able to set a Timer Boundary event on a Receive Task that follows an Event based Gateway. Should this be possible?

This needs a fix in bpmn-js / BpmnRules.

Waiting for bpmn-js to be released.

Closed via https://github.com/camunda/camunda-modeler/commit/00f3ec8e7d3e5d74b098e716abc3de83ba50e149.


[VS Code] Joining collaboration session: Cannot start 'JoinWorkspaceAsync' while 'JoinWorkspaceAsync' is running.

<!--
For Visual Studio problems/feedback, please use the Report

Sometimes, I'm facing issues while joining and sharing Live share with Collaboratives.

LiveShareLogs.zip
Here is the log file.

@mihir-spinx Thanks for reporting this! We'll investigate these logs and try to get back to you ASAP.

This should be fixed in the new versions of Live Share. Closing the issue. Please re-activate if you see it again.

Thanks! @IlyaBiryukov
I will update my version and then if I found again, I'll let you know.


create-app: remove references to remove-plugin

Hey, I just made a Pull Request!

This PR resolves https://github.com/backstage/backstage/issues/10072 by removing the script in package.json that calls remove-plugin.
It also removes the documentation for remove-plugin. I believe that the documentation is not versioned, so if you prefer to keep the docs around for users of older versions, but mark it as deprecated, I could change that.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[N/A] Tests for new functionality and regression tests for bug fixes
I didn't come across any tests for the code generation in create-plugin that covers package.json
[N/A] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Working on the changeset

This was fixed in https://github.com/backstage/backstage/commit/567b14a27b2a52ebf59a357de95a9a5b1d4be5c0


when using "Cross-cluster Data Migration Tool" , not disable compaction may cause be crash

Steps to reproduce the behavior (Required)
if not set ADMIN SET FRONTEND CONFIG("lake_compaction_max_tasks"="0");  will cause be crash
Expected behavior (Required)
Real behavior (Required)
StarRocks version (Required)

You can get the StarRocks version by executing SQL select current_version()

It‘s required to disable compaction when migrating to a shared-data cluster now. We're also working on not having to disable    compaction in the future.


feat(tutorial): complete step 5 - chennai

https://carbon-tutorial-bijiliaboobacker.mybluemix.net

Works as Expected. Step 5 Passed.


Web Crawlers not indexing the new added components

I have observed that after adding new components to the shadcn webpage, the search engine crawlers are not picking them up and indexing them. Can you provide any insights into what may be causing this issue?

Seems to be working fine on google?

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


iOS Scroll Overflow Fix

Pros: Should fix the iOS issue (works on my simulator at least)
Cons: Can no longer scroll the background when the swal is open (is this desired functionality?)

#136 #142 #143

Thank you @acupajoe for this PR! Seems good to me, let me a couple of hours to test it on iPad.
One thing - please exclude all changes in dist/* files from PR (see https://github.com/limonte/sweetalert2/issues/148)

@limonte let me know what your tests find! I've updated the PR and squashed commits.

@acupajoe I merged this code to gh-pages branch to test, you check it yourself here https://limonte.github.io/sweetalert2/
Unfortunately, on my iPad we're still having the same bug.

@limonte http://stackoverflow.com/a/24670659/3629438?

@acupajoe I'm not sure how can we apply that answer to this issue.

I just tried this, and this fix only seems to prevent scrolling of the background.  The screen still 'jumps' and scrolls vertically to the center of the page when the keyboard is focused, which is the main problem identified by #136.

@carter-thaxton thanks for confirming! I have the same result.

@limonte, @carter-thaxton appreciate it guys, I'll keep looking into it!

Have made no additional progress on this: am stuck like everyone else. Am closing PR in the meantime, will reopen if solution is found.


Add Hamming Distance algorithm in C++

It adds the Hamming Distance algorithm using C++ language, moreover I've written some comments to make the code more readable and understandable.

If I've made any mistakes in this pull request (it's my first contribution to a Github project, first pull request) let me know: leave a comment below.


keyboard shortcuts modal: Add section for Basic shortcuts.

We should copy the "The basics" section from https://chat.zulip.org/help/keyboard-shortcuts into the top of this modal:

You can get to the modal by typing ?.
This section can maybe be two columns wide? Or one column, but centered, and the two columns can be done as followup.

It seems you've just enabled the issue triaging. I'm just scraping all issues from your repository and will give you some more information about this in a few minutes or so.
Because of the rate limit we can't scrape all information (including all comments and authors) right now - our system is already set up to scrape this in the next days over which the predictions will become more precise every day.
Sit tight!

@zulipbot claim

@psycho-valker Hey there, I hope you noticed that I already have a PR open for this, so it'd be best if you could find a different issue to work on. :)

@synicalsyntax , yeah sure :)


docker run with wasmedge shim stop working #81

Issue Highlight

Test below command fail due to c2c2d0d98237e297e72cbcf9c695a4a215a39bad #81

docker run --rm --runtime=io.containerd.wasmedge.v1 --platform wasi/wasm jorgeprendes420/wasmtest echo 'hello'

Fail commit need run with wasmedge 0.12.1

[x] Test below command fail due to ca5260fd34635ca56d81db3f59ee8672fc7fde68  #78

git clone https://github.com/WasmEdge/wasmedge_hyper_demo.git
cd wasmedge_hyper_demo
docker compose up client

Fail commit need run with older wasmedge 0.11.2
[Update]
The shim now requires the entrypoint path to be resolved using normal posix executable resolution now.
so ENTRYPOINT need start with / is the new usage restrictions and add padding / in path could resolve the second one.

Motivation
Due to the plan of deprecating the fork under Second State, I need to conduct an evaluation of the current functionality of containerd/runwasi before proceeding. I have discovered that using the wasmedge runtime with Docker has been broken for quite some time (all testing while ctr is working fine). Here, I am providing a document that includes the codebase and process I have been using to test docker run.

I've identified the underlying issue in containerd-shim and created an upstream PR: https://github.com/containerd/rust-extensions/pull/151
Once that's merged upstream we need to bump the containerd-shim dependency here. This will also require bumping the ttrpc dependency to 0.8.0.
We should also add a test to make sure we catch these kind of issues.


Enable Graphicle.final to be computed from edge info if missing from ParticleSet

In the case that a Graphicle object has a ParticleSet without a final mask, compute it from the adjacency.

Added failing test for subscripting Graphicle objects. This has broken, because the cached_property of Graphicle.final is now showing up as an attrs field, or something, and getting passed to the Graphicle constructor method. Needs fixing before merging.


.uploadProgress cycles three times per upload?

Not sure if this is expected behaviour, but for each multipart upload, the upload progress cycles 3 times. First 1% to 100%, then 50% to 100%, then 60% to 100% (or slight variations thereof). I was expecting to see a single progress for the complete upload.

To properly investigate this issue we need you to follow the issue template and provide the required information. A test project would help the most.


gorm.DB callback rollback

Your Question
if i use gorm callback,  my function is failed, transaction rollback, but callback is already running, how can i rollback this callback, if func failed, i don`t want use callback

Check error in your callbacks with
db.Error == nil

is this db?

yes

i wrote an demo, but it`s runing

i use gorm v2


Make nntrainer dependent on ml-api-common package

Now that ml-api-common package is ready, nntrainer can be depending on the package instead of workaround.
Let's make it happen

:octocat: cibot: Thank you for posting issue #885. The person in charge will reply soon.

:octocat: cibot: Thank you for posting issue #885. The person in charge will reply soon.

This is resolved thanks to @jaeyun-jung


Command Palette integration

I've never used the Refactor menu in VSCode, so I was surprised to find out it doesn't seem to be integrated with the Command Palette (I can't find Refactor commands through it, like Surround With etc.).
The Command Palette is my preferred method of interaction with this type of command so I don't have to remember custom keyboard shortcuts (or god forbid, use a mouse 😄 ).
Is there a way to add some/all of these commands to the Command Palette? Or is there a design reason those aren't tied together?
Thanks! Love the power of the extension, just trying to figure out how to fit it in my workflow.

Thanks for the suggestion!
Code actions (as shown in the code action menu) are context specific and are not available most of the time. Adding them to the command palette would add a lot of commands which won't be working most of the time.
I'm keeping this issue open, in case I find a way to filter/hide them when they are not available for the given cursor location.

Adding them to the command palette would add a lot of commands which won't be working most of the time.

Good point, I'm surprised that there's not a way to make them context-dependent, doesn't look like there is...
I wonder how big of an issue it is to have not-working commands available, however? I guess there are three reasons I can think of to avoid them, and then my thoughts on those...

avoid polluting global namespace

I just looked through my palette by hand and there are hundreds of commands there that I've never seen before 😅 And most of them are irrelevant to most contexts. (eg ESlint commands in a Ruby file, CSV highlighting commands in JS, etc...) So I don't think namespace pollution is a problem in practice, at least for me?

reduce discoverability of important P42 commands (eg licensing commands)

thought, maybe a different prefix for the refactor actions?

user frustration at broken commands

maybe make it a setting, and/or when an action is not available pop up a toast pointing users to the refactor menu to discover which actions are currently available?
most of the time I know the action I want to take, and it's essentially always been available when I go through to the refactor menu, so at least for my usage pattern it wouldn't be frustrating


Error in Multi-Page Xamarin.Forms Tutorial. Step 9

In step 9 of this tutorial there is an error in line 23 and 28, in function OnSaveButtonClicked, of the example code. The code should be File.WriteAllText(filename, editor.Text);

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

ID: 60587f77-05de-89b9-8a08-c7e7221d27af
Version Independent ID: 4080b687-b353-f833-4bb7-a7a3f9993338
Content: Perform navigation in a multi-page Xamarin.Forms application - Xamarin
Content Source: docs/get-started/quickstarts/multi-page.md
Product: xamarin
Technology: xamarin-forms
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Hi @danixbsc
Afraid not. If you look at step 8 in the tutorial, the Editor no longer has an x:Name, and therefore can't be referenced in the code in step 9.


Error in GPUTree explainer- cannot import name '_cext_gpu'

I am trying to use GPUTree explainer, however, the explainer gives me error. See below my codes:
explainer = shap.explainers.GPUTree(rf_model)
shap_values = explainer(X_test)

The last command gives me the following error:
cuda extension was not built during install!
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
Cell In[45], line 2
      1 start_time = time.time()
----> 2 shap_values = explainer(X_test.head(100))
      3 end_time = time.time()
      4 print("seconds taken: ", end_time - start_time)

File C:\Python311\Lib\site-packages\shap\explainers\_tree.py:262, in TreeExplainer.__call__(self, X, y, interactions, check_additivity)
    259     feature_names = getattr(self, "data_feature_names", None)
    261 if not interactions:
--> 262     v = self.shap_values(X, y=y, from_call=True, check_additivity=check_additivity, approximate=self.approximate)
    263     if isinstance(v, list):
    264         v = np.stack(v, axis=-1)  # put outputs at the end

File C:\Python311\Lib\site-packages\shap\explainers\_gpu_tree.py:76, in GPUTreeExplainer.shap_values(self, X, y, tree_limit, approximate, check_additivity, from_call)
     73 transform = model.get_transform()
     75 # run the core algorithm using the C extension
---> 76 assert_import("cext_gpu")
     77 phi = np.zeros((X.shape[0], X.shape[1] + 1, self.model.num_outputs))
     78 _cext_gpu.dense_tree_shap(
     79     self.model.children_left, self.model.children_right, self.model.children_default,
     80     self.model.features, self.model.thresholds, self.model.values,
   (...)
     84     output_transform_codes[transform], False
     85 )

File C:\Python311\Lib\site-packages\shap\utils\_general.py:19, in assert_import(package_name)
     17 msg,e = import_errors[package_name]
     18 print(msg)
---> 19 raise e

    [... skipping hidden 1 frame]

Cell In[39], line 1
----> 1 shap_values = explainer(X_test.head(100))

File C:\Python311\Lib\site-packages\shap\explainers\_tree.py:262, in TreeExplainer.__call__(self, X, y, interactions, check_additivity)
    259     feature_names = getattr(self, "data_feature_names", None)
    261 if not interactions:
--> 262     v = self.shap_values(X, y=y, from_call=True, check_additivity=check_additivity, approximate=self.approximate)
    263     if isinstance(v, list):
    264         v = np.stack(v, axis=-1)  # put outputs at the end

File C:\Python311\Lib\site-packages\shap\explainers\_gpu_tree.py:76, in GPUTreeExplainer.shap_values(self, X, y, tree_limit, approximate, check_additivity, from_call)
     73 transform = model.get_transform()
     75 # run the core algorithm using the C extension
---> 76 assert_import("cext_gpu")
     77 phi = np.zeros((X.shape[0], X.shape[1] + 1, self.model.num_outputs))
     78 _cext_gpu.dense_tree_shap(
     79     self.model.children_left, self.model.children_right, self.model.children_default,
     80     self.model.features, self.model.thresholds, self.model.values,
   (...)
     84     output_transform_codes[transform], False
     85 )

File C:\Python311\Lib\site-packages\shap\utils\_general.py:19, in assert_import(package_name)
     17 msg,e = import_errors[package_name]
     18 print(msg)
---> 19 raise e

    [... skipping hidden 1 frame]

Cell In[45], line 2
      1 start_time = time.time()
----> 2 shap_values = explainer(X_test.head(100))
      3 end_time = time.time()
      4 print("seconds taken: ", end_time - start_time)

File C:\Python311\Lib\site-packages\shap\explainers\_tree.py:262, in TreeExplainer.__call__(self, X, y, interactions, check_additivity)
    259     feature_names = getattr(self, "data_feature_names", None)
    261 if not interactions:
--> 262     v = self.shap_values(X, y=y, from_call=True, check_additivity=check_additivity, approximate=self.approximate)
    263     if isinstance(v, list):
    264         v = np.stack(v, axis=-1)  # put outputs at the end

File C:\Python311\Lib\site-packages\shap\explainers\_gpu_tree.py:76, in GPUTreeExplainer.shap_values(self, X, y, tree_limit, approximate, check_additivity, from_call)
     73 transform = model.get_transform()
     75 # run the core algorithm using the C extension
---> 76 assert_import("cext_gpu")
     77 phi = np.zeros((X.shape[0], X.shape[1] + 1, self.model.num_outputs))
     78 _cext_gpu.dense_tree_shap(
     79     self.model.children_left, self.model.children_right, self.model.children_default,
     80     self.model.features, self.model.thresholds, self.model.values,
   (...)
     84     output_transform_codes[transform], False
     85 )

File C:\Python311\Lib\site-packages\shap\utils\_general.py:19, in assert_import(package_name)
     17 msg,e = import_errors[package_name]
     18 print(msg)
---> 19 raise e

File C:\Python311\Lib\site-packages\shap\explainers\_gpu_tree.py:13
      5 from ._tree import (
      6     TreeExplainer,
      7     _xgboost_cat_unsupported,
      8     feature_perturbation_codes,
      9     output_transform_codes,
     10 )
     12 try:
---> 13     from .. import _cext_gpu
     14 except ImportError as e:
     15     record_import_error("cext_gpu", "cuda extension was not built during install!", e)

ImportError: cannot import name '_cext_gpu' from partially initialized module 'shap' (most likely due to a circular import) (C:\Python311\Lib\site-packages\shap\__init__.py)

I suspect this is becuase shap installation could not compile cext_gpu.cu as I do not see _cext_gpu in shap directory. As file /explainers/_gpu_tree.py has from .. import _cext_gpu, and it is unable to pull that module.
I am working on windows 11 and my shap version is 0.46.0.

Hi,
and thanks for reporting this.
Did you install shap using
python setup.py install

@CloseChoice No I installed shap using pip

@LSRathore that might be the mistake, gpu support is only available if installing via (you need to clone the repo first)
python setup.py install


onContextMenuItem mouse click type

Thanks for making this. It's made adding actions to tables much easier.
Most links on the internet seem to allow a user to right click on them to bring up the native browser context menu and then selecting to open them in a new tab for example. They also usually open in a new tab when clicking on them using the middle mouse click.
Is there a way I could inject the href into each menu item before opening the menu, and keep the menu open when right clicked so as to show the native link context menu?
Thanks again for your work on this plugin.

Looking into this, this weekend. Sorry for the delay.

It is possible to keep the browser context menu at least when using a contextMenuButton ?
Without that it's impossible for users to right-click and copy text or use a open link...
Thanks

@nicgravel Yeah, you could do something like this for now:
        beforeContextMenuRow: function(e, row, buttonElement){
            if(!buttonElement){
            	row.dispatchEvent(e);
                return;
            }
            else {
            	$table.bootstrapTable('showContextMenu',{event:e, contextMenu:'#files-menu'});
            }
            return false;
        }


Created the Schiene Shipyards Reach II

About the PR
This PR adds a Remaster of the Reach shuttle, known as Reach II ! It is larger, more complex and with more and modernized features.
Screenshots

Changelog

:cl: Schiene

add: The SS Reach II, a successor to the SS Reach shuttle, has been put into service.

Having a maprender to look at would be nice.
Stuff that stands out to me from a broad view:

Docking ports look not standard.
Laying tiles diagonally like the glass ones doesn't look good. Same with diagonal firelocks.
That middle part looks awfully susceptible to being cut off.
Map looks too big for lowpop.
There doesn't seem to be a lot of maintas areas or anywhere out of the way for traitors?

Having a maprender to look at would be nice.
Stuff that stands out to me from a broad view:

Docking ports look not standard.
Laying tiles diagonally like the glass ones doesn't look good. Same with diagonal firelocks.
That middle part looks awfully susceptible to being cut off.
Map looks too big for lowpop.
There doesn't seem to be a lot of maintas areas or anywhere out of the way for traitors?

I've made the map over two weeks ago. When it was made, and only after I already spent two months on it, was I told we're having a mapping freeze. This map has been unupdated since it was put up. It likely doesn't even work by now regardless of any small issues.
The middle part is quite a few tiles wide, more than enough to be immune to all but seriously heavy bombing.
Standardized docking ports weren't a thing when I made this.
I was told they work diagonally, so I rolled with it.
It's got 50 named job slots, and infinite passengers. It ain't low-pop.
It has as much maints and little nooks and crannies as I could reasonably put on a ship of that size.

Having a maprender to look at would be nice.
Stuff that stands out to me from a broad view:

Docking ports look not standard.
Laying tiles diagonally like the glass ones doesn't look good. Same with diagonal firelocks.
That middle part looks awfully susceptible to being cut off.
Map looks too big for lowpop.
There doesn't seem to be a lot of maintas areas or anywhere out of the way for traitors?

I've made the map over two weeks ago. When it was made, and only after I already spent two months on it, was I told we're having a mapping freeze. This map has been unupdated since it was put up. It likely doesn't even work by now regardless of any small issues.
The middle part is quite a few tiles wide, more than enough to be immune to all but seriously heavy bombing.
Standardized docking ports weren't a thing when I made this.
I was told they work diagonally, so I rolled with it.
It's got 50 named job slots, and infinite passengers. It ain't low-pop.
It has as much maints and little nooks and crannies as I could reasonably put on a ship of that size.

But just to add, I have felt and still do feel like I just wasted two months on this.

But just to add, I have felt and still do feel like I just wasted two months on this.

I'm the person who made the issue and I was expecting reach 1 to get rotated out for this.
With that being said making a map out of nowhere shouldn't come with the expectation it gets merged in the same way I don't expect a first draft of code to get merged as is. Making a map without prior consult comes with the risk it gets rejected which also applies to https://github.com/space-wizards/space-station-14/pull/9686 and any other code that gets put up without prior consult. I've put lots of work into prs only to have them rejected or reverted and don't take it personally. I spent dozens of hours on the box2d port and it got reverted within a day.
Maintainers have lives too. Reviewing a map is a large piece of work. I could review a dozen other, smaller prs in the time I could spend reviewing this. I spend many hours a week just reviewing other people's work when I could be doing other things I enjoy doing. We have maybe 5 active maintainers on content atm: mirrorcult, electrosr, wrexbe, moony, and myself and receive 500-600 prs a month so large ones are going to sit longer than small ones as we donate our free time for this.
Fixing the prototype names would take me 20 minutes to do and I wouldn't expect a mapper to do it.
Considering you don't seem interested in the map getting reviewed further I'm gonna close the PR for now.


iOS still doing backup to iCloud

Looking at Issue #40 and Issue #44 no backup to iCloud and remove files/ prefix
we can see that there is an implementation to not backup to iCloud. But while I was testing my application for submission to Apple Store I realize that it's still got my extracted folder to iCloud.
So, I changed it to use the unzippedPath instead of the path.
Just for you to know, I'm using the follow configuration for ContentSync:
var sync = ContentSync.sync({ src: metadata.url, id: 'GVM', copyCordovaAssets: true });

I'm not sure if this is the correct way to do this. Should I mark either the path and the unzippedPath with the attribute? or Just the unzippedPath is ok?

@eberlitz probably both? Do you want the archive to end up in iCloud ? Also you can use sync on images and videos as well. Would you want those to be in iCloud ?

OK, so I changed to deal with both path and unzippedPath.


Remove --dfp --ffp from ASHLAR call when there are no profiles

ASHLAR can be run without illumination profiles. However, the current call still has --dfp and --ffp even when no profiles are supplied.

I think this issue is related:
Caused by:
  Process `ashlar` terminated with an error exit status (1)

Command executed:

  ashlar  -m 30 --pyramid --ffp Scan_20191107_121923_01x4x00775-ffp.tif Scan_20191108_114610_01x4x00775-ffp.tif Scan_20191113_110818_01x4x00775-ffp.tif Scan_20191114_120559_01x4x00775-ffp.tif Scan_20191115_102223_01x4x00775-ffp.tif Scan_20191119_104911_01x4x00775-ffp.tif --dfp Scan_20191107_121923_01x4x00775-dfp.tif Scan_20191108_114610_01x4x00775-dfp.tif Scan_$

Command exit status:
  1

Command output:
  usage: ashlar [-h] [-o DIR] [-c [CHANNEL]] [--flip-x] [--flip-y]
                [--output-channels [CHANNEL [CHANNEL ...]]] [-m SHIFT]
                [--filter-sigma SIGMA] [-f FORMAT] [--pyramid]
                [--tile-size PIXELS] [--ffp [FILE [FILE ...]]]
                [--dfp [FILE [FILE ...]]] [--plates] [-q] [--version]
                [FILE [FILE ...]]

Command wrapper:
  usage: ashlar [-h] [-o DIR] [-c [CHANNEL]] [--flip-x] [--flip-y]
                [--output-channels [CHANNEL [CHANNEL ...]]] [-m SHIFT]
                [--filter-sigma SIGMA] [-f FORMAT] [--pyramid]
                [--tile-size PIXELS] [--ffp [FILE [FILE ...]]]
                [--dfp [FILE [FILE ...]]] [--plates] [-q] [--version]
                [FILE [FILE ...]]

Work dir:
  /home/ds230/work/77/9dea62a9d3a52666f62717275df8b9

Tip: when you have fixed the problem you can continue the execution adding the option `-resume` to the run command line

executor >  slurm (1)

Can you share the .command.sh from the work/ directory?
Looks like it's finding the illumination profiles, but not the raw images. The pipeline assumes that raw images end in .ome.tiff and reside in raw_images/ subdirectory:
https://github.com/ArtemSokolov/mcmicro-nf/blob/a61b9ab47ba2aececd072ecd446eccf08fd9cb2b/main.nf#L48
Do these assumptions hold for your dataset?

It was raw_files


replace deleteProject with stopProject

Issue
Close #98
Description

Change deleteProject to stopProject

Screenshots

Hi @joseliecast
Do you think we can remove the primsa generated file in the commit?

I'll create a ticket to research more what to do about generated files.


High Affordance Buttons

New variants to support high affordance

May require new tokens/variables depending on solution. Please keep me in the loop with any progress, thanks 😄

When @dplsek is back from annual leave, finalised spec to be completed + ready for dev/ variables (@pseys )

returning to backlog until we have more capacity and button is stable


How  transform your code to multi nodes？

thanks for your amazing work, i want change your code using multi cpu nodes. Do you have some advice???

Hi @dreamlychina , Thanks for your interest. The code should work with multi cpu nodes. In MPI, you can launch using mpirun -np ${num_proc} where num_proc can be the total number of cores on multiple nodes.