Error: Expected to be a pending migration but it wasn't

I'm getting this error Error: Expected database\migrations\2021.05.30T14.14.38.create_users_table.ts to be a pending migration but it wasn't! You should investigate this. Use --skip-verify to bypass this error. whenever I use create. I'm using the https://github.com/sequelize/umzug/tree/master/examples/4.sequelize-seeders as reference.
What can it be? It's creating the migration table on my database tho, but it's empty.

This usually means you have a glob pattern pointing at the wrong directory. If you could share the options you're passing to the constructor it might be possible to see what's wrong. Or, even better, a git repo/branch which reproduces the error.

import { Umzug, SequelizeStorage } from 'umzug'
import { Sequelize } from 'sequelize'

import databaseConfig from '../database/config'

const sequelize = new Sequelize(databaseConfig)

const context = {
  sequelize
}

export const migrator = new Umzug({
  migrations: {
    glob: ['database/migrations/*.ts', { cwd: __dirname }]
  },
  context,
  storage: new SequelizeStorage({
    sequelize,
    modelName: 'migrations'
  }),
  logger: console
})

export const seeder = new Umzug({
  migrations: {
    glob: ['database/seeders/*.ts', { cwd: __dirname }]
  },
  context,
  storage: new SequelizeStorage({
    sequelize,
    modelName: 'seeders'
  }),
  logger: console
})

export type Migration = typeof migrator._types.migration
export type Seeder = typeof seeder._types.migration

The thing is that when using create it does create the migration.

cc @mmkal I created a repository with the problem, the usage is on the readme: https://github.com/zefexdeveloper/umzug-problem

