Nyappdiv 4th and more

Hey @mlissner, wanted you to review this to make sure it looks good.  mostly want to make sure you think my addition to AbstractSite is okay.  As I mentioned in the slack channel, there is some code in the new method that duplicates what's going on in _download(), though it's not many lines.  I think the real solution would be to extract the get/post handling logic into their own method on AbstractSite (similar to the one I created), then _download() could call those, and they would also be available to all child scrapers to use.  Right now, there are a lot of scrapers that duplicate (more or less) the logic in my new method, most of which could probably be replaced with calls to this new method (or whatever new methods for post/get tat we come up with for AbstractSite).  Let me know what you think.

Umm, I'm not sure how much work it would be.  I haven't audited all scrapers including requests.  My guess is that it's a good number.
Do you want me to try my hand at abstracting the post/get logic, adjust download accordingly, then see how many scrapers may benefit from adjusting (to call new methods)?
Sent from a phone

On Oct 5, 2016, at 11:49 AM, Mike Lissner<EMAIL_ADDRESS>wrote:
@mlissner requested changes on this pull request.
I didn't look closely at the NY scraper, but I think the AbstractSite changes are in the right direction. I agree though, we should fully abstract out the download method.
Is it a lot of work to update the other existing scrapers with this change when you submit?
In juriscraper/AbstractSite.py:

@@ -287,6 +288,32 @@ def _make_html_tree(self, text):
"""
return get_html_parsed_text(text)

def _get_html_tree_by_url(self, url, request_dict={}):
I think this is a good idea to provide this, but I think you're right that the code in this method and the code in _download should be generalized and pulled out.

This might also be a good time to pull the dict out of the default keyword argument, since it's a common cause of bugs. I don't think it's causing us issues, but it's not ideal, and we may as well fix it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Yeah sure, that sounds like a great plan. I think the more important work
is to pull out the download stuff so that scrapers can be abstracted in the
future. It's a bonus to clean up the old ones, but this doesn't have to
wait for that.
On Wed, Oct 5, 2016 at 1:28 PM Philip Ardery<EMAIL_ADDRESS>wrote:

Umm, I'm not sure how much work it would be. I haven't audited all
scrapers including requests. My guess is that it's a good number.
Do you want me to try my hand at abstracting the post/get logic, adjust
download accordingly, then see how many scrapers may benefit from adjusting
(to call new methods)?
Sent from a phone

On Oct 5, 2016, at 11:49 AM, Mike Lissner<EMAIL_ADDRESS>wrote:
@mlissner requested changes on this pull request.
I didn't look closely at the NY scraper, but I think the AbstractSite
changes are in the right direction. I agree though, we should fully
abstract out the download method.
Is it a lot of work to update the other existing scrapers with this
change when you submit?
In juriscraper/AbstractSite.py:

@@ -287,6 +288,32 @@ def _make_html_tree(self, text):
"""
return get_html_parsed_text(text)

def _get_html_tree_by_url(self, url, request_dict={}):
I think this is a good idea to provide this, but I think you're right
that the code in this method and the code in _download should be
generalized and pulled out.

This might also be a good time to pull the dict out of the default
keyword argument, since it's a common cause of bugs. I don't think it's
causing us issues, but it's not ideal, and we may as well fix it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/freelawproject/juriscraper/pull/162#issuecomment-251789663,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOdqlNpmQolvwR_TE7yWQM_CBQeaM2gks5qxAhQgaJpZM4KOSw2
.


shorter notes can drag sometimes

probably has to do with the music library im using. perhaps getting the kalimba note sound files myself will help with this?

This turns out to be caused by the highlighted bar, not by the sound playing. If you disable the yellow bar, the song runs as it should, even in development mode

Fixed by doing the above workaround, commit https://github.com/oakleyaidan21/kalimba-tabs/commit/dacc68fcf0b799e86050cb09f190f194ae59e947


FanzyZones Win+arrow not functioning with Win Keyboard Manager mapping

Environment
Windows build number: 10.0.19041.264
PowerToys version: 0.18.2
PowerToy module for which you are reporting the bug (if applicable): FanzyZones (Keyboard Manager?)

Steps to reproduce

In FancyZones enable "Override Windows Snap hotkeys (Win + arrow) to move windows between zones"
In Keyboard Manager use "Remap a key" to swap Alt (Left) and Win (Left), by mapping:

Win (Left) to Alt (Left)
Alt (Left) to Win (Left)

Hold Alt (Left) (mapped to Win) press Left (arrow key).

Expected behavior
Window moves between zones.
Actual behavior
Window uses normal Windows Snap behavior.
Additional test scenario
This re-binding of Win (Left) to another key seems to cascade to mapped shortcuts as well.
Steps to reproduce

Follow steps to reproduce described above
In Keyboard Manager use "Remap shortcuts" to give a VIM style movement binding:

Win (Left), Shift (Left), H to Win (Left), Left

Hold Alt (Left) (mapped to Win Left) and Shift (Left) then press H key

Expected behavior
Window moves between zones.
Actual behavior
Window uses normal Windows Snap behavior.
Work around
Now that I understand the issue, I'm working around this by leaving Win/Alt unmodified and instead creating shortcut mappings for any hotkeys I'd like to use with the key next to spacebar. This seems to work well enough and means I can do things such as map Alt-L which was not possible with Win-L.
If the issue reported isn't reasonably achievable, my request would be to put a note in Keyboard Manager that rebinding Win (Left) may cause unpredictable behavior.

Hi @codycraven
with the current implementation, that is not achievable, since FancyZones uses a lowlevel keyboard hook that will bypass whatever you set in the Keyboard Manager.
In order to achieve it, FancyZones would need to be aware of the Keyboard Manager configuration and process it directly.

@arjunbalgovind we should look at how we can get everything to play nicely here

The temporary workaround is to disable and then re-enable KBM, so it first the key gets remapped and then FZ processes it correctly. Agree we need to find the correct way to do this.

Closing as duplicate of https://github.com/microsoft/PowerToys/issues/3079


Dashboard access permission

Is your feature request related to a problem? Please describe.
I'm missing then ability to permit access in the dashboard level.
there is only ability to set owners, but owners have full permissions on the dashboard they own but in my use-case I need to give basic access to specific dashboards only
I want for security purposes  to block access for non permitted user to access dashboards
Describe the solution you'd like
Use FAB permission view mechanism to have new permission named dashboard access
and for every dashboard there would be a matching view_menu instance that can be used a permission_view and be assigned into Roles

additionally users will be validated with the necessary permissions when requesting dashboards(specific or list)  and will be rejected if they don't have them

nice

@mistercrunch @villebro @altef

I would very much like dashboard level permissions as well; Thanks for writing this up, @amitNielsen!
@justin-barton

@altef we are using your rls implementation thanks for that!

there is an old PR #5099 but now it is stable
I plan to re-implement just trying to make sure the feature summary that I've listed is the right way to go
@mistercrunch @altef

@amitNielsen This would be a very useful feature indeed ! Thanks for taking a look at it.
The feature summary you described is exactly what I would expect from this feature

great new fature!

I've open a sip #10408


Django links point to v3 of Django

The links in this article for Django send you to documentation for v3 of django which has a banner at the top of the page that reads...
This document is for an insecure version of Django that is no longer supported. Please upgrade to a newer release!

Recommend changing the references to Django 4.0

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

ID: fe78588d-6ed5-52b1-7b02-6e53affb000d
Version Independent ID: df4cdd51-678e-7a57-ef23-59c48b623fdd
Content: Monitor Python applications with Azure Monitor - Azure Monitor
Content Source: articles/azure-monitor/app/opencensus-python.md
Service: azure-monitor
Sub-service: application-insights
GitHub Login: @AaronMaxwell
Microsoft Alias: aaronmax

@scgbear - Thanks again for bringing this to our attention. We have updated the Doc and it will be live once its merged.  We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Feature/narrower table columns

Pivotal task
This PR changes Data explorer table columns width on Pathways section.
With the new width some years columns could be seen without scrolling to the right giving the user a hint that more years are hidden in this side of the table.

Maybe we could also change the width of the historical emission table. Just to keep them similar

Haven't forced column width on GHG because there's only one year (2014) with the default selections and would look weird.
To define a forced width in any other section just add the section and the desired width to DATA_EXPLORER_TABLE_COLUMNS_WIDTH on data-explorer-constants.js.


Update MockServer Tests to use mockserver/mockserver image with 5.14.0 version

Upgraded the mockserver-client-java test dependency to 5.14.0 and used mockserver/mockserver:mockserver-5.14.0 docker image for testing.

@eddumelendez Done code formatting and pushed the changes.

thanks for your contribution @sivaprasadreddy ! this is now in main branch.


The Log Analytics SKU "PerGB2018" in the example is invalid

I was testing Terraform creation of a Log Analytics Workspace, and when you use "PerGB2018" it's flagged as invalid.  A working value appears to be "Standalone" which I got from an Azure DevOps Project that I created a Log Analytics Workspace in last week.

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

ID: aa28dc85-7097-6005-1a5b-6cfe8a7e9528
Version Independent ID: 842a431e-cdd8-c695-70eb-78294acd80f3
Content: Create a Log Analytics workspace using Azure CLI
Content Source: articles/azure-monitor/learn/quick-create-workspace-cli.md
Service: log-analytics
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@ghoelzer-rht - Is your subscription using the new pricing model?

