Can't download from Facebook

Checklist

[X] I'm reporting a broken site
[X] I've verified that I'm running yt-dlp version 2022.02.04. (update instructions)
[X] I've checked that all provided URLs are alive and playable in a browser
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
Europe
Description
Just can't download https://www.facebook.com/UNILADTech/videos/463029358636004/...
See output below.
Verbose log
E:\_PROGS\CLI\yt-dl-ffmpeg>yt-dlp_min.exe https://www.facebook.com/watch/?v=463029358636004
[facebook]<PHONE_NUMBER>36004: Downloading webpage
[facebook]<PHONE_NUMBER>36004: Downloading webpage
ERROR: [facebook]<PHONE_NUMBER>36004: Cannot parse data; please report this issue on  https://github.com/yt-dlp/yt-dlp , filling out the "Broken site" issue template properly. Confirm you are on the latest version using -U; please report this issue on  https://github.com/yt-dlp/yt-dlp , filling out the "Broken site" issue template properly. Confirm you are on the latest version using -U

Have the same issue any update on this? Perhaps the video is geo blocked?

I had the same issue.  I was able to get around that by passing in a --cookies yourfbcookie.txt .  Basically, export the facebook cookie from your browser. I used a chrome addon for that.
 yt-dlp --cookies yourfbcookie.txt  https://www.facebook.com/UNILADTech/videos/463029358636004

Is there any other way to download it without using cookies and give my username and password?
Could yt-dlp find a hacky way to pass that?


EXCESSIVE_ARGUMENTS is not configured correctly

Now that the CFLint integration into cfeclipse works nicely, I get message:

@denuno ,  I don't know.  is this a back version of CFLint?

a back version of CFLint

org.cfeclipse.cflint_<IP_ADDRESS>707040628.jar seems to have fixed it. Thanks!


[Feature] Allow using any OpenAI-compatible mode

Currently, the model="gpt-4o" is hardcoded in the code. We should allow using any OpenAI-compatible model. This will allow users to use other providers (e.g., OpenRouter) and even local models.

Hello, we tried to solve the issue.
This is what we did:
Modified the code to allow using any OpenAI-compatible model instead of hardcoding 'gpt-4o'. Added a command-line argument to specify the model and updated the LLM initialization.
You can review changes in this commit: https://github.com/jacks-sam1010/virattt-ai-hedge-fund-13/commit/929196a08705d05fa2ed0faf120d8c8354635df5.

[!CAUTION]
Disclaimer: The concept of solution was created by AI and you should never copy paste this code before you check the correctness of generated code. Solution might not be complete, you should use this code as an inspiration only.

Latta AI seeks to solve problems in open source projects as part of its mission to support developers around the world. Learn more about our mission at https://latta.ai/ourmission . If you no longer want Latta AI to attempt solving issues on your repository, you can block this account.

@jacks-sam1010 Can you create a PR with those changes? Instead of (or in addition to) using CLI to specify the model, we should use the .env file.

Yes, please create a PR 👍

@virattt  let's keep the issue open until a PR is submitted.


add safe contracts for orderly mainnet

Please add a basic PR description that at least contains an RPC URL to verify the deployments


Script to fix Stripe webhooks

A recent changes added metadata to the webhooks but legacy webhooks were not updated.
This script goes thru all the shops and verifies if their webhook is properly configured.
If not, it deletes the invalid webhook and creates a new one.

Ran the script in prod.


Save and/or state files, cloud sharing between devices

Would be nice to save on one device and it be available on another device.  Any chance this is something Daijishou could handle? maybe similar you have planned with the backup/restore to Google drive?

#118

#118

Just to be sure, currently Daijisho only backs up its configs to google drive, not including the states and saves files across standalone players, right?


chiptool reads threadnetworkdiagnostics cluster with all relevant attributes as null[1.3]

Reproduction steps
Raspberry Pi running all-cluster-app --thread；
Reading the cluster threadnetworkdiagnostics with chiptool after successful pairing yields null values.

Bug prevalence
1
GitHub hash of the SDK that was being used
1
Platform
raspi
Platform Version(s)
No response
Type
Common Cluster Logic
Anything else?
no

done


Feature: ContentEditable should accept a ref

Our use case is giving an editor in a dialog initial focus when the dialog is opened.
A ref prop should be accepted here: https://github.dev/facebook/lexical/blob/168f0d43fcbd3d4d3129aff2e57eb9cfab0ba8e4/packages/lexical-react/src/LexicalContentEditable.tsx#L14-L36

Feel free to add it in a PR?

@trueadm will do, can you assign me to the issue?

@DaniGuardiola I'm not sure we need to forward the ref to this component or necessarily should. We already use a ref within LexicalContentEditable to set it as the root element for the editor instance (i.e. where it should inject any DOM updates).
If you need to autofocus an editor, you can add the AutoFocusPlugin to that editor.

@DaniGuardiola We can merge the refs, but I still think we already expose most of the potential use cases through the editor instance, which we should probably encourage users to use over refs.
For example. to imperatively focus/blur the editor, you can call editor.focus() or editor.blur(). That logic comes with some cross browser bug fixes, and some logic for focusing to the end of of a contenteditable with pre-populated content.

@thegreatercurve good point... I guess something that bugs me with that approach is that accessing the editor instance is not very ergonomic since if you're abstracting lexical into a component, you either need to:

split it into the context provider and the plugins/other stuff inside (which in turn means you have to split your app components so that you can consume the context which a bunch of prop drilling), or
assign to a ref so that the parent can access it (which also means no accessing it during render - probably a good thing, and a nullable type that you have to check or optionally chain - editorRef.current?.focus)

That's a different topic though, around ergonomics of the context etc etc. In conclusion, gotcha :P

@DaniGuardiola We can merge the refs, but I still think we already expose most of the potential use cases through the editor instance, which we should probably encourage users to use over refs.
For example, to imperatively focus/blur the editor, you can call editor.focus() or editor.blur(). That logic comes with some cross browser bug fixes, and some logic for focusing to the end of of a contenteditable with pre-populated content.

editor.focus() is only available within the LexicalComposer right?
how would you focus the editor when the button to click on to focus it is outside of the LexicalComposer ?

Is there a better solution? This prevents tab from being able to tab past the input.

We ran into a similar problem, and we came up with this hack.
export const RefPlugin = forwardRef<HTMLElement>((props, ref) => {
  const [editor] = useLexicalComposerContext();

  useEffect(() => {
    editor.registerRootListener((root, _prevRoot) => {
      if (!ref) return;
      if (typeof ref === 'function') {
        ref(root);
      } else {
        throw new Error('non-callback ref not supported');
      }
    });
  }, [editor]);

  return null;
});

const ref = useCallback((element: null | HTMLElement) => {
  console.log('Yeah!', element);
}, []);

return (
  <LexicalComposer initialConfig={initialConfig}>
    <RichTextPlugin
      contentEditable={contentEditable}
      ErrorBoundary={LexicalErrorBoundary}
      placeholder={null}
    />
    <RefPlugin ref={ref} />
  </LexicalComposer>
);

Not likely to be a good solution... just a hack to be used at your own peril.
Note: Not sure what will happen if the root element ever changes in the editor and the ref callback is called a second time


打包编译后没有结束进程

Describe the bug
使用这个插件后，打包编译后没有结束进程，导致流水线无法自动往后执行

Reproduction
mark
System Info
import Components from 'unplugin-vue-components/vite'
import { VantResolver} from 'unplugin-vue-components/resolvers'
Components({
        resolvers: [VantResolver()]
      }),

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

找到问题了，是版本兼容问题，安装0.14.2版本就正常了


waitForSelector returns undefined

Steps to reproduce
Tell us about your environment:

Puppeteer version: 0.12.0
Platform / OS version: Windows 10
URLs (if applicable):

What steps will reproduce the problem?
Please include code that reproduces the issue.
const btnNext = await page.waitForSelector(".wrapper-next>.mdl-button"); console.log(btnNext);
This code is performed after an ajax call because only until then will the button be appended to body.

What happens instead?
console.log shows that btnNext is undefined. I'm not sure what is the expected behavior here. The doc says it will return a promise object, but what will happen if 1. the element is not found or 2. the element doesn't appear before the time limit?
Now I can't really think of a case where returning undefined would make sense. It's either the element is found or timeout error is thrown. Any pointer is appreciated.

It seems the doc does not state that the promise of page.waitForSelector() is resolved in element handler:

returns:  Promise which resolves when element specified by selector string is added to DOM.

It seems it is just resolved in undefined or rejected when timed out.

@vsemozhetbyt Ah it seems that I misunderstood the documentation. This function will only tell when the element is ready on DOM, but doesn't get the element itself. Thank you.


Node version badges "invalid"

