UX Suggestion: Dismiss confirmation modal with ESC

When flicking between the different top level menus, the exploration flow is stopped on the "Deploy" section with the forced mouse only interaction with the "Do you want to re-deploy the Website" modal.

Suggestions

[x] allow the "cancel" flow to be actioned by pressing the esc key
[x] allow tab key presses to focus the front-most buttons (currently it tabs through the greyed out content

Btw, now fixed here https://github.com/Cockpit-HQ/Cockpit/commit/48ff14341ef7e8018cc153727e37580bb1e8ebf8

Awesome @aheinze  ... Can I suggest adding a CONTRIBUTING file to this repo to suggest issues are created on the new repo?


Update, December 2024

Update information about Kien Giang Medical College, December 2024

@CoffeeSoftVn The domain registrant for kgmc.edu.vn is Trường Cao đẳng Y tế Kiên Giang (Kien Giang Medical College). This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@CoffeeSoftVn Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


AttributeError: 'HTTPError' object has no attribute 'headers'

The retry code of client.py (line 115) tries to access e.headers that don't exist.
requests==2.22.0
apple-music-python==1.0.2
Traceback (most recent call last):
  File "/home/username/.virtualenvs/env/project/lib/python3.5/site-packages/applemusicpy/client.py", line 107, in _get
    return self._call('GET', url, kwargs)
  File "/home/username/.virtualenvs/env/project/lib/python3.5/site-packages/applemusicpy/client.py", line 92, in _call
    r.raise_for_status()  # Check for error
  File "/home/username/.virtualenvs/env/project/lib/python3.5/site-packages/requests/models.py", line 940, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 504 Server Error: Gateway Time-out for url: https://api.music.apple.com/v1/catalog/us/songs/962218666

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
[...]
  File "/home/username/.virtualenvs/env/project/lib/python3.5/site-packages/applemusicpy/client.py", line 362, in song
    return self._get_resource(song_id, 'songs', storefront=storefront, l=l, include=include)
  File "/home/username/.virtualenvs/env/project/lib/python3.5/site-packages/applemusicpy/client.py", line 151, in _get_resource
    return self._get(url, **kwargs)
  File "/home/username/.virtualenvs/env/project/lib/python3.5/site-packages/applemusicpy/client.py", line 115, in _get
    sleep_seconds = int(e.headers.get('Retry-After', delay))
AttributeError: 'HTTPError' object has no attribute 'headers'

I will fix this and update the code

I adjusted the HTTPError handler so you shouldn't get the AttributeError anymore. It will delay for some seconds and then retry the call until it hits the maximum retry limit.


Feature/individual entity

I'm sure there is a nicer way to do this, but hopefully this gets oat moving in the right direction.
Adds support for individual resources at the top-level in JsonAPI without breaking existing behaviors.
The spec says:

An individual resource SHOULD be represented as a single "resource object" (described below) or a string value containing its ID (also described below).

This change works by setting a flag in the serializer ('individual') that indicates you want a singular resource.
I originally modified the inflection rules as well (so if you specify 'individual' we don't try to pluralize the names), but then I decided against it and went back to pluralizing everywhere for consistency. You can see that moment of self-doubt in the commit history.
Note: it might be useful to also include a flag to turn off pluralization for those few cases where a plural name makes no sense (like in this case, where I was writing /api/status)
Usage:
class Status < Oat::Serializer
  adapter Oat::Adapters::JsonAPI
  schema do
    individual
    type 'status'
    map_properties *%i(at status)
  end
end

Output:
{
    "statuses": {
        "at": "2014-09-21T08:24:12.807-07:00",
        "status": "unknown"
    }
}

I'm hesitant to add the "individual" method as part of the generic DSL for what is, at least at the moment, a very JsonAPI specific thing.  I think that this method is also more a modifier on adapter behaviour rather than part of the schema definition.
Given that there will always be adapter-specific nuances like this, I'm thinking it might be a good idea to separate the generic schema DSL methods from adapter specific options and modifiers. For example something like:
schema(individual: true) do
  type 'status'
  map_properties *%i(at status)
end

ie. the schema block is reserved for the generic DSL, but options passed as arguments to .schema() are passed directly to the adapter (which can use or ignore them accordingly).
Another, possibly more consequential change would be something like:
# This schema is applied to any adapter.
schema do
  type 'status'
  map_properties *%i(at status)
end

# This schema is merged and applied onto the generic one
# only when using the JsonAPI adapter
schema JsonAPI do
  individual!
  # etc
end

ie. we have a way to define a media-type agnostic schema (the main point of this library), but can also define media-type specific schemas that will be merged on top of the generic one. DSL methods used within these blocks can be adapter-specific and don't need to be compatible across adapters.
I'm liking this idea because it would allow to cater for the different quirks of different media types, and even define different schemas for different use cases of the same resource. Example:
schema do
  type ['Product']
  map_properties *%i(at status)
end

# Only when using the FullRepresentation adapter
schema FullRepresentationAdapter do
   entities :orders, item.orders, OrderSerializer
   entities :similar_products, item.similar_products, ProductSerializer
  # etc
end

# Only when using the GeographicRepresentation adapter
schema GeographicSearchRepresentationAdapter do
  property :distance_from_current_location, item.distance
end

# etc.


Error using Functionary-small-v3.2 AWQ version with vLLM

Hello Functionary team,
I'm trying to use the Functionary-small-v3.2 AWQ version with vLLM for inference, but I'm encountering an error. The vLLM library doesn't seem to recognize the 'FunctionaryForCausalLM' architecture.
Here's the specific error I'm getting:
ValueError: Model architectures ['FunctionaryForCausalLM'] are not supported for now.
I'm able to run the non-AWQ version successfully, but I'd like to use the AWQ version. Could you please provide guidance on:

Is the Functionary-small-v3.2 AWQ version compatible with vLLM?
Are there any special steps or configurations needed to use the AWQ version with vLLM?
If vLLM doesn't support this architecture, do you have any recommendations for alternative with the AWQ version of Functionary-small-v3.2?

Any information or resources you can provide would be greatly appreciated. Thank you for your help!

Hi, we do not have a functionary-small-v3.2 AWQ model currently. To help to reproduce, may I know where did you get this model from?

Thank you for your response. I apologize for the confusion. I should have been clearer in my initial message. I don't have an official AWQ version of functionary-small-v3.2. Instead, I have quantized the model myself using the AWQ method. Here's the process I followed:
I used the AWQ library to quantize the functionary-small-v3.2 model.
Here's the code I used for quantization:
pythonCopyfrom awq import AutoAWQForCausalLM
from transformers import AutoTokenizer
import tqdm as notebook_tqdm
model_path = 'meetkai/functionary-small-v3.2'
quant_path = 'meetkai/functionary-small-v3.2-awq'
quant_config = {
"zero_point": True,
"q_group_size": 128,
"w_bit": 4,
"version": "GEMM"
}
Load model
model = AutoAWQForCausalLM.from_pretrained(
model_path,
**{"low_cpu_mem_usage": True},
device_map='cuda'
)
tokenizer = AutoTokenizer.from_pretrained(model_path, trust_remote_code=True)
After quantizing the model using this method, I attempted to use it with vLLM, which is when I encountered the error about the 'FunctionaryForCausalLM' architecture not being supported.
I appreciate any guidance you can provide on this matter.

Are there any plans to release an official AWQ version of functionary-small-v3.2 in the future?
If so, do you have an estimated timeline for when this might be available?

Based on past experience, quantized versions like AWQ conserve significant RAM with minimal loss, though I'm unsure if this applies to functionary models.

I deployed a self-quantized GPTQ version of Functionary-small-v3.2, and it works perfectly for me.
I developed the quantized model based on AutoGPTQ documentation, using wikitext2 as the calibration dataset.


Use default image

Use default image (Visual Studio 2015)

:white_check_mark: Package verification completed without issues. PR is now pending human review


Add initial support for exposing educational notes as diagnostic codes

I've attached a gif of what this looks like in VSCode. A couple of notes on the implementation:

https://github.com/apple/swift/pull/31521 is a prerequisite
This relies on proposed changes in LSPv3.16, which is not yet released. The proposed new capability can be found here: https://github.com/microsoft/vscode-languageserver-node/blob/d2909f55704da3f30d5cd231125b4b90dbac88cf/protocol/src/protocol.ts#L1398
This change alone is not enough for the feature to work in VSCode. We'll also need to update the vscode-languageclient dependency in the VSCode extension from 4.0.0 to 7.0.0 when it's released. I've tested with the 7.0.0-next.1 preview and confirmed it's working

@benlangmuir thanks for looking this over! I think I've addressed most of your concerns, but I'd be fine with waiting until Swift 5.3 and/or LSP 3.16 ship before merging this to avoid complications.

Sorry, I forgot to reply to this:

I'd be fine with waiting until Swift 5.3 and/or LSP 3.16 ship before merging this to avoid complications.

I think we should wait for LSP 3.16 for this. The API might get tweaked for https://github.com/microsoft/vscode-languageserver-node/issues/601 and we are waiting for the client code to support it anyway.  I don't think we need to wait for Swift 5.3, but if it happens to come first we can take advantage and update the tests.

Closing since this is pretty out of date, and I can't really tell what's happening with LSP 3.16. I'll reopen later if complex diagnostic codes become officially supported


Can not use --provider and --mapbox-access-token

When I use mapbox style with charites serve style.yml --provider mapbox --mapbox-access-token my-access-token
It will display error in console in debug tool of Google Chrome.
evented.js:140 Error: An API access token is required to use Mapbox GL. See https://www.mapbox.com/api-documentation/#access-tokens-and-token-scopes
    at ajax.js:183

This is my humble suggestion. Currently, both --provider and --mapbox-access-token options are only used for charites serve command. It is not necessary to have both options as global parameters. We can move both of them into local parameters of serve command.


[Bug]: Unsupported field name in tool response

Describe the bug
The message generated a user proxy after tool execution contains the field "name", but it should not according to the OpenAPI specs (https://github.com/openai/openai-openapi/blob/f4a2833d00e92c4b1cb531d437da88a03de997d8/openapi.yaml#L5478C5-L5495):
ChatCompletionRequestToolMessage:
  type: object
  title: Tool message
  properties:
    role:
      type: string
      enum: ["tool"]
      description: The role of the messages author, in this case `tool`.
    content:
      type: string
      description: The contents of the tool message.
    tool_call_id:
      type: string
      description: Tool call that this message is responding to.
  required:
    - role
    - content
    - tool_call_id

Example of the output of user proxy after execution:
{
  ‘tool_call_id’: ‘call_1YWzmz9ADEH5aHeSyjBuvO5k’,
  ‘role’: ‘tool’,
  ‘name’: ‘currency_calculator’,
  ‘content’: ‘{“currency”: “USD”, “amount”:<PHONE_NUMBER>0000002}’
}

This causes problems with open-source LLMs (see e.g.https://levelup.gitconnected.com/do-you-know-function-calling-is-also-available-for-open-source-llms-in-autogen-b1d920f48b9b)
Steps to reproduce
No response
Expected Behavior
No response
Screenshots and logs
No response
Additional Information
No response

@yenif Can you take a look at this? I think it is an easy fix to remove line 916 in conversable_agent.py.


Version 1.50

There is 2 connections in this version.
The Catalog connection works
The data connection gives the error:
Details: "OData: The feed's metadata document appears to be invalid. Error: The metadata document could not be read from the message content.
InvalidEnumMemberPath : 'Collection(Capabilities.FilterExpressionRestrictionType)/MultiValue' is not a valid enum member path. : (96, 14)
"

Hi Jared,
The odata response of datasphere contains mainly two parts: the real data and the metadata describing the real data.
For sure, PowerBi reads the metadata part and parses it to understand data types etc. Now it seems that the metadata provided by datasphere seems to be incorrect from PowerBi perspective. Now the question is: who is right? A typical one if you write connectors between two products 😊.
What I would recommend narrowing down the root cause:
Getting the facts:
Capture the Request and Response. This could be done using fiddler or another http sniffer or as an alternative, build the URL for your service request manually and let the browser call the API.
In the beginning of the response, you see a URL pointing to the metadata. Open and download it. In fiddler you see the request for metadata already and you can pick it from there.
Narrow down the root cause:

The parameter belongs to a certain column of your datasphere view. When you have identified it, remove it from the source and check if it fixes the topic.
If yes, check the data type – is it different to the others?

Best regards, Olaf

Hi Olaf
I'm having the same problem. I can't install fiddler on my corporate PC, so I used Postman to get the metadata o the service.
The annotation causing the error seems to be at the entity set not at the attribute level. The annotation looks like:

I can't see anything in Datasphere that might control this.
Any thoughts!

Hi Andrewzdyer,
please check out the latest comment on issue #12 - in addition, could you please share the annotation sample you found? In your last reply, you write "The annonation looks like:" - but unfortunately not followed by a sample.
Thanks, Olaf

Thanks Olaf. I forgot to add the annotation text as code. I have edited the last comment to fix this :)
Based on your comment in issue 12, I'll have a look at the view settings in Datasphere to see where a filter may be set. It doesn't appear to be on a field, rather on the entity. If I find config to update in Datasphere to update I will post.


[Enhancement] Argument type 'String' does not match the type of the format specifier '%d'

Search before asking

[X] I had searched in the issues and found no similar issues.

Enhancement Request

located at:
eventmesh-runtime/src/main/java/org/apache/eventmesh/runtime/admin/handler/RejectClientBySubSystemHandler.java line 109
Describe the solution you'd like
reference:

Are you willing to submit PR?

[x] Yes I am willing to submit a PR!

I want to fix it.


simplify setup for sending emails from development

Hi there, thanks for building & open sourcing Release Ninja & for the exceptional documentation.
Streamline the setup of sending emails from development, specifically removing the need to edit development.rb

Howdy from Release Ninja! You should write a release note targeted at a semi-technical end user who is
not familiar with the code base. Include at least 1 image, wherever possible. Review the help article if
you are not familiar with Release Ninja.
When your pull request is ready, do one of the following:

Notify Release Team
Don't notify anyone because it's a small change or doesn't concern them
Whatever you do though, make sure you :tada:

Have you ever seen a program like fake smtp? It starts an smtp server on port 1025 locally, but black holes it so you can read everything that goes through it.
I believe these programs lead to a better local development experience because they can be used offline without change.

https://nilhcem.github.io/FakeSMTP/ Here is a link to fake smtp.

Hey thanks a ton for the advice! I didn't know about fake smtp. I'm happy to go with fake smtp instead so I'll close this pull request. If I do want to make a contribution, do you suggest I start with the issue you opened about "Automatic project acceptance" or something else?

Awesome! Super excited to hear that. im going to prune the issues that I haven't put up here to find a good one to start with! I did some changes to the invite system that closes that issue, already.

Thanks Stephen,
Please don't feel pressured to get back to me today, it is Sunday, and even if it wasn't, it's bed time in my time zone.


Unable to find CloseableHttpClient

I've gone about this several different ways now, and I'm running into roadblocks at each point. Here's the code that calls unirest:
package com.akqa.glass.recipie;

import android.util.Log;

import com.mashape.unirest.http.HttpResponse;
import com.mashape.unirest.http.JsonNode;
import com.mashape.unirest.http.Unirest;
import com.mashape.unirest.http.exceptions.UnirestException;

import org.json.JSONException;
import org.json.JSONObject;

import java.io.BufferedReader;
import java.io.File;
import java.io.InputStream;
import java.io.InputStreamReader;

//import org.apache.http.HttpResponse;
//import org.shaded.apache.http.HttpHeaders;

public class JSONParser {
    static InputStream is = null;
    static JSONObject jObj = null;
    static String json = "";
    private static final String TAG = JSONParser.class.getSimpleName();
    // constructor
    public JSONParser() {
    }
    public JSONObject getCamFindJSON(String type, String input) {
        Log.d("PARSER", "Inside Parser");
        /*
         *  Request processing from API
         */
        if(type == "request"){
            try {
                HttpResponse<JsonNode> response = Unirest.post("https://camfind.p.mashape.com/image_requests")
                .header("X-Mashape-Key", "Fhn5jZi5ixmshwnJMy7CGyj5yDCnp15DTQZjsniuwpVHfYHvFJ")
                .field("image_request[image]", new File(input))
                .field("image_request[language]", "en")
                .field("image_request[locale]", "en_US")
                .asJson();
            } catch (UnirestException e) {
                Log.d(TAG, "Couldn't get request");
                e.printStackTrace();
            }
        }
        /*
         *  Receive response from API
         */
        else if(type == "response"){
            try {
                HttpResponse<JsonNode> response = Unirest.get("https://camfind.p.mashape.com/image_responses/" + input)
                .header("X-Mashape-Key", "Fhn5jZi5ixmshwnJMy7CGyj5yDCnp15DTQZjsniuwpVHfYHvFJ")
                .asJson();
            } catch (UnirestException e) {
                Log.d(TAG, "Couldn't get reponse");
                e.printStackTrace();
            }
        }
        /*
         *  Parse Response into readable JSON
         */
        try {
            BufferedReader reader = new BufferedReader(new InputStreamReader(
                    is, "iso-8859-1"), 8);
            StringBuilder sb = new StringBuilder();
            String line = null;
            while ((line = reader.readLine()) != null) {
                sb.append(line + "n");
                Log.d("Raw Data", line);
            }
            is.close();
            json = sb.toString();
        } catch (Exception e) {
            Log.e("Buffer Error", "Error converting result " + e.toString());
        }
        // try parse the string to a JSON object
        try {
            jObj = new JSONObject(json);
        } catch (JSONException e) {
            Log.e("JSON Parser", "Error parsing data " + e.toString());
            e.printStackTrace();
        } catch (Exception e) {
            Log.e("JSON Parse", "Unknown Error");
            e.printStackTrace();
        }
        // return JSON String
        return jObj;
    }
}

Here is the logcat output:
11-24 16:26:57.473  12605-12856/com.akqa.glass.recipie E/dalvikvm﹕ Could not find class 'org.apache.http.impl.client.CloseableHttpClient', referenced from method com.mashape.unirest.http.Unirest.shutdown
11-24 16:26:57.473  12605-12856/com.akqa.glass.recipie W/dalvikvm﹕ VFY: unable to resolve check-cast 453 (Lorg/apache/http/impl/client/CloseableHttpClient;) in Lcom/mashape/unirest/http/Unirest;
11-24 16:26:57.473  12605-12856/com.akqa.glass.recipie D/dalvikvm﹕ VFY: replacing opcode 0x1f at 0x0006
11-24 16:26:57.481  12605-12856/com.akqa.glass.recipie I/dalvikvm﹕ Could not find method org.apache.http.client.methods.HttpRequestBase.releaseConnection, referenced from method com.mashape.unirest.http.HttpClientHelper.request
11-24 16:26:57.481  12605-12856/com.akqa.glass.recipie W/dalvikvm﹕ VFY: unable to resolve virtual method 1085: Lorg/apache/http/client/methods/HttpRequestBase;.releaseConnection ()V
11-24 16:26:57.481  12605-12856/com.akqa.glass.recipie D/dalvikvm﹕ VFY: replacing opcode 0x6e at 0x0012
11-24 16:26:57.481  12605-12856/com.akqa.glass.recipie I/dalvikvm﹕ Could not find method org.apache.http.client.methods.HttpRequestBase.releaseConnection, referenced from method com.mashape.unirest.http.HttpClientHelper.request
11-24 16:26:57.481  12605-12856/com.akqa.glass.recipie W/dalvikvm﹕ VFY: unable to resolve virtual method 1085: Lorg/apache/http/client/methods/HttpRequestBase;.releaseConnection ()V
11-24 16:26:57.481  12605-12856/com.akqa.glass.recipie D/dalvikvm﹕ VFY: replacing opcode 0x6e at 0x0021
11-24 16:26:57.481  12605-12856/com.akqa.glass.recipie I/dalvikvm﹕ Could not find method org.apache.http.client.config.RequestConfig.custom, referenced from method com.mashape.unirest.http.options.Options.refresh
11-24 16:26:57.489  12605-12856/com.akqa.glass.recipie W/dalvikvm﹕ VFY: unable to resolve static method 1059: Lorg/apache/http/client/config/RequestConfig;.custom ()Lorg/apache/http/client/config/RequestConfig$Builder;
11-24 16:26:57.489  12605-12856/com.akqa.glass.recipie D/dalvikvm﹕ VFY: replacing opcode 0x71 at 0x0020
11-24 16:26:57.489  12605-12856/com.akqa.glass.recipie D/dalvikvm﹕ DexOpt: unable to opt direct call 0x0701 at 0x49 in Lcom/mashape/unirest/http/options/Options;.refresh
11-24 16:26:57.489  12605-12856/com.akqa.glass.recipie W/dalvikvm﹕ Exception Ljava/lang/NoClassDefFoundError; thrown while initializing Lcom/mashape/unirest/http/options/Options;
11-24 16:26:57.489  12605-12856/com.akqa.glass.recipie W/dalvikvm﹕ threadid=11: thread exiting with uncaught exception (group=0x416aabd8)
11-24 16:26:57.496  12605-12856/com.akqa.glass.recipie E/AndroidRuntime﹕ FATAL EXCEPTION: AsyncTask #1
    Process: com.akqa.glass.recipie, PID: 12605
    java.lang.RuntimeException: An error occured while executing doInBackground()
            at android.os.AsyncTask$3.done(AsyncTask.java:314)
            at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:355)
            at java.util.concurrent.FutureTask.setException(FutureTask.java:222)
            at java.util.concurrent.FutureTask.run(FutureTask.java:242)
            at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:240)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
            at java.lang.Thread.run(Thread.java:841)
     Caused by: java.lang.NoClassDefFoundError: org.apache.http.client.config.RequestConfig
            at com.mashape.unirest.http.options.Options.refresh(Options.java:45)
            at com.mashape.unirest.http.options.Options.<clinit>(Options.java:34)
            at com.mashape.unirest.http.HttpClientHelper.prepareRequest(HttpClientHelper.java:154)
            at com.mashape.unirest.http.HttpClientHelper.request(HttpClientHelper.java:131)
            at com.mashape.unirest.request.BaseRequest.asJson(BaseRequest.java:68)
            at com.akqa.glass.recipie.JSONParser.getCamFindJSON(JSONParser.java:41)
            at com.akqa.glass.recipie.RecipIE$CamFindRequest.doInBackground(RecipIE.java:287)
            at com.akqa.glass.recipie.RecipIE$CamFindRequest.doInBackground(RecipIE.java:275)
            at android.os.AsyncTask$2.call(AsyncTask.java:302)
            at java.util.concurrent.FutureTask.run(FutureTask.java:237)
            at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:240)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
            at java.lang.Thread.run(Thread.java:841)