Hi Matt –
I’m a Microsoft Employee, so I’m using my Employee Subscription, and that SKU comes back as invalid when I try to create a log analytics workspace via the Azure CLI/Cloud Shell.
Best Regards,
Greg Hoelzer
App Dev Tech Specialist |Microsoft|Azure
mobile:<PHONE_NUMBER>tel:612-325-8200
email: Greg.Hoelzer<EMAIL_ADDRESS>Our Mission
Empower every person and every organization on the planet to achieve more
[cid:image006.jpg@01D4801E.3135CA50]https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fptdrv.linkedin.com%2Fgkgqdnc&data=02|01|Greg.Hoelzer%40microsoft.com|7a8633a91d6f4342143708d65550df99|72f988bf86f141af91ab2d7cd011db47|1|0|636790203212588517&sdata=CooIgMbLNlY1IGLnih20zJT5eB%2BKbEG8FybKNpU0lCc%3D&reserved=0
From: Matt Goedtel<EMAIL_ADDRESS>Sent: Wednesday, February 6, 2019 9:26 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Greg Hoelzer<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] The Log Analytics SKU "PerGB2018" in the example is invalid (#23239)
@ghoelzer-rhthttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fghoelzer-rht&data=02|01|greg.hoelzer%40microsoft.com|e009add0c7ae4639834108d68c475768|72f988bf86f141af91ab2d7cd011db47|1|0|636850635370582983&sdata=73Q0O7jY51aaQz0pQeCo%2B01w4SKkbDC2lDnGl3EPlgs%3D&reserved=0 - Is your subscription using the new pricing model?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F23239%23issuecomment-461063470&data=02|01|greg.hoelzer%40microsoft.com|e009add0c7ae4639834108d68c475768|72f988bf86f141af91ab2d7cd011db47|1|0|636850635370592977&sdata=AthBLgcDte4o1jCVrE7cIG3azoefpHyvLlc5AuMuMk0%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHZCcJFGZegOI7Pieu60_JWwuNReBtGJks5vKvPvgaJpZM4aRhqs&data=02|01|greg.hoelzer%40microsoft.com|e009add0c7ae4639834108d68c475768|72f988bf86f141af91ab2d7cd011db47|1|0|636850635370592977&sdata=h1dRZAJ7yR2RSFA9jsL9kBCJJwSKIeviivLeivEv1yE%3D&reserved=0.

@ghoelzer-rht - If I remember correctly, PerGB2018 isn't an option available with our internal subscriptions.  This isn't a doc issue so I'm requesting this issue is #please-close.

Closing issue, as MS internal subscriptions don't have access to referenced Azure SKU.

We're running into this with a customer subscription. We're trying to automate the creation of a Log Analytics workspace, but pergb2018 isn't valid. How do we work around this?

Running into the same issue above. Receiving errors when trying pergb2018, but the other options in the documentation work, ultimately have to select a SKU and then switch it manually causing problems with fully automating this piece.


Implemented 3.3.5 - the getter for a loader's registry.

:+1:
btw I'm thinking we should publish the new spec work together as soon as possible and publish it as a 0.20. Even though SystemJS uses the old spec, there's no reason to hold this project back anymore when we have the loader working to the new spec already.

Interesting, I'll try to keep the pull requests coming then :). I've started work on the refactor that caridy committed a while ago to Registry objects and ModuleStatus objects, but am wondering what to do about #461 . What are your thoughts on using Map?

Excellent thanks so much for your work here, that refactor would be really great to get this project released to parity.


As a user, I would like to specify the role in an affiliation record as a picklist similar to relationships, in addition to the Title

e.g.
contact1: Mary Bloggs
account1: Acme Ltd
role: Director
e.g.
contact1: Joe Bloggs
account1: Christ Church
role: Church member

Actually, for the affiliation role, I'd also like to be able to define a list of allowed values that can be entered via the user interface. I guess this is not possible as it is a standard Salesforce text field? Maybe it would be good to have a NPSP specific field with a set of managed values similarish to how the Reciprocal relationships function.
e.g.
Empoyer-Director
Church-Church Member

@donners77 If you complete the Title column in the Data Import template, that will populate down to the Role field on the Affiliation record.

Hmm... Though the Title is sometimes different than the role, for example, "Director" might be a title and "Employee" would be a role.  Any way to add some if/then logic to the import so that a custom role on the Affiliation could be specified, and if not, it would default to the Title?

@BrightStepTracy True - but that's a completely separate issue than what was posted as a Data Import issue. I am updating the title of this so it's a more accurate reflection of the request.

@judisohn I see :)  And, I +1 the Role Picklist on Affiliations.

We added a "Type" field to Affiliations to categorize contacts into general groups: Employee, Board Member, Teacher, Student, Parent etc.  We leave the Role as the title they provide us, which we often use on correspondence or name tags.  I don't think one field can do both things.

**lurch: add

Tracking W-008325


Adding query timeout feature proposition

Timeout may be set individually in every call using QueryOption
e.g.
chromedp.Query(sel, chromedp.QueryTimeout(1*time.Second)).Do(ctx, ex)

Coverage increased (+1.5%) to 68.184% when pulling efe81d070413f8b2b0a36301de5403603f320f9e on mawasak:master into bf52fed0d3e6fc1acb7096f4748fec335fcb5547 on chromedp:master.

Thanks for the patch. We're designing v2 now, and we believe there are better ways to handle this. In particular, practically all internal timeouts should be replaced with context.Context. So the user should be able to attach a context (and thus a timeout or a cancel func) to any action, not just a Query.
Stay tuned!


Error when trying to run this app.

Catchable fatal error: Argument 1 passed to App::bind() must be an instance of string, string given, called in /Applications/MAMP/htdocs/MVCBoilerplate/app/core/bootstrap.php on line 3 and defined in /Applications/MAMP/htdocs/MVCBoilerplate/app/core/App.php on line 14
I am using the exact step as my pull request. Any clue as to why this is happening and how to fix it?

Oh I see... need to make the app to be on PHP7 or above. I am using PHP5.6 on my MAMP. I'll put it in the README file.

@the7th
Can you work on how the config.php file works. Like explain what it does.
Basically, this is where you configure your application database.

Hi, I added description for the conf file but I couldn't find anywhere a sample of how you comment and describe functionalities so I kinda followed the laravel framework style and tried to make the comment clear as possible.

OK. Make pr


build.lua has no access to plugin dir

https://github.com/folke/lazy.nvim/blob/83493db50a434a4c5c648faf41e2ead80f96e478/lua/lazy/manage/task/plugin.lua#L50
From reading the code, I think this line has the issue, that, if a plugin specifies a build.lua file, it gets sourced into the current neovim lua runtime, thereby sharing its CWD.
The build file typically wants a CWD equal to plugin dir.
That is already the case if the build property is a script or a function (via the plugin spec parameter).
Furthermore, if the build is a lua file or a function, it does not seem to run async.
https://github.com/folke/lazy.nvim/blob/83493db50a434a4c5c648faf41e2ead80f96e478/lua/lazy/manage/task/plugin.lua#L62
If this is correct, what would I need to change to run build.lua in plugin.dir and make it and the function variant async?

coroutines?
vim.uv.new_thread?
spawn new nvim --headless -c ?

Fixed in https://github.com/folke/lazy.nvim/pull/1530

build functions or *.lua build files (like build.lua) now run asynchronously.
You can use coroutine.yield(status_msg) to show progress.
Yielding will also schedule the next resume to run in the next tick,
so you can do long-running tasks without blocking Neovim.

vim.env.LAZY_BUILD_DIR is now set to the directory of the plugin that is building,
before starting the build process.

Changing the cwd is not advised since that wouldn't work correctly with code running async or using vim.schedule.

I'll have to remove that vim.env.LAZY_BUILD_DIR, since that too won't work with async builds.
You could have multiple builds happening at the same time, so that env var would be correct for only one build process


[Feature Request] Add Rosa Training

The code isn't out yet but thought I would link here Rosa is a modification of lora to increase the quality https://twitter.com/marktenenholtz/status/1745875618732925086

it needs to be ported to Torch first


Correction of link to Siemens PKI

Correction of the generic link to Siemens into the link to the Siemens PKI web site

Thanks!


[20.09] consul: 1.8.6 -> 1.8.10

Motivation for this change
Version bump. Fixes CVE-2020-25864 and CVE-2021-28156.
https://github.com/hashicorp/consul/releases/tag/v1.8.10
Things done

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

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

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

Result of nixpkgs-review pr 119630 run on x86_64-linux 1

1 package built:

consul

Does the vendorSha not need an update?

@SuperSandro2000 there were no changes to the dependencies, so the hash matches.
https://github.com/hashicorp/consul/compare/v1.8.6...v1.8.10
hash mismatch in fixed-output derivation '/nix/store/va3rfhpllwzwx05rnmx4hffsgg1ikdzr-consul-1.8.10-go-modules':
  wanted: sha256:0000000000000000000000000000000000000000000000000000
  got:    sha256:1zz3hhngvx7989m73cp5a9j6spg42hgqd9vs8v332fvcr277lyxj

@GrahamcOfBorg test consul


Potential race between StopEndpoint and RefreshEndpoint

The main problem is that you cannot safely use EndpointManager without EndpointService, cause all checks for processing sockets are implemented in EndpointService.
So first of all we need to move all these checks to EndpointManager. EndpointService should handle endpoint storage requests (KickEndpoint, RestoreEndpoints) and don't allow change endpoints while they are restoring.
Next step is to add RefreshEndpointRequest to these EndpointManager checks.

We also need to describe all the endpoint-related logic here https://github.com/ydb-platform/nbs/tree/main/doc/blockstore - what entities we have (EndpointManager, ServiceEndpoint, SessionManager, etc.), what are the responsibilities of each of them, which entity calls which entity


problem using groovy-lint on M1 mac (arm64) - Error unsupported architecture

Hi Team,
I debugged the logs a little and found the probable root cause, why my linter is failing on my new Mac (M1 Pro).
2022-08-24T09:55:29.954Z vscode-groovy-lint Request execute npm-groovy-lint for file:///Users/.../pipelines/Jenkinsfiles/deploy-test/Jenkinsfile.install-microk8s-cluster with options {"displayErrorsEvenIfDocumentClosed":false}
2022-08-24T09:55:29.955Z vscode-groovy-lint Reset diagnostics for file:///Users/.../pipelines/Jenkinsfiles/deploy-test/Jenkinsfile.install-microk8s-cluster
Start analyzing file:///Users/.../pipelines/Jenkinsfiles/deploy-test/Jenkinsfile.install-microk8s-cluster
Java jre or jdk between 8 and 14 is required
Installing Java jre 14 in /Users/stefan/.java-caller...
**VsCode Groovy Lint error: Unsupported architecture**
Error: Unsupported architecture
    at Object.install (/Users/stefan/.vscode/extensions/nicolasvuillamy.vscode-groovy-lint-2.0.0/server/node_modules/njre/lib/install.js:204:32)
    at JavaCaller.manageJavaInstall (/Users/stefan/.vscode/extensions/nicolasvuillamy.vscode-groovy-lint-2.0.0/server/node_modules/java-caller/lib/java-caller.js:254:43)
    at async JavaCaller.run (/Users/stefan/.vscode/extensions/nicolasvuillamy.vscode-groovy-lint-2.0.0/server/node_modules/java-caller/lib/java-caller.js:86:13)
    at async CodeNarcCaller.startCodeNarcServer (/Users/stefan/.vscode/extensions/nicolasvuillamy.vscode-groovy-lint-2.0.0/server/node_modules/npm-groovy-lint/lib/codenarc-caller.js:266:29)
    at async CodeNarcCaller.callCodeNarcServer (/Users/stefan/.vscode/extensions/nicolasvuillamy.vscode-groovy-lint-2.0.0/server/node_modules/npm-groovy-lint/lib/codenarc-caller.js:102:22)
    at async NpmGroovyLint.callCodeNarc (/Users/stefan/.vscode/extensions/nicolasvuillamy.vscode-groovy-lint-2.0.0/server/node_modules/npm-groovy-lint/lib/groovy-lint.js:237:32)
    at async NpmGroovyLint.run (/Users/stefan/.vscode/extensions/nicolasvuillamy.vscode-groovy-lint-2.0.0/server/node_modules/npm-groovy-lint/lib/groovy-lint.js:66:13)

