Setting custom templates specifically to areas

I would like to bring back this issue that I know has been previously discussed in #1105.
I think this feature was very useful and I would like to re-open the discussion on whether it would be possible to bring that back. @aembler mentioned that something about supporting this also for particular areas but I haven't heard anything about that since that (which was in September).
I personally think that this functionality should be brought back, as mentioned in the other issue thread.

Just for reference, the last 4 projects we've implemented for 5.7, we've missed this feature in 2 of them.

Yeah, I'd be interested in hearing some feedback on the old API, etc.. Certainly don't want to keep out a useful feature but the way we did it originally always seemed a little hacky to me, and I'm not sure why.

The old system was flawed because it didn't work when the block was added in first instance. The AJAX stuff didn't know about the defined template. That was often an issue for us. Telling customers to publish changes and reload the check the change wasn't the best thing to do..
If you add the old functionality back into 5.7, which I'd support, please use the page theme class and add another method and make sure it works when a block is added.

Yeah, and I think in fact it also lost the template when you just entered the edit mode, no matter when the block was added.

Don't remember. We ended up writing our own added which used an event to set the block template.. It was saved in the database which made sure everything worked as expected..

@ahukkanen Ah yes. That was a persistent problem. We'd want to make sure that custom templates were always honored even in edit mode, etc..

We used this funcitonality extensively. While it had it's flaws in 5.7, it really helped to our customers to do easy managment of blocks where we had stuff pre-defined for them.
Stuff like auto-resizing images to the the correct sizes for specific areas, correct menu views for specific locations etc. etc.
It would really be helpful if this functionality was re-created in some form for 5.7.

This is now fixed in develop and will be released in the next release of concrete5. Syntax is as follows:
<?php 	$a = new Area('Main'); 	$a->setCustomTemplate('image', 'responsive_image'); 	$a->setCustomTemplate('content', 'content_block_custom_template'); 	$a->display($c); ?>
This shouldn't have the same issues that it had in 5.6, because we're using a similar method to the theme-based custom templates: any time a block is added with a custom template we just set the custom template record on the block. This means no problems with cache, etc..
I've also made it possible to select this custom templates in composer output control blocks – so you can set a custom template on a block you're making editable in composer, and it'll be retained.


Merge 4.10.x at 7c8e93bc9d41 into 5.3.x

4.10.x:
(packaging) Update puppet version to 4.10.8
(PUP-7933) Remove documentation about last in scheduledtasks type
(PUP-7848) Simplify Regexp for VAR_NAME and add test for performance
(PUP-7848) Fix problem with VAR pattern and longer segments
(PUP-7902) Add test to assert that only one newline is stripped last
(PUP-7902) Ensure that empty heredoc lines are not trimmed
(PUP-7902) Add test asserting that empty heredoc lines are not trimmed

CLA signed by all contributors.

I used a PR for this as there were some merge commits.  The puppet version and the spec tests in commit 9ac850389e747d66ccd

PR title says 5.3.x, but target is master - which is correct?

@branan DOH  Apologies....yes you're right.  changed target to 5.3.x

There is one additional commit on 4.10.x that doesn't come with this mergeup, is it intentional to leave https://github.com/puppetlabs/puppet/commit/8bcaba7d90ea9115f6e89a6805d20f4c866c7f3f behind?

@Magisus  Wasn't intentional.  I raised the PR 5 days ago, that commit is only 22 hours old.

Alright, it'll come along next time


Layer regen faster than script

Sometimes when I run the script, a layer might regen while the script is mining, which causes it to hang since it won't stop the script until it has mined all the layers in a tab, but it also stops mining before the script itself stops.
Edit: from what I've seen, this may be an issue with how fast turbo exec runs the script, in comparison to how fast the game is capable of mining the tiles.

I'm not sure I completely understand the scenario you're describing. When you say "hang", do you mean that it gets stuck on a layer before the last one, or something else?
It is known that if you use this with turbo exec and there's a lot of unmined layers ready, the whole game will hang for a second or two when you enter the mine, because it's furiously mining all the layers between frames. There's not much I can do about that beyond deliberately slowing it down.

Oh, the other reason why I'm confused: Half the script (the part that digs tiles) doesn't exit until you leave the mine. So in that sense it never really stops mining, only the layer-generating part stops.

ahh ok


Grift

Please open an Apache Jira ticket per the contributing guidelines so we know more about what this is.


ng serve error

When I do npm install -g angular-cli I get the warning below, and ng serve is not working also.
$ npm install -g angular-cli
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs version 3 and before will fail on newer node releases. Please update to<EMAIL_ADDRESS>as soon as possible.
npm WARN deprecated<EMAIL_ADDRESS>This package has been discontinued in favor of<EMAIL_ADDRESS>npm WARN deprecated<EMAIL_ADDRESS>This package has been discontinued in favor of<EMAIL_ADDRESS>npm WARN deprecated<EMAIL_ADDRESS>graceful-fs version 3 and before will fail on newer node releases. Please update to<EMAIL_ADDRESS>as soon as possible.
/usr/local/bin/ng -> /usr/local/lib/node_modules/angular-cli/bin/ng
/usr/local/lib
└──<EMAIL_ADDRESS>
ng new test3
// all ok...

ng build
ng serve
Could not find watchman, falling back to NodeWatcher for file system events.
Visit http://www.ember-cli.com/user-guide/#watchman for more info.
Livereload server on http://localhost:49153
Could not serve on http://localhost:4200. It is either in use or you do not have permission.

how should I properly update graceful and lodash? im doing npm install lodash -g and npm install graceful-fs -g succesfully. but the error above kees saying i have old versions
Thanks!

Hi. Are you already running something on port 4200? If not try using some higher port: ng serve --port 10000 for example.
About warnings when installing angular-cli; just ignore them. It means that some angular-cli dependencies are using deprecated versions of packages.

Thanks for the info. It lead me to find the fault. Had to enter sudo ng serve because of some permission error.
without the sudo, i get this:
Error: EACCES: permission denied, open '/Users/macbookuser/.config/configstore/ember-cli.json'
You don't have access to this file.

@karjac14, did you managed to solved the problem? How to change the permission? I'm getting the same error without using sudo.


Grab .wasm binaries from the web

I want to be able to share modules with others but not require them to download/compile them themselves
Spin.toml
My intuition says this URL would be written in the spin.toml like so:
[[component]]
id = "key-value"
source = "https://github.com/ecumene/components/.../hello-world.wasm"

But how would we get the modules? I think there are generally two ways to achieve this

Build a tool that saves them to a cache based on the spin.toml and change nothing here
Have Spin download these at runtime

We could also do both! Maybe we could include a mapping of these modules to their place on the drive, and that would leave it up to something built into Spin or some manager to resolve them.

We could combine the two ways: having spin download these wasm files at runtime and cache them to a spin.lock file, which includes the checksums. In this way when the next time spin is running, if the checksum of the spin.toml is not changed, then can use the cached wasm files. And of course if the lock file is deleted, then spin will always fetch the newest remote wasm modules.

Would the lockfile map the downloaded modules to their place on disk too?

I would decouple the two conversations as two distinct ones:

using HTTP URLs as module sources in spin.toml files
caching pulled modules (and assets), which also includes when running from Bindle, and I think it makes sense to have a common caching implementation for various sources.

For 1, do we need to consider any authentication mechanisms when performing HTTP requests, or are we ok with public sources for now?
(I think for the first iteration on this, public sources, like GitHub releases, are totally fine).

For 1, do we need to consider any authentication mechanisms when performing HTTP requests, or are we ok with public sources for now?

Like HTTP basic auth? Or something else like a cookie?
For my purposes public sources are fine

I think we should default to verifying the integrity of remote-sourced binaries to encourage good security practices. That might look something like:
[component.source]
url = "https://raw.githubusercontent.com/..."
integrity = "sha256:abc123..."

If necessary, we could allow explicit integrity opt-out, e.g.: integrity = "insecure"
This could also (later) be expanded nicely to code signing, e.g. integrity = "ed25519:<pubkey>".

I'm not opposed to this (provided we address the software supply chain risks) but would like to get a sense for where it fits in with bindle publishing and the registry.  Presumably the situation here is that a developer would like to reuse a handler, such as Bartholomew, but within their own application context; whereas bindles are more about providing full applications.
Should we instead provide a convenient way for users to publish and reference module-only bindles, with all the guarantees that provides consumers around provenance and immutability?  Or would the "plain HTTP" solution still be necessary because there aren't enough well known bindle servers around?
Longer term this speaks to questions such as the component registry, and the composing of applications from public, published components.  So let's get a sense of where we envisage this being used, whether it is about convenient short-term sharing within a close collaboration, or long-term publishing of components designed for reuse.
I guess I am worried that we risk doing the unreliable, physically coupled publishing strategy first, and risk ending up with a spaghetti ecosystem with high vulnerability to supply chain attacks, which becomes entrenched before we have a structured alternative.  On the other hand, I do see the value of convenient sharing and don't want to hold it up while we labour on a 'perfect' solution!


Question: How to uninstall posh-git ?

Hi,
In the case were you no longer require posh-git, how does one go about uninstalling it ?
Thanks,
E

It depends on how you installed it.  If you used Chocolatey, I think the command would be choco uninstall poshgit.  If you used Install-Module (PowerShellGet), then use Uninstall-Module posh-git.

hmm, appears I just ran .\install.ps1

In that case, remove the folder containing the install.ps1 file.  Edit your profile by executing notepad $profile, remove any lines that refer to posh-git or profile.example.ps1.  If there are no lines in this file, then check notepad $profile.CurrentUserAllHosts and remove those lines from this file.

hmm, Uninstall-Module posh-git, throws this error:
PackageManagement\Uninstall-Package : No match was found for the specified search criteria and module names 'posh-git'

So, you didn't install with Install-Module.  Did you install using Chocolatey?  Or did you git clone this repo?

Here is a screenshot of what I did:

There was an entry in the profile ($profile) to posh-git and I removed it.  Since Uninstall-Module posh-git is failing, can you tell me how I can verify it is uninstalled ? :)

Delete the file C:\Users\Exocomp\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 and remove the R:\posh-git folder (unless that's a shared folder other folks use).
To verify it is uninstalled from PowerShell's perspective, run Get-Module -ListAvailable posh-git.  That should return nothing.
So you set your execution policy back to Restricted? I take it you don't normally run PowerShell scripts or modules?

Lately I have been using Powershell quite a bit with managing a few servers and in TeamCity for my CI server, I normally change the policy and run the scripts I need and go back to restricted, I'm a bit paranoid when it comes to security.  However, I don't call my self a powershell guru by any means, :)
Anyway, nothing wrong with posh-git it is just that I got used to gitbash and I thought I'd try posh-git.
The command "Get-Module -ListAvailable posh-git" returns nothing.  But I don't understand how I was using posh-git and then have it disappear.  See pic here where it was working:

Any other ideas or should just consider this done and move on? :)

It was working because you profile was likely dot sourcing (including) the profile.example.ps1 file.  That file overrides PowerShell's prompt function to display Git status summary information.  When you removed that from your profile, your prompt is no longer being overridden when PowerShell starts.

Ok, so what your telling me is it was never installed on the system to being with, it was just loading the profile and importing the module from git repo for that session ?

