Some classes are not importable

It appears that some of the classes (i.e. DigitalState) are packaged after compilation (.class files)
Which means that they cannot be imported.
In example:
// use a configuration builder
var ledConfig = DigitalOutput.newConfigBuilder(pi4j)
        .id("my-dout")
        .name("My LED")
        .address(PIN_LED)
        .shutdown(DigitalState.LOW)
        .initial(DigitalState.HIGH);

throws an error: Cannot resolve symbol 'DigitalState'.
Is this intentional? Can it be fixed?
Tested with Pi4J v2.5.0 & v2.6.0

I added this code to an existing testcase.  Appears to work for me.
my imports include
import com.pi4j.io.gpio.digital.Digital;
import com.pi4j.io.gpio.digital.DigitalInput;
import com.pi4j.io.gpio.digital.DigitalOutput;
import com.pi4j.io.gpio.digital.DigitalState;
var ledConfig = DigitalOutput.newConfigBuilder(pi4j)
.id("my-dout")
.name("My LED")
.address(18)
.shutdown(DigitalState.LOW)
.initial(DigitalState.HIGH);
    var led = pi4j.create(ledConfig);

    logger.info("pin detail " + led);

When executed.
[main] INFO com.pi4j.test.devices.dht22.GpioTest - pin detail @my-dout "My LED" (#18)
Maybe we are not trying this the same way, can you give more details ?

Also. with 2.6.0-SNAPSHOT  from my POM file            Note pi4j-v2-devices is mine and not required by you.                                                                                .

com.pi4j
pi4j-v2-devices
0.0.1

com.pi4j
pi4j-core
${pi4j.version}

com.pi4j
pi4j-plugin-gpiod
${pi4j.version}

com.pi4j
pi4j-plugin-pigpio
${pi4j.version}

org.slf4j
slf4j-api
${slf4j.version}

org.slf4j
slf4j-simple
${slf4j.version}

com.pi4j
pi4j-plugin-linuxfs
${pi4j.version}

IDE: intellij IDEA
Build tool: Gradle 7.2
JVM: 17.0.2

Steps to reproduce:

Create a new Gradle project
Include the following dependencies:

dependencies {
    api group: 'com.pi4j', name: 'pi4j-core', version: '2.6.0'
    api group: 'com.pi4j', name: 'pi4j-plugin-raspberrypi', version: '2.6.0'
    api group: 'com.pi4j', name: 'pi4j-plugin-pigpio', version: '2.6.0'
}

Try to import DigitalState: import com.pi4j.io.gpio.digital.DigitalState;
An error is thrown: "Cannot resolve symbol 'DigitalState'"

It seems that small subset of the files inside the 'pi4j-core' JAR are compiled.
Here is a partial list of them: Parity, StopBits, DataBits, FlowControl, DigitalState, PullResistance ...
These files cannot be imported.
--- minimal test case ---

I followed Pi4J website > Getting started with Pi4J > Minimal example application.
Had intellij open this trusted.
This example had been updated for 2.6.0-SNAPSHOT and newer providers. So I edited it match your details.
diff --git a/build.gradle b/build.gradl
dependencies {
implementation 'org.slf4j:slf4j-api:2.0.12'
implementation 'org.slf4j:slf4j-simple:2.0.12'

implementation 'com.pi4j:pi4j-core:2.5.1'
implementation 'com.pi4j:pi4j-plugin-raspberrypi:2.5.1'
implementation 'com.pi4j:pi4j-plugin-gpiod:2.5.1'

implementation 'com.pi4j:pi4j-core:2.6.0'
implementation 'com.pi4j:pi4j-plugin-raspberrypi:2.6.0'
implementation 'com.pi4j:pi4j-plugin-pigpio:2.6.0'
}

diff --git a/pom.xml b/pom.xml
index 89238d1..c9b6f4f 100644
--- a/pom.xml
+++ b/pom.xml
@@ -70,7 +70,7 @@

com.pi4j

       <artifactId>pi4j-plugin-gpiod</artifactId>

       <artifactId>pi4j-plugin-pigpio</artifactId>
       <version>${pi4j.version}</version>
   </dependency>

b/src/main/java/module-info.javamodule com.pi4j.example {
// Pi4J MODULES
requires com.pi4j;

requires com.pi4j.plugin.gpiod;

requires com.pi4j.plugin.pigpio;
// SLF4J MODULES
requires org.slf4j;

The import works and the use of DigitalState is good.
When I try to build this ‘sudo ./gradlew build’   I hit an error  General error during semantic analysis: Unsupported class file major version 65.  I have not looked into this but hopefully something specific to my environment.
But I do not see your error.   I am using a new java, as long as you are java 11 or newer that should not be the problem, and at least gradle 6.6
openjdk version "21.0.3" 2024-04-16 LTS
./gradlew -version

Gradle 6.6

FYI, minimal example is now bumped to 2.6.0

After a lot of testing, it appears to be a bug in IntelliJ IDEA & Gradle and not in Pi4Jv2.
Upgrading to the latest releases (2024.1 & 8.7 respectively) resolve this issue.


[TASK] [v1.2.x] High integration test failure rate using nfs as backupstore

What's the task? Please describe
High integration test failure rate using nfs as backupstore
Describe the items of the task (DoD, definition of done) you'd like

[x] investigate and fix the high failure rate on v1.2.x integration test when using nfs as backupstore.

Additional context
Ref:

https://ci.longhorn.io/job/public/job/v1.2.x/job/v1.2.x-lh-tests-ubuntu-amd64/66/
https://ci.longhorn.io/job/public/job/v1.2.x/job/v1.2.x-lh-tests-ubuntu-arm64/

We've updated our integration test, I've run a new job to verify the problem still exits
https://ci.longhorn.io/job/public/job/master/job/ubuntu/job/amd64/job/longhorn-tests-ubuntu-amd64/562/

Tested on latest master:  SLES 15-sp3-v20210622
https://ci.longhorn.io/job/public/job/v1.2.x/job/v1.2.x-longhorn-tests-sles-amd64/7/


⚠ Bofrost.be has degraded performance

In 0b8937c, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1204 ms

Resolved: Bofrost.be performance has improved in 751cad9 after 306 days, 15 hours, 34 minutes.


Azure AI Custom Image Analysis model not returning performance metrics

Please provide us with the following information:

This issue is for a: (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce
Trained and working Azure AI Custom Image Analysis model.
Any log messages given by the failure
Status: Error(code={'code': 'InternalServerError', 'message': 'Batch did not complete successfully. OutputResultWriteFailed: An unexpected error was encountered.'}, message='', target='', details=[])
Expected/desired behavior
The following code from this guideline - https://github.com/Azure-Samples/cognitive-service-vision-model-customization-python-samples/blob/main/docs/cognitive_service_vision_model_customization.ipynb - do not return any performance metrics.
from cognitive_service_vision_model_customization_python_samples import Evaluation
eval_dataset_name = '{specify_your_eval_dataset_name}'
evaluation_name = '{specify_your_eval_run_name}'

evaluation = Evaluation(evaluation_name, model_name, eval_dataset_name)
training_client.evaluate_model(evaluation)

evaluation = training_client.wait_for_evaluation_completion(model_name, evaluation_name)

OS and Version?

Windows 10

Versions

Mention any other details that might be useful
I've created a question in the Q&A section of Microsoft - https://learn.microsoft.com/en-us/answers/questions/1880298/azure-ai-custom-image-analysis-model-not-returning?page=1&orderby=helpful&comment=answer-1665959. However the community couldn't help.

Thanks! We'll be in touch soon.

Hi @yvonnebarthp @karolzak and @yvonnebarth do you have any update on this issue?

Hi @chanezon is there any progress over this issue?


SAR-8697 Update CYA and business registration

please have a look to https://jira.tools.tax.service.gov.uk/browse/SAR-8697 ... I added some comment I hope will explain the philosophy of the new code .

Richard .... verify by default check for 1 times ....   (..it seems I cannot comment on a singular suggestion any more once I close the conversation .... )
@CheckReturnValue
public static  T verify(T mock) {
return MOCKITO_CORE.verify(mock, times(1));
}

to be honest the one thing that I will change is putting this:
if (optNino.isEmpty && !isEnabled(EnableOptionalNinoJourney))
throw new IllegalStateException(s"This cannot be because Nino is empty and EnableOptionalNinoJourney is false")
check at the begin of the submit method .... so we check immediately if something is screwed already before doing anything else ....... but the presence of this EnableOptionalNinoJourney in this file it doesnt convince me at all ..... anyway .... just a thought

Richard Line 237 it is not new code .... I am keen to double check it .... but if we start to check code that we did not write and  I cannot see the end ..... let's talk after standup

Richard you can verify any method .... you dont have to configure it if it doesnt return anything ..... I am just verifying that auditService.auditSoleTraderJourney(journeyId) has been called

Milly I could but I think is misleading ..... let's talk after the standup

Richard I removed that useless statement


How to detect that the cursor is on the input field of files, history, ... etc.?

As title.

Not sure what you're trying to achieve, try :help nvim_win_get_cursor and :help nvim_list_wins().

Not sure what you're trying to achieve, try :help nvim_win_get_cursor and :help nvim_list_wins().

I want to change the current working directory only when the cursor is not on the floating window/terminal of fzf-lua.

I would recommend using an autocmd instead and checking the window is either floating window or that it's filetype=fzf.

Sorry for my vague question. I just resolved this problem: A plugin I created has a bug related to another plugin called FTerm.nvim. And I was detecting vim.opt.filetype while the correct one should be vim.bo.filetype. And that filetype=fzf is helpful for me in the future debugging.

For future readers:
I just encountered this hours ago to fix a plugin. You can use vim.api.nvim_win_get_config(0).relative == "" to check that it is NOT a floating window.


[WIP] Linking of Middleware with VMs

Purpose or Intent
This PR introduces the lives_on to Middleware. Hawkular exposes the /etc/machine-id on its feeds and we use this value to lookup for an existing managed VM on other providers. If a VM with a matching Machine ID is found, lives_on is populated with data from this VM.
This allows for a later UI navigation between Cloud <-> Hypervisor <-> VM <-> Middleware.
Steps for Testing/QA
Set RHEV-M with one Hypervisor and one VM
Add this RHEV-M to MiQ
Install Hawkular Services into the VM
Add this Hawkular instance to MiQ
Check that the lives_on for the Hawkular record is populated with data from the VM on the Hypervisor

This PR is still a work in progress.

@miq-bot add_label wip providers/hawkular

@miq-bot add_label wip , providers/hawkular

@jpkrohling I am taking this PR and will work on adding on top of it UI representation (in a separate commit and PR)

please address rubocop comments, it will be hard to get it merged with the current amount of warnings.

@miq-bot add_label enhancement

gem changes label is irrelevant here, as the gem upgrade should not be part of this PR (it gives here a false alert to miq build team)

Some of the rubocop warnings are related to the PR this work is based on. The ones directly related to this PR will be fixed.

btw, @Jiri-Kremser is working now on upgrading miq to hawkular gem 2.0, this PR is based on 1.0, so definitely worth to align and make sure it works with 2.x instead.

This last version is different from the previous ones as it has a different processing for the alternate machine ID. It should be now easier to understand and read the code.

I think you should be rebasing on top of #9299

Ok, wish me luck :)

@miq-bot rm_label "gem changes"

@chessbyte @Fryguy @blomquisg  how can I remove "gem changes" label via the bot?
it doesn't work at the moment
the label is not relevant as the commit with the gem change will go away, it's just for the wip.

@miq-bot rm_label gem changes

Status for this PR: the code was tested via rails console.
Setup:

Hawkular Server under ID 4
VM

irb(main):002:0> hawkular_torii = ExtManagementSystem.find_by_id(4)
=> #<ManageIQ::Providers::Hawkular::MiddlewareManager id: 4, name: "Hawkular @ Hypervisor", created_on: "2016-06-20 15:35:16", updated_on: "2016-06-21 13:05:36", guid: "96a03d0c-36fc-11e6-92b5-3c970e9648d7", zone_id: 1, type: "ManageIQ::Providers::Hawkular::MiddlewareManager", api_version: nil, uid_ems: nil, host_default_vnc_port_start: nil, host_default_vnc_port_end: nil, provider_region: nil, last_refresh_error: nil, last_refresh_date: "2016-06-21 13:05:36", provider_id: nil, realm: nil, tenant_id: 1, project: nil, parent_ems_id: nil, subscription: nil>
irb(main):005:0> EmsRefresh.refresh hawkular_torii
...
...
   FROM "middleware_servers" WHERE "middleware_servers"."id" = $1 LIMIT $2  [["id", 3], ["LIMIT", 1]]
  MiddlewareServer Inst Including Associations (0.1ms - 1rows)
  ManageIQ::Providers::Redhat::InfraManager::Vm Load (1.6ms)  SELECT  "vms".* FROM "vms" WHERE "vms"."template" = $1 AND "vms"."type" IN ('ManageIQ::Providers::Redhat::InfraManager::Vm') AND "vms"."id" = $2 LIMIT $3  [["template", false], ["id", 1], ["LIMIT", 1]]
  ManageIQ::Providers::Redhat::InfraManager::Vm Inst Including Associations (0.7ms - 1rows)
=> #<ManageIQ::Providers::Redhat::InfraManager::Vm id: 1, vendor: "redhat", format: nil, version: nil, name: "hawkular", description: nil, location: "33d1682f-bca4-4b4c-b19e-cb47d344746c.ovf", config_xml: nil, autostart: nil, host_id: 1, last_sync_on: nil, created_on: "2016-06-17 07:51:49", updated_on: "2016-06-17 07:51:49", storage_id: 2, guid: "58a6552a-3460-11e6-905f-3c970e9648d7", ems_id: 3, last_scan_on: nil, last_scan_attempt_on: nil, uid_ems: "33d1682f-bca4-4b4c-b19e-cb47d344746c", retires_on: nil, retired: nil, boot_time: "2016-06-15 18:10:32", tools_status: nil, standby_action: nil, power_state: "on", state_changed_on: "2016-06-17 07:51:48", previous_state: nil, connection_state: "connected", last_perf_capture_on: nil, registered: nil, busy: nil, smart: nil, memory_reserve: nil, memory_reserve_expand: nil, memory_limit: nil, memory_shares: nil, memory_shares_level: nil, cpu_reserve: nil, cpu_reserve_expand: nil, cpu_limit: nil, cpu_shares: nil, cpu_shares_level: nil, cpu_affinity: nil, ems_created_on: nil, template: false, evm_owner_id: nil, ems_ref_obj: "--- \"/api/vms/33d1682f-bca4-4b4c-b19e-cb47d344746c...", miq_group_id: 1, linked_clone: nil, fault_tolerance: nil, type: "ManageIQ::Providers::Redhat::InfraManager::Vm", ems_ref: "/api/vms/33d1682f-bca4-4b4c-b19e-cb47d344746c", ems_cluster_id: 1, retirement_warn: nil, retirement_last_warn: nil, vnc_port: nil, flavor_id: nil, availability_zone_id: nil, cloud: false, retirement_state: nil, cloud_network_id: nil, cloud_subnet_id: nil, cloud_tenant_id: nil, raw_power_state: "up", publicly_available: nil, orchestration_stack_id: nil, retirement_requester: nil, tenant_id: 1, resource_group_id: nil, deprecated: nil>

And this shows the alternate_machine_id in action:
  Vm Load (1.2ms)  SELECT  "vms".* FROM "vms" WHERE "vms"."type" IN ('Vm', 'ManageIQ::Providers::InfraManager::Vm', 'ManageIQ::Providers::CloudManager::Vm', 'VmServer', 'ManageIQ::Providers::Vmware::InfraManager::Vm', 'ManageIQ::Providers::Microsoft::InfraManager::Vm', 'ManageIQ::Providers::Redhat::InfraManager::Vm', 'VmXen', 'ManageIQ::Providers::Google::CloudManager::Vm', 'ManageIQ::Providers::Azure::CloudManager::Vm', 'ManageIQ::Providers::Amazon::CloudManager::Vm', 'ManageIQ::Providers::Openstack::CloudManager::Vm') AND "vms"."template" = $1 AND "vms"."uid_ems" = $2 AND "vms"."type" = $3 LIMIT $4  [["template", false], ["uid_ems", "2f68d133a4bc4c4bb19ecb47d344746c"], ["type", "ManageIQ::Providers::Redhat::InfraManager::Vm"], ["LIMIT", 1]]
  Vm Inst Including Associations (0.0ms - 0rows)
  Vm Load (0.5ms)  SELECT  "vms".* FROM "vms" WHERE "vms"."type" IN ('Vm', 'ManageIQ::Providers::InfraManager::Vm', 'ManageIQ::Providers::CloudManager::Vm', 'VmServer', 'ManageIQ::Providers::Vmware::InfraManager::Vm', 'ManageIQ::Providers::Microsoft::InfraManager::Vm', 'ManageIQ::Providers::Redhat::InfraManager::Vm', 'VmXen', 'ManageIQ::Providers::Google::CloudManager::Vm', 'ManageIQ::Providers::Azure::CloudManager::Vm', 'ManageIQ::Providers::Amazon::CloudManager::Vm', 'ManageIQ::Providers::Openstack::CloudManager::Vm') AND "vms"."template" = $1 AND "vms"."uid_ems" = $2 AND "vms"."type" = $3 LIMIT $4  [["template", false], ["uid_ems", "33d1682f-bca4-4b4c-b19e-cb47d344746c"], ["type", "ManageIQ::Providers::Redhat::InfraManager::Vm"], ["LIMIT", 1]]
  Vm Inst Including Associations (846.1ms - 1rows)

fantastic!

since #9299 was merged, you can rebase to have a neat PR with just your changes :smile:

btw, in all the examples above from rails console where find_by_id(id) is used, find(id) works as well - this is the default to do 'by id'. For other properties (name, addr, host...) there's a need to specify the 'by' part.

@miq-bot rm_label gem changes

@abonas why did you remove the "gem changes" label?  This has contains a change to the Gemfile.

@blomquisg This PR was based on another one, which had gem changes. As that was merged already, I just rebased this PR and should not appear to have any gem changes anymore.

@jpkrohling there are several test failures on Travis, please address them.
After that, I think that wip can be removed from this PR.
@durandom thank you for the thorough review!

@miq-bot rm_label wip

@jpkrohling If you change the migration to a change and t.references :lives_on, :type => :bigint I'm good with how this is. Nice work!
The references is better, because it adds an index as well

@blomquisg @durandom looks like it's good to go - merge please?

LGTM :+1: @blomquisg merge?


Use new TextBuffer LanguageMode API

Depends on https://github.com/atom/text-buffer/pull/260
This is a continuation of work started in https://github.com/atom/atom/pull/15713, with the overall goal of allowing Atom to use parsing systems other than TextMate grammars.
One Language Per Buffer
The main user-facing change introduced in this PR is that language modes (previously called TokenizedBuffers) now belong to a TextBuffer, not an individual TextEditor. This means that if have you have a file open in 3 different tabs, the file will only be parsed once instead of 3 times for the purpose of syntax highlighting. It also means that when you select a language for the file using the grammar selector, your choice will apply in all 3 places.
TextEditor API Changes
Previously, the way to configure an editor's language was to assign to the editor a TextMate Grammar, and the editor would internally construct a TokenizedBuffer which would use the first-mate APIs to parse the buffer.
Now, the TextEditor class is no longer responsible for constructing its parser directly; it relies on the buffer having a language mode which provides information about syntax highlighting, folding, commenting, and suggested indentation.
This means that the .getGrammar and .setGrammar methods don't really make sense any more, and neither does the grammar parameter to the TextEditor constructor. These APIs will continue to work for backwards-compatibility, but will be deprecated at some point.
Other API Changes
Other language-related APIs like TextEditorRegistry.setGrammarOverride were designed around the TextMate concept of scope names - strings like source.js that are intended to fit into TextMate's scope selector system. Though scope selectors will continue to be a concept in Atom, we will no longer assume that these selectors use the TextMate-style naming conventions. Where possible, we will identify languages by their common name, instead of assuming that they have a special scope name that is different from their regular name.
Since TextEditors no longer construct their own language modes, I've moved this functionality into the existing GrammarRegistry object exposed as atom.grammars. It is implemented in the following methods:

atom.grammars.assignLanguageMode(buffer, languageId) - Assign the buffer a language mode that uses the language with the given id. For textmate grammars, we use the scopeName (e.g. source.js) as an ID. Tree-sitter grammars will have different looking ids (probably just javascript, go, etc).

atom.grammars.autoAssignLanguageMode(buffer) - Assign the buffer a language mode that uses the most appropriate language, based on the buffer's file extension and content.

atom.grammars.maintainLanguageMode(buffer) - Assign the buffer a language mode and continue to update the language mode as additional language packages are loaded, or the buffer's file path changes.

The TextEditorRegistry is no longer responsible for anything to do with grammars. The grammar-related methods will continue to work but they will be deprecated sometime soon.
Remaining Tasks

[ ] Rename TokenizedBuffer to TextMateLanguageMode
[ ] Track visibility correctly when a language mode is used by multiple editors

Next Steps
It should now be possible to integrate Tree-sitter parsers into Atom just by changing the GrammarRegistry and the PackageManager. The core editor no longer assumes anything about how its parser works. Once this is merged, I will begin doing this.

😓  Finally ✅  .

/cc @atom/maintainers - Curious if anyone has thoughts or opinions on the API changes described above (assignLanguageMode, autoAssignLanguageMode, maintainLanguageMode). Reasonable? Confusing?

Where possible, we will identify languages by their common name, instead of assuming that they have a special scope name that is different from their regular name.

@Alhadis @lierdakil this change would mean that any TextMate grammars that are assigned programmatically are required to have a name value, even if they generally shouldn't be user-selectable.  One example is the JS regexp grammars that are used for the find-and-replace fields.  Do you have any concerns with that change?  Since I think it makes sense to set grammars based on their names rather than the internal Grammar instances, I can potentially see a new hidden property or something similar being added to TextMate grammars that need names but should still be hidden from the Grammar Selector.

I'm fine with having a hidden property if that's what it takes.
I'm more concerned with the usage of a human-readable identifier instead of a scopeName property to uniquely identify a grammar instance...

I'm more concerned with the usage of a human-readable identifier instead of a scopeName property to uniquely identify a grammar instance...

It's definitely a fairly major change. My problem with the current paradigm is that the current concept of scope names is kind of TextMate-specific. With most parsing systems, syntax tree nodes aren't named in this hierarchical scheme like entity.name.type.object.console.js. They just have a single name like identifier. Similarly, programming languages are usually identified using their name, like ruby or javascript; strings like source.ruby and source.js are not particularly familiar to most people, and they're consistent with each other (should the name be abbreviated or not?).
Practically speaking, I think grammars' names should be just as unique as their scopeName, the only issue that I can think of with using them is that the letter casing might not be obvious (C++ vs c++, JavaScript vs javascript), but I think that should be addressed by treating the names as case-insensitive.

My approach would be to introduce a new field simply called id. If not specified, it's derived from the existing scopeName, with the source. and text. prefixes hacked off: .source.js ⇒ js
Non-alphanumeric characters are replaced with dashes, so that .source.js.rails becomes js-rails instead.

The word id (identifier) is pretty much a synonym of the word name, so I feel like that would just add to the confusion. There would then be three ways of referring to a grammar:
id: "ruby"
name: "Ruby"
scopeName: "source.ruby"

Can you elaborate on what concrete problem you're seeing with using the grammar's name to identify it?

The internal property seems reasonable to me. Should we also have the grammar selector exclude grammars that have injection selectors?

If a package author changes the name of a grammar, wouldn't that invalidate any serialised overrides or user config settings which reference the old name? Say, for example, an author decided to change "Fortran - Fixed Form" to "Fortran (Fixed form)" or even "FORTRAN77". There's less risk of this happening with an internal identifier, because authors have no incentive to change it. Human-readable identifiers, however, are more vulnerable to bikeshed-ish changes.

I also wouldn't filter out grammars simply because they contain an injectionSelector field. See atom/language-gfm#175.

We could go with same process as the atom config.  i.e. the name is "fortranFixedForm" and if you want to later change how it's automatically reformatted for display then you use the optional title field to set it to "Fortran (Fixed Form)"

Possibly, but that still wouldn't address something like, say, Batchfile script -> Batchfile (if an author later decides the "script" part is extraneous. Or something like abbreviating a name the author later decides is too lengthy and looks better in a contracted form...

Ideally, it'd be great if identifiers matched whatever followed language- in the names of Atom's core language packages. E.g., language-gfm is gfm instead of GitHub-flavoured Markdown, et al.
I'm all for having a SSOT, and I'm all for getting rid of the weird, nonsensical scope-name conventions used by TextMate (which have never made sense to me; the source./text. inconsistencies drive me nuts). So I'm certainly not protesting this PR... however, I sense we could go about this differently and promote the use of a single, explicit identifier to represent grammars internally.

strings like source.ruby and source.js are not particularly familiar to most people, and they're not even consistent with each other (should the name be abbreviated or not?)

Personally, the ID should match whatever is used as the last scope in a grammar's patterns. So for JavaScript, that would be js, because that's what's affixed to the scope-list of each successful match (keyword.operator.js, etc).

v1
name: batchfileScript

v2
name: batchfileScript
title: Batchfile

What am I missing?

There's less risk of this happening with an internal identifier, because authors have no incentive to change it.

I see your point. I guess name has taken on a certain usage pattern in the TextMate grammars because it's not used internally as an identifier in existing systems.

I guess name has taken on a certain usage pattern in the TextMate grammars because it's not used internally as an identifier in existing systems.

Even that's inconsistent, though. The same field-name is used for describing the scopes of successful matches. E.g., the name property of a patterns entry is semantically different to the name field used by the grammar itself.
It's all a horrid mess, in all honesty...

@Alhadis @damieng @50Wliu I've updated the PR to remove the use of language names in assignLanguageMode. The method now takes a parameter called languageId. For TextMate grammars, this will just be the scopeName, so that grammars will continue to be identified primarily by their scopeName as before.
Tree-sitter grammars will have their ids that will look a bit different: javascript, ruby, c++.

LGTM.


Fix a typo: poxy should be proxy

a small typo
adjust comment format

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@ChenglongGao327: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
d334c3d7e3eb7bd0bc7d29666f7429b0485b556e
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ChenglongGao327: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
d334c3d7e3eb7bd0bc7d29666f7429b0485b556e
link
/test release-notes_istio

lint_istio
d334c3d7e3eb7bd0bc7d29666f7429b0485b556e
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Hotfix null path

Executor refactored
Utils_executor.4c file created to contain auxiliar files
Added protection for NULL strings on ft_split and ft_free_arr
has_absolute_path function refactored
Added stat function to check if the binary is a directory
No leaks when 'PATH' var is unseted and a command is ran

Fixed #109
Fixed #86


Create a login feature for our users (legal clinics)

What: a log-in feature
Why: so that we can track their usage
How: Option 1) https://developers.google.com/identity/protocols/OpenIDConnect 2) connect it to Web Amazon database

being worked on. Let me know if you want to join.


libquotient: 0.6.2 -> 0.6.3

Motivation for this change
Upstream update but adding on a few minor changes:

fix neochat's version tag
add maintainer to neochat (@mjlbach - I didn't want to just add you without your consent)
upgrade quaternion to the latest beta. Yes, we normally don't do that but:
it is needed to compile against libquotient v0.6+
quaternion is still a young product without a stable v1.0 release so this version isn't necessarily any less stable than the previous
I have been using the beta2 version since release without any issues

Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[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.

@GrahamcOfBorg build neochat quaternion

1 and 2 look good to me!  I haven't used quaternion for a large extent of time, so I can't comment on that. Happy to also be added/help maintain neochat (I haven't added myself to the master maintainers list yet though).

Thanks for the feedback and welcome onboard!
I suggest you open a PR with 2 commits - one adding yourself to the maintainer list and the other adding yourself to neochat (I suggest you add yourself to the head of the list as you were the one who got it up and running).


[opencv4] Build error with feature cuda

Host Environment

OS: Windows 10 21H2
Compiler: Visual Studio 2022 cl v19.31.31104

To Reproduce
Steps to reproduce the behavior:
 .\vcpkg.exe install opencv4[contrib,cuda]  --recurse
Failure logs
Computing installation plan...
The following packages will be built and installed:
opencv4[contrib,core,cuda,default-features,dnn,jpeg,png,quirc,tiff,webp]:x86-windows -> 4.5.5
Detecting compiler hash for triplet x86-windows...
-- Automatically setting HTTP(S)_PROXY environment variables to <IP_ADDRESS>:8889
Restored 0 packages from C:\Users\shuchin\AppData\Local\vcpkg\archives in 232.3 us. Use --debug to see more details.
Starting package 1/1: opencv4:x86-windows
Building package opencv4[contrib,core,cuda,default-features,dnn,jpeg,png,quirc,tiff,webp]:x86-windows...
-- Using cached opencv-opencv-4.5.5.tar.gz.
-- Cleaning sources at C:/tools/vcpkg/buildtrees/opencv4/src/4.5.5-f2b5f31c0d.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/tools/vcpkg/downloads/opencv-opencv-4.5.5.tar.gz
-- Applying patch 0001-disable-downloading.patch
-- Applying patch 0002-install-options.patch
-- Applying patch 0003-force-package-requirements.patch
-- Applying patch 0004-fix-policy-CMP0057.patch
-- Applying patch 0005-fix-eigen.patch
-- Applying patch 0006-fix-uwp.patch
-- Applying patch 0008-devendor-quirc.patch
-- Applying patch 0009-fix-protobuf.patch
-- Applying patch 0010-fix-uwp-tiff-imgcodecs.patch
-- Applying patch 0011-remove-python2.patch
-- Applying patch 0012-fix-zlib.patch
-- Applying patch 0013-fix-opengl.patch
-- Applying patch 0014-fix-gstreamer.patch
-- Applying patch 0015-fix-freetype.patch
-- Using source at C:/tools/vcpkg/buildtrees/opencv4/src/4.5.5-f2b5f31c0d.clean
-- Using cached opencv-cache/tiny_dnn/adb1c512e09ca2c7a6faef36f9c53e59-v1.0.0a3.tar.gz.
-- Using cached opencv-cache/nvidia_optical_flow/a73cd48b18dcc0cc8933b30796074191-edb50da3cf849840d680249aa6dbef248ebce2ca.zip.
-- Using cached opencv-opencv_contrib-4.5.5.tar.gz.
-- Cleaning sources at C:/tools/vcpkg/buildtrees/opencv4/src/4.5.5-c35cb8696d.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/tools/vcpkg/downloads/opencv-opencv_contrib-4.5.5.tar.gz
-- Applying patch 0007-fix-hdf5.patch
-- Applying patch 0016-fix-freetype-contrib.patch
-- Using source at C:/tools/vcpkg/buildtrees/opencv4/src/4.5.5-c35cb8696d.clean
-- Using cached opencv-cache/wechat_qrcode/238e2b2d6f3c18d6c3a30de0c31e23cf-detect.caffemodel.
-- Using cached opencv-cache/wechat_qrcode/cbfcd60361a73beb8c583eea7e8e6664-sr.caffemodel.
-- Using cached opencv-cache/wechat_qrcode/6fb4976b32695f9f5c6305c19f12537d-detect.prototxt.
-- Using cached opencv-cache/wechat_qrcode/69db99927a70df953b471daaba03fbef-sr.prototxt.
-- Using cached opencv-cache/xfeatures2d/boostdesc/0ea90e7a8f3f7876d450e4149c97c74f-boostdesc_bgm.i.
-- Using cached opencv-cache/xfeatures2d/boostdesc/232c966b13651bd0e46a1497b0852191-boostdesc_bgm_bi.i.
-- Using cached opencv-cache/xfeatures2d/boostdesc/324426a24fa56ad9c5b8e3e0b3e5303e-boostdesc_bgm_hd.i.
-- Using cached opencv-cache/xfeatures2d/boostdesc/202e1b3e9fec871b04da31f7f016679f-boostdesc_binboost_064.i.
-- Using cached opencv-cache/xfeatures2d/boostdesc/98ea99d399965c03d555cef3ea502a0b-boostdesc_binboost_128.i.
-- Using cached opencv-cache/xfeatures2d/boostdesc/e6dcfa9f647779eb1ce446a8d759b6ea-boostdesc_binboost_256.i.
-- Using cached opencv-cache/xfeatures2d/boostdesc/0ae0675534aa318d9668f2a179c2a052-boostdesc_lbgm.i.
-- Using cached opencv-cache/xfeatures2d/vgg/e8d0dcd54d1bcfdc29203d011a797179-vgg_generated_48.i.
-- Using cached opencv-cache/xfeatures2d/vgg/7126a5d9a8884ebca5aea5d63d677225-vgg_generated_64.i.
-- Using cached opencv-cache/xfeatures2d/vgg/7cd47228edec52b6d82f46511af325c5-vgg_generated_80.i.
-- Using cached opencv-cache/xfeatures2d/vgg/151805e03568c9f490a5e3a872777b75-vgg_generated_120.i.
-- Using cached opencv-cache/data/7505c44ca4eb54b4ab1e4777cb96ac05-face_landmark_model.dat.
-- Found external ninja('1.10.2').
-- Configuring x86-windows
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:128 (message):
Command failed: ninja -v
Working Directory: C:/tools/vcpkg/buildtrees/opencv4/x86-windows-rel/vcpkg-parallel-configure
Error code: 1
See logs for more information:
C:\tools\vcpkg\buildtrees\opencv4\config-x86-windows-out.log
Call Stack (most recent call first):
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake:415 (vcpkg_execute_required_process)
ports/opencv4/portfile.cmake:402 (vcpkg_cmake_configure)
scripts/ports.cmake:145 (include)
Error: Building package opencv4:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with git pull and .\vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+opencv4
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[opencv4]+Build+error
including:
package: opencv4[contrib,core,cuda,default-features,dnn,jpeg,png,quirc,tiff,webp]:x86-windows -> 4.5.5
vcpkg-tool version: 2022-03-09-1affd32f93b299d5a907816c328ca3ededb73a7e
vcpkg-scripts version: 773516ecf 2022-03-28 (14 hours ago)
Additionally, attach any relevant sections from the log files above.
Additional context
config-x86-windows-out.log
sue.

I find a similar issue: https://github.com/opencv/opencv_contrib/issues/1478, there a solution on this issue: https://stackoverflow.com/questions/46584000/cmake-error-variables-are-set-to-notfound
I can't confirm this issue is a port bug or upstream issue. cc @cenit Could you help confirm this issue? Thanks in advance.

CUDA_nppi_LIBRARY has been deprecated from cuda and that was a problem back in the days. Your linked issue @LilyWangLL is not valid unfortunately. Here library is a different one and maybe it has been omitted from installation.
For original poster issue, i'd say that the main issue is a broken cuda installation. First error is when detecting cuda version at the beginning of the cmake run, where it says that it has found version 11.6 but it's missing native archs...

CUDA_nppi_LIBRARY has been deprecated from cuda and that was a problem back in the days. Your linked issue @LilyWangLL is not valid unfortunately. Here library is a different one and maybe it has been omitted from installation. For original poster issue, i'd say that the main issue is a broken cuda installation. First error is when detecting cuda version at the beginning of the cmake run, where it says that it has found version 11.6 but it's missing native archs...

Thanks for your suggestion, it really works.  I changed the architecture of OpenCV to x64-Windows, and finally the compilation was successful.  I searched for this issue link and it seems to require setting additional environment variables to make CUDA work for programs compiled for x86 architecture.

there are no more cublas, cufft, npp etc libraries in 32bit version, so there is no way to build 32bit cuda-enabled opencv, sorry
we should add a support clause to cuda port, stating that it does not  support x86 anymore (cross-compiler from 64bit to 32bit is there, but libraries no more). In this way vcpkg would have told you that the request was impossible to satisfy because a dependency was missing

only other option is to downgrade cuda a lot (< v7 maybe?) and use that


Remove support for Ubuntu 8.04-9.04

Description
Removes support for Ubuntu distros that are EoL by the manufacturer and no longer supported by Chef
Issues Resolved
#361
Check List

[ ] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[x] The CLA has been signed. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

👍


How to make this reply only with the answer?

How to make this reply only with the answer?

Sorry.  Been trying a few things and it's already late at night and I didn't notice that I was asking for a joke which is typically a QnA type.

Ooppss, sorry, there it is! Where do I change thing template?  And I thought I don't have to think of how the prompt will be?

Even GPT4 is confused.
I have done a lot prompting in the past, so I thought I'll try DSPy to brute force prompting as I thought it would do ... but how it fails just for simple case like this?  Which part again that I don't need to think about the prompt itself?

Chat models require special treatment, if you aren't compiling your program.
Set dspy.configure(experimental=True) for this and let us know.

Fixed in DSPy 2.5 if you follow the migration guide!


DQ - fix issues with lambda generation and introduce DQ test framework

What type of PR is this?
Improvement/Bug Fix
What does this PR do / why is it needed ?

Which issue(s) this PR fixes:

Fixes #
Other notes for reviewers:
Does this PR introduce a user-facing change?

This PR was closed because it has been inactive for 35 days. Please re-open if this PR is still relevant.


Cancel payment - IOU is still marked as paid when payment is canceled unless report is revisited

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.16-3
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Issue found when executing PR https://github.com/Expensify/App/pull/32674
Action Performed:

[User A] Request money from User B
[User B] Click on IOU preview > Pay elsewhere
[User B] Click 3-dot menu > Cancel payment > Cancel payment

Expected Result:
On User A's end, the IOU preview will no longer be marked as paid when the payment is cancelled
Actual Result:
On User A's end, the IOU preview is still marked as paid unless the IOU report is revisited
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/223b5330-0e62-43dd-8083-5be7ff01f18b
View all open jobs on GitHub

Proposal
Please re-state the problem that we are trying to solve in this issue.
What is the root cause of that problem?
We do not update the iouReport.isCancelledIOU: true optimistically when canceling the payment.
What changes do you think we should make in order to solve the problem?
When canceling the payment, we should optimistically set iouReport.isCancelledIOU: true.
What alternative solutions did you explore? (Optional)

Reverting the original PR because it has caused numerous deploy blockers and the author is ooo

PR reverted, Assigning @Gonals so you can track this issue and fix it in next iteration

Setting it as monthly, as this is no longer happening (but I want it to keep track)


integration

takes #2 and makes it usable for integration.
also going to include some simple ACDC/KERI parsing logic in the README.

Overall poor coverage and I'd wager there is a bunch of broken code here but it's a good starting point, and I successfully integrated a basic KERI/ACDC use case with this branch, I'll post results in a comment from my work account.

>>> quisdk.ingest_messages(prefix, messages, deep=True)
succesfully verified key event [EA_1ZGv4tEhJW2AYH0wLh2lLlllmH3dwpH3RGs2GtgXr, EA_1ZGv4tEhJW2AYH0wLh2lLlllmH3dwpH3RGs2GtgXr]
succesfully verified key event [EA_1ZGv4tEhJW2AYH0wLh2lLlllmH3dwpH3RGs2GtgXr, EA_1ZGv4tEhJW2AYH0wLh2lLlllmH3dwpH3RGs2GtgXr]
succesfully verified key event [EA_1ZGv4tEhJW2AYH0wLh2lLlllmH3dwpH3RGs2GtgXr, EC0M8M3Oxrpu63NQpqca5pkvyg1kDDl0D55OzvMjbumS]
succesfully verified key event [EA_1ZGv4tEhJW2AYH0wLh2lLlllmH3dwpH3RGs2GtgXr, EA_1ZGv4tEhJW2AYH0wLh2lLlllmH3dwpH3RGs2GtgXr]
succesfully verified key event [EA_1ZGv4tEhJW2AYH0wLh2lLlllmH3dwpH3RGs2GtgXr, EC0M8M3Oxrpu63NQpqca5pkvyg1kDDl0D55OzvMjbumS]
succesfully verified key event [EA_1ZGv4tEhJW2AYH0wLh2lLlllmH3dwpH3RGs2GtgXr, EAfqovhVb24y0pDcQDt8AAgK0p3eYFBRZlvZJj2TdpeA]
succesfully verified key event [EA_1ZGv4tEhJW2AYH0wLh2lLlllmH3dwpH3RGs2GtgXr, EA_1ZGv4tEhJW2AYH0wLh2lLlllmH3dwpH3RGs2GtgXr]
succesfully verified key event [EA_1ZGv4tEhJW2AYH0wLh2lLlllmH3dwpH3RGs2GtgXr, EC0M8M3Oxrpu63NQpqca5pkvyg1kDDl0D55OzvMjbumS]
succesfully verified transaction event [EN1cqKihWohl02O8IVXyZyO1W838SqWNbLeeMo8RS0VL, EN1cqKihWohl02O8IVXyZyO1W838SqWNbLeeMo8RS0VL]
succesfully verified key event [EA_1ZGv4tEhJW2AYH0wLh2lLlllmH3dwpH3RGs2GtgXr, EA_1ZGv4tEhJW2AYH0wLh2lLlllmH3dwpH3RGs2GtgXr]
succesfully verified key event [EA_1ZGv4tEhJW2AYH0wLh2lLlllmH3dwpH3RGs2GtgXr, EC0M8M3Oxrpu63NQpqca5pkvyg1kDDl0D55OzvMjbumS]
succesfully verified key event [EA_1ZGv4tEhJW2AYH0wLh2lLlllmH3dwpH3RGs2GtgXr, EAfqovhVb24y0pDcQDt8AAgK0p3eYFBRZlvZJj2TdpeA]
succesfully verified transaction event [EE_Wrv2OHqIOptEni3mE3Ckc4C6jO1RvgtxdpDZBiuB0, EMznaaxNbMwJUXEqOr5TYZIMCYSQowHAeMY-d7Uhu4Re]
succesfully verified acdc EE_Wrv2OHqIOptEni3mE3Ckc4C6jO1RvgtxdpDZBiuB0
succesfully verified key event [ENayINhHQnx6525EpcTmkvo6ZixiJyiskwkVNbMPohYa, ENayINhHQnx6525EpcTmkvo6ZixiJyiskwkVNbMPohYa]
succesfully verified key event [ENayINhHQnx6525EpcTmkvo6ZixiJyiskwkVNbMPohYa, ENayINhHQnx6525EpcTmkvo6ZixiJyiskwkVNbMPohYa]
succesfully verified key event [ENayINhHQnx6525EpcTmkvo6ZixiJyiskwkVNbMPohYa, EFCUFbl7Ybu3g3xpAOyAbkm7osM_OxFGFM9xVI7fz-B-]
succesfully verified key event [ENayINhHQnx6525EpcTmkvo6ZixiJyiskwkVNbMPohYa, ENayINhHQnx6525EpcTmkvo6ZixiJyiskwkVNbMPohYa]
succesfully verified key event [ENayINhHQnx6525EpcTmkvo6ZixiJyiskwkVNbMPohYa, EFCUFbl7Ybu3g3xpAOyAbkm7osM_OxFGFM9xVI7fz-B-]
succesfully verified key event [ENayINhHQnx6525EpcTmkvo6ZixiJyiskwkVNbMPohYa, EJWEtwi_KqBEPiyTceH8eZ8lw4jbPf1DMH5-AUYjA6hQ]
succesfully verified key event [ENayINhHQnx6525EpcTmkvo6ZixiJyiskwkVNbMPohYa, ENayINhHQnx6525EpcTmkvo6ZixiJyiskwkVNbMPohYa]
succesfully verified key event [ENayINhHQnx6525EpcTmkvo6ZixiJyiskwkVNbMPohYa, EFCUFbl7Ybu3g3xpAOyAbkm7osM_OxFGFM9xVI7fz-B-]
succesfully verified transaction event [EINZnO3Z30Q7y2oV1sDCQphieRH244-XJFRAbzuFbU7n, EINZnO3Z30Q7y2oV1sDCQphieRH244-XJFRAbzuFbU7n]
succesfully verified key event [ENayINhHQnx6525EpcTmkvo6ZixiJyiskwkVNbMPohYa, ENayINhHQnx6525EpcTmkvo6ZixiJyiskwkVNbMPohYa]
succesfully verified key event [ENayINhHQnx6525EpcTmkvo6ZixiJyiskwkVNbMPohYa, EFCUFbl7Ybu3g3xpAOyAbkm7osM_OxFGFM9xVI7fz-B-]
succesfully verified key event [ENayINhHQnx6525EpcTmkvo6ZixiJyiskwkVNbMPohYa, EJWEtwi_KqBEPiyTceH8eZ8lw4jbPf1DMH5-AUYjA6hQ]
succesfully verified transaction event [ENIcZJXSgLgz5whOszoME4DPe7B93Qltk6n6C6E9YxF2, EAu3kyuiOnHphq1Mx5T2LPXOzjSBRnWyMqOcq7qAjyHq]
succesfully verified acdc EE_Wrv2OHqIOptEni3mE3Ckc4C6jO1RvgtxdpDZBiuB0
succesfully verified acdc ENIcZJXSgLgz5whOszoME4DPe7B93Qltk6n6C6E9YxF2
>>> quisdk.ingest_messages(prefix, messages, deep=False)
succesfully verified key event [EA_1ZGv4tEhJW2AYH0wLh2lLlllmH3dwpH3RGs2GtgXr, EA_1ZGv4tEhJW2AYH0wLh2lLlllmH3dwpH3RGs2GtgXr]
succesfully verified key event [EA_1ZGv4tEhJW2AYH0wLh2lLlllmH3dwpH3RGs2GtgXr, EC0M8M3Oxrpu63NQpqca5pkvyg1kDDl0D55OzvMjbumS]
succesfully verified key event [EA_1ZGv4tEhJW2AYH0wLh2lLlllmH3dwpH3RGs2GtgXr, EAfqovhVb24y0pDcQDt8AAgK0p3eYFBRZlvZJj2TdpeA]
succesfully verified transaction event [EN1cqKihWohl02O8IVXyZyO1W838SqWNbLeeMo8RS0VL, EN1cqKihWohl02O8IVXyZyO1W838SqWNbLeeMo8RS0VL]
succesfully verified transaction event [EE_Wrv2OHqIOptEni3mE3Ckc4C6jO1RvgtxdpDZBiuB0, EMznaaxNbMwJUXEqOr5TYZIMCYSQowHAeMY-d7Uhu4Re]
succesfully verified acdc EE_Wrv2OHqIOptEni3mE3Ckc4C6jO1RvgtxdpDZBiuB0
succesfully verified key event [ENayINhHQnx6525EpcTmkvo6ZixiJyiskwkVNbMPohYa, ENayINhHQnx6525EpcTmkvo6ZixiJyiskwkVNbMPohYa]
succesfully verified key event [ENayINhHQnx6525EpcTmkvo6ZixiJyiskwkVNbMPohYa, EFCUFbl7Ybu3g3xpAOyAbkm7osM_OxFGFM9xVI7fz-B-]
succesfully verified key event [ENayINhHQnx6525EpcTmkvo6ZixiJyiskwkVNbMPohYa, EJWEtwi_KqBEPiyTceH8eZ8lw4jbPf1DMH5-AUYjA6hQ]
succesfully verified transaction event [EINZnO3Z30Q7y2oV1sDCQphieRH244-XJFRAbzuFbU7n, EINZnO3Z30Q7y2oV1sDCQphieRH244-XJFRAbzuFbU7n]
succesfully verified transaction event [ENIcZJXSgLgz5whOszoME4DPe7B93Qltk6n6C6E9YxF2, EAu3kyuiOnHphq1Mx5T2LPXOzjSBRnWyMqOcq7qAjyHq]
succesfully verified acdc ENIcZJXSgLgz5whOszoME4DPe7B93Qltk6n6C6E9YxF2


OnClickListener for ok and cancel buttons

Is there a way to set custom click listeners for the ok and cancel buttons?

Yes there is, and it is mentioned in the README.

What I meant was currently we have onDateSet call back which gets called when the user clicks "OK". What I wanted to ask was if we could attach our own listeners to the buttons such as Android has in the current AlertDialog specification i.e. builder.setPositiveButton(positiveText,
new DialogInterface.OnClickListener() {
@Override
public void onClick(DialogInterface dialog, int which) {
                        }
                    });

It seems as the positive and negavtive button clicks are locked to specific callbacks and not customisable. Hence the question.

Allow me to copy the relevant section from the README then
OnDismissListener and OnCancelListener
Both pickers can be passed a DialogInterface.OnDismissLisener or DialogInterface.OnCancelListener which allows you to run code when either of these events occur.
tpd.setOnCancelListener(new DialogInterface.OnCancelListener() {
    @Override
    public void onCancel(DialogInterface dialogInterface) {
      Log.d("TimePicker", "Dialog was cancelled");
    }
});

why dismiss also go to this method 'setOnCancelListener'

It shouldn't, and as far as I can see, it doesn't?


canceled typo?

Seems there is a typo at https://github.com/buildkite/agent/blob/1636d0eeeea7c7c66128a02784aecc7b4728cb7e/buildkite/job.go#L147, where cancelled os spelt canceled. This seems to be the only place, as everywhere else, the correct spelling is used.

Or perhaps this is intentional because the Buildkite API returns 'canceled'?

Yeah, it's what the Buildkite API returns, and apparently canceled is the preferred spelling in the US? I'm Australian, so when I write comments and variables, I tend to use our spelling.  ;)

I know right! It hurts every time I type "color" (it's supposed to be colour!!!)

Event Chrome knows I'm right! :)

Going to close this - but thanks for mentioning it! If you see anything else in the codebase that looks funky-town - feel free to open another issue :)


circle: Fix build renaming all image references

This commit fixes a regression introduced in 9d43b16, it renames
remaining references to thewtex images.

xref #146

+1 Thanks for the follow-up!


Achievements and/or badges

Feature Request
Desired behaviour
Achievements/badges for contributing tools, workflows, comments, labels, etc.

Collected in #827


[Ovmm] sim eval changes

Motivation and Context

Adds obstacles for continuous actions
Sim eval vectorized: eval on all episodes, subfolders for each subset
Heuristic pick policy for visualization
Visualization fixes
Update habitat-lab to object_rearrange

Changelog

How Has This Been Tested

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have made changes to existing documentation where needed.
[ ] I have added tests that show that the PR is functional.
[ ] I ran tests/hw_manual_test.py on hardware and observed that robot behavior looks normal.

Tested pick + place on my robot in lab and it seemed to work, so I think we're ok there


Integration Guides

As a developer, I want to have various integration guides, so that integrating ZITADEL with my system landscape is a no-brainer.

[x] #3041
[ ] Grafana
[ ] ArgoCD
[ ] NGINX

For role mapping in Grafana the following works assuming you created roles grafana_admin and grafana_editor (credits to dudeastic on Discord).
role_attribute_path=contains(keys("urn:zitadel:iam:org:project:roles"), 'grafana_admin') && 'Admin' || contains(keys("urn:zitadel:iam:org:project:roles"), 'grafana_editor') && 'Editor' || 'Viewer'


Why validation has to have 10 times repition of data?

Hello,
Great work. Can you tell me why there is 10 time repetition while validating?

It's Monte Carlo sampling. I've done it for testing and validation. To be completely honest, I have no clue if it's good practice to do so for the valudation set. I should probably ask around.


Debug V8

I tried to debug my javascript code executed by V8ScriptEngine. But when I tried to install Chromedevtools in Eclipse, the following error message appeared: "Could not find http://chromedevtools.googlecode.com/svn/update/dev/". Are there any other possibilty? Maybe in VS Code?

Ok, I tried in VS Code with Node Debugger and I could attach. It's not perfect, but it works :).

@balazsszekely Yes, unfortunately it looks like the Google Chrome Developer Tools package, deprecated for a while, has now been removed.
Newer V8 versions no longer support the corresponding protocol, which is why ClearScript still uses V8 5.5. We're hoping to support the new "V8 Inspector" protocol in the next release; in the meantime it's great to know that VS Code supports the original protocol. Thank you!

We've posted ClearScript 5.5. This release adds support for local and remote debugging via Inspector, enabling the use of Chrome DevTools and other JavaScript debuggers.

So I haven't been successful in getting Chrome's Inspector to attach to ClearScript, is there a guide somewhere detailing how to do it, so I can see where I messed up?

So I haven't been successful in getting Chrome's Inspector to attach to ClearScript, is there a guide somewhere detailing how to do it, so I can see where I messed up?

Sorry we missed your message last week. Were you able to resolve your issue?
If you've configured Chrome's Inspector page (chrome://inspect) to monitor the appropriate ports (ClearScript uses 9222 by default), active applications with V8 debugging enabled should appear on that page dynamically. Click the desired application to launch and attach Chrome's debugger.

No problem. I was able to figure it out. Don't remember what I did differently. I think I changed the port number that I was using.


docs: Improvements to the design document

This PR also moves some WIP sections to the extensions directory,

WDYT about adding some figures (either from the paper or made specifically for this doc)?

I suggest we add figures from the paper once that's live, if we're allowed to.


[RR Request]: JSON Crack v2.0.0

Open Source Project name
JSON Crack
What is your project?
JSON Crack (previously JSON Visio) is a visualization tool for JSON data, making developers lives easier to view and even for non-developers to understand data. Either type directly into the editor or import/fetch json from locally or URL!
Version
2.0
Date
August 27, 2022
Description of breaking changes
Since the v1 to v2, JSON Crack received following features:

Fetch JSON
Download File
Share Link
Settings
Copy/Download Graph
Search Nodes
Light Theme
Fullscreen View
VS Code's Monaco Editor
Expand/Collapse Nodes
JSON Validator

GitHub Repo
https://github.com/AykutSarac/jsonvisio.com
Website
https://jsoncrack.com/
Link to changelog
https://github.com/AykutSarac/jsonvisio.com/releases/tag/v2.0.0
Social media
https://twitter.com/aykutsarach/status/1563573958984667137
Anything else to add?
JSON Crack was known as JSON Visio previously and shared on GitHub's twitter https://twitter.com/github/status/1519363257794015233

Congrats on being featured in the August 2022 Release Radar 🥳

Read the blog here
Check out our GitHub Tweet
Feel free to retweet Mish's tweet featuring you
Keep an eye on our YouTube Channel for a August Release Radar promo video 😄


(typescript) Should this take a dependency on the LTS version?

Rather than the latest Node Version?
//cc @pascalberger @AdmiringWorm
This came up in this issue:
https://github.com/Microsoft/vsts-image-generation/issues/135#issuecomment-388804222

Yeah, I guess we probably should do that.
I actually wish there was a better way to handle these kind of dependencies though.
Oh well, maybe in the future.

@AdmiringWorm agreed, I think that this is an area that could be improved in the future, once package indexes and true meta packages exist, but for now, I think that changing the dependency makes the most sense.

I think that changing the dependency makes the most sense.

Working on it now


WebStorm IDE Autocompletion issue with "Accessible Members Up Top" Y052

I really like the readability afforded by putting the public members at the top. Especially for longer files. However, in WebStorm (which I guess a lot of us use), it seems to confuse the autocompletion engine:
Consider the "traditional" approach:
function myFactory() {
  function myMethod(arg) {
    //..
  }

  return {
    myMethod: myMethod
  };
}

When I am elsewhere in the project and type myFactory. - the IDE will provide solid autocomplete for the available method myMethod, along with any JSDocs I have defined above myMethod.

However, if we flip this around to put the public API up top:
function myFactory() {
  return {
    myMethod: myMethod
  };

  function myMethod(arg) {
    //..
  }
}

then WebStorm will no longer recognize myFactory.myMethod() as a function, and any JSDoc will have no effect.

This is actually a big disadvantage when it comes to large projects. Sure, with WebStorm you can click through a couple of times to get to the actual definition of myMethod, but you forego the advantages on in-place autocompletion with full documentation as you code.
There has been a similar discussion in https://github.com/johnpapa/angular-styleguide/issues/133, but this issue does not address the autocomplete issue specifically.

I have the same issue, although with VS2013/ReSharper. I suspect, though, that it's more of an issue with ReSharper and WebStorm than with the style guide.

Maybe, you want to check Jetbrains issues:
https://youtrack.jetbrains.com/issues/WI

Indeed it is a JetBrains issue. Partially fixed in WebStorm 10.0.4 and the EAP of PhpStorm 9, but not fully.
See the issue on the JetBrains bug tracker here: https://youtrack.jetbrains.com/issue/WEB-17022

Great!, i did a vote, to pull up the issue priority.

For those it might interest, I've created an issue for ReSharper too: https://youtrack.jetbrains.com/issue/RSRP-442304


Docs: Slack instead of irc

#8562 notes that we don't use irc anymore. Replacing with
the current Slack info.

Cherry-picked to v9.2.x

Cherry-picked to v9.1.x branch.


Provide better default margin model for GDAX cash accounts

READY TO BE REVIEWED/MERGED

NOTE: FractionalQuantityRegressionAlgorithm is failing due to recent changes in minimum order sizes. This PR has no ill effect on the regression suit.

GDAXBrokerageModel.GetMarginModel -> NonShortableCashAccountMarginModel
GDAX cash accounts aren't allowed to short and require sufficient quantity of quote currency
to purchase and sufficient quantity of base currency to sell. This model aims to enforce
these constraints
Add IBrokerageModel.GetMarginModel and invoke from BrokerageModelSecurityInitializer
It seems all the other models are being provided via the brokerage model but all the margin models
are assigned via the security constructors. This allows us to set margin models using the same
pattern that we used for overriding default margin models. This becomes particularly important
when considering how different exchanges/brokerages manage cash and margin in the account.
Add NonShortableCashAccountMarginModel
This margin model forces us to purchase everthing outright with cash.
This also means there's no maintenance margin. This also means that in order
to buy/sell currency pairs we require the quote currency to buy and the base
currency to sell. For example, you can't purchase LTCBTC with USD, and likewise
you can't sell LTCBTC without having LTC to sell.

This is being improve by @StefanoRaggi -- closing as it's now obsolete.


LICENSE: default-plugin uses API which is not licensed for commercial usage

📜 Description
The default-plugin generated by the CLI uses the API of https://randomuser.me:
https://github.com/backstage/backstage/blob/master/packages/cli/templates/default-plugin/src/components/ExampleFetchComponent/ExampleFetchComponent.tsx.hbs#L79

https://randomuser.me uses https://www.uifaces.co for generating data.
https://www.uifaces.co/license in turn uses https://generated.photos/terms-and-conditions for generating photos
https://generated.photos/terms-and-conditions is for non-commercial usage only (unless paid)

Why generating a plugin with CLI in an commercial context, this can be an issue.
👍 Expected behavior
The CLI should generate a plugin that is compatible with commercial environments.
👎 Actual Behavior with Screenshots
https://randomuser.me

https://www.uifaces.co/licenses/

https://generated.photos/terms-and-conditions

👟 Reproduction steps
Generate a new plugin with the CLI:
yarn new --select plugin

📃 Provide the context for the Bug.
Backstage Plugin development
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

Yep - let's remove this from the ExampleFetchComponent - let's replace with hardcoded list or some better example?
Also there's an occurrence here: https://github.com/backstage/backstage/blob/master/packages/cli/templates/default-plugin/src/components/ExampleFetchComponent/ExampleFetchComponent.tsx.hbs#L33

Yep - let's remove this from the ExampleFetchComponent - let's replace with hardcoded list or some better example?

I expect from an ExampleFetchComponent to provide an example for fetching data :)
But good question regarding alternatives. Maybe https://reqres.in/ ?
cheers
flash ⚡

I'm also opting for some hardcoded data to avoid this ever becoming a problem again. We can always sprinkle a bit of async in there as well and have a comment showing how you fetch and json parse from some example domain that does not exist.

@ShadowWalker98 sure you can! Will assign to you! Be sure to check out the contributing guide and good luck!

Okay sure! If I need any help or have questions, I am to comment here, yes?

Yep - let's remove this from the ExampleFetchComponent - let's replace with hardcoded list or some better example?

I expect from an ExampleFetchComponent to provide an example for fetching data :)
But good question regarding alternatives. Maybe https://reqres.in/ ?
cheers flash zap

https://reqres.in/ is not free to use are backstage will to pay for fake data ?

I think we just need images. Any random avatar service that DOES allow for this use (perhaps from open source projects specifically) should be good as a replacement

Hi @freben does it matter if users are static I curated a list of 20 users that should fix this issue.

Human emoji from dicebear should be fine 👍

@jhaals  so it okay to put json in examplefetchcomponent ?


trouble matching --preset ISOSEQ settings

Operating system
Debian GNU/Linux 11 (bullseye)
Package name
> pbmm2 --version
pbmm2 1.13.0
Using:
  pbmm2    : 1.13.0 (commit v1.13.0-2-gbcd99f5)
  pbbam    : 2.4.99 (commit v2.4.0-23-g59248fe)
  pbcopper : 2.3.99 (commit v2.3.0-28-ga9b1ffa)
  boost    : 1.81
  htslib   : 1.17
  minimap2 : 2.26
  zlib     : 1.2.13

Conda environment
> conda list
# packages in environment at /opt/conda:
#
# Name                    Version                   Build  Channel
_libgcc_mutex             0.1                 conda_forge    conda-forge
_openmp_mutex             4.5                  2_kmp_llvm    conda-forge
bam2fastx                 3.0.0                h9ee0642_0    bioconda
bax2bam                   0.0.11                        0    bioconda
boltons                   23.0.0             pyhd8ed1ab_0    conda-forge
brotlipy                  0.7.0           py39h27cfd23_1003
bzip2                     1.0.8                h7f98852_4    conda-forge
c-ares                    1.19.1               hd590300_0    conda-forge
ca-certificates           2023.7.22            hbcca054_0    conda-forge
certifi                   2023.7.22          pyhd8ed1ab_0    conda-forge
cffi                      1.15.0           py39hd667e15_1
charset-normalizer        2.0.4              pyhd3eb1b0_0
colorama                  0.4.4              pyhd3eb1b0_0
conda                     23.7.4           py39hf3d152e_0    conda-forge
conda-content-trust       0.1.1              pyhd3eb1b0_0
conda-package-handling    1.8.1            py39h7f8727e_0
cryptography              36.0.0           py39h9ce1e76_0
htslib                    1.17                 h6bc39ce_1    bioconda
idna                      3.3                pyhd3eb1b0_0
isoseq                    4.0.0                h9ee0642_0    bioconda
isoseq3                   4.0.0                h9ee0642_0    bioconda
jsonpatch                 1.32               pyhd8ed1ab_0    conda-forge
jsonpointer               2.4              py39hf3d152e_2    conda-forge
keyutils                  1.6.1                h166bdaf_0    conda-forge
krb5                      1.20.1               hf9c8cef_0    conda-forge
ld_impl_linux-64          2.35.1               h7274673_9
libcurl                   7.87.0               h6312ad2_0    conda-forge
libdeflate                1.19                 hd590300_0    conda-forge
libedit                   3.1.20191231         he28a2e2_2    conda-forge
libev                     4.33                 h516909a_1    conda-forge
libffi                    3.3                  he6710b0_2
libgcc-ng                 13.2.0               h807b86a_2    conda-forge
libnghttp2                1.51.0               hdcd2b5c_0    conda-forge
libssh2                   1.10.0               haa6b8db_3    conda-forge
libstdcxx-ng              13.2.0               h7e041cc_2    conda-forge
libzlib                   1.2.13               hd590300_5    conda-forge
lima                      2.7.1                h9ee0642_0    bioconda
llvm-openmp               16.0.6               h4dfa4b3_0    conda-forge
ncurses                   6.3                  h7f8727e_2
openssl                   1.1.1w               hd590300_0    conda-forge
packaging                 23.1               pyhd8ed1ab_0    conda-forge
pbbam                     2.4.0                h8db2425_0    bioconda
pbccs                     6.4.0                h9ee0642_0    bioconda
pbcopper                  2.3.0                hfce7173_0    bioconda
pbmm2                     1.13.0               h9ee0642_0    bioconda
pbtk                      3.1.0                h9ee0642_0    bioconda
pip                       21.2.4           py39h06a4308_0
pluggy                    1.3.0              pyhd8ed1ab_0    conda-forge
pycosat                   0.6.3            py39h27cfd23_0
pycparser                 2.21               pyhd3eb1b0_0
pyopenssl                 22.0.0             pyhd3eb1b0_0
pysocks                   1.7.1            py39h06a4308_0
python                    3.9.12               h12debd9_0
python_abi                3.9                      2_cp39    conda-forge
readline                  8.1.2                h7f8727e_1
requests                  2.27.1             pyhd3eb1b0_0
ruamel.yaml               0.17.32          py39hd1e30aa_0    conda-forge
ruamel.yaml.clib          0.2.7            py39h72bdee0_1    conda-forge
ruamel_yaml               0.15.100         py39h27cfd23_0
setuptools                61.2.0           py39h06a4308_0
six                       1.16.0             pyhd3eb1b0_1
sqlite                    3.38.2               hc218d9a_0
tk                        8.6.11               h1ccaba5_0
toolz                     0.12.0             pyhd8ed1ab_0    conda-forge
tqdm                      4.63.0             pyhd3eb1b0_0
tzdata                    2022a                hda174b7_0
urllib3                   1.26.8             pyhd3eb1b0_0
wheel                     0.37.1             pyhd3eb1b0_0
xz                        5.2.6                h166bdaf_0    conda-forge
yaml                      0.2.5                h7b6447c_0
zlib                      1.2.13               hd590300_5    conda-forge
zstd                      1.5.5                hfc55251_0    conda-forge

Describe the bug
Comparing:
pbmm2 align -j 16 -k 15 -w 5 -u -o 2 -O 32 -e 1 -E 0 -A 1 -B 2 -z 200 -Z 100 -r 200000 -g 2000 -C 5\
 -G 200000 --sort genome.fasta reads.hifi.bam output.bam

to:
pbmm2 align -j $ncpus --preset ISOSEQ --sort genome.fasta reads.hifi.bam output.bam

I matched equivalent parameters per the help returned from pbmm2 align --help:
ISOSEQ : -k 15 -w 5  -u -o 2 -O 32 -e 1 -E 0 -A 1 -B 2 -z 200 -Z 100 -r 200000 -g 2000 -C 5 -G 200000

But I find the results are very different. This should produce a gapped alignment (cDNA vs genomic assembly), and with --preset ISOSEQ I see many N (skipped) in cigar string, as expected. MAPQ and edit distance look good. However, with the explicit parameter set (no --preset used, but the -k 15 -w 5 ... instead), I see similar CIGAR, but with Ds (deletions) in place of N, much lower MAPQ and much larger edit distances. A typical example of output with --preset ISOSEQ:
transcript/47119        16      chr1    14407   60\
      423=140N69=757N24=1X127=659N159=92N119=1X78=177N136=237N137=172N147=206N99=546N227=5598N154=4429N25=\
    *       0       14939\
   CTGCTCAGTTCTTTATTGATTGGTGTGCCGTTTTCTCTGG\
...
AGGAGTCATGGTGCCTGCGAGCCGCCCTCCCGGAAGCTC  *       ib:Z:0,2,2\
      im:Z:m64039_201204_055021/60163887/ccs,m64039_201204_055021/158862130/ccs       is:i:2  ic:i:56\
 zm:i:47119      RG:Z:e4927d21   mg:f:99.8962    NM:i:2

While with the explicit parameter list (no --preset), the same transcript/genome combo yields:
transcript/47119        16      chr1    14409   30\
      2S420=140D70=757D24=1X127=659D159=92D119=1X76=177D135=237D139=172D146=206D99=546D231=177S\
       *       0       4733\
   CTGCTCAGTTCTTTATTGATTGGTGTGCCGTTTTCTCTGG\
...
AGGAGTCATGGTGCCTGCGAGCCGCCCTCCCGGAAGCTC  *       ib:Z:0,2,2\
      im:Z:m64039_201204_055021/60163887/ccs,m64039_201204_055021/158862130/ccs       is:i:2  ic:i:56\
 zm:i:47119      RG:Z:e4927d21   mg:f:99.3736    NM:i:2988

Please note the very similar CIGARs, except the D in place of N in the second case.
Are the parameters I'm passing incorrect or missing something?
Error message
Completes without complaint; just many fewer decent hits returned.
To Reproduce
Steps to reproduce the behavior. Providing a minimal test dataset on which we can reproduce the behavior will generally lead to quicker turnaround time!
Please try with test data of your choice. I've seen it with various HiFi cDNA datasets, from both mouse and human, so don't think there is anything particular to my data.
Expected behavior
A clear and concise description of what you expected to happen.
Expect very similar results, given the equivalency of the --preset ISOSEQ option listed by pbmm2 align --help. Am I missing something?
Thanks for your time!

BTW, tried w/ https://downloads.pacbcloud.com/public/software/installers/smrtlink_<IP_ADDRESS>339.zip and the equivalent parameters listed by the pbmm2 align --help there, which differs in that it adds -L 0.5 to --preset ISOSEQ parameter equivalence list. So command: pbmm2 align -j 16 -k 15 -w 5 -u -o 2 -O 32 -e 1 -E 0 -A 1 -B 2 -z 200 -Z 100 -r 200000 -g 2000  -C 5 -G 200000 -L 0.5 --sort genome.fasta reads.hifi.bam mmap.bam and, unfortunately, find the same issue. I suspect the Ds vs Ns in CIGAR (mentioned in original issue report) may be a hint. Thanks for any help you can provide.

Why are you trying to manually configure pbmm2 instead of using --preset? The source code is available, so you can go and figure it out that it's due to this line

Thanks for your help Armin. Users of a pipeline incorporating pbmm2 asked for the option to change some parameters to be able to better match very small exons. They are sophisticated users who need to be able to make adjustments for specific cases. This similar situation can be handled using minimap2 by tweaking settings. So I exposed the pbmm2 mapping parameters in the option file for the pipeline, hoping to enable the same performance, but wanted to keep the default settings for those parameters equivalent to --preset ISOSEQ, because that is the option I used until receiving the user request. Unfortunately my attempt to set the defaults by following the documentation failed testing. I took a quick look at the code but could not find the right line, and I could not afford to spend too much time looking for it. I hope you don't mind me reporting the mismatch between the documentation and the actual behavior (might benefit others as well), or asking for some guidance. In any case, thanks again for the help. I really do appreciate it. Best regards, Mitch


Notebook cell status bar API

We have a proposal for cell status bar items but we should revisit its design. The current proposal is modelled closely after the existing global status bar API. However the global status bar and cell status bars have a very different lifecycle: the global status bar is always there and shares the lifecycle of the editor. Cells on the other hand are usually short-lived, often not visible (not scrolled in view, hidden editor etc pp).
This is what's needed to manage the status bar for cells: https://github.com/microsoft/vscode-github-issue-notebooks/blob/edf85a2e9db0d28166526c844e479724434209b6/src/extension/notebookProvider.ts#L156-L182 and it shows a couple of weaknesses of the design

it has much semantic overlap with commands/menus
it listens to output changes of any notebook (no matter if visible or not), e.g it actively needs to manage status bar item which is often error-prone
it doesn't know anything about the lifecycle because the workbench will dispose the object the extension has created. That's generally fishy because only object-creator should call dispose.

So, I think we should first justify why context keys and commands aren't sufficient and then we should turn this into a provider model. E.g have a NotebookCellStatusBarItemProvider which we ask for cell's items, e.g
class NotebookCellStatusBarItem {
  command: Command;
  text: string;
}

interface NotebookCellStatusBarItemProvider {
  // provider has changed,
  onDidChange?: Event<void>;

  provideCellStatusBarItem(cell: NotebookCell): ProviderResult<NotebookCellStatusBarItem>;
}

We decide when to call provideCellStatusBarItem, like on output change etc, and it will return short-lived data-only objects that we manage.

I think we should first justify why context keys and commands aren't sufficient and then we should turn this into a provider model

100% agree.

I agree, this isn't finalized, we just had to get it off the ground. I would like to see a model that lets an extension write a static contribution for a cell status bar item but it needs to be able to plug in dynamic data (like for the title). This would need

a new type of contribution point
the ability to set new arbitrary context keys on a cell, or a single object-type context key that multiple parties can contribute to

this would be a new concept in vscode, TreeItems only let you set a single context key

A way to plug in dynamic data, I like the concept of a title that references a custom metadata field

I don't think the provider model works. The extension needs to be in total control of when the items change. And maybe we have solved  these issues with other providers, but wouldn't it have to do the same bookkeeping to keep track of whether an item has already been added to a cell? I think a static contribution model would be easiest, especially for items that don't have dynamic content.

Talked with Peng about it and I see how the provider model makes sense. I still like the static contribution model because it fits a lot of usecases very easily but maybe it requires too much new stuff.

lets an extension write a static contribution for a cell status bar item but it needs to be able to plug in dynamic data (like for the title).

What's the use-case for that? This has come up for commands as well, e.g. the ability to change its title, but we have always stayed away from that because of the confusion that will cause. Is not being able to update (command) title a blocker or something that's nice to have?

Most of the scenarios that we've seen from the python extension would be served with static titles. Some of them have dynamic titles and some of them it's easy to imagine how dynamic data would show up - maybe the title is just an icon but then you want to have a tooltip with details or a timestamp or something.
one example -

and it would be very cool to have something like a gitlens annotation here. I think an API that only works like a toolbar would be incomplete.

Here's what we're planning, hopefully for March if I can finish it:

Remove createCellStatusBarItem
Remove the statusMessage cell metadata
Replace it with this provider pattern

export class NotebookCellStatusBarItem {
    readonly text: string;
    readonly alignment: NotebookCellStatusBarAlignment;
    readonly command: string | Command | undefined;
    readonly tooltip: string | undefined;
    readonly priority?: number;
    readonly accessibilityInformation?: AccessibilityInformation;

    constructor(text: string, alignment: NotebookCellStatusBarAlignment, command?: string | Command, tooltip?: string, priority?: number, accessibilityInformation?: AccessibilityInformation);
}

interface NotebookCellStatusBarItemProvider {
    onDidChangeCellStatusBarItems?: Event<void>;
    provideCellStatusBarItems(cell: NotebookCell, token: CancellationToken): ProviderResult<NotebookCellStatusBarItem[]>;
}

export namespace notebook {
    export function registerNotebookCellStatusBarItemProvider(selector: NotebookDocumentFilter, provider: NotebookCellStatusBarItemProvider): Disposable;
}

// Called when a cell becomes visible

I'd say also when a cell output changes and likely others


Use the latest AL2022 release server

Summary
Remove distribution_release_al2022  and use latest get the latest AL2022 repository version.
Implementation details

Remove distribution_release_al2022 from generate-release-vars.sh and variables.pkr.hcl
Use latest for sudo dnf update -y --releasever=latest in al2022.pkr.hcl

Testing
Test case 1: Using the latest Amazon Linux AL2022 (20221101) as source AMI

Generated the new release variables

ami_version          = "99999999"
ecs_agent_version    = "1.65.0"
ecs_init_rev         = "1"
docker_version       = "20.10.13"
containerd_version   = "1.4.13"
source_ami_al2022    = "al2022-ami-minimal-2022.0.20221101.0-kernel-5.15-x86_64"
source_ami_al2022arm = "al2022-ami-minimal-2022.0.20221101.0-kernel-5.15-arm64"
...

Built AL2022 with the generated release variables using the source AMI al2022-ami-minimal-2022.0.20221101.0-kernel-5.15-x86_64, and the build is completed successfully.

==> amazon-ebs.al2022: + sudo dnf update -y --releasever=latest
    amazon-ebs.al2022: Waiting for process with pid 1602 to finish.
    amazon-ebs.al2022: Amazon Linux 2022 repository                     24 MB/s |  17 MB     00:00
    amazon-ebs.al2022: Dependencies resolved.
    amazon-ebs.al2022: Nothing to do.
    amazon-ebs.al2022: Complete!

Test case 2: Using the previous Amazon Linux AL2022 (20221019) as source AMI

Generated the new release variables

ami_version                 = "88888888"
ecs_agent_version           = "1.65.0"
ecs_init_rev                = "1"
docker_version              = "20.10.17"
containerd_version          = "1.6.6"
source_ami_al2022           = "al2022-ami-minimal-2022.0.20221019.4-kernel-5.15-x86_64"
source_ami_al2022arm        = "al2022-ami-minimal-2022.0.20221019.4-kernel-5.15-arm64"
...

Built AL2022 with the generated release variables using the source AMI al2022-ami-minimal-2022.0.20221019.4-kernel-5.15-x86_64, and the build is completed successfully.

==> amazon-ebs.al2022: + sudo dnf update -y --releasever=latest
    amazon-ebs.al2022: Amazon Linux 2022 repository                     23 MB/s |  17 MB     00:00
    amazon-ebs.al2022: Last metadata expiration check: 0:00:06 ago on Tue 01 Nov 2022 09:14:15 PM UTC.
    amazon-ebs.al2022: Dependencies resolved.
    amazon-ebs.al2022: ================================================================================
    amazon-ebs.al2022:  Package               Arch    Version                       Repository    Size
    amazon-ebs.al2022: ================================================================================
    amazon-ebs.al2022: Upgrading:
    ...
    amazon-ebs.al2022: Upgraded:
    amazon-ebs.al2022:   amazon-linux-repo-s3-2022.0.20221101-0.amzn2022.noarch
    amazon-ebs.al2022:   openssl-1:3.0.5-1.amzn2022.0.3.x86_64
    amazon-ebs.al2022:   openssl-libs-1:3.0.5-1.amzn2022.0.3.x86_64
    amazon-ebs.al2022:   system-release-2022.0.20221101-0.amzn2022.noarch
    amazon-ebs.al2022:
    amazon-ebs.al2022: Complete!

New tests cover the changes: no
Description for the changelog
Use "latest" to get the latest AL2022 repository version
Licensing
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Will close this PR as pining release server version helps us to make sure building ECS optimized AL2022 AMIs with the same release version across different regions.


League Event integration

Flextype 0.9.0 should use League Event instead of Flextype Events
The league/event package provides a versatile tool to manage events in your app or domain. The package supports string based and class based events, as well as Closure or class based listeners. This makes the package ideal for regular event management but also allows for a clean event-driven style of programming.
Link: https://event.thephpleague.com/2.0/

Implemented


Add support for Innr SP120 smart plug.

Support for: Switching; Voltage/Current/Power measurement.

Thanks!


chore(master): release 2.1.30

:robot: I have created a release beep boop
2.1.30 (2024-03-13)
Bug Fixes

deps: update dependency laravel/framework to v10.48.2 (d4fa715)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/laravel-stripe-webhooks/releases/tag/v2.1.30 :sunflower:


Small developments

plot_connectome with new feature for different node sizes
copy_hemisphere now corrected and documented
possibility to import properties from a dictionary (useful when we have measures separately calculated for each node)
small tweaks here and there in the code

Codecov Report

Merging #23 into master will increase coverage by 1.32%.
The diff coverage is 75.51%.

@@            Coverage Diff             @@
##           master      #23      +/-   ##
==========================================
+ Coverage    28.3%   29.62%   +1.32%
==========================================
  Files          20       20
  Lines        1862     1890      +28
  Branches      503      508       +5
==========================================
+ Hits          527      560      +33
+ Misses       1281     1272       -9
- Partials       54       58       +4

Impacted Files
Coverage Δ

maybrain/plotting/connectome.py
71.11% <53.84%> (-8.31%)
:arrow_down:

maybrain/brain.py
72.13% <83.33%> (+5.14%)
:arrow_up:

Continue to review full report at Codecov.

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


Server Database Structure and Functionality with Default Data

In a branch named Issue-019.
db collections structures

all files defining collections are located in the api directory.
settings.development.json holds arrays of objects correlating to each collection.
I tried to split up the relational collections with their intuitive partner data (ie. Recipes and RecipesIngredients in the same folder)
Minimal implementation. (ie. Recipes do not yet support an image of the dish)

Server side installation of collections

Mongo.js currently installs all defined collections
Publications.js currently publishes all documents to everyone, except for IngredientsAllergies (only visible to owner and admin)

Going to add back support for an image to Recipes, since the RecipeCard created in a branch uses it.


WebDAVFileProvider doesn't handle deletion results properly.

When calling removeItem(path:completionHandler) -> OperationHandle? inside WebDAVFileProvider: FileProviderOperations the result will be 204 (No Content) which is valid (the item was deleted), however, the completion handler is called with an error whenever the response isn't 207 (Multi-Status).

Thank you for report, I also noticed error report for other methods are not as expected, I will rectify it asap.

https://github.com/amosavian/FileProvider/commit/66fc1e128483081a2b5d8563d161ae6096ab0e5d

Fixed https://github.com/amosavian/FileProvider/commit/66fc1e128483081a2b5d8563d161ae6096ab0e5d


Add Swagger files for CLU 2022-03-01-preview

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Hi @JeffreyRichter, this PR adds CLU's swagger. We added it on top of the swagger of TA. Both services are under the same /language umbrella. However, there are two validation failures which I hope you can help us.

The Avocado failure says MISSING_APIS_IN_DEFAULT_TAG, which I don't know how to fix because we do not have a default tag. This is also the first time we have tried to put Swagger files of two services under the same version.
The breaking change failure is because we made "error" as required in an error response. Do you know how to override this validation failure?

Thanks for your help.

The board review issue: https://github.com/Azure/azure-rest-api-specs/issues/17505

Hi @tjprescott , this PR has the same [MISSING_APIS_IN_DEFAULT_TAG] failure in Avocado. I tried to add analyzeconversations.json in 2022-02-01-preview but it does not help. I want to add analyzeconversations.json only in 2022-03-01-preview. Really appreciate if you can help me out?

Hi @weidongxu-microsoft  or @tjprescott . This PR has the same MISSING_APIS_IN_DEFAULT_TAG issue. This PR merges CLU's 2022-03-01-preview version into a release/feature branch. Can you help us skip this check? Thanks!

@ChongTang skip CI will only happen before you are ready to merge. I don't think this PR is at this stage yet.

/azp run

Actually, there's 4 more instances of "language" (or "detectedLanguage") that you might want to document are BCP 47, if, in fact, they are:

https://github.com/Azure/azure-rest-api-specs/blob/a74a78919147b3a2866b40f6f326d6bcae78908f/specification/cognitiveservices/data-plane/Language/preview/2022-03-01-preview/analyzeconversations.json#L394
https://github.com/Azure/azure-rest-api-specs/blob/67e66fc626cb798f29b6026c4ba4a30a3d927e13/specification/cognitiveservices/data-plane/Language/preview/2022-03-01-preview/analyzeconversations.json#L436
https://github.com/Azure/azure-rest-api-specs/blob/a74a78919147b3a2866b40f6f326d6bcae78908f/specification/cognitiveservices/data-plane/Language/preview/2022-03-01-preview/analyzeconversations.json#L561

Thanks Heath! I resolve both "language" and "modelAsString" issues. I also searched in the file and resolved all occurrences.


Delete Button

Change Delete dropdown menu to a Delete button

What?  Where?  Pretend  I have no Idea what your talking about. This is a very sad ticket.

Try to delete an event by opening the event first. Drop down in the event
called Delete. Has YES or NO in the drop down. Could change to a button
instead to delete.
On Wed, Jun 24, 2020, 7:15 AM Shark<EMAIL_ADDRESS>wrote:

What? Where? Pretend I have no Idea what your talking about. This is a
very sad ticket.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sharkbit/BadgeApp/issues/11#issuecomment-648758259,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQAZBWBU2SEQ2G5BT64U7Z3RYHN63ANCNFSM4OGGAKQA
.

I will change it to:
Calendar event,  if has permission show delete button, or 'deleted', else show status only

Fixed event delete button


Text colour should be black

What would you like to be added?

when I landed on this page. I need to highlight the text in order to see them. The box stroke, fill and text color all are in same color which is white. I am not from front-end but I think we can collaborate and make this issue done.
Why is this needed?
It will make website better and help others.

The style sheet for this website typically uses black text on white. That diagram then uses white text on blue.
If you set a user style sheet or otherwise customize how the site is displayed, make sure that your customization leaves it readable. This also applies when you have a browser plugin for doing that customization.
/triage not-reproducible
/remove-kind feature
/kind bug

Ohk I got this


Script Assert - Dynamic Parameters are not found

I always get the following error-message:
The following parameters used in the script were NOT found on the JSON "parameters" object of your script asset file:///c:/hello.jsx
            t, t
        Please set defaults in your JSX script (see documentation) or copy the following placeholder JSON code snippet and replace the values with your own:
            "parameters" : [
                {
                    "key" : "t",
                    "value" : null
                }
                {
                    "key" : "t",
                    "value" : null
                }
            ]
        Remember to always use a fallback default value for any use of the NX object to have the ability to run this script on After Effects directly. Example:            const dogName = NX && NX.get("doggo") || "Doggo";

my json:
{
    "assets":[
        {
            "src":"file:///c:/hello.jsx",
            "type":"script",
            "parameters":[
                {
                    "type":"string",
                    "key":"compName",
                    "value":"Captain Sparkles"
                },
                {
                    "type":"string",
                    "key":"layerOne",
                    "value":"Captain layer"
                },
                {
                    "type":"string",
                    "key":"title",
                    "value":"Captain title"
                }
            ]
        }
    ]
}

my jsx:
const a = NX.get("layerOne")

function Fiona(compName, layerName, title,solidTitle) {
    var newComp = app.project.items.addComp(compName, 1920, 1080, 1, 10, 25);
    var newLayerSo = newComp.layers.addSolid([100, 100, 0], 'Distortion', 600, 600, 1.0);
    var newLayer = newComp.layers.addText(title);
}
app.beginUndoGroup("code")
Fiona("compName" , "layerName", NX.get("title"),"")
app.endUndoGroup

I know that this is not the best example, but what i really don't understand is,
that no matter what key i wanted to get. It always tells me that i should insert 't'.
And if i really add 't' as a key to my json, the error-message is gone.
So for some reason the parser is always looking for a 't'.
Tested with the latest version of nexrender-cli.

important info: but the video gets rendered anyway.

Yes, I second that! It drives me nuts as well! Until finding time to fix it, our scripts do also have parameter "t" everywhere...
Might be your step into contributing, @jbojbo, what do you think? :o)

Hey, @dukuo, I would really appreciate your thoughts on this one as well! Maybe you could help us understand what might be going wrong here.


Add 'trailing' option to 'editor.renderWhitespace'

This PR fixes #43127
Add a new option ('trailing') to editor.renderWhitespace that renders only trailing whitespace (including lines with only whitespace).

Thank you!

Any chance we could get a way to combine both the selection and trailing options? Maybe selection should be its own setting?

I also think the selection option doesn't correspond to other options in editor.renderWhitespace: it works like all but only for selected text, therefore playing a slightly different role. Moreover, as you said, extracting selection to its own setting will increase customization capabilities (will allow combine options).  So, I like your idea.
My little investigation showed that realization shouldn't be hard, so I can create the issue (where we can discuss the details) and implement this feature if @alexdima finds it acceptable.

There's now a relevant bug: https://github.com/microsoft/vscode/issues/106697
Go forth and upvote it.


Uncaught Invariant Violation: addComponentAsRefTo(...)

I am getting the next errors on console when I am instantiating a DataPicker in the render method from my component.
Uncaught Invariant Violation: addComponentAsRefTo(...): Only a ReactOwner can have refs. You might be adding a ref to a component that was not created inside a component'srendermethod, or you have multiple copies of React loaded
Then when I click on the datapicker input, the dialog is shown, but I got:
react-datepicker.min.js:7 Uncaught TypeError: Cannot read property 'jquery' of null
and
ReactErrorUtils.js:71 Uncaught TypeError: Cannot read property 'focus' of undefined
I am running React v0.14.8. Do you have any idea why this is happening?
Thanks

What version of the date picker are you using?  Also please post the relevant code as it's very hard to tell what's going on without it.

react-datepicker v0.25.0
Basically I have a custom component that uses DatePicker, imported as a ReactDatePicker.
import ReactDatePicker from 'react-datepicker';
// [...]
getInitialState: function() {
  return {
    startDate: moment()
  };
},
render() {
    const {
      labelText,
      disabled,
    } = this.props;

    let className = '';
    if (disabled) {
      className += ' disabled';
    }

    return (
      <label className={`field${className}`}>
        { labelText }
        <ReactDatePicker
          selected={this.state.startDate}
        />
        <br />
      </label>
    );
  },

And the callstacks of the errors:

Thanks

How are you declaring your class?  If it's a functional component, it won't work because we use refs; you'll need to use React.createClass or class Blah extends React.Component { ....

@Gywem, take a look at #334 and #136 as well (please search for this kind of thing in the future)

"npm ls react" will tell us the list of react component available in node_modules. I saw two version available, I deleted react folder from node_modules and did npm install again which solved my issue

I was struggling with the same issue for a day.
So finally in my case it was 2 different versions of React inside node_modules but it was somehow difficult to reproduce it - sometimes npm would install only one version, another time - both.
$ npm ls react
<EMAIL_ADDRESS>/home/chestozo/my-mega-pack/client
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
There are 2 types of fix as far as I could understand:

use same React version as your dependencies
In my case it was like on the snippet above - I had<EMAIL_ADDRESS>and<EMAIL_ADDRESS>
This was because in my package.json I had "react": "15.4.0" while in dependency package common-components they had "^15.1.0".
After changing version in my package.json to the same version as specified in common-components - "^15.1.0" - it was fixed.

another fix is to specify resolve.alias in webpack config (I am using webpack) - found here
https://stackoverflow.com/a/42411974/449345
https://stackoverflow.com/a/31170775/449345

Like this:
{
    resolve: {
        alias: {
            react: path.resolve('./node_modules/react'),
            'react-dom': path.resolve('./node_modules/react-dom')
        }
    }
}

Maybe it helps someone else.