I installed 'jre-8u341-macosx-x64.dmg', additional to macOS Java, but no luck so far.
➜  ~ /Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java -version
java version "1.8.0_341"
Java(TM) SE Runtime Environment (build 1.8.0_341-b10)
Java HotSpot(TM) 64-Bit Server VM (build 25.341-b10, mixed mode)

➜  ~ /usr/bin/java -version
java version "17.0.2" 2022-01-18 LTS
Java(TM) SE Runtime Environment (build 17.0.2+8-LTS-86)
Java HotSpot(TM) 64-Bit Server VM (build 17.0.2+8-LTS-86, mixed mode, sharing)

Did somebody solve this already?

I found in ~/.vscode/extensions/nicolasvuillamy.vscode-groovy-lint-2.0.0/server/node_modules/njre/lib/install.js
the missing architecture arm64.
function install (version = 8, options = {}) {
  const { openjdk_impl = 'hotspot', release = 'latest', type = 'jre' } = options
  options = { ...options, openjdk_impl, release, type }
  let url = 'https://api.adoptopenjdk.net/v2/info/releases/openjdk' + version + '?'

  if (!options.os) {
    switch (process.platform) {
      case 'aix':
        options.os = 'aix'
        break
      case 'darwin':
        options.os = 'mac'
        break
      case 'linux':
        options.os = 'linux'
        break
      case 'sunos':
        options.os = 'solaris'
        break
      case 'win32':
        options.os = 'windows'
        break
      default:
        return Promise.reject(new Error('Unsupported operating system'))
    }
  }
  if (!options.arch) {
    if (/^ppc64|s390x|x32|x64$/g.test(process.arch)) options.arch = process.arch
    else if (process.arch === 'ia32') options.arch = 'x32'
    else return Promise.reject(new Error('Unsupported architecture'))
  }

Indeed... what if you try to install java by yourself ? :)
that way, node-java-caller won't try to install java and it should work directly :)

Indeed... what if you try to install java by yourself ? :) that way, node-java-caller won't try to install java and it should work directly :)

That's what I tried as well. As you can see above I installed Oracle Java on top.
That didn´t help. Then I tried with OpenJDK17U-jdk_aarch64_mac_hotspot_<IP_ADDRESS>_1.pkg and removed Oracle Java 1.8.0 before.
Could it be, that there's a max version of 14? Why does it try to install java 14, if I have java already installed (v17.x)
my state is now:
➜  ~ /usr/bin/java -version
openjdk version "<IP_ADDRESS>" 2022-08-12
OpenJDK Runtime Environment Temurin-<IP_ADDRESS>+1 (build <IP_ADDRESS>+1)
OpenJDK 64-Bit Server VM Temurin-<IP_ADDRESS>+1 (build <IP_ADDRESS>+1, mixed mode)

I'm glad you found a way :)

Thanks for the quick response and the great tool!

Why would this plugin not work with recent JAVA versions? Why is 14 the latest supported one?

There's indeed no reason, I'll try to arrange that :)

Can we reopen the issue? I am not sure how to pass JAVA_HOME to the plugin

I have a PR in progress for some time
https://github.com/nvuillam/npm-groovy-lint/pull/259
But test cases are failing and I have some issues to find time to complete it...
If someone has more availability than me, please feel free to try to complete it, i can't provide a delivery date in my current situation :/

All good fellow Nicolas. Thanks for replying so fast and linking the PR. Hopefully, somebody more knowledgeable than me can take a look at it.

I could get it working with OpenJDK11U-jdk_aarch64_mac_hotspot_<IP_ADDRESS>_1.pkg, but I had to remove the newer versions. link

This is the solution for Mac m2 at least now in July 2023. Kudos for the man for figuring this out.

Tried everything, even with OpenJDK11U-jdk_aarch64_mac_hotspot_<IP_ADDRESS>_1.pkg no error was shown but also no issues were found in the code. So I cloned the repo, bumped npm-groovy-lint to 11.1.1 and just copied the folder back to where the extension is supposed to be (nicolasvuillamy.vscode-groovy-lint-2.0.0) and voilà - it's working.

Tried everything, even with OpenJDK11U-jdk_aarch64_mac_hotspot_<IP_ADDRESS>_1.pkg no error was shown but also no issues were found in the code. So I cloned the repo, bumped npm-groovy-lint to 11.1.1 and just copied the folder back to where the extension is supposed to be (nicolasvuillamy.vscode-groovy-lint-2.0.0) and voilà - it's working.
MacOS Ventura 13.5.2 (Apple Silicon) Node v20.6.1

Can you share the steps you made?

Tried everything, even with OpenJDK11U-jdk_aarch64_mac_hotspot_<IP_ADDRESS>_1.pkg no error was shown but also no issues were found in the code. So I cloned the repo, bumped npm-groovy-lint to 11.1.1 and just copied the folder back to where the extension is supposed to be (nicolasvuillamy.vscode-groovy-lint-2.0.0) and voilà - it's working.
MacOS Ventura 13.5.2 (Apple Silicon) Node v20.6.1

Can you share the steps you made?

Well those are the steps, cloned this repo to a /tmp folder, bumped the npm-groovy-lint version in packages.json file, pulled the new package(s), ran build command and just copied folder from /tmp to the proper location.

@djukxe @kkreso @ramiroachaval  this is fixed in newest release v3.0.0, thanks to the great job of @stevenh :)
Please can you confirm it works well for your case now ?

If yes, please rate the app -> https://marketplace.visualstudio.com/items?itemName=NicolasVuillamy.vscode-groovy-lint&ssr=false#review-details
If not, please reopen the issue and we'll check :)


Jeff Schaller: Watch tradikin.com

Jeff Schaller requests the watch of the watch_keyword tradikin\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

tradikin\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


relationReferenceAttribute and dirtyAttributes

Hi,
If the contents of the relationReferenceAttribute array changes, then this attribute does not fit in dirtyAttributes, so they do not work out behaviors like TimestampBehavior, BlameableBehavior and others.
(\yii\behaviors\AttributeBehavior::evaluateAttributes)
How to be in this situation?

There is no way, since 'dirty' attributes may refer only to the ActiveRecord table columns and can not refer to any virtual attribute, which relationReferenceAttribute is.


riot-web: 0.16.0 -> 0.16.2

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from riot-web.
meta.description for riot-web is: '"A glossy Matrix collaboration client for the web"'.

Checks done (click to expand)

built on NixOS

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.16.2 with grep in /nix/store/xs7mp2f42dbj49fr36qmnll76dd3zgrn-riot-web-0.16.2

directory tree listing: https://gist.github.com/16a5fc6331fcc758807ff7782b96edd2

du listing: https://gist.github.com/4fb5ac77a61f2fc3d1e434a78d9e90ee

Instructions to test this update (click to expand)

One-time optional setup to skip building using Cachix:

Install cachix from https://cachix.org/
Use r-ryantm's cache:cachix use r-ryantm

Test this update by entering a nix shell, seeing what is inside the
result, and if applicable, running some binaries:
nix-shell --pure -I nixpkgs=https://github.com/r-ryantm/nixpkgs/archive/c530d641f8118d32863e6bdf1acd55f71573c800.tar.gz -p riot-web
ls -la /nix/store/xs7mp2f42dbj49fr36qmnll76dd3zgrn-riot-web-0.16.2

cc @bachp for testing.

0.16.4 is out already.

Ofborg will prepare the next bump after this is merged :smile:


Bug with Aggregate OnFailure Hooks

There's an issue in both the async & non-async aggregate hooks which results in the hook sending back the valid rather then invalid links.
See: https://github.com/warden-stack/Warden/blob/master/src/Warden/Core/IIterationProcessor.cs#L251
I'll submit a PR for this shortly.

Thanks, waiting for the PR then :).

Hey @spetz have a couple of PRs coming.

Fix for this issue
New Integration for SMTP emails
A new version of an IIteratorProcessor that deals with the other bug

One thing I've struggled to get working is the tests. Running dotnet test in the test project directory complains that there's no test adapter.
Do I need to get some external adapter for the Machine.Specification tests?


Allow to use $or with a mango JSON index

Overview
Since #816, mango JSON index on compound fields can be selected only if the selector make sure that all the fields listed in the index are always present. This commit add a special case where all clauses of an $or can ensure that a field is present.
For instance, if I had an index:
[A, B]

is_usable would now return true for the selector:
{
  "A": "foo",
  "$or": {
    "B": "bar",
    "B": "baz"
  }
}

Testing recommendations
Run the mango test suite. Manually run some mango queries with/without JSON indexes and check that the results are as expected.
Related Issues or Pull Requests

#816

Checklist

[ ] Code is written and works correctly;
[ ] Changes are covered by tests;
[ ] Documentation reflects the changes;