That is what I suspect but it's hard for me to say for sure.  It appears that posh-git is located on your R: drive.  Is that a network share?  How did the posh-git bits get to be in R:\posh-git?

Appears I cloned it.

It is a temporary drive.  I think it is just my confusion so basically I thought that by calling install.ps1 it installed it on the machine but all it did was update the profile and load it from R:/posh-git for every session.  That makes sense to me.  If that make sense to you then I can move one.  What say you? :)

all it did was update the profile and load it from R:/posh-git for every session

That is correct.

Excellent, thanks for your assistance!

get-module posh-git | eliminar-módulo
funciono gracias

get-module posh-git | eliminar-módulo
funciono gracias

I just ran $env:PSMODULEPATH to get my onedrive path, deleted the module and powershell folder from that onedrive path and that fixed it. Issue is using -Scope currentuser when installing it and it goes to onedrive files on demand. Terrible from MS to not give it rights to uninstall cleanly in powershell. I also tried the 3+ versions of powershellget to no avail. erghhhhhhhhhhhhhhhh


Method does not override or implement a method from a supertype

When following the instructions provided in the README i get the following error when compiling the project:
node_modules\react-native-touch-id-android\android\src\main\java\co\eleken\react_native_touch_id_android\FingerprintPackage.java:24: error: method does not override or implement a method from a supertype
@Override
^
1 error
:react-native-touch-id-android:compileReleaseJavaWithJavac FAILED
I'm not exactly sure what causes the problem, so any help would be greatly appreciated! :)

Experiencing the same issue. Did you manage to solve it? @EliasJorgensen


Add ApiClassExtractor to configuration hash of AbiExtractingClasspathResourceHasher

So we can distinguish between hashes of ApiClassExtractor
and of KotlinApiClassExtractor.
This may fix https://github.com/gradle/gradle/issues/16790.

@bot-gradle test QFL

OK, I've already triggered QuickFeedbackLinux build for you.

@bot-gradle test and merge

Your PR is queued because #16807 is being built.

OK, I've already triggered a build for you.


Ruby on Rails example

Do you have experience using temporal-ruby with Ruby on Rails, and ActiveRecord thread pooling? I think it would require some framework-specific work: https://guides.rubyonrails.org/threading_and_code_execution.html

Hey @bouk! I haven't yet tested it with ActiveRecord (only Rails with Mongoid), but @robholland or @drewhoskins-stripe might have.
I think this should be straight forward using a new middleware (feel free to submit a PR with it as it might be helpful for other users as well)

I'm interested in this as well.
We are adding Temporal to our Rails app running with Sidekiq. If there was a good migration doc, I imagine a lot of people would happily start migrating over certain job queues.

for those who are looking for this, Lenny (above) did follow through on writing an example! https://github.com/milk-video/temporal-rails-example

Hello, I took a look at the above repo example, but I don't think it shows how to deal with DB pool and threading.
I integrated Temporal in our Rails application and I initialize it with a rake tasks so that it gets access to the rest of the code.
I defined a workflow that calls an async activity and this one uses ActiveRecord to fetch data from the DB. If I run that workflow 5 times on my local, it takes 5 connections from the DB pool and never release them even if the activity has completed.
Unless I'm missing something, I feel like this should be handled by this gem?

I added a middleware that wraps yield in a block that ensure DB connections are released, this seems to fix the issue for now.
    class DbConnectionHandlerMiddleware
      def call(_)
        ActiveRecord::Base.connection_pool.with_connection do
          yield
        ensure
          ActiveRecord::Base.clear_active_connections!
          ActiveRecord::Base.connection.close
        end
      end
    end

# During the worker initialization
worker.add_activity_middleware(DbConnectionHandlerMiddleware)


[Docs] Make readme up-to-date

Change the Wall-E 2.2 to Wall-E 2.3
Include Oled images
Change board image

Solved by #99


Linux Jessie & cups 1.7.5-11 misses the last 2 lines of each page printed.

I have an HP Deskjet 6840 which is shared by several PCs (Mac & Linux) around the house.
Under Jessie (kernel 4.9.35-v7+) on a Raspberry Pi 3 (fully updated/upgraded) using HPLIP 3.16.11 and using A4 paper, the printer consistently misses the last 2 lines off every page when using lpr to queue a job.
It is possible to discern that the printer has attempted to print the first of these two lines as there is a feint dotted line along the bottom of the page but  the second of these two lines disappears into a black hole! I suspect that these two lines should actually be the top two lines on the next page.
I haven't selected any particular font, opting for whatever font is the default.
I wondered if the driver was ignoring the paper size in the config and assuming 8.5" x 11" but A4 is approx 11.7" (297mm) long so the page would be adequately long.
The printer test page reports:
Media Limits: 0.12 x 0.12 to 8.15 x 11.56 inches
Has anyone else noticed this "feature"?

I'm guessing this is a margins issue with this printer, which has larger margins when printing duplex output. But not a CUPS issue...
(probably file a bug with the HPLIP folks...)

Hmmm... perhaps, as it only happens with Linux (of just about any flavour). Thanks Michael.


Please ignore - PR raised accidentally

Apologies - I've accidentally raised a PR with the wrong base. I'm working on a fork to make a firefox version of this extension. At this point I don't think it can be easily unified into the original and it makes more sense to keep them separate. Merging this would break compatibility with Chrome, which is definitely not desirable!

Hey @jrockwar,
Thanks for even attempting this! I don't know a ton about firefox extensions, but I would love for this to be available there (and safari). Is the problem that this uses manifest v2 and firefox uses manifest v3? Or is this using some chrome specific functionality that would be hard to support? (e.g. does firefox not yet support offscreen, or it might but with a different api?) Most of those should be workable with some slight tweaks.
Anyway, happy you're taking this on, but I'm also happy to help as it would be nice to do, and I'd prefer to not have a hard fork if possible!