In that repo, you've set cwd: __dirname which means it's looking for files matching database/seeders/*.ts in the cli/ directory. If you get rid of the cwd parameter or use path.join(__dirname, '..') to be explicit it should work.

It worked, thank you very much. I thought as I was running the command on the root dir it would start from there.
One last question: why do I have to specify --folder when running create as the directory is already specified in the config? Thank you again.

Since all you do is specify a glob, there isn't necessarily a single "folder" umzug can know to put the first migration in. Once you've created one, though, it will assume you want to create the next in the same folder. So it's ok to pass --folder in via CLI the first time, you won't have to for the second.
No, using ts-node directly is pretty much equivalent to using ts-node/register. The only downside is you can't just look at the code to see how it works - it needs to be run with a special script. As long as that's documented in your project that's fine though.


deps: bump RTE to v0.7.3, PFP to v0.0.3

Trivial dep bump.
Signed-off-by: Francesco Romani<EMAIL_ADDRESS>

/retest


SASS Inject Reload Issue (v0.10.0) when using .scripts()

Mix Version: 0.10.0
Node Version: 6.10.0
NPM Version: 3.10.10
OS: Mac OS Sierra
Description
Hi! I follow steps 1 thru 4 to confirm this is an issue for the latest version.
If using .scripts([]) when you compile your SASS it triggers a compilation of your JS as well which will initiate a refresh regardless of the BrowserSync setting.
If I remove .scripts() from my mix file, then the new CSS is injected without issue and no reload occurs.
I checked out #413 and #430 - and am up to date with these, but in my scenario it reloads anyway.
I'm not sure if there is a way to ignore the app.js being recompiled when a SASS change triggers it and yet still reload if the JS was changed directly.
Basically the best way would be like Laravel 5.3/Gulp whereby SASS/JS compiling occurs in a  decoupled fashion and therefore SASS changed can be injected without reload and without compiling the JS.
Steps To Reproduce:
Install a regular Laravel 5.4 project, have mix.sass and mix.scripts present and use mix.browserSync()
Unfortunately I cannot provide access to the repo, but I have included a stripped down version of the webpack.mix.js file:
const { mix } = require('laravel-mix');

mix.browserSync({
    proxy: 'example-app.dev',
    notify: false,
    ghostMode: {
        clicks: false,
        forms: false,
        scroll: false,
    }
});

mix.sass('resources/assets/sass/app.scss', 'public/css');

mix.scripts([
    'resources/assets/js/some-jquery-plugin.js',
    'resources/assets/js/another-jquery-plugin.js',
    'resources/assets/js/global.js'
], 'public/js/app.js');

mix.copy(
    'resources/assets/example.svg',
    'public/js/ui/example.svg'
);

Hi,
Have you found a solution for this?
I have kinda the same problem, im just using the standard .js and .sass in my webpack.mix file, but when i change something in my js, it trigger compilation of my css too when running "npm run watch".
Perhaps it could be related, even though yours is the other way around.

@AndreasHerss I ended up going back to Gulp unfortunately for this particular project.

Your Laravel-Mix version is 0.10.0 at time of posting. Perhaps you want to create a new branch and test the latest version, which is 0.11.4? I am not sure what exactly are fixed, but I think the SASS injection thing might be fixed.


Negative width when components only contain spaces

It seems when components only contain spaces, their width is the amount of spaces but negative.
Which results in the CenterAPI.center never exiting its if loop.
CenterAPI.center(Component.text(" "));
https://paste.gg/p/anonymous/ae2ec3c831574270a5aeb7601399cf87
Edit:
Using 1.1.0-SNAPSHOT from OSSRH

It seems using CenterAPI.center(Component.text("1111"), Component.text(" ")); also triggers the issue, however replacing the second argument with Component.text("1") does not result in any issues, and the component is seemingly centered fine.

Solved In #8


Gyroscope and Accelerometer Data Not Working

I am running the demo and the API and the Wii Mote RVL-036 on Windows 10 and the Gyroscope and accelerometer data is not being processed. The Wii Motion Plus data just sits at 0 and the accelerometer can be calibrated once, and then doesn't change after that. Any thoughts? I noticed that people were having similar issues based on comments on your YouTube video.

@Flafla2 Update: The API is working as expected with the original Wiimote, but not the RVL-CNT-01-TR. Do you have a solution for this?

having same problem


Post Message action freezes on execution, but continues successfully after killing running proces/microflow on server node

The java action that posts a message to a channel on Slack freezes up when it is executed from a microflow on our test node in the Mendix cloud.
But when I go to the node metrics of the test node and kill the running microflow from the Running Now tab page, the message gets posted to Slack successfully.
Here is a detailed analysis of what happens, as far as we can see it.
When the microflow starts and the java action is executed, we see the following messages appear in the console log:
Apr 26 12:57:46.009 - INFO - SlackConnector: postMessage: development, Test with Nick present
Apr 26 12:57:46.030 - INFO - SlackConnector: Using session: com.ullink.slack.simpleslackapi.impl.SlackWebSocketSessionImpl@1530ee5a, is connected: false
Apr 26 12:57:46.049 - INFO - SlackConnector: Reconnecting slack session
We looked where that 'Reconnecting' log message is posted. That happens in the getSession() method, which I posted below for convenience. We have the feeling that the java method freezes at the second 'session.connect()' statement. I placed a comment behind the call.

 We see the following info messages posted to the log:
Apr 26 13:09:27.662 - INFO - SlackConnector: Channel: development
Apr 26 13:09:28.569 - INFO - SlackConnector: done postingMessage
Any help is greatly appreciated!
Best regards,
Theo Tol

I suspect this is caused by a deadlock due to incorrect concurrency handling. I've rewritten the connector to improve concurrency.  Can you test if this solves your issues? Published as release 1.3.1 in the appstore.

Hello Andrej,
I tested the changes, but unfortunately posting the message still freezes up the microflow on the server. When I go to the node metrics of the test node and kill the running microflow from the Running Now tab page, the message is not posted, as was the case with the previous version.
One thing I have to mention (and what I should have mentioned earlier) is that I am working in Mendix 6.10.2, so I have copied all the .java files from the GitHub project to my own project manually because the new version is developed with Mendix 7.0.2. I hope that is not causing this issue I am having.
If there is anything I can do to help fix this issue, or if I can deliver more information, please let me know.
Best regards,
Theo Tol


ARTEMIS-643 wrong paths in restricted-security-client.policy

user.dir points to current working directory from which the maven command
was invoked. If the command is not invoked from project root directory,
the generated paths are wrong what causes failures of some tests.
(cherry picked from commit f4a0763baf6678ad16226943e9cde1d7d923691b)

@dudaerich Could you add the ENTMQ to the commit message please.


Errors: 250003 Invalid Access License number

Thank you for keeping up with this API!
I'm trying to use the UPS side but I'm getting a
Errors: 250003 Invalid Access License number
I double checked and it works in the UPS API C# examples.
I have the proper access key, username and password.

Is it for production or test UPS environment?


Add ability to format as accounting values (in fmt_*() methods where it makes sense)

We currently don't have the ability to format numeric values as accounting-type values (i.e., handling of negative values different than using the minus sign). This should ideally work inside:

fmt_number()
fmt_integer()
fmt_currency()
fmt_percent()

As for how it would look, this is a good start:

Great Idea! 😃
Not sure if this is just to show the format but the "percent" value looks wrong 😄 .
Most programms (like excel, powerbi, ...) multiply by 100 and not divide by 10 😮 .
For example you perform a calculation resulting in 0.15 and formatted as percent yields 15% (1 = 100%)

I rescaled the number before applying the percent formatting (to put it in a better range).


Renamed Kyiv and updated version

Codecov Report
Patch and project coverage have no change.

Comparison is base (016aefa) 83.55% compared to head (35c10f9) 83.55%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #479   +/-   ##
=======================================
  Coverage   83.55%   83.55%
=======================================
  Files          70       70
  Lines        4664     4664
  Branches      600      600
=======================================
  Hits         3897     3897
  Misses        760      760
  Partials        7        7

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add versioning support for git archives

Given that we are using hatch-vcs (in both the project and the template), the following two files should be added in to support versioning from VCS for a user installing the project through a git archive -

.git_archival.txt (example (can be copied entirely))
.gitattributes (example (can be copied entirely))

@Saransh-cpp does that apply only for hatch-vcs or also for setuptools config?

Just saw this, for all vcs configs, independent of the backend.


workflows: Add an internal test action

workflows: Add a smoke test that uses a sigstore client
This makes sure that the repository we have published to Pages works as a Sigstore Staging root-signing repository:

installs sigstore-python
modifies sources to use our TUF URL (this is not yet exposed in sigstore-python CLI)
runs sign & verify: sigstore-python will update metadata from our published TUF repository

This does not actually check that the client has received the expected metadata versions but the tuf-on-ci test has already tested that the published repository versions match expected versions.
Fixes #32

Keeping this a draft for now: I'm still considering making this a reusable workflow instead -- this mostly a trade-off between workflow maintainability and the ease of automated issue handling

I will change this to a reusable workflow:

this internal action approach requires a uses: action/checkout in the test workflow (because otherwise the action isn't available) and that adds complexity to the test workflow and creates strange situations since the checkout kind of  should be from the publish branch but the action may have change in main...
there might be a way to make this reusable workflow part of tuf-on-ci template somehow but I'm not going to try it yet: let's see how it works here and then think about unpstreaming

Marked ready for review:

The custom test is now a reusable workflow: this minimizes the changes needed in  test.yml
We maybe could later upstream the test.yml changes (so the custom test workflow is in the template, just as a no-op workflow)

Testing this before merging is non-trivial but I've separately tested

the reusable workflow in general and running it from test.yml
the sigstore-python code

It should be close to what we want


Bug: Reconnecting MQTT not working properly

Please make sure that the issue you're planning to report is not already registered :)

Describe the bug
Ever when the device wakes up, MQTT only reconnects after the grace period of 2 mins.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
MQTT should reconnect right away
Screenshots
If applicable, add screenshots to help explain your problem.
Misc info (please complete the following information):

Windows build (ideally screenshot/info of winver.exe output):
Windows' UI language:
HASS.Agent version: 2.0.1

Please check what's applicable (multiple answers possible):

[x] Installed via installer
[ ] Installed manually
[x] Problem occurs in HASS.Agent
[ ] Problem occurs in Satellite Service

Additional context
Add any other context about the problem here.
Logs
2024-01-07 19:40:12.128 +01:00 [INF] [HASS_API] Server recovered from failed state
2024-01-07 19:42:03.875 +01:00 [WRN] [MQTT] Disconnected: UnspecifiedError
2024-01-07 19:42:03.899 +01:00 [ERR] [MQTT] Error while connecting: Error while connecting with host 'ha:1883'.
2024-01-07 19:42:09.012 +01:00 [INF] [MQTT] Connected

Hm, from what I see the reconnection happens immediately after the MQTT client "notices" the issue. The thing that takes 2 minutes is for the client to realise there is an issue.
We're using the MQTT .NET managed client (it on itself is taking care of reconnection) but I'll see if this behaviour can be tweaked or if something else is the culprit.

No, it takes exactly the grace period. When I had it set to 60 minutes, it would only reconnect after 60 minutes. I then lowered it to 2 mins but would expect the client to reconnect within seconds of the PC waking up again and also not posting that mqtt failed notification.
There's some issue apparently in the managed client's reconnect logic. It could be that my PC is using WiFi and that takes a moment to connect when the PC wakes up.

I think I have the fix designed in my head but just to confirm it, are there any "[SYSTEMSTATE]" logs near the logs that you've posted aka could you please post a little more logs :)?

2024-02-05 11:02:42.686 +01:00 [INF] [SYSTEMSTATE] Session halting: system suspending
2024-02-05 11:42:29.057 +01:00 [WRN] [MQTT] Disconnected: UnspecifiedError
2024-02-05 11:42:29.332 +01:00 [ERR] [MQTT] Error while connecting: Error while connecting with host 'ha:1883'.
2024-02-05 11:42:31.618 +01:00 [INF] [HASS_API] Server recovered from failed state
2024-02-05 11:42:34.429 +01:00 [INF] [MQTT] Connected
2024-02-05 11:57:52.661 +01:00 [INF] [SYSTEMSTATE] Session halting: system suspending
2024-02-05 12:12:46.721 +01:00 [INF] [SYSTEMSTATE] Session resuming
2024-02-05 12:12:50.289 +01:00 [WRN] [MQTT] Disconnected: UnspecifiedError
2024-02-05 12:12:52.417 +01:00 [INF] [HASS_API] Server recovered from failed state
2024-02-05 12:14:47.349 +01:00 [ERR] [MQTT] Error while connecting: Error while connecting with host 'ha:1883'.
2024-02-05 12:14:52.446 +01:00 [INF] [MQTT] Connected

Sure, does that help?

Yup :D
Also something interesting I noticed that "session resuming" occurs only once.

I also noticed that. Sometimes it'll also immediately show the notification when the system is reactivated instead of after grace period and then MQTT will be in stopped state. It's really weird.
I'd expect it to just instantly reconnect when system is reactivated and network available and only show a notification if it was unable to properly reconnect within grace period.

In general it's "working as expected" - in quotes since by the current design when connection breaks, mqtt client is allowed the specified time to recover the connection.
Of course, it's not applicable if the system went to hibernation/sleep and the mqtt server has long forgotten about the client - there is very slim chance to recover such connection. I'll now know what piece of code is "causing this", now I need to figure out a clever solution.

I have a POC ready that could solve the issue but one question arose, does the HASS.Agent reliably detect system resuming from hibernation/sleep?
[INF] [SYSTEMSTATE] Session resuming

This log to be specific, in the previous excerpt from the logs that you've provided I can see two entries for the suspending but only one for the resuming - if this repeats I might need to change the fix logic a little bit.

Detection seems to be relatively reliable overall but could be a bit quicker
2024-02-17 08:37:19.033 +01:00 [WRN] [MQTT] Disconnected: UnspecifiedError
2024-02-17 08:37:19.759 +01:00 [ERR] [MQTT] Error while connecting: Error while connecting with host 'ha:1883'.
2024-02-17 08:37:23.748 +01:00 [INF] [HASS_API] Server recovered from failed state
2024-02-17 08:37:24.972 +01:00 [INF] [MQTT] Connected
2024-02-17 08:38:52.184 +01:00 [INF] [SYSTEMSTATE] Session resuming

Small update just to let you know I haven't forgotten about it :D
I have the fix ready but I'm having hard times reproducing your behaviour when testing, after waking my system it connects quite quickly.
Either way I'll give it a few more tests and include as part of 2.1.0-beta1 - we'll see if it helps your case.

And you do not get a connection failed notification when it reconnects?

Nope, reconnect in the logs and confirmed in the UI, no notifications at all.

This problem may also be affecting the Satellite service, you may have to port the fix over to the Satellite service too.
@amadeo-alex

@larena1 have you noticed any difference with https://github.com/hass-agent/HASS.Agent/releases/tag/2.1.0-beta1 ?

It's reconnecting straight away now but still posts the Windows notification, which it probably should not.
2024-04-08 12:00:31.170 +02:00 [INF] [MQTT] System resumed less than {gracePeriod} seconds ago, ignoring grace period on disconnection
2024-04-08 12:00:31.170 +02:00 [INF] [MQTT] System resumed less than {gracePeriod} seconds ago, ignoring grace period on disconnection
2024-04-08 12:00:31.202 +02:00 [WRN] [MQTT] Disconnected: UnspecifiedError
2024-04-08 12:00:34.180 +02:00 [INF] [HASS_API] Server recovered from failed state
2024-04-08 12:00:36.239 +02:00 [INF] [MQTT] Connected

It is of course expected that the connection needs to be reestablished when the system wakes but there's no point informing the user of if when the reconnect succeeds within the grace period. That's basically what the grace period was meant for, right?

The grace perdiod is for the mqtt library to possibly restore connection - HASS.Agent is using managed mqtt client that internally takes care of reconnection.
With system being in hibernation/sleep for X and then awakening, in most cases there is no chance of connection being recovered.

HASS.Agent will wait a grace period before notifying you of disconnects from MQTT or HA's API.
https://github.com/hass-agent/HASS.Agent/blob/e08c93766c5ff482c0a70adf2a31564408c65b2f/src/HASS.Agent/HASS.Agent/Resources/Localization/Languages.en.resx#L153
It clearly says it'll only notify after grace period passed why imo makes sense as I don't need to be notified of a regular, expected reconnect. Can you restore that behavior?

Ok, will do that in the next cycle (most likely as part of 2.1.1 bugfix release) - https://github.com/hass-agent/HASS.Agent/issues/145


Cool package! Integration with Meshes.jl

This is a nice package! Have you thought about how you can integrate LightLattices with something like Meshes.jl or GeometryBasics.jl for easy visualization and to benefit from their algorithms?

Thank you!
To be honest, I haven't thought about it.
As far as I understand, the purpose of meshes is the discretization of continuous manifolds. Here, the general interest is to describe a collection of physical objects arranged in lattice. (My specific interest is nuclear spins in solids, but one can consider other physical objects).
On the other hand, one can consider lattices as a subset of meshes.
So, could you be more specific what kind of integration you have in mind?
For example, do you know some particular algorithms from Meshes.jl GeometryBasics.jl which are good to apply to lattices?

Hey! Sorry I missed your reply. I was thinking of a unified API to iterate over the elements of the lattice and the nodes of those elements where the lattice is a lattice of meshes.

I think the iteration over nodes is solved by defining eachindex dispatch for appropriate types. In this regards, we don't need a special interface. We can reuse the one for AbstractArray-s.
By the way, this guys are discussing on slack the general interface to setup a system of atoms (particles) for molecular simulations. If you are, by chance, interested in this stuff, you may consider joining the slack channel.


Correct spelling error in the "TextBox or RichTextBox?" paragraph. #1064

Summary
Change then to than in the TextBox or RichTextBox? section.
Fixes #1064

Awesome, thanks for this fix!

Thanks for the help on the process!


Remove property from seekable method of FileIO

This fix is a follow up to address the issue in #27276 where seekable with property causes the following error with Python 3.7.:
  File "/usr/lib/python3.7/_collections_abc.py", line 744, in __iter__
    yield (key, self._mapping[key])
  File "/usr/local/lib/python3.7/dist-packages/numpy/lib/npyio.py", line 251, in __getitem__
    bytes = self.zip.open(key)
  File "/usr/lib/python3.7/zipfile.py", line 1540, in open
    return ZipExtFile(zef_file, mode, zinfo, zd, True)
  File "/usr/lib/python3.7/zipfile.py", line 821, in __init__
    if fileobj.seekable():
TypeError: 'bool' object is not callable

This fix removed property annotation of the seekable methods.
This fix also adds a test case, though the test case is only exposed in python 3.7+.
This fix fixes #27276.
Signed-off-by: Yong Tang<EMAIL_ADDRESS>

Thanks @dynamicwebpaige 👍 , the sanity ci test was failing because of the pylint format issue. Have fixed the sanity ci test and updated.

@mihaimaruseac Thanks for the review. There were ci failures related to api compatible. I have updated the api goldens file so tests should all pass now.

This is not a backwards-compatible change.
I think we need to make this change in 2.0 only. This will require having two classes, a V1 with a property and a V2 with a method, and these should have separate tf_export decorator.

Nevermind, let's try to merge this as-is.

We took a look and found very few to no usages of this, so it's fine to have a backwards-breaking bugfix.


List out of range

Sometimes the script tries to index an item that is not in the range of the list given by wmctrl. Cause not found yet, happens rarely. Restart of x-server solves the problem

Traceback (most recent call last):
  File "/usr/bin/moro", line 107, in <module>
    appList.append((response[cList[0]+1:cList[1]].lower(), appId))
IndexError: list index out of range


Support for AAD as external IdP for Workload Identity Federation

Hello, Workload Identity Federtation looks like a great tool for avoiding handing out and rotating client secrets for certain use-cases.
We would really like to use it for MSI-based authentication between AAD-tenants and were expecting to be able to do so by defining a credential as an external OIDC IdP.
Trying to setup this workflow causes the following error during the token exchange: AADSTS700222: AAD-issued tokens may not be used for federated identity flows.
While writing this issue I noticed https://login.microsoftonline.com/error?code=700222 which seems to indicate that this is a temporary limitation: The federated identity credentials flow does not support tokens issued by Azure AD at this time.
Could you document this limitation and provide more information on when we can expect to see this functionality?
Thanks.

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

ID: cf644d11-51ae-8ef0-34c8-d471a47d5cf1
Version Independent ID: d5e3190b-f287-6542-fd2b-f8fe9066c23e
Content: Workload identity federation - Microsoft identity platform
Content Source: articles/active-directory/develop/workload-identity-federation.md
Service: active-directory
Sub-service: develop
GitHub Login: @rwike77
Microsoft Alias: ryanwi

@sopelt
Thanks for your feedback! We will investigate and update as appropriate.

@sopelt
Thank you for pointing this out! I've created a PR to update the documentation and it's currently waiting for the author to review and sign off.
Unfortunately, we don't provide product release updates through our GitHub channels. For this, I'd recommend referring to our Azure Updates or Microsoft 365 Roadmap pages for this info.
I will now close out this issue. Please allow some time for the author to review and the changes to reflect.
Thank you for your time and patience!

If anyone wants to "roll their own IdP" I wrote up a series of posts on how to create the necessary keys & config to allow you to login with a federated credential: https://finarne.wordpress.com/2024/07/25/acquire-an-entra-id-token-using-federated-credentials-part-1-oidc-discovery-documents/


Text Named entity recognition  Special Word

Hi , In Named entity recognition, the text data has an&sign, and the page will report an error, as shown in the figure. The label studio version ^ 1.0.1 used in the project is installed through npm. How to solve the problem of special characters? What other special characters also report errors like this.

Hi,
please share your labeling config and data sample that can be used to reproduce this error.

data：Barnes & Noble携手联想推出新款10.1英寸Nook平板电脑

Labeling config?

Hi, without label config, only this data cannot be displayed, and then the page reports an error.


Add with_children: bool to delete_all(), to allow calling delete_all on an is_root=True base class, to delete any subclass rows as well.

A simple change: adds with_children: bool to delete_all(), which gets passed through to find_all().
When there is an inheritance tree, this allows deleting all documents in a collection using the base class in one simple operation.

Hi! Thank you for the pr. Please check the tests

Sorry, fixed

@TheBloke thank you for the PR. It looks good. Could you please add a test case for this?

Thank you @CAPITAINMARVEL ,
I'll add your tests to the branch this week.


Get_cli errors on the latest version of flutter

I am trying to run get_cli on the latest version of Flutter/dart however I seem to get the below error

below is my version of flutter

I found the same error, it happened because waitFor will be removed in a future version of Dart, is there another way? I tried adding the --enable_deprecated_wait_for flag when creating the project and it didn't work, have you found a way?

I experienced the same problem, this happened because waitFor will be removed in the next dart, I added the --enable_deprecated_wait_for flag but it still couldn't solve the problem

Upon further investigation the issue has more to do with dcli than this package.
you will have to downgrade flutter and dart  for now if you still need to use this package.
I believe once its fixed in dcli you should be able to use it again

found any workaround?   Facing the same issue

I found a workaround as get init is not working, we only need to manually initialize the project, and we can still add pages.
hope the issue will get resolved, but till then
we can still use
// use this option for Getx_pattern
get create page:home

and
// use this option for CLEAN (by Arktekko)
get create screen:home

add get dependency, create the home screen, then you can edit the main file based on your architecture
for Getx_pattern
import 'package:flutter/material.dart';

import 'package:get/get.dart';

import 'app/routes/app_pages.dart';

void main() {
  runApp(
    GetMaterialApp(
      initialRoute: AppPages.INITIAL,
      getPages: AppPages.routes,
    ),
  );
}

for CLEAN main.dart
import 'package:flutter/material.dart';

void main() {
  runApp(const MainApp());
}

class MainApp extends StatelessWidget {
  const MainApp({super.key});

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      home: Scaffold(
        body: Center(
          child: Text('Hello World!'),
        ),
      ),
    );
  }
}

config.dart
class Environments {
  static const String PRODUCTION = 'prod';
  static const String QAS = 'QAS';
  static const String DEV = 'dev';
  static const String LOCAL = 'local';
}

class ConfigEnvironments {
  static const String _currentEnvironments = Environments.LOCAL;
  static final List<Map<String, String>> _availableEnvironments = [
    {
      'env': Environments.LOCAL,
      'url': 'http://localhost:8080/api/',
    },
    {
      'env': Environments.DEV,
      'url': '',
    },
    {
      'env': Environments.QAS,
      'url': '',
    },
    {
      'env': Environments.PRODUCTION,
      'url': '',
    },
  ];

  static Map<String, String> getEnvironments() {
    return _availableEnvironments.firstWhere(
      (d) => d['env'] == _currentEnvironments,
    );
  }
}

dart pub global deactivate get_cli

dart pub global activate -s git https://github.com/knottx/get_cli.git --git-ref knottx

dart pub global deactivate get_cli

dart pub global activate -s git https://github.com/knottx/get_cli.git --git-ref knottx

Works perfectly - only dependancies required updating


Support any iterable object in keras.fit_generator

I signed it!

Thanks for the PR! This code path is actually being deprecated in 2.0 in favor of keras/engine/training_v2.py
If you want to add support for this, it should be there

@noamwies Could you please address the reviewer comments. Thanks!

Can one of the admins verify this patch?

It has been 14 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

I'm going to go ahead and close this PR, because it seems to have stalled. If you're still interested in pursing this (and responding to my comments), please feel free to reopen!


All of this is actually already fixed in this pr: https://github.com/music-assistant/server/pull/801 🙂 I just didn't bother fixing it in the non async version since it's double work and we are hopefully merging the async version before next beta releases. Sorry I should have mentioned that to you...

No worries. I will test that branch later today and give feedback 🙂

Depends on if the async version makes it in before next beta


Increment version for anomalydetector releases

Increment package version after release of Azure.AI.AnomalyDetector

API change check
API changes are not detected in this pull request.


fanficfare: 2.25.0 -> 2.26.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/fanficfare/versions.
These checks were done:

built on NixOS
/nix/store/8xysybhmjya5wx4rsykxk7d9f37g3qbk-fanficfare-2.26.0/bin/.fanficfare-wrapped passed the binary check.
/nix/store/8xysybhmjya5wx4rsykxk7d9f37g3qbk-fanficfare-2.26.0/bin/fanficfare passed the binary check.
2 of 2 passed binary check by having a zero exit code.
2 of 2 passed binary check by having the new version present in output.
found 2.26.0 with grep in /nix/store/8xysybhmjya5wx4rsykxk7d9f37g3qbk-fanficfare-2.26.0
directory tree listing: https://gist.github.com/8dac0cbfced5624b49e894cfb51f13be
du listing: https://gist.github.com/3710839076360d257f245cd976e974fa

meta.description for fanficfare is: '"FanFicFare is a tool for making eBooks from fanfiction web sites"'.
cc @lucas8 for testing.
Experimental: this build is cached with Cachix. To use the cache follow these experimental instructions:
One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout e9ce49860a003f8e091b3d8023a2431eeb2f44aa && nix-shell --pure -I nixpkgs=. -p fanficfare

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: fanficfare
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: fanficfare
Partial log (click to expand)
reading manifest file 'FanFicFare.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'FanFicFare.egg-info/SOURCES.txt'
running build_ext

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK
/nix/store/r8c6drkz3bdxnbmbsvlgac3nbpijxa4g-fanficfare-2.26.0


Hera V5 ideal usage

After discussing with @flaviuvadan and @samj1912 we hit on a very intuitive, Pythonic way of declaring Argo concepts[1]: if we make use of context managers, then we can mirror Argo's yaml spec and sprinkle on syntactic sugar where appropriate. This gives us 1 to 1 mapping between Hera and Argo, while allowing us to specialise certain use cases, such as a "simple workflow" use case which is the current standard Hera assumption of requiring a DAG made up of Tasks (which ties up Tasks<>Templates in a 1-1 mapping).
This issue is to collect ideal usage examples and discuss Hera V5 features -- V5 is currently in the hera/v5 working branch, with the main PR as #437 which will have PRs into, and a V5 alpha will be released from this branch.

Pythonic Steps Workflow Declaration vs YAML

coinflip.pycoinflip.yaml

def _flip_coin():
    import random

    result = "heads" if random.randint(0, 1) == 0 else "tails"
    print(result)

with Workflow(name="coinflip", generate_name=True) as w:
    # templates defined under a Workflow context manager could be added automatically but
    # "Explicit is better than implicit." Using dict access on the templates might be convenient
    # for referencing templates. Unsure of the name duplication used as a key if it is present
    # in the Template class itself
    w.templates["flip-coin"] = ScriptTemplate(
        name="flip-coin",
        source=_flip_coin,
    )
    w.templates["heads"] = ContainerTemplate(
        name="heads",
        image="alpine:3.6",
        command=["sh", "-c"],
        args=['echo "it was heads"'],
    )
    w.templates["tails"] = ContainerTemplate(
        name="tails",
        image="alpine:3.6",
        command=["sh", "-c"],
        args=['echo "it was tails"'],
    )
    with StepsTemplate(name="coinflip") as coinflip:
        coinflip.add_step(name="flip-coin", template=flip_coin)
        coinflip.add_step(
            name="heads", template=heads, when=f"{flip_coin.get_result()} == heads"
        )
        coinflip.add_step(
            name="tails", template=tails, when=f"{flip_coin.get_result()} == tails"
        )

    w.templates["coinflip"] = coinflip
    w.set_entrypoint(coinflip)
    # or equivalently
    # w.set_entrypoint(w.templates["coinflip"])

    w.annotations = {
        "workflows.argoproj.io/description": "This is an example of coin flip defined as a sequence of conditional steps."
    }

apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: coinflip-
  annotations:
    workflows.argoproj.io/description: |
      This is an example of coin flip defined as a sequence of conditional steps.
      You can also run it in Python: https://couler-proj.github.io/couler/examples/#coin-flip
spec:
  entrypoint: coinflip
  templates:
  - name: coinflip
    steps:
    - - name: flip-coin
        template: flip-coin
    - - name: heads
        template: heads
        when: "{{steps.flip-coin.outputs.result}} == heads"
      - name: tails
        template: tails
        when: "{{steps.flip-coin.outputs.result}} == tails"

  - name: flip-coin
    script:
      image: python:alpine3.6
      command: [python]
      source: |
        import random
        result = "heads" if random.randint(0,1) == 0 else "tails"
        print(result)
  - name: heads
    container:
      image: alpine:3.6
      command: [sh, -c]
      args: ["echo \"it was heads\""]

  - name: tails
    container:
      image: alpine:3.6
      command: [sh, -c]
      args: ["echo \"it was tails\""]

Here we can see the direct 1-1 mapping and the yaml shown from the Argo example should be exactly what we get from Hera when calling w.to_yaml(). It also opens the door for the coinflip-recursive.yaml example as we are no longer forced to use a DAG which prevent cyclic relationships.
Pythonic DAG Workflow Declaration vs YAML

dag_coinflip.pydag-coinflip.yaml

def _flip_coin():
    import random

    result = "heads" if random.randint(0, 1) == 0 else "tails"
    print(result)

with Workflow(name="coinflip", generate_name=True) as w:
    w.templates["flip-coin"] = ScriptTemplate(
        name="flip-coin",
        source=_flip_coin,
    )
    w.templates["heads"] = ContainerTemplate(
        name="heads",
        image="alpine:3.6",
        command=["sh", "-c"],
        args=['echo "it was heads"'],
    )
    w.templates["tails"] = ContainerTemplate(
        name="tails",
        image="alpine:3.6",
        command=["sh", "-c"],
        args=['echo "it was tails"'],
    )
    with StepsTemplate(name="coinflip") as coinflip:
        coinflip.add_step(name="flip-coin", template=flip_coin)
        coinflip.add_step(
            name="heads", template=heads, when=f"{flip_coin.get_result()} == heads"
        )
        coinflip.add_step(
            name="tails", template=tails, when=f"{flip_coin.get_result()} == tails"
        )

    w.templates["coinflip"] = coinflip

    with DAG(name="diamond") as diamond:
        a = Task(name="A", template=coinflip)
        b = Task(name="B", template=coinflip)
        c = Task(name="C", template=coinflip)
        d = Task(name="D", template=coinflip)

        a >> [b, c] >> d  # rrshift usage required to be under a DAG context manager

    w.templates["diamond"] = diamond

    w.set_entrypoint(diamond)
    w.annotations = {
        "workflows.argoproj.io/description": "This is an example of coin flip defined as a DAG."
    }

apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: dag-diamond-coinflip-
  annotations:
    workflows.argoproj.io/description: |
      This is an example of coin flip defined as a DAG.
      You can also run it in Python: https://couler-proj.github.io/couler/examples/#dag
spec:
  entrypoint: diamond
  templates:
  - name: diamond
    dag:
      tasks:
      - name: A
        template: coinflip
      - name: B
        depends: "A"
        template: coinflip
      - name: C
        depends: "A"
        template: coinflip
      - name: D
        depends: "B && C"
        template: coinflip

  - name: coinflip
    steps:
    - - name: flip-coin
        template: flip-coin
    - - name: heads
        template: heads
        when: "{{steps.flip-coin.outputs.result}} == heads"
      - name: tails
        template: coinflip
        when: "{{steps.flip-coin.outputs.result}} == tails"

  - name: flip-coin
    script:
      image: python:alpine3.6
      command: [python]
      source: |
        import random
        result = "heads" if random.randint(0,1) == 0 else "tails"
        print(result)
  - name: heads
    container:
      image: alpine:3.6
      command: [sh, -c]
      args: ["echo \"it was heads\""]

Note here that the Tasks defined under the DAG context would be different to the current Hera Task as it would expect a template parameter to be passed in, and would no longer be used for generating the top level templates now being stored in w.templates. Also, we may even want to consider explicitly adding the tasks to the DAG, and then defining the relationship between them, otherwise we are not sure what a declaration of a Task actually means. Like so:
    with DAG(name="diamond") as diamond:
        a = Task(name="A", template=coinflip)
        b = Task(name="B", template=coinflip)
        c = Task(name="C", template=coinflip)
        d = Task(name="D", template=coinflip)

        diamond.add_tasks([a, b, c, d])

        a >> [b, c] >> d  # we can then validate that you are referencing existing tasks in the dag

Pythonic "Simple Workflow" Declaration
If we still want to support the canonical "simple workflow" shown in the README, where developers don't care so much about the Argo details and just want to orchestrate some tasks, we can include a SimpleWorkflow class which assumes a DAG is used and allows rrshift DAG declaration of Tasks:
hello_hera.py
from hera import Task, SimpleWorkflow

def say(message: str):
    print(message)

with SimpleWorkflow("diamond") as w:
    a = Task('a', say, ['This is task A!'])
    b = Task('b', say, ['This is task B!'])
    c = Task('c', say, ['This is task C!'])
    d = Task('d', say, ['This is task D!'])

    a >> [b, c] >> d  # Implicit DAG declaration only allowed in a SimpleWorkflow context manager

Note that here we don't pass in a template to the Task (this might require a separate class to the proposed lightweight Task used in the examples above).

[1] we did this by trying to convert the coinflip Argo example which uses steps, which is a missing feature in Hera, using whatever syntax we thought made sense without worrying about implementation details

@elliotgunton an alternative syntax (if users don't want to be explicit about it)
w = Workflow(name="coinflip", generate_name=True)
w.add_script(
    name="flip-coin",
    source=_flip_coin,
)
w.add_container(
    name="heads",
    image="alpine:3.6",
    command=["sh", "-c"],
    args=['echo "it was heads"'],
)
w.add_container(
    name="tails",
    image="alpine:3.6",
    command=["sh", "-c"],
    args=['echo "it was tails"'],
)
with w.add_steps(name="coinflip") as s:
    s.add(name="flip-coin", template=flip_coin)
    s.add(
        name="heads", template=heads, when=f"{flip_coin.get_result()} == heads"
    )
    with s.parallel() as p:
	p.add(
          name="tails", template=tails, when=f"{flip_coin.get_result()} == tails"
      )
w.set_entrypoint(coinflip)
w.annotations = {
    "workflows.argoproj.io/description": "This is an example of coin flip defined as a sequence of conditional steps."
}
w.add_templates(**templates)

with Workflow(name="coinflip", generate_name=True) as w:
    Script(
        name="flip-coin",
        source=_flip_coin,
    )
    Container(
        name="heads",
        image="alpine:3.6",
        command=["sh", "-c"],
        args=['echo "it was heads"'],
    )
    Container(
        name="tails",
        image="alpine:3.6",
        command=["sh", "-c"],
        args=['echo "it was tails"'],
    )
    with Steps("coin-flip"):
        Step(name="flip-coin", template=flip_coin)
        Step(
            name="heads", template=heads, when=f"{flip_coin.get_result()} == heads"
        )
        with ParallelSteps:
			Step(
	            name="tails", template=tails, when=f"{flip_coin.get_result()} == tails"
	        )
w.set_entrypoint(coinflip)

w.annotations = {
	"workflows.argoproj.io/description": "This is an example of coin flip defined as a sequence of conditional steps."
}

I found out today that using depends in the DAGTask without a .Succeeded means it is equivalent to (task.Succeeded || task.Skipped || task.Daemoned) (see https://argoproj.github.io/argo-workflows/enhanced-depends-logic/#depends). Is it worth having V5 Hera Tasks default to using Succeeded when defining them with >>?
Task("a") >> Task("b")

to yaml
tasks:
- name: a
  template: a
- name: b
  template: b
  depends: a.Succeeded

Is the most common use case that it doesn't matter if "a" actually succeeded and only that "b" executes after "a"? I would think devs expect (as I did) that "b" only executes if "a" actually succeeded, whereas today I found the tasks after the one that was skipped (due to its when condition not being met) actually executed (I expected the DAG to stop).

I think this example is closest to the conversation we had. Here are the two main examples I have from my notes
with Workflow(..., entrypoint='coinflip') as w:
    flip_coin = Script('flip-coin', source=my_func, ...)
    heads = Container('heads', ...)
    tails = Container('tails', ...)

    with Steps('coinflip') as s:
        flip_coin(...)
        with ParallelStep() as s2:
            heads(...)
            tails(...)

def generator():
    X.do(...)
    print([1, 2, 3])

def process(a, b):
    print(a)

with Workflow(...) as w:
    g = Script('generator', source=generator)
    p = Script('fanner', source=process)
    # f(a=1, b=2)  # __call__  # {{.tasks.g.outputs.result}}
    with DAG():
        g() >> p.partial(b=1).map(g.output)

One thing I am wondering about in the context of transitioning to calls similar to g() and p.partial(...) is the effect it will have on testing and local execution. Will Hera's internals have to add an exception for tests + local environment that executes the Python function as is in the __call__? Does that significantly impact the testability of code that clients write?


Fix calculation bug with TextEdit::get_line_height()

When get_line_height() is not greater than 0, there is no visible text.
In these cases, the user is required to increase line_spacing and/or font_size to obtain a reasonably positive line_height.
There are many cases where the return value of get_line_height() is used for calculation, and in some cases the final result is allowed to be negative. So limit the return result of get_line_height() to not less than 0. Print an error if get_line_height() is 0 and used as the denominator.
Fix #69209.

Should make the minimum return 1, then we wouldn't need to worry about a divide by 0, or is there a use case for 0 line height?

Set line_spacing small enough to hide all text. Might not be necessary for the use cases of TextEdit. So not less than 1 is fine.

Missing the warning print, either with ERR_FAIL_COND_MSG or a check in _update_cache / _update_theme_item_cache so it doesn't go unnoticed.

Thanks!

Cherry-picked for 4.0.4.


[PE-D][Tester B] Edit command does not edit the selected person's details

Expected output: Editing a person's details e.g. edit 1 n/abc should (under normal user expectations) immediately update the details shown in the Overview panel.
Actual output:  Editing a person's details does not immediately update the details shown in the overview panel.
Steps to replicate:

Run executable jar file

Click on a candidate or run view INDEX with INDEX being a valid candidate's INDEX to see their details in the Overview panel

run edit INDEX n/NAME or edit any other parameters and using the same INDEX of the person selected

Additional details:
It will be updated upon clicking on the PersonListCard in the Applicants panel again.
Reasons for severity:
While there is a quick fix to the problem, a recruiter who left their laptop open for a while after editing a certain candidate's details may forget that the detail they are currently seeing is not the most up-to-date and proceed with some admin matters with the outdated details.
Suggestions: Make use of an Observer pattern to attach an observer to the PersonListPanel because the PersonListPanel automatically updates when you edit, just the Details of a person that does not get updated immediately. I am also not sure how prof coded PersonListPanel, but doing my suggestion works for my group (my grp also has a detail panel, so all my suggestions for the observer patterns comes from what we did to fix our bugs)

Labels: severity.Medium type.FunctionalityBug
original: PeterHW963/ped#11

Task

You should create a section under UG called 'Appendix: Planned Enhancements' as this is not a complete bug but an enhancement problem.
Write this issue inside 'Appendix: Planned Enhancements' section and how you will enhance the issue.
Write a note under 'edit', 'add' and 'delete' (May have more) command that says this behaviour. Change any command which should have changed the summary stats and person panel.


support configuring workspace deploymentStrategy in DWOC

What does this PR do?
This PR adds a new DWOC field config.workspace.deploymentStrategy which allows for specifying the workspace deployment strategy in the DWOC. The possible choices are Recreate (Default) and RollingUpdate.
What issues does this PR fix or reference?
https://github.com/devfile/devworkspace-operator/issues/1045 & https://github.com/eclipse/che/issues/21974
Is it tested? How?
Edit the DWOC and set the deploymentStrategy field to RollingUpdate. Also, ensure that the only accepted options for the deploymentStrategy field are Recreate and RollingUpdate.
kind: DevWorkspaceOperatorConfig
apiVersion: controller.devfile.io/v1alpha1
config:
  routing:
    clusterHostSuffix: <IP_ADDRESS>.nip.io
    defaultRoutingClass: basic
  workspace:
+    deploymentStrategy: RollingUpdate
    imagePullPolicy: Always

Deploy a workspace and modify a field that would change the deployment spec, for example, modify one of the container's CPU or Memory request.
To try this out, you could apply the following devworkspace:
cat <<EOF | kubectl apply -f -
kind: DevWorkspace
apiVersion: workspace.devfile.io/v1alpha2
metadata:
  name: plain-devworkspace
  namespace: devworkspace-controller
spec:
  started: true
  routingClass: 'basic'
  template:
    components:
      - name: web-terminal
        container:
          image: quay.io/wto/web-terminal-tooling:next
          memoryLimit: 5Gi
          memoryRequest: 256Mi
          mountSources: true
          command:
           - "tail"
           - "-f"
           - "/dev/null"
EOF

Next, watch the workspace status (as it will change when the rolling update occurs): kubectl get dw -n devworkspace-controller
Once the workspace is running, you could then increase the memoryRequest:  kubectl edit dwoc -n plain-devworkspace -n devworkspace-controller
apiVersion: workspace.devfile.io/v1alpha2
kind: DevWorkspace
(...)
spec:
  routingClass: basic
  started: true
  template:
    components:
    - container:
        command:
        - tail
        - -f
        - /dev/null
        image: quay.io/wto/web-terminal-tooling:next
        memoryLimit: 5Gi
+        memoryRequest: 1Gi
        mountSources: true
        sourceMapping: /projects
      name: web-terminal

Under the workspace's deployment (which could be checked on the OpenShift or Kubernetes dashboard) you should see a second pod get created and started before the old one is terminated.
You should also see the devworkspace status phase change from Running -> Starting -> Running:
$ kubectl get dw -n $NAMESPACE -w
NAME                 DEVWORKSPACE ID             PHASE      INFO
plain-devworkspace   workspacec3a273cb552340a5   Starting   Waiting for workspace deployment
plain-devworkspace   workspacec3a273cb552340a5   Running    Workspace is running
plain-devworkspace   workspacec3a273cb552340a5   Running    Workspace is running
plain-devworkspace   workspacec3a273cb552340a5   Running    Workspace is running
plain-devworkspace   workspacec3a273cb552340a5   Starting   Networking ready
plain-devworkspace   workspacec3a273cb552340a5   Starting   Waiting for workspace deployment
plain-devworkspace   workspacec3a273cb552340a5   Running    Workspace is running

Extra test case: removing the deploymentStrategy from the DWOC

Set the deploymentStrategy to RollingUpdate in the DWOC
Apply a workspace (kubectl apply -f ./samples/plain-devworkspace -n $NAMESPACE), ensure the deployments spec.strategy.type is RollingUpdate
Remove the deploymentStrategy field from the DWOC
Trigger a reconcile on the workspace (e.g. add an annotation)
Check the workspace deployment, the spec.strategy.type field should be Recreate

In other words, when the deploymentStrategy field is absent from the DWOC, the deployment strategy will be Recreate
PR Checklist

[ ] E2E tests pass (when PR is ready, comment /test v8-devworkspace-operator-e2e, v8-che-happy-path to trigger)

[ ] v8-devworkspace-operator-e2e: DevWorkspace e2e test
[ ] v8-che-happy-path: Happy path for verification integration with Che

@amisevsk another issue I've encountered is fixing the bug W.R.T the workspace status saying it's ready before the rolling update has completed. I don't think the deployment status struct fields have enough granularity to determine when the rolling update has finished (I tried something like deployment.Status.ReadyReplicas > 0 && deployment.Status.UnavailableReplicas == 0 and other variations).
I think I'll have to add some extra logic for checking the RollingUpdate deployment status specifically when it's used. It's a bit tricky to debug this properly since the RollingDeployment update progresses quickly :P

This has now been addressed in checkRollingUpdateDeploymentStatus()

/retest

/retest

/retest

/retest

/retest


Add an option for an extra initial and final step

In some cases the user might want to render the scene before any transition has occurred or after the agent reached the terminal state. This PR adds the options extra_initial and extra_final to do so in a similar fashion as it's done in BlinkPOMDPSimulator.jl.

I would fix but am flying


Documentation misses information

Describe the bug
The documentation misses the following information:

The Prerequisites which are given in github are not sufficient: “Install-Module –Name Azure –AllowClobber” is required as well and it should be mentioned that git commands from the command prompt are required.

The documentation refers to .net 2.1, and VS 2017, which needs to be updated, in particular the requirement to install .net core 2.2 and soon .net core 3.0.  Documentation of the instructions on the build/run process of the “new CLI” in Visual studio + the possible commands how to configure the setup is urgently needed.

Although there is the Industrial IoT repository with which the full microservices stack can be set up it would be good to have a step by step documentation and setup instruction for every service for multiple reasons

Naming of the services could be done individually
The understanding of which service is doing which task  would be much better for the user (e.g. I have no clue what each single resource which is deployed by the deployment script is doing). I have not yet looked into it, but I imagine it being very hard just learning this interplay by inspecting all services individually.
The „upgrade“ of existing infrastructures as the one we built up for our PoC would be feasible. At the first step we only started with an IoT Hub and an Edge gateway with the OPC publisher module, but we currently could not just extend this setup for the other modules/microservices. We would need to deploy a whole new compilation of resources.

The upgrade info. would be useful. For the .net info, I added a TODO in the doc. Agree we should put the specifics.
For publisher module, it would be super useful if we can describe how to setup the OPC UA simulation and hook up to try out.
E2E, with simulation environment and try out/troubleshoot overall is helpful too.


fix(app, app-shell): Add app layer robot update flow error handling

Closes RQA-1562, RQA-1714, RQA-1715, RQA-1680, RQA-1536, RQA-1747

Overview
This PR adds a layer of enforced consistency between robot update stages to reduce intermittent bugs that occur when updating and somewhat gracefully handle errors when they occur. Users are no longer indefinitely locked into update flows if the robot fails to respond - users may restart the update (except during the robot restart step) or exit the update if the app does not receive a robot update session event in 10 minutes (timer is debounced on new events).
The redux store now includes robot update session logic to delineate between robot updates initiated from a manual zip file vs. the S3 downloaded zip file, which is utilized when retrying a new update. We currently assume the S3 downloaded file is always correct, but users are prompted to select a new upload file if they previously selected an update file and the update failed.
This PR provides a general refactoring to update flows. Previously, update sessions were preserved in the redux store whenever an error occurred, leading to some erroneous assumptions about current robot update progress when a new update flow was launched - this PR now ensure a fresh session each time the flows are launched, and any sudden dismissal of the flows clears a session. Additionally, update flows are no longer conditionally rendered by the existence of a session/robot connection, which prevents flows suddenly closing (although this behavior still occurs in a few spots that will be addressed in a future PR). Lastly, progress bar logic has been made more scalable as more update step progress percentages will be added in future PRs (providing a more accurate & granular picture of update progress).
A bonus refactor of the app software update flows is included to bring them in-line with Figma.
NOTE: It is possible when uploading files manually to error out when restarting the update from within an existing update. It's non-blocking to the user (trying again AFTER the error works), but this will be addressed in a following PR.
Restarting an Update Via Zip File
https://github.com/Opentrons/opentrons/assets/64858653/eddcc0e9-40cd-4a18-9cc7-6603e5645136
Note that the update debounce interval was adjusted for this video.

Test Plan

Build this branch, launch it, then upload an older robot version via zip file to a robot (probably best to test on an OT-2, since they tend to be more error prone). Verify this works.
Update the robot to the latest version via S3 download (clicking on a banner). Verify this works.
Try reinstalling via Robot Settings > Advanced. Verify this works.
Set the TIME_BEFORE_ALLOWING_EXIT_MS within RoboUppateProgressModal to something like 5000, verify that the restart logic works. Verify that restarting the update does NOT render if the robot is on the "restarting" step

Changelog

Added "retry the update" logic for robot updates.
Refactored existing update flows to guard update transitions, reducing error occurrence.

Review requests

Test on real robots please!

Risk assessment
low-ish

Bringing back the cleanup function - I initially removed it when debugging some OT-2 update issues (caused by fun Wifi issues - not related to the PR), but it's absolutely essential to prevent some infinite re-rendering bugs caused by suddenly closing update banners (which will be addressed separately in a future PR).

No clue what the lint issue is - my prettier doesn't seem to change anything when I run it on useRobotUpdateInfo. Will look into this.


Floating Section Header not scrolling with tableView after using MXParallaxHeader for the tableHeaderView

So I am facing this problem on my project. Somehow we must use UITableView with Plain Style and then dynamically adding table section header in to the tableView. And for the TableHeaderView of course I am using MXParallaxHeader. However, when I scroll the tableView up, my section header view got stock at the origin position while all cells are scrolling up. It is a very weird behavior I never seen before.  I know #65 asked the same question but there is no a correct response. Please help. Thank you

So I tried #65 solution again and it worked. Basically what you should do to make UITableView Section Header works with MXParallaHeader is to add UITableView into MXScrollView,  assign your MXParallaxHeader (View) to the scrollView.parallaheader.view. And then set the correct scrollView.contentSize otherwise it won't be scrollable. This works well for my project, but the upcoming issue is that scrollView.parallaheader.minimumHeight doesn't work in this case. If someone know the solution, please share. Thanks

@Tim77277 I did that like you say , it worked . But It have a problem, when I scroll the list to the bottom , I can't keep scroll down although I set scrollView.bounces = true and collectionView.bounces = true. Did you get this problem?

Same problem here

@Tim77277 I did that like you say , it worked . But It have a problem, when I scroll the list to the bottom , I can't keep scroll down although I set scrollView.bounces = true and collectionView.bounces = true. Did you get this problem?

Same problem here


vscode window cannot be operated!

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: lastest
OS Version: windows 10

Steps to Reproduce:
1.Open vscode in your windows 10
2.Log in to win10 remotely from another computer and Wait a minute and then close, return your computer.
3.You will not be able to operate vscode unless you restart vscode.

Might be related to https://github.com/microsoft/vscode/issues/114097 , but I didn't get a chance to try out https://github.com/microsoft/vscode/issues/114097 yet.

sure, but I have to try in two hours. @bpasero

Good, this insider builds is ok, the problem did not recur.  At the same time, I found that Google browser has the same problem. @bpasero

When will the version be released?

Early November, but I suggest you stick with Insiders for the time being, it is fine.


Lab 4 and 5 - numeronyms and stringer interface

Fixes #67 & #70
Changes proposed in this PR:

[x] Implement and unit test numeronyms function
[x] Make IPAddr type implement fmt.Stringer to print dotted ip

Codecov Report

Merging #73 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #73   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          10     12    +2
  Lines         159    175   +16
=====================================
+ Hits          159    175   +16

Impacted Files
Coverage Δ

04_numeronym/mohankrishna/main.go
100% <100%> (ø)

05_stringer/mohankrishna/main.go
100% <100%> (ø)

Continue to review full report at Codecov.

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

I have added some comments. Please check.


Recording the trace of specified seed

Hi,
Excellent project. I see that basic block level pins is inserted during compile. Suppose I have a specified input that may lead to a crush. Is there any way to get the basic block level execution trace of the specified seed through AFLGo?

Hi @FrankWuwuwu,
You may take a look at "AFLGO_PROFILER_FILE" here. Note that it has overhead and you should not enable it during fuzzing.
Best.

Thanks for reply! I'm kind of not sure how to use it. I want to print all BBname when executing a specific seed. So, I can got a BBname trace after the execution.

@strongcourage

@FrankWuwuwu If you enable AFLGO_PROFILER_FILE, you will get a trace of covered basic blocks ID. Please see the code here https://github.com/aflgo/aflgo/blob/master/llvm_mode/afl-llvm-rt.o.c#L452-L479.


Xcode 9 - Main Thread Sanitizer

[READ] Step 1: Are you in the right place?
Yes
[REQUIRED] Step 2: Describe your environment

Xcode version: 9.0 beta (9M136h)
Firebase SDK version: 4.0.0
Library version: 4.0.0
Firebase Product: analytics, core

[REQUIRED] Step 3: Describe the problem
Xcode 9 seems to be reporting a lot of Firebase calls to UIApplication properties. Even though the UI is not being updated this is particularly cumbersome due to the extension of logs it produces on a default environment.
=================================================================
Main Thread Checker: UI API called on a background thread: -[UIApplication delegate]
PID: 740, TID: 51958, Thread name: (none), Queue name: FIRAnalyticsQueue, QoS: 9
Backtrace:
4   UnbabelMobile                       0x0000000101246448 __38+[FIRAnalytics createAppDelegateProxy]_block_invoke + 56
5   libdispatch.dylib                   0x0000000104751614 _dispatch_client_callout + 16
6   libdispatch.dylib                   0x0000000104752368 dispatch_once_f + 120
7   UnbabelMobile                       0x00000001012449d4 __47+[FIRAnalytics startWithConfiguration:options:]_block_invoke_2 + 104
8   libdispatch.dylib                   0x0000000104751654 _dispatch_call_block_and_release + 24
9   libdispatch.dylib                   0x0000000104751614 _dispatch_client_callout + 16
10  libdispatch.dylib                   0x0000000104761008 _dispatch_queue_serial_drain + 716
11  libdispatch.dylib                   0x0000000104754e58 _dispatch_queue_invoke + 340
12  libdispatch.dylib                   0x00000001047621c4 _dispatch_root_queue_drain_deferred_wlh + 412
13  libdispatch.dylib                   0x00000001047697fc _dispatch_workloop_worker_thread + 868
14  libsystem_pthread.dylib             0x00000001aa6e71e8 _pthread_wqthread + 924
15  libsystem_pthread.dylib             0x00000001aa6e6e40 start_wqthread + 4
=================================================================
Main Thread Checker: UI API called on a background thread: -[UIApplication applicationState]
PID: 740, TID: 51959, Thread name: (none), Queue name: com.google.fira.worker, QoS: 9
Backtrace:
4   UnbabelMobile                       0x0000000101244384 FIRAIsAppActive + 56
5   UnbabelMobile                       0x0000000101243830 -[FIRASessionReporter shouldStartNewSession] + 24
6   UnbabelMobile                       0x00000001012433d4 -[FIRASessionReporter initWithPersistedConfig:] + 284
7   UnbabelMobile                       0x000000010122f0bc __48-[FIRAMeasurement startMeasurementOnWorkerQueue]_block_invoke + 1828
8   libdispatch.dylib                   0x0000000104751614 _dispatch_client_callout + 16
9   libdispatch.dylib                   0x0000000104752368 dispatch_once_f + 120
10  UnbabelMobile                       0x000000010122e97c -[FIRAMeasurement startMeasurementOnWorkerQueue] + 268
11  UnbabelMobile                       0x000000010122e748 -[FIRAMeasurement setEnabledOnWorkerQueue:] + 124
12  UnbabelMobile                       0x000000010124304c __52-[FIRAScheduler scheduleOnWorkerQueueBlockID:block:]_block_invoke + 44
13  libdispatch.dylib                   0x0000000104751654 _dispatch_call_block_and_release + 24
14  libdispatch.dylib                   0x0000000104751614 _dispatch_client_callout + 16
15  libdispatch.dylib                   0x0000000104761008 _dispatch_queue_serial_drain + 716
16  libdispatch.dylib                   0x0000000104754e58 _dispatch_queue_invoke + 340
17  libdispatch.dylib                   0x00000001047621c4 _dispatch_root_queue_drain_deferred_wlh + 412
18  libdispatch.dylib                   0x00000001047697fc _dispatch_workloop_worker_thread + 868
19  libsystem_pthread.dylib             0x00000001aa6e71e8 _pthread_wqthread + 924
20  libsystem_pthread.dylib             0x00000001aa6e6e40 start_wqthread + 4

Steps to reproduce:
Compile an app which uses the Analytics platform and configure the FirebaseApp.
Relevant Code:
FirebaseApp.configure()

Same problem here:

Same issue here! Running Xcode 9 on iOS 11.

Acknowledged. The issue is in a closed source part of Firebase and we're actively working on the fix.
I'll keep this Issue updated with the status.

You're awesome. Thank you!

Hi there. Just checking on whether there is an ETA on this one?
My CI / Tests are failing right now.

We're testing a fix that is targeted for the next Firebase patch update. I'll follow up here when it's available.

Thanks @paulb777.
Quick note for those that are finding tests failing, note that iOS 11 is crashing on this error. Switching Tests back to iOS 10.2 or 10.3 stops tests failing unnecessarily.

+1

☝

Thanks everyone for the feedback.
We just released Firebase 4.0.3 that fixes the main thread sanitizer issue.

But where? https://firebase.google.com/download/ios goes to 4.0.2

@steipete Sorry about the delay. The CocoaPod was updated when I posted but the zipfile update was delayed. It's now fixed and https://firebase.google.com/download/ios now goes to 4.0.3.

which pod should I use to get this updated version with the fix?

Unless there is a special reason to use an old version, you should update to the current Firebase 4.1.1.
This particular fix released in FirebaseAnalytics 4.0.2, which was included with the Firebase 4.0.3 release.

source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '9.0'
#use_frameworks!
target 'MiddleEast' do
pod 'Firebase/Core'
pod 'Firebase/Messaging'
end
@paulb777 Hello, I am through the above Podfile file update, but CocoaPod inside automatically updated Firebase is 3.17.0 version, which is why?

I'm facing same issue,
Using AFNetworking (3.1.0)
Using Branch (0.18.8)
Using CardIO (5.4.1)
Using Crashlytics (3.8.6)
Using Fabric (1.6.13)
Using Firebase (3.17.0)
Using FirebaseAnalytics (3.9.0)
Using FirebaseCore (3.6.0)
Using FirebaseInstanceID (1.0.10)
Using FirebaseMessaging (1.2.3)
Using GTMOAuth2 (1.1.5)
Using GTMSessionFetcher (1.1.11)
Using Google (3.1.0)
Using GoogleSignIn (4.1.0)
Using GoogleToolboxForMac (2.1.1)
Using KontaktSDK (1.4.4)
Here the pods im using
Xcode 9
iOS 11

How to handle this issue like try catch

@ZhengXueNing @Sea-Eagle Make sure you run pod repo update before pod update to get the latest available pods.
If that doesn't work, it's likely that you have a another pod in your Podfile that depends upon Firebase 3.x and doesn't support Firebase 4.x. In particular, @Sea-Eagle, it looks like you're using the Google pod which has been deprecated.  See https://stackoverflow.com/questions/44538472/cocoapods-ios-google-has-been-deprecated-how-to-get-rid-of-the-warning
If you're still stuck, create a question on stackoverflow and include the contents of your Podfile.

Sure I will check and update

How can handle this issue I want to just skip this if I got any error how can I do that try catch not working

@Sea-Eagle See https://stackoverflow.com/a/44392584/556617

Here is My new pod update
Last login: Thu Sep 21 20:02:48 on ttys000 User$ pod update Update all pods Updating local specs repositories   $ /usr/bin/git -C /Users/.cocoapods/repos/master fetch origin   --progress   remote: Counting objects: 9, done.           remote: Compressing objects: 100% (9/9), done.           remote: Total 9 (delta 6), reused 0 (delta 0), pack-reused 0           From https://github.com/CocoaPods/Specs      7cf3745c74a..b418e34e7ae  master     -> origin/master   $ /usr/bin/git -C /Users/.cocoapods/repos/master rev-parse   --abbrev-ref HEAD   master   $ /usr/bin/git -C /Users/.cocoapods/repos/master reset --hard   origin/master   HEAD is now at b418e34e7ae [Add] QMServices 0.5.2 Analyzing dependencies Removing Google Downloading dependencies Using AFNetworking (3.1.0) Using Branch (0.18.8) Using CardIO (5.4.1) Using Crashlytics (3.8.6) Using Fabric (1.6.13) Installing Firebase 4.2.0 (was 3.17.0) Installing FirebaseAnalytics 4.0.3 (was 3.9.0) Installing FirebaseCore 4.0.7 (was 3.6.0) Installing FirebaseInstanceID 2.0.3 (was 1.0.10) Installing FirebaseMessaging 2.0.3 (was 1.2.3) Using GTMOAuth2 (1.1.5) Using GTMSessionFetcher (1.1.11) Using GoogleSignIn (4.1.0) Using GoogleToolboxForMac (2.1.1) Using KontaktSDK (1.4.4) Using LJAutoScrollView (1.0.1) Using MBProgressHUD (1.0.0) Using Protobuf (3.4.0) Using Reachability (3.2) Using SCNetworkReachability (2.0.5) Using SDWebImage (4.1.0) Using STPopup (1.8.2) Using Stripe (11.3.0) Using YLProgressBar (3.10.1) Using libPhoneNumber-iOS (0.9.10) Using macros_blocks (0.0.1) Installing nanopb (0.3.8) Generating Pods project Integrating client project Sending stats Pod installation complete! There are 18 dependencies from the Podfile and 27 total pods installed.

The issue is changed to
[Firebase/Core][I-COR000003] The default Firebase app has not yet been configured. Add [FIRApp configure]; (FirebaseApp.configure() in Swift) to your application initialization. Read more: https://goo.gl/ctyzm8.
I'm already doing in a method
if([FIRApp defaultApp] == nil){
    [FIRApp configure];
}

I got it. As someone said before - it's all about dependencies. After few hours I changed
pod 'Google/Analytics' to pod 'GoogleAnalytics'
and Google/SignIn it will be GoogleSignIn
then
pod install
pod update
and finally I'v got:
Installing Firebase 4.2.0 (was 3.17.0)

We only use Firebase Core, and changing the Podfile from pod 'Firebase/Core' to 'pod FirebaseCore' has worked to update it.

@markostt, @lsalvoni thanks for sharing. This what helped me:
- pod 'Google/SignIn'
+ pod 'GoogleSignIn'
- pod 'Firebase/Core'
+ pod 'FirebaseCore'
- pod 'Firebase/Messaging'
+ pod 'FirebaseMessaging'

I'm using
pod 'FirebaseDatabase'
pod 'FirebaseStorage'
pod 'FirebaseCore'
pod 'FirebaseAnalytics'
pod 'FirebaseAuth'

And still stuck with the issue. Even after repo update and pod update.
Using FacebookCore (0.2.0)
Using FacebookLogin (0.2.0)
Using FirebaseAnalytics (4.0.3)
Using FirebaseAuth (4.2.0)
Using FirebaseCore (4.0.7)
Using FirebaseDatabase (4.0.3)
Using FirebaseInstanceID (2.0.3)
Using FirebaseStorage (2.0.2)

There was a fix to a similar issue addressed here.  It seems there is another related issue on the current release, tracked at #310.


move wlr_drm_connector_add_mode to wlr/backend/drm.h

It is meant to be used by compositors, so it should be in the public headers.

I updated the PR to forward-declare drmModeModeInfo and also fixed the rootston include.

rootston should now include xf86drmMode.h since it uses wlr_drm_connector_add_mode

It is included in config.h

Thanks!


Help using CSS

Hi! First, thank you very much for allowing using this theme for free!
Haven't found information about how CSS files are actually generated. For example, I would like to change image size for "blog-card.html" partial, but do not understand where original CSS files are placed. I was able to find them only after compiling in /resources/_gen/assets/css/css/. Can you please help me with it?
Thank you!
P.S. I am really sorry if it is a wrong place to ask such kind of questions.

hey @gliese3, you can find every CSS files in assets/scss. But I suggest you use the custom.scss file to write your CSS. thanks

Yes, got it. Haven't heard about scss before. Thank you!

Any instruction? I added assets/scss/custom.scss, and it still does not work

It worked perfectly for me. It is now possible to modify already existed styles from here or to add new ones. Don't know why it didn't work out for you.


android firebase file upload in background service stopped when clear app from recents.

Step 1: Are you in the right place?

For issues or feature requests related to the code android storage file a Github issue.

Step 2: Describe your environment

Android device: _____Mi note5
Android OS version: _____oreo
Google Play Services version: _____
Firebase/Play Services SDK version: _____

Step 3: Describe the problem:
I have used your code for file upload in background service. It works fine when the app is running. but when the app is removed from recent apps or get killed then the uploading and notification stopped and remains as it is.
@RequiresApi(api = Build.VERSION_CODES.LOLLIPOP)
public class NotificationJobService extends JobService implements UploadFileToServer.UploadEventListener {
    private JobStartedListner jobStartedListner;
    ArrayList<File> sourceFileList = new ArrayList<File>();
    UploadFileToServer uploadFileToServer;

    @Override
    public void onPreExecute() {

    }

    @Override
    public void onComplete() {

    }

    @Override
    public void onProgressUpdated(Integer progress, int totalSize, int currentFilePosition) {

    }

    public interface JobStartedListner {
        public void onJobStarted();
    }

    public NotificationJobService() {
    }

    @Override
    public boolean onStartJob(JobParameters jobParameters) {
        Log.e("Job Params", jobParameters.toString());
        String[] data = jobParameters.getExtras().getStringArray("data");
        for (int i = 0; i < data.length; i++) {
            if (data[i] != null) {
                File f = new File(data[i]);
                sourceFileList.add(new File(data[i]));
            }
        }
        uploadFiles(this, sourceFileList, this);
        return false;
    }

    public void uploadFiles(UploadFileToServer.UploadEventListener uploadEventListener, ArrayList<File> sourceFileList, Context context) {
        uploadFileToServer = new UploadFileToServer(uploadEventListener, /*new File(imagepath)*/sourceFileList, context);
    }

    @Override
    public boolean onStopJob(JobParameters jobParameters) {
        uploadFileToServer.cancel(true);
        return true;
    }
}