Suddenly a bunch of my Node.js version badges are saying "invalid". An example is https://img.shields.io/node/v/mime-db.svg

Ah, I think it's from the Node.js 0.12 release yesterday. Looking at your source (https://github.com/badges/shields/blob/321c725949cf58f04fd6b0de5d30af9ce5a6a9b0/server.js#L940-L941), there is the assumption that the first line will contain a file name that is a Node.js binary. Now that ICU is part of Node.js, this is no longer the case (as the file names in that file are sorted alphabetically).

Thanks a lot for your help! The fix is now live.

No problem :) Thanks for the quick turn-around :D shields.io is so awesome :100:


GIX-1284: New Sale lifecycle and proposal param

Motivation
Support new SNS Sale Lifecycle state: Adopted.
Changes
Most of the changes are candid related.
A part from those ones, the review should focus on:

New method getLifecycle in sns swap canister.
New method getLifecycle in sns wrapper canister, that redirects to the sns swap canister method.
Use new param sale_delay_seconds in converters.
New SwapLifecycle "Adpted".

Tests

Add test for new methods.

@mstrasinskis please review


DevOps not GDPR compliant for stakeholder role

Follow up #8304
Please update documentation to reflect Azure DevOps is not GDPR compliant for the stakeholder role.
We have multiple external organizations in stakeholder-roles in other projects. This is a data breach and a serious issue and should be addressed ASAP.
The issue @ Developer Community (https://developercommunity.visualstudio.com/content/problem/485973/userstakeholder-has-access-to-organization-setting.html) you are referring to has no activity from Microsoft. It is Under Consideration, so this is not going to be fixed in the foreseeable future. Let other customers know about this issue before they could face the same problem.
We need to restrict access immediately. We also need to consider in the next 72 hours if we need to notify our national privacy watchdog as we are required by national law ❗
Is there an audit trail available to these pages?

@JvanderStad We apologize for the confusion, issue https://github.com/MicrosoftDocs/azure-devops-docs/issues/8304 has been re-opened.
Please refer there for further updates.


Can we drop Sellenium?

Hello all,
As pointed to @danroth27 on Gitter, I think Sellenium is too much of a friction to get set up and working and that blocks people to contribute more as they have to install Java and its friends and not to mention it has to be kept running.
So, my suggestion was to use a modern and simpler framework for E2E tests and I have two to suggest:

https://www.cypress.io/ -> would be a good alternative that is simple to install and easy to code the tests
http://phantomjs.org/ -> could be used as the core headless browser so any widely used test framework like Jasmine, QUnit, Mocha, Capybara, WebDriver, etc. could be used.

I'm all for the first option as it makes contributions easier.
That is for E2E tests. Unit tests would still be ran in C#.
What the others on the team think? Is a PR acceptable with that?

Cypress isn't free software and the PhantomJS repository is archived. Both is not optimal.

Archiving the project: suspending the development
https://github.com/ariya/phantomjs/issues/15344
PhantomJS Is Dead, Use Chrome Headless in Continuous Integration
https://semaphoreci.com/blog/2018/03/27/phantomjs-is-dead-use-chrome-headless-in-continuous-integration.html

I absolutely agree but there is AFAIK no better alternative. Maybe you could drop the selenium standalone part. All the alternative are still based on selenium (like http://nightwatchjs.org)

I also agree that Selenium is inconvenient to set up. Unfortunately like others have pointed out, we don't have clear better alternatives.
Regarding cypress.io, we don't have a strong enough reason to take a bet on that any time soon. It would force us to rewrite all our E2E tests in TypeScript/JS, is not a free OSS product, is still in beta, has not been extensively battle-tested like Selenium is, and doesn't have broadly-established developer mindshare.
One small improvement we could make would be automating the startup and shutdown of selenium-standalone when the E2E tests run. That doesn't fix the installation inconvenience but helps with the day-to-day inconvenience.
I'll leave this issue open for a few days for visibility.

Absolutely there will need to be a rewrite of E2E tests and I’m ok doing that if that is the path.
I didnt noticed phantonjs has been abandoned.
Regarding Cypress, it is free for OSS projects forever. The only thing paid there will be the dashboard services only for closed source projects. And yes, it is open source as well.
It is a descent alternative.
Automate selenium startup still not ideal IMHO...

Thanks for the suggestion. However, we're not going to take a dependency on Cypress at this point for the reasons given above. Sorry!

I'll close this as we don't have any immediate plans to replace Selenium.


Add the abbility to switch between text editor

I mean something like this  :

I dont ofc need all of these text editors , just adding the basic one that are cable of reading .json .yaml .java .proprieties .


Replaced string-based interface with numerical constants

…so that a user does not have to remember commands like 'GET PYE'. String-commands are still supported but generate a ROS_WARN
https://github.com/ros-industrial/robotiq/issues/92

Thanks for the contribution....merging.


How can I get the slow moving average and trend intensity index?

I had the idea that I could just use the candles, but that wouldn't get me any of the past 60 day closing times as I had hoped.
How can I gather the historical close and open times over a 60 day period, or perhaps there is a easier solution to simply import charts you have already created in the IQoption gui.
Thank you in advance for any help you can provide

Slow moving average:
d=str(Stock.candles).split("'size': ")
                        while(len(d)<60):
                                time.sleep(1)
                                d=str(Stock.candles).split("'size': ")

                        while(num<len(d)):
                                a=float(d[num].split("'close': ")[1].split(',')[0])
                                Smax=Smax+a
                                num=num+1

                        Smax=(Smax/len(d))
                        Saverage=Smax #Slow moving average

Trend intensity:
Imax=0
                        Imin=0
                        average=0
                        num=(len(d)//2) #half
                        while(num<len(d)):
                                a=float(d[num].split("'close': ")[1].split(',')[0])
                                Imax=Imax+a
                                num=num+1

                        Imax=(Imax/(len(d)//2))
                        Iaverage=Imax#Trend intensity


Ask DevRel to stop scanning old repo

Ask the DevRel tooling folks to stop scanning the old repository, we will get duplicate samples otherwise.

Sent https://github.com/googleapis/sloth/pull/643 to remove from sloth

Done.


extraction: krml: recognize mul_underspec as a multiplication

I think was just an omission.
Also wondering how to add a test for this, @msprotz do you maybe know? Perhaps in the karamel repo?

Yes, you could add a basic test like let main () = 0ul FStar.UInt32.mul_underspec 1ul or something simple like that. There are probably such tests already? Curious this never got exercised in all these years!


Fixed video link for Demo 3

Just a small fix or Demo 3 video link ;)

Thank you @ayako it's the small details that make a HUGE difference!


Initial account configuration script/library for new account beginners

This would be in a new repository (handel-account-setup) and would help them set up a sane account configuration base on which to run handel-codepipeline and handel.

https://github.com/byu-oit-appdev/handel-quickstart

Creating a custom VPC will be too expensive, especially for personal accounts. Just use the default VPC and generate an account config file from that.

Resolves https://github.com/byu-oit/handel/pull/287
I decided not to go with the separate handel-quickstart project and instead implemented support for default VPCs in the library itself. See http://handel.readthedocs.io/en/latest/handel-basics/account-config-file.html for the documentation.


The data is not synchronized in real time between file and memory

After the service is started, a data is inserted into the db file of sqllite3 through navicat, the service does not select the data (the service is to select every 3 seconds); restart the service, open the sqllite db file, we can select the one data at this time.
the data is not synchronized in real time between file and memory?   Or does  go-sqlite3  not read data from files in sqllite3 db in real time?

Please provide more detail on your exact issue. What queries are being executing from navicat? What queries are being executed from your Go application? Is your Go application using any transactions? How are you opening the database file? Please provide the actual sql.Open line.

The first step is to use navicat to open the existing sqllite3 file and create a table.
CREATE TABLE IF NOT EXISTS topic(   id            TINYINT PRIMARY KEY NOT NULL,   name          NVARCHAR(30) NOT NULL,   update_time   DATETIME DEFAULT (datetime(CURRENT_TIMESTAMP, 'localtime')) );
The second step is to open my service, the code is as follows:
`
package main
import (
"database/sql"
"time"
_ "github.com/mattn/go-sqlite3"
"github.com/sirupsen/logrus"

)
func main() {
db, err := sql.Open("sqlite3", "trans.db")
if err != nil {
logrus.Errorln(err)
return
}
defer db.Close()
go func() {
	rows, err := db.Query("select id,name from topic")
	if err != nil {
		logrus.Errorln(err)
		return
	}
	defer rows.Close()

	for rows.Next() {
		var id int
                    var name string
		if err := rows.Scan(&id,&name); err != nil {
			logrus.Errorln(err)
			return
		}
                    logrus.Debugln("select ok", id, name )  // the data from navicat insertion; not obtained by query
	}
	time.Sleep(time.Second * 5)
}()

}
The third step is to insert the data in navicat and return to success.
insert into topic(id,name) VALUES(1,"myclass")
`
but the data from navicat insertion; not obtained by query.
If I terminate my service and then start execution, I get my insert data.

Which version of Go are you using (as reported by running go version)? Also, please try calling rows.Close at the bottom of the loop before calling time.Sleep and see if that changes anything.

@rittneje   According to your thinking, the problem still exists.
$ go version go version go1.12.4 linux/amd64

According to your thinking, the problem still exists.

Sorry, I'm not sure what you meant by this. Did you mean that you tried adding rows.Close like I mentioned and it still doesn't work?
To clarify, you are able to reproduce the issue with just the main function you pasted above, correct? No additional code is needed in the Go binary?
As a test, please try opening the same database via the SQLite CLI. Then update it via navicat, and then run your SELECT query at the command line and see if you get the right output.
$ sqlite3 trans.db
sqlite> select id, name from topic;

According to your thinking, the problem still exists.

Sorry, I'm not sure what you meant by this. Did you mean that you tried adding rows.Close like I mentioned and it still doesn't work?

Yes, it still doesn't work

To clarify, you are able to reproduce the issue with just the main function you pasted above, correct? No additional code is needed in the Go binary?

Yes,  I adding rows.Close like you mentioned and it still doesn't work

As a test, please try opening the same database via the SQLite CLI. Then update it via navicat, and then run your SELECT query at the command line and see if you get the right output.

I tested, sqlite3 cli and the service I wrote are the same problem.

@rittneje  Maybe the problem with navicat

Yeah, if you are observing the same issue with the CLI, it's possible that navicat is somehow causing it. Not really sure how though. Perhaps someone for the SQLite community will be able to shed some light on the matter. https://www.sqlite.org/support.html


test if fix worked

The deployements with netifly v16 are working now therefore the test was succesful and this PR is no longer needed


Can't filter search results to Zea mays4m

Can't filter to Zea mays4m from "All Species" search. It seems that, in Ensembl, the taxon_id is used to look up the name, and so it's set to the v3 "Zea mays".
This came up in #7

I think it's okay to show zea mays results from each maize assembly/annotation (in this case)

If you look at these search results, and filter to Zea Mays, you can see that only the v3 result is kept.

@ajo2995 but what you describe is probably what should happen.

Fixed in 1.0.6


feat: support wal-g to backup/restore pgsql

how to use:

config wal-g tools
kbcli cluster backup <clusterName> --method config-wal-g
wait this job to completed.
enable archiving

apiVersion: apps.kubeblocks.io/v1alpha1
kind: OpsRequest
metadata:
  generateName: pg-cluster-reconfiguring-
spec:
  clusterRef: <clusterName>
  reconfigure:
    componentName: postgresql
    configurations:
      - keys:
          - key: postgresql.conf
            parameters:
              - key: archive_command
                value: "'envdir /home/postgres/pgdata/wal-g/env /home/postgres/pgdata/wal-g/wal-g wal-push %p'"
              - key: archive_timeout
                 value: "60s"
        name: postgresql-configuration
  type: Reconfiguring

backup
kbcli clutser backup <clusterName> --method wal-g

how to cleanup the expired wal logs
when deleting the full backup, it will cleanup the outedated wal logs with this backup. but if no any full backup exists, the wal logs will retain all time.
manually clean wal logs if necessary

/cherry-pick release-0.8


daemon: Use LastSuccessInteraction instead of LastInteraction

cilium-agent periodically checks the connectivity to the k8s api-server by "kubernetes" probe. cachedVersion() returns a cached value of the k8s version to the probe if not expired or invalid.
The logic for evaluating the validity of the cache is as follows:

check if the api-server connectivity is healthy. If the last check was more than k8sMinimumEventHeartbeat(default: 1m) ago, then valid=false is returned.
if the api-server connectivity is given, returns valid=false if the last check was more than k8sVersionCheckInterval(default: 15m) ago.
otherwise returns the cached value and valid=true.

Currently k8smetrics.LastInteraction.Time() is used in the step 1, which is updated periodically regardless of whether the api-server connectivity is alive or not. This commit fixes it to use k8smetrics.LastSuccessInteraction.Time() instead.
Fix the logic of the api-server connectivity check for the kubernetes probe

/test

The L4LB is hitting a flake described in https://github.com/cilium/cilium/issues/31167. Rebasing onto the lastest main commit should resolve the issue.

@dylandreimerink Rebased to main.

/test


[WIP] Add iTunes plugin

Would you consider the idea of adding iTunes also to the list of music players? For now I just built something to show if it's running or not, but I see that it's something really easy to implement given that I can just copy most of the code already used in the Spotify one

By the way, just finished most the functionality, will wait for you to give me some advice with the design part (icon and colors you want to leave there) and this PR to be closed:
https://github.com/buley/itunes-node-applescript/pull/1/files

@rodrijuarez I will clone your build tomorrow onto my MBP and test this out, then come back and provide feedback.
Thanks!


Nothing to switch on or off fragments, or various tools.

    @Override
    public void onBackPressed() {
        if (tryCloseFragment(ColorStitchBlockFragment.TAG)) {
            return;
        }
        super.onBackPressed();
    }

Adding that to the MainActivity will make it so that the ColorStitchBlockFragment is closed when you press back, and if already closed will exit (consistent with Android best practices (some amount of hitting back should exit)).
But, there's no way to turn on or off fragments to display various bits of information etc. Or any any idea how such a thing would happen, or if it needs to. But, mobile screens are small, and if you want to use several things like compare the size of the image to a given hoop size, you would need some place to select the hoop. Or if you wanted to break the Pattern apart and look at each section individually, you would need to be able call up a different fragment as such.

I think for future work we should probably try to put these tool settings/selection in a Material design layout using slide out menus like the following link.
https://material.google.com/patterns/navigation-drawer.html#navigation-drawer-specs
Your thoughts?

You can use navigation drawers, they totally work and look sort of nice. In Touch Embroidery, I use a drawer for the various layers, and each layer has a thumbnail, and some basic data about that layer, and things can be rearranged.
You only have so much screen space, and the way it's setup currently sort of takes a lot of that space. And when you close the fragment, there's no way to get it back. Though, at present, other than statistics, and colors currently it doesn't have any other information.
Though if the whole thumbnail of the embroidery thing in part 2 were done up, such that there was a database of embroidery works, that one could have a fragment for that, that would  work for a drawer.
Though it very likely would be better as a different activity. Especially a PICK intent looking for an embroidery file, and just use that like a gallery. Save embroidery objects to it, get them back out of it, and a nice view of the embroidery library. Especially if it saved the files out too. So you could do whatever that "Embrotailer lite" thing was trying to do, but much better in that you could save a library of embroidery to the activity and convert it to PES and upload it directly to somebody's embroidery machine.
I wrote an Android Vector Icon Drawer, called DAVID: Android Vector Icon Draw, that includes a library a bit like that. Where it simply has something that responds to a PICK intent, allowing you to send out the request, then loads up the Library activity, allows you to select requires icon svg, and loads that up. -- But, because it's done via an intent, anything that requests a file like that can use the same library. (I can pick them from Touch Embroidery just as easily as from the icon drawer). --- So really other recently viewed files such things might not require their own fragment.
Sure, I guess. I could toss that into a drawer, in pretty short order. And we can always switch out the fragments in the drawers.

Implemented


References not working as expected

Hi there!
I have the following data:
{
		"companies": [
			{
				"id": 4321,
				"company_name": "enim aliquam"
			},
			{
				"id": 4671,
				"company_name": "dolorem ex"
			}
		],
		"employees": [
			{
				"id": 1,
				"username": "Abbigail Yundt",
				"companieId": 4321
			},
			{
				"id": 2,
				"username": "Ted Cruzo",
				"companieId": 4321
			},
			{
				"id": 3,
				"username": "Amara Ratke",
				"companieId": 4671
			}
		]
	}

Now if I try the request GET localhost:3000/companies/1/employees with Postman I get this response:
[
    {
        "id": 1,
        "username": "Abbigail Yundt",
        "companieId": 4321
    },
    {
        "id": 2,
        "username": "Ted Cruzo",
        "companieId": 4321
    },
    {
        "id": 3,
        "username": "Amara Ratke",
        "companieId": 4671
    }
]

Seems to me this must be a bug. I was thinking the service could not figure out the reference if I used companies and companyId due to the plural not simply adding a '-s; suffix. So I tried both 'companyId' and 'companieId', same result.
Can someone shed some light on this for me? Thanks in advance!

Nevermind, I just tried the reference 'companyId' and it suddenly worked.


Feature Request: Allow tab title to be set by console apps

Add support for console apps that attempt to set their window title:
cmd => title "Title"
pwsh => $host.ui.RawUI.WindowTitle = "title"
bash => export PS1=
This works in current shells and is useful for allowing long running scripts to display a current action message before executing a block of long running commands that emit a lot of superfluous console output (compiler output, file copies, etc) and would reduce switching back and forth to a tab just to view its progress
$host.ui.RawUI.WindowTitle = "compile..."
# build command
$host.ui.RawUI.WindowTitle = "containerize..."
# docker build
$host.ui.RawUI.WindowTitle = "deploy..."
# docker push

... have you tried this? It works.

If you are setting a tabTitle that will, by design, override whatever the shell says.

Yes, I have tabTitle set. Would it not make more sense to be able to override that via running scripts?

See, the problem with that is the path that you're already seeing without setting tabTitle is a title that's emitted by the shell. So you can't really have it both ways, where the tabTitle overrides the thing set by the shell, and the shell is able to override the tabTitle.

Understood, thanks for the clarification


WebApp:Error while restarting a webapp

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az webapp restart
Errors:
cannot import name 'DefaultErrorResponseException' from 'azure.mgmt.web.models' (/usr/lib/python3/dist-packages/azure/mgmt/web/models.py)
Traceback (most recent call last):
python3/dist-packages/knack/cli.py, ln 233, in invoke
    cmd_result = self.invocation.execute(args)
cli/core/commands/__init__.py, ln 558, in execute
    self.commands_loader.load_arguments(command)
azure/cli/core/__init__.py, ln 480, in load_arguments
    self.command_table[command].load_arguments()  # this loads the arguments via reflection
...
cli/command_modules/appservice/custom.py, ln 39, in <module>
    from azure.mgmt.web.models import KeyInfo, DefaultErrorResponseException
ImportError: cannot import name 'DefaultErrorResponseException' from 'azure.mgmt.web.models' (/usr/lib/python3/dist-packages/azure/mgmt/web/models.py)

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az webapp restart --resource-group {} --name {}

Expected Behavior
Environment Summary
Linux-5.13.0-7614-generic-x86_64-with-glibc2.33
Python 3.9.5
Installer: DEB

azure-cli 2.18.0 *

Extensions:
azure-devops 0.19.0

Additional Context

route to service team

Please update the cli to latest version 2.29.1. It should resolve the issue.

closing due to lack of response. Please file a new issue if this is still a problem.


Improper indentations in serialized output of versions 0.9.*

This following sample code
#[derive(Serialize)]
struct Data {
    a: Vec<String>
}

# ---main---
let data = Data {
    a: vec!["row1".to_string(), "row2".to_string()]
};
let ser = serde_yaml::to_string(&data).unwrap();
assert_eq!(ser, "a:\n- row1\n- row2\n");

produces output: "a:\n- row1\n- row2\n" as the value of ser
whereas the expected output is: "a:\n. - row1\n. - row2\n". Notice the 2 spaces before each vec item.
The current serialized output is improper as per yamllint linter

It's not clear to me that either one is more proper than the other. The YAML spec exclusively shows no leading space before the - in a map value, for example in https://yaml.org/spec/1.2.2/#example-mapping-scalars-to-sequences.

The standard seems to allow for both kinds of indentations.
My actual concern is that the 0.9.* versions serializes data differently compared to the previous versions. So this broke my build.
Does this change originate from unsafe-libyaml ?
If you are convinced about unsafe-libyaml and intend to use it in future versions, sounds OK to me.
Else it makes sense to conform to more objective criteria like passing yamllint lint tests.

My actual concern is that the 0.9.* versions serializes data differently compared to the previous versions.

It's intentional that 0.9 is not behaviorally identical to 0.8. I am sure this is not the only serialization difference between the two.


SIMD optimizations

It would be nice to use SIMD for types that can support it. At the moment our SIMD support is pretty limited, but ASM is a possibility - perhaps with a fallback to regular operations.

Do you monitor this issue for regressions?


Prettier Plugin Tailwind not working with EJS

I have a Nodejs Express project. I am using EJS as the template partial language. This does not seem to work. Even after install this plugin and having prettier work, the automatic class sorting does not work.
Steps to reproduce the behavior:

Install prettier
Install prettier-plugin-prettier
Try to save file to format or running npx prettier --check views/
Does not work

Expected behavior
Sort my tailwind css classes
Screenshots
npx prettier --check views/ Checking formatting... [error] No supported files were found in the directory: "views/". All matched files use Prettier code style!
Versions:

prettier-plugin-tailwind version: 4.0.0
Operating system: Windows
NPM/Yarn version: 8.1.2

Hi @SavarJ, sadly I've just put a note on the README that this package is no longer maintained.
I suggest using the official prettier-plugin-tailwindcss package instead.


fix: maintain consistent topbar colour on login

Details

This PR fixes the issue where the top bar was not of correct colour when opening the initial login page.
While implementing the fix, I found a few more issues. The animation for changing the top bar colour was running even when:

The animated value was same as the previous animated value or was null.
When it was less than the new animated value (This happened whenever we updated top bar colour, the value became from 1 -> 0 -> 1. It was needless to run the animation during the 1 -> 0 phase).

As such, I added a condition in the useAnimatedReaction function that prevented the top bar colour from changing if any of the above conditions were satisfied.
Also, I found out that it was much cleaner to replace the static value of the top bar colour being set in the CustomStatusBar component to a dynamic colour based on the current active route. This was contrary to what I proposed initially where we were essentially running the above logic inside a new useEffect hook inside the NavigationRoot component.
Fixed Issues

$ https://github.com/Expensify/App/issues/23345
PROPOSAL: https://github.com/Expensify/App/issues/23345#issuecomment-1645491438
Tests

Open the App and Logout.
Verify that the login screen has the correct top bar colour.
Login and browse the various screens.
Verify that all of them have the correct top bar colour.

[x] Verify that no errors appear in the JS console

Offline tests

N/A
QA Steps

Open the App and Logout.
Verify that the login screen has the correct top bar colour.
Login and browse the various screens.
Verify that all of them have the correct top bar colour.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

https://github.com/Expensify/App/assets/30054992/94809fa2-4f01-447f-9a92-7a17cc2a2de0

Mobile Web - Chrome

https://github.com/Expensify/App/assets/30054992/94effebb-100e-43bc-9bb7-5830632d2a1f

Mobile Web - Safari

https://github.com/Expensify/App/assets/30054992/d6e8b827-ce08-4eed-b6af-c57e9b6ad8e9

Desktop

iOS

https://github.com/Expensify/App/assets/30054992/5308b4da-6a83-4e20-bcd7-43352bba272e

Android

https://github.com/Expensify/App/assets/30054992/cda0aaf2-432c-48fc-8c82-3940bd812279

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://github.com/Expensify/App/assets/85645967/f38e337a-c557-4db2-8112-71ecb054ce72

Mobile Web - Chrome & Mobile Web - Safari
https://github.com/Expensify/App/assets/85645967/0d729543-ac69-4df4-8ef5-f37252f3a2d3

iOS & Android
https://github.com/Expensify/App/assets/85645967/b13a80b8-c85b-476a-be90-55bc67a7c360

Thanks guys! Looks good to me too but marking it as hold freeze to focus on conference related PRs.

🚀 Deployed to staging by https://github.com/mountiny in version: 1.3.68-6 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/Julesssss in version: 1.3.68-17 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/mountiny in version: 1.3.70-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/thienlnam in version: 1.3.70-8 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


Error when executing bazel build py_grpc_library in MacOS

What version of gRPC and what language are you using?

gRPC v1.27.3
Python

What operating system (Linux, Windows,...) and version?

MacOS 10.15.3

What runtime / compiler are you using (e.g. python version or version of gcc)

Bazel 2.2.0

What did you do?
I tried compiling from .proto to the Python version with py_grpc_library, but some errors occurred in the process. For more details about how to reproduce the bug, you may refer to the sample code here.
However, the process somehow completed successfully when I tried running it on Ubuntu 18.04 LTS.
What did you expect to see?
Build completed successfully.
What did you see instead?
Error message that prevented the build to complete.
 Or perhaps this only happens in my laptop? It seems that this problem still occurs even after I update my grpc to v1.28.1 and bazel to v3.0.0.
Also, it looks like the some of the dependencies still use python 2?

I am getting this too, it seems to be the same flavor as this issue https://github.com/grpc/grpc/issues/13856

Hi, sorry, does anyone else encounter this issue? Or perhaps this only happens in my laptop? It seems that this problem still occurs even after I update my grpc to v1.28.1 and bazel to v3.0.0.
Also, it looks like the some of the dependencies still use python 2?

Same here with grpc v1.33.2.


[Sprint: 60] XD-3632 Log reactor completions at info level.

Fixes #1810 (GitHub). Fixes XD-3632.

merged


Fix documentation for supportedLocales

The old documentation was still describing old behavior

Added a link to the Unicode extension of BCP47 with the algorithm described.


Fix advanced logging document not consistent

custom attribute use some_value is most place.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


There is a typo in the Doctrine driver

Problem
The doctrine driver fails because there is a space missing in this query:
$query = 'SELECT id, message FROM bernard_messages
                  WHERE queue = :queue AND visible = :visible
                  ORDER BY sentAt, id LIMIT 1' . $this->connection->getDatabasePlatform()->getForUpdateSql();

Location: DoctrineDriver.php:104

fixed on master, see #240, #223

Fixed on master (next alpha will be tagged soon)


Feature Request: Keyboard shortcut to exclude current video from future playback

I know Aerial supports using the right arrow to skip a video, if possible I'd love to see an additional keyboard shortcut to exclude a video from future playback.
For example, if a video is playing that I don't like, I could hit the down arrow which would uncheck that video in the settings and not play it again. It would then remove it from the cache and save space for more favored videos.
With the ever growing list of videos, this feature would allow users to quickly curate screensavers to just ones they want to see. Otherwise, it's tedious to manually uncheck a video from the settings. Especially since it's difficult (if not impossible?) to know which video just played and the corresponding name in the settings.

Hi @byalextran
So the problem is, starting with Catalina, and still in Big Sur, Aerial can no longer intercept keyboard presses. So I'm a bit reluctant to add functionalities that are limited to only past OS releases (that I no longer have around to develop on/test, furthermore).
With 2.0 however, I'm doing a complete overhaul of the video list so hopefully you can spot a lot more easily the videos you want to enable/disable. So maybe that will lower that need.

aww, bummer. curse you catalina (and big sur)! 😅
and yeah, if there's a way for the screensaver to display the name of the video (that matches what's in the settings), that would help in this case. something like china - day - great wall 1.
thanks!

@byalextran check out beta1, there's a specific button to hide the videos you don't like :)

https://github.com/JohnCoates/Aerial/releases/tag/v2.0.0beta1
There are many other changes so make sure you read the release notes.

@glouel you're a miracle worker! just went through and hid a bunch of videos. super easy/quick process. thanks a bunch! great job with the 2.0 UI refresh.


num of gpus

Hi, I tried to run this program with two GPUs, and it turned out to be very different from the result of 4 GPUs, and the loss of using 2 GPUs drops quickly. Is this program related to the number of GPUs？

Hi, re-ID experiments are somewhat sensitive to the number of batch size and GPUs. We use 4 GPUs empirically, since such a setting generally achieves optimal performance. I did not test it on 2 GPUs, how does it perform? I will further look into how to decrease its sensibility.

I tested on market1501 to dukemtmc, map decreased by about 5%.

Hi, when I train the model, sometimes there are two problems:

It got stuck, not running anymore.
Warning "OMP: Warning #190: Forking a process while a parallel region is active is potentially unsafe."
My experimental environment: cuda 10.0, python 3.7.3, torch 1.2.0, faiss 1.6.3.
Can you provide me your environment settings? Thank you!

Hi,
My environment is: cuda 9.0, python 3.6.9, torch 1.3.1, faiss 1.6.3. I also tested with torch 1.1.0.
I haven't met your problems before. On which line did it get stuck?

I don't know which line it got stuck, but I think these two problems are related to sourece and target dataloader https://github.com/pytorch/pytorch/issues/24927

You can also try to use other search_option (default:0) for compute_jaccard_distance() to test if the problem is with the faiss. https://github.com/yxgeee/SpCL/blob/master/spcl/utils/faiss_rerank.py#L37

Okay, thank you!


potential overfitting

Hi,
I'm wondering about how to properly select the number of epochs to run the algorithm. Should I run the algorithm once with default epochs, evaluate when the score appears to numerically stabilize, then re run it with a lower number of epochs and use that imputed information? I'm wondering if the team has utilized a more systematic framework for evaluating how to properly set the parameters of the algorithm, and avoid potential overfitting? Any thoughts and suggestions would be appreciated!

Additionally, I'm wondering if there's a mechanism already in place where the algorithm will choose the weights, etc corresponding to the number of epochs where the score has stabilized sufficiently during the training. From what I can tell I don't think so, but any thoughts on this also appreciated!
Thanks!

Hi @jayypaul, thank you for your interest in Tangram!
We haven't evaluation the effect of the different number of training epochs in this version! However, its a good idea to see how much the mapping changes with different number of epochs by analyzing the cell annotation maps, diagnosis plots as well as AUC.
@Hejin0701 do you have any other recommendations/suggestions?

Hey, thanks for your response, on this post and the other. I'll keep these ideas in mind.
Best Regards,
Jordan W.

Hi @jayypaul Thanks for your interest in Tangram. Normally running large number of epochs does not cause the overfitting for Tangram. I have tested the Tangram mapping from 1E3 up to 1E5 epochs, the general cell type distribution stay pretty much the same. However, as Shreya mentioned, we do not have embedded tool to evaluate overfitting. One thing you can do if you are worried about overfitting is to run Tangram mapping at both cell (mode='cells') and cluster (mode=clusters) level and then compare whether there are any significant difference between the two annotation maps. The cluster level mapping consists of much smaller parameters (~2 to 3 order of magnitude smaller) compared to cell level mapping and thus is much less prone to overfitting.

Hi Hejin, thanks for your insight and I appreciate the advice. Good to know that it's less of an issue than I thought!


feat(bo): modif libelle page utilisateur

close jira 631

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


feat: cherrypicker support auto-add picked label

close https://github.com/ti-community-infra/tichi/issues/460
cherrypicker support auto-add picked label.

/assign @Mini256

/merge


Timer

Removed vote_timer function.
Added Discord task to routinely check for concluded proposals.
Added corresponding function in gov/proposals.py which handles the logic for the Discord task.
Added JSON file to track ongoing votes. These are purged when a vote has concluded and the result has been posted.
Removed leading spaces for the proposal information posted to the forum channel, the formatting of this message could be thrown off previously.

Closing this for now.

Closing this for now.

why?

Closing this for now.

why?

Working on merge issues and didn't want to leave it hanging

What do you mean by hanging?

What do you mean by hanging?

Sorry to be clearer I meant I didn't want to leave the PR open when I was going to make other changes first. Am going to try have this one ready today anyway now :)

What do you mean by hanging?

Sorry to be clearer I meant I didn't want to leave the PR open when I was going to make other changes first. Am going to try have this one ready today anyway now :)

Ready for this one to be reviewed and merged when ready :)


Add more workloads

It would be great if we could have bigger more interesting workloads. Using the RISC-V tests would be a good place to start.

https://github.com/embench would be a good set of workloads to get running!


CRUD /hwinfo

[x] GET /api/1.2/hwinfo
[ ] GET /api/1.2/hwinfo/:id
[ ] GET /api/1.2/hwinfo/:name
[ ] PUT /api/1.2/hwinfo/:id
[ ] PUT /api/1.2/hwinfo/:name
[ ] POST /api/1.2/hwinfo
[ ] DELETE /api/1.2/hwinfo/:id
[ ] DELETE /api/1.2/hwinfo/:name

We'll have to tackle pagination (which we haven't yet, could follow the pattern of the query_builder) with this one because of the amount of data