Nice to see you commenting back @erikbrinkman !
To be completely honest, I don't know much about firefox extensions either but I thought this "should" be doable. My experience with TS is nearly non-existent so I've had to use LLMs liberally to cover for my lack of knowledge!
I have something that works now at https://github.com/jrockwar/repubfox. I'd also like not to have a hard fork, as this is "your" extension after all. I also thought raising an issue and waiting for you to solve this for me wasn't a fair ask.
The implementation is messy (mostly due to the LLM-ness of the code) but I have hope that one day I can merge this back, only if I figure out a way to do it without breaking Chrome functionality. For now, my plan (if that's alright with you) is to keep adding improvements (e.g. PDF) and contributing back to your upstream while I figure out if there is a way to merge back the firefox compatibility. I don't want a hard fork either, but I don't want to burden you with having to maintain two extensions while we figure this out.
On the technical side, you were calling a few chrome-specific APIs and I had to tweak how things are done in firefox, but the biggest change was the lack of native MHTML support in Firefox which has required me to write an MHTML generator to play nice with the rest of your code. (https://github.com/jrockwar/repubfox/tree/main/src/mhtml)

That all makes sense. I may have some time over the holiday to take a look. In the meantime I opened up an issue, and updated the readme to link to you for firefox support for the time being.


Remove unnecessary legacy tests

Since the legacy and new names point to the same object,
there is no need to run through all the tests separately

Looks good.  Thanks!


new rule - flag f-strings that contain expressions with the same quote as its outer quote

As a result of PEP 701, in Python 3.12, you are now able to use expression components that contain the same quote as the outer f-string which allow f-strings like this:
foo = f'{os.environ['HOME']}/foo'
Or even nest f-strings:
foo = f"""{f'''{f'{f"{1+1}"}'}'''}"""
However, when using a Python version less than 3.12, the above expressions should raise a SyntaxError. Based on the user's Python version defined in their configuration file, I believe ruff can easily prevent any SyntaxError from occurring if a rule is enabled.

If I'm understanding this correctly, it is one of the task in https://github.com/astral-sh/ruff/issues/6591. I'll merge this into the parent issue. Thanks for the suggestion!


Installation trough composer doesn’t install the actual repo

The title says it all; I was getting multiple 404 errors from API calls while testing some of the plugin functions; search for backupzip classes and didn’t find anything ’bout it in the plugin directory.. because there’s anything about it.

not sure what you mean. please try again to explain what files are missing or what did not work when you tried what.
the repo comes with a php file for the backupzip job class and it registers it with composer autoloading. that plugin vendor folder will be merged with your root vendor folder as intended by kirbys composer installer.
https://github.com/bnomei/kirby3-janitor/blob/master/classes/BackupZipJob.php
https://github.com/bnomei/kirby3-janitor/blob/master/vendor/composer/autoload_classmap.php#L9

if you used janitor in you plugin before also make sure its v2. you might need to remove the dependencies, remove the composer.lock file or force installation using composer require bnomei/kirby3-janitor:^2.5

When using, as written in the doc, the composer require bnomei/kirby3-janitor command add that line in the composer.json file : "bnomei/kirby3-janitor": "^1.4" so there`s a lot of new file/features (I guess) that goes missing. That’s why i said that the "Installation trough composer doesn’t install the [actual] repo".
Once force to 2.5, everything works fine

thanks @jesuismaxime for providing more information. i understand your issue now but i can not find any wrong configuration on my end. everything on packagist seems fine to me.
the composer require will check an existing composer.lock file and if that has a version of janitor 2.0.0 it will not upgrade but use 1.4.2. but that is my only guess how it might happen.


Add most common UK cylinders

Comprehensive list to be defined, but already reported in Google Store was:

standard Faber steel 232bar 12 & 15 L

http://www.divefaber.com/list/print/scuba_lpr.asp?da=11.96&a=14.5
http://www.divefaber.com/list/print/scuba_lpr.asp?da=14.5&a=22

done in 9b430b5efb4f3c153696b4e18d464bbd728fe505


Cw/update GitHub action

What does this PR do?

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

👋 Hi there, this PR looks to be mistakenly opened against the upstream repo from your betterup/datadog-agent fork so I'm going to close it
If you think this is in error please comment further and add a description for these changes - thank you!


feat(app): add UI to each modal step in ot-3 pipette cal

closes RLIQ-227 RLIQ-223 RLIQ-221
Blocked to merge until https://github.com/Opentrons/opentrons/pull/11618 merges
Overview
Add the UI to each step modal in the ot-3 pipette calibration flow: BeforeBeginning, AttachStem, DetachStem, Results. Only adds the UI aspects so nothing is really wired up yet.

Changelog

add the UI for BeforeBeginning, AttachStem, DetachStem, Results, updates tests
extends the PipetteWizardStepProps to include goBack prop.
make subHeader prop optional in SimpleWizardBody
make small UI changes to GenericWizardTile
add probe image to equipmentImages
fix naming in GenericWizardTile related components (story and test)
add probe image and a attach/detach stem image that will be updated later

Review requests

with an OT-3 pipette on the robot, click on Calibrate pipette offset button in the overflow menu. Click through the flow. There should be 4 pages and they should each more or less follow the figma designs. The main things that aren't very finalized are the attach/detach stem images.

Risk assessment
low

TODO: address this comment after that PR merges.


Updating Tanzu Build Service with link to v1.3 on VMware docs

Latest Tanzu Build Service and two earlier version are now on Docs and linked from the master Tanzu landing page.

Thanks, @yugrinov!


Version Requirements: 18.17+

Just a quick note that you must use 18.17+ for the code to work. Using 18.9 for example, fails.
You are using Node.js 18.9.1. For Next.js, Node.js version >= v18.17.0 is required.

One other note: if you are running v. 21+ you get a deprecation warning:
(node:3423) [DEP0040] DeprecationWarning: The punycodemodule is deprecated. Please use a userland alternative instead. (Usenode --trace-deprecation ... to show where the warning was created)

Newest version of NextJS does indeed require Node 18.17+.
As to why the deprecation warning shows when running 21+, I don't think it is a specific issue with this repository, but rather a general issue: depcreation warning
With that being said, I am closing this issue.


Avoid tab when the picker is open

(Thanks for sharing this, it's a really good date picker!)
Is your feature request related to a problem? Please describe.
When the picker is open, pressing tab should not move the cursor in other fields, which can -also- cause some other pickers to show
Describe the solution you'd like
if the picker is open, a preventDefault() should be called if event.key is tab

Hi, I had the same problem than you.
But apparently, you can fix it by adding tabindex="-1" on the inputs where you want to use the picker. It works well for me in Chrome and Firefox.


YouTube & Facebook censoring C.J. Hopkins

https://taibbi.substack.com/p/meet-the-censored-cj-hopkins-critic

Not long ago, Hopkins shared on Facebook a picture of a tower in Dusseldorf on which was written the message, “Vaccination = Freedom.” He compared it to the infamous Auschwitz message Arbeit macht frei, i.e. “Work shall set you free.” Facebook said it violated community standards against “dangerous individuals,” and removed it to prevent “offline harm.” He soon found that friends and acquaintances were prevented from sharing this and other posts of his. A website where he publishes also appeared to be permanently slapped with warning labels, one fairly well-known — he tells the story below.

https://taibbi.substack.com/p/meet-the-censored-cj-hopkins-critic

Not long ago, Hopkins shared on Facebook a picture of a tower in Dusseldorf on which was written the message, “Vaccination = Freedom.” He compared it to the infamous Auschwitz message Arbeit macht frei, i.e. “Work shall set you free.” Facebook said it violated community standards against “dangerous individuals,” and removed it to prevent “offline harm.” He soon found that friends and acquaintances were prevented from sharing this and other posts of his. A website where he publishes also appeared to be permanently slapped with warning labels, one fairly well-known — he tells the story below.


setProgressPercentage is not functional

The progress bar number is rising but the background color is not.

I set shouldAnimate to false and it works normally

Could you post the code you used for the progress bar? Also what device and android level are you using?

Hey @Ryhat could you post more info, or a video of your issue? I was unable to replicate the issue you described. If I can't get more details then I'll be closing out this issue soon.

Oops, didn't mean to hit close there. Keeping this open for a bit longer to potentially hear back from the OP

I'm so sorry that I haven't checked my mailbox for a long time. Here is my code for short.
I have a activity and service.
Activity for display and service for update position.
After I created this issue I found that my UI would freeze, but the service would keep running.
Then I change service to WorkManager and nothing changes.
I try to change RoundedProgressBar to normal ProgressBar and it works fine.
activity:
@Subscribe(threadMode = ThreadMode.BACKGROUND)
    public void onMessage(MessageEvent event) {
        Log.d(TAG, "onMessageEvent: " + event.mMsg);
        Log.d(TAG, "onMessageEvent: " + event.mPos);
        Log.d(TAG, "onMessageEvent: " + event.mIsRunning);
        Log.d(TAG, "onMessageEvent: " + event.mStatus);
    }

    boolean mBound = false;
    WorkService mService;

    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_ufo);

        progressBar = findViewById(R.id.progress_bar);
        progressBar.setAnimationLength(100);

    }

xml
  <com.mackhartley.roundedprogressbar.RoundedProgressBar
        android:id="@+id/progress_bar"
        android:layout_width="match_parent"
        android:layout_height="30dp"
        android:layout_marginTop="8dp"
        android:layout_marginBottom="8dp"
        app:rpbAnimationLength="100"
        app:rpbShowProgressText="true"
        app:rpbTextSize="16sp"
        app:rpbBgTextColor="@color/accent20"
        />

Hi Ryhat, thanks for the response. It's hard to tell, but from the looks of your code it seems like you might be trying to directly update the RoundedProgressBar from a background thread. If that's the case, then you should avoid doing that on Android as that's not recommended. Here's a StackOverflow post with more info about how to safely update views with background threads: https://stackoverflow.com/a/5185155/5759305
If that is indeed the issue then this isn't a bug on the part of the RoundedProgressBar library. However, please correct me if my above assumptions are wrong.

Sorry I'm not a professional Android Java programmer and may have made a very rookie mistake.
I am using eventbus to pass my data. I checked the link and I realized that I used ThreadMode.BACKGROUND but I should use  ThreadMode.Main.
Thank you for your patient reply and sorry for my poor English.

I still have a question. Why official ProgressBar is working fine(I`ve been used 20+ days).

Haha no worries, I think your english is fine, you sound like a fluent speaker.
As for why the official progress bar works in this case I'm not sure, RoundedProgressBar actually uses the "official" progress bar under the hood, it just adds a lot of tricks as well. In general very weird things happen when updating the UI from a background thread so it's hard to know what would be causing this issue.
From your other comment, it sounds like you were able to fix the problem which is great, so I'll close out this issue. If you're still having trouble and your code is on github feel free to send a link and I'll take a look. If it's something simple I'd be happy to take a look and help.


Data Factory: Web Activity Basic authentication dissapeared?!?

Web Activity Authentication issue
Since today 2019-10-29, the authentication type Basic suddenly dissapeared from the control flow component Web Activity. As a result our ADF pipeline does not work anymore and we can not change the authentication of the API itself.
Is this a mistake or will this type of authentication dissapear forever? I haven't seen any updates about this and also the documentation still refers to the basic authentication type.
https://docs.microsoft.com/nl-nl/azure/data-factory/control-flow-web-activity
Please come with a solution!
Best Regards

Documentdetails
⚠ Dit gedeelte niet bewerken. Het is vereist om problemen te koppelen tussen docs.microsoft.com en GitHub.

ID: 34b3d465-6a2b-88ad-6e80-4fb784cd489e
Version Independent ID: 51b70888-d089-7352-4abd-7d587726700a
Content: Webactiviteit in Azure Data Factory
Content Source: articles/data-factory/control-flow-web-activity.md
Service: data-factory
GitHub Login: @djpmsft
Microsoft Alias: daperlov

@RudyEvers Thank you for reaching out and bringing this to our notice. This looks strange, I was able to see all the options in authentication section including Basic.

Could you please try refreshing your browser (or clearing your browser cache) and let us know if you still notice the issue. The strange thing I noticed from the screenshot is that I can see "Username" and "Password" which are the elements/fields of Basic authentication.
If the issue still persists and If you have a support plan you may file a support ticket, else could you please send an email to<EMAIL_ADDRESS>with the below details, so that we can create a one-time-free support ticket for you to work closely on this matter.
Email subject: Data Factory: Web Activity Basic authentication dissapeared?
Thread URL: https://github.com/MicrosoftDocs/azure-docs/issues/41664
Subscription ID:
Data Factory Name:
Region:

Hi @KranthiPakala-MSFT
Thank you for the quick response. I tried a couple of things. Refresh of my browser, cleared the cache. Tried an other browser but that didn't resolve the issue. Really a strange situation.
I will send an email to the AzCommunity. Hopefully it can be sorted out.
Regards,
Ruud

Hi @KranthiPakala-MSFT ,
Issue is caused when using GitHub with ADF. When I enable GitHub the issue occurs and when I don't I can see all authentication types. Not normal behavior I would think.

@RudyEvers Thanks much for sharing your findings. I'm looking into this issue and will keep posted once I have an update.

@RudyEvers Could you please confirm if you were able to see the Basic authentication option before 10/29/2019? And also were there any existing pipelines with Web Activity in Git Mode having Basic Auth setup and working before 10/20/2019 or is this the first time you are trying to use Basic Auth in Web Activity of your Data factory with Git mode enabled?

@RudyEvers I have checked with internal team and received a confirmation that Basic and ClientCertificate authentication types are only available in Data factory "Live Mode" and not in "Git Mode". This is a know limitation.
Having said that , if the user selects Basic or ClientCertificate in Live Mode, then they cannot publish the pipeline to Git. The current available option is to use MSI auth type.
But there is already a work item on this requirement and ADF engineering team is working on it for fixing this to allow in both modes and user should be able to cross publish.
I do not have an ETA yet, but we can expect the fix to be out in the near future.
Apologizes for the inconvenience. If you have any suggestion/feedback regarding this, please feel free share it in ADF user voice forum: https://feedback.azure.com/forums/270578-azure-data-factory. All the feedback shared in this forum is actively monitored and reviewed by ADF engineering team.
Hope the above info helps. Please let us know if you have any further query.

Hi @KranthiPakala-MSFT
Thank you for sorting things out. It is a pitty that basic authentication is not supported in Git mode. For now I changed my environment back to Live Mode and will use the ARM export to deploy it to my production environment. Hopefully it will be available in the near future.
After working with SSIS for years, I must say they are doing a really good job with ADF.

@RudyEvers Thanks for sharing the feedback and sincere apologizes for the inconvenience. Hopefully this fix should be out soon.
Based on this update, I will go head and close this issue. If you have any further query, please feel free to reopen the issue and tag me in your reply. We will be glad to assist you.
Thank you.

Hi
I'm facing same issue with SalesForce Commerce Cloud Connection(obtain access token) activity
Git seems to lose connection password
Do you know please , if issue is fixed now ?
Regards
Christophe

The fix is currently awaiting deployment. As we are currently holding off deployments due to the US holiday, you should see the all authentication modes supported in the Web Activity starting next week. Heads up, you will need to use Azure Key Vault to store your passwords as we do not store them in Git mode (which is why the feature didn't exist at first).


Sanitise XML Request body

We are using 2.9.3 and logging both header and body of the request and response.  As we don't want sensitive information to be logged, we want  sanitize XML request body.
tried using sanitizeArgs but this is not helping.
Any suggestions on how to sanitize  XML request payload

@ravthiru It's worth checking if using sanitizeMatchedBytes against the REQUEST_BODY could work for you.
Otherwise, you could do something like per transaction using ctl:auditLogParts, removing part the REQUEST_BODY (part C) from the audit logs (ctl:auditLogParts=-C) whenever there's a match with the rule that enables XML inspection (ctl:requestBodyProcessor=XML).
A finer-grained support for the Sanitize directives will be implemented in 3.x and is being tracked #1898.


Baseline doesn't work if flyway_schema_history table exists

Which version and edition of Flyway are you using?
Community Edition 6.2.4 (PostgreSQL)
If this is not the latest version, can you reproduce the issue with the latest one as well?
(Many bugs are fixed in newer releases and upgrading will often resolve the issue)
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Command line
Which database are you using (type & version)?
PostgreSQL 10.1
Which operating system are you using?
Docker (CentOS)
What did you do?
(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)
Baseline the database with a specific version. If the flyway_schema_history does not exist, then it's created and the baseline works. If the table exists (but it's empty) then the output shows that the baseline was successful, but no entry is actually written to the table, so the baseline doesn't work as expected.
What did you expect to see?
An entry in the flyway_schema_history table.
What did you see instead?
No entries in the flyway_schema_history table.

This is actually expected behavior. However I agree it's misleading. The answer is to delete the schema history table and try again.
Also, how did you get into a state where the schema history is empty?

Thanks, it works as expected once the table is deleted.
How I got there: I scripted an existing database which had the flyway table in it and was then playing around with various steps in baseline and migrate.
Perhaps a more informative message could be displayed if the table exists, but is empty? Or could it just not apply the baseline as I had expected?

Perhaps a more informative message could be displayed if the table exists, but is empty? Or could it just not apply the baseline as I had expected?

Yes, I 100% agree. It's an unusual case that is rarely encountered in a normal workflow, which is why we haven't given it much attention. We will schedule some work to make the messaging clearer.


Update citation

asterisk for co-first author messes up alphabetical ordering in references section

Thank you for the attention to the all such details.


Can i Add outside item  to items inside grid?

Yes you can just follow this:
https://github.com/ollija/react-native-sortable-grid/issues/8


Fix labels 'blood coagulation in another organism'

Changed labels for 'blood coagulation in another organism'
id: GO:0035806
-name: modulation of blood coagulation in another organism
+name: perturbation of blood coagulation in another organism
id: GO:0035807
-name: positive regulation of blood coagulation in another organism
+name: induction of blood coagulation in another organism
id: GO:0035892
-name: modulation of platelet aggregation in another organism
+name: perturbation of platelet aggregation in another organism
id: GO:0035893
-name: negative regulation of platelet aggregation in another organism
+name: disruption of platelet aggregation in another organism
id: GO:0035894
-name: positive regulation of platelet aggregation in another organism
+name: induction of platelet aggregation in another organism
id: GO:0035899
-name: negative regulation of blood coagulation in another organism
+name: disruption of blood coagulation in another organism

Fix definitions for 'perturbation' terms:
The process in which an organism effects a change that affects  [ blood coagulation in another organism. ]


MicrosoftStsAuthorizationStrategy#getAuthorizationEndpoint() returns incorrect value

See MicrosoftStsAuthorizationStrategy#getAuthorizationEndpoint()
Needs to have the following appended to it:
/oauth2/v2.0/authorize
Resolve #241 first

Fixed in branch release/0.2.0


osm-controller: correctly print byte array

Description:
Correctly prints byte array as a string.
Resolves #3355
Signed-off-by: Atharva321<EMAIL_ADDRESS>
Affected area:

Functional Area

Other
[X]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? no

Did you notify the maintainers and provide attribution?

Is this a breaking change? no

@Atharva321 this PR cherry-picked your original commit as is.

Codecov Report

Merging #3360 (50421f3) into main (0915de2) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##             main    #3360   +/-   ##
=======================================
  Coverage   66.81%   66.81%
=======================================
  Files         166      166
  Lines        7890     7890
=======================================
  Hits         5272     5272
  Misses       2585     2585
  Partials       33       33

Flag
Coverage Δ

unittests
66.81% <0.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

cmd/osm-controller/osm-controller.go
16.66% <0.00%> (ø)

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 0915de2...50421f3. Read the comment docs.

Hey @Atharva321, your commit has been merged, thanks! https://github.com/openservicemesh/osm/commit/50421f38e334297d98daddb4e8bf51fcd7cc0746


ENH: rename 'TIFF' to 'SINGLE_TIFF'

'TIFF' might not be the best name, so 'SINGLE_TIFF'. See #117

Thanks!

Doesn't this break things?

this went in yesterday so it has never been released and probably only breaks @CJ-Wright

Yes, this breaks all of my things. It is the equivalent of "HULK SMASH" to my code base. /s
Its fine though, a) I'll just fix things in a refactor on my side, b) I haven't started using this handler in filestore, I have it in my own repos as TIFF, so I can gracefully transition.