Thanks for this @nono. Would you be able to write an integration test (e.g. https://github.com/apache/couchdb/blob/master/src/mango/test/05-index-selection-test.py#L24)?
It's probably also looking at https://github.com/apache/couchdb/pull/1014 as that PR changes the implementation of has_required_fields a little and $or would be susceptible to the related bug.

fixed in #1038

Thanks @willholley!


Video Conference Mute Config Button

Description of the new feature / enhancement
Append Config button to the Video Conference Mute buttons when connected devices change.
Scenario when this would be used?
Video Conference Mute is great, but it often becomes confused when the peripheral environment changes (probably affects fewer people right now if they're only working remotely). When the audio or video devices change, it'd be really helpful to change the Mic/Camera mute buttons by appending a Config button to the strip. Seeing it there would remind the use that the software isn't set up for the current devices, and it would give them a quick shortcut to the config screen where they can fix the problem.
Supporting information
No response

There have been many issues with the toolbar - so it has to be changed some day. Good extra idea.

Thanks for the feedback but VCM is moving to maintenance only in the 0.67 timeframe. Our team will only directly address critical bugs, security and accessibility issues.
We'll accept community PRs for enhancements.


CollectCliffords pass fails for circuit with large PauliLindbladError

Environment

Qiskit version: 1.3.0rc1
Python version: 3.11
Operating system: macos

What is happening?
qiskit.transpiler.passes.CollectCliffords goes through a circuit and merges recognized clifford gates into combined Clifford operations.
However, this fails if we've appended a many-qubit PauliLindbladError (qiskit_aer.noise.errors.PauliLindbladError) to the circuit. The PauliLindbladError is represented in the circuit as a quantum_channel instruction. At some point, CollectCliffords attempts to convert this channel to a Kraus object, which involves creating a many-qubit SuperOp which naturally crashes with this error:
ValueError: array is too big; `arr.size * arr.dtype.itemsize` is larger than the maximum possible size.
The attempt to convert to a Kraus object apparently happens here:
https://github.com/Qiskit/qiskit/blob/cd26d498c9b74475753b9179ac2b7f84122ffe81/qiskit/dagcircuit/collect_blocks.py#L168
It looks like it encounters the PauliLindbladError (as a quantum_channel) as a successor node (of something), and tries to use that quantum_channel as a dictionary key (suc). Attempting to check for equality with other dict keys apparently involves converting the quantum_channel to a many-qubit SuperOp, which fails.
How can we reproduce the issue?
from qiskit import QuantumCircuit
from qiskit.transpiler.passes import CollectCliffords
from qiskit.transpiler.passmanager import PassManager
from qiskit_aer.noise.errors import PauliLindbladError

pm = PassManager(CollectCliffords(
    do_commutative_analysis = False,
    split_blocks = False,
    split_layers = False,
    collect_from_back = False,
))

qc = QuantumCircuit(20)
qc.cx(0,1)
qc.cx(0,1)
qc.append(PauliLindbladError(generators=['X'+'I'*19],rates=[0.1]),range(20))

qc_transpiled = pm.run(qc)

What should happen?
Personally I don't want CollectCliffords to attempt to do anything with the quantum_channel instructions. It should leave those instructions unchanged, without raising any errors.
Any suggestions?
It looks like internally, the low-level collect functions use a filter_fn in order to ignore some instructions, avoiding the dictionary lookup:
https://github.com/Qiskit/qiskit/blob/cd26d498c9b74475753b9179ac2b7f84122ffe81/qiskit/dagcircuit/collect_blocks.py#L163-L172
Can we modify the existing filter_fn used by CollectCliffords so that it ignores quantum_channel instructions?

Thanks @aeddins-ibm for the initial analysis. Apparently, hashing PauliLindbladError nodes in DAGCircuit requires expanding their definitions (causing the error above). This should be fixed by #13484 which changes the internal indexing data structure to use nodes' integer indices rather than nodes themselves.
However, here is a question, cc'ing @jakelishman and @mtreinish. It does not seem that the PauliLindbladError class coming from qiskit-aer inherits from Operation (please correct me if I'm am wrong). Even though the above code now works, doesn't this break the contract of what nodes can be added to a DAGCircuit? And if it does break, how do we go about it?

This is coming from the Rust DAGCircuit implementation. In the Rust DAGCircuit we're no longer storing a DAGNode python space object in the dag anymore, but instead generating the object on the fly from the rust data. This change would potentially break a lot of user code because prior to #12550 object identity was used for for equality. Since we're generating new DAGNode objects on each python space access that returns a node object identity checks obviously would no longer work. To offset that in #12550 I had to add a equality and hash implementation for DAGNodes so that we can continue to use equivalent nodes as keys in a dict or set members without any issue even if they're not the same exact object. Typically this isn't an issue because all the members of a DAGNode are hashable. The issue here is arguably an aer bug if the __eq__ implementation aren't valid/viable for many qubit PauliLindbladError objects. You'd have the same error if you did PauliLinbladError(...) ==  PauliLinbladError(...)
As for whether this is an API break, I view it as more of a grey area. I don't think we've ever formally defined that an Operation object needs to have __eq__ or be hashable. I think we make that assumption at several layers of the stack that we can compare operations. I think we'll have issues at several levels if an operation __eq__ implementation isn't valid.


[JENKINS-64629] Fix uncaught exception for unauthorized users

When attempting to email a user with a locked, disabled, or otherwise unauthorized account, different types of AuthenticationException were not caught which would cause the mail to fail.
https://issues.jenkins.io/browse/JENKINS-64629
Related to similar update in https://github.com/jenkinsci/mailer-plugin/pull/104
@jeffret-b @basil @jglick @l3ender

@basil - I'm happy to help test an incremental build. We're currently using mailer plugin v1.32.1; I'm not sure how that plugin and this one (email-ext-plugin) are related. Our builds are freestyle and we use the "E-mail Notification" post-build action.
Let me know if I can assist--thanks!

Can I help with testing or any release preparation?

Can I help with testing or any release preparation?

https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/email-ext/2.82-rc1453.0cbb7237bf07/ has incremental releases you can try out.

@l3ender To add to what @jvz wrote above, there are three relevant PRs for this bug:

jenkinsci/email-ext-plugin#277
jenkinsci/mailer-plugin#104
jenkinsci/ldap-plugin#74

The incremental builds for each plugin are:

https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/email-ext/2.82-rc1453.0cbb7237bf07/
https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/mailer/1.33-rc354.11d656da84a4/
https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/ldap/2.4-rc534.e36de41fc087/

For instructions on how to install a custom build, see: https://www.jenkins.io/doc/book/managing/plugins/#advanced-installation

Released in 2.82.


Lift root requirement

I had a stab at a version which does not require root access, and actually not even mounting or repackaging at all. Using isoinfo we can directly extract the kernel and the initrd. As it turns out (via https://unix.stackexchange.com/questions/243657) you can simply append another gzipped cpio archive to the original initrd.img and the kernel will happily read both archives and merge them together into the initramfs.
#!/bin/env bash

isoinfo -i proxmox.iso -R -x /boot/linux26 > linux26
isoinfo -i proxmox.iso -R -x /boot/initrd.img > initrd.img
echo 'proxmox.iso' | cpio -H newc -o | gzip --best >> initrd.img

Thank you, this looks really good. Will implement this!

The ISO is only slightly compressible even with gzip --best, only ~2%, so that step can probably be skipped too.


Support Windows Nodes

This module should support windows nodes. We need passwords too. :)

@1WindowsPuppetAdmin: we've got two stories bring some Windows love to the module:

#21
#22
This will add Windows support for enrolling nodes and delivering credentials.

Closing as duplicate of #24.


I want to add Selection Sort in this repo.

Selection Sort is one of the important Sorting Algorithms.

sure go for it🐱🏍

Done Sir.

great✌🐱🏍


NTVS 1.2 Feedback

Love it? Hate it? Let us know what you think!

Had this weird problem. I'm on VS 2015 Community with NTVS 1.1 installed. Everything just works fine.
Then saw that 1.2 has been released, so went to upgrade.
But when i tried saving .ts files it says on the status bar "The project contained errors. Output generation skipped". But it works whenever I Build the project.
So i decided to go back to 1.1 for the mean time.

The editing experience in 1.2 is much faster and closer to what I've come to expect from browser based JavaScript in Visual Studio.
Unfortunately with issues like #1185 and #1188 it's still not sable enough to recommend and roll out across all our teams.

@mirumatsu Can you share the full error message you are seeing and any other details, along with some steps to reproduce the issue so we can look into fixing this? Does it happen for new typescript projects as well?
Thanks.

There were no error messages, not even a line where there is suspected error. No error when building.
I created a new TS project, and just copied the files from the other project to check if the error would still be there. And, yes, the error still occurred.
This was my setup on my home PC

Installed VS Community 2015
Installed NTVS 1.1 after 2015

Updated VS [Update 1]

Updated VS [VS with Update 2]
Updated NTVS 1.2 RC

Updated VS [Update 3]
Updated NTVS 1.2

Then the problem started with last setup.
Then I decided to go back to previous setup, but the error indication was still there.
Made a full uninstall, then reinstalled with setup 3, but still there.
My last attempt was:
5. Full reset of my PC
Installed VS Community 2015 with Update 3
Installed NTVS 1.1
Pulled the project from office PC.
Saved a file, Built the project and Error indication gone!
But I noticed something regarding node tools analyzing my codes (never showed before),
so I opened my project folder and noticed that ".ntvs_analysis.dat" was there (never there before).
Suspicion: .ntvs_analysis.dat's absence is the culprit.

@mirumatsu Just confirming that you are on NTVS 1.2.
The .ntvs_analysis.dat file is only used by our old static analysis engine that powers intellisense. You can see which intellisense engine you are using by going to Tools -> Options and then Text Editor -> Node.js -> Intellisense. You should be in ES6 IntelliSense. If you are already on ES6 IntelliSense, the .ntvs_analysis.dat file will not be used at all. It was probably created if you opened the project with NTVS 1.1.

Currently I'm on NTVS 1.1 ancd my default IntelliSense is Full IntelliSense. I see the ES6 IntelliSense Preview as the last option. I'm planning to give 1.2 another try. Is the ES6 IntelliSense in 1.2 still a Preview or is it like a final build?

@mirumatsu With NTVS 1.2, ES6 IntelliSense is the default option that we want all users to be on, except if they absolutely cannot live without a certain ES5 IntelliSense feature that is no longer supported. The new IntelliSense is a better overall experience and much more stable as well.

Released several versions since 1.2


TypeError: 'NoneType' object is not iterable

Hi,
I am new to the scGNN package and I am trying to run it to see the output for the tutorial provided in Seurat.
https://satijalab.org/seurat/articles/pbmc3k_tutorial.html
I read the data and create a Seurat object using Read10X and saved the count matrix using the below command.
pbmc.data <- Read10X(data.dir = "~/seurat/filtered_gene_bc_matrices/hg19/")
pbmc <- CreateSeuratObject(counts = pbmc.data, project = "pbmc3k", min.cells = 3, min.features = 200)
write.table(as.matrix(GetAssayData(object = pbmc, slot = "counts")), '~/counts.csv', sep = ',', row.names = T, col.names = T, quote = F)
Then I use scGNN to read the counts.csv as below
python scGNN_v2.py --load_seurat_object counts.csv --output_dir .\seu_dir\ --total_epoch 31 --feature_AE_epoch 500 300 --output_intermediate
It successfully reads the data, preprocesses, and goes through the pre-EM runs and Graph AE. When it enters the main loop, I get the below error message.
TypeError: 'NoneType' object is not iterable
Full Error message

Entering main loop ...
2023-08-11 10:06:22,512 - --------> Computing all metrics ...
Traceback (most recent call last):
File "~\scGNN2.0-main\scGNN2.0-main\scGNN_v2.py", line 248, in
metrics = result.Performance_Metrics(X_sc, X_process, X_feature_recon, edgeList, ct_labels_truth, dropout_info, graph_embed, X_embed, args, param)
File "~\scGNN2.0-main\scGNN2.0-main\result.py", line 77, in init
self.update(self.cluster_labels_old, X_process, X_feature_recon, edgeList, graph_embed, X_embed, param)
File "~/scGNN2.0-main\scGNN2.0-main\result.py", line 85, in update
cluster_index_list = cluster_summary(cluster_label_list)[1]
File "~\scGNN2.0-main\scGNN2.0-main\clustering.py", line 121, in cluster_output_handler
for i in range(len(set(listResult))):
TypeError: 'NoneType' object is not iterable

Could you assist with sorting this issue?
Thanks

Hi @Ashduc,
The error is reported when calculating performance metrics due to no ground truth cell type label input. You could use given_cell_type_labels and load_cell_type_labels to set the ground truth label as input.

Hi @chthub,
I do not have ground truth labels for this analysis.
How to perform scGNN without ground truth labels?


Removed gcv/cf folder

This folder doesn't actually seem to be used any more (except for one utility function). Removing it clarifies the code structure.
Ostensibly this is where the code to support spec.match.gcp-style policies lives; however, the relevant code just doesn't seem to actually be reachable.

@maxsmythe Not sure if you might happen to have specific knowledge about this or if there might be something I'm missing.

I've confirmed that spec.match.gcp doesn't do anything currently. The match seems to be treated as empty - i.e. matching everything.

Unfortunately no specific knowledge on my end


As a player, after seeing the generated image, I want to guess the input prompt within the pre-set time limit, so that I can score points based on my accuracy, enhancing the game's interactivity and engagement.

Acceptance Criteria:

[x] sopra-fs24-group-32/sopra-fs24-group-32-client#34
[x] sopra-fs24-group-32/sopra-fs24-group-32-client#33
[x] sopra-fs24-group-32/sopra-fs24-group-32-client#2
[x] sopra-fs24-group-32/sopra-fs24-group-32-client#32
[x] sopra-fs24-group-32/sopra-fs24-group-32-client#30

commit: 0ce79ac

commit: 391b969


Add support for JXA actions

Fixes https://github.com/quicksilver/Quicksilver/issues/2604
Please see discussion at the issue.

Merging this. Nice feature to have :)
Looking forward to also seeing the documentation updated as per https://github.com/quicksilver/Quicksilver/issues/2604#issuecomment-1107533863