this endpoint is addressed in #2232


Theme Watch triggering for all image files in /assets

What happened
When I do theme watch lately, it will usually run as expected for 10-30 minutes, until eventually it perceives all the images files in /assets as having been updated, and starts trying to upload them all.
What I expected to happen
Only upload files when they're actually changed.
Steps to reproduce

Theme watch
Work on theme for about half an hour as normal
Observe in the command line, "Received Update event on assets/img.png" for every image in the assets folder

My Environment
OS (including version): Windows 10 v 1803
Themekit version: 0.7.5
Ignore Files(if any):

Do you have any software on your computer that may be scanning files? I have a suspicion that it may be a virus scanner but I can't be certain. I would normally say to ignore image files anyways because they don't need to be watched while you are developing your site.

how do i ignore image files?

There are some examples in the documentation https://shopify.github.io/themekit/ignores/#ignores-in-configyml-example

@samjross have you had any further problems with this?

Closing because this issue seems to have been solved.

It actually hasn't stopped doing it, but it's not specifically image files as I initially thought. It looks like it's just all files, or maybe just all files in /assets/. I thought it was just images because I have mostly images there.
When it happens I can't even press ctrl+c to stop the process, it just continues until I close the console.
Still happening with most recent update of theme kit

What is your editor? themekit uses windows ReadDirectoryChangesW functionality in the background, which is really well integrated with windows so there really should not be any fluke events. Something is touching either your files or the directory itself.