11-24 16:26:57.520  12605-12860/com.akqa.glass.recipie D/PARSER﹕ Inside Parser
11-24 16:26:57.520  12605-12860/com.akqa.glass.recipie I/dalvikvm﹕ Rejecting re-init on previously-failed class Lcom/mashape/unirest/http/options/Options; v=0x0
11-24 16:26:57.528  12605-12860/com.akqa.glass.recipie W/dalvikvm﹕ threadid=13: thread exiting with uncaught exception (group=0x416aabd8)
11-24 16:26:57.528  12605-12860/com.akqa.glass.recipie I/Process﹕ Sending signal. PID: 12605 SIG: 9

+1

+1
also getting these messages from gradle:

Warning:Dependency org.apache.httpcomponents:httpclient:4.3.6 is ignored for debug as it may be conflicting with the internal version provided by Android.
In case of problem, please repackage it with jarjar to change the class packages
Warning:Dependency org.apache.httpcomponents:httpclient:4.3.6 is ignored for debug as it may be conflicting with the internal version provided by Android.
In case of problem, please repackage it with jarjar to change the class packages
Warning:Dependency commons-logging:commons-logging:1.1.3 is ignored for debug as it may be conflicting with the internal version provided by Android.
In case of problem, please repackage it with jarjar to change the class packages
Warning:Dependency org.apache.httpcomponents:httpclient:4.3.6 is ignored for debug as it may be conflicting with the internal version provided by Android.
In case of problem, please repackage it with jarjar to change the class packages
Warning:Dependency org.json:json:20140107 is ignored for debug as it may be conflicting with the internal version provided by Android.
In case of problem, please repackage with jarjar to change the class packages
Warning:Dependency org.apache.httpcomponents:httpclient:4.3.6 is ignored for release as it may be conflicting with the internal version provided by Android.
In case of problem, please repackage it with jarjar to change the class packages
Warning:Dependency org.apache.httpcomponents:httpclient:4.3.6 is ignored for release as it may be conflicting with the internal version provided by Android.
In case of problem, please repackage it with jarjar to change the class packages
Warning:Dependency commons-logging:commons-logging:1.1.3 is ignored for release as it may be conflicting with the internal version provided by Android.
In case of problem, please repackage it with jarjar to change the class packages
Warning:Dependency org.apache.httpcomponents:httpclient:4.3.6 is ignored for release as it may be conflicting with the internal version provided by Android.
In case of problem, please repackage it with jarjar to change the class packages
Warning:Dependency org.json:json:20140107 is ignored for release as it may be conflicting with the internal version provided by Android.
In case of problem, please repackage with jarjar to change the class packages