operator project-quay (3.9.0-nightly.20230812)

Add 3.9.0-nightly.20230812 to community operators

/merge possible

/merge possible


IZPACK-1687: Update maven plugins to current versions

Update maven plugins to current versions

@reinhapa Please review and merge,

Lgtm


Create a tool for migrating records between record stores

Since Sumatra supports multiple back-ends for storing records, there should be a way to migrate records between them.
Imported from Bitbucket issue 52,  created by apdavison on 11-26-2010 at 11:55, last modified: 03-09-2011 at 13:43

The RecordStore classes now have sync(project_name) and sync_all() methods, and there is a new command smt sync.
There is an example of how to use this in [source:doc/migration.txt]
Trac comment by apdavison on 03-09-2011 at 13:43


Remove RDK logger dependency from parodus github

Removed RDK logger dependency from parodus github. Also added patch in yocto to support rdk logging for parodus on device arm. Tested this changes, it is working fine.

Current coverage is 11.11% (diff: 100%)

Merging #23 into master will increase coverage by 3.75%

@@            master        #23   diff @@
=========================================
  Files            2          1     -1
  Lines           68         45    -23
  Methods          0          0
  Messages         0          0
  Branches        12          8     -4
=========================================
  Hits             5          5
+ Misses          62         39    -23
  Partials         1          1

Powered by Codecov. Last update 697e208...cd3249c


How can we support request for features/comments/feedback?

one way could be to have a forum (like discus) but maybe it is overkill?
Can we use gitHub to have people submit issues, report bugs and similar?
@FedericoTartarini , any thoghts?

I think we can use the issues on GitHub, I will add a link in the footer as I did in the CBE thermal comfort tool

79830a128f8362cbb707db4d13f08a9521de8cb0


pull request for e2e test at 01/24/2017 10:15:12

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


[Task]: Design for NFT address metadata

Task description
As part of the design changes we have to do for explorer, we need to display the information associated with an NFT address when a user searches for it.
Link to the user stories document.
Requirements
When a user searches for an NFT address, it should not only display the amount of IOTA coins held by the NFT (as described in https://github.com/iotaledger/explorer/issues/232), but should also have other NFT specific information.
Acceptance criteria
When an NFT address is searched for, it should display the metadata associated with NFT.
TODO (@laumair): Explain what metadata is
Creation checklist

[ ] I have assigned this task to the correct people
[X] I have added the most appropriate labels
[X] I have linked the correct milestone and/or project

@laumair to add information about what metadata is and can then request design team for their support in designing.

Done in https://github.com/iotaledger/explorer/pull/320


Register data resources inside of the VFS

Would it be possible to add support for the resources key to automatically include different data files inside the VFS, e.g.
---
title: Resources
resources:
  - data.csv
---

would automatically place the data.csv inside of the current working directory for either webR/pyodide allowing for a read.csv('data.csv')/pd.read_csv('data.csv') statement to work as-is.

I like this idea! With a small tweak: resources should be a key in the shinylive-{r,python} chunk. This could be done at the lua-filter level by copying my work in quarto-base64.

This could be done at the lua-filter level by copying my work in quarto-base64.

Oh wait, the fact that it's hosted with the document means we wouldn't need to base64 encode the file.

@gadenbuie, we still need the quarto-base64 extension for the embedded file approach using comments. This addresses when an app is being directly sourced, e.g. {{< include >}} or written inside the code cell.


Write a TypeScript program to print elements of an array

Description
Write a TypeScript program to print elements of an array
Input  : [1, 2, 3, 4, 5]
Output : 1 2 3 4 5

How to contribute

Save the solution in PrintElementsOfAnArray.ts file
Add PrintElementsOfAnArray.ts file in program/print-elements-of-an-array folder

!assign


Could not login into google account using Chrome

Hi Everyone!
Currently, I log in to Google account with the command:
testcafe chrome:userProfile main.js
or
testcafe chrome main.js
Then Google does not allow us to log in. I can log in to it before.
Is there any solution to this login? Thank you so much!

@takaaptech
Hello,
Please track our progress here. I closed this issue as a duplicate.

Hi, @Farfurix Thank you! I will follow that thread, Hope we can find a way to pass that issue!


Node can be down even the state and target are up

Description

Node can be down even the state and target are up

Results

That will make the farmer bot treat the node as an up node
If all nodes are down and this false node is the only one left in the farmer bot that would deceive the farmer (having an on node while it is actually down, but it won't affect setting power targets because its state is up)

Logs

node 18 on devnet is down while its state and target are up

{
  "id": "0000000617-000001-7e072",
  "nodeId": 18,
  "farmId": 3042,
  "farmName": "dierenboerderij",
  "twinId": 27,
  "country": "Belgium",
  "gridVersion": 5,
  "city": "Beervelde",
  "uptime": 7320,
  "created":<PHONE_NUMBER>,
  "farmingPolicyId": 1,
  "updatedAt":<PHONE_NUMBER>,
  "capacity": {
    "total_resources": {
      "cru": 4,
      "sru":<PHONE_NUMBER>000,
      "hru":<PHONE_NUMBER>000,
      "mru":<PHONE_NUMBER>
    },
    "used_resources": {
      "cru": 0,
      "sru":<PHONE_NUMBER>80,
      "hru": 0,
      "mru":<PHONE_NUMBER>
    }
  },
  "location": {
    "country": "Belgium",
    "city": "Beervelde",
    "longitude": 3.8802,
    "latitude": 51.0826
  },
  "publicConfig": {
    "domain": "",
    "gw4": "",
    "gw6": "",
    "ipv4": "",
    "ipv6": ""
  },
  // status
  "status": "down",
  "certificationType": "Diy",
  "dedicated": false,
  "inDedicatedFarm": false,
  "rentContractId": 0,
  "rentedByTwinId": 0,
  "serialNumber": "Not Specified",
  // power
  "power": {
    "state": "Up",
    "target": "Up"
  },
  "num_gpu": 0,
  "extraFee": 0,
  "healthy": true
}

long time fixed


[FEATURE REQUEST] A Time-based Auto Scan

Is your feature request related to a problem? Please describe.
Current Auto-Scan mode depends on page/document detection. Auto-Scanning won't work when the page's colour is the same colour as the background (like, when a book is on a table, and both page and book are i.e. purely sepia coloured.)
Describe the solution you'd like
An alternative auto-scan solely based on a timer could help alot, without needing to depend on document detection. Like.. "scan every X sec" for example. (would be the best to make the timing configurable)
Describe alternatives you've considered
Additional context

Thank you for your hard work and efforts!

@0lm thanks for the request. May just i ask why clicking on the capture button is not enough in this case?

@0lm i see. Makes sense i can think about this. It would only be available in batch mode i suppose. Would you want document detection still to be applied, or should i just use the full image without trying to detect any page?
Also could you share some image example so that i can see if i can improve the page detection for books? maybe even support scanning both left and right page at the same time


Revert "[Outlook] (manifest) updating API overview to account for JSON manifest"

Reverts OfficeDev/office-js-docs-pr#3562

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

File
Status
Preview URL
Details

docs/outlook/apis.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


update to newer v0.1.6 vertica driver

Reference newer version of Vertica Go driver to fix issue with error-after-parse state.

I've updated the driver and cut a new release.

Thank you, Kenneth. I'll be watching for more issues.
On Nov 15, 2019 4:53 PM, Kenneth Shaw<EMAIL_ADDRESS>wrote:
I've updated the driver and cut a new release.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/xo/usql/pull/101?email_source=notifications&email_token=AK56SCNWYWKKUXMGLUTZBGDQT4RXVA5CNFSM4JN7WCPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEG6T7A#issuecomment-554559996, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AK56SCKWIT5D6LPWCLYMTJ3QT4RXVANCNFSM4JN7WCPA.


Make new methods const where possible

Unfortunately I had to remove ..Default::default() usage since https://github.com/rust-lang/rust/issues/67792 isn't stable yet.

Thanks!


Need file attachement plugin support in the editor

Thanks for the wondeful library.
It would be great if we have a file attachement plugin support in the editor for example attaching .pdf, .doc, .zip, etc...

@ofgowtham added package @yoopta/file
You can play with it in examples - https://yopta-editor.vercel.app/examples/withBasicExample


Diagnostics page unstable

Since the last few updates the diagnostics page keeps crashing and fails to connect. Sometimes it takes 5 minutes, sometimes 30, other times it fails to start completely.
8.24.4 update finally got synced up and started witnessing, then the 8.25 update came and it hasn't been good ever since.
The real troubles started with the 8.21 update. 8.16 was stable and functioning fine, ever since then it's been unstable and non-functional.

Closing this as haven't heard anything more in ages


Add different display types for leaf_distributions x-axis.

Here is a demo for ctree_leaf_distributions with a small tree where xaxis_display_type='individual' would be preferred:

And here is a demo for ctree_leaf_distributions with a large / deep tree where xaxis_display_type='auto' would be preferred:

@parrt @tlapusan LMK what you think! I like this as one potential solution, the gaps between the node IDs aren't too distracting if it there are a lot of leaves. We can add other options to xaxis_display_type too, if you want to try other solutions.
Also, when we are happy with the path forward, the changes will also need to be made to leaf_sizes, leaf_purity, rtree_leaf_distributions.

Probably should standardize the x-axis title to "Leaf IDs" in rtree_leaf_distributions as well.

Seems to me that node IDs just aren't useful unless you can identify a specific node, so for the auto I just don't think I would ever find it useful.
I think we should order the information by its usefulness not the arbitrary node ids.  Too bad we can't simply have a hover over the bar that would pop up the node id if you want it. I don't think we can do interactive stuff with matplotlib.

I know I would find xaxis_display_type='auto' useful to make an overview plot of all the nodes.
For example, I would use it to make a first figure of all the nodes to say "here are all of the nodes of the tree, as you can see nodes X, Y, Z are interesting because of ...", and then include a second figure with xaxis_display_type='individual' cropped down to those nodes of interest. The major axis ticks will give a reader a rough idea of what nodes are interesting in the first plot while contextualizing them, and the second plot would give precise info on each node's properties.

I suppose the node ID General area could be useful and it doesn't hurt to include but fewer options is always good.
What do you think about ordering the graph by magnitude of y axis to get a better idea of what's important?

I think we should order the information by its usefulness not the arbitrary node ids. Too bad we can't simply have a hover over the bar that would pop up the node id if you want it. I don't think we can do interactive stuff with matplotlib.

What do you think about ordering the graph by magnitude of y axis to get a better idea of what's important?

Yeah, we could do interactive stuff with something like plotly, but then we couldn't save it to a flat file.
I'll add a xaxis_display_type='y_sorted' which will display the nodes in decreasing y value, without any x-axis tick labels.

What do you think about ordering the graph by magnitude of y axis to get a better idea of what's important?

@parrt how does this look for xaxis_display_type='y_sorted'?

I know I would find xaxis_display_type='auto' useful to make an overview plot of all the nodes.
For example, I would use it to make a first figure of all the nodes to say "here are all of the nodes of the tree, as you can see nodes X, Y, Z are interesting because of ...", and then include a second figure with xaxis_display_type='individual' cropped down to those nodes of interest. The major axis ticks will give a reader a rough idea of what nodes are interesting in the first plot while contextualizing them, and the second plot would give precise info on each node's properties.

@mepland curios what do you mean by "cropped down to those nodes of interes" :)
If the plot will contain a lot of leaves, by using 'individual' will still be useless since the user couldn't clearly get the node id.
I see useful the utility of "auto" in this case :

user get an idea in which range of ids are the leaves he wants to investigate
switch back to "individual", BUT the ctree_leaf_distributions() should have a parameter, like show_leaf_id_range, which will display only the leaves from that range. In this case, the leaf ids could be clearly seen. This is kind of the same leaf filtering strategy which I described here https://github.com/parrt/dtreeviz/pull/220#issuecomment-1383199791, but it seems it doesn't have that much attention :D

@tlapusan I meant basically what you suggested. We could include any combo of:

Specify the range of node_id values to include via show_leaf_id_range as you suggest.
Specify the exact node_id values to include via show_leaf_id_list
Specify for the leafs in terms of the range of y-value via show_leaf_y_range

I think 1 and 2 are the most useful, with 2 anything, such as 3, can be added on by the user.

Hi @parrt and @tlapusan, circling back to this. I think if I implement show_leaf_id_list, 2 above, this should give the end user the flexibility to do whatever they want without making the dtreeviz code overly complex. What do you think?
Would love to get this merged this month!

Hi @mepland,
I pull your code and ran the ctree_leaf_distributions for each xaxis_display_type value.

It seems to be some issues (worked in sklearn notebook). For auto, the x values are not correct distributed and for "y_sorted" there is a code issue (maybe because meanwhile we changed the code to support multi class labels (not only binary classification)).

@tlapusan @parrt I fixed the code so now it works with multiclass, and added the show_leaf_id_list parameter:

@mepland nice, those bugs were fixed :)
few suggestions :