Hi @samtstern From the initial bit of what I have read workManager is used for synchronous tasks. Can it also do async work?

I hope this gets fixed


Fix mingw support

This addresses #1105.
It also cleans up some redundant checks. E.g. if defined(_WIN32) || defined(_WIN64) is equivalent to if defined(_WIN32) because even in 64 bit mode, _WIN32 is defined as well.
In memio.c I had to make one exception and use #if defined (_WIN32) && !defined(__MINGW32__) as in this case mingw doesn't expose this particular Windows API function.

 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.

Thanks! It looks like the CI is failing, I'll dig into this further in a bit and for now I will restart them just to make sure it wasn't a glitch of some sort.

Your merges from master a month ago broke the MinGW build in this branch (I haven't tested with latest master merged in):
C:/msys64/tmp/netcdf-c/libdispatch/dwinpath.c: In function 'NCremove':
C:/msys64/tmp/netcdf-c/libdispatch/dwinpath.c:232:32: error: 'ENOENT' undeclared (first use in this function)
     if(cvtname == NULL) return ENOENT;
                                ^~~~~~

It would be good if there was continuous integration setup for MinGW, e.g. with Appveyor, to detect such issues immediately.
Regarding the PR itself, are there any issues with it or can it be merged?

This is odd. According to this:
https://msdn.microsoft.com/en-us/library/5814770t.aspx
ENOENT is defined under visual studio. Is is really not  defined
under MINGW? Did you look at the errno.h for MINGW?

ENOENT is part of errno.h, but I can't see that this file is included in dwinpath.c. It could be that it is transitively included in Linux from other standard library headers (or similarly with MSVC headers) but this doesn't seem to be the case in MinGW and to be honest is not something one should rely one in general.

Looks great, can you rebase so that it can be merged ?

@jschueller This PR has been stale for a while, so I'm only willing to invest time if there's agreement it will be merged. Ideally, the rebasing can also be done by @DennisHeimbigner or @WardF, similar to how they've done it before in this PR.

Is it possible to do the ming build on a standard Ubuntu linux box?
If so, I can set up a CI run to ensure that this continues to work.

totally, see https://github.com/stevengj/nlopt/blob/master/.travis.yml

I've rebased and am prepping it for merge, but I see a failure I will follow up on when the other CI finishes.

it seems struct MagicFile has moved to dinfermodel.c, you need to rebase the changes to dfile.c against the current master


Getting NPM warn for the latest Angular project.

Command
version
Is this a regression?

[x] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
npm WARN deprecated<EMAIL_ADDRESS>This functionality has been moved to @npmcli/fs
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-unicode-property-regex instead.
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-async-generator-functions instead.
npm WARN deprecated<EMAIL_ADDRESS>Use your platform's native performance.now() and performance.timeOrigin.
npm WARN deprecated<EMAIL_ADDRESS>this package has been renamed to ts-evaluator.

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.1602.0 (cli-only)
@angular-devkit/core         16.2.0 (cli-only)
@angular-devkit/schematics   16.2.0 (cli-only)
@schematics/angular          16.2.0 (cli-only)

Anything else relevant?
No response

Attached new angular repro.
repro-app.zip
on npm install getting below warnings.
npm WARN deprecated<EMAIL_ADDRESS>This functionality has been moved to @npmcli/fs
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-unicode-property-regex instead.
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-async-generator-functions instead.
npm WARN deprecated<EMAIL_ADDRESS>Use your platform's native performance.now() and performance.timeOrigin.
npm WARN deprecated<EMAIL_ADDRESS>this package has been renamed to ts-evaluator. Please install ts-evaluator instead
added 1009 packages, and audited 1010 packages in 15s

This has already been addressed via https://github.com/angular/angular-cli/pull/25820 which will be available as part of version 17.0.0 that will be released later this week.
For version 16 users, these warnings are safe to ignore.


FontUtil.convertToBoldFont should consider using the bold JFace font type for default font

If the font passed into FontUtil.convertToBoldFont is a JFace dialog font (JFaceResources.DIALOG_FONT), then the returned font should be it's bold version.
The current implementation creates a new font from the provided one by converting it to bold, however this causes problems if the user resizes the dialog font in Eclipse/Preferences/Appearance. This resize mechanism will resize the font of all controllers that has the control's default font. If we create a new bold font with the current implementation, that won't be recognized as the default, and won't be resized. E.g.: as a result, all the controls will have fonts of the new size in DeployPreferencesPanel except for the Advanced section`.


Complaint request filter: Match against endpoint URLs from adapter instead of hostname from HAR

In e9e52478e3572445357488ff81964b2f56a52c1f, I implemented a filter that only includes requests to servers that the user's device also provably (through Tracker Control/the App Privacy Report) contacted.
I am currently doing that by checking the request's hostname from the HAR against the hostnames in the TC/APR export.
Instead of the HAR hostname, I think we should be checking against all endpoint URLs that the corresponding adapter accepts.
Imagine a tracking endpoint https://api\d.tracker.tld/ingest. If during our analysis, we happened to find requests to https://api2.tracker.tld/ingest but the user's device happened to use https://api5.tracker.tld/ingest instead, we would currently exclude those requests.
However, implementing it this way is surprisingly hard. We only get a hostname from the TC/APR export. Meanwhile, our adapters' endpoint URLs can be strings or regexes of full URLs.
How would we check whether android2-ads.adcolony.com matches /^https:\/\/(android|ios)?ads\d-?\d\.adcolony\.com\/configure$/? Maybe I'm missing something, but I really can't see an automated way that isn't hacky and error-prone.
I feel like the only (proper) way to implement this change would be to also manually add a hosts array to each adapter in TrackHAR.

@zner0L What do you think?

I just thought of creating a kind of Endpoint object which would allow to decompose the endpoint URL similarly to the URL JS object. For regexes, we could combine a host regex with a path and protocol component (like this: https://stackoverflow.com/questions/9213237/combining-regular-expressions-in-javascript).


Tesla: some MADS fixes

This gets MADS to a sorta-working but still flakey state
Biggest 2 issues are:

half-press down sometimes doesn't prevent ACC from engaging
full-press up to turn off MADS results in shifting to reverse if below 5mph!!

bbbf82d987d681bc/00000008--d548c019f5

From discord:
observed stalk quirks with MADS:
half-press down while too slow for acc still engages MADS, but car alerts that "Cruise is unavailable"
full-press down from nothing results in both cruise and lat, so there's currently no cruise-only option
half-press up when cruise isn't enabled results in "Hold for neutral" message, but this isn't a problem because you would only half-press up to cancel cruise as it's currently programmed
full-press up to turn off mads when acc is already off results in an attempt to shift to reverse. If below 5mph and turning off mads, the car actually goes into reverse.
The first 3 are only annoyances, the last one is serious, I think we can't use full-up for anything, we shouldn't encourage that input to be used regularly.
also it seems flakey that sometimes half-down results in lat+acc, and I can't tell why. It seems when that happens we don't send the half-up to cancel acc, which tells me we're not getting the CC.cruiseControl.cancel signal.
Input alternatives I'm thinking of after playing with it:
A: stalk press counter: 1x, 2x, 3x for mads, both, acc (or acc, both, mads based on user preference). Only use half up once to turn everything off, avoiding reverse issue. mads or acc can individually be turned off by steering or brake overrides respectively.
B: or keep current half/full down logic, but add falling edge detection with a max() to allow for "full-press-only", and use half-up to turn off everything at once, avoiding reverse issue.
C: or half-down for acc, full-down for acc+lat, half-up for mads on (if everything is off)...or half-up for everything off (if anything is on)
D: or 1x down for acc, 2x down for acc+lat, half-up for mads on (from off state)...or half-up for everything off (from engaged state)
C-D result in the fewest alerts, but still get an alert for enabling mads, maybe acceptable. However having half-up do 2 different things based on state might be confusing.
A and D are the closest to OEM Tesla behavior, and right now A is the best sounding option to me to be intuitive for existing Tesla owners upgrading to SP. maybe a bit weird for existing SP users downgrading to a tesla though 😉

will be superseded shortly


add PR template

Purpose
The team have agreed that we can improve pull requests and ensure we've completed all the requirements from our definition of done with a pull request template.
Fixes UML-480
Approach
Add a pr template file to our docs.
Learning
https://help.github.com/en/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository
Checklist

[x] I have performed a self-review of my own code
[x] I have updated documentation (Confluence/GitHub wiki/tech debt doc) where relevant
[ ] I have added tests to prove my work
[ ] The product team have tested these changes

Coverage remained the same at 77.736% when pulling b5e66770b268c14f8d46b914a8cb728eedc89bb2 on UML-480 into 18022b8caa9075dc166c77fc96e6b6564b18c320 on master.

My only concern with the precommit stuff is that it's entirely reliant on the devs to have it installed?

My only concern with the precommit stuff is that it's entirely reliant on the devs to have it installed?

Yes, that's true. I think this then beecomes part of our agreed ways of working (if we agree to use it), and is something we introduce people to.
Terraform validate, format and github checking for secrets also happen after a commit/PR. This helps spot those things ealier though.


Display the identity provider in the requester's info on the access request modal

Identify the requester's identity provider (IDIR, BCSC, etc) in the requester's information (top right of the access request modal) as we can't assume that the username ends with an idir

DoD: a design that displays the identity provider

Design specs:

@JohnathanBrammall @ikethecoder @Jonesy please review ticket :)

This looks great. Thanks @elisafw-ux

@Jonesy ready for implementation


Group layouts makes small area of the page non clickable

Hello. I use an example layout.
p-6 px-4 py-6 pointer-events-none
When I drop pointer-events-none to make my errors selectable small rectangular of the page becomes non-clickable cause it is always rendered (because of the container's padding).
I don't know how to hide it cause notifications slot available only for Notification
What am I missing?
Thanks.

Hey!
You can solve this problem by adding pointer-events: initial to the first div of the Notification component and remove the pointer-events-auto class if it has one.
Keep the pointer-events-none class in the first div of the NotificationGroup component to avoid non-clickable areas in the page.

Thanks, @emmanuelsw
I came up with following approach. But also will try yours.

<NotificationGroup group="generic">

        <Notification
          v-slot="{ notifications, close}"
          enter="transform ease-out duration-100 transition"
          enter-from="translate-y-2 opacity-0 sm:translate-y-0 sm:translate-x-4"
          enter-to="translate-y-0 opacity-100 sm:translate-x-0"
          leave="transition ease-in duration-100"
          leave-from="opacity-100"
          leave-to="opacity-0"
          move="transition duration-100"
          move-delay="delay-100">

 0">

                <svg class="w-6 h-6 text-white fill-current" viewBox="0 0 40 40" xmlns="http://www.w3.org/2000/svg">
                  <path d="M20 3.33331C10.8 3.33331 3.33337 10.8 3.33337 20C3.33337 29.2 10.8 36.6666 20 36.6666C29.2 36.6666 36.6667 29.2 36.6667 20C36.6667 10.8 29.2 3.33331 20 3.33331ZM21.6667 28.3333H18.3334V25H21.6667V28.3333ZM21.6667 21.6666H18.3334V11.6666H21.6667V21.6666Z"/>
                </svg>

....


Fix spark history

Fixes the spark history server to work in a Offline Repository environment.
Especially since a build of a Offline Repository wasn't possible.
It's also now possible to install the spark history server from the dcos ui, previously it's only been possible to do that via CLI

Thanks for the PR, but as with all data services packages, the source is elsewhere.  This is just object code.  You'll need to retarget your PR to https://github.com/mesosphere/spark-build/tree/master/history/package

@mgummelt, thanks for the info. Is there some documentation about this information, couldn't find it?
Another question, will this PR changes somehow merged into the spark-build project?

This PR will not be auto-merged into spark-build.  To ultimately get these changes into universe, you need to resubmit your PR to the spark-build project, after which I will push the updated package to universe.

There's no explicit mapping for where the source exists for each package, no.  That would be a nice improvement to universe, though.

@mgummelt ... where do I need to file such a feature request :)

http://jira.dcos.io
Thanks!

@mgummelt see https://jira.mesosphere.com/browse/DCOS_OSS-1306


update scala version

Hi Joseph, thanks! Can you merge the latest changes to the repo (which should fix the Travis build) and also make the corresponding changes in the pom for Maven?

Updated as requested.

Thanks!


Move to sphinx with md plugin

Add more flexibility to the website styling by moving to sphinx PyData theme.
Take advantage of MyST parser to keep the tutorial as scripts.

To be clear, in order to handle the tutorials as we're doing (plain-text documents that get converted to notebooks), we need not just myst, but myst-nb. What we want then is to write notebooks in pure markdown. Note that this will require a change from how we're handling them now: mkdocs-gallery (like sphinx-gallery) has you write notebooks as py files, whereas myst-nb has you write them as md files. It's very possible that jupytext can convert between these formats for us; it definitely can convert between ipynb and the myst-nb markdown formats, so at worst we can convert the mkdocs-gallery py file to ipynb, and then from that to myst-nb markdown. Just so we're not having to rewrite things manually.


Terms Fragment Created

This branch is a part of Terms & Service Features that would be shown to user after SignIn. In this Branch the fragment is created along with its view model.

Fixes #

@... PTAL?

This branch is a part of Terms & Service Features that would be shown to user after SignIn. In this Branch the fragment is created along with its view model.
Fixes #
@... PTAL?

Hi @HemanParbhakar thanks for the fix! Some minor procedural stuff:

Please fill in the template when creating a PR - @username PTAL for potential reviewers, Fixes #<issue no> with the appropriate issue.
Copyright headers in files should reflect the year the file was created (2021).
Lastly, to make tickets more discoverable and scannable bug and PR naming, we've been following the convention of [<Feature name>] <Change>, so in this case the PR title would be something like [ToS] Add fragment to display Terms of Service.
I'll pass the PR off to @atalekar for a first pass, then off to @shobhitagarwal1612 for a final LGTM. Thanks for the change!

@HemanParbhakar Regarding the PR description:

Fixes #

^-- please reference GitHub issue number here.

@... PTAL?

^-- please remove this line if you don't use it

@HemanParbhakar Did you happen to get a chance to address #753?

@HemanParbhakar Did you happen to get a chance to address #753?
https://github.com/google/ground-android/pull/747 fixed

Corporate CLA signed. @googlebot rescan

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.
What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ Googlers: Go here for more info.

@googlebot I signed it!

Woohoo!
On Thu, May 27, 2021 at 10:49 AM Gino Miceli @.***>
wrote:

@.**** approved this pull request.
@HemanParbhakar https://github.com/HemanParbhakar LGTM! Congrats on
your first merge! 🥳 💯
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google/ground-android/pull/744#pullrequestreview-670472298,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSRR3CMJBALSJJH6XUOZ63TP2A3PANCNFSM4ZVPII6Q
.

--
Alok Talekar


Update included C SDK

Fixed by https://github.com/sqlitecloud/sqlitecloud-kotlin/commit/3eff5687e56006ccd63c7913ae8d7f3e441f7554