I am also facing the same issue...:(
any fix..??

+1
any fix??

+1

Three years and no response...

+1

We are now on Apache HttpClient 4.5.6. Not sure if this is still an issue or what Unirest could even do about it if it's a Apache problem


PCI Bracket for ATX connection [SUGGESTION]

Since the KVM will usually be outside of the server, there is no clean way to run the ATX power breakout cables to the motherboard.
Do you know/can you recommend a PCI bracket that can pass through the ATX power connector?
I'm assuming a simple 8 pin male-to-male connector block mounted to a PCI bracket should do the trick, but I have not found one on AliExpress yet.
Otherwise, everything else is great! I would use the CM4 eMMC so I don't have to depend on an SD card, and looking forward to a POE version. I would prefer this for datacenter and remote office deployments over the normal KVM.
I do recommend forking the PiKVM repo to prebuild images with Github Actions, so that we have images that are known to work with the hardware stack (in case you need to include some custom drivers or code, or PiKVM upstream does something stupid and poisons their codebase - like colors.js and faker).

look this https://github.com/ThomasVon2021/pikvm-atx-adapter

LOL you should probably link to that near the top of the README.
Awesome though!

It looks like the ATXA-A adapter card does not fit in the Blikvm shell, so I just need to know if I should design and 3D print a case for the adapter.
Thanks,
Bryan

Sorry, this is a hardware design problem, you currently need to 3D print the shell for ATX-A, the interface will be unified later
At 2022-01-31 08:50:13, "Bryan Vaz" @.***> wrote:
Ok stupid question: Do you have a case for the ATXA-A adapter?
It looks like the ATXA-A adapter card does not fit in the Blikvm shell, so I just need to know if I should design and 3D print a case for the adapter.
Thanks,
Bryan
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


ServiceFabricDeploy should support dynamic application names

Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: ServiceFabricDeploy
list here (V# not needed):
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks/ServiceFabricDeployV1
Environment

Server - Azure Pipelines
Account: WKAxcess
Team Project: Axcess
Deffinition: 2379

Agent - Hosted
Hosted Windows 2019 with VS2019

Issue Description
Service fabric can create dynamic applications (based on "root" applications) but there is no way to update them.
Task logs
[Enable debug logging and please provide the zip file containing all the logs for a speedy resolution]
Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Error logs
[Insert error from the logs here for a quick overview]

Hi @henry-padilla, sorry I don't get it. Can you explain a bit more about the bug, also can you provide logs??

I cannot provide logs for something the task doesn't do.
We have a Service Fabric Application that we copy to create several dynamic Applications. There is currently no way to update those dynamic applications.
Given an application "AppRoot" if you deploy that to Service Fabric you will have an ApplicationType "AppRootType" and an application "AppRoot". If I use "AppRoot" to create a new application called "AppRoot-001" and "AppRoot-002" those will run fine.
But when I upgrade "AppRoot" to version 1.5 it doesn't upgrade "AppRoot-001" nor "AppRoot-002". The best I can do is to remove those and have the system recreate them. But if they are doing work I can't just remove them.
Does that help?


Allow for managing what UIs are available

Description
Allow to configure UIs by setting relevant flags in params: chatEnabled, pushEnabled and settingsEnabled.  They are enabled by default.
If only one is enabled, the sidebar is hidden.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Draft PR (breaking/non-breaking change which needs more work for having a proper functionality [Mark this PR as ready to review only when completely ready])
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Fixes/Resolves
Fixes #101
Checklist:

[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] Any dependent changes have been merged and published in downstream modules

Additional Information
Note: Even if chatEnabled=false, a chatProvider=external must still be provided as the chat proxy is what handles accounts, for now.

Turbo fire great to see there's a router here now too.
All worked as expected while testing, but one concern I did have is that once the sidebar goes you also lose access to the profile options behind the icon:
Maybe not prio for w3i SDK usage but may be something we need to account for eventually.

The case where someone manually disabled web3inbox's pages in desktop mode is beyond rare, but can definitely look into accounting for it in the future


Rewrite front end to work using AngularJS.

What is a quick description of the change?
These changes establish a file structure and organization for the front end of the project using AngularJS modules and components.
The front end is now split into 4 modules, with 4 components:

The navigation module, which contains the header and navBar components.
The directoryPage module, which contains the directoryPage component.
The candidatePage module, which contains the candidatePage component. The previous commit had 3 separate components within this module, but they have been combined to avoid having to retrieve data from the database more than once.

These three modules are contained within the larger voterCentral module, which encompasses the entire AngularJS app. All components except the navBar and header components also have corresponding template files (the templates for these two are embedded).
This code can now be automatically merged, as it works with the most recent version on master.
Is this fixing an issue?
none
Are there more details that are relevant?
none
Check lists (check x in [ ] of list items)

[  ] Test written/updating
[X] Tests passing
[X] Coding style (indentation, etc)

Please explain why any are not present, if any.
Any additional comments?
{Fill in here or remove (leave question)}

I pushed a fix to the form on the index page which should change how things redirect to the directory page. Let me know if everything is still breaking... it all works for me locally so that's pretty concerning.

Oh, I didn't know that. Wouldn't that mean you all have to download it locally? It's pretty easy, I can link a tutorial.

Can you add the "download angular" instructions/command to the relevant readme?

Should be done now!


Refactor: Move APIs from Page Router to App Router

What changed? Why?

Refactored the API backend from the pages router to app router.
I did notice some of these errors (but the build runs and passes)

Generating static pages (0/10)  [    ]Error fetching chains: eS [Error]: Dynamic server usage: Page couldn't be rendered statically because it used nextUrl.searchParams. See more info here: https://nextjs.org/docs/messages/dynamic-server-error
Fixed this with : REF
export const dynamic = 'force-dynamic';
Notes to reviewers

I was unable to get to unit tests working.  Ran into issues mocking next/server, going to dig in another time when I have some more capacity.
I figure getting the pattern is more critical than unit tests, so getting this merged up so we can move forward.

How has it been tested?

Tested all of the API routes + Signature Mint pages.

Dope


Connect Login with Backend and Mongodb

Describe the bug
Connect Login with Backend [ if backend  is working  otherwise re-write fully backend ] .
and use is login remove login button and add logout button

please assign me
i will give you within 1 day

its already connected , i just have not enabled it by adding mongo db uri


Branch 17

Modify link to local file for fire_url

Discussed the issue with @Rz02 and it looks good. Can be merged!


Remove the Contract tab on Order details page for off-chain transactions

This tab is not relevant when the system operates in off-chain mode. Currently the tab shows "Loading..."
We should display the tab conditionally on the system operating in off vs on-chain mode.


Adding QK emulation initial experiment vignette. More needs to be done

Just adding my initial Quantile kriging test markdown.
I think I did everything right following https://uq4covid.github.io/vignettes/guide-to-posting-vignettes
But I'm not super familiar with github or markdown, so not certain

Thinks thats done now?


User should be able to save project contract as draft

Describe the task
Check the existing contract module and analyze it by referring to the database we're using to create the contract mentioned above. If modifications are required, make the necessary adjustments such as dropping or updating contract table migrations and creating new table migrations that are needed. Update the contract form according to the new table fields using database queries and backend functionality, and enable the ability to save it as a draft.
Expected behavior
User would be able to save contract as draft.
References
Use this issue #3151 for getting more insight about feature and for referring database and working flow.

All functionality are merged in this issue #3151.
So closing this issue.


请问这个代码有对应的参考文献吗

您好，想对照文献学习一下，请问是否有参考文献

可以参考：[1] Waveform Design and Signal Processing Aspects for Fusion of Wireless Communications and Radar Sensing
[2] Performance analysis of joint radar and communication using OFDM and OTFS


Update helm chart script

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
It helps to sync files from RBAC folder
Which issue(s) this PR fixes:

Fixes #926
Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

/ok-to-test

/lgtm

/retitle Automatically sync RBAC files in helm chart


The denoised image of the test is displayed in full black

May I ask whether the input CT and CBCT are denoised and de-denoised according to the one-dimensional gray image input into the Dataloader?
After noise is predicted using GaussianDiffusionTrainer in Diffusion_condition.py provided by the author, GaussianDiffusionSampler is used to remove noise from the verification set. The result picture is shown as all black. Does the author have this problem?

请问from Diffusion import GaussianDiffusionTrainer_cond中的Diffusion是作者自定义的脚本嘛？

May I ask whether the input CT and CBCT are denoised and de-denoised according to the one-dimensional gray image input into the Dataloader? After noise is predicted using GaussianDiffusionTrainer in Diffusion_condition.py provided by the author, GaussianDiffusionSampler is used to remove noise from the verification set. The result picture is shown as all black. Does the author have this problem?

Sorry for the late response.

For the model training, input CT and CBCT (into Dataloader) are both clean images, and the CT image will be perturbed by Gaussian noise in the trainer function.
I have not encountered the "all black" problem. Maybe you can provide more details about it.

请问from Diffusion import GaussianDiffusionTrainer_cond中的Diffusion是作者自定义的文件嘛？

Hi,
The module should be imported from "Diffusion_condition.py" and the script of train_condition.py has been updated. (Line 16).

Hello, may I ask if the input of ct is random noise during the test? Why the model is not stable during my test, sometimes it can generate normal images, and sometimes it generates all noise.
Thank you very much for your help.

Hello, may I ask if the input of ct is random noise during the test? Why the model is not stable during my test, sometimes it can generate normal images, and sometimes it generates all noise.
Thank you very much for your help.

Yes, the initial input of CT is a standard Gaussian noise during the inference stage. Could you provide more details about "sometimes it generates all noise"?

请问from Diffusion import GaussianDiffusionTrainer_cond中的Diffusion是作者自定义的文件嘛？

你好，
该模块应从“Diffusion_condition.py”导入，并且 train_condition.py 的脚本已更新。 （第 16 行）。

Sorry,I mean that the introduced GaussianDiffusionTrainer_cond is not declared in the Diffusion_condition.py file.
GaussianDiffusionTrainer_cond==GaussianDiffusionTrainer?
please

请问from Diffusion import GaussianDiffusionTrainer_cond中的Diffusion是作者自定义的文件嘛？

你好，
该模块应从“Diffusion_condition.py”导入，并且 train_condition.py 的脚本已更新。 （第 16 行）。

Sorry,I mean that the introduced GaussianDiffusionTrainer_cond is not declared in the Diffusion_condition.py file. GaussianDiffusionTrainer_cond==GaussianDiffusionTrainer? please

Sorry, the class name was wrong and it has been corrected

Hello, I trained and saved the model through GaussianDiffusionTrainer, but my training set is in png format instead of npy format, but I converted it. For the test code GaussianDiffusionSampler, how should I write it for testing? Are the test inputs still cbct and ct?

Hello, may I ask if the input of ct is random noise during the test? Why the model is not stable during my test, sometimes it can generate normal images, and sometimes it generates all noise.
Thank you very much for your help.

Yes, the initial input of CT is a standard Gaussian noise during the inference stage. Could you provide more details about "sometimes it generates all noise"?

Hello, may I ask whether it is reasonable to return torch.clip(x_0, -1,1) in GaussianDiffusionSampler during the test? x_0 contains cbct and generated ct. The range of cbct is [-1,1], but the range of generated ct in my test is all less than -1. As a result, the generated image is all black, I modified the code as follows, but the generated image is not stable, most of the time is noise, and occasionally it can be faintly seen.
x_0 = x_0[:, 0, :, :]
min_val = x_0.min()
max_val = x_0.max()
normalized_tensor = (x_0 - min_val) / (max_val - min_val) * 2 - 1
Thank you very much for your help

Hello, may I ask if the input of ct is random noise during the test? Why the model is not stable during my test, sometimes it can generate normal images, and sometimes it generates all noise.
Thank you very much for your help.

Yes, the initial input of CT is a standard Gaussian noise during the inference stage. Could you provide more details about "sometimes it generates all noise"?

Hello, may I ask whether it is reasonable to return torch.clip(x_0, -1,1) in GaussianDiffusionSampler during the test? x_0 contains cbct and generated ct. The range of cbct is [-1,1], but the range of generated ct in my test is all less than -1. As a result, the generated image is all black, I modified the code as follows, but the generated image is not stable, most of the time is noise, and occasionally it can be faintly seen.
x_0 = x_0[:, 0, :, :] min_val = x_0.min() max_val = x_0.max() normalized_tensor = (x_0 - min_val) / (max_val - min_val) * 2 - 1
Thank you very much for your help 你好，请问在测试期间返回GaussianDiffusionSampler中的torch . clip（x _ 0，-1，1）是否合理？x_0包含cbct和生成的ct。cbct的范围是【-1，1】，但是在我的测试中生成的ct的范围都小于-1。结果生成的图像全黑，我修改了如下代码，但生成的图像并不稳定，大部分时间都是噪点，偶尔还能隐约看到。x_0 = x_0【:，0，:】min _ val = x _ 0 . min（）max _ val = x _ 0 . max（）normalized _ tensor =（x _ 0-min _ val）/（max _ val-min _ val）* 2-1非常感谢您的帮助

我不清楚作者的代码部分是否完全正确 我在GaussianDiffusionSampler也出现了一些错误，可以加q1121269990讨论下

@QijingGJ Hello, I'm currently reproducing this work, but I'm having trouble writing test code, I don't know if I can communicate with you, here's my email<EMAIL_ADDRESS>or if you have QQ, this is my QQ:<PHONE_NUMBER>

Hello, may I ask if the input of ct is random noise during the test? Why the model is not stable during my test, sometimes it can generate normal images, and sometimes it generates all noise.
Thank you very much for your help.

Yes, the initial input of CT is a standard Gaussian noise during the inference stage. Could you provide more details about "sometimes it generates all noise"?

Hello, may I ask whether it is reasonable to return torch.clip(x_0, -1,1) in GaussianDiffusionSampler during the test? x_0 contains cbct and generated ct. The range of cbct is [-1,1], but the range of generated ct in my test is all less than -1. As a result, the generated image is all black, I modified the code as follows, but the generated image is not stable, most of the time is noise, and occasionally it can be faintly seen.
x_0 = x_0[:, 0, :, :] min_val = x_0.min() max_val = x_0.max() normalized_tensor = (x_0 - min_val) / (max_val - min_val) * 2 - 1
Thank you very much for your help 你好，请问在测试期间返回GaussianDiffusionSampler中的torch . clip（x _ 0，-1，1）是否合理？x_0包含cbct和生成的ct。cbct的范围是【-1，1】，但是在我的测试中生成的ct的范围都小于-1。结果生成的图像全黑，我修改了如下代码，但生成的图像并不稳定，大部分时间都是噪点，偶尔还能隐约看到。


Remove process_ and go_ debug metrics by default.

Remove process_ and go_ debug metrics by default.
If a customer, or developer is interested in these metrics they can comment out the required lines in collector.go and make their own build of the OME.
Now, it may be useful to tie is back to get --debug flag at some point, but right now i don't think this will required.

This has been disabled already in the FA OME


doc(kubernetes): update configuring auto-instrumentation for nodejs

What needs to be changed?
After this merged PR is released, documentation about no way to configure auto-instrumentations becomes outdated
What is the name + path of the page that needs changed?

The relative path: content/en/docs/kubernetes/operator/automatic.md
page: Kubernetes Operator / Auto-instrumentation -> Configure Automatic Instrumentation > Node.js > Excluding auto-instrumentation

Additional context:
It becomes outdated after the next release of opentelemetry-operator.

Thanks, so it sounds like it can be changed to say something to the effect of:
"You can include only specific instrumentations by using the OTEL_NODE_ENABLED_INSTRUMENTATIONS environment variable. For example, here's how you can include only http and nestjs-core instrumentations:
export OTEL_NODE_ENABLED_INSTRUMENTATIONS="http,nestjs-core"

"

Seems that this task was already done in this PR and can be closed.

Ah yes, but there were some outstanding points with that PR (I assumed this issue is the follow up to that), let me double check on that.

Here's what's missing but indeed that should be an issue on it's own while this one here is closed, apologies for overlooking that
https://github.com/open-telemetry/opentelemetry.io/pull/4137#discussion_r1560953944
(this follow up issue is a little bit more complicated since we need to see that also the JS repo will be updated accordingly)


Add What is Utreexo? episode (7 of 14)

This is part of https://github.com/bitcointranscripts/bitcointranscripts/issues/407.
Original file: 15.txt
Added titles.
Cleaned Language fillers.

Thank you @edilmedeiros! I added a missing speaker name and removed the bitcoin-core tag.
I'm also currently experimenting with using AI to create summaries and chapters for the transcripts, so I also added an AI-generated summary to this one, as well as a couple of extra chapters.

Thank you @edilmedeiros! I added a missing speaker name and removed the bitcoin-core tag. I'm also currently experimenting with using AI to create summaries and chapters for the transcripts, so I also added an AI-generated summary to this one, as well as a couple of extra chapters.

What tool are you using for the summaries?


Errors Thrown from jQuery – Linting?

Hi there,
A super noob here – sorry.
I sent the following email to JQuery with the associated response.
Am I asking the right question?
Hi There,
Super noob here.
I am trying to run jQuery JavaScript Library v1.11.3 in Brackets on OS X.
When I open the file in Brackets to sight the code there is a litany of errors thrown.
eg: 'module' was used before defined
Combine this with the previous statement
Expected 'jQuery' at column 9, not column 5
There are more than 50 errors. Brackets stops looking after 50.
I must be doing something very wrong here???
screen grab available here:
http://www.leapfrog.net.au/client/lincoln/Screen Shot 2015-08-17 at 2.39.21 am.png
Any guidance would be greatly appreciated.
Trev
Re: errors thrown in Brackets
14 minutes ago
Don’t use jslint against jQuery source. You could contact the brackets people to find the setting to stop linting jQuery.
JΛ̊KE

@10polarbears As you might be aware- JSLint is a static code analysis tool used in software development for checking if JavaScript source code complies with coding rules. You may want to address them for better compliance with JavaScript coding standards.
However, if you are sure that your code doesn't contain other errors and you don't want to be bothered by linting errors, you can disable JSLint by:-

Click on Debug > Open Preferences File.
Disable JSLint by adding the following line as preference to the brackets.json preferences file- "linting.enabled": false, . In case you add this preference as the last line, make sure you don't add the comma at the last.
Now, you should not be bothered by Linting errors. Later, if you want to re-enable JSLint, you can either set the linting.enabled preference to true or just delete the preference to apply the default linting preference.

Firstly thank so very much for you explanation and help.
That certainly did the trick once I added the recommend line.
It does raise one question though.
What to do about JSON.
Because of your answer I am now starting to look in the right places for answers.
Here I find the remanded prefs for JSON which have linting on and collapsed off.
Default Preferences (JSON)
{
    "useTabChar": false,
    "tabSize": 8,
    "spaceUnits": 4,
    "closeBrackets": false,
    "showLineNumbers": true,
    "styleActiveLine": false,
    "wordWrap": false,
    "linting.enabled": true,
    "linting.collapsed": false,
    "quickview.enabled": true
}

Would it be true to say that if I am using JQuery and JSON then both "linting.collapsed" and "linting.enabled" should be set to false?
Thank you again.

I would not recommend to disable the linting feature, but better to use an alternative linter like ESLint instead of the bundled JSLint.
It should be sufficient to set linting.enabled to false to disable the linter.


Expected timestamp not accurate for external contracts

job.deliveryTime is not accurate when on an external contract job.

This seems to be an issue with the scs-sdk-plugin.
I added a temporary fix in e409110 that sets the values to 0.

This seems to be an issue with the scs-sdk-plugin.
I added a temporary fix in e409110 that sets the values to 0.


Make Problem

Hello
I have problem with make command...
root@ubuntulab:~/Dokumenty/keyhunt# make
g++ -O3 -c oldbloom/bloom.cpp -o oldbloom.o
g++ -O3 -c bloom/bloom.cpp -o bloom.o
gcc -O3 -c base58/base58.c -o base58.o
gcc -O3 -c rmd160/rmd160.c -o rmd160.o
g++ -O3 -c sha3/sha3.c -o sha3.o
g++ -O3 -c sha3/keccak.c -o keccak.o
gcc -O3 -c xxhash/xxhash.c -o xxhash.o
g++ -O3 -c util.c -o util.o
g++ -m64 -mssse3 -Wno-unused-result -Wno-write-strings -O2 -c secp256k1/Int.cpp -o Int.o
g++: error: unrecognized command-line option ‘-m64’
g++: error: unrecognized command-line option ‘-mssse3’
make: *** [Makefile:10: default] Error 1
my pc
root@ubuntulab:~/Dokumenty/keyhunt# lscpu
Architecture:            aarch64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                  1
On-line CPU(s) list:   0
Vendor ID:               ARM
Model name:            Neoverse-N1
Model:               1
Thread(s) per core:  1
Core(s) per cluster: 1
Socket(s):           1
Cluster(s):          1
Stepping:            r3p1
BogoMIPS:            50.00
Flags:               fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp
asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
NUMA:
NUMA node(s):          1
NUMA node0 CPU(s):     0
Vulnerabilities:
Itlb multihit:         Not affected
L1tf:                  Not affected
Mds:                   Not affected
Meltdown:              Not affected
Mmio stale data:       Not affected
Retbleed:              Not affected
Spec store bypass:     Mitigation; Speculative Store Bypass disabled via prctl
Spectre v1:            Mitigation; __user pointer sanitization
Spectre v2:            Mitigation; CSV2, BHB
Srbds:                 Not affected
Tsx async abort:       Not affected
Can i run keyhunt on this VPS ?
How can i fix this ??

ARM architecture - not compile.

I tried it on Ubuntu with Parallels on M1 and I'm looking for a solution for the same error.

it is due to doublings in code. alberto also not known about this error. but hope so, he will help.


SyntaxError: Non-ASCII character

I'm getting this error:
Traceback (most recent call last):
  File "/home/travis/.local/bin/travis-wait-improved", line 6, in <module>
    from travis_wait_improved.sherpa import main
  File "/home/travis/.local/lib/python2.7/site-packages/travis_wait_improved/sherpa.py", line 29
SyntaxError: Non-ASCII character '\xe2' in file /home/travis/.local/lib/python2.7/site-packages/travis_wait_improved/sherpa.py on line 29, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details

.travis.yml:
  ...
  before_deploy:
    - pip install travis-wait-improved --user
    deploy:
      skip_cleanup: true
      provider: script
      script: travis-wait-improved --timeout 30m bash scripts/travis_deploy.sh
      on:
        all_branches: true
  ...

When I tried without --user:
Could not install packages due to an EnvironmentError: [Errno 13] Permission denied: '/usr/local/lib/python2.7/dist-packages/docopt.py'
Consider using the `--user` option or check the permissions.

Cause is probably ❱ character:
# line 29 in sherpa.py
HEADER = colored("Travis-wait ❱", "magenta", attrs=["bold"])

@Amit-A Thank you for taking the time to contribute. I see that your environment appears to be using Python 2.7, but this tool was written for Python 3.6+. Even if the special character was replaced you would run into issues with the f-strings used later on in the tool.

Feel free to reopen this issue if you believe it is still a relevant change given the context I added.


Please send events of changes caused by user interaction.

It would be very helpful / valuable if the component would send events about changes.
thank you!
It would be very helpful / valuable if the component would send events about changes which are caused by user interaction.
i.e. a  view-changed event with x, y, lat, lon, zoom, ... would make the component directly usable as an input component.

Reflecting the changes to the ol-map would be nice too.

Hello @veith. Thank you for your suggestions. I think I would approach this in two ways.
First instances of OlMap have a set of their native event, which I could simply forward from the ol-map element. For example, moveend could be used like
<ol-map @on-moveend="${onMoveend}></ol-map>

<script>
  function onMoveend(event) {
    // The MapEvent provided in the detail object
    const rawEvent = event.detail
  }
</script>

The other idea is to provide a more targeted events, rewired from the native ones. The `view-changed` which you propose for one

Please see the demo built off PR #68: https://events--openlayers-elements.netlify.app/#/elements/ol-map/demos/demo/ol-map/
In the console you will see the ol-map log events moveend and view-change

Reflecting the changes to the ol-map would be nice too.

I'm not sure how great we can make this. I added a change event, simply forwarded from the OpenLayers objects. Right now it will be fired by the map and layer elements.


[Bug]: Not receiving status updates when Let apps access your location is toggled ON

Please check the following before submitting a new issue.

[X] I have searched the existing issues.
[X] I have carefully read the documentation and verified I have added the required platform specific configuration.

Please select affected platform(s)

[ ] Android
[ ] iOS
[ ] Linux
[ ] macOS
[ ] Web
[X] Windows

Steps to reproduce

Start Listening to getServiceStatusStream()
Go to Location Privacy Settings (initial state, all items are toggled ON)
Toggle Let apps access your location as OFF
Event is triggered
Toggle Let apps access your location as ON
Event is NOT triggered

Expected results
getServiceStatusStream() should receive status updates
Actual results
getServiceStatusStream() did NOT receive status updates
Code sample
Code sample
    Geolocator.getServiceStatusStream().forEach((element) async {
      var permission = await Geolocator.checkPermission();
      var noPermissions = ![
        LocationPermission.whileInUse,
        LocationPermission.always
      ].contains(permission);

      noPermissions
          ? _pushState(AppState.permissions)
          : _popState(AppState.permissions);
      notifyListeners();
    });

Screenshots or video

Screenshots or video demonstration
[Upload media here]

Version
9.0.2
Flutter Doctor output
Doctor output
[√] Flutter (Channel stable, 3.10.6, on Microsoft Windows [Version 10.0.25921.1000], locale en-AE)
    • Flutter version 3.10.6 on channel stable at C:\src\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f468f3366c (5 weeks ago), 2023-07-12 15:19:05 -0700
    • Engine revision cdbeda788a
    • Dart version 3.0.6
    • DevTools version 2.23.1

[√] Windows Version (Installed version of Windows is version 10 or higher)

[√] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at C:/Android/Sdk
    • Platform android-33, build-tools 33.0.0
    • ANDROID_SDK_ROOT = C:/Android/Sdk
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Community 2022 17.6.2)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
    • Visual Studio Community 2022 version 17.6.33723.286
    • Windows 10 SDK version 10.0.22621.0

[√] Android Studio (version 2021.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[√] IntelliJ IDEA Community Edition (version 2022.2)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2022.2.2
    • Flutter plugin version 71.2.5
    • Dart plugin version 222.4167.21

[√] VS Code (version 1.72.0)
    • VS Code at C:\Users\User\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.60.0

[√] Connected device (4 available)
    • SM A205S (mobile) • adb-R59N1086LVT-yGSzP7._adb-tls-connect._tcp. • android-arm64  • Android 11 (API 30)
    • Windows (desktop) • windows                                       • windows-x64    • Microsoft Windows [Version 10.0.25921.1000]
    • Chrome (web)      • chrome                                        • web-javascript • Google Chrome 115.0.5790.171
    • Edge (web)        • edge                                          • web-javascript • Microsoft Edge 115.0.1901.203

[√] Network resources
    • All expected network resources are available.

I provided PR for this issue https://github.com/Baseflow/flutter-geolocator/pull/1307 since I already found the cause.

This should be fixed in version 0.1.3 of the geolocator_windows plugin, which was published earlier today.


In generator-react-server  v0.4.2  dependencies  "react-server": "^0.3.4" !

After updating to v0.4.2, package.json remained in the old version.

closed in #541


Fix MegaLinter issues

Description of proposed changes

Practical tips for PR review & merge:

[ ] All GitHub Actions report PASS
[ ] Newly added code/functions have unit tests

[ ] Coverage tools report all newly added lines as covered
[ ] The positive scenario is exercised
[ ] Negative scenarios are exercised, e.g. assert on all possible errors
[ ] Assert on events triggered if applicable
[ ] Assert on changes made to storage if applicable

[ ] Modified behavior/functions - try to make sure above test items are covered
[ ] Integration tests are added if applicable/needed

Codecov Report

Merging #1380 (c81b74c) into dev (a3cb44b) will decrease coverage by 1.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              dev    #1380      +/-   ##
==========================================
- Coverage   71.08%   70.02%   -1.06%
==========================================
  Files         107      107
  Lines       12553    12553
  Branches      128      128
==========================================
- Hits         8923     8790     -133
- Misses       3620     3763     +143
+ Partials       10        0      -10

see 7 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Make max size optional

Now you can configure bundlesize with path alone.
"bundlesize": [{ "path": "./index.js" }]

or
bundlesize -f index.js

This means your build will always pass, but it will give the comparison with master as a message/warning.

Published as<EMAIL_ADDRESS>


Create GCP Project with new email

Made the project https://console.cloud.google.com/home/dashboard?authuser=3&organizationId=0&project=healthy-eating-project-359101
The email for login is our healthy eating email.


[Feature Request]

Hey dude, I've been using this module for a while now and it's amazing, really love it. However there's one little thing that bothers me a bit, don't even know if this could be called a feature request, but doesn't feel like a bug either. When I first load my world it takes a few seconds for the theme to pop in and replace the standard one resulting in a very annoying lagging - which doesn't last long - my worry is that some lower end machines of my players won't handle this very well and might crash the browser. Is there anyway this issue could be optimized?

So there really isn't a good solution to this, because it basically won't initialize until Foundry is ready, which is after already loading the UI.
Technically I could hide the UI until Foundry is ready, but that causes issues if something crashes, you basically could get stuck and never be able to use the UI.
As for lower-end machines, this should never cause them to crash, but it can mean it would take longer for the theme to load. Trust me with the release of my Fantasy RPG UI, I've put some thought into making this transition smoother, but I haven't really thought of a smoother way.
If the main concern is crashing, that shouldn't be an issue and if it is crashing your players, please let me know, cause that is a bug. As for now, I currently really don't have a good solution to make the transition smoother.
Though please know, I've got a few idea's I want to try so I am not saying I don't plan to make improvements, I am just not sure if any of them will work without putting more stress on either the GM or players' side.


Add mosquitto broker auth to cluster manager and node engine

Fixes #357.
By using the override-mosquitto-auth.yml docker override the cluster orchestrator can be started in a manner such that MQTT communications are sent via TLS. To this effect the mosquitto/mosquitto.conf has to be configured and certificates have to be generated and provided correctly, see the README.
The node engine also accepts flags to specify the certificate and key file for MQTT over TLS communication, this is also documented in the cluster_orchestrator README.
Unfortunately the eclipse-mosquitto docker container, the python-paho-mqtt library and the go-paho-mqtt library implement different methods for providing the password to  certificate keyfiles (or none at all) which adds to the complexity of the instructions in the README.

Before this can be merged the cluster_service_manager image that is pulled in the docker compose will have to be updated to incorporate this PR

I can also specify
image: ghcr.io/oakestra/oakestra-net/cluster-service-manager:alpha-v0.4.302 in the override file. However that should be changed again when oakestra-net is released next

Thanks! The wiki is page on MQTT Authentication includes everything documented here.
Would you be able to answer my question on the docker packages? I'm unfamiliar with how this kind of problem is usually solved

Then regarding the packages, I updated the override with the custom CSM version to use the one with MQTT auth support. The rest should work as expected after the next release then.

After merging the systemd PR we have conflicts in the root.go cobra file. Can you check?

Fixed!

@Mjaethers Green light on my side :D awesome!! Feel free to merge when you want!


[Bug] Opimise the page loading cost

💻 系统环境 | Operating System
macOS
🐛 问题描述 | Bug Description
Opimise the page loading cost

🚦 期望结果 | Expected Behavior
open a page with less time < 1s.
📷 复现步骤 | Recurrence Steps
No response
📝 补充信息 | Additional Information
No response

/chat/bot/create 临时改为 /agent (https://github.com/kubeagi/agent-portal/pull/68)


Crosscompilation docs confusing / Ideas for LLVM stdenv

Problem
Either this is just my misunderstanding and/or different terminology in Nix, or the docs on crosscompilation here are wrong/misleading.
Proposal
I'm coming from the Bazel world where we also have have host, target and build (well, there it's called execution but whatever) platforms. The docs state that the host is the platform the target is run on. I believe this is incorrect. At least it misaligns with the terminology used in Bazel.
I believe it would be more appropriate to document crosscompilation something like this:

The host platform is the machine that invokes the build. For instance the developers laptop.
The build platform is the machine that executes the build. For instance a remote compile server.
The target platform is the machine that runs the final executable. For instance a mobile device.

For most users, host, build and executable will always be the same: We are building software for ourselves by ourselves, always on the same machine.
If host and target are the same, but build is different, we might be in a situation where for instance a developer requests  a remote execution server to create an executable for them. For instance because they are on a low-end device and the remote build server is a high-end device.
If host and build are the same, but target is different, we might be in a situation where a developer builds a mobile app locally.
If build and target are the same, but host is different, we are likely building a tool that is part of a toolchain that runs on the build platform. For instance a compiler that is built using other, lower level compilers for later (or immediate) use by the build platform.

(IMO it is incorrect to state that the target platform is the most irrelevant platform. It is in fact the host platform that is least relevant to the build, since it is just the platform that says "hello build platform please give me executable X for target platform Y".)

I've encountered this because I think the cross compilation support in nixpkgs is a bit unintuitive. I feel like nixpkgs is mixing up platforms and configurations a bit and this might be a reason why e.g. the LLVM stdenvs are so hard to get working everywhere.
Maybe it would be worth considering a differentiation between platforms and toolchain configurations, similar to how Bazel does it. Every time I try to cross-compile something I have to build like half the world, which shouldn't be necessary because e.g. a Clang on x86-unknown-linux-gnu should be able to build libc++ for x64-unknown-linux-musl without first requiring a Clang built for musl. I might be doing something wrong, but my experiments with this would always first build a specific clang for musl, which should be unnecessary.
To me, attributes like platform.isDarwin make sense, but platform.useLLVM seems rather unintuitive to me: Whether we use LLVM as C++ toolchain for stdenv is part of a toolchain configuration and not really related to any platform. We can switch back and forth rather easily between Clang and GCC, i.e. we can choose whether we want to use LLVM or not, but we can't choose our operating system in the same way. We also can't choose our hardware with the same flexibility.
I hope this was not too verbose to read 😅 I kinda feel like the LLVM stdenv is running into the same issues that caused Bazel to deprecate crosstool and instead use Platforms/ToolchainTransitions/Configurations.
Checklist

[x] checked latest Nixpkgs manual (source) and latest NixOS manual (source)
[x] checked open documentation issues for possible duplicates (potentially related https://github.com/NixOS/nixpkgs/issues/28327 https://github.com/NixOS/nixpkgs/issues/106375)
[x] checked open documentation pull requests for possible solutions

cc @rrbutani

I'll have time to take another look at this later this weekend (and I just realized I forgot to post my reply to your other issue – sorry) but here are some quick thoughts:

I'm coming from the Bazel world where we also have have host, target and build (well, there it's called execution but whatever) platforms. The docs state that the host is the platform the target is run on. I believe this is incorrect. At least it misaligns with the terminology used in Bazel.

You are correct that there is a discrepancy. My understanding is:
For nixpkgs it's:
             build     → host      → target

For Bazel this lines up as:
 host      → execution → target

i.e. what Bazel calls the execution platform is analogous to what nixpkgs calls the build platform and bazel's target platform thus lines up with nixpkgs' host platform.
It's just "off by one"; i.e. for nixpkgs the final package set's build/host/target are "package oriented" whereas for Bazel it's more compiler oriented.
I know that for Bazel "host platform" generally means literally the platform the Bazel server and client are running on (for which nixpkgs has no direct equivalent because there isn't necessarily one machine nix derivations are being on as part of a package being built).
I'm confident that this is modeled appropriately in nixpkgs but I'm having trouble articulating how it maps back to the Bazel world. I believe host != execution/host != target's use case is primarily RBE toolchains/knowing where to run binaries? Which you'd model in nixpkgs just like cross-compilation (the build tools for your executors themselves come from a package set and if that package set's build platform is not the same, it's a cross-compilation). If you can share a concrete example where host platform in Bazel is used in constraints maybe we can work through what the nixpkgs analogue would be.
Not sure if you've already seen them but I think the docs here have some useful examples of how this plays out for various kinds of dependencies.
In particular, note that in nixpkgs' a compiler's target platform is the target it produces code for whereas its host platform is the platform the compiler runs on. For a package being compiled using the compiler these labels all shift: the package will use the compiler from the set of build packages; i.e. the package's buildPlatform, its hostPlatform is the compiler's targetPlatform.
This notion of having multiple nixpkgs instances that progressively slide their way to the build/host/target triple of your final package set is explained here and elsewhere in the manual better than I can articulate 🙂

(IMO it is incorrect to state that the target platform is the most irrelevant platform. It is in fact the host platform that is least relevant to the build, since it is just the platform that says "hello build platform please give me executable X for target platform Y".)

I believe this is in reference to the fact that most packages don't have a "target platform". Compilers do, because they produce native code, but most applications/libraries do not.

Every time I try to cross-compile something I have to build like half the world, which shouldn't be necessary because e.g. a Clang on x86-unknown-linux-gnu should be able to build libc++ for x64-unknown-linux-musl without first requiring a Clang built for musl. I might be doing something wrong, but my experiments with this would always first build a specific clang for musl, which should be unnecessary.

Maybe this is confusion caused by the cc-wrapper package having clang and the target triple in the name? Is it actually rebuilding clang/LLVM?
We actually handle specifically this scenario as you're describing; LLVM and clang (native cross-compilers) are not recompiled when you ask for, i.e. crossSystem.config = { useLLVM = true; ... }. If you share your experiments I'm happy to help debug.

To me, attributes like platform.isDarwin make sense, but platform.useLLVM seems rather unintuitive to me: Whether we use LLVM as C++ toolchain for stdenv is part of a toolchain configuration and not really related to any platform. We can switch back and forth rather easily between Clang and GCC, i.e. we can choose whether we want to use LLVM or not, but we can't choose our operating system in the same way. We also can't choose our hardware with the same flexibility.

The idea behind .useLLVM is that it's a property of a nixpkgs set instance; i.e. in an instance with hostPlatform.useLLVM, .stdenv is LLVM-backed. As you say, packages can (and do! chrome and firefox insist on LLVM for cross-lang LTO/PGO) pick other stdenvs.
I'll concede that "platform" is perhaps a bit misleading here (but system seems too narrow..).

I kinda feel like the LLVM stdenv is running into the same issues that caused Bazel to deprecate crosstool and instead use Platforms/ToolchainTransitions/Configurations.

I've encountered this because I think the cross compilation support in nixpkgs is a bit unintuitive. I feel like nixpkgs is mixing up platforms and configurations a bit and this might be a reason why e.g. the LLVM stdenvs are so hard to get working everywhere.

Having used cross-compilation setups in both Bazel and nixpkgs: there are definitely limitations to how cross in nixpkgs works (splicing isn't perfect, flakes conception of systems doesn't really mesh well with cross, etc) but on the whole I think it's actually modeled quite well; I think the big conceptual discrepancy here is the sliding scale of nixpkgs instances with different build/host/target platforms (in kind of the same way that Bazel transitions can modify the target platform for parts of your build graph/influence toolchain resolution).
Hopefully this provides some clarity or at least more things to read.
Definitely also feel free to ask questions in the NixOS matrix channels or to DM me; I'm very happy to answer questions and walk through examples.

We're following the autoconf definitions https://www.gnu.org/software/autoconf/manual/autoconf-2.68/html_node/Specifying-Target-Triplets.html

@rrbutani Thanks for your extensive answer! This cleared things up a lot for me. I also went over various Autotools-related docs on the topic and I now think I understand the difference. Regarding when rebuilds are triggered, I'm testing this ATM.
My actual use case is building RBE images with nix. At the moment the build caches of rules_ll invocations arent reproducible across machines. Roughly speaking my use case is building Bazel itself with Clang/LLVM and then creating a Container that contains that Bazel and a Clang/LLVM C++ toolchain so that we can use that as remote execution Docker image.
I'm close to getting it to work in a way that the Bazel remote execution toolchain 1:1 maps to a local nix dev environment. I believe that this actually makes it possible to build e.g. a cache up with CI and then pull artifacts from that cache for reuse with local, non-remote builds. Or with trusted parties, users could share caches across machines without the need for remote execution runners at all. Or something in between 😃
Almost works. Almost 😅 I'll let you know when this actually works and/or I have some code ready.
This is why I keep running into these complicated issues lol.

I'm going to close this because the main question has been answered.  Feel free to open new issues for any behavior you still think we should change.


Running std example with UI

I normally use the COE directly intead of using the UI, but I attempted to use the UI again today.
This video below shows the response I get, when trying to run the COE with the std example:
https://www.youtube.com/watch?v=YLdQyZFDYPg&feature=youtu.be
It also confused me that I can launch the coe multiple times, but not change the port.
I am unsure If these are bugs or me using the UI in a wrong way.

Martin,
Seems like you are running the 2.0.0 RC of the app with the 0.0.6 COE. Version 2 of the app only works with COE 0.1.2 or higher. Also, the only examples that currently work are 3 Watertanks and UAV. If you try to import from the app, they should be the only ones to appear.
Can you give it another try and reply back?

This is what I got when I upgraded the COE:
COE(Command line options: [port]

Version: 0.1.2
Now running on port 8082
Server started, Hit Enter to stop.

ERROR [NanoHttpd Request Processor (#1)] (RequestProcessors.java:251) - Internal error in initialization
java.lang.Exception: {WaterTank}-file:////home/martin/.config/INTO-CPS APP/intoCpsApp/tmp/install_temp/case-study_single_watertank/FMUs/singlewatertank-20sim.fmu: Illegal character in path at index 37: file:////home/martin/.config/INTO-CPS APP/intoCpsApp/tmp/install_temp/case-study_single_watertank/FMUs/singlewatertank-20sim.fmu
at org.intocps.orchestration.coe.json.InitializationMsgJson.getFmuFiles(InitializationMsgJson.java:163)
at org.intocps.orchestration.coe.httpserver.RequestProcessors.processInitialize(RequestProcessors.java:247)
at org.intocps.orchestration.coe.httpserver.RequestHandler.initialize(RequestHandler.java:280)
at org.intocps.orchestration.coe.httpserver.RequestHandler.handleRequest(RequestHandler.java:177)
at org.intocps.orchestration.coe.httpserver.NanoWSDImpl.serveHttp(NanoWSDImpl.java:36)
at fi.iki.elonen.NanoWSD.serve(NanoWSD.java:861)
at fi.iki.elonen.NanoHTTPD$HTTPSession.execute(NanoHTTPD.java:925)
at fi.iki.elonen.NanoHTTPD$ClientHandler.run(NanoHTTPD.java:192)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.URISyntaxException: Illegal character in path at index 37: file:////home/martin/.config/INTO-CPS APP/intoCpsApp/tmp/install_temp/case-study_single_watertank/FMUs/singlewatertank-20sim.fmu
at java.net.URI$Parser.fail(URI.java:2848)
at java.net.URI$Parser.checkChars(URI.java:3021)
at java.net.URI$Parser.parseHierarchical(URI.java:3105)
at java.net.URI$Parser.parse(URI.java:3053)
at java.net.URI.<init>(URI.java:588)
at org.intocps.orchestration.coe.json.InitializationMsgJson.getFmuFiles(InitializationMsgJson.java:160)
... 8 more

I know I would also need to update my examples, so I am aware of the reason for the error.
I noticed that the UI removes my old version of the COE, since it is using the same install folder and is using the name coe.jar. It would be nice to be able to have multi version of the COE, like normal package managers are able to handle. Like one for testing and one for development.
The way linux normally handles this is creating subfolders for each version.
So all files related to release 0.0.8 is stored in its own folder.
Also if UI 2.0 RC cannot use release 0.0.7 (COE - 0.0.6, overture 2.3.6 ....), it should not be possible to download it using this UI.
One could adapt a standard OS independent package manager to handle all the interdependency rules, to avoid writing it from scratch. But again I will not be the main user of the INTO-CPS app, since I like to control the process of running the COE manually.

I agree that it would be nice to cope with multiple versions and such. But the download manager was not really designed as a packager manager or something of the sort. It's just meant to be a little convenience tool to save the users the effort of manually downloading the various tools. That's also why it lets you download incompatible versions.
Personally, I don't like tools that download other tools so I never use it myself.
That said, the co-sim view in the app should probably detect and reject invalid COE versions.

I totally agree with your assessment on the UI.
I also like to download the individual parts myself.
A simple way to cope with multiple versions would be this:
I noticed the UI created the folder structure:
/home/martin/.config/INTO-CPS APP/intoCpsApp/tmp/install_temp
This would just need to be changed to:
/home/XX/.config/INTO-CPS APP/intoCpsApp/tmp/install_temp/r_0_0_8
/home/XX/.config/INTO-CPS APP/intoCpsApp/tmp/install_temp/r_0_0_7
/home/XX/.config/INTO-CPS APP/intoCpsApp/tmp/install_temp/r_0_0_6
/home/XX/.config/INTO-CPS APP/intoCpsApp/tmp/install_temp/r_0_0_5
/home/XX/.config/INTO-CPS APP/intoCpsApp/tmp/install_temp/r_0_0_4
Where /home/XX/ is the the XX user path in Linux.
One then selects one of the allowed release candidates (that is able to run with this UI release).
Then users will have matching versions of COE, Overture, Openmodellica ... for simulation.
This should be a solution that would work on all operating systems.
Again this is just a sugestion, that would make it easier for non-experienced users.

Hmm, I tried to change to the new versions of the example:
This was the error I got:
Error: Could not parse config.
Message: Error: ENOENT: no such file or directory, open '/home/martin/into-cps-projects/case-study_three_tank/Multi-models/Non-3D/Non-3D.mm.json'
Path: /home/martin/into-cps-projects/case-study_three_tank/Multi-Models/Non-3D/Experiment 1/Non-3D.coe.json

Try without spaces

Can you try without spaces?

Space in the path is not supported by the app. It keeps spaces as ' ' but it should be encoded as %20 according to http://stackoverflow.com/questions/1634271/url-encoding-the-space-character-or-20
This is also not handled in the Overture FMU tool wrapper.

I think the best approach would be to always use "Experiment_1" or "Experiment-1".

Agreed. See #153 for tracking the standardisation of example names.


Analog clock face ignores fontcolor

I have the hands updating, but I use an SVG for the clock face, and I think that will not work for color selection.  I am not that good at building graphics and transitions, so tabling this for someone else to look at.

What's the issue? The clock numbers on the face?

I think there are some good example of HTML/CSS analog clocks you could probably derive from. Probably have more control over things like fonts and colors?

Reverted code back to using the original clock model.  Need to replace the svg with fonts.

getting closer, but still not there :

Problem fixed.  Still need to rotate clock face, but font color is respected.


ISO 4217 Currency Code Service - Amendment number 173

Please find the following PUBLIC NOTICE from the Bank of Sierra Leone in regards the redenomination
of the Sierra Leonean LEONE (SLE/925) : https://www.six-group.com/dam/download/banking-services/interbank-clearing/en/news/public-notice-sierra-leone.pdf.
Change of country name
With immediate effect, the following minor correction is made to “Table A.1 – Currency and funds code list” (as advised by the ISO 3166 Maintenance Agency): TURKEY to TÜRKİYE

This first part of this amendment will have to be fixed either by removing SLL (on 31st March, 2023) or by introducing a new category for historic currencies (and change the category in due time).
The change from TURKEY to TÜRKİYE is just a documentation update (enum names are the alpha-2 codes).

Superseded by #320.


Broadlink MP1 Validation

Hello,
Broadlink MP1 (4 Outlet Power Strip) device seems to be working. Just saying as README declare it was not tested.
Get, Set actions
Get & Get actions are both working.
Small issue: One Set might be missed when changing 2+ sockets state 'at the same time' (like in screenshot below).

However, there are no issues when setting 2+ sockets state using one single Set block.
'Set from msg.payload' action
I could not make Set from msg.payload to work.
I tried to inject those 2 json payloads with no success.
{"state":{"s1":true}}

{"s1":true}

This happens with many node-red flows I have. I usually introduce a delay node with about 100 msecs on (for instance) the line going to s2. It's not ideal, but it gets around the issue which I think is a node-red issue and not really related to the nodes in question.

Hi @TomyCesaille - Thanks for the info, I'll mark it as working in the Readme.
For the set via msg.payload function, it needs to be in the following format as I understand it.
{
    "action": "setState",
    "state": false,
    "s1": true,
    "s2": true,
    "s3": false,
    "s4": false
}

As for the other issue, it's either the issue mentioned by @lotekjunky or possibly that the Broadlink unit can't respond to two subsequent requests that quickly.
Does it work if you do them serially? Or by setting each outlet using the message format above?

Hi @mlfunston, I tried your payload and it makes nodered crash.
Format might be good then, but this is leading to an exception.
24 Feb 19:20:18 - [red] Uncaught Exception:
24 Feb 19:20:18 - SyntaxError: Unexpected token u in JSON at position 0
    at Object.parse (native)
    at MP1._device.on (/data/node_modules/node-red-contrib-broadlink-control/nodes/MP1Node.js:58:84)
    at emitNone (events.js:86:13)
    at MP1.emit (events.js:185:7)
    at Socket.Device.cs.on (/data/node_modules/node-red-contrib-broadlink-control/nodes/Device.js:50:22)
    at emitTwo (events.js:106:13)
    at Socket.emit (events.js:191:7)
    at UDP.onMessage (dgram.js:548:8)

This is fine when assigning multiple SET in 1 flow serially.

I tried doing some tests separately on the code and it seems to work ok, but you need to include all 4 s parameters. If you want to change s1 and s3 for example, send the following:
{ "action": "setState", "state": false, "s1": true, "s2": false, "s3": true, "s4": false }
Only the switches marked with true will be changed to the state defined - false (off) in the case above.
Let me know if that works.

Updated in v1.0.8


Having minimal dependencies

Hi,
vcpkg.json doesn't allow to have minimal dependencies.
you can't specify qtbase[core,gui] for example.
How did you manage to overcome it?
Regards,
Alex

@abique this should be asked at vcpkg/issues.


Fix obj's name set in wrong order when importing

Fixes https://github.com/godotengine/godot/issues/94924

Thanks!


Add true JSON and YAML display options for events

I'm adding different options for displaying the events, aka "notations".
Original motivation: I got tired of looking at "qp-batch-summary" events, which are nested, and feeling lost.
So far, there's three notations:

"Flat", this is the current/old implementation, I left it alone for the most part. It's pretty readable, except if the event are nested. It is also not friendly to any automated parsing.
"JSON", json complaint format, for some events it's quite unreadable (the one with strings with multiple lines), but this could be a good option if you want to export events and want to process them in a separate application.
"YAML", yaml complaint format. It is very readable including nested events. And could still be read by automated parsing.

The notations have 2 forms: SingleLine and Free. Singleline is the one used by the main window, where only the first line is visible. Free can use as many newlines as wanted and it's used by the details window. I found that creating functions for each of these forms was easier than trying to special-case a lot of places in the formatting logic.
For future: The functions in QJsonUtils are begging for unit tests, I think I might do that next in a separate branch (finally unit tests for TLV!) before doing any further improvement in the notations.
Finally, some before/after images!
Simple event (not much change or improvement)
Before (Flat)

After (YAML)

Complex event (a lot of change)
Before (Flat)

After (YAML)

I don't think anyone depends or is attached to the Flat or JSON notations. But maybe someone is (?).
The YAML notation is set as the default right now, so everyone should switch automatically. We can know if someone requires the older notations if someone complains.
Another reason to not get rid of the notations just yet is that I'm sure there are some edge cases where the YAML notation is not 100% compliant. Example: Strings with ':', '\n', or '"" can be tricky. I would like to fix them after I put the unit tests in place, as it is very easy to fix something but break something else right now. (Right now, comparing the formatting between notations helps me test)


Support http/https proxies

In case you want to do it for symmetry: https://github.com/phoenixframework/esbuild/pull/27

Thank you! We are trying to keep up with all the awesome contributions! :)


MongoDB Migration gives authentication error on mongodb in ubuntu 14

I have an AWS machine where I have installed mongodb 3.2.7 and applied authentication there. Now when I call the migration scripts using the mongodb-migration library, it gives an authentication error saying that permission denied.
Please help.

are you able to connect to it manually? If you run from "localhost" maybe try localhost and <IP_ADDRESS>.

It runs perfectly fine on localhost. The problem comes when I try to run it on qa and production servers. I'm using mongoose to connect, however I even tried MongoClient, but it didn't work.
mongoose.connect("mongodb://{username}:{password}@localhost:27017/{dbName}?authMechanism=DEFAULT&authSource={authDB}");
This works well on localhost, but breaks on qa and production servers.

So it looks like this is not a migration module issue.
Have you tried connecting with an external client like mongohub or robomongo?

+1 to what @molszanski has said, so far I'm, not convinced it's this module's issue.
What happens @mehul-talentica when you run the code suggested above on the server?
mongoClient = require('mongodb').MongoClient
dbName = 'test'
url = "mongodb://localhost:27017/#{dbName}"
mongoClient.connect url, (err, dbConn) ->
	@dbConn.collection('posts').find {}, (err, posts) ->
		console.log posts

If it doesn't work the issue is with your setup.
Are you sure you run it on the same server the mongo instance is running on?
Should you use its public hostname instead of the localhost?

Closing due to lack of activity

@molszanski  my apologies for not replying fast.
The migrations work when there is no authentication. The moment I enable authentication, either on my local machine or production servers, the migrations fail, giving the following error.
Files [ '001-moveProfilePictureToUserObject.js' ]
{ [MongoError: not authorized on QS to execute command { find: "dbMigrations", filter: {} }]
name: 'MongoError',
message: 'not authorized on {dbName} to execute command { find: "dbMigrations", filter: {} }',
ok: 0,
errmsg: 'not authorized on {dbName} to execute command { find: "dbMigrations", filter: {} }',
code: 13 }
D:\path to project\node_modules\mongodb-migrations\node_modules\mongodb\lib\utils.js:98
process.nextTick(function() { throw err; });
^

I'm pretty sure this is the setup issue unrelated to this module.
As suggested above you need to test it without the migrations and confirm/reject the hypothesis that you can't connect to the DB from a stand-alone node.js script.

I'm able to connect the application to the DB after removing the migration script.

If you want me to debug your issue I need an isolated test-case:

the Mongo installation with auth that I can connect to from my computer
(so you need to send me the connection string) - to ensure the DB is
accessible and be able to see what happens to the migrations collection
the repository that consists of a single script that connects to the DB,
finds the records in some collection and prints them to the console - to
see how the normal connection (raw mongodb driver, or an orm like mongoose)
a single migration in the same repository that does the same and fails
with the error that you've described

I'll be back from holidays in 2 weeks and can check it then.
You can use my email from the profile to send me the sensitive info (DB
connection string).
On Tue, Dec 20, 2016 at 11:56 AM Mehul Sayani<EMAIL_ADDRESS>wrote:

I'm able to connect the application to the DB after removing the migration
script.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/emirotin/mongodb-migrations/issues/27#issuecomment-268189455,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgGCAW1QaF-oL9QYpRRf4JzCcDK7bUkks5rJ5hDgaJpZM4K-x3r
.

Sure. Thanks mate!

Without debugging I have only one guess. Is it possible that the dbMigrations collection has some specific permissions that do not allow the user you use for migrations to run operations on it?
I see that mongo allows collection-level access control (https://docs.mongodb.com/v3.2/core/collection-level-access-control/), so is it possible, for example, that you've created the table yourself using the "master" account, and use the account with different permissions to access it?
Or maybe you don't have the collection in place and your user account doesn't have permissions to create it (normally it will be auto-created on the first write attempt)?


Update basepunkorg.yaml

/validate 3213e0283cbf230f612e3a79c81285f4b470eda0

Thank you
On Wed, Jun 5, 2024 at 7:59 PM Carl Cervone @.***> wrote:

@ccerv1 approved this pull request.
Looks good!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


fix: D1 execute and backup commands improvements

Better and faster handling when importing big SQL files using execute --file
Increased visibility during imports, sends output with each batch API call
Backups are now downloaded to the directory where wrangler was initiated from

发自我的 iPhone在 2022年11月1日，上午1:06，Celso Martinho @.***> 写道：
Better and faster handling when importing big SQL files using execute --file
Increased visibility during imports, sends output with each batch API call
Backups are now downloaded to the directory where wrangler was initiated from
You can view, comment on, or merge this pull request online at:
  https://github.com/cloudflare/wrangler2/pull/2107
Commit Summary
c0f1b61  fix: D1 execute and backup commands improvements
File Changes  (3 files)
A
.changeset/d1-execute.perf.md
(9)

M
packages/wrangler/src/d1/backups.tsx
(9)

M
packages/wrangler/src/d1/execute.tsx
(96)

Patch Links:
https://github.com/cloudflare/wrangler2/pull/2107.patch
https://github.com/cloudflare/wrangler2/pull/2107.diff
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>


Introduce a null check for type prior to element type check

Purpose
$Title.

@MaryamZi , test case ?

@Kishanthan this is to fix an NPE thrown at the getElementType(BType type) method, if the constructor accepting no args is used and thus array type is not set.
Do we need a test case for this particular scenario?

@hasithaa agreed, will work on fixing usages of this constructor. Will also work on fixing instances where the type is set incorrectly (element type instead of array type encapsulating element type), as discussed.

Created https://github.com/ballerina-platform/ballerina-lang/issues/10057 to track fixing incorrect/inconsistent usage, as discussed offline.
Closing this PR since this change would not be needed once the above issue is fixed.


Support for React >=0.40

Since imports were changed in https://github.com/facebook/react-native/releases/tag/v0.40.0, two small changes are required to be compatible.

This is already implemented.


AttachmentContent - Don't have project reference in the existing create method

As a user, I want to attach a content to Test Case, When I attach a content, it has only workspace reference. I don't have admin access for workspace, but I have an access for fewer projects within the workspace. So I won't able to attach the content with the workspace reference. However I can attach the content using project reference. But the Toolkit has no flexibility to pass project reference for attachmentContent.
No flexibility to accommodate the below scenario using toolkit
using WS API, attachmentContent/Create?project=ProjectReference

Implemented in 3.1.1


Feature Request: variables in rule file

I am using organize to move files from and to iCloud.
Unfortunately the local path of the iCloud is pretty lengthy which make the rule look ugly.
e.g
- Move: '~/Library/MobileDocuments/com~apple~CloudDocs/Documents/Organize/filed_docs/Rechnungen/{python.year}/'
I would prefer something like
` rule:

global variable
destination: "~/Library/Mobile Documents/com~apple~CloudDocs/Documents/Organize/filed_docs/Rechnungen/{python.year}/"
- Move: "{destination}/Rechnungen/{python.year}/"
`

Yes, good one! It's on the todo list. I'll keep this issue open until this is implemented.

Good that you understood the idea. Allthough I did not manage to format the code snippets correctly.

I use a workaround now
In the environment file I have defined a variable, e.g. DESTINATION
  filters:
      - python: |
          import os
          return {"help": {
                    "destination":os.environ['DESTINATION']
                      }

      - Move: '{python.help.destination}/...

SInce environment variable are now working also under macOS this issue can be closed TMH.


Annotate callback props with @param tags

We now need to document the signature of how callback functions passed down to components are called. I will soon provide a list such components.

#3096

Sorry Ali, forgot this was here.

Oh, no worries :grin: Thanks for providing that list :+1: :+1: