Telegram interface

To run goal-oriented bot with Telegram interface, what does "Telegram interface" or "<TELEGRAM_TOKEN>" mean?
python -m deeppavlov interactbot deeppavlov/configs/go_bot/gobot_dstc2.json -d -t <TELEGRAM_TOKEN>

you have create a account for telegram chatbot. it generate a token. you use that tokent into your command line interface. visit this page,
https://core.telegram.org/bots/api


Few issues with current setup

Nodes are unable to retrieve parent. Adding a getParent() method would be useful.

There is no way to create a SimpleCommentedConfigurationNode with a path, value, and comment in 1 line. Currently I have to create the node then call setComment on it.

I do not see a way to retrieve the current path of a node. So if I do something like this
ConfigurationNode node = this.config.getNode("general").getChild("config-enabled").setValue(true);

I should be able to use node.getPath()  which would return general.config-enabled

Is it possible to pass a path and have nodes generated, if they do not exist, for the full path? so if I use the same example above but instead wrote it as
ConfigurationNode node = this.config.getNode("general.config-enabled").setValue(true);

The output would be
general {
  config-enabled=true
}

Perhaps a getKey() method? which would return the name of the current node. Using the same example as above
node.getKey() would return "config-enabled"
node.getPath() would return "general.config-enabled"
node.getValue() would return "true"

Retrieving a child node that contains a value which is not a map or list always creates a new node object
rootNode.getNode(key).getChild(childKey)

Example above if called twice will return 2 different objects.

This exists internally -- only issue is that this is not constant until the node is created
node.getNode("general", "config-enabled").setValue(true).setComment("Aren't configs great?");
Nodes currently don't hold their full paths. Might be able to build this up from parent links though.
works as this.config.getNode("general", "config-enabled").setValue(true);
Same as 1, but it's probably good to have this (not consistent only on list element nodes because index may change)
If the node has a value set, those should return the same value -- tested at https://github.com/zml2008/configurate/blob/master/configurate-core/src/test/java/ninja/leaping/configurate/SimpleConfigurationNodeTest.java#L55

OK can we make this public as it is useful.
OK please have setComment return the node as it currently is void.
Sounds good.
OK perfect
OK
Yup, that was it. Thanks!

@zml2008 1 more thing, can setComment return the node? Thanks!

Nevermind, I didn't realise it was done in previous commit. Thanks again.


puppeteer not triggering response

With the current tree the response event of the main frame is not triggered. In the script below I would expect to see:
in response: https://secure-www.gap.com/buy/shopping_bag.do

before
in load: https://secure-www.gap.com/buy/shopping_bag.do

but it's not called at all.
script:
const puppeteer = require('puppeteer');

args = [];
args.push('--no-sandbox');
args.push('--disable-setuid-sandbox');

(async () => {
  browser = await puppeteer.launch({
    headless: false,
    args,
  });

  page = await browser.newPage();

  page.setViewport({ width: 1000, height: 600 });

  await page.setRequestInterception(true);
  page.on('request', (request) => {
    request.continue();
    return;
  });

  page.on('response', (response) => {
    console.log(`in response: ${response.url()}`)
  });

  page.on('load', async (...args) => {
    const pageURL = page.url();
    console.log(`in load: ${pageURL}`)
  })

  await page.goto('about:blank', { waitUntil: 'load' });

  await page.goto('http://gap.com', { waitUntil: 'load' });

  await page.click('.optly-modal-close');

  await page.click('#shoppingIconTrigger');
})();

Possibly unrelated, using this script:
const puppeteer = require('puppeteer');

args = [];
args.push('--no-sandbox');
args.push('--disable-setuid-sandbox');

(async () => {
  browser = await puppeteer.launch({
    headless: false,
    args,
  });

  page = await browser.newPage();

  page.setViewport({ width: 1000, height: 600 });

  await page.setRequestInterception(true);
  page.on('request', (request) => {
    request.continue();
    return;
  });

  page.on('response', (response) => {
    console.log(`in response: ${response.url()}`)
  });

  page.on('load', async (...args) => {
    const pageURL = page.url();
    console.log(`in load: ${pageURL}`)
  })

  await page.goto('about:blank', { waitUntil: 'load' });

  await page.goto('https://www.google.com/chrome/', { waitUntil: 'load' });

  await page.click('a.chr-header__link');

  await page.waitFor(2000);
})();

I would expect to see
in load: https://enterprise.google.com/chrome/chrome-browser

but I'm seeing:
in load: https://www.google.com/chrome/

as the last entry.

I want to know if there is a solution.

Same issue I am having,  XHR/AJAX responses are not being showen on the "response" event for the page.

Do you have any updates?

Same issue I am having, XHR/AJAX responses are not being showen on the "response" event for the page.

I just tested and couldn't replicate, you need to also listen to request and make sure it's request.continue()


Cleaner Variable Overrides

I'd like to start by saying thanks for putting all of this together - it feels like exactly the kind of thing that I've been itching to create for myself.
That said, I'd like to make it easier to override some of the default arbitrary values (e.g. border width: https://github.com/BlazeCSS/blaze/search?utf8=✓&q=1px)
Also, it's not currently possible to override the set screen widths, which could be a bit of a pain on some projects.  (I can see why though - setting to anything other an an em measurement would result in compile errors.  That should be fixable.)
I intend to make a PR to start moving things in this direction - this is as a heads-up and for further discussion. 😄

I've released v2.9.0 👍 any further suggestions feel free to PR or raise new issue(s)


[6.5.x] RHBPMS-4166: BRMS Generates wrong source code for Guided Rules if using 'Formula'

See https://issues.jboss.org/browse/RHBPMS-4166
(cherry picked from commit 8dfe586710f045dda7bc1adb5f23509c8ca9eb04)
This is the corollary of https://github.com/droolsjbpm/drools/pull/868 for 6.5.x

DO NOT MERGE YET - NEED ACKs ON JIRA

@triceo Hi.. can you please ack the JIRA?

ACKs received.. OK to review...


Does open with url: "file://<file_path>" work on Android?

I try to share a PDF file from the file system but it just doesn't work.

i double checked if the file exists
i asked for permission to read storage and it is allowed by the user
when sharing it e.g. with google drive it always says that there is "no data" to share
i render the PDF before sharing it so i also know that the file is not empty or corrupt

Also the docs are a bit unclear about if it's even possible to do this.
As in the docs for url: URL you want to share (only support base64 string in iOS & Android ).
Does this mean only sharing a string is possible like: url: "data:<data_type>/<file_extension>;base64,<base64_data>" is possible? because scrolling down a bit it is stated that you can directly pass a file by usingfile://...
My options:
const options = {"filename": "test.pdf", "url": "file:///data/user/0/com.x.x/files/6cfe208c-1b45-4fac-af0f-aadb7e678a6b.pdf"}
Edit:
There are no errors. It resolves with success
Thanks in advance!

Android share with file path should work.
Possibly we're facing a bug since there are few issues reporting this behaviour.
Thanks for all information you've provided.
Are you testing this with real device or emulator?

hey!
testing on a real device:

galaxy s9
Android 9

if you need any other information don't hesitate to ask. For now i'm using the fallback by reading the file with rn-fetch-blob then share it via base64 string.

@tststs great, thanks for your reply.
I don't know if I will be able to dig into this problem.
Feel free to share more information or bring up a solution.
I'll be glad to help with code review.

any updates on this ?

As far as I remember, sharing using file path is working fine.
You can test it with our example.

As far as I remember, sharing using file path is working fine.
You can test it with our example.

The example given there doesn't use file path, rather it uses data URLs with base64 encoded strings which doesn't have any issue. The only problem in this scenario is that url with path like "file://<file_path>" doesn't work. (NB: It works fine on ios)

@jgcmarins hey, I faced something same,
when URL be like this "/storage/emulated/0/Downloads/Bill765.pdf" it does not work so I can't share this PDF
But when URL be like this "/data/user/0/com.lmaalam_admin/cache/Bill197994929333884192053.pdf"
it's working fine!
So I'm forced to use the first file URL for other functionality and want to share it in this package, any idea about this?

Hi 👋
I also have this issue, when sharing file using local path - other applications do not receive it.
Logcat show NULL (clip={text/plain NULL}) instead of file:
03-23 00:34:02.875  2548  3704 I ActivityManager: START u0 {act=android.intent.action.SEND_MULTIPLE typ=text/plain flg=0xb080001 cmp=org.telegram.messenger/org.telegram.ui.LaunchActivity clip={text/plain NULL} (has extras)} from uid 10192 on display 0
03-23 00:34:02.875  2548  3704 I ActivityManager: Ignoring FLAG_ACTIVITY_NEW_DOCUMENT, launchMode is "singleInstance" or "singleTask"

I have created reproducible repo - https://github.com/olessavluk/sharebug

run it
click button "Share text.txt"

@jgcmarins any chance you could take a look?

I've got the same issue with Samsung galaxy s9+, android 10.
Works with a pixel simulator though. Very weird...

I have the same issue. Is there anybody solved the issue? I have text file and trying to share it with path like file:///data/user/0/com.myapp/files/my_file.txt but not working in (just) android

I met the same issue on android. we can't share with local file ""/data/user/0/com.lmaalam_admin/cache/Bill197994929333884192053.pdf"", we have to convert it to base 64.

I met the same issue on Android. we can't share with local file ""/data/user/0/com.lmaalam_admin/cache/Bill197994929333884192053.pdf"", we have to convert it to base 64.

Thanks for the idea. I will check and share the result soon.

Hi again.
i created a pull request that should enable sharing of files on secondary storage, i.e sd cards: https://github.com/react-native-community/react-native-share/pull/754

Hi again.
I created a pull request that should enable sharing of files on secondary storage, i.e sd cards: #754

Hi @nirre7,
Your pull request is fixed for sharing issue: file://<file_path> on android. is that right?

Your pull request is fixed for sharing issue: file://<file_path> on android. is that right?

Hey @taduyde would you mind helping us testing that? 😄

Hi @nirre7,
Your pull request is fixed for sharing issue: file://<file_path> on android. is that right?

It depends on where the file(s) are. If the file is on secondary storage like a sd card then it should work.
For more information https://developer.android.com/reference/androidx/core/content/FileProvider there is different configs on android to enable "access" to different locations.
But like @MateusAndrade said would be great if you could help us test it, it might be that we need to add more configuration to handle different scenarios/usecases.

Hi @nirre7, @MateusAndrade,
I already tested this pull request, but that pull request not help we resolve this issue with local file as here: /data/user/0/com.lmaalam_admin/cache/Bill197994929333884192053.pdf

local file

The PR fixes secondary storage for example sd cards, i.e not "local files".
More information => https://developer.android.com/reference/androidx/core/content/FileProvider#SpecifyFiles
Im guessing (!) that the config your scenario needs is:

https://developer.android.com/reference/androidx/core/content/FileProvider#SpecifyFiles

@taduyde probably you need to transform your file on a base64 before sharing that. There are been some problems when passing file whenever you call the open that we need to investigate. 😿
I think this can help you: https://github.com/react-native-community/react-native-share#share-remote-pdf-file-with-gmail--whatsapp-ios

Just tested the new version with mentioned PR and it's working for local files and files of the same package (/data/user/0/com.myapp), for different package it throws an error: (Permission denied)
Local file:

Same package:

File from different package:

I met the same issue on Android. we can't share with local file ""/data/user/0/com.lmaalam_admin/cache/Bill197994929333884192053.pdf"", we have to convert it to base 64.

Thanks for the idea. I will check and share the result soon.

Converting file to base64 before share solved my issue. Thanks!

I have a local Image that needs to be shared. For ex in My react native project, I have a Image named Resources/1.png I want to share this Image. How can I achieve it?

I met the same issue on Android. we can't share with local file ""/data/user/0/com.lmaalam_admin/cache/Bill197994929333884192053.pdf"", we have to convert it to base 64.

Thanks for the idea. I will check and share the result soon.

Converting file to base64 before share solved my issue. Thanks!

I have tried converting it to base64 using fetch blob but I'm seeing an error saying that the file or directory doesn't exist. Cannot share file on Android only. iOS is working fine.
`shareBill = async (title: string) => {
const billPdfPath = this.props.billPdfDataFetched?.path;
if (!billPdfPath) {
  return;
}

const newPath = `${RNFetchBlob.fs.dirs.CacheDir}/${title}_bill.pdf`;

await RNFetchBlob.fs.cp(billPdfPath, newPath);

const shareOptions = {
  title: title,
  subject: `${strings('bill.emailSubject')} – ${title}`,
  message: `${title} bill`,
  url: `file://${newPath}`,
  type: 'application/pdf',
  failOnCancel: true,
};

try {
  await RNShare.open(shareOptions);
  track(EVENTS.BILL_SHARE);
} catch (err) {
  track(EVENTS.BILL_SHARE, false);
} finally {
  RNFetchBlob.fs.unlink(newPath);
}

};`


Content of the last page is streched to the end

Example:

The content is stretched to the end of the page which shouldn't be the case.

Thanks for pointing that out, fixed in  56cdbe5!


Ability to add/ generate API Keys for config/ events

This is a Feature Proposal
Hi there!
I am currently using event-gateway in production (albeit in a non public facing manner, more so just to better coordinate AWS Lambda invocations/ events) and was wondering if there were any plans to generate API keys/ set api keys to prevent unauthorized access to the config/ gateway endpoints? A similar to experience to AWS's API Gateway Api keys (setting keys in serverless.yml, consuming via x-api-key) would be super.
Thanks for reading!

Hey @paulxuca ! Great suggestions. I'll fill you in our current plans.
For the Events API, we're working on adding the ability to specify authorization logic on an emitted event or an HTTP endpoint. We're hoping to start on that work in the next two weeks. I'd hope to have it finished by mid to late May.
For the Config API, we haven't prioritized auth on that end as much for two reasons. First, the Config API is on a different port than the Events API, so it can be kept in a private network or have some sort of proxy in front of it that handles authorization. Second, it has a different auth model than the Events API. The Events API authorization on a particular endpoint or event will be tied to the logic of that endpoint or event itself, whereas Config API authorization is more uniform and about who can alter the Event Gateway as a whole. The former needs to be more programmable on a more granular basis, while the latter can be handled with the rough auth proxy generally.
What do you think, @paulxuca ?
cc @mthenw and @ganeshvlrk.

Yep, we'll allow for custom authorization logic via a Lambda function to authorize or reject an event. We'll likely also have an API key based option as well, where you can specify a particular API key to be included in the Authorization header to authorize a request.

Cool! Thanks for the follow up. :)


request should be a public attribute/property of ClientResponse

In order to debug my application, I wanted to inspect attributes of the request (e.g. headers). I could not find a way to do this, and ended up hacking the aiohttp code to do this.
It would be nice if request was a public attribute/property of ClientResponse so that one could do this:
async with aiohttp.ClientSession(headers=...) as session:
    async with session.get('https://api.github.com/events', headers=...) as resp:
        print(resp.request.headers)

I don't want to expose ClientRequest class -- it has too many internal details which should be never touched by user.
But I'm ok with introducing RequestInfo named tuple with url and headers fields.
@garyvdm would you make a Pull Request?

hmm I could look at it then add tests for it if I could can get it to do such sometime.

https://github.com/aio-libs/aiohttp/pull/1733 - ClientResponse implementation (mistakenly used another bug id).

#1733 is merged


PR for #53 - NuGet package icon is missing

Included in this pull request is a change to the project files to include the expected metadata to include the XPlat Windows APIs logo within the NuGet package.

@jamesmcroft this will resolve the issue raised earlier (#53 - NuGet package icon is missing)

@jamesmcroft so we had this same issue on our MADE project where the icons don't load properly from GitHub blobs so we decided to use the image from our Twitter account. I decided to use the one from your Imgur account as it's publicly accessible which resolves this issue

@tom-made cool, no worries. Just wondered why we had to do it that way that was all. I might investigate this further but good with this change for now.


How to solve the problem of not being able to access huggingface?

python3 server.py --ip '<IP_ADDRESS>' --port 60808
checkpoint directory ./checkpoint not found, downloading from huggingface
Traceback (most recent call last):
File "/home/lighthouse/miniconda3/envs/omni/lib/python3.10/site-packages/urllib3/connection.py", line 199, in _new_conn
sock = connection.create_connection(
File "/home/lighthouse/miniconda3/envs/omni/lib/python3.10/site-packages/urllib3/util/connection.py", line 85, in create_connection
raise err
File "/home/lighthouse/miniconda3/envs/omni/lib/python3.10/site-packages/urllib3/util/connection.py", line 73, in create_connection
sock.connect(sa)
OSError: [Errno 101] Network is unreachable
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/lighthouse/miniconda3/envs/omni/lib/python3.10/site-packages/urllib3/connectionpool.py", line 789, in urlopen
response = self._make_request(
File "/home/lighthouse/miniconda3/envs/omni/lib/python3.10/site-packages/urllib3/connectionpool.py", line 490, in _make_request
raise new_e
File "/home/lighthouse/miniconda3/envs/omni/lib/python3.10/site-packages/urllib3/connectionpool.py", line 466, in _make_request
self._validate_conn(conn)
File "/home/lighthouse/miniconda3/envs/omni/lib/python3.10/site-packages/urllib3/connectionpool.py", line 1095, in _validate_conn
conn.connect()
File "/home/lighthouse/miniconda3/envs/omni/lib/python3.10/site-packages/urllib3/connection.py", line 693, in connect
self.sock = sock = self._new_conn()
File "/home/lighthouse/miniconda3/envs/omni/lib/python3.10/site-packages/urllib3/connection.py", line 214, in _new_conn
raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPSConnection object at 0x7c4471473e50>: Failed to establish a new connection: [Errno 101] Network is unreachable

hi, you may need a proxy to get better connection to huggingface and whisper checkpoint.

有大佬提供百度网盘吗，模型放网盘


Fix tried to send handshake twice

cc #5201
There was a possible state inconsistency in the NotificationsInSubstream.

Not sure about the test failure on should_revalidate_across_many_blocks, I think I've seen it before (i.e. I think it is just a flaky test, but don't take my word for it).

test was fixed, just merge master @tomaka

#5360 has been merged and triggers this error way more often, so I'm going to merge this fix as soon as the CI passes.

@NikVolf Now it's testing::pool::should_push_watchers_during_maintaince that is failing for what it's worth.


Make all external links on the Docs website open in a new tab

Existing Behavior
Most external links already have target="_blank" on the anchor tags. For the iframe approach being used to render the docs portal within the landing page, it would be ideal to have all external links present this behavior
Concern
Some pages, when opened, like Github or Medium, block rendering inside a frame. This causes a broken behavior on the page like:

Thanks!
/assign @sarahmaddox

On iframing the docs into the Kubeflow UI, please see issue https://github.com/kubeflow/kubeflow/issues/2546

Investigation shows that all links within the doc pages do already open in a new tab. This is configured by the following setting in our config.toml file:
[blackfriday]
hrefTargetBlank = true

After spending some time investigating this issue report, the only links that I can find that do not follow this rule are the following links in the top nav and footer:

Footer: Privacy Policy
Top nav: Blog, GitHub


msion  and test

Added Mission test✔
Added Professional test✔

Hi @citec-47
Status: Approved :heavy_check_mark: :heavy_check_mark: :heavy_check_mark:

Good job implementing the requirements  :+1: This checkpoint is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
To Highlight 💪🏻

Missions test passes ✔

Optional Suggestions  :

N/A

Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you take them into account as they can make your code better.
Cheers, and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag @0sugo  in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Module is a node type of variable

It seems that the treesitter implementation for Go does not correctly parse modules. The module is correctly parsed when inside the function declaration.
However, when a module is used in a function or method it instead becomes a type of variable.
Example Code:
package main

import (
	"fmt"
	"time"
)

// Here time is a module
func getTime(t time.Time) string {
	return t.String()
}

func main() {
        // Here, fmt and time are variables not modules
	fmt.Println("The time is: ", getTime(time.Now()))
}

Parsed Tree:
[source_file](https://tree-sitter.github.io/tree-sitter/playground#) [0, 0] - [15, 0]
  [package_clause](https://tree-sitter.github.io/tree-sitter/playground#) [0, 0] - [0, 12]
    [package_identifier](https://tree-sitter.github.io/tree-sitter/playground#) [0, 8] - [0, 12]
  [import_declaration](https://tree-sitter.github.io/tree-sitter/playground#) [2, 0] - [5, 1]
    [import_spec_list](https://tree-sitter.github.io/tree-sitter/playground#) [2, 7] - [5, 1]
      [import_spec](https://tree-sitter.github.io/tree-sitter/playground#) [3, 1] - [3, 6]
        path: [interpreted_string_literal](https://tree-sitter.github.io/tree-sitter/playground#) [3, 1] - [3, 6]
      [import_spec](https://tree-sitter.github.io/tree-sitter/playground#) [4, 1] - [4, 7]
        path: [interpreted_string_literal](https://tree-sitter.github.io/tree-sitter/playground#) [4, 1] - [4, 7]
  [function_declaration](https://tree-sitter.github.io/tree-sitter/playground#) [7, 0] - [9, 1]
    name: [identifier](https://tree-sitter.github.io/tree-sitter/playground#) [7, 5] - [7, 12]
    parameters: [parameter_list](https://tree-sitter.github.io/tree-sitter/playground#) [7, 12] - [7, 25]
      [parameter_declaration](https://tree-sitter.github.io/tree-sitter/playground#) [7, 13] - [7, 24]
        name: [identifier](https://tree-sitter.github.io/tree-sitter/playground#) [7, 13] - [7, 14]
        type: [qualified_type](https://tree-sitter.github.io/tree-sitter/playground#) [7, 15] - [7, 24]
          package: [package_identifier](https://tree-sitter.github.io/tree-sitter/playground#) [7, 15] - [7, 19]
          name: [type_identifier](https://tree-sitter.github.io/tree-sitter/playground#) [7, 20] - [7, 24]
    result: [type_identifier](https://tree-sitter.github.io/tree-sitter/playground#) [7, 26] - [7, 32]
    body: [block](https://tree-sitter.github.io/tree-sitter/playground#) [7, 33] - [9, 1]
      [return_statement](https://tree-sitter.github.io/tree-sitter/playground#) [8, 1] - [8, 18]
        [expression_list](https://tree-sitter.github.io/tree-sitter/playground#) [8, 8] - [8, 18]
          [call_expression](https://tree-sitter.github.io/tree-sitter/playground#) [8, 8] - [8, 18]
            function: [selector_expression](https://tree-sitter.github.io/tree-sitter/playground#) [8, 8] - [8, 16]
              operand: [identifier](https://tree-sitter.github.io/tree-sitter/playground#) [8, 8] - [8, 9]
              field: [field_identifier](https://tree-sitter.github.io/tree-sitter/playground#) [8, 10] - [8, 16]
            arguments: [argument_list](https://tree-sitter.github.io/tree-sitter/playground#) [8, 16] - [8, 18]
  [function_declaration](https://tree-sitter.github.io/tree-sitter/playground#) [11, 0] - [13, 1]
    name: [identifier](https://tree-sitter.github.io/tree-sitter/playground#) [11, 5] - [11, 9]
    parameters: [parameter_list](https://tree-sitter.github.io/tree-sitter/playground#) [11, 9] - [11, 11]
    body: [block](https://tree-sitter.github.io/tree-sitter/playground#) [11, 12] - [13, 1]
      [call_expression](https://tree-sitter.github.io/tree-sitter/playground#) [12, 1] - [12, 50]
        function: [selector_expression](https://tree-sitter.github.io/tree-sitter/playground#) [12, 1] - [12, 12]
          operand: [identifier](https://tree-sitter.github.io/tree-sitter/playground#) [12, 1] - [12, 4]
          field: [field_identifier](https://tree-sitter.github.io/tree-sitter/playground#) [12, 5] - [12, 12]
        arguments: [argument_list](https://tree-sitter.github.io/tree-sitter/playground#) [12, 12] - [12, 50]
          [interpreted_string_literal](https://tree-sitter.github.io/tree-sitter/playground#) [12, 13] - [12, 28]
          [call_expression](https://tree-sitter.github.io/tree-sitter/playground#) [12, 30] - [12, 49]
            function: [identifier](https://tree-sitter.github.io/tree-sitter/playground#) [12, 30] - [12, 37]
            arguments: [argument_list](https://tree-sitter.github.io/tree-sitter/playground#) [12, 37] - [12, 49]
              [call_expression](https://tree-sitter.github.io/tree-sitter/playground#) [12, 38] - [12, 48]
                function: [selector_expression](https://tree-sitter.github.io/tree-sitter/playground#) [12, 38] - [12, 46]
                  operand: [identifier](https://tree-sitter.github.io/tree-sitter/playground#) [12, 38] - [12, 42]
                  field: [field_identifier](https://tree-sitter.github.io/tree-sitter/playground#) [12, 43] - [12, 46]
                arguments: [argument_list](https://tree-sitter.github.io/tree-sitter/playground#) [12, 46] - [12, 48]`

tree-sitter is not context-aware, that's what queries are for, so you can tag specific bits and correlate that with their usage later on within a scope.


Performance improvements

I took a profiler to this package and got a bunch of fun performance wins!
The net improvement from commits in this PR (as recorded on my early 2013 2.7 GHz Core i7 MacBook Pro) is as follows:
benchmark             old ns/op     new ns/op     delta
BenchmarkHash1024     11766         4608          -60.84%

benchmark             old MB/s     new MB/s     speedup
BenchmarkHash1024     87.03        222.21       2.55x

benchmark             old allocs     new allocs     delta
BenchmarkHash1024     66             0              -100.00%

benchmark             old bytes     new bytes     delta
BenchmarkHash1024     2064          0             -100.00%

The bulk of my effort was put into reducing allocations, so I'm sure I left some cycles on the table if you (or anyone else) is curious to hunt for them.

Very nice. Thank you!


[MemAccessUtils] Regard end/abort_apply as use.

Unique storage use visitor was not previously considering end_apply and abort_apply as uses of an address even when the begin_apply took that address as an argument.  They are uses of it though because the address may be stored into the coroutine's frame and used when the second partial function is invoked.

@swift-ci please test

@swift-ci please smoke test and merge


refactor: move some ExitId tests to PaymentExitGame test suite to expose tested functions through public API

Bumps test coverage of PaymentExitGame to 100% by moving ExitId tests to PaymentExitGame test suite (PaymentExitGame exposes tested function through public API).

References #389

well...that is the dilemma when things are coupled. I personally don't even think chasing this coverage here has strong benefit. But I would suggest to just replace the e2e test code using the exitId function from exit game to implicitly cover the code as there is no logic there anyway....
It is currently using the ExitIdWrapper. We can use the function form exit game directly instead.
eg. https://github.com/omisego/plasma-contracts/blob/master/plasma_framework/test/src/exits/payment/PaymentExitGame.test.js#L244

It is currently using the ExitIdWrapper. We can use the function from exit game directly instead.
eg. https://github.com/omisego/plasma-contracts/blob/master/plasma_framework/test/src/exits/payment/PaymentExitGame.test.js#L244

Good idea! I'll do it that way.


incompatible with the  element

This is due to this here: https://github.com/floating-ui/floating-ui/issues/2496#issuecomment-1686187905
I think this library should not add transforms for positioning, and should instead leave that to floating-ui.

@ynotdraw @NullVoxPopuli I understand why this change was made, but I think it would be more appropriate to allow the user to opt out of transforms. transform is the more performant way to position most HTML elements. floating-ui's vue implementation defaults to using transform.
We could consider automatically opting for top/left or warning if the floating element is a dialog.
WDYT?

sounds good to me, seems fair to change behavior based off of element


Does HTTPotion Support SNI?

Getting handshake failure when I try to use it against aws cloudfront which currently (if you pick the free version of certificate) only allows clients that supports SNI.
%HTTPotion.ErrorResponse{message: "{:tls_alert, 'handshake failure'}"}

I had to specify the ssl version. As mentioned here
# Either use this

HTTPoison.get("https://example.com/", [], [ssl: [{:versions, [:'tlsv1.2']}]])

# or worst case:

HTTPoison.get("https://example.com/", [], [ssl: [{:verify, :verify_none}]])

Damn, Erlang ssl's behavior is so weird, why does it only automatically set SNI if you force TLS 1.2 o_0
You can probably do something like that:
HTTPotion.get("https://example.com/", [ibrowse: [ssl_options: [{:versions, [:'tlsv1.2']}]]])

But it seems like you can also pass the hostname as the server_name_indication option instead of TLS 1.2. HTTPotion should automatically do this. I'll implement that soon.

Done. SNI should work automatically on current master.


defensive issues (tighter invariance checking)

Is the task about improving the invariants in the module?

@brewmaster012 @kingpinXD might have more context.


IgnoreXmlnsAttribute

I have gpx version 1.0 files I'm trying to parse and they would parse correctly except for the version and xmlns attributes being 1.0
IgnoreVersionAttribute fixes the version issue but the xmlns issue remains.
I'm happy to submit a pull request if you approve of either:

Implementing IgnoreXmlnsAttribute
Changing IgnoreVersionAttribute to also ignore xmlns

related to https://github.com/NetTopologySuite/NetTopologySuite.IO.GPX/issues/35


OP-18137 : Added new query params for new endpoint

https://devopsmx.atlassian.net/browse/OP-18137
We prefer small, well tested pull requests.
Please refer to Contributing to Spinnaker.
When filling out a pull request, please consider the following:

Follow the commit message conventions found here.
Provide a descriptive summary for your changes.
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Add inline code comments to changes that might not be obvious.
Squash your commits as you keep adding changes.
Add a comment to @spinnaker/reviewers for review if your issue has been outstanding for more than 3 days.

Note that we are unlikely to accept pull requests that add features without prior discussion. The best way to propose a feature is to open an issue first and discuss your ideas there before implementing them.

This PR  triggered this build in this execution, please wait for it  and child pipelines to succeed before merging:  https://isd.prod.opsmx.net/deck/#/applications/gcp-gitprtrigger/executions/details/01GG7ABRVSFR7NHF3QPBWQ3JAA

This PR  triggered this build in this execution, please merge to master only if this succeeds:  https://isd.prod.opsmx.net/deck/#/applications/gcp-gitprtrigger/executions/details/01GG7ACBG5F9TG9SZWHG1B6SV4

SUCCESSFUL RunTests RESULT: Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 Reviewers ,  this PR did not cause the failures in  https://jenkins.opsmx.net:8181/jenkins/job/Dev-API-Automation-Test-GitPR/569/artifact/test-output/extentreport.html


[Bug] CoreDNS integration causes issues

Seeing errors like this in dd agent logs:
[ AGENT ] 2018-09-22 00:07:37 UTC | ERROR | (kubelet.go:97 in parseKubeletPodlist) | Can't parse template for pod coredns-3506319915-lfh6f: in instances: found non JSON object type, value is: '[map[prometheus_url:http://%%host%%:9153/metrics tags:[dns-pod:%%host%%]]]'

But the annotations are exactly those that were provided in the docs for the coreDNS integration page. Why does dd agent throw this error?

@pratikmallya I ran into the same issue this morning and fixed it with the following annotation object:
"annotations": {
  "ad.datadoghq.com/coredns.check_names": "[\"coredns\"]",
  "ad.datadoghq.com/coredns.init_configs": "[{}]",
  "ad.datadoghq.com/coredns.instances": "[{\"prometheus_url\":\"http://%%host%%:9153/metrics\", \"tags\":[\"dns-pod:%%host%%\"]}]"
}

The issue being that the value of the ad.datadoghq.com/coredns.instanceskey is wrapped in an unnecessary array.
Good luck!

Apologies for the long delay on this issue - You are correct @chrisnankervis.
@DataDog/baklava could we get this updated ?
Thanks for bringing this up to our attention.
Best,
.C

https://github.com/DataDog/integrations-core/pull/2701

Closing as it seems to be fixed


Elixir highlighting is incorrect

Hi Highlight team,
Here is an example showcasing the issues of Elixir highlighting. It's taken from reviewable.io UI that uses highlight.js under the hood.
First, highlight.js

Second, my VSCode editor

(there's some custom coloring going on here but I'll focus on the general issues)
What's wrong in highlight.js

Incorrect namespace highlighting in defmoduledeclaration (different colors when it should be monochrome)
Incorrect namespace highlighting in code body (monochrome when namespace should be different color)
require and import statements are not highlighted.
@moduledoc, @doc, @typedoc incorrectly highlighted as module attributes.
<- and |> not highlighted.
with statement not highlighted.

Thanks for looking into this!

I'm working on a PR — here are my thoughts so far:

require, import and with are simply missing; added.
Module names can be compound (perhaps other names too?); allow . as part of identifier.
@moduledoc, @doc and @typedoc appear to be defined as module attributes, not sure why it's wrong to highlight them as such?
As far as I can tell by looking at the CSS class reference and other languages, highlight.js philosophy is not to highlight operators or namespaces.  If that's not correct perhaps a maintainer can correct me?
Found an extra bug where :: and neighbors gets highlighted as symbol; fixed.

If we can clarify my questions above I can open a PR with the fixes.  Thanks!

OK
OK
You're right, it's OK to keep them highlighted as module attributes.
Fine not to highlight namespace, as #2 is fixed.
Great :)


Better error when plugin applied to a wrong type

Fixes

https://github.com/gradle/gradle/issues/24580

When a plugin is applied in the wrong context, the error explains it and guides the user:
> Failed to apply plugin class 'SomePlugin'.
   > The plugin must be applied to a Project (or in a build script), but was applied to the Settings (or in a settings script)

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

The merge queue build has failed. Click here to see all failures.

The merge queue build has failed. Click here to see all failures.


Fix missing list

Notes for Reviewers
This PR fixes #10252
Signed commits

[ ] Yes, I signed my commits.

🚀 Preview for commit e436cfb64b40c5cf059493b0099f9501e1a6c518 at: https://65c637c30a51b5008255295c--meshery-docs-preview.netlify.app


First version of parse-print analysis script.

Fixes #787
Problem:
It's hard to gauge how well the parser printer combination works currently without manually testing projects against it.
Fix:
Created a script that can be run with npm run parse-print-analysis, which will produce a bunch of diffs for files in those projects so that issues can be identified and then retested subsequently.
Commit Details:

Fixes #787.
Created parse-print-analysis.ts file which processes files in a
collection of projects to see the result of parsing and then
printing a JavaScript file.
Fixed one small issue with the parser not allowing fragments as a
top level element of a component.
Added parse-print-analysis npm script.

Noice!


Remove file property containing absolute path to file

Solves: https://github.com/faceyspacey/babel-plugin-universal-import/issues/60

@faceyspacey See anything wrong with this. AFIK it shouldnt cause an issue?

@faceyspacey @ScriptedAlchemy Can I do anything to speed up review of this PR?

Make it relative please

@faceyspacey ☝
Perhaps, for developers to use within their application?
If I'm correct, that object is accessible to coders. Needing a relative path might be useful?
Cannot confirm this though

@Arturszott, could you make it relative and we will merge your update


In which byte order (endianness) does it produce 16-bit raw pixel data?

https://github.com/lovell/sharp/blob/3a64a0529a1903cd395caa91bdf62507eb12c303/docs/api-output.md?plain=1#L530-L534
It explains the pixel arrangement and channel arrangement in each pixel, but doesn’t explain how bytes of a multibyte (16-bit) value in a pixel are arranged.
Question
await Sharp("test.png")
	.toColorspace("grey16") // or "rgb16"
	.raw({depth: "ushort"})
	.toBuffer()

In which byte order (endianness) does it produce 16-bit raw pixel data? Big endian, little endian, or the native byte order of the underlying platform (machine)?
Related
https://github.com/lovell/sharp/issues/2104.

Good question, I would expect it to be native to the underlying architecture but we should probably verify this (e.g. via s390x/QEMU) and update the docs accordingly.

@issuefiler Were you able to verify the endianness? (I've not had a chance, nor will I for a while, so anything you can do to help here is much appreciated.)

v0.33.0 is now available with prebuilt binaries for Linux s390x that appear to work so I'm hoping this means native endianness is as expected.


:ambulance: default access rights access error

Website Domains are not evaluated as expected after installing demo.

It was the issue of the runbot.


Add MyBinder link to example

If we add this, we should probably add it systematically to all examples both F# and C#


Dio - QueuedInterceptor to handle Refresh Token with multiple requests

Package
dio
Version
4.0.6
Output of flutter doctor -v
No response
Dart Version
3.64.0
Steps to Reproduce
I am calling multiple api's like this
await Future.wait([profile, calendar, cities]);
I have a interceptor class which extends Dio QueuedInterceptor. On profile api, my access token expires and onError of Interceptor class gets called. So I hit refresh_token api, then I retry the current request, on its success I call return handler.resolve(response);.
`Future<void> onError(DioError err, ErrorInterceptorHandler handler) async {

    if (err.response?.statusCode == 401) {
      var tokenDio = Dio();

      try {
        Response refreshResponse = await tokenDio.post('/${endPoint.path}',
            data: endPoint.requestBody);

        if (refreshResponse.statusCode == 201) {
          var newAccessToken = refreshResponse.data['access_token'];

          var newHeaders = err.requestOptions.headers;
          newHeaders['Authorization'] = 'Bearer $newAccessToken';

           var response = await dio.request(
            err.requestOptions.path,
            data: err.requestOptions.data,
            queryParameters: err.requestOptions.queryParameters,
            options: Options(
              method: err.requestOptions.method,
              headers: newHeaders,
            ),
          );

          return handler.resolve(response);
        }
        else {
          return handler.reject(err);
        }
      } catch (error) {
        return handler.reject(err);
      }
    }
    else {
      return handler.next(err);
    }
  }`

Expected Result
should'nt return handler.resolve(response); ignore the remaining 2 queued requests?
Actual Result
But the remaining api's still call the interceptor onError method and my refresh_token api is hit total of 3 times.

I also have a similar problem, it will be triggered multiple times without bei

Future.wait

I also have a same problem.

I also have this same problem

@AlexV525

@hemantchauhan From the code you've provided, you're using the dio instance again when the token is refreshed, which will get locked again because you're handling the lock at this moment. Please do not use the same instance in queued interceptors.
Provide more information if the issue still persist after applied the above suggestion.


Woke v0.18.0 fails to install from source due to replace directive

Hello! Recently we started running into issues installing woke. After some investigation it seems to be due to this recent change: https://github.com/get-woke/woke/pull/117.
Currently we are installing woke by running:
go install github.com/get-woke/woke@latest

Unfortunately after the recent changes it now results in this error:
  go: downloading github.com/get-woke/woke v0.18.0
  go install github.com/get-woke/woke@latest: <EMAIL_ADDRESS>  	The go.mod file for the module providing named packages contains one or
  	more replace directives. It must not contain directives that would cause
  	it to be interpreted differently than if it were the main module.

Reading through the woke docs, the recommended way to install from source is to run:
go get -u github.com/get-woke/woke

However, the recommended command results in a warning:
go get: installing executables with 'go get' in module mode is deprecated.
	Use 'go install pkg@version' instead.
	For more information, see https://golang.org/doc/go-get-install-deprecation
	or run 'go help get' or 'go help install'.

Reading through the document linked in the warning, it seems like this method will stop working in Go 1.18. The document recommends using go install instead. Unfortunately go install doesn't like replace directives. I found this thread in the Go issue tracker discussing it: https://github.com/golang/go/issues/44840. Please correct me if I have said anything that is incorrect or partially incorrect. This is my first time running into this issue with a tool.
I didn't look into the context of why the replace directive was added to woke. I am not sure if it is easy to remove or if there is a better solution that achieves all of the desired goals.
My current workaround is to install v0.17.0 instead of latest.

Thanks for reporting @BlueMonday! Can you confirm what version of go you're encountering this error with?
It seems like the replace directive should be remove to support future go versions. The context for that change is here.
It also seems like the documentation needs to be updated to support go's deprecation of go get for installing executables.

Thanks for reporting @BlueMonday! Can you confirm what version of go you're encountering this error with?

Hello! Sorry, I should have included that.
I confirmed that the issue occurs with these two specific Go versions: 1.17.5 and 1.16.5. I think it would be safe to assume the issue would impact all 1.17 and 1.16 versions. I think it would also affect all Go 1.18 versions but I haven't gotten a chance to test using a 1.18 version.

Thanks!
I have two PRs open to resolve this:

https://github.com/get-woke/woke/pull/182 switch to a forked version of the go-git module so replace isn't needed
https://github.com/inclusive-dev-tools/go-git/pull/1 upstream fix so woke can import the module directly

This should be fixed in v0.18.1 and you should be able to go back to go install github.com/get-woke/woke@latest

This should be fixed in v0.18.1 and you should be able to go back to go install github.com/get-woke/woke@latest

Thank you for the really quick turnaround! Really appreciate it! Will switch back to using latest.


Support derivations with content-addressed outputs

Hi, there's some overlap here with #24 that allows you to do this as well in more type safe manner (without forcing you to use txt for hashes)  (see also https://github.com/haskell-nix/hnix-store/pull/272/commits/641cd4fd502f30820706e6d3bdcd657812fb5a25)
Your PR is handy since I wasn't sure how CA one looks exactly!

Cool, I can integrate your changes after I'm done with it!

https://github.com/obsidiansystems/Haskell-Nix-Derivation-Library/tree/pr-26 contains latest master, #24, and #26


Resource not found

When the payload is posted in endpoint /api/message:
{"input":{"text":"hi"}}
The follow response is returned (500 Internal Server Error):
{"code":500,"error":"Resource not found"}

This likely means your credentials or workspace_id are incorrect

For anyone that is wondering where they can find the credentials, here's how:
1- Log in to Bluemix.
2- Select Catalog and then Watson to get to the list of services
3- Select a service, and then create an instance of the service by clicking Create.
4- Select Service Credentials and then View Credentials on the service dashboard.


chore: move test to contract folder

Summary

Move contract test to inside contract folder.

Sure, but why aren't we also moving call-test-contract.test.ts?

I didn't notice that! Thanks for pointing, I'm adding this also


[SR-12460] Don't crash when missing a type in a Diagnostic message.

Print an empty string for the missing type.
Resolves SR-12460
Given this swift file:
extension {
  func ==(lhs: Foo, rhs: Foo) -> Bool {}
}

And the swift arguments that XCode uses to compile swift.
Produce this output:
/Users/eyork/dev/test/Test/Test/main.swift:13:11: error: expected type name in extension declaration
extension {
          ^
/Users/eyork/dev/test/Test/Test/main.swift:14:8: **error: operator '==' declared in extension of '' must be 'static'**
  func ==(lhs: Foo, rhs: Foo) -> Bool {}
       ^
  static
/Users/eyork/dev/test/Test/Test/main.swift:14:16: error: use of undeclared type 'Foo'
  func ==(lhs: Foo, rhs: Foo) -> Bool {}
               ^~~
/Users/eyork/dev/test/Test/Test/main.swift:14:26: error: use of undeclared type 'Foo'
  func ==(lhs: Foo, rhs: Foo) -> Bool {}
                         ^~~
Program ended with exit code: 1

This line in bold has the fixed result. It will refer to the missing type as ''.
Before this fix, the compiler would crash when producing that line.

Ok, I will make those updates.

Made that update. The new diagnostic message is "operator '==' declared in extension must be 'static''. How does that look?

I added a test in swift/test/decl/ext/extensions.swift but I am not sure how to run that single test.

@swift-ci please smoke test

@blueeor Looks like there are test failures.

ok, I will look at that.

The test fails for swift 4:
RUN: at line 1';   /Users/eyork/apple-swift/build/Ninja-DebugAssert/swift-macosx-x86_64/bin/swiftc -frontend -target x86_64-apple-macosx10.9  -module-cache-path '/Users/eyork/apple-swift/build/Ninja-DebugAssert/swift-macosx-x86_64/swift-test-results/x86_64-apple-macosx10.9/clang-module-cache' -sdk '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk'  -swift-version 4  -ignore-module-source-info -typo-correction-limit 10  -typecheck -verify -disable-objc-attr-requires-foundation-module /Users/eyork/apple-swift/swift/test/decl/ext/extensions.swift
I am assuming that it's working correctly for swift 5.
I don't know how to set the error test in extensions.swift to only be for swift 5?

Why does it fail for Swift 4 and not 5?

@blueeor Have you tried running BUILD_DIR/bin/swift on a separate file with the relevant test code to verify the correct diagnostic is emitted?

I was mistaken. This doesn't have anything to do with swift language 4 or 5.
This test is running swiftc with different options vs when xcode runs swift. With the default options on swift, this diagnosis message doesn't appear.  I haven't yet figured out which swift option will make this diagnosis message appear (a pointer in the right direction would help me). The other question is would I need to put this test in it's own file and add a test that runs swiftc with the correct options? Or is there already a test that runs swift with the same options that XCode would use?

@blueeor I think it would be fine to add a new test file with particular set of flags in RUN which reproduce this problem, you can use SR number as a file name, we do that in test-suite already.

The code surrounding the emission of the error is not showing any dependence on an invocation flag, and the diagnostic does appear with a proper extension, so it has to be something else.

I haven't yet figured out which swift option will make this diagnosis message appear (a pointer in the right direction would help me).

@blueeor From the stack-trace seems like the crash appears when trying to index symbols (IndexSwiftAST), so you can pass something like target-swift-ide-test -print-indexed-symbols
could be that @xedin?

OK, so in between recent snapshots and the Xcode 11.3 release something happened that caused us to completely skip validation of members inside these broken extensions, which is why the error is not emitted normally in this case. We either have to fix that or hit the code path by using the appropriate command to emit index data (@LucianoPAlmeida pointed out the right one).

@LucianoPAlmeida Thanks. I will update the test with that or I guess make a new test for this.
@AnthonyLatsis It sounds like you are saying there is a larger bug at play here?

I updated the tests and it passes for me now. I pushed the commit. Will the ci system pick this up or does it need a prompt to run again?

I updated the tests and it passes for me now. I pushed the commit. Will the ci system pick this up or does it need a prompt to run again?

@blueeor Someone with the rights should kick the CI
cc @xedin :)

Here is the test-case we can use for this issue, let's have it as test/decl/ext/sr_12460.swift
// RUN: %target-swift-ide-test -print-indexed-symbols -source-filename %s 2>&1 | %FileCheck -check-prefix CHECK %s

//Test that we don't crash when validating members inside an extension with no type name.

// CHECK: :[[@LINE+1]]:11: error: expected type name in extension declaration
extension {
  // CHECK: :[[@LINE+1]]:8: error: operator '==' declared in extension must be 'static'
  func ==(lhs: Any, rhs: Any) -> Bool {}
}

@xedin I updated the test file with those changes.

@swift-ci please smoke test

Thank you, @blueeor! Please don't forget to resolve associated SR.


How to use visualization_grounding_net.py?

Hi! Would it be possible to provide some guidance on how to run the visualization_grounding_net code? I've been trying to run it for some time, but nothing seems to work. I'll be thankful!

I have the same question. Thanks for pointing it out.


Blockquotes in AMP enabled page Showing as regular text

Blockquotes Showing as regular text in AMP enabled page.

That's just CSS, you need to add the styles for the quote in the custom CSS section of AMP.

@ahmedkaludi Please let me know your thoughts on this

Just to help:
This is simply a CSS issue, you could add options to the plugin settings, however, all the user needs to do really is add CSS to their custom CSS section, such as:
.amp-wp-content blockquote {     background-color: #fff;     border-left: 3px solid #000;     border-top: 1px solid #ddd;     border-bottom: 1px solid #ddd;     border-right: 1px solid #ddd;    color: #445; }

Thanx @nicholasgriffintn I'll close this issue now :)

@beingteja I have Understood your problem , as you can see in the image Even your Theme style is not displayed in the AMP page , We are working on this and will let you know once we have successfully put even theme styles in AMP pages and then i think you will not get any of this issue


Allow Datagrid filters to render display labels

I am guessing we will need to change the filtering implementation a bit to improve the way the labels are displayed (sentence case + i18n) — but think business logic should be separated here — can discuss the approach to achieve this separately.
Seems like we are using accessor, column, and id for the filtering + filter summary labels, but may need a way to show displayed labels other than the identifier.
e.g. passwordStrength: normal should be displayed as Password strength: Normal.
May need a separate issue to address this for date (see comments), but we can use this issue to evaluate first in case they can be contained.

Filter summary

Where's the 'List all' chevron?
Label should match sentence case (first letter capitalized)

Originally posted by @sdignum in https://github.com/carbon-design-system/ibm-products/issues/2500#issuecomment-1343315181

[ ] Date format presented in the Filter panel are mm/dd/yyyy and in the tags formatted as dd/mm/yyyy

Originally posted by @My-Money29 in https://github.com/carbon-design-system/ibm-products/issues/2500#issuecomment-1801908211

Actually, I think this scenario may still be possible. I can open a separate issue for this as suggested!

https://github.com/carbon-design-system/ibm-products/issues/3899


⚠ Adam Brand Music has degraded performance

In ad02621, Adam Brand Music (https://adambrandmusic.com) experienced degraded performance:

HTTP code: 200
Response time: 6608 ms

Resolved: Adam Brand Music performance has improved in 89d8e58 after 8 minutes.


[Feature Request] Output Manual Control Mode as Boolean

First of all, thank you very much for your great work. Adaptive Lighting is really great and has already completely replaced Circadian Lighting
Now to my problem. I have some automations that I would like to set up on the manual control state of my Adaptive Lighting. Unfortunately I don't get state not extrahier. I tried it with this Binary Sensor for example:
  - platform: template
    sensors:
      adaptive_lighting_buro_deckenlampe_manual_control:
        friendly_name: "Adaptive Lighting Büro Deckenlampe im manuellen Modus"
        value_template: >-
          {{ is_state_attr('switch.adaptive_lighting_buro_deckenlampe', 'manual_control', 'light.buro_deckenlampe') }}

Unfortunately it always shows off. No matter what the manual_control value of the switch is.
So I would like to ask if it would be possible to output the manual control state as boolean on/off or as a separate sensor?
No matter what the answer is, thanks again for the great work and stay healthy ;-)

Hello,
The manual_control attribute return a list not a string your code should be :
  - platform: template
    sensors:
      adaptive_lighting_buro_deckenlampe_manual_control:
        friendly_name: "Adaptive Lighting Büro Deckenlampe im manuellen Modus"
        value_template: >-
          {{ is_state_attr('switch.adaptive_lighting_buro_deckenlampe', 'manual_control', ['light.buro_deckenlampe']) }}

if you have more than one light in your switch it's better to do this:
  - platform: template
    sensors:
      adaptive_lighting_buro_deckenlampe_manual_control:
        friendly_name: "Adaptive Lighting Büro Deckenlampe im manuellen Modus"
        value_template: >-
          {{ 'light.buro_deckenlampe' in state_attr('switch.adaptive_lighting_buro_deckenlampe', 'manual_control') }}

Great, thanks @peexl for helping.
Please reopen if the issue persists.

About the input_boolean, that is not possible because the manual control status is per light not per Adaptive Lighting instance.


Does dubbo springboot support SSL for dubbo protocol, and https for rest protocol?

thanks  for your response.
internal net call also need ssl and https in our company.
Thus, we plan to change the source code to support.
thanks!
On Thu, Jan 31, 2019 at 6:12 PM tppppp<EMAIL_ADDRESS>wrote:

@dongdongqin https://github.com/dongdongqin
it seems not to be supported from official website so far.
there is a suggestion.
you can run api-gateway application to protect your rest api, and then all
of service applications are internal net call.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-dubbo-spring-boot-project/issues/407#issuecomment-459289526,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUqA_Tq8bobz0r10SYzwt_JgWqvstJHcks5vIsGTgaJpZM4aQnsR
.


Default to current namespace instead of "Kubeflow" or None

Works better in a multi-user setting.
CC @zabbasi

@karthikv2k Any suggestion on how we might tackle this?
Should we do something like

Have fairing look for POD_NAMESPACE environment variable
Have JupyterNotebook set POD_NAMESPACE env variable on the pod?

Has been fixed in https://github.com/kubeflow/fairing/pull/318?


Can't login: Token has expired - SecurityException

Describe the bug
When I want to login on my Android phone, a message about an expired token is displayed.
To Reproduce
Steps to reproduce the behavior:
Try to login.
Expected behavior
Either I should be logged in successfully or I should have the option to renew the token.
Screenshots

Smartphone (please complete the following information):

Device: Google Pixel 6
OS: Android 14
Browser: Cromite
Version: Latest

Additional context
It happens on my girlfirend's iPhone as well. So, it doesn't seem to be entirely Android related.
Edit: I could solve this on my Android phone by removing all cache and user data from the app and then specifiying my server URL again and logging in from scratch. However, there should be a more user-friendly way of handling expired tokens.

I'm not able to reproduce this. Once token expires, I can login again and the new token is set.


stale action runs into rate limit

What happened?
The stale actions all run at the same time and now happen to run into a rate limit.

TIL that the sync action supports templating the synced files using a Jinja syntax. We should revisit all synced files to see if they could benefit from a more personalized touch (e.g. injecting different times for cron jobs, injecting the repo name, etc.).


JWE handling does not prepend the algorithm to the salt

As stated in "4.8.  Key Encryption with PBES2" in https://tools.ietf.org/html/rfc7518#appendix-C

the salt parameter MUST be computed from the "p2s" (PBES2 salt input) Header Parameter value
and the "alg" (algorithm) Header Parameter value"

You might want to consider testing against data generated by a different implementation like this
https://github.com/cisco/node-jose/blob/master/test/jwe/jwe-test.js

@lagebaue - Thanks for reporting the issue. p2s was incorrectly set equal to the salt rather than equal to the salt input. Now fixed and published in NPM as v1.0.1.


knife client create should check file permissions

Description
Support user-friendly error checking on file permissions for knife client create
knife user create is already covered in PR
Related Issue
https://github.com/chef/chef/issues/3514
https://github.com/chef/chef/issues/3517
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[ ] I have read the CONTRIBUTING document.
[x] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[x] All commits have been signed-off for the Developer Certificate of Origin.

This failing windows unit test looks related:
  1) Chef::Knife::ClientCreate run when clientname is passed with -f or --file should write the private key to a file
     Got 1 failure and 1 other error:

     1.1) Failure/Error: expect(filehandle).to receive(:print).with("woot")

            (Double "Filehandle").print("woot")
                expected: 1 time with arguments: ("woot")
                received: 0 times
          # ./spec/unit/knife/client_create_spec.rb:127:in `block (5 levels) in <top (required)>'
          # ./spec/spec_helper.rb:304:in `block (2 levels) in <top (required)>'
          # ------------------
          # --- Caused by: ---
          # SystemExit:
          #   exit
          #   ./lib/chef/knife/client_create.rb:89:in `exit'

     1.2) Failure/Error: knife.run

          UnexpectedSystemExit:
            exit
          # ./lib/chef/knife/client_create.rb:89:in `exit'
          # ./lib/chef/knife/client_create.rb:89:in `run'
          # ./spec/unit/knife/client_create_spec.rb:129:in `block (5 levels) in <top (required)>'
          # ./spec/spec_helper.rb:304:in `block (2 levels) in <top (required)>'
          # ------------------
          # --- Caused by: ---
          # SystemExit:
          #   exit
          #   ./lib/chef/knife/client_create.rb:89:in `exit'

https://buildkite.com/chef-oss/chef-chef-master-verify/builds/6073#1fc23a03-85f3-4c49-bb00-d6d434a32d4f/352-1282

@snehaldwivedi Should this PR contain all 10 commits?

@snehaldwivedi Should this PR contain all 10 commits?

@tas50 No it contain only https://github.com/chef/chef/issues/3514, I have created this branch by https://github.com/chef/chef/pull/10187 as I required code of it. PR is the base PR for merge part.

@tas50 Can you please have a look into the PR for merge or if any more changes required form my side?

I still don't understand why a change to check for file permissions requires bringing in knife-opc. The work of this PR seems entirely unrelated to the title.

@tas50 I think this PR builds off of #10187 and includes all the commits from that PR.

Yes we have 3 PRs in flight that are all working on the same code and it's very hard to track what we're trying to achieve with that. These should really all get closed at this point and the work should back to knife-opc. Get that clean. Figure out how to interact with these server objects without creating a large abstraction layer and then we can create a plan to move that into the client.

@lamont-granquist Most of the part of card #3517  was already covered in PR #10187. This PR covers one of the remeaning sections #3514.
Please have a look at it.

Could you refresh this so that it contains only the changes from d3b1d51 and
bcef863 ? It might be best to start a new branch and cherry-pick or re-apply the changes.

@marcparadise I have created a new PR with required changes for this card here, so closing this PR


/en prefix bug does not allow parameters

Description
When trying to access /en as parameters for example /en?source=google, it gives an error.

I've tried everything and I don't know how to solve this.
Mandatory reproduction URL (CodeSandbox or GitHub repository)
(exemple with bug)

https://codesandbox.io/p/sandbox/next-intl-bug-template-forked-yow8ep
Reproduction description
Steps to reproduce:

enter url /en
add params /en?source=google
redirected you too many times.

Expected behaviour
redirect to /?source=google or allow /en?source=google

Thanks for the report! This is already fixed in the 3.0 release candidate: https://github.com/amannn/next-intl/pull/569

Thanks for the report! This is already fixed in the 3.0 release candidate: #569

Thanks for responding more when trying to use the fixed version, I have error with "import Link from "next-intl/link""

Please carefully read through the release notes: https://next-intl-docs.vercel.app/blog/next-intl-3-0

Please carefully read through the release notes: https://next-intl-docs.vercel.app/blog/next-intl-3-0

Thanks @amannn


Error when npx create and prompt

There is an issues in create.mjs file.
The issue is whenever prompted to write an npm package name, after inputting any name even just 'example' it showing that npm package only can contain small, numbers and hypens, but litterally in create.mjs file after receiving the prompt value its appending @ and / as suffix prefix, so everytime it makes an error.

I'll add a note on the first question for "(leave empty for none)" although this won't affect existing development environments that have been created.

Just seen that I read the issue incorrectly.
You are correct, the prefix and suffix were being added and thus causing the validation to fail. This has been fixed in the latest version.


syz-ci: poll lore mailing list archives for pending fixes

Sometimes a fix is posted to a kernel mailing list, but then either (1) it gets lost, or (2) somebody else spends time to fix the same bug again without being aware of the existing fix. One precedent:
https://groups.google.com/forum/#!topic/syzkaller-bugs/ilAjLbsyV0A
We could poll mailing list archives from https://lore.kernel.org/lists.html stored in git to discover pending fixes and notify dashboard.
This will also have some synergy with bug notifications about pending fixes: #1574
Will this need a special type of association between bugs and commits? Or we could simply upload it as normal fixing commit?

There is a caveat here: If a patch fixes a problem, but the patch is ignored because it's either the wrong fix, duplicate, or poor quality, then it needs to be ignored. But unfortunately there is no information to derive this; in the worst case, because the only place this information exists is in a maintainer's head (or some other database they maintain).
The only way to make this useful, is to collect all posted patches and categorize them as "proposed" -- I think this might sort of answer your questions "[...] special type of association [...]?" and "[...] upload it as normal fixing commit?".
In other words, the patches could be acknowledged and tracked, but only displayed as a separate list of "potential fixes". This might provide value, since it might allow someone encountering the same problem, to quickly pick a fix (although they might have several patches/versions to choose from).

Generally, a patch with a fix (or even a potential fix - even if it is incorrect) that gets sent to the mailing lists has the syzbot address (from the Reported-by tag) CCed. If possible, this could be used for acknowledging and tracking the patches.
Also, adding to what @melver said, it might also help to provide a feature for users who have already started working on a bug (or are about to) to make it known that they will be working on the bug too.
syzbot provides a sign-in option where users can sign in using their email-ids.
Users could sign in and "mark" a bug if they're going to be working on it/have already fixed it, and this would be visible to all others who visit the bug's page on the dashboard.
This "mark" could also be extended indicate at least one of 3 things (which can each be identified with a simple colored dot) -

"I want to work on this bug, but I am still in the process of understanding it better."
"I understand the bug, and have a fair idea about what to do. But my potential fix needs to be tested, and reviewed."
"I know what's going on, and I have a fix."

Granted this would require people to visit the dashboard more than most people care for (since a lot of them work directly off of the syzbot mail), but at least this way people know who else are working on a fix/if a fix has already been submitted, and check that out too in a more real-time manner.

syzbot provides a sign-in option where users can sign in using their email-ids.
Users could sign in and "mark" a bug if they're going to be working on it/have already fixed it, and this would be visible to all others who visit the bug's page on the dashboard.

This is outside of the scope of the project for 2 reasons:

This is a slippery slope to implementing a full-fledged bug tracking system. Once people can do these actions, they will also want marking bugs as fixed, submitting tests requests and all other actions. Building a full-fledged bug tracking system requires 10x more developer resources that is currently allocated on syzbot (look at Bugzilla/Mantis/Jira) and there is not point in spending resources at implementing yet another one. Moreover, use of Bugzilla is discouraged for Linux kernel.
All of this is not specific to syzbot and is relevant to all other kernel bugs. syzbot should not invent own ways of solving these problems, and the ways that are not helpful for kernel bugs reported by other entities (low return of investment). syzbot should use whatever is the current kernel's way of dealing with these problems. As you noted, some kernel developers won't even use some external web service.

syzbot provides a sign-in option where users can sign in using their email-ids.
Users could sign in and "mark" a bug if they're going to be working on it/have already fixed it, and this would be visible to all others who visit the bug's page on the dashboard.

This is outside of the scope of the project for 2 reasons:

This is a slippery slope to implementing a full-fledged bug tracking system. Once people can do these actions, they will also want marking bugs as fixed, submitting tests requests and all other actions. Building a full-fledged bug tracking system requires 10x more developer resources that is currently allocated on syzbot (look at Bugzilla/Mantis/Jira) and there is not point in spending resources at implementing yet another one. Moreover, use of Bugzilla is discouraged for Linux kernel.
All of this is not specific to syzbot and is relevant to all other kernel bugs. syzbot should not invent own ways of solving these problems, and the ways that are not helpful for kernel bugs reported by other entities (low return of investment). syzbot should use whatever is the current kernel's way of dealing with these problems. As you noted, some kernel developers won't even use some external web service.

A related user request:
# I wish that syzbot dashboard allows manually specifying e.g. "patch proposed" state, for
# some patches take long time before accepted (and may result in duplicated works like I did
# on this bug).

https://groups.google.com/g/syzkaller-bugs/c/ysjnCmKu6Dc/m/94C76byKBQAJ


Upgrading 2.7.82 to 2.8.0

I don't know if I am just looking in the wrong place but i can't find any documentation here on GitHub or a detailed Change Log.
Are there code breaking changes between 2.7.82 and 2.8.0? What has changed since 2.7.82?
Thank you.

I found the documentation on the Wiki tab. I was looking for an overview readme file.
But I do not see a change log.

There is a CHANGELOG.md markdown file in the root of the project.
I assume you can find what you need in there.


forge 1.20.1 mods, server cant load chuncks

when i relog to server i load chunck, when i go to new territory its not chunks

Do you have no fog enabled?

hi, i fixed this bug(thanks Fran12334) he writed issue same with my, it was, because my render distance was below, than server render distance, i needed just max my render distance

link to [Quilt 1.19.4 cheatutils 2.4.0] not rendering chunks outside of initial view distance
#26


Checksum

Please add also a Checksum to the releases! It would be very nice

You can close the issue, no problem but please think for it...

You can close the issue, no problem but please think for it...
Ah, no, that was an accident. I've put it in the project board, and it's slated for the next release tomorrow.

Cool

@mawoka-myblock, Sums are now with the latest release, thanks for the tip!


bugdown: Add domain-name to relative image-url in open graph data.

fixes #4608
Need advice on whether this needs testing, and if yes, how. Since it requires querying external services that might change their behavior someday, I'm confused what to do.

Automated message from Dropbox CLA bot
@aero31aero, it looks like you've already signed the Dropbox CLA. Thanks!

@aero31aero this looks great, but you should add a test so that we don't break this in the future!    zerver/tests/test_link_embed.py is probably the place to put it; I imagine we'll want to do a new case in PreviewTest, similar to the first 3 lines of test_inline_url_embed_preview (but with captured open-graph data for Youtube)

Added tests.

Nice, merged, thanks @aero31aero!


Remove duplicated line

The line 81 is duplicated below on line 85.

Well how did that get there?
Thanks! 👍


feat: add CNCF required files

Adding OWNERS file, that is common (not required) to have in CNCF projects.

cc @scrocquesel @adam-sandor @gyfora @mbalassi @andreaTP @metacosm

Roger, thanks.


LLAPI Transport not available on WSA/UWP (v2)

Please squash so that the commit log only shows the latest commit in this branch, otherwise that'll be 3 extra commits.

:tada: This PR is included in version 3.6.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Unable to connect from DBeaver on Mac to SQL Server that uses Active Directory authentication

System information:

Operating system: MacOS Big Sur: 11.2.3 (20D91)
DBeaver version: <IP_ADDRESS>106090921
Additional extensions: none

Connection specification:

Database name and version: Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64)
Sep 24 2019 13:48:23
Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2019 Standard 10.0 (Build 17763: ) (Hypervisor)

Driver name: Microsoft JDBC Driver for SQL Server, with Azure drivers installed

Do you use tunnels or proxies (SSH, SOCKS, etc)?: Yes, F5 Big-Ip

Describe the problem you're observing:
Working remotely, I wish to connect DBeaver on a Mac to SQL Server that uses an Active Directory service to authenticate and authorize users.
I've tried multiple approaches to connect and authenticate, including those recommended in issue 3647 and issue 9751.
Nevertheless, I am unable to authenticate. Here's one error I've received.

Steps to reproduce, if exist:
Based on the configuration, these seem to be the settings needed:
Authentication: Active Directory - Password
Driver properties:

authentication: ActiveDirectoryPassword
trustServerCertificate: true    # to avoid SSL errors

Using them reproduces my error. Curiously, the username string in the error message is usually empty, but not always (like above). I wonder if DBeaver is failing to use it.
What settings should be used to connect with my configuration?

@artgoldberg did you try to connect using e.g. SMSS?
Probably something Is going wrong with user settings
https://docs.microsoft.com/en-us/answers/questions/133709/login-failed-for-user-39lttoken-identified-princip.html

Thanks @uslss .  I'm using a Mac and "SSMS is available only as a 32-bit application for Windows".  I started trying to use Azure Data Studio, but it doesn't support Active Directory - Password authentication.
However, the document you reference provides a hint. While it's terribly written, it seems to suggest that the name of the user granted rights to access a SQL Server database must exactly match the User Principal Name (UPN) for the user in the Active Directory server used to authenticate the user. Is this correct? Please let me know, as that would be important information if it is true, and Googling does not answer the question.
Thanks
Arthur

Hello @artgoldberg
You have SQL Server database and driver, but also you have Azure drivers.
Have you tried to use the Connection dialog for Azure Database?

Thanks @LonwoLonwo
No, I've not tried an Azure database. But I have no problem using SQL Server Authentication to access SQL Server, so I do not need to try that. The key challenge here is to get Active Directory authentication working.
What do you think Serge @serge-rider ?
Thanks
Arthur

https://github.com/dbeaver/dbeaver/issues/4990

Thanks @LonwoLonwo , I've tried #4990 and it didn't work.
However, colleagues of mine enabled connection from DBeaver on Mac to SQL Server by using Kerberos to access the Active Directory authentication. It's complicated. I can provide details if you like.

Yes @artgoldberg
It will be very helpful!

What I did is to set up the Kerberos configuration in /etc/krb5.conf on the Mac for the AD realm(s) aka domain(s). Then, it's just a matter of setting the properties correctly:
databaseName=master
authenticationScheme=JavaKerberos
encrypt=true
integratedSecurity=true
serverName=mssqlserver.example.org
trustStoreType=KeychainStore
<EMAIL_ADDRESS>

Thanks @jnahmias , that's great!


meltano add transformer dbt-duckdb: invalid value -2

Hi!
I have a brand new meltano project, in a new virutal env.
If I run:
meltano add transformer dbt-duckdb

I get
Need help fixing this problem? Visit http://melta.no/ for troubleshooting steps, or to
join our friendly Slack community.

<flag 'DefinitionSource'> invalid value -2
    given 0b1 10
  allowed 0b1 11

Pip Freeze dump:
aiodocker==0.21.0
aiohttp==3.8.4
aiosignal==1.3.1
alembic==1.11.1
aniso8601==9.0.1
anyio==3.7.1
asgiref==3.7.2
async-timeout==4.0.2
atomicwrites==1.4.1
attrs==23.1.0
Authlib==1.2.1
Babel==2.12.1
backoff==2.2.1
bcrypt==3.2.2
blinker==1.6.2
cached-property==1.5.2
certifi==2023.5.7
cffi==1.15.1
charset-normalizer==3.1.0
check-jsonschema==0.22.0
click==8.1.4
click-default-group==1.2.2
croniter==1.4.1
cryptography==41.0.1
distlib==0.3.6
dnspython==2.3.0
email-validator==1.3.1
fasteners==0.18
filelock==3.12.2
Flask==2.1.3
Flask-BabelEx==0.9.4
Flask-Cors==3.0.10
Flask-Executor==0.10.0
Flask-Login==0.6.1
Flask-Mail==0.9.1
Flask-Principal==0.4.0
Flask-RESTful==0.3.10
Flask-SQLAlchemy==2.5.1
Flask-WTF==1.1.1
flatten-dict==0.4.2
frozenlist==1.3.3
greenlet==2.0.2
gunicorn==20.1.0
h11==0.14.0
httptools==0.6.0
idna==3.4
itsdangerous==2.1.2
Jinja2==3.1.2
jsonschema==4.18.0
jsonschema-specifications==2023.6.1
Mako==1.2.4
markdown-it-py==3.0.0
MarkupSafe==2.1.3
mdurl==0.1.2
meltano==2.19.1
meltano-flask-security==0.1.0
multidict==6.0.4
packaging==23.1
passlib==1.7.4
platformdirs==3.8.1
psutil==5.9.5
psycopg2-binary==2.9.6
pycparser==2.21
Pygments==2.15.1
pyhumps==3.8.0
python-dateutil==2.8.2
python-dotenv==0.21.1
python-gitlab==3.15.0
pytz==2023.3
PyYAML==6.0
referencing==0.29.1
requests==2.31.0
requests-toolbelt==1.0.0
rich==13.4.2
rpds-py==0.8.8
ruamel.yaml==0.17.21
six==1.16.0
smart-open==6.3.0
smtpapi==0.4.12
sniffio==1.3.0
snowplow-tracker==0.10.0
speaklater==1.3
SQLAlchemy==1.4.49
structlog==23.1.0
typing_extensions==4.7.1
tzlocal==5.0.1
urllib3==2.0.3
uvicorn==0.17.6
uvloop==0.17.0
virtualenv==20.23.1
watchgod==0.8.2
websockets==11.0.3
Werkzeug==2.1.2
WTForms==3.0.1
yarl==1.9.2

Hey @ReneTC! I think the issue is this: https://github.com/meltano/meltano/issues/7813 and isn't dbt-duckdb specific, but lmk if you disagree and/or if there is something I can do to assist. 🙇

Hey @jwills thanks a lot. You are right. Switching to python 3.10.12 works.

I can't really make sense if this issue, now it doesn't work anymore with python 3.10.12?

anyone that can reproduce?

Okay I am now quite sure this error has to do with my company. It is very strict with weird certifications and python versions and packages. If anyone have any idea if the issue is fixable I would love to know

Fixed by using anaconda instead of pyenv and pipx. I also had to use meltano: 2.10.0 and python 3.8.10


Add memory_format in torch.Tensor.to

What does this PR do?
Fixes #144.
Adding argument memory_format in torch.Tensor.to.

Hey @jjsjann123, is it possible this is coming from somewhere else?
with:

commit eb42bdb7624385d53237d0737a10b334ee2e79d8 (HEAD, jie/to_memory_format)
Author: pre-commit-ci[bot]<EMAIL_ADDRESS>Date:   Wed Apr 10 23:08:55 2024 +0000
[pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

I am still getting:
[rank0]:     super().optimizer_step(*args, **kwargs)
[rank0]:   File "/usr/local/lib/python3.10/dist-packages/pytorch_lightning/core/module.py", line 1303, in optimizer_step
[rank0]:     optimizer.step(closure=optimizer_closure)
[rank0]:   File "/usr/local/lib/python3.10/dist-packages/pytorch_lightning/core/optimizer.py", line 152, in step
[rank0]:     step_output = self._strategy.optimizer_step(self._optimizer, closure, **kwargs)
[rank0]:   File "/usr/local/lib/python3.10/dist-packages/pytorch_lightning/strategies/ddp.py", line 270, in optimizer_step
[rank0]:     optimizer_output = super().optimizer_step(optimizer, closure, model, **kwargs)
[rank0]:   File "/usr/local/lib/python3.10/dist-packages/pytorch_lightning/strategies/strategy.py", line 239, in optimizer_step
[rank0]:     return self.precision_plugin.optimizer_step(optimizer, model=model, closure=closure, **kwargs)
[rank0]:   File "/usr/local/lib/python3.10/dist-packages/pytorch_lightning/plugins/precision/amp.py", line 80, in optimizer_step
[rank0]:     closure_result = closure()
[rank0]:   File "/usr/local/lib/python3.10/dist-packages/pytorch_lightning/loops/optimization/automatic.py", line 144, in __call
__
[rank0]:     self._result = self.closure(*args, **kwargs)
[rank0]:   File "/usr/local/lib/python3.10/dist-packages/torch/utils/_contextlib.py", line 115, in decorate_context
[rank0]:     return func(*args, **kwargs)
[rank0]:   File "/usr/local/lib/python3.10/dist-packages/pytorch_lightning/loops/optimization/automatic.py", line 129, in closur
e
[rank0]:     step_output = self._step_fn()
[rank0]:   File "/usr/local/lib/python3.10/dist-packages/pytorch_lightning/loops/optimization/automatic.py", line 318, in _train
ing_step
[rank0]:     training_step_output = call._call_strategy_hook(trainer, "training_step", *kwargs.values())
[rank0]:   File "/usr/local/lib/python3.10/dist-packages/pytorch_lightning/trainer/call.py", line 309, in _call_strategy_hook
[rank0]:     output = fn(*args, **kwargs)
[rank0]:   File "/usr/local/lib/python3.10/dist-packages/pytorch_lightning/strategies/strategy.py", line 390, in training_step
[rank0]:     return self._forward_redirection(self.model, self.lightning_module, "training_step", *args, **kwargs)
[rank0]:   File "/usr/local/lib/python3.10/dist-packages/pytorch_lightning/strategies/strategy.py", line 642, in __call__
[rank0]:     wrapper_output = wrapper_module(*args, **kwargs)
[rank0]:   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
[rank0]:     return self._call_impl(*args, **kwargs)
[rank0]:   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1541, in _call_impl
[rank0]:     return forward_call(*args, **kwargs)
[rank0]:   File "/usr/local/lib/python3.10/dist-packages/pytorch_lightning/strategies/strategy.py", line 635, in wrapped_forward
[rank0]:     out = method(*_args, **_kwargs)
[rank0]:   File "/home/tfogal/dev/nemo/nemo/utils/model_utils.py", line 399, in wrap_training_step
[rank0]:     output_dict = wrapped(*args, **kwargs)
[rank0]:   File "/home/tfogal/dev/nemo/nemo/collections/multimodal/models/text_to_image/imagen/imagen.py", line 393, in training
_step
[rank0]:     loss_mean, loss_dict = self.fwd_bwd_step(dataloader_iter, False)
[rank0]:   File "/home/tfogal/dev/nemo/nemo/collections/multimodal/models/text_to_image/imagen/imagen.py", line 346, in fwd_bwd_
step
[rank0]:     losses_reduced_per_micro_batch = fwd_bwd_function(
[rank0]:   File "/home/tfogal/dev/mlm/megatron/core/pipeline_parallel/schedules.py", line 374, in forward_backward_no_pipelining
[rank0]:     output_tensor = forward_step(
[rank0]:   File "/home/tfogal/dev/mlm/megatron/core/pipeline_parallel/schedules.py", line 192, in forward_step
[rank0]:     output_tensor, loss_func = forward_step_func(data_iterator, model)
[rank0]:   File "/home/tfogal/dev/nemo/nemo/collections/multimodal/models/text_to_image/imagen/imagen.py", line 254, in fwd_outp
ut_and_loss_func
[rank0]:     loss, loss_dict = model(*batch)
[rank0]:   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
[rank0]:     return self._call_impl(*args, **kwargs)
[rank0]:   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1541, in _call_impl
[rank0]:     return forward_call(*args, **kwargs)
[rank0]:   File "/opt/pytorch/lightning-thunder/thunder/__init__.py", line 194, in forward
[rank0]:     res = self._forward_fn(*args, **kwargs)
[rank0]:   File "/opt/pytorch/lightning-thunder/thunder/__init__.py", line 629, in fn_
[rank0]:     cache_entry, inps, pro_to_epi = get_computation_and_inputs(*args, **kwargs)
[rank0]:   File "/opt/pytorch/lightning-thunder/thunder/__init__.py", line 262, in cache_info_wrapper
[rank0]:     res = fn(*args, **kwargs)
[rank0]:   File "/opt/pytorch/lightning-thunder/thunder/__init__.py", line 504, in get_computation_and_inputs
[rank0]:     prologue_trc, computation_trc, *maybe_epilogue = interpreter(
[rank0]:   File "/opt/pytorch/lightning-thunder/thunder/__init__.py", line 175, in _general_frontend
[rank0]:     return thunder_general_jit(fn, args, kwargs, sharp_edges=sharp_edges)
[rank0]:   File "/opt/pytorch/lightning-thunder/thunder/core/jit_ext.py", line 1440, in thunder_general_jit
[rank0]:     result = jfn(*args, **kwargs)
[rank0]:   File "/opt/pytorch/lightning-thunder/thunder/core/interpreter.py", line 6684, in fn_
[rank0]:     raise e
[rank0]:   File "/opt/pytorch/lightning-thunder/thunder/core/interpreter.py", line 6647, in fn_2
[rank0]:     return fn(*args, **kwargs)
[rank0]:   File "/opt/pytorch/lightning-thunder/thunder/core/interpreter.py", line 6046, in _impl
[rank0]:     return fn.__func__(fn.__self__, *args, **kwargs)
[rank0]:   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
[rank0]:     return self._call_impl(*args, **kwargs)
[rank0]:   File "/opt/pytorch/lightning-thunder/thunder/core/interpreter.py", line 6046, in _impl
[rank0]:     return fn.__func__(fn.__self__, *args, **kwargs)
[rank0]:   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1541, in _call_impl
[rank0]:     return forward_call(*args, **kwargs)
[rank0]:   File "/opt/pytorch/lightning-thunder/thunder/core/interpreter.py", line 6046, in _impl
[rank0]:     return fn.__func__(fn.__self__, *args, **kwargs)
[rank0]:   File "/home/tfogal/dev/nemo/nemo/collections/multimodal/models/text_to_image/imagen/imagen.py", line 135, in forward
[rank0]:     x_start = x_start.to(memory_format=torch.channels_last)
[rank0]:   File "/opt/pytorch/lightning-thunder/thunder/core/interpreter.py", line 6158, in partial_call_impl
[rank0]:     return partial_function.func(*(partial_function.args + args), **(partial_function.keywords | kwargs))
[rank0]:   File "/opt/pytorch/lightning-thunder/thunder/core/interpreter.py", line 1258, in wrapping_wrapper
[rank0]:     res = ufn(*uargs, **ukwargs)
[rank0]:   File "/opt/pytorch/lightning-thunder/thunder/core/symbol.py", line 250, in __call__
[rank0]:     result = self.meta(*args, **kwargs)
[rank0]:   File "/opt/pytorch/lightning-thunder/thunder/core/langctxs.py", line 124, in _fn
[rank0]:     result = fn(*args, **kwargs)
[rank0]: TypeError: to() got an unexpected keyword argument 'memory_format'

from the NeMo model. Did I apply it wrong somehow?

Interesting. sounds like my patch isn't bullet proof then.
Is it easy to run the repro? I can take a look there.

Is it easy to run the repro? I can take a look there.

"Easy" might be a bit of a strong term... i'll ping you on slack, you'd need something internal.

FAILED thunder/tests/test_inplace_copy.py::test_prim_inplace_copy_fwd_nvfuser_cuda_bfloat16 - AssertionError: Tensor-likes are not close!

Mismatched elements: 1 / 16 (6.2%)
Greatest absolute difference: 0.01953125 at index (1, 1) (up to 0.01 allowed)
Greatest relative difference: 0.032958984375 at index (1, 1) (up to 0.01 allowed)

Is this a numerical issue? since I'm not reproing this one locally.

FAILED thunder/tests/test_inplace_copy.py::test_prim_inplace_copy_fwd_nvfuser_cuda_bfloat16 - AssertionError: Tensor-likes are not close!

Mismatched elements: 1 / 16 (6.2%)
Greatest absolute difference: 0.01953125 at index (1, 1) (up to 0.01 allowed)
Greatest relative difference: 0.032958984375 at index (1, 1) (up to 0.01 allowed)

Is this a numerical issue? since I'm not reproing this one locally.

I think so, I've already relaxed this bf16 to 1e-2, I'll check what's wrong, you could re-run this test I think

FAILED thunder/tests/test_inplace_copy.py::test_prim_inplace_copy_fwd_nvfuser_cuda_bfloat16 - AssertionError: Tensor-likes are not close!

Mismatched elements: 1 / 16 (6.2%)
Greatest absolute difference: 0.01953125 at index (1, 1) (up to 0.01 allowed)
Greatest relative difference: 0.032958984375 at index (1, 1) (up to 0.01 allowed)

Is this a numerical issue? since I'm not reproing this one locally.

I think so, I've already relaxed this bf16 to 1e-2, I'll check what's wrong, you could re-run this test I think

Thanks for confirming.
I still have Tom's use case to clear but struggling with running that, so not really blocked by the CI yet.

Is it easy to run the repro? I can take a look there.

Jie and I iterated offline.
This was my bad. I was running things incorrectly (had 2 thunder installs, picked up wrong one). The patch works fine.
Sorry for the noise!


fix a bug with cd-workflow.yml

Original error in GitHub Action:

23 Building image [docker.pkg.github.com/Guaand/github-actions-for-packages/tic-tac-toe:sha-fa3c49b]
24 invalid argument "docker.pkg.github.com/Guaand/github-actions-for-packages/tic-tac-toe:sha-fa3c49b" for "-t, --tag" flag: invalid reference format: repository name must be lowercase

So, I changed the cd-workflow.yml:

67 "Guaand" into "guaand"

Then, I edited Dockerfile to trigger off GitHub Action.

Why not follow the original "Warning" to use the v2 of build-push-action?
I have tried, but it seems that build-push-action@v2 won't generate an image to my repository's package.
So, I reviewed the log in GitHub Action again, and follow the original error to change url of my repository, from "Guaand" to "guaand"

And it WORKS!🎉

See Stuck on GitHub Actions: Publish to GitHub Packages.


VIYA 4.0 Installation - Azure VPN Enabled Subscription

Build Machine: jps-test.unx.sas.com
Kubernetes Cluster being created with: https://gitlab.sas.com/tosher/viya4-iac-vpn (Works everytime)
Using the following to perform installation:
viya4iac=/opt/sas/install/viya4-iac-azurefeb2023
viya4dep=/opt/sas/install/viya4-deployment
viya4base=/opt/sas/install/
viya4ns=${viya4base}/viya4-txdps/spurs
TFVARS=${viya4iac}/txdps.tfvars
TFPLAN=${viya4iac}/txdps.plan
export KUBECONFIG=${viya4iac}/mtljmu-txdps-viya4-aks-kubeconfig.conf
cd ${viya4dep}
ansible-playbook -vvv
-e BASE_DIR=${viya4base}
-e CONFIG=${viya4ns}/ansible-vars.yaml
-e TFSTATE=${viya4iac}/terraform.tfstate
-e JUMP_SVR_PRIVATE_KEY=$HOME/.ssh/id_rsa
playbooks/playbook.yaml --tags "baseline,viya,install"
Keeps failing at this stage here:
TASK [vdm : kustomize - Get user's customizations] **************************************************************************************************************************
task path: /opt/sas/install/viya4-deployment/roles/vdm/tasks/kustomize.yaml:33
fatal: [localhost]: FAILED! => {
"msg": "Unable to import siteconfig_info due to invalid syntax"
}
PLAY RECAP ******************************************************************************************************************************************************************
localhost                  : ok=102  changed=10   unreachable=0    failed=1    skipped=101  rescued=0    ignored=0
Has anyone come across this? and what is the requirement it is looking for to be present?

@jamesr26, Are you still having this issue?
Azure VPN Enabled Subscription has not been part of IAC testing yet, so difficult to tell if this setup has anything missing.

Azure VPN Enabled VIYA 4.0 06-2023 tested and working. This is now resolved.


Feature REQ: Support for HEC raw endpoint

Starting in version 6.4, Splunk has added a raw endpoint for HEC.
Reference:
http://dev.splunk.com/view/event-collector/SP-CAAAE8Y
Having this available in the kafka-connect-splunk connector would enable users to easier consume and sink unstructured data

@lilgreenwein What were you thinking here. A source connector for receiving data and writing it to Kafka or a sink connector to write to Splunk? This functionality seems to make the most sense for receiving data.

Likely mostly as a source connector.  There are some HEC logging drivers starting to appear that address this raw endpoint /services/collector/event/raw directly, rather than the standard /services/collector/event


feat: add support for react-native v0.73

react-native v0.73 changed a few internal classes regarding ShadowNodes.
I've updated the corresponding headers and function calls to the best of my knowledge.
The current state compiles, but I've commented out the "adopt" function call in MGContentContainerComponentDescriptor.h, because I couldn't get the types to work properly. It would be nice if someone could help me with that :)
Other than that, I want to thank the entire margelo team for creating this amazing library.
Please don't be discouraged to work on this library. You've truly created something revolutionary, which has a bright future for the react-native space.

@SamuelScheit It seems that in XCode 15.3, it doesn't build.


ORA-28041: Authentication protocol internal error

Connect to Oracle using SID
conn, err := sql.Open("oracle", "oracle://user:pass@<IP_ADDRESS>:1521/ORCL?SID=ORCL

Response:
ORA-28041: Authentication protocol internal error

I using navicat connect is ok

this is not related to SID
may be password expire


AUR package cannot find templates in config path

Hello, I've been playing around with flavours for a couple hours now and It's pretty great. I've been having trouble getting it to recognize my custom schemes and templates in my .config/flavours directory. I cloned it to my machine and was playing around with it looking for a bug and ... couldn't find one? The cloned version works just fine. Both the outputs are shown below
using /usr/bin/flavours installed through aur:
❱ flavours apply nord
Error: Couldn't read template i3/nebi3 at "/home/neb/.local/share/flavours/base16/templates/i3/templates/nebi3.mustache". Check if the correct template/subtemplate was specified, and run the update templates command if you didn't already.

Caused by:
    No such file or directory (os error 2)

using local build & cargo run:
❱ cargo run -- apply nord
    Finished dev [unoptimized + debuginfo] target(s) in 0.21s
     Running `target/debug/flavours apply nord`
Some("/home/neb/.config/flavours/templates/i3/templates/nebi3.mustache"), Is_file: true
Some("/home/neb/.config/flavours/templates/nvim/templates/default.mustache"), Is_file: false
Some("/home/neb/.config/flavours/templates/kitty/templates/default.mustache"), Is_file: false

the extra "is_file" lines were my attempts at debugging it's the only change I've made to the code
I double checked if it was recognizing my config file as shown:
❱  flavours -v
Using directory: "/home/neb/.local/share/flavours"
Using config file: "/home/neb/.config/flavours/config.toml"

I'm at a loss for why these two builds would be different, and why only the AUR build would be unable to recognize the templates and schemes directories in my .config. Hoping you might have some insights
thanks!

Hey!
IIRC, the AUR version is using a tagged release, while the feature that allows you to put schemes and templates in .config hasn't been part of a relase yet.
I think we're good for a tag now, I'll get it going

thanks!

Thanks for fixing it so fast!


Remove side-effects from main

Close #40

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 9 (0.0%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.3%) to 55.306%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

core/src/cli_commands/bootstrap.rs
0
9
0.0%

Files with Coverage Reduction
New Missed Lines
%

core/src/main.rs
2
0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
813

Relevant Lines:
1470

💛  - Coveralls

Fixed up main.rs. In addition, I fixed some bugs in parsing the boostrap YAML file and sprinkled some logging statements in.