I'm using sublime text 3

Okay some extra questions that may help

Are you running themekit in cmd.exe or powershell or something else?
Do you have your files on your main harddrive or are they on an external drive?
Do you leave themekit running for days at a time?
Is it only the asset folder or are templates being uploaded as well?

Hi tanema.

Are you running themekit in cmd.exe or powershell or something else?

Running it under Cmder ( which use ConEmu ) configured for use of GitBash. Or to cut it short - GitBash,

Do you have your files on your main harddrive or are they on an external drive?

They are on the main hard drive, but not in the "C:" drive but at my "D:" drive.

Do you leave themekit running for days at a time?

No, the PC is turned of every day and I switch between different projects every day, so it's not on for more than 3-4 hours a day ( max 8 hours if there is a big project ).

Is it only the asset folder or are templates being uploaded as well?

No its everything and it's randomly some times, I mean that it uploads different files from different folder one after another.
Here is a video of the issue when it happens for me: https://streamable.com/8wwx3 ( please note that because of NDA can't show the full console with the store name, that's why it's cropped )

Another report of this from @besteven
with the environment:

OS [e.g. iOS]: Window 10
Themekit version [e.g. v0.7.5]: v0.8.1 (the lastest version)
Editor [e.g. atom, sublime]: VS Code
Ignore: None