I would point out that this only affect the 'auto' registration.  You can still manually register the handler as 'TIFF'.

Thank you! I didn't think of that. None of my code which handles TIFF is running anywhere and all the dbs that currently have TIFF in them are legacy, so I am not super worried.

Speaking of auto-registration, is there a function which registers all the handlers in filestore?

It is in databroker https://github.com/NSLS-II/databroker/blob/master/databroker/handler_registration.py

Awesome, thank you!


I have multiple GPU, why test-device.lua only see 1

$ lspci
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290]
02:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960](rev a1)
$ luajit -l cltorch  ./src/test/test-device.lua
running require cltorch...
... require cltorch done
num devices:    1
device properties, device   1
deviceType  GPU
localMemSizeKB  48
globalMemSizeMB 4095
deviceVersion   OpenCL 1.2 CUDA
platformVendor  NVIDIA Corporation
deviceName  GeForce GTX 960
maxComputeUnits 8
globalMemCachelineSizeKB    0
openClCVersion  OpenCL C 1.2
maxClockFrequency   1367
maxMemAllocSizeMB   1023
maxWorkGroupSize    1024
Using NVIDIA Corporation , OpenCL platform: NVIDIA CUDA
Using OpenCL device: GeForce GTX 960
c1
7
-4
5
[torch.ClTensor of size 3]
7
4
5
[torch.ClTensor of size 3]
Thanks.

Hi Mingwu,
Normally it will probably be because the OpenCL drivers for that GPU have not been installed.  Can you provide the output of clinfo please?  (You might need to sudo apt-get install clinfo first)

$ sudo clinfo
[sudo] password for zhou:
Number of platforms:				 2
Platform Profile:				 FULL_PROFILE
Platform Version:				 OpenCL 1.2 CUDA 7.5.23
Platform Name:				 NVIDIA CUDA
Platform Vendor:				 NVIDIA Corporation
Platform Extensions:				 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_copy_opts
Platform Profile:				 FULL_PROFILE
Platform Version:				 OpenCL 2.0 AMD-APP (1598.5)
Platform Name:				 AMD Accelerated Parallel Processing
Platform Vendor:				 Advanced Micro Devices, Inc.
Platform Extensions:				 cl_khr_icd cl_amd_event_callback cl_amd_offline_devices
Platform Name:				 NVIDIA CUDA
Number of devices:				 1
Device Type:					 CL_DEVICE_TYPE_GPU
Vendor ID:					 10deh
Max compute units:				 8
Max work items dimensions:			 3
Max work items[0]:				 1024
Max work items[1]:				 1024
Max work items[2]:				 64
Max work group size:				 1024
Preferred vector width char:			 1
Preferred vector width short:			 1
Preferred vector width int:			 1
Preferred vector width long:			 1
Preferred vector width float:			 1
Preferred vector width double:		 1
Native vector width char:			 1
Native vector width short:			 1
Native vector width int:			 1
Native vector width long:			 1
Native vector width float:			 1
Native vector width double:			 1
Max clock frequency:				 1367Mhz
Address bits:					 64
Max memory allocation:<PHONE_NUMBER>
Image support:				 Yes
Max number of images read arguments:		 256
Max number of images write arguments:		 16
Max image 2D width:				 16384
Max image 2D height:				 16384
Max image 3D width:				 4096
Max image 3D height:				 4096
Max image 3D depth:				 4096
Max samplers within kernel:			 32
Max size of kernel argument:			 4352
Alignment (bits) of base address:		 4096
Minimum alignment (bytes) for any datatype:	 128
Single precision floating point capability
Denorms:					 Yes
Quiet NaNs:					 Yes
Round to nearest even:			 Yes
Round to zero:				 Yes
Round to +ve and infinity:			 Yes
IEEE754-2008 fused multiply-add:		 Yes
Cache type:					 Read/Write
Cache line size:				 128
Cache size:					 131072
Global memory size:<PHONE_NUMBER>
Constant buffer size:				 65536
Max number of constant args:			 9
Local memory type:				 Scratchpad
Local memory size:				 49152
Kernel Preferred work group size multiple:	 32
Error correction support:			 0
Unified memory for Host and Device:		 0
Profiling timer resolution:			 1000
Device endianess:				 Little
Available:					 Yes
Compiler available:				 Yes
Execution capabilities:
Execute OpenCL kernels:			 Yes
Execute native function:			 No
Queue on Host properties:
Out-of-Order:				 Yes
Profiling :					 Yes
Platform ID:					 0x23e2650
Name:						 GeForce GTX 960
Vendor:					 NVIDIA Corporation
Device OpenCL C version:			 OpenCL C 1.2
Driver version:				 352.79
Profile:					 FULL_PROFILE
Version:					 OpenCL 1.2 CUDA
Extensions:					 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_copy_opts  cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64
Platform Name:				 AMD Accelerated Parallel Processing
Number of devices:				 2
Device Type:					 CL_DEVICE_TYPE_GPU
Vendor ID:					 1002h
Board name:
Device Topology:				 PCI[ B#1, D#0, F#0 ]
Max compute units:				 40
Max work items dimensions:			 3
Max work items[0]:				 256
Max work items[1]:				 256
Max work items[2]:				 256
Max work group size:				 256
Preferred vector width char:			 4
Preferred vector width short:			 2
Preferred vector width int:			 1
Preferred vector width long:			 1
Preferred vector width float:			 1
Preferred vector width double:		 1
Native vector width char:			 4
Native vector width short:			 2
Native vector width int:			 1
Native vector width long:			 1
Native vector width float:			 1
Native vector width double:			 1
Max clock frequency:				 947Mhz
Address bits:					 64
Max memory allocation:<PHONE_NUMBER>
Image support:				 Yes
Max number of images read arguments:		 128
Max number of images write arguments:		 64
Max image 2D width:				 16384
Max image 2D height:				 16384
Max image 3D width:				 2048
Max image 3D height:				 2048
Max image 3D depth:				 2048
Max samplers within kernel:			 16
Max size of kernel argument:			 1024
Alignment (bits) of base address:		 2048
Minimum alignment (bytes) for any datatype:	 128
Single precision floating point capability
Denorms:					 No
Quiet NaNs:					 Yes
Round to nearest even:			 Yes
Round to zero:				 Yes
Round to +ve and infinity:			 Yes
IEEE754-2008 fused multiply-add:		 Yes
Cache type:					 Read/Write
Cache line size:				 64
Cache size:					 16384
Global memory size:<PHONE_NUMBER>
Constant buffer size:				 65536
Max number of constant args:			 8
Local memory type:				 Scratchpad
Local memory size:				 32768
Max pipe arguments:				 16
Max pipe active reservations:			 16
Max pipe packet size:<PHONE_NUMBER>
Max global variable size:<PHONE_NUMBER>
Max global variable preferred total size:<PHONE_NUMBER>
Max read/write image args:			 64
Max on device events:				 1024
Queue on device max size:			 262144
Max on device queues:				 1
Queue on device preferred size:		 16384
SVM capabilities:
Coarse grain buffer:			 Yes
Fine grain buffer:				 No
Fine grain system:				 No
Atomics:					 No
Preferred platform atomic alignment:		 0
Preferred global atomic alignment:		 0
Preferred local atomic alignment:		 0
Kernel Preferred work group size multiple:	 64
Error correction support:			 0
Unified memory for Host and Device:		 0
Profiling timer resolution:			 1
Device endianess:				 Little
Available:					 Yes
Compiler available:				 Yes
Execution capabilities:
Execute OpenCL kernels:			 Yes
Execute native function:			 No
Queue on Host properties:
Out-of-Order:				 No
Profiling :					 Yes
Queue on Device properties:
Out-of-Order:				 Yes
Profiling :					 Yes
Platform ID:					 0x7ff0428b5670
Name:						 Hawaii
Vendor:					 Advanced Micro Devices, Inc.
Device OpenCL C version:			 OpenCL C 2.0
Driver version:				 1598.5 (VM)
Profile:					 FULL_PROFILE
Version:					 OpenCL 2.0 AMD-APP (1598.5)
Extensions:					 cl_khr_fp64 cl_amd_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_gl_sharing cl_ext_atomic_counters_32 cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt cl_khr_image2d_from_buffer cl_khr_spir cl_khr_subgroups cl_khr_gl_event cl_khr_depth_images
Device Type:					 CL_DEVICE_TYPE_CPU
Vendor ID:					 1002h
Board name:
Max compute units:				 8
Max work items dimensions:			 3
Max work items[0]:				 1024
Max work items[1]:				 1024
Max work items[2]:				 1024
Max work group size:				 1024
Preferred vector width char:			 16
Preferred vector width short:			 8
Preferred vector width int:			 4
Preferred vector width long:			 2
Preferred vector width float:			 8
Preferred vector width double:		 4
Native vector width char:			 16
Native vector width short:			 8
Native vector width int:			 4
Native vector width long:			 2
Native vector width float:			 8
Native vector width double:			 4
Max clock frequency:				 1400Mhz
Address bits:					 64
Max memory allocation:<PHONE_NUMBER>
Image support:				 Yes
Max number of images read arguments:		 128
Max number of images write arguments:		 64
Max image 2D width:				 8192
Max image 2D height:				 8192
Max image 3D width:				 2048
Max image 3D height:				 2048
Max image 3D depth:				 2048
Max samplers within kernel:			 16
Max size of kernel argument:			 4096
Alignment (bits) of base address:		 1024
Minimum alignment (bytes) for any datatype:	 128
Single precision floating point capability
Denorms:					 Yes
Quiet NaNs:					 Yes
Round to nearest even:			 Yes
Round to zero:				 Yes
Round to +ve and infinity:			 Yes
IEEE754-2008 fused multiply-add:		 Yes
Cache type:					 Read/Write
Cache line size:				 64
Cache size:					 16384
Global memory size:<PHONE_NUMBER>4
Constant buffer size:				 65536
Max number of constant args:			 8
Local memory type:				 Global
Local memory size:				 32768
Max pipe arguments:				 16
Max pipe active reservations:			 16
Max pipe packet size:<PHONE_NUMBER>
Max global variable size:<PHONE_NUMBER>
Max global variable preferred total size:<PHONE_NUMBER>
Max read/write image args:			 64
Max on device events:				 0
Queue on device max size:			 0
Max on device queues:				 0
Queue on device preferred size:		 0
SVM capabilities:
Coarse grain buffer:			 Yes
Fine grain buffer:				 Yes
Fine grain system:				 Yes
Atomics:					 Yes
Preferred platform atomic alignment:		 0
Preferred global atomic alignment:		 0
Preferred local atomic alignment:		 0
Kernel Preferred work group size multiple:	 1
Error correction support:			 0
Unified memory for Host and Device:		 1
Profiling timer resolution:			 1
Device endianess:				 Little
Available:					 Yes
Compiler available:				 Yes
Execution capabilities:
Execute OpenCL kernels:			 Yes
Execute native function:			 Yes
Queue on Host properties:
Out-of-Order:				 No
Profiling :					 Yes
Queue on Device properties:
Out-of-Order:				 No
Profiling :					 No
Platform ID:					 0x7ff0428b5670
Name:						 AMD FX(tm)-8320 Eight-Core Processor
Vendor:					 AuthenticAMD
Device OpenCL C version:			 OpenCL C 1.2
Driver version:				 1598.5 (sse2,avx,fma4)
Profile:					 FULL_PROFILE
Version:					 OpenCL 1.2 AMD-APP (1598.5)
Extensions:					 cl_khr_fp64 cl_amd_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_gl_sharing cl_ext_device_fission cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt cl_khr_spir cl_khr_gl_event
========================
it shows:
Name:						 Hawaii

BTW, I'm 'ssh -X' into that machine, and running with 'sudo'.
Does it matter?

Indeed I need to run with 'sudo su', and then it can see 2 GPUs.
luajit -l cltorch ./src/test/test-device.lua
running require cltorch...
... require cltorch done
num devices:	2
device properties, device	1
deviceType	GPU
localMemSizeKB	48
globalMemSizeMB	4095
deviceVersion	OpenCL 1.2 CUDA
platformVendor	NVIDIA Corporation
deviceName	GeForce GTX 960
maxComputeUnits	8
globalMemCachelineSizeKB	0
openClCVersion	OpenCL C 1.2
maxClockFrequency	1367
maxMemAllocSizeMB	1023
maxWorkGroupSize	1024
device properties, device	2
deviceType	GPU
localMemSizeKB	32
globalMemSizeMB	4052
deviceVersion	OpenCL 2.0 AMD-APP (1598.5)
platformVendor	Advanced Micro Devices, Inc.
deviceName	Hawaii
maxComputeUnits	40
globalMemCachelineSizeKB	0
openClCVersion	OpenCL C 2.0
maxClockFrequency	947
maxMemAllocSizeMB	2867
maxWorkGroupSize	256
Using NVIDIA Corporation , OpenCL platform: NVIDIA CUDA
Using OpenCL device: GeForce GTX 960
c1
7
-4
5
[torch.ClTensor of size 3]
7
4
5
[torch.ClTensor of size 3]
Using Advanced Micro Devices, Inc. , OpenCL platform: AMD Accelerated Parallel Processing
Using OpenCL device: Hawaii
c1
7
-4
5
[torch.ClTensor of size 3]
7
4
5
[torch.ClTensor of size 3]
============================================
Now my question is why I can only run OpenCL on R290 as 'su'? but not as ordinary user?
Is there any way I can fix this?
Thanks.

BTW, I'm 'ssh -X' into that machine, and running with 'sudo'.
Does it matter?

Yes, probably.  GPU drivers in general tend to prefer one uses them from a desktop enviornment, which is using that GPU.  As far as I know, AMD GPUs are no less picky in this respect.  Unfortunately I dont have am AMD GPU to test with, and prevoius threads on the amd list, eg https://github.com/amd/OpenCL-caffe/issues/13 never seemed to get resolved.  I'm not really sure how to solve this to be honest.
For NVIDIA, on linux, it tends to be sufficient to just run with sudo.
For NVIDIA, on Windows, I find I have to use vnc to connect to the desktop (eg rdesktop doesnt work correctly, inserts some other driver into the video stack somehow).
Maybe you can try vnc perhaps???  The best thing would be to check with some support guy, but, there's a lot of AMD guys in that thread I just linked to, so ... ????

Guess I have to use 'sudo su'.
The next question is how do I tell cltorch which GPU device to run?

Guess I have to use 'sudo su'.

Cool.  If that works, thats excellent info :-)

The next question is how do I tell cltorch which GPU device to run?

In theory it hsould be like:
cltorch.setDevice(2)

... for the second gpu, or:
cltorch.setDevice(1)

... for the first one

Just a small comment as I also was facing this problem.
First running scripts with sudo in linux is kind of unsafe.
I didn't test with Nvidia or AMD graphic cards but I had the same problem with Intel HD integrated graphics. The trick was to add the user to the group "video"
sudo usermod -a -G video $LOGNAME
and to close the ssh session and reconnect again. then clinfo displays your gpu with no need for sudo.

Although this issue is a little old, but I would like to add some notes.  Hope this can help others.
In my case /dev/kfd is root:render instead of root:video:
crw-rw---- 1 root render 237, 0 Feb 26 15:15 /dev/kfd

So you would need to use sudo usermod -a -G render $LOGNAME to do this.


Clarification on StaticAnalysis API for Security Collector

I'm parsing some veracode xml scans, have all the data ready to POST to the API however looking for clarification on the descriptions of the data to POST as I've created items and they aren't showing in the dashboard.  Can I get descriptions on the following items?
{
  "hygieiaId": "string",
  "niceName": "string",
  "projectId": "string",
  "projectName": "string",
  "projectUrl": "string",
  "projectVersion": "string",
  "serverUrl": "string",
}

I've switched to just inserting the data directory into the database.  I'd be more than happy to help test the API whenever the change is added, however.

@tabladrum .I am using checkMarx scan for the security scan. Any way i can integrated that with UI?

We are going to work on allowing other tools to push SCA data. Please stay tuned.

Any update on checkmarx integration with Hygieia?


Support ISO For Original Files

It would make things a lot simpler if we could just shove the entire iso into orig/GAMEID and have nod handle extracting any necessary files on build, instead of requiring dolphin (or GCRebuilder) to extract them in the README.
Ideally it wouldn't even have to "extract" them, it can just stream the data from the iso as it's building.

Added with decomp-toolkit v1.1.2 and https://github.com/encounter/dtk-template/commit/ff6be416c6ba7148e07bb8228394da3b4a5373b3


help needed for Selectable hour grid in week hours view.

reply as soon as possible

that's now how this works, you should post this on stackoverflow with some code you have tried, and be glad if people help you

its done.


Testing Github CI to see if the number of commits is causing issues

No, this is also failing, but also giving a nonsensical error in shellspec. Gonna close this out and try to figure out what's going wrong in the morning.


Failure to start with Boot.js

After the last update, the Boot.js is failing with the following error:
RUNTIME ERROR
/Orchestrator/Boot.js@home

Failed to resolve module specifier "/Orchestrator/MessageManager/enum". Invalid relative url or base scheme isn't hierarchical.
stack:
TypeError: Failed to resolve module specifier "/Orchestrator/MessageManager/enum". Invalid relative url or base scheme isn't hierarchical.

I tried with a completely fresh installation after manually deleting all the files in /Orchestrator, /lib, and /resources, however; I had the same error as above.
Thank you for all your hard work!

This is due to the last update, you need to save, then restart with killing all script.

Thank you, that worked. I will add that to things to try in the future.


[Server] Kubernetes: Cannot delete the last cluster

Current Behavior

Meshery server has a logic which checks if there are any k8s contexts available and if not then it assumes that it must be users first request and loads the kubeconfig
Expected Behavior

The other possible assumption is that user has voluntarily deleted the last context and there are none left. Currently that case is not considered and Meshery server loads all the contexts again.
Some thought needs to be given as to when to load all contexts and when not to, in order to allow for deletion of last context
Screenshots/Logs

Environment

Host OS: Mac Linux Windows
Platform: Docker or Kubernetes
Meshery Server Version: stable-v
Meshery Client Version: stable-v

Contributor Guides and Resources

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

@Revolyssup, I researched a little bit on this issue. My initial thought is that there could be two ways to tackle this.

Since our Kubernetes middleware automatically loads all the contexts again when there are none left, we need to store somewhere that are contexts were loaded already once (probably in the database).
Or, we can just load all the contexts when the server starts once, and remove that logic from middleware altogether. (Probably in this file: https://github.com/meshery/meshery/blob/0b8f2b575cb594ab74661d53f3f1aefce84fb5ac/cmd/main.go#L190)

Thoughts?

@Revolyssup, I researched a little bit on this issue. My initial thought is that there could be two ways to tackle this.

Since our Kubernetes middleware automatically loads all the contexts again when there are none left, we need to store somewhere that are contexts were loaded already once (probably in the database).
Or, we can just load all the contexts when the server starts once, and remove that logic from middleware altogether. (Probably in this file: https://github.com/meshery/meshery/blob/0b8f2b575cb594ab74661d53f3f1aefce84fb5ac/cmd/main.go#L190)

Thoughts?

How about we have a Discover Clusters button which triggers discovery instead of doing it automatically?

etes middleware automatic

Loading contexts is a provider specific operation and cannot be performed until a user has logged in with a provider. Therefore, we can't do it on startup.

@Revolyssup, I researched a little bit on this issue. My initial thought is that there could be two ways to tackle this.

Since our Kubernetes middleware automatically loads all the contexts again when there are none left, we need to store somewhere that are contexts were loaded already once (probably in the database).
Or, we can just load all the contexts when the server starts once, and remove that logic from middleware altogether. (Probably in this file: https://github.com/meshery/meshery/blob/0b8f2b575cb594ab74661d53f3f1aefce84fb5ac/cmd/main.go#L190
)

Thoughts?

How about we have a Discover Clusters button which triggers discovery instead of doing it automatically?

Hmmm. There are pros and con to it.

etes middleware automatic

@nishantwrp Loading contexts is a provider specific operation and cannot be performed until a user has logged in with a provider. Therefore, we can't do it on startup.

Oh okay, got it.

@Revolyssup, I researched a little bit on this issue. My initial thought is that there could be two ways to tackle this.

Since our Kubernetes middleware automatically loads all the contexts again when there are none left, we need to store somewhere that are contexts were loaded already once (probably in the database).
Or, we can just load all the contexts when the server starts once, and remove that logic from middleware altogether. (Probably in this file: https://github.com/meshery/meshery/blob/0b8f2b575cb594ab74661d53f3f1aefce84fb5ac/cmd/main.go#L190
)

Thoughts?

How about we have a Discover Clusters button which triggers discovery instead of doing it automatically?

So, even the first time the user will have to click on discover clusters?


Arrows to navigate to next and previous months are not announcing properly

Copied from internal bug b/236668243:
When the arrow button for next month is tapped, the button will be announcing the current month. We are expecting it to be announced as a button as well otherwise users are unable to know it is tappable. (This issue applies to previous month button as well.)
Current behavior:
The button is announcing "July 2022".
Expected behavior:
"Next month August 2022 button."
Or a better behavior would be "Current month is July 2022, next month button".

Minimal repro code
import 'dart:async';
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      home: MyHomePage(),
    );
  }
}

class MyHomePage extends StatefulWidget {
  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  DateTime currentDate = DateTime.now();

  Future<void> _selectDate(BuildContext context) async {
    final pickedDate = await showDatePicker(
      context: context,
      initialDate: currentDate,
      firstDate: DateTime(2015),
      lastDate: DateTime(2050),
    );
    if (pickedDate != null && pickedDate != currentDate) {
      setState(() {
        currentDate = pickedDate;
      });
    }
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text("DatePicker"),
      ),
      body: Center(
        child: Column(
          mainAxisSize: MainAxisSize.min,
          children: [
            Text(currentDate.toString()),
            ElevatedButton(
              onPressed: () => _selectDate(context),
              child: const Text('Select date'),
            ),
          ],
        ),
      ),
    );
  }
}

Seems close to https://github.com/flutter/flutter/issues/96643


Beta 4 crashes while startup - Teensy 4.1

@terjeio
Hello Terje,
I tried starting your Beta 4, but when the program shows up, it closes a few seconds later without a warning.
This is with the teensy 4.1, but I can't give you more input...

It is a Win10 issue, with luck I may be able to upload a fix it later in the evening. Use Beta 3 until fixed.

Fixed in Beta 5 - now up.


Vite 2.9.7+ leads to Javascript heap out of memory

Describe the bug
When building my site (Vue, TS, Tailwind, moderately large app with mostly bespoke components), with any version >= 2.9.7, I get GC errors like this near the end of the build process (full debug log is pasted under "Logs" below):
vite v2.9.9 building for production...
transforming (1877) node_modules\monaco-editor\esm\vs\base\common\navigator.jsUse of eval is strongly discouraged, as it poses security risks and may cause issues with minification
Use of eval is strongly discouraged, as it poses security risks and may cause issues with minification
✓ 1877 modules transformed.
<--- Last few GCs --->