when the plot will contain a lot of leaves, still hard to identify a node id by following the xaxis_display_type="auto" -> show_leaf_id_list=[x, y, z].
As we discussed here, https://github.com/parrt/dtreeviz/pull/254#issuecomment-1413107120, the step 1 and 3 could be more helpful. In the end, if someone could get the node id from the 'raw' visualisation... why would he need to use the show_leaf_id_list ?

xaxis_display_type="auto"
Would be helpful to have int values on X axis... seeing floating numbers is a little odd since the values should represent leaf ids.

xaxis_display_type="y_sorted"
Looks nice, do you think would be helpful to have also the leaf ids on X axis ?

@parrt how does this look for xaxis_display_type='y_sorted'?

Looks pretty cool to me!

Would it be possible to get the bars the same width (maybe only when there is room)?  I guess it's no big deal and they aren't uniform as they are now.
I'm still not convinced we'll get a good way to identify leaves of interest looking at x axis labels.  What about tooltip text?  Unlike the tree view, these are just matplotlib plots so we can do tooltips: https://towardsdatascience.com/tooltips-with-pythons-matplotlib-dcd8db758846

tooltip could also help :)
I tried the first example from https://mplcursors.readthedocs.io/en/stable/ and it's not working for me... and I do meet the requirements "Python 3, and Matplotlib≥3.1."
I see tooltip as a 'hidden' feature... not sure that majority of people will discover it.

haha. figures mplcursors didn't work.
I guess I am OK with this PR; if it's useful to you guys that's good enough for me!

Hi @parrt and @tlapusan, I just added a show_leaf_filter parameter that takes a function which a user can configure to implement any filtering criteria they would like on the leaf values, per class. Here is the doc string and a demo:
:param show_leaf_filter: Callable[[np.ndarray], bool], optional
   The filtering function to apply to leaf values before displaying the leaves.
   The function is applied to a numpy array with the class i sample value in row i.
   For example, to filter to leaves with 100 < total samples, and 5 < class 1 samples, use show_leaf_filter = lambda x: (100 < np.sum(x)) & (5 < x[1])

cool!  Typo here though: "to filter to leaves with 100".  Should that be "filtering out"?

Replying to your comments @tlapusan:

As we discussed here, Add different display types for leaf_distributions x-axis. #254 (comment), the step 1 and 3 could be more helpful. In the end, if someone could get the node id from the 'raw' visualisation... why would he need to use the show_leaf_id_list ?

show_leaf_filter gives you option 3, and more! Option 1, giving a range of node_id values, can be implemented easily by the user with an expansive show_leaf_id_list, so I do not think we should implement it specifically.

xaxis_display_type="auto"
Would be helpful to have int values on X axis... seeing floating numbers is a little odd since the values should represent leaf ids.

I agree it doesn't look the best, but if we force the x-axis ticks to have an int format then the tick labels do not make sense. In this example it would be 2, 5, 7, 10, 12, 15. I think it is better to leave as is, especially as users will be using auto when there are a lot of leaves and you are in more of this case.

xaxis_display_type="y_sorted"
Looks nice, do you think would be helpful to have also the leaf ids on X axis ?

When sorted by y value the leaf node_id values are all out of order, and would need to be individually labeled, like individual. However, when y_sorted is useful there are probably too many leaves for this to happen without overlapping text - putting us back in this situation.

cool! Typo here though: "to filter to leaves with 100". Should that be "filtering out"?

@parrt, not really a typo, the filter keeps leaves that pass its criteria. I'd be open to rewording it though, if it's not clear. Any suggestions?

Would it be possible to get the bars the same width (maybe only when there is room)? I guess it's no big deal and they aren't uniform as they are now.

@parrt, aren't the bars all the same width now? They just expand and contract to fit the available horizontal space. I guess I'm not sure what you mean by this.
And yeah, tooltip text is nice in theory - but frequently breaks and can't be printed to a flat image anyway :smile:

aren't the bars all the same width now? They just expand and contract to fit the available horizontal space. I guess I'm not sure what you mean by this.

no worries. i just meant two diff nodes have diff width bars.

to filter to leaves

yeah, that doesn't make sense to me. Maybe: "to filter for"?
For example, to filter for leaves with 100 < total samples, and 5 < class 1 samples, use show_leaf_filter = lambda x: (100 < np.sum(x)) & (5 < x[1])
Or,
For example, to view only those leaves with more than 100 total samples and less than 5 class 1 samples, use show_leaf_filter = lambda x: (100 < np.sum(x)) & (5 < x[1])
Why do you use "100 < total" btw? Ain't that backwards?  Never seen that except C programmers in 1980s.

For example, to view only those leaves with more than...

Updated to this.

Why do you use "100 < total" btw? Ain't that backwards? Never seen that except C programmers in 1980s.

Well, I did learn to program in C++ from particle physicists mostly trained in the 80s and early 90s so that might be part of it :smiley:, but I also like when the inequalities increase from left to right, like a number line.

@parrt I think it's ready to merge!

Ah with that interpretation of an axis, I can understand why that makes sense. Unfortunately no one expects that ;)

yay! Thanks very much for these important changes...


Complete test coverage for resyncing of NodeInfo data

Coverage decreased (-0.07%) to 77.137% when pulling 519306e244effaf0065622d307ec87960c921013 on jmedved:contiv-crd into f6e9c0a94d983d70bd12c12bc3f872a18b359c19 on contiv:contiv-crd.


Chunked upload_documents

Extend upload_documents to allow for chunked uploads of documents (steal from copy_index.py). Add a progress bar for large uploads and maybe add some some documentation so the user knows right away what the server expects

Implemented in https://github.com/ccs-amsterdam/amcat4apiclient/commit/33b3014a44b108c514f27ac98a393244e832caec. Thanks @mrwunderbar666


Split off parts of the runtime module into input, forest and parser.

Only runtime remains GLL-specific, the other modules can be moved to grammer at some point.

I haven't addressed any of @Centril's comments, but if @qmx, @CAD97, or anyone else wants to take a stab at them, I'd be glad to mentor!


Update CCDB to latest, fix chart issues

This fixes:

Data issue in line chart when toggling back and forth between Area Chart and Stacked Area Chart
Color contrast in buttons is improved
Charts resize correctly when browser window is resized

Additions

Removals

Changes

How to test this PR

Pull code down
run code
Confirm buttons appear lighter than what is on production now
Go to line chart in Trends view
Count the date periods that appear
Toggle between Area and Line chart and confirm that we are not losing date periods when we swap the charts
Resize the browser window width
Confirm that the charts are actually resizing to fit the page

Screenshots
https://github.com/user-attachments/assets/e8de4e76-10ac-4a64-bd2b-a15f0601dac2
Notes and todos

Checklist

[ ] PR has an informative and human-readable title

PR titles are used to generate the change log in releases; good ones make that easier to scan.
Consider prefixing, e.g., "Mega Menu: fix layout bug", or "Docs: Update Docker installation instructions".

[ ] Changes are limited to a single goal (no scope creep)
[ ] Code follows the standards laid out in the CFPB development guidelines
[ ] Future todos are captured in comments and/or tickets
[ ] Project documentation has been updated, potentially one or more of:

This repo’s docs (edit the files in the /docs folder) – for basic, close-to-the-code docs on working with this repo
CFGOV/platform wiki on GHE – for internal CFPB developer guidance
CFPB/hubcap wiki on GHE – for internal CFPB design and content guidance

Front-end testing

Browser testing
Check the current browser support cutoff list](https://cfpb.github.io/consumerfinance.gov/browser-support#current-browser-support-metrics) for browsers that are advisable
to prioritize for testing.
Accessibility

[ ] Keyboard friendly (navigable with tab, space, enter, arrow keys, etc.)
[ ] Screen reader friendly
[ ] Does not introduce new errors or warnings in WAVE

Other

[ ] Is useable without CSS
[ ] Is useable without JS
[ ] Does not introduce new lint warnings
[ ] Flexible from small to large screens

We don't use structured clone yet because jsdom doesn't support it in
testing that i know of.  I'll check to see if we can use it in an update
On Tue, Sep 24, 2024, 7:09 AM Ans @.***> wrote:

@.**** approved this pull request.
The cloneDeep
https://github.com/cfpb/ccdb5-ui/blob/5c76b5368b5dd65656811c9a770b33660041b41b/src/utils/index.js#L211
method is pretty minimal, but you could look into whether structuredClone
https://developer.mozilla.org/en-US/docs/Web/API/structuredClone would
be a more efficient/standard way of doing this.
—
Reply to this email directly, view it on GitHub
https://github.com/cfpb/consumerfinance.gov/pull/8591#pullrequestreview-2325404664,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH5PYQILOZJZIV7YHZ2PD3ZYFXC5AVCNFSM6AAAAABOYLZ5DSVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDGMRVGQYDINRWGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


[Qiskit Ecosystem] Add an ecosystem.json file

Summary
In order to pass the check on the Qiskit Ecosystem the proejct need an Ecosystem file called ecosystem.json.
This file is needed as soon as their are customization, here its the repo the tests are launching and the test requirements file.
Details

[x] Create ecosystem.json
[x] Dry run of Ecosystem check job run

Closes #165
Related to https://github.com/qiskit-community/ecosystem/issues/202

Hi @cqc-melf :)
I'm a Qiskit Advocate contributor to the Qiskit Ecosystem. Your project is actually a member but don't pass our checks anymore. Here a PR with a simple file to make it pass.


Knex migration attempts to create already existing changelog and fails entire migration

Environment
Knex  0.14.4
PostgreSQL 9.6.6
Bug
Since the upgrade to 0.14.4 we've started getting this error in CI:
 Knex:warning - migration failed with error: create table "crm"."crm_migrations" ("id" serial primary key, "name" varchar(255), "batch" integer, "migration_time" timestamptz) - relation "crm_migrations" already exists
02:18:00 Error migrating:  { error: relation "crm_migrations" already exists

It looks like 7ff766f7a380dbea97b99e4d3bd2077a7b9f8f35 actually wasn't as innocent as expected.
Might be related to the fact that we are using custom migration changelog table via

tableName: ${SCHEMA}.crm_migrations

parameter.

I think that syntax is not supported, but there has been requests to support something like that. Basically the problem is probably that .hasTable('schema.tableName') doesn't work (IIRC there was long discussion why it does not work).
Probably it is necessary to change configuration to also support schemaName in addition to tableName parameter.
Need to dig up old discussions and check out the code to be able to decide exactly how to support that.

@elhigu AFAIR, there is also plan to get rid of createTableIfNotExists in favour of hasTable. If former supported schemas and latter will not, that's going to be a rather painful breaking change.

Former did support schema only by accident. It has never been an official tested / documented feature. Schema reference should have been given currently with .withSchema() builder method.
Reason for not supporting schema.table.column references has been ambiguity of the syntax, when at some places part1.part2 means schema.table and in others table.column. It always has depended of the context where identifier has been used.
Anyways I'am interested in looking through all the knex APIs and see if it would be feasible to allow, test and document schema.table.column syntax officially.

Related discussion https://github.com/tgriesser/knex/pull/2026

I would  say that fastest fix for this would be to add schemaName to configuration and supporting schema.table syntax is bigger issue to resolve.

Kind-of related issue/request #1138

We've had the same issue, locked to<EMAIL_ADDRESS>to work around it.
Something like 'knex.migrate.withSchema(...)...' as suggested above, or perhaps a 'withSchema' property on the migrations config object would be a good fix.

Any news on this? I guess that it's pretty bad to have the current version broken... 😿

@nunorafaelrocha broken is a bit strong term for missing feature. But yeah it wouldn't hurt if someone implements this by adding that schemaName attribute to configuration.

Hi @elhigu. Sorry, I meant no harm. But adding this feature as a patch and then force developers to change the use of the lib doesn't quite follows semver (it actually sounds like a BC). In a way, doing it on a patch have broken the use of it for everyone that allows patch updates.

Exactly, after this update came out, our CI builds started failing without us changing anything, and that is pretty much a definition of semver breaking change.
I'll look into providing a PR for this next week.

@nunorafaelrocha no harm done, just mentioned about dangers of using implementation deatails as a features.
This breaking/non-breaking/semver discussion has actually been discussed here at least couple of times before :) Knex is following semver and Knex is still < 1.0 so semver says that every change can be breaking change (of course it is debateable if knex version 1.0 should already have been released).
That aside line between non-breaking change and non breaking ones is pretty shady, since every small change that can be tested also changes functionality in some way and may break someone's code (even making simple bugfixes / adding new attribute somewhere can break someone's tests). So mostly I've been drawing that line where changing functionality that is not documented/tested public API is non-breaking change and changing documented functionality is breaking.
That being said of course if I would have know that people is using this implementation detail here, I would have marked it as breaking one even that it was undocumented functionality.
@igor-savin-ht nice I'm looking forward to check that PR 👍

@elhigu Any timeline for a release with this fix?

Asap, this weekend I suppose.

Awesome, thank you!


Remove deprecated WidevineCdm folder for Chromium 67

PLEASE DON'T MERGE UNTIL WE'RE READY FOR Chromium 67

is the package-lock necessary?

I just wasn't sure if something else was needed instead or if it's not needed or included in the cdm download now.

@darkdh yes- package-lock.json changes needed to get rid of a security error brought up on the repo
@bbondy I'll update the 0.22.x-c67 branch to use this and do a new build so we can confirm it works 😄

I verified this does work... but unfortunately npm install with the dep brave/muon-winstaller isn't running the precompile step and so muon-winstaller is not aliased as a binary. I can manually run the steps and the npm run build-installer works fine.  Not sure of a way to fix this, other than hackery

work-around in place... doing a build now:
https://github.com/brave/browser-laptop/commit/43abb24df3d3c66ee196853cabab56a73038c051


New method for placing naval bases

The existing buildings file in HoI4 has just about the same number of naval bases that we output. On the whole, we should be able to just read in HoI4's naval positions, associate them with the appropriate provinces, then output them again.

There was only one province were this didn't work (8913), and it looks like that province is bugged: it should be sea, but is marked as land. I've reported that as an HoI4 bug on the forums.


reload: copy state on both name and labels

Fix https://github.com/prometheus/prometheus/issues/5193
Using just name causes the linked issue - if new rules are inserted with
the same name (but different labels), the reordering will cause stale
markers to be inserted in the next eval for all shifted rules, despite
them not being stale.
Ideally we want to avoid stale markers for time series that still exist
in the new rules, with name and labels being the unique identifer.
This change adds labels to the internal map when copying the old rule
data to the new rule data. This prevents the problem of staling rules
that simply shifted order.
If labels change, it is a new time series and the old series will stale
regardless. So it should be safe to always match on name and labels when
copying state.
Can you have a look @fabxc?

The CopyState comment needs updating.

Okay, updated it.

Thanks! It doesn't solve the problem generally, but should help.


Fixed Arena protos

Fixes #278

test me

Build Passed :ok_hand:
You can safely merge 'fix-arenas' into 'revision'.

👍

:eyes:


Custom punct before blocks

Yew support "Dynamic tag" https://yew.rs/docs/concepts/html/elements#dynamic-tag-names
Which allows writing
<@{format!("h{}", level)} class="title">{ text }</@>

Current implementation of syn-rsx, instead force you to write same code in following syntax
<{format!("h{}", level)} class="title">{ text }</{format!("h{}", level)}>

To support yew syntax, we should extend transform_fn for blocks  to also support outer punctuation.
Can be related to https://github.com/rs-tml/rstml/issues/8
To avoid duplication in current syntax (in open and closed tags), we can also avoid matching them if node_name has Block type, this allowing to support syntax like:
<{format!("h{}", level)} class="title">{ text }</{...}> // or any other custom syntax in closed tag block body

Thanks to @LLBlumire wildcards are now allowed in close tags, so it is now easier to use "blocks" in element name.
Currently wildcard is limited to already valid NodeName, so:
//this works:
<{"foo"}> </_>
//this doesn't:
<@{"foo"}> </ @>

Because there still might be needs for special puncts in element name place, i decide to keep this issue open for a while.
Probably one way to add custom punctuation support  is to allow NodeName extension through the config.

Maybe we could replace the syn::Block in NodeName::Block with a NodeBlock, that way it could store arbitrary tokens, and a transform_tag could just return Result<Option<NodeName>>, if it is Ok(Some(_)) this is the value used for the OpenTag::name, if it is Ok(None) the tag will be parsed as a normal tag.
Alternatively, we could make OpenTag an enum, but we already have the NodeName enum, and I think it would work quite well.
(Maybe we could even parse the remaining tokens in the tag as NodeAttributes.

@ModProg hi, in my opinion it could be done by extending enum Node.
Probably we can add variant KeywordElement/BuiltinElement with custom body.
And trait with methods:

peek_element(ParseStream)-> bool
parse_element(RecoverableContext, ParseStream) -> Option<KeywordElementInner>

So that adding new type of elements would be moved outside of rstml.
There is two challenges that need to be solved:

How to avoid duplication between ElementNode and KeywordElement
If KeywordElementInner would be generic type - user should provide it through config with some reasonable default

I guess a reasonable default would be Vec<Node> being what NodeElement's body is.
Another question, would this custom node necessarily be open tag, body, and optional closing tag, or should it be able to parse any syntax, i.e. even one not starting with <.
Technically this is something that is already supported by reparsing RawText, though a fully custom parser could probably do a bit more, i.e. allow usages of < that would be invalid in normal raw text.
if we were to support the peeking to be called even without a leading <, it could make sense to not have any NodeElement releated types here, i.e. making the Variant Node::Custom(T =Infallible/!).

If we go with the fully custom node, I think it would make sense to expose part of NodeElement::parse_recoverable to allow custom nodes to easily parse bodies and closing tags.


KAFKA-17648: AsyncKafkaConsumer#unsubscribe swallow TopicAuthorizationException and GroupAuthorizationException

If users subscribe to a topic with invalid name or without permission, they will get some exceptions. Network thread sends MetadataRequest and FindCoordinatorRequest in the background, so there will be some error events in the background queue. When running AsyncKafkaConsumer#close or AsyncKafkaConsumer#unsubscribe, these exceptions should be ignored, or users can't close the consumer successfully.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Yes, it's same. I will close this one.

Hi @kirktrue, after discussing with @m1a2st,  this PR will focus metadata error on unsubscribe and close and his PR https://github.com/apache/kafka/pull/17440 will focus on other functions like beginningOffsets, endOffsets, etc. Thank you.
Could you help me review https://github.com/apache/kafka/pull/17199 first? This PR will rely metric to know there is background event, so we can check unsubscribe and close can work when there is metadata error. Thanks.

Hi @lianetm, thanks for review and suggestion. Updated both title and PR description. Thanks.


How to disable a sapling in the config.

Hello, i have tired many different times and ways to disable a sapling from the mob, Forbidden & Arcanenus . The sapling in question is the is the Mysterywood sapling  and no matter what i try it wont disable where you cant put it into a bonsai pot. The reason i am trying to disable this for me and my friends is becase i dont want a automatic farming way of getting golden apples.
thank you for your time.

Which version of BonsaiTrees are you using?

I believe it is the latest 1.12.2 version

You have two options. You can either disable the use of the tree as a bonsai by editing the bonsaitrees settings.cfg as such
# Tree types to disable (e.g. forestry:hillCherry) [default: ]
S:disabledTreeTypes <
forbidden_arcanus:mysterywood
 >

Or you can solely disable the golden apple drop by putting this json in the types.d folder of the bonsaitrees config folder.
forbidden_arcanus_mysterywood-NoGapple.zip
Make sure to do this in the server configuration. If you join the server without the config changes you'll still be able to see the normal recipe in JEI, but it doesn't actually affect your ability on the server.


Add PHI PII definitions

Unrelated to the subject of this PR, the Redaction section has numbered steps, but only one top-level number.  I think it would look better to make 1. Reviewing the image(s) and metadata for PHI/PII. as minor title and outdent everything below it by one number.

Unrelated to the subject of this PR, the Redaction section has numbered steps, but only one top-level number. I think it would look better to make 1. Reviewing the image(s) and metadata for PHI/PII. as minor title and outdent everything below it by one number.

Agreed and done.


[transmission] use env config

Description of the change
Goes along with https://github.com/k8s-at-home/container-images/pull/106/ discussed here https://github.com/k8s-at-home/charts/pull/813
Changes configmap config to env config
Let's wait until the container image is pushed and released before merging this.
Additional information

Checklist

[x] Chart version bumped in Chart.yaml according to semver.
[x] Title of the PR starts with chart name (e.g. [home-assistant])
[x] Variables are documented in the README.md (this can be done with using our helm-docs wrapper ./hack/gen-helm-docs.sh stable <chart>)

While I appreciate the question for input, this is as close to rediscovering the wheel as one can get. I'll be stepping back from the project and rolling out my own chart for personal use

I'll be stepping back from the project and rolling out my own chart for personal use

Sorry you feel that way. I can admit what I originally changed was a mistake but I was hoping to make up for it with this PR.

I'll be stepping back from the project and rolling out my own chart for personal use

Sorry you feel that way. I can admit what I originally changed was a mistake and I was hoping to make up for it with this PR.

That's ok, I don't feel any ill will :) That said, it seems we have different viewpoints on what the project was meant to do, and that's perfectly fine. Consider it an amicable split :)

That said, it seems we have different viewpoints on what the project was meant to do, and that's perfectly fine. Consider it an amicable split :)

Viewpoints on one chart, one configmap change, shouldn't make you ragequit contributing to these charts. I'd still like to have you around. You offer insight, and criticism not many people have the depth of knowing.
From the start we should have offloaded this configuration to the container image, it's all about iterating over design choices. I strongly feel this environment based configuration is much better than using a configmap in either way of it being a string or YAML objects.

[..]shouldn't make you ragequit contributing to these charts

In order for me to ragequit, I'd have to write a salty rant first. Which I didn't. So let's leave the emotionally charged language at the door

From the start we should have offloaded this configuration to the container image

That would require me to be the author of the image. Which I wasn't. But even baring that, I don't see the technical superiority of just passing through every option as an env instead of a config file. Maybe except for the fact that any change in these settings - which was your main argument in the original patch - would really be now obfuscated to anyone upgrading, IF they were to change. What's faster, looking at values.yaml, or looking at a tpl file inside of the source of the container? Which CD suite will show the difference in that kind of happenstance? Helm diff sure wouldn't
And here's the thing - for some time k8s@home has been plagues by changes for changes sake. Or for "consistency". At first common would just be that - a common lib for common media containers, which was fine because *arr containers really are made from the same cloth. But then one after another every app or chart was heavily pushed to migrate to it, no matter if it really fit or not. And this change, the "one configmap" is simply a change that took it too far for me.

But then one after another every app or chart was heavily pushed to migrate to it, no matter if it really fit or not

Actually, about 90% of simple apps (the once people normally deploy at home in stock docker), need:

A service
A deployment
Ingress
Some storage

That's what the common chart (and other common-charts within other projects) is there to facilitate. Together with easier maintenance.
There is nothing "special" about transmission that  requires it to be a completely seperate chart. Besides one configmap, it's no different from: Jackett, Tautulli, Sonarr, etcetcetc.
To be clear:
I've had cases where I had to hack charts to fit into the common chart, yes.
But those are rare and definately more diffcult than "just" adding a configmap.


TypeError: Cannot read property 'dynamodb' of undefined

I followed the instructions to install plugin, declare in "plugins" section of serverless.yml, and install with sls dynamodb install.
when i run sls dynamodb start I get the error in the title, at /Users/overlord/Dev/Trails4.0/serverless/node_modules/serverless-dynamodb-local/index.js:211:45
here's what that line looks like in context:
startHandler() {         let self = this,             options = this.options;         return new BbPromise(function(resolve) {             let config = self.service.custom.dynamodb,                 options = _.merge({                         sharedDb: self.options.sharedDb || true                     },                     self.options,                     config && config.start
Any ideas on how to make this work?

Sorry, terrible formatting... line 211 is: let config = self.service.custom.dynamodb,


Two GeoFilteredList

Hi,
Your work would be very usefull but when i want to test with npx adalo dev the components that i see in adalo are two GeoFilteredList.
Unfortunately I need more the GeoLocalization component.
It happened to others?

Yes, It has happened to one other person. We release an installer over the weekend. The suggested installation method is via https://adalo.pragmaflowservers.com/install-component
unless you want to customize the code. If that is the case, I believe it was solved by reordering the components in package.json
swap lines 18-21 with lines 22-25 and fix the comma, should do the trick


Error on message submit without subject

I implemented a system based off of the example by @RKushnir, and it works. At some point, or since the beginning, submitting a new message without a subject results in a Cannot redirect to nil! error.
Here is the action:
def create
recipient_usernames = conversation_params(:recipients).split(',')
recipients = User.where(:username => recipient_usernames).all
conversation = current_user.
  send_message(recipients, *conversation_params(:body, :subject)).conversation

redirect_to conversation

end
Conversation is nil here, though I dont see why it should be.
Any ideas?

Messages now don't require a subject, this can be closed.

I'm having the same problem If message no longer requires a subject may I see how you would send a message without a subject like receipt=current_user.send_message(OtherUserObject, 'Test message body') This gets me wrong number of arguments 2 given min 3 required


More granular CLI tests

Tests that check specific error messages for different behaviors

@supiket Could you elaborate on this a bit more?

When reviewing the linked PR above your comment, we had talked about how it would be nice to have more specific asserts than assert!(r.is_err())


Update vaccine modelling

This makes a number of changes to the vaccine model to support our upcoming work related to importing vaccine information:

Add validation and not null to most fields
Add unique constraints on globally unique fields
Rename supplier to manufacturer

Most of the changes here relate to changes I had to make to the tests/factories to support these changes, which I've included as a separate commit.

It must have been frustrating to make as many alterations to the specs as you've had to make in e10b527, and I wonder whether it's something that the factories could handle better, but let's roll forward.

I'm hoping I've left the factories in a better state than I started, but yeah, I think part of the problem is that a lot of factories end up creating new campaigns, and from there we get a whole new set of vaccines, etc. I was wondering if there was a way we could get factory bot to do a "find or create" on vaccines, but it didn't seem officially supported, and I didn't like the implicit nature of that.
I think the work in #1550 might be relevant here in terms of how we manage the vaccine data.


Remove default mail signature

An issue for the same topic was already opened on google code. It boils down to: the default signature is unprofessional, annoying and judging from the top google hits it is also the first thing that people try to get rid when starting to use k9.

Being "professional" is not one of the goals of this project.
If you're bothered by the signatures of your communication partners I'm happy to review pull requests for a feature to hide signatures in mails received.

And annoying it's users is? Don't get me wrong - I am perfectly aware that this is an open source project, done by people in their free time.  I would at least 'put it to the vote' and leave the issue open to see what others have to say about it...

On March 26, 2015 6:46:17 PM EDT, sspind<EMAIL_ADDRESS>wrote:

And annoying it's users is? Don't get me wrong - I am perfectly aware
that this is an open source project, done by people in their free time.
 I would at
least 'put it to the vote' and leave the issue open to see what others
have to say about it...

I'm  new to the list so maybe I'm  ignorant  but what's  the issue here? The app allows you to change and/or diasble signatures. How is that a bad user experience?

Reply to this email directly or view it on GitHub:
https://github.com/k9mail/k-9/issues/589#issuecomment-86743921

The issue is with the default signature which I claim to be unnecessary. It really is just a personal preference - one that I share with quite a few people at least judging from the results you get from googling 'k9 signature'.

All mobile email clients I think provide the first clause. "Sent from my iPhone" is the default signature on every iPhone device. My HTC's default signature is 'Sent from a HTC One".
"Please excuse my brevity." is perhaps over kill however.
Maybe we should present the signature configuration during account set-up?

That would be great but also more complicated to implement...