This seems to be specifically an issue with windows 10 events. I will get access to a windows 10 computer soon to test this.

Okay! I have been able to reproduce this on windows 10 only.

Okay I can confirm that it is because windows 10 fires write events if even any of the timestamps change, including last_viewed. This makes it complicated to fix because now I need to add in more complicated checks to make sure that the file contents have actually changed. I will be in contact about any progress made on this.

@ikolarov @samjross @besteven
Please try out this version with an updated fix for windows file watching by running:
theme update --version=v1.0.0-issue519
This is a special version of the pre-release themekit with a new filewatcher. Please give it a try and report if it has fixed your issues and if you experience any other bugs with it.

@tanema from what I can see it works OK for me now. There was a single instance where the watch froze and stop updating but this was a single instance and couldn't reproduce the issue a second time.
It seems that the issue is fixed on my end, we will install it on all the PC's here and see if any other have issues with it.
Thank you for the support @tanema!

Okay this has been merged into master so it will be on the prerelease.
Please use the prerelease going forward and open any issues for the prerelease.
You can update to the prerelease by running theme update --version=v1.0.0-pre


Feature Request: Public Docker Image and Helm Chart

I’d like to request the addition of a public Docker image and Helm chart for this great project. This would greatly simplify deployment, allowing users to deploy the application as a blackbox service more efficiently. It's pretty obvious that providing these resources would enhance accessibility and streamline the integration process for various deployment environments.
Thank you for considering this enhancement!

Can you split the request into two (as they can be developed separately, yet likely one after another)? In other words, I could work on a Docker image but have no intention for a helm chart 😉

@jaceklaskowski I think the tasks are enough, to fit PRs at the subject

As part of the repo migration, this issue has been added to unitycatalog #433


toFlatJSON(): My attempt at what I think is meant by the flatten() feature for reporters

I wanted to have an output of the JSON in such a way that I could search over it meaning I would need properties like name and type as opposed to each of the metrics being keyed by the name of the metric e.g. requestsPerSecond.  This will help me  getting the output into elastic search and the like too.
This feels like the intended functionality for the flatten() method mentioned in the todos in the README but I could be wrong.  Not 100% sure about the name (toFlatJSON).  I did think about a method which is called  flatten which would take the original output of toJSON but this is the implementation I have gone with for now.

I just found your elastic search reporter.  I will close this pull request.

:+1:


Merge ui service annotations with our official ones

What changed?
I merged the operatorservice and workflowservice protos between here and our UI repo.
When a conflict arose I chose the version in the UI; this may not be the correct choice but I hope to rectify that as part of this PR
Why?
The new proto library we're attempting to use crashes if you have multiple service definitions for a given proto. gogo/protobuf technically should have but didn't, so now we need to merge our definitions so there's only one.
This blocks me from upgrading our UI and CLI repos (our CLI embeds the ui-server)
Breaking changes
No

The UI tests pass with this change even before my update PR hits, we should be good to continue.


Removed extraneous "the" in alerts-automatic-migration.md

@Reisclef : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Reisclef - thanks so much for catching this double word error.


ensure: no binary found

Noticed there was some plan for documentation of this error!
https://github.com/prisma/prisma-client-go/blob/b9cc5909b677c122bcb6a771ef179bff40aa1ef7/engine/lifecycle.go#L118
I'm on Windows so I assume that's the issue. I generated the code using Docker because the latest version doesn't support Windows!

This comment might actually be outdated.

I generated the code using Docker because the latest version doesn't support Windows!

Could you elaborate?
Can you try using v0.0.8 which should still support windows?

Yeah I'm doing that now and it works fine!
I didn't know about the new code generation stuff (query-engine-debian-openssl-1.1.x_gen) so I thought I could just spin up Docker to generate the Prisma code!
It's running fine now though, I'll wait for Windows support upstream before updating 👍

Cool! You don't need docker though, do you?

A general note: when you encounter the ensure: no binary found error, it's probably best to re-run go run github.com/prisma/prisma-client-go generate to make sure you have the correct generated code.

I couldn't run the generator on Windows for the latest version so that's why I used Docker.
But for now I just cloned, checked out and built from source to make sure I had the right one - it's all running smoothly now!


Feature request: options for overriding on specific filetypes? yaml looks bad

The treesitter parser for yaml sticks the yaml keys at TSField which is white on this color scheme
https://github.com/ikatyang/tree-sitter-yaml/issues/28

using the  autogroup recommended in the issue I was able to put it at the green used in github-nvim-theme which is closer to what is on the github website
  augroup github-yml-theme
      au!
      au BufEnter *.{yaml,yml} :hi TSField guifg=#3fb950
  augroup END

vim.api.nvim_create_autocmd("FileType", { pattern = { "yaml", "yaml.ansible" }, command = "hi TSField guifg=#3fb950" })

My question is if we can get something more built in to override on filetypes to fix issues like this?
Or maybe better I can make a pull request to add this auto group to fix the color scheme for yaml for this one issue?
Which do you think would be better?

I kind of like this option if we want to put it in the wiki
require("github-theme").setup({
  theme_style = "dark_default",
  overrides = function (c)
    -- fix the look of yaml in this color scheme
    vim.api.nvim_create_autocmd("FileType", { pattern = { "yaml", "yaml.ansible" }, command = "hi TSField guifg=".. c.green })
    return{ }
  end
})

since overrides is a function then c.green is available

Can't you apply<EMAIL_ADDRESS>as an override?

Can you override the unassigned highlight by enabling dev mode? It's used to assign a new highlight that is not overridden by the colorscheme.
require('github-theme').setup({
  -- ...
  overrides = function(c)
    return {
      -- ...
<EMAIL_ADDRESS>= { fg = c.red },
    }
  end,
  dev = true,
})

@ful1e5 that works well. Thank you 👍


Add option for dash show wanted albums as list + SR dash small edit

HP wanted albums list option for dash
SR small edit to align the airdate to right (same as CP does for release year)

Thanks!


Include reason for BadApiResponse in PromoteTransactionCommand

PromoteTransactionCommand calls CheckConsistencyCommand internally to determine if the tail transaction can be promoted or not.
When status in CC response is False,  BadApiResponse is raised which should contain the info field from CC response as well. This is the reason returned by the node.

The response payload should already be included in the context attribute of the exception:
https://github.com/iotaledger/iota.py/blob/master/iota/adapter/__init__.py#L484-L496

@todofixthis I'm talking about this exception:
https://github.com/iotaledger/iota.py/blob/9416068a13f12d09b27dd9522f5885ff0eaae25c/iota/commands/extended/promote_transaction.py#L38-L43
The response from the node should be alright from the adapter's perspective, it it should contain status, info and duration fields.
Btw a question: how are exceptions raised with with_context should be handled in application code? What is the best practice to get also the context and not just the error message written to the output?

with_context is meant to be a way for developers to include other relevant information with the exception that is more lightweight than trawling through the stack frames.
Including the information in the exception message is often convenient, but sometimes not (e.g., the context for an exception might be a bundle, and that means a VERY long exception message!).
Attaching additional information to the exception requires a bit of extra effort on the application developer's part, but it opens up additional options for troubleshooting.
In particular, I used this technique on a previous project that logged exceptions (and their context values) to a database, which proved invaluable for diagnosing errors that occurred on production.
Additionally, for developers who are not familiar with PyOTA internals, this gives them a way to inspect/debug values that are relevant to the exception, in a way that doesn't require them to edit/debug 3rd-party code.

Thanks @todofixthis  for the explanation, I'm gonna include it in for #310.


empty objects output for empty modules

I have some module files that don't actually export anything (they are doing things like adding event listeners to a page), but in order to include them I'm defining them as modules:
goog.module('foo');
document.addEvent(...)

then in my top-level js file I have:
goog.module('site');
goog.require('foo');

Each of these "empty" modules produces empty object at the end of the total output.  The last bit of my compiled file is:
({});({});({});({});

How are you running the compiler? I don't see that in my simple test case.
http://closure-compiler-debugger.appspot.com/#input0%3Dgoog.module('foo')%253B%26input1%3Dgoog.module('bar')%253B%250Agoog.require('foo')%253B%26conformanceConfig%26externs%26refasterjs-template%26includeDefaultExterns%3D1%26CHECK_SYMBOLS%3D1%26CHECK_TYPES%3D1%26CLOSURE_PASS%3D1%26FOLD_CONSTANTS%3D1%26INLINE_VARIABLES%3D1%26MISSING_PROPERTIES%3D1%26REMOVE_UNUSED_VARIABLES%3D1
On Fri, Jul 3, 2015 at 8:26 AM, kaaaahhhhnnnn<EMAIL_ADDRESS>wrote:

I have some module files that don't actually export anything (they are
doing things like adding event listeners to a page), but in order to
include them I'm defining them as modules:
goog.module('foo');document.addEvent(...)
then in my top-level js file I have:
goog.module('site');
goog.require('foo');
Each of these "empty" modules produces empty object at the end of the
total output. The last bit of my compiled file is:
({});({});({});({});
—
Reply to this email directly or view it on GitHub
https://github.com/google/closure-library/issues/487.

no response from author


[WIP] ColorManager proposal

This issue is a proposal for ColorManager a class to handle setting of colors in our layers where we color individual data points (i.e., Points, Vectors, Shapes, Tracks). Currently, this is handled by code in each layer. Many of the layers share code leading to a ton of code duplication. Additionally, there is a bit of fragmentation (e.g., Tracks handles coloring by property differently than Points, Vectors, and Shapes.
Proposed API
Similar to our TextManager, the ColorManager would be a dataclass that contains the current color values as a property and has the methods for setting the colors. ColorManager would not store the layer properties. Each layer utilizing ColorManager would have one ColorManger object for each display property that has a color.
# create a points layer with blue points
points_layer = viewer.add_points(data, face_color='blue')
points_layer = viewer.add_points(data, face_color=[0, 0, 1, 1])

# create a points layer with face color set by the property 'class', use defaults
points_layer = viewer.add_points(data, properties=properties, face_color='class')

# create a points layer and specify some mapping options
face_color = {
    'color': 'class',
    'mode': 'colormap',
    'colormap': 'viridis'
}
points_layer = viewer.add_points(data, properties=properties, face_color=face_color)

# update the face color colormap
points_layer.face_color.colormap = 'plasma'

Mapping modes
I propose the following modes for setting colors:

direct: the user provides the exact colors to use. This is either a single color that is broadcasted or an array of colors (one for each datum.
direct_mapping: a mapping of each property value to a color. This would be a dictionary where the keys are the property value and the values is the color.
color_cycle: a cycle of color is applied to the property values. This is useful for categorical properties where the user doesn't want to specify a color for each property value.
color_map: mapping of continuous property values to color.

Questions

Do we want to maintain support for the current API? In particular, we have many properties for color at the layer level (e.g., layer.face_color_mode and layer.edge_color_mode) that would be unnecessary with ColorManager
Do we want persistence of settings when we switch between modes? Currently, if we are in color_cycle mode, switch to colormap mode, and then switch back to color_cycle mode, the original color_cycle settings are "remembered".

Related issues
Some related issues:

#1356
#1491

Approach:
We could break this up into a series of PRs:

[ ] Create ColorManager, implement in Points
[ ] Create layer controls GUI for ColorManager and add to Points
[ ] Add color manager + layer controls to Shapes
[ ] Add color manager + layer controls to Vectors
[ ] Add color manager + layer controls to Tracks

@adamltyson, I recall that you are using properties to color point in some of your applications. It would be great to hear if this proposal would fit your use case and/or if there are any issues you come across that you think we could solve here.

@kevinyamauchi, yep, this proposal looks great. Currently I only have two classes so it's pretty simple, but soon we'll have an application with many more, and being able to flexibly encode these with colors would be great.
I don't have much to add, but this looks like a good idea to me. I don't think it would solve any specific issues, other than making my life a bit easier :thumbsup:

From this comment in #2204 by @sofroniewn , we will do the following after #2204 merges.

After this merges, I could see the following next steps

[ ] refactor vectors to use a private _edge ColorManager
[ ] refactor shapes to use a private _edge and _face ColorManager
[ ] refactor tracks to use a private ColorManager (have to think about name)
[ ] Create a new Edge > ColorManager class that also included width as an attribute
[ ] Give points a public edge and face and deprecate old attributes.
[ ] Give vectors a public edge and deprecate old attributes
[ ] Give shapes a public edge and deprecate old attributes
[ ] Use tracks public colormanger

Now that #2204 is merged I think we should continue the "private" refactor in as many places as possible first - @jni also mentioned trying to use this in labels too, and then reconvene before deciding exactly how to expose everything publicly.
I think @jni wasn't sold yet on the layer.edge.color API, but we can defer that decision until we've gotten further. How does that sound @kevinyamauchi?

I agree that we should perform the private refactor first and then determine how we can should best set up the new public API when we can test it on all of the layers.
I like the aesthetics of layer.edge.color, but I think it will be difficult to implement that sort of hierarchal API for all ColorManager fields unless we allow ColorManager to access the layer. This is because since some of the ColorManager fields require knowing what the layer properties are to set properly (e.g., setting the color to map to a property by passing the name of the propety).
Perhaps we could keep the layer.edge_color setter, but it would accept both a value (e.g., color or property name) or a dictionary that can set multiple ColorManager fields. We can then in the setter "inject" the necessary values from the layer into the dictionary before passing it to the ColorManager update method. The API would then look something like:
# set the edge color to a single color
points_layer.edge_color = 'red'

# set the edge color of each point individually
points_layer.edge_color = ['red', 'blue', 'magenta']

# set the edge color to map to the property point_type
points_layer.edge_color = 'point_type'

# set the edge color to map to the property point_type and set the colormap
points_layer.edge_color = {
    'color': 'point_type',
    'continuous_colormap': 'viridis',
    'color_mode': 'colormap'
}


⚠ Processors has degraded performance

In 8b09873, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 89 ms

Resolved: Processors performance has improved in 0fee04d.


Improving the documentation regarding select()

Improving the documentation regarding select() so that no false guarantees are made about state and saga run timing

Yeah; that's a subtle case, thanks


[Feature] Add an Indian Phone Number calculator .

Description
This app takes a phone number as input and validates whether it is a of Indian phone number format, including those starting with +91, 91, 0, and standard 10-digit numbers.
Built using HTML,CSS and JavaScript .
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

@Rakesh9100 @jessicachawla kindly consider this issue .

@Rakesh9100 pls see if this is needed


Adding Softera.Bankfeed to Connectivity Apps

Softera.Bankfeed added

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 10575.


Remove not needed anymore BeansWeakCache substitution. Closes #3226

Fix for #3226
Tested locally on a couple of Camel Quarkus projects:
Quarkus 2.4.1.Final
ubi-quarkus-native-image:21.2-java11
ubi-quarkus-native-image:21.3-java17
ubi-quarkus-native-image:21.3-java11

There is some special build step that I forget to do?

It's werid that qute.json  got some changes. I'll take a look.

@vladimirfx what are the steps you used to verify locally ? I think it should run all intgration tests in native mode.

@vladimirfx I think you need to raise a PR agaist to main branch but not 2.4.x branch.

@vladimirfx what are the steps you used to verify locally ? I think it should run all intgration tests in native mode.

I run full non native build locally and test resulting artifacts on own projects.

Yeah, it should be against main

Rebased on main.

I've checked locally that native tests succeed against few select project. But better wait for a full CI build to approve.


[NO MRG] R noarch packages

For pure R packages, we can make the package noarch: generic. There'll be a warning however that the package was compiled for r-3.4.1 if it's imported in r-3.3.2.
I tested building this package in linux and importing in windows and it works. (conda install r-regsitry -c isuruf if you want to try)
cc @conda-forge/core, @bgruening, @johanneskoester, @jdblischak, @daler, @mingwandroid

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

noarch packages can't have selectors. If the selectors are necessary, please remove noarch: generic.

If this works, it would be awesome! Thanks @isuruf!

@conda-forge-admin, please lint

@conda-forge-admin, please lint

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@isuruf This is really great! I was able to install and use the r-registry package from your channel with both R 3.3.2 and R 3.4.1 on Linux, macOS, and Windows. I ran the following in R to test:
library("registry")
r <- registry()
r

I received no warnings or errors.

It works for me as well. I must admit I'm not a fan to pollute the recipe and the directory that much with the postlink magic but the advantages outweighing my concerns!

There are several other ways though.

Teach conda about a new noarch: r
Set R_LIBS_USER in activate.sh
Edit Rprofile file

Or creating a file in R_HOME/etc/Renviron.site

We should not accept post links scripts here. We should unify the windows layout with the others instead.

Post linking everything nullifies the advantages of hardlinks. Doing this for the odd packages when necessary is ok but doing it wholesale is not.

@mingwandroid, what do you think about the 4 alternatives I mentioned above? none of them require post link scripts

Teach conda about a new noarch: r

xref: https://github.com/conda/conda/issues/5974

Is functionally no different from a post link.
You are overriding the users libs folder here.
3 and 4 are just 2 again.

Why would you want to do anything other than making the layout the same on Windows as the others? Then discussion of hacks doesn't need to happen.

Why would you want to do anything other than making the layout the same on Windows as the others? Then discussion of hacks doesn't need to happen.

Backwards compatibility for R 3.3.2 and R 3.4.1

There's no such backwards compatibility not concerns about them.
Each r package pins to the exact r-base version and it needs to stay this way.

Each r package pins to the exact r-base version and it needs to stay this way.

That's not what this PR intends to do. noarch: python doesn't pin to the python version either.

You are attempting compatibility across platforms here for packages that do not need compilation. There is no compatibility across R versions.

What I mean is if we change the layout in R 3.5, the noarch generic packages won't work in 3.4 and 3.3

The R packages that do not need compilation contain bytecode specific to that version of R. You cannot expect bytecode for R 3.5 to run on 3.4 or from 3.4 to run on 3.3. It does not work.

Does bytecode for R 3.3 run on 3.4 and 3.5? Or is that incompatible as well?

The R people evolve the language and at the same time the bytecode format. They do not guarantee any compatibility between different minor versions. You'll probably get away with patch versions but I'm not sure. I do know that they themselves do not risk anything here and do full build-outs at each patch version for the systems they provide binaries for (Windows for ever and macOS since 3.4).
If you really want full noarch: r so that it does the bytecode compilation at install time then that might be workable but IMHO, having cross-platform noarch is a good enough change and you shouldn't try to over-reach for now.
When I last checked 1/2 the R packages needed compilation and 1/2 did not.


Raspberry 3B+ with purethermal 2 failed

I am a novice. And a lepton 3.5 installed on purethermal 2, my Raspberry pi 3B+ installed Raspbian Buster.
I tried to run this program: uvc-radiometry.py
I got this error message :
$ sudo ./uvc-radiometry.py
unsupported descriptor subtype VS_COLORFORMAT
unsupported descriptor subtype VS_COLORFORMAT
unsupported descriptor subtype VS_COLORFORMAT
unsupported descriptor subtype VS_COLORFORMAT
unsupported descriptor subtype VS_COLORFORMAT
device opened!
Version gpp: 3.3.26 dsp: 3.3.26
FLIR part #: 500-0771-01
FLIR serial #: '{"(\x00\x00\x00\x00\x00'
format: UYVY
frame 160x120 @ 9fps
format: Y16
frame 160x120 @ 9fps
frame 160x122 @ 9fps
format: Y8
frame 160x120 @ 9fps
format: RGBP
frame 160x120 @ 9fps
format: }�6�
frame 160x120 @ 9fps
uvc_start_streaming failed: -2
please help me.

Does this happen with the firmware on the development branch?

This is not a purethermal firmware issue, it looks like you may not using the groupgets fork of libuvc as per the instructions in the capture examples.
If you want to use the upstream libuvc, you can give the branch master+libuvc_upstream.


openstack loadbalancer cmd  is not working anymore

Hi all,
for any reason the following command is not working anymore:

openstack --os-cloud  <cloud> loadbalancer list

I get the following error:
public endpoint for load-balancer service in eu-ch2 region not found
Traceback (most recent call last):
  File "/home/linux/ansible-env/lib/python3.8/site-packages/cliff/app.py", line 410, in run_subcommand
    result = cmd.run(parsed_args)
  File "/home/linux/ansible-env/lib/python3.8/site-packages/cliff/display.py", line 115, in run
    column_names, data = self.take_action(parsed_args)
  File "/home/linux/ansible-env/lib/python3.8/site-packages/octaviaclient/osc/v2/load_balancer.py", line 347, in take_action
    attrs = v2_utils.get_loadbalancer_attrs(self.app.client_manager,
  File "/home/linux/ansible-env/lib/python3.8/site-packages/octaviaclient/osc/v2/utils.py", line 226, in get_loadbalancer_attrs
    client_manager.load_balancer.load_balancer_list
  File "/home/linux/ansible-env/lib/python3.8/site-packages/osc_lib/clientmanager.py", line 45, in __get__
    self._handle = self.factory(instance)
  File "/home/linux/ansible-env/lib/python3.8/site-packages/octaviaclient/osc/plugin.py", line 32, in make_client
    endpoint = instance.get_endpoint_for_service_type(
  File "/home/linux/ansible-env/lib/python3.8/site-packages/osc_lib/clientmanager.py", line 246, in get_endpoint_for_service_type
    endpoint = self.auth_ref.service_catalog.url_for(
  File "/home/linux/ansible-env/lib/python3.8/site-packages/keystoneauth1/access/service_catalog.py", line 392, in url_for
    return self.endpoint_data_for(service_type=service_type,
  File "/home/linux/ansible-env/lib/python3.8/site-packages/keystoneauth1/access/service_catalog.py", line 459, in endpoint_data_for
    raise exceptions.EndpointNotFound(msg)
keystoneauth1.exceptions.catalog.EndpointNotFound: public endpoint for load-balancer service in eu-ch2 region not found
clean_up ListLoadBalancer: public endpoint for load-balancer service in eu-ch2 region not found
END return value: 1

hi @hadoopch! the problem is that eu-ch2 has only elbv3, but now elb client is using elbv2, we need to implement another client for v3, i let you know when it is ready
best regards,
Polina


Add categories for the push registration

Make the showcase register the devices in 2 UnifiedPush Server categories ("ionic" and "showcase")

@danielpassos How this works without release? Is master broken now?

@wtrocki It should not broke anything. I just added a category name in the registration process. The JS SDK lib published already support it for ages => https://github.com/aerogear/aerogear-js-sdk/blob/master/packages/push/src/PushRegistration.ts#L39

Perfect!


Stale bot spam

We're developing a small website theme as a hobby in our limited free time, not the Chromium source code here. The stale bot spamming and closing issues is counterproductive and quite annoying.  My pull request has also been closed by this robot. Can we please disable it for this repo?
I am still actively working on improvements to this theme in my repo, more or less as a hard fork. I haven't updated my pull request in a while as I haven't had time to split the branches out again after merging them. Most of my changes are cumulative, anyway, but that style of development doesn't appear to suit contribution guidelines for this repo.

@Darthagnon Yep. I also realize this problem. I've already deleted this stable bot in this repo. Thanks for reminding me to handle this problem.

Most of my changes are cumulative, anyway, but that style of development doesn't appear to suit contribution guidelines for this repo.

About the PR https://github.com/g1eny0ung/hugo-theme-dream/pull/247, and this one, to be honest, there's something too "cumulative" about the changes here. There are so many changes here that I'm really having a hard time dealing with up to 200+ changes. 🤯
I noticed your comments on https://github.com/g1eny0ung/hugo-theme-dream/pull/247#issuecomment-1152811351, it's making it difficult for me. The issue at hand is that if I merge this PR, I may miss out on several critical details of the master branch down the line. It seems like there wasn't a comprehensive summary of the specifics provided in this PR. In my experience with open source, this inevitably creates more problems later on, because if something goes wrong somewhere, I need to recall it from the very beginning of the context (yes, this PR), which will take more time.
I want to make it clear that I am not blaming or complaining, but rather, I am willing to embrace the change and move forward. Shall we begin with the modifications in the docs folder? I will extract the alterations, review them, and once they are merged, then merge the master branch into this pull request. This will separate that part of the changes from the PR.

Shall we begin with the modifications in the docs folder?

Started with #279.


Update the codegen to say returning Promise.

Related to googleapis/gax-nodejs#39

Current coverage is 81.04% (diff: 100%)

Merging #592 into master will increase coverage by 0.14%

@@             master       #592   diff @@
==========================================
  Files           258        266     +8
  Lines          9736      10011   +275
  Methods           0          0
  Messages          0          0
  Branches       1282       1296    +14
==========================================
+ Hits           7876       8113   +237
- Misses         1527       1564    +37
- Partials        333        334     +1

Powered by Codecov. Last update 6ab296b...fb3ffc5

LGTM