[28844:000002578023BC60]   176387 ms: Mark-sweep (reduce) 2029.9 (2080.1) -> 2029.8 (2080.6) MB, 2407.3 / 2.4 ms  (+ 158.9 ms in 7 steps since start of marking, biggest step 59.3 ms, walltime since start of marking 2874 ms) (average mu = 0.517, current mu[28844:000002578023BC60]   179410 ms: Mark-sweep (reduce) 2033.6 (2083.3) -> 2032.9 (2083.8) MB, 2607.4 / 0.1 ms  (average mu = 0.385, current mu = 0.138) allocation failure GC in old space requested

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
 1: 00007FF7C7607B7F v8::internal::CodeObjectRegistry::~CodeObjectRegistry+114079
 2: 00007FF7C7594546 DSA_meth_get_flags+65542
 3: 00007FF7C75953FD node::OnFatalError+301
 4: 00007FF7C7ECB29E v8::Isolate::ReportExternalAllocationLimitReached+94
 5: 00007FF7C7EB587D v8::SharedArrayBuffer::Externalize+781
 6: 00007FF7C7D58C4C v8::internal::Heap::EphemeronKeyWriteBarrierFromCode+1468
 7: 00007FF7C7D55D64 v8::internal::Heap::CollectGarbage+4244
 8: 00007FF7C7D536E0 v8::internal::Heap::AllocateExternalBackingStore+2000
 9: 00007FF7C7D78266 v8::internal::Factory::NewFillerObject+214
10: 00007FF7C7AAA5EA v8::internal::DateCache::Weekday+1466
11: 00007FF7C7F58F91 v8::internal::SetupIsolateDelegate::SetupHeap+494417
12:<PHONE_NUMBER>A767F2

vite 2.9.6 (and all previous versions I've used over time) work fine. I'm back to 2.9.6 now, thought maybe 2.9.9 would resolve the issue, but no such luck.
Unfortunately, it's a corporate site, so there's no mechanism I can think of for a reproducible demo, but I'm happy to share screens over Teams/zoom/etc. to demo the issue.
Reproduction
not possible
System Info

Windows 10
npm 7.19.1
node 16.4.0
8GB RAM

Public dependencies:
"dependencies": {
	"@starptech/prettyhtml": "^0.10.0",
	"axios": "^0.27.2",
	"clone-deep": "^4.0.1",
	"core-js": "^3.22.5",
	"he": "^1.2.0",
	"js-htmlencode": "^0.3.0",
	"markdown-it": "^13.0.1",
	"markdown-it-attrs": "^4.1.4",
	"markdown-it-bracketed-spans": "^1.0.1",
	"markdown-it-container": "^3.0.0",
	"markdown-it-deflist": "^2.1.0",
	"markdown-it-link-attributes": "^4.0.0",
	"markdown-it-revealjs": "^1.0.0",
	"markdown-it-sub": "^1.0.0",
	"markdown-it-sup": "^1.0.0",
	"markdown-it-task-checkbox": "^1.0.6",
	"monaco-editor": "^0.33.0",
	"query-string": "^7.1.1",
	"reveal.js": "^4.3.1",
	"vue": "^3.2.33",
	"vue-object-merge": "^1.0.0",
	"vue-router": "^4.0.15"
},
"devDependencies": {
	"@rollup/plugin-eslint": "^8.0.2",
	"@rushstack/eslint-patch": "^1.1.3",
	"@types/auth0-js": "^9.14.6",
	"@types/markdown-it": "^12.2.3",
	"@types/markdown-it-container": "^2.0.5",
	"@types/markdown-it-link-attributes": "^3.0.1",
	"@typescript-eslint/eslint-plugin": "^5.23.0",
	"@typescript-eslint/parser": "^5.23.0",
	"@vitejs/plugin-vue": "^2.3.3",
	"@vue/compiler-sfc": "^3.2.33",
	"@vue/eslint-config-typescript": "^10.0.0",
	"autoprefixer": "^10.4.7",
	"eslint": "^8.15.0",
	"eslint-config-prettier": "^8.5.0",
	"eslint-plugin-vue": "^8.7.1",
	"eslint-plugin-vuejs-accessibility": "^1.1.1",
	"gulp-changed": "^4.0.3",
	"gulp-flatten": "^0.4.0",
	"gulp-rename": "^2.0.0",
	"node-sass": "^7.0.1",
	"postcss": "^8.4.13",
	"prettier": "^2.6.2",
	"rollup-plugin-analyzer": "^4.0.0",
	"stylelint": "^14.8.2",
	"stylelint-config-standard": "^25.0.0",
	"tailwindcss": "^3.0.24",
	"typescript": "^4.6.4",
	"vite": "^2.9.6",
	"vite-svg-loader": "^3.3.0",
	"vue-eslint-parser": "^8.3.0"
},

Our index.js bundle comes out to 6.9MB, and the map is 10MB. We have a second bundle to split off the Monaco editor that is 2.7MB and 9.4MB for the map. (This is an internal corporate site, so bundle size is not a concern.) So, it's a non-trivial web site, but I'm sure there are far larger ones out there.
POSSIBLE RELATED ISSUE (but a different version of Vite that worked fine for me): #2433
Used Package Manager
npm
Logs
PS C:\Temp\VS\******\******-ui> vite build --debug
  vite:config bundled config file loaded in 841.04ms +0ms
  vite:config using resolved config: {
  vite:config   plugins: [
  vite:config     'vite:build-metadata',
  vite:config     'alias',
  vite:config     'svg-loader',
  vite:config     'vite:modulepreload-polyfill',
  vite:config     'vite:resolve',
  vite:config     'vite:html-inline-proxy',
  vite:config     'vite:css',
  vite:config     'vite:esbuild',
  vite:config     'vite:json',
  vite:config     'vite:wasm',
  vite:config     'vite:worker',
  vite:config     'vite:asset',
  vite:config     'vite:vue',
  vite:config     'eslint',
  vite:config     'vite:define',
  vite:config     'vite:css-post',
  vite:config     'vite:build-html',
  vite:config     'vite:worker-import-meta-url',
  vite:config     'vite:watch-package-data',
  vite:config     'commonjs',
  vite:config     'vite:data-uri',
  vite:config     'rollup-plugin-dynamic-import-variables',
  vite:config     'vite:asset-import-meta-url',
  vite:config     'vite:build-import-analysis',
  vite:config     'vite:esbuild-transpile',
  vite:config     'vite:terser',
  vite:config     'vite:reporter',
  vite:config     'vite:load-fallback'
  vite:config   ],
  vite:config   resolve: {
  vite:config     dedupe: undefined,
  vite:config     alias: [ [Object], [Object], [Object], [Object] ]
  vite:config   },
  vite:config   build: {
  vite:config     target: [ 'es2019', 'edge88', 'firefox78', 'chrome87', 'safari13.1' ],
  vite:config     polyfillModulePreload: true,
  vite:config     outDir: 'dist',
  vite:config     assetsDir: 'assets',
  vite:config     assetsInlineLimit: 4096,
  vite:config     cssCodeSplit: true,
  vite:config     cssTarget: [ 'es2019', 'edge88', 'firefox78', 'chrome87', 'safari13.1' ],
  vite:config     sourcemap: true,
  vite:config     rollupOptions: {},
  vite:config     minify: 'esbuild',
  vite:config     terserOptions: {},
  vite:config     write: true,
  vite:config     emptyOutDir: null,
  vite:config     manifest: false,
  vite:config     lib: false,
  vite:config     ssr: false,
  vite:config     ssrManifest: false,
  vite:config     reportCompressedSize: true,
  vite:config     chunkSizeWarningLimit: 500,
  vite:config     watch: null,
  vite:config     commonjsOptions: { include: [Array], extensions: [Array] },
  vite:config     dynamicImportVarsOptions: { warnOnError: true, exclude: [Array] }
  vite:config   },
  vite:config   server: {
  vite:config     preTransformRequests: true,
  vite:config     port: 3010,
  vite:config     https: false,
  vite:config     proxy: { '^/api': [Object] },
  vite:config     fs: { strict: true, allow: [Array], deny: [Array] }
  vite:config   },
  vite:config   define: { __VUE_OPTIONS_API__: true, __VUE_PROD_DEVTOOLS__: false },
  vite:config   ssr: { external: [ 'vue', '@vue/server-renderer' ] },
  vite:config   configFile: 'C:/Temp/VS/******/******-ui/vite.config.ts',
  vite:config   configFileDependencies: [ 'C:/Temp/VS/******/******-ui/vite.config.ts' ],
  vite:config   inlineConfig: {
  vite:config     root: undefined,
  vite:config     base: undefined,
  vite:config     mode: undefined,
  vite:config     configFile: undefined,
  vite:config     logLevel: undefined,
  vite:config     clearScreen: undefined,
  vite:config     build: {}
  vite:config   },
  vite:config   root: 'C:/Temp/VS/******/******-ui',
  vite:config   base: '/',
  vite:config   publicDir: 'C:\\Temp\\VS\\******\\******-ui\\public',
  vite:config   cacheDir: 'C:\\Temp\\VS\\******\\******-ui\\node_modules\\.vite',
  vite:config   command: 'build',
  vite:config   mode: 'production',
  vite:config   isWorker: false,
  vite:config   isProduction: true,
  vite:config   preview: {
  vite:config     port: undefined,
  vite:config     strictPort: undefined,
  vite:config     host: undefined,
  vite:config     https: false,
  vite:config     open: undefined,
  vite:config     proxy: { '^/api': [Object] },
  vite:config     cors: undefined,
  vite:config     headers: undefined
  vite:config   },
  vite:config   env: {
  vite:config     VITE_AUTH0_CLIENT_KEY: '***************',
  vite:config     VITE_AUTH0_DOMAIN: ''***************',
  vite:config     VITE_AUTH0_AUDIENCE: 'http://******',
  vite:config     BASE_URL: '/',
  vite:config     MODE: 'production',
  vite:config     DEV: false,
  vite:config     PROD: true
  vite:config   },
  vite:config   assetsInclude: [Function: assetsInclude],
  vite:config   logger: {
  vite:config     hasWarned: false,
  vite:config     info: [Function: info],
  vite:config     warn: [Function: warn],
  vite:config     warnOnce: [Function: warnOnce],
  vite:config     error: [Function: error],
  vite:config     clearScreen: [Function: clearScreen],
  vite:config     hasErrorLogged: [Function: hasErrorLogged]
  vite:config   },
  vite:config   packageCache: Map(0) { set: [Function (anonymous)] },
  vite:config   createResolver: [Function: createResolver],
  vite:config   optimizeDeps: {
  vite:config     esbuildOptions: { keepNames: undefined, preserveSymlinks: undefined }
  vite:config   },
  vite:config   worker: {
  vite:config     format: 'iife',
  vite:config     plugins: [
  vite:config       [Object], [Object], [Object],
  vite:config       [Object], [Object], [Object],
  vite:config       [Object], [Object], [Object],
  vite:config       [Object], [Object], [Object],
  vite:config       [Object], [Object], [Object],
  vite:config       [Object], [Object], [Object],
  vite:config       [Object], [Object], [Object],
  vite:config       [Object], [Object], [Object],
  vite:config       [Object]
  vite:config     ],
  vite:config     rollupOptions: {}
  vite:config   }
  vite:config } +56ms
vite v2.9.9 building for production...
transforming (56) src\components\ProgressBar.vue  vite:resolve 1.53ms ../../****-design/styles/default.css -> C:/Temp/VS/******/******-ui/****-design/styles/default.css +0ms
  vite:resolve 4.72ms ./fonts/source-sans-pro/source-sans-pro.css -> C:/Temp/VS/******/******-ui/node_modules/reveal.js/dist/theme/fonts/source-sans-pro/source-sans-pro.css +203ms
transforming (97) src\import\import-entity-page.vue  vite:resolve 10.58ms ./source-sans-pro-regular.eot -> C:/Temp/VS/******/******-ui/node_modules/reveal.js/dist/theme/fonts/source-sans-pro/source-sans-pro-regular.eot +0ms
  vite:resolve 10.99ms ./source-sans-pro-regular.eot?#iefix -> C:/Temp/VS/******/******-ui/node_modules/reveal.js/dist/theme/fonts/source-sans-pro/source-sans-pro-regular.eot?#iefix +0ms
  vite:resolve 11.61ms ./source-sans-pro-italic.eot -> C:/Temp/VS/******/******-ui/node_modules/reveal.js/dist/theme/fonts/source-sans-pro/source-sans-pro-italic.eot +0ms
  vite:resolve 12.27ms ./source-sans-pro-italic.eot?#iefix -> C:/Temp/VS/******/******-ui/node_modules/reveal.js/dist/theme/fonts/source-sans-pro/source-sans-pro-italic.eot?#iefix +0ms
  vite:resolve 12.79ms ./source-sans-pro-semibold.eot -> C:/Temp/VS/******/******-ui/node_modules/reveal.js/dist/theme/fonts/source-sans-pro/source-sans-pro-semibold.eot +0ms
  vite:resolve 13.11ms ./source-sans-pro-semibold.eot?#iefix -> C:/Temp/VS/******/******-ui/node_modules/reveal.js/dist/theme/fonts/source-sans-pro/source-sans-pro-semibold.eot?#iefix +0ms
  vite:resolve 13.53ms ./source-sans-pro-semibolditalic.eot -> C:/Temp/VS/******/******-ui/node_modules/reveal.js/dist/theme/fonts/source-sans-pro/source-sans-pro-semibolditalic.eot +0ms
  vite:resolve 13.37ms ./source-sans-pro-semibolditalic.eot?#iefix -> C:/Temp/VS/******/******-ui/node_modules/reveal.js/dist/theme/fonts/source-sans-pro/source-sans-pro-semibolditalic.eot?#iefix +0ms
  vite:resolve 1.99ms ./messages.css -> C:/Temp/VS/******/******-ui/****-design/styles/messages.css +1s
transforming (135) src\documentation\DocumentationPage.vue  vite:resolve 1.53ms ./source-sans-pro-regular.woff -> C:/Temp/VS/******/******-ui/node_modules/reveal.js/dist/theme/fonts/source-sans-pro/source-sans-pro-regular.woff +2s
  vite:resolve 2.31ms ./source-sans-pro-italic.woff -> C:/Temp/VS/******/******-ui/node_modules/reveal.js/dist/theme/fonts/source-sans-pro/source-sans-pro-italic.woff +5ms
  vite:resolve 4.80ms ./source-sans-pro-semibolditalic.woff -> C:/Temp/VS/******/******-ui/node_modules/reveal.js/dist/theme/fonts/source-sans-pro/source-sans-pro-semibolditalic.woff +9ms
  vite:resolve 2.23ms ./source-sans-pro-semibold.woff -> C:/Temp/VS/******/******-ui/node_modules/reveal.js/dist/theme/fonts/source-sans-pro/source-sans-pro-semibold.woff +6ms
transforming (149) src\pages\text-editor-page.vue  vite:resolve 1.50ms ./****-brand.css -> C:/Temp/VS/******/******-ui/****-design/styles/****-brand.css +3s
transforming (175) ****-vue\src\forms\FieldElementText.vue  vite:resolve 2.99ms ./source-sans-pro-regular.ttf -> C:/Temp/VS/******/******-ui/node_modules/reveal.js/dist/theme/fonts/source-sans-pro/source-sans-pro-regular.ttf +2s
  vite:resolve 2.48ms ./source-sans-pro-italic.ttf -> C:/Temp/VS/******/******-ui/node_modules/reveal.js/dist/theme/fonts/source-sans-pro/source-sans-pro-italic.ttf +6ms
  vite:resolve 2.39ms ./source-sans-pro-semibolditalic.ttf -> C:/Temp/VS/******/******-ui/node_modules/reveal.js/dist/theme/fonts/source-sans-pro/source-sans-pro-semibolditalic.ttf +4ms
  vite:resolve 4.44ms ./source-sans-pro-semibold.ttf -> C:/Temp/VS/******/******-ui/node_modules/reveal.js/dist/theme/fonts/source-sans-pro/source-sans-pro-semibold.ttf +9ms
transforming (194<EMAIL_ADDRESS>vite:resolve 2.20ms ../fonts/iosevka/iosevka.css -> C:/Temp/VS/******/******-ui/****-design/fonts/iosevka/iosevka.css +2s
transforming (234) node_modules\filter-obj\index.js  vite:resolve 2.39ms ../fonts/source-sans-3/source-sans-3.css -> C:/Temp/VS/******/******-ui/****-design/fonts/source-sans-3/source-sans-3.css +892ms
transforming (266) src\components\TextEditor.vue  vite:resolve 5.49ms ../fonts/stix-two-text/stix-two-text.css -> C:/Temp/VS/******/******-ui/****-design/fonts/stix-two-text/stix-two-text.css +406ms
transforming (286<EMAIL_ADDRESS>vite:resolve 1.27ms ./variables.css -> C:/Temp/VS/******/******-ui/****-design/styles/variables.css +280ms
transforming (326<EMAIL_ADDRESS>vite:resolve 48.88ms ./iosevka-fixed-ss14-extended.woff2 -> C:/Temp/VS/******/******-ui/****-design/fonts/iosevka/iosevka-fixed-ss14-extended.woff2 +3s
  vite:resolve 49.63ms ./iosevka-fixed-ss14-extendedoblique.woff2 -> C:/Temp/VS/******/******-ui/****-design/fonts/iosevka/iosevka-fixed-ss14-extendedoblique.woff2 +0ms
  vite:resolve 50.11ms ./iosevka-fixed-ss14-extendeditalic.woff2 -> C:/Temp/VS/******/******-ui/****-design/fonts/iosevka/iosevka-fixed-ss14-extendeditalic.woff2 +1ms
  vite:resolve 50.46ms ./iosevka-fixed-ss14-extendedmedium.woff2 -> C:/Temp/VS/******/******-ui/****-design/fonts/iosevka/iosevka-fixed-ss14-extendedmedium.woff2 +0ms
  vite:resolve 50.96ms ./iosevka-fixed-ss14-extendedmediumoblique.woff2 -> C:/Temp/VS/******/******-ui/****-design/fonts/iosevka/iosevka-fixed-ss14-extendedmediumoblique.woff2 +1ms
  vite:resolve 51.89ms ./iosevka-fixed-ss14-extendedmediumitalic.woff2 -> C:/Temp/VS/******/******-ui/****-design/fonts/iosevka/iosevka-fixed-ss14-extendedmediumitalic.woff2 +1ms
  vite:resolve 52.87ms ./iosevka-fixed-ss14-extendedsemibold.woff2 -> C:/Temp/VS/******/******-ui/****-design/fonts/iosevka/iosevka-fixed-ss14-extendedsemibold.woff2 +1ms
  vite:resolve 53.98ms ./iosevka-fixed-ss14-extendedsemiboldoblique.woff2 -> C:/Temp/VS/******/******-ui/****-design/fonts/iosevka/iosevka-fixed-ss14-extendedsemiboldoblique.woff2 +1ms
  vite:resolve 56.32ms ./iosevka-fixed-ss14-extendedsemibolditalic.woff2 -> C:/Temp/VS/******/******-ui/****-design/fonts/iosevka/iosevka-fixed-ss14-extendedsemibolditalic.woff2 +2ms
  vite:resolve 58.26ms ./iosevka-fixed-ss14-extendedbold.woff2 -> C:/Temp/VS/******/******-ui/****-design/fonts/iosevka/iosevka-fixed-ss14-extendedbold.woff2 +2ms
  vite:resolve 59.35ms ./iosevka-fixed-ss14-extendedboldoblique.woff2 -> C:/Temp/VS/******/******-ui/****-design/fonts/iosevka/iosevka-fixed-ss14-extendedboldoblique.woff2 +1ms
  vite:resolve 60.34ms ./iosevka-fixed-ss14-extendedbolditalic.woff2 -> C:/Temp/VS/******/******-ui/****-design/fonts/iosevka/iosevka-fixed-ss14-extendedbolditalic.woff2 +1ms
  vite:resolve 61.48ms ./SourceSans3VF-Roman.ttf.woff2 -> C:/Temp/VS/******/******-ui/****-design/fonts/source-sans-3/SourceSans3VF-Roman.ttf.woff2 +1ms
  vite:resolve 62.32ms ./SourceSans3VF-Italic.ttf.woff2 -> C:/Temp/VS/******/******-ui/****-design/fonts/source-sans-3/SourceSans3VF-Italic.ttf.woff2 +1ms
  vite:resolve 63.21ms ./STIXTwoText-Roman-var.woff2 -> C:/Temp/VS/******/******-ui/****-design/fonts/stix-two-text/STIXTwoText-Roman-var.woff2 +1ms
  vite:resolve 64.42ms ./STIXTwoText-Italic-var.woff2 -> C:/Temp/VS/******/******-ui/****-design/fonts/stix-two-text/STIXTwoText-Italic-var.woff2 +1ms
transforming (1516) node_modules\monaco-editor\esm\vs\platform\contextkey\common\contextkeys.js  vite:resolve 9.85ms ./codicon.ttf -> C:/Temp/VS/******/******-ui/node_modules/monaco-editor/esm/vs/base/browser/ui/codicons/codicon/codicon.ttf +20s
transforming (1869) node_modules\monaco-editor\esm\vs\editor\common\model\bracketPairsTextModelPart\bracketPairsTree\nodeReader.jsUse of eval is strongly discouraged, as it poses security risks and may cause issues with minification
Use of eval is strongly discouraged, as it poses security risks and may cause issues with minification
✓ 1877 modules transformed.
rendering chunks (76)...
<--- Last few GCs --->

[29628:00000187C8F02010]   116581 ms: Mark-sweep (reduce) 2038.5 (2083.0) -> 2038.2 (2083.8) MB, 1610.1 / 0.1 ms  (average mu = 0.178, current mu = 0.006) allocation failure scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
 1: 00007FF7DEC07B7F v8::internal::CodeObjectRegistry::~CodeObjectRegistry+114079
 2: 00007FF7DEB94546 DSA_meth_get_flags+65542
 3: 00007FF7DEB953FD node::OnFatalError+301
 4: 00007FF7DF4CB29E v8::Isolate::ReportExternalAllocationLimitReached+94
 5: 00007FF7DF4B587D v8::SharedArrayBuffer::Externalize+781
 6: 00007FF7DF358C4C v8::internal::Heap::EphemeronKeyWriteBarrierFromCode+1468
 7: 00007FF7DF355D64 v8::internal::Heap::CollectGarbage+4244
 8: 00007FF7DF3536E0 v8::internal::Heap::AllocateExternalBackingStore+2000
 9: 00007FF7DF378266 v8::internal::Factory::NewFillerObject+214
10: 00007FF7DF0AA735 v8::internal::DateCache::Weekday+1797
11: 00007FF7DF558F91 v8::internal::SetupIsolateDelegate::SetupHeap+494417
12: 00000187CB054F1F
PS C:\Temp\VS\******\******-ui>

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Shot in the dark: the appearance of the "eval is dangerous" warnings immediately prior to the error points to the shared scope being unintentionally polluted? See: "Avoiding eval".
My interest was initially piqued by the appearance of:
 5: 00007FF7DF4B587D v8::SharedArrayBuffer::Externalize+781
but eval looks to be more likely for your case?

@michaelwooley, thanks for looking at this!
The eval warning is from rollup, I believe it's being triggered by some mentions of eval in the VS Code source (the Monaco editor referenced just before the warning) that aren't actually eval() statements.
Either way, the warning happens very early, and several minutes of work happen (transforming modules, and especially rendering chunks, which takes forever on my machine) before the error strikes.
And that same warning also shows up in 2.9.6, which usually doesn't result in this memory error.
New data point: I just had the same error happen on 2.9.6 (a first!). I closed a few apps, and I ran npm run build from a command prompt instead of the VS integrated terminal (where I normally work) and 2.9.6 worked fine again.
So, maybe node is getting barely enough memory from my system for vite or rollup or whatever needs to do its thing (usually), and perhaps 2.9.7+ (which have some updated dependencies) are just sending it over the edge? Still, while this laptop only has 8GB of RAM, I wouldn't think that would be a concern for a site that bundles down to under 15MB.

It's possible this is a duplicate of https://github.com/vitejs/vite/issues/2433 (though that one isn't version-specific). Perhaps the workaround there would be helpful

Yeah I think this is a duplicate of #2433. And without a repro this would also go stale even though there's an issue somewhere. Closing this to converge the discussion to that issue


Get-PnPTeamsTeam

I'm trying to run the Get-PnPTeamsTeam and it looks successful but doesn't return anything.
# Using the Certificate connection type to PnPOnline the App Registration do have the required access (Group.Read.All). $PnPConnection = Connect-PnPOnline -Tenant '<TENANTID>' -ClientId '<CLIENTID>' -Thumbprint '<CERTIFICATE THUMBPRINT>' -Url '<SHAREPOINT URL>' -ReturnConnection
$Teams = Get-PnPTeamsTeam # Trying to fetch all teams, took about 4mins to run
$Team = Get-PnPTeamsTeam -Identity "<TEAM NAME>" # Trying to fetch one specific team
All tests above returns nothing. When I try to add a faulty team name I do get the error message: PnP.PowerShell.Commands.Model.Teams.GraphException.
I think the script runs and fetches everything but it never returns the findings.

I'm closing the issue as it turns out it the old module SharePointPnPPowerShellOnline was used over the PnP.Powershell module.


Change import from ocl to opencamlib

The 2022 releases use a new import name, because the package is now also published on PyPi and ocl was already taken. (see https://github.com/aewallin/opencamlib/releases/tag/2022.12.17)

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

There are too few lines.  There should be one empty line at the end of the file.

For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Non noarch packages should have python requirement without any version constraints.
Non noarch packages should have python requirement without any version constraints.

For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

Something is funky, on the osx-arm64 builds FindPython is picking up an old Python v2.7 interpreter, even when providing -D Python_EXECUTABLE which points to the right Python interpreter, this might be an issue with FindPython which I will have to debug another time.

@looooo this is ready to go now, should I rebase the changes into a single commit?

@looooo this is ready to go now, should I rebase the changes into a single commit?

no I guess it's fine this way

thank you for the work.


mcdex db.update failing

D:\mcdex>mcdex db.update
2017/07/25 16:13:21 Failed to rename mcdex.dat.tmp: rename C:\Users\rasmu\AppData\Roaming\.minecraft\mcdex\mcdex.dat.tmp C:\Users\rasmu\AppData\Roaming\.minecraft\mcdex\mcdex.dat: The process cannot access the file as it is in use by another process

(Process part translated by me from danish)
same setup where we left it last time :) JDK x64 Server running fine. I can manually change the file from mcdex.dat.tmp to mcdex.dat when i click the permission confirmation as i'm working on C drive en %appdata% (Windows 10 pro x64)
All this is tried with Minecraft client and server shut down.
What i'm trying do do is use it to install extra mods into a modpack, that is also installed with mcdex, and then i saw the list command and wanted to try it out.
some debug info:
Version: v0.7.0-0-g86e2d10
Env: {MinecraftDir:C:\Users\rasmu\AppData\Roaming\.minecraft McdexDir:C:\Users\rasmu\AppData\Roaming\.minecraft\mcdex JavaDir:C:\Program Files\Java\jdk1.8.0_131}

Fixed in 336bd3e; update to latest mcdex (v0.7.1) and it should be good to go.


ESP8266 as Slave

Is this possible? Hope can add this feature for this i2c setup...

I would like this too.

This would be a nice idea, ESP8266 or ESP32 as slave over I2C !

egzactly


bump urijs to 1.19.8 to resolve snyk vulnerability

What?

bump urijs to 1.19.8

Why?

to resolve snyk vulnerability

I think Martin has merged this one in now.


"use of package mssql without selector" "mssql redeclared in this block"

In the file: gorm/dialects/mssql/mssql.go
`func init() {
gorm.DefaultCallback.Create().After("gorm:begin_transaction").Register("mssql:set_identity_insert", setIdentityInsert)
gorm.RegisterDialect("mssql", &mssql{})
}
type mssql struct {
db *sql.DB
gorm.DefaultForeignKeyNamer
}`
When building, get:
"use of package mssql without selector"
"mssql redeclared in this block"
Complaining about this line specifically:
gorm.RegisterDialect("mssql", &mssql{})

We should fixed all issues for mssql, if you still have any problem, please create a new issue.
Thank you.