Quickbooks Integration Missing

Relevant integration (if any):
Quickbooks (https://quickbooks.intuit.com/)
🐛 Describe the bug
Quickbooks integration appears on the https://toggl.com/tools page, but does not appear as a listed domain in the Integrations portion of the TogglButton extension
Other details or context
Reported by user

I asked user where they would like to see the TogglButton, and they replied saying they went with another app instead of Toggl so they don't need this feature :(
Having said that, the current issue is more simple. The QuickBooks integration option isn't available  in the integrations page at all, so if we can add it in, and then show the button on the main screen in QBO somewhere, users who are interested in the integration can start using it and maybe we will get more feedback on other places to include it. :)

https://chrome.google.com/webstore/detail/toggl-button-productivity/oejgccbfbmkkpaidnkphaiaecficdnfn?hl=en

This definitely caused some confusion for me. I suggest removing it if there is no integration.

References to Quickbooks have been removed, as the integration did not exist 🙈
Converting this issue to feature request


Is mixing FromSqlRaw and IncludeFilter supported?

Description
I'm trying to use FromSQLRaw in conjonction with IncludeFilter and it fails
var initialList = await context.AlertDetailsDbSet.FromSqlRaw(@"SELECT dbo.AlertDetail.* FROM dbo.AlertDetail
                        WHERE AlertDetailID IN (
                        select t.AlertDetailID FROM (SELECT
                            ad.AlertDetailID,
                            X.Y.value('(ContextId)[1]', 'varchar(50)') as ContextId,
                            X.Y.value('(Value)[1]', 'varchar(50)') as Value
                        from dbo.AlertDetail as ad
                        OUTER APPLY (SELECT TRY_CAST(CAST(ad.Context AS VARCHAR(MAX)) AS XML)) AS T(Z)
                        OUTER APPLY T.Z.nodes('/SerializableAlertDetail') as X(Y)) as t
                        INNER JOIN dbo.Context c  on t.ContextId = c.ContextId
                        INNER JOIN dbo.EnumDetail e on c.EnumId = e.EnumID
                        WHERE t.ContextId IS NOT NULL AND t.Value IS NOT NULL
                        AND e.IsPreAlert = 1)")
                        // Pouring the TrackedVehicle related graph
                        .IncludeFilter(ad => ad.TrackedVehicule)
                            .IncludeFilter(ad => ad.TrackedVehicule.AlertInstructions.Where(ai => ai.RowEnabled == true))
                            .IncludeFilter(ad => ad.TrackedVehicule.Registration)
                            .IncludeFilter(ad => ad.TrackedVehicule.Device)
                            .IncludeFilter(ad => ad.TrackedVehicule.GpsBox)
                            .IncludeFilter(ad => ad.TrackedVehicule.GpsBox.Icon)
.OrderByDescending(ad => ad.AlertDateTime)

                         .Skip(skip)

                         .Take(take)

                         // We disable the tracking mechanism because the context will be thrown away as soon as we have the data
                         .AsNoTracking()

                         // We want an asynchrounous execution
                         .ToListAsync(cancellationToken)

                         // We do not need to preserve the context because we're immdiately finished
                         .ConfigureAwait(continueOnCapturedContext: false);

As soon as I remove the IncludeFilter calls it works.
Exception
If you are seeing an exception, include the full exceptions details (message and stack trace).
System.AggregateException
  HResult=0x80131500
  Message=One or more errors occurred. (No mapping exists from object type System.Object[] to a known managed provider native type.)
  Source=System.Private.CoreLib
  StackTrace:
   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.Wait()
   at RTE.Technologies.SafeProtect.Common.DummyConsole.Program.Main(String[] args) in D:\AzureDevops\SafeProtect.Common\SafeProtect.Common.Data.ConsoleTest\Program.cs:line 356

  This exception was originally thrown at this call stack:
    [External Code]
    RTE.Technologies.SafeProtect.Common.Data.DataBridge.Core.AlertDetailDataBridge.GetAlertDetailListAsync(int, int, int, bool, bool, System.Threading.CancellationToken) in AlertDetailDataBridge.cs

Inner Exception 1:
ArgumentException: No mapping exists from object type System.Object[] to a known managed provider native type.

Fiddle or Project
Should be easy to reproduce.
Further technical details

EF version: 3.1.8
EF Plus version: 3.0.61
Database Provider: MS SQL Server

Hello @omatrot ,
Unfortunately no, this is not supported.
To support it, we will need to re-write probably fully this feature and even more, investigate if it's still useful as EF Core 5 is bringing a feature similar to include filter.
Best Regards,
Jon

Performance Libraries
context.BulkInsert(list, options => options.BatchSize = 1000);
Entity Framework Extensions • Entity Framework Classic • Bulk Operations •  Dapper Plus
Runtime Evaluation
Eval.Execute("x + y", new {x = 1, y = 2}); // return 3
C# Eval Function • SQL Eval Function

Will it work if I'm using a view instead?

I don't think it will work either @omatrot ,
As said, when we initially built this feature, it was for pure LINQ, we never did any test with SQL or view


add =~ and $matchdata

mruby regex has no function to use operator =~
and $1, $2 also not available
use global $matchdata as replacement of $1, $2

@WindProphet Would you write some tests for =~ and $matchdata?
https://github.com/h2so5/mruby-pure-regexp/blob/master/test/regexp.rb
https://github.com/h2so5/mruby-pure-regexp/blob/master/test/string.rb


Mixtral Bug

I try to make a mlx version of my MOE model cloudyu/Mixtral_34Bx2_MoE_60B https://huggingface.co/cloudyu/Mixtral_34Bx2_MoE_60B
But the mlx version doesn't work, I don't know the reason.
it report:
mlx-examples/llms/mlx_lm/models/mixtral.py", line 137, in call
mx.argpartition(-gates, kth=ne, axis=-1)[:, :ne]
ValueError: [argpartition] Received invalid kth 2 along axis -1 for array with shape: (1,2)
I read the code
https://github.com/ml-explore/mlx-examples/blob/main/llms/mlx_lm/models/mixtral.py
at 130 line:
it should be ne = self.num_experts_per_tok - 1  instead of ne = self.num_experts_per_tok
ne = self.num_experts_per_tok that means 1+self.num_experts_per_tok experts working.

Yup, that's a bug.. do you want to send a PR with your suggested fix?

Yup, that's a bug.. do you want to send a PR with your suggested fix?

https://github.com/ml-explore/mlx-examples/pull/673


kafka: deduplicate batches;

This change will allow us to remove any duplicates from the batches.

blocking this until further notice, will add some logging on our fork to see if we actually have duplicates

Will wait until further investigation :)

I had a look at what might be the reason of the duplicates and I concluded that the duplicates seem to appear when the partitions are rebalanced.  The code responsible seem to have a comment that informs about the possibility of re-processig of messages https://github.com/segmentio/kafka-go/blob/ebca72eaee918d303c532feb7ff29afdcd8c2efa/reader.go#L114
Sadly from what I can see this process of rebalancing is transaprent to us so we can't change the logic to fiish processing the partial batch


Adding a not_ or not_in validator?

I've had cases where it's nice to be able to compose the standard validators to do what I need without needing to write a custom function. It generally ends up looking more declarative and less imperative, so easy to read later. Often, however, there are cases where I'd like to be able to invert a standard operator, for instance, if I want a field to match a regex, but also not be a reserved value, I'd like to be  do something like:
reserved_values = {"id", "timestamp"}
attr.validators.and_(
    attr.validators.matches_re(r"^[\w\.\-]+$"),
    not_(attr.validators.in_(reserved_values)),  # not_ TBD.
)

It could maybe be added as just a specific variant of in_, i.e. not_in without much trouble, but I don't know if something like as generic as not_ would be a good idea. It could then maybe be used when composed with other validators. I'd be willing to give not_in a stab, but if it should be generalized to not_, /shrug.

fixed by #1010


Request to make SC4S_SOURCE_UDP_FETCH_LIMIT configurable

The SC4S_SOURCE_UDP_FETCH_LIMIT configuration variable seems to have been skipped or missing.  After discussions with Baszi and Ryan, they agree that the default of 100 is likely not sufficient for all use cases.

@jrehm-mmm,
Thanks for reaching out.
We will review about this change with internal team and will keep you posted.
Thank you.

Can you perhaps give an update on the status of this request?

Other properties are added in 2.49.0


10.0.35 with wrong name.

Simple error but appreciate if you fix it!
The [ symbol at the beginning and the 10.0.34 number which should be 10.0.35
[What's new and changed in Dynamics 365 Finance version 10.0.34 |

@fsilva-jr, thank you for the feedback. The article has been updated.


faulty default "install whatever matches the name" logic on partial name match

Brief description of your issue
I was working on VSCode terminal and wanted to install a linux command. I wasn't sure if it exists but tried my luck believing it would throw an error on me.
Upon entering the install command, I got a prompt asking "Yes/No" to continue the installation, and here comes the problem: VSCode terminal has only about 1/3 of the screen and the description above the prompt was not good enough to stop me to believe it got what I wanted.
I confirmed only to regret it later when I see the full name of the package I allowed to be installed after it has downloaded a big file, and it was only when a Windows notification popped up.
I have checked the screen, and the name of the package was given 1-2 pages worth of scrolling away.
Every package manager I have used so far has nothing like this. If they can't find a full match, they are listing matching packages but then exit right away.
I have the fault to allow the installation without reading it whole, but you guys have the responsibility to prevent such occurrences because we are believers that developers would think about such behaviors before making it default.
Steps to reproduce
winget install tee

try this command in a VSCode terminal.
The name of the package is very far away from the prompt and all the printing causes a false sense of correctness.
Expected behavior
There are two expectation on such occasions:

print matching package names AND exit. user should enter command again with the whole name
the name of the package to be installed should appear just above the consent prompt, even if it is given somewhere else in the text above it.

Actual behavior

The name of the package that has only partial match to its name, is given only "once" at the top of all scrolled text (and maybe in the description section)
although it is a partial match, , the package is set to be installed.

Environment
``winget --info``
`
Windows Package Manager v1.3.2691
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19044.2251
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.18.2691.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

This appears to be a subtle issue with the differences in the search behavior between the "msstore" (Microsoft Store) source and the "winget" source. It looks like "TEEM" from the Microsoft store was the match (false positive) in this case.


Facing issue while using istio : “ upstream connect error or disconnect/reset before headers. reset reason: protocol error”

We are facing the “upstream connect error or disconnect/reset before headers. reset reason: protocol error” when we are calling one api to another api using the postman.
You can check the listeners on your ingress gateway are present and configured with the correct protocol as expected
istioctl pc listener -n istio-ingress <ingress_pod_name>

and you may be able to capture more or the exact error on the ingress gateway by increasing envoy's logging level:
istioctl pc log -n istio-ingress <ingress_pod_name> --level <trace|debug>
# send bad request
# reset log level back to normal
istioctl pc log -n istio-ingress <ingress_pod_name> --reset


Create basic architecture

Proposal for Basic Fastify API Architecture
This PR proposes a basic architecture for a Fastify API. It does not contain any features. I suggest we open an issue and create a roadmap for the next steps.

The base was generated by (and designed to work with) fastify-cli.
Uses TypeScript with typescript-eslint
Uses glob to run tests on Windows.
Uses shared workflow v4.1.0

Core plugins used:
helmet, cors, swagger, env, sensible, under-pressure
TODO:

add doc about docker-composition
create CI workflow

fastify-cli generates a lot of comments, but I decided to keep them because they are educational.
I've also added a server.js file just to show how not to depend on fastify-cli.
Wait for your feedbacks.

Also I would personally love to see typescript! Together with ESM.

Is there perhaps a debug bar plugin for fastify which can give us metrics on the performance of our server,similar to the debug bar we see in the symfony demo and laravel framework? I can't seem to find one.
I think Typescript integration would be great.
On the note of the roadmap what is your initial ideas on the features and use cases of this project?

I'm not sure the way I've organized the plugins is relevant @melroy89.
I've tried to leverage the autoloader to keep the code clean, but I'd like your feedback.

Autoloader is good to use indeed! And also the best way of doing it IMO. I personally have my files within the plugins directory without the additional sub-directories now you created. Which I believe will reduce the complexity.
I personally added the Swagger fastify.register in server.ts. You created a separate plugin for only register the swagger plugin, I believe this is not necessary.

Is there perhaps a debug bar plugin for fastify which can give us metrics on the performance of our server,similar to the debug bar we see in the symfony demo and laravel framework? I can't seem to find one.

Not that I know of. I do know @fastify/under-pressure if you want to limit the calls. And in your case your are looking for fastify-metrics maybe to collect data and push it to Prometheus. And then use some Grafana instance for example to plot data.
But again, no built-in "debug bar" web UI element. I think fastify-metrics is the closest. And of course just use the default Pino logging??

Not that I know of. I do know @fastify/under-pressure if you want to limit the calls.

Ho, yep, I should add this plugin too I think.

So, todo:

Adding TypeScript. With Type-Providers I guess.
Under-pressure plugin, I will link this video of Matteo in the comments: https://www.youtube.com/watch?v=VI29mUA8n9w
Simplifying plugin folder structure
Put swagger plugin config directly in app.ts

Do you have any other idea right now for the basic architecture?

@jean-michelet You are right on track with Type Providers for TS. Especially also for schema validation both out and incoming requests/responses. But also declaring your own version/extending the FastifyInstance interface (part of declare module 'fastify') for Fastify config options.
Maybe also add an common example for authentication using @fastify/auth.  Like maybe a simple but yet powerful JWT strategy on top of fastify/auth. Reminder fastify/auth is not providing an authentication strategy itself.
I believe another good practice is to configure setErrorHandler on the Fastify app. As well as setNotFoundHandler. My code:
    this.app.setErrorHandler((err, req, reply) => {
      req.log.error({ err })
      reply.status(err.statusCode || 500)
      reply.send(err)
    })

    this.app.setNotFoundHandler(async (req, reply) => {
      req.log.info({ req }, 'request was not found')
      reply.code(404)
      return { message: 'Not found' }
    })

Maybe you also want to add an caching example.
Last but not least, best practices for logging. Fastify() constructor provides a way to give additional options for the logger, but also ajv. Maybe ajv is out of scope, but very powerful non the less if you want to let's say remove additional body properties which aren't part of your schema you can configure that via { ajv: { customOptions: { removeAdditional: 'all' } }.  And the logger via: { logger: <...>}. Options for the logger is either a boolean. Or  during development I use a more advanced JS object that I pass to the logger:
 {
    level: 'info',
    transport: {
      target: 'pino-pretty',
      options: {
        translateTime: 'HH:MM:ss Z',
        ignore: 'pid,hostname',
      },
    },
  }

Here a full example, what I have (do whatever you want with this info):
const environment = process.env.NODE_ENV || 'production'
 const envToLogger: {
     [key: string]: object | boolean
   } = {
     development: {
       level: 'info',
       transport: {
         target: 'pino-pretty',
         options: {
           translateTime: 'HH:MM:ss Z',
           ignore: 'pid,hostname',
         },
       },
     },
     production: true,
     test: false,
   }

   this.app = Fastify({
     logger: envToLogger[environment] ?? true,
     ajv: {
       customOptions: {
         coerceTypes: 'array', // change data type of data to match type keyword
         removeAdditional: 'all',// Remove additional body properties
       },
     },
   }).withTypeProvider<JsonSchemaToTsProvider>()

Ps. MAYBE... a MySQL or other database integration example? Like @fastify/mysql.

I shouldn't have replied by mail, sorry ^^

@melroy89
Now that I think about it, maybe I should go beyond the basic architecture and offer a complete application, albeit with a modest scope. It could save review time from Matteo and the Core Team.
I have some reading to do (I wanted to make this demo as an opportunity to learn Fastify deeper), but I am pretty confident I can push a lot to review the next week.
Wdyt?

Should we use ts-standard?
I use it on my own projects, but the rules are pretty strict. For example, explicit-function-return-type is applied.

Should we use ts-standard? I use it on my own projects, but the rules are pretty strict. For example, explicit-function-return-type is applied.

I'm using eslint and the official typescript-eslint plugin: https://typescript-eslint.io/getting-started/. I use eslint together with @typescript-eslint/recommended" and prettier.

I have another general remark; move all the code (except maybe the test code? Leave that in test) to a sub-directory called src. I personally do not like to have my code in the root-folder next to the README.md, instead I move the code into a separate directory like src.
Update the package.json file (or other configs) accordingly if needed.

Current TODO for setting up basic architecture:

add doc about docker-composition
create CI workflow
achieve better coverage (test under-pressure health check)

If anyone has feedbacks, I'll continue to work on this next week.
@metcoder95 maybe?

In order to keep a simple CI, I think we should only run the tests on Linux.
It's a demo, not a dependency so I think it's ok.

I left a pair of comments, so far I believe we can maybe simplify it a little and focus a bit more on the documentation that highlights the pieces of fastify.

Yes, I haven't really thought about the documentation yet. I had planned to split the creation of this repository into several PRs to give interested developers the opportunity to contribute. But I think we should not create something too simple, it's a great opportunity to show implementations with advanced parts of Fastify and Node.js.
Regarding the development process, which do you prefer @mcollina @metcoder95? I can also work until version 0 is ready, I'm fine working on my own ;)

Regarding the development process, which do you prefer @mcollina @metcoder95? I can also work until version 0 is ready, I'm fine working on my own ;)

If no answer, I will start to create a API.
Not sure what I should use for authentication though... I think it's a bad idea to use JWT by default, challenging to implement securely imo. At the same time, many Node.js tutorials demonstrate this...

We can keep it on v0 for a while until we feel comfortable with it.

Not sure what I should use for authentication though... I think it's a bad idea to use JWT by default, challenging to implement securely imo. At the same time, many Node.js tutorials use it...

Can be a good default, tho it is important to document that this is just a demo and further security recommendations should be added

Can be a good default, tho it is important to document that this is just a demo and further security recommendations should be added

Can be a good opportunity to educate about security too, but I understand that it could be out of scope.

How do you feel about this kind of composition?
import fp from 'fastify-plugin';
import { RowDataPacket } from 'mysql2/promise';
import { FastifyInstance } from 'fastify';

type CreateRepository = (tableName: string) => {
  find: <T>(select?: string, where?: Record<string, any>) => Promise<T | null>;
};

export default fp(
  async function (fastify: FastifyInstance) {
    const processRecord = (record: Record<string, any>) => {
      const keys = Object.keys(record);
      const values = Object.values(record);
      const clause = keys.map((key) => `${key} = ?`).join(' AND ');

      return [clause, values] as const;
    };

    // This is an example to demonstrate the power of composition in fastify
    // You might want to use an ORM or a query builder for your project
    const createRepository: CreateRepository = (tableName) => {
      const find = async <T>(select = '*', where = {}) => {
        const [clause, values] = processRecord(where);

        const query = `SELECT ${select} FROM ${tableName} WHERE ${clause}`;

        const [rows] = await fastify.mysql.query<RowDataPacket[]>(query, values);
        if (rows.length < 1) {
            return null;
        }

        return rows[0] as T;
      };

      return {
        find
      };
    };

    fastify.decorate('createRepository', createRepository);
  },
  { name: 'repository', dependencies: ['mysql'] }
);

import fp from "fastify-plugin";

export default fp(
  async function (fastify) {
    fastify.decorate("authRepository", fastify.createRepository('users'));
  },
  { name: "authRepository", dependencies: ['repository'] }
);

I'm working on the design of the api, a basic task application.
I'd like to manage authorization with user permissions.
I want to add the ability to add avatars to users and task generation in CSV format to show how to manipulate files.
This could be a good start, I haven't thought much about what to do next, but do you have any ideas? Any plugin suggestions?

For now, the tests will not pass.
Can you activate the CI @mcollina?
I identified some stuff to fix, but a merge doesn't involve official communication, and it would allow others to contribute.

@fastify/collaborators
A code review would be appreciated.

From metcoder95, regarding the doc:

It will be nice here to develop a bit more about the methodology or decisions made that lead to this repository; that backstory sometimes helps companies to decide wether or not to adopt a given technology (I've faced that in the past)

OK, but it would be nice if, even if I'm the one who suggested it, other developers could share their perspectives.

I fixed the CI: https://github.com/jean-michelet/demo/actions/runs/9722290349/job/26835992622
Waiting for the merge or further review before continuing on this.

Maybe just set a wildcard to ignore everything under scripts/*

Don't understand how to it.
I'm having rather a hard time with the Tap documentation, if someone would be kind enough to copy/paste the solution for me, I've spent too much time on it already.

I worked locally to add a rate limiter, but I think we should merge this before, otherwise I'll make your reviews obsolete.
@mcollina

@Fdawgs you are now blocking the merge (request for change) ;). Is there still something we need to fix?

Ah no problem, thanks for your heads up.

Nice. It's approved! 🙏🎉. Well done @jean-michelet

Can it be merged plz?
I would like to continue.


add select property

Hello. There was a linting issue with your PR (missing semicolon), however I see you've closed it.


chef apache error in chef-client

================================================================================
Error executing action start on resource 'service[httpd]'
================================================================================
Mixlib::ShellOut::ShellCommandFailed
------------------------------------
Expected process to exit with [0], but received '1'
---- Begin output of /usr/bin/systemctl --system start httpd ----
STDOUT:
STDERR: Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
---- End output of /usr/bin/systemctl --system start httpd ----
Ran /usr/bin/systemctl --system start httpd returned 1

Resource Declaration:
---------------------
# In /var/chef/cache/cookbooks/apache/recipes/default.rb

 34: service "httpd" do
 35:        supports [:restart, :reload, :status]
 36:        action [:enable, :start]
 37: end
 38:

Compiled Resource:
------------------
# Declared in /var/chef/cache/cookbooks/apache/recipes/default.rb:34:in `from_file'

service("httpd") do
  action [:enable, :start]
  supports {:restart=>true, :reload=>true, :status=>true}
  retries 0
  retry_delay 2
  default_guard_interpreter :default
  service_name "httpd"
  enabled true
  pattern "httpd"
  declared_type :service
  cookbook_name "apache"
  recipe_name "default"
end

Platform:
---------
x86_64-linux

Running handlers:
[2016-07-30T14:47:07+00:00] ERROR: Running exception handlers
Running handlers complete
[2016-07-30T14:47:07+00:00] ERROR: Exception handlers complete
Chef Client failed. 0 resources updated in 07 seconds
[2016-07-30T14:47:08+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
[2016-07-30T14:47:08+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2016-07-30T14:47:08+00:00] ERROR: service[httpd] (apache::default line 34) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of /usr/bin/systemctl --system start httpd ----
STDOUT:
STDERR: Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
---- End output of /usr/bin/systemctl --system start httpd ----
Ran /usr/bin/systemctl --system start httpd returned 1
[2016-07-30T14:47:08+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

You will need to debug it and figure out why apache2 gave an error exit
status. See "systemctl status httpd.service" and "journalctl -xe" for
details.


Uncaught SyntaxError: Unexpected token /

[Enter steps to reproduce below:]

...
...

Atom Version: 0.186.0
System: Mac OS X 10.10.2
Thrown From: sass-autocompile package, v0.3.1
Stack Trace
Uncaught SyntaxError: Unexpected token /
At file:///Applications/Atom.app/Contents/Resources/app/static/index.html?loadSettings=%7B%22locationsToOpen%22%3A%5B%7B%22pathToOpen%22%3Anull%7D%5D%2C%22bootstrapScript%22%3A%22%2FApplications%2FAtom.app%2FContents%2FResources%2Fapp%2Fsrc%2Fwindow-bootstrap.js%22%2C%22resourcePath%22%3A%22%2FApplications%2FAtom.app%2FContents%2FResources%2Fapp%22%2C%22devMode%22%3Afalse%2C%22safeMode%22%3Afalse%2C%22appVersion%22%3A%220.186.0%22%2C%22shellLoadTime%22%3A174%2C%22initialPaths%22%3A%5B%5D%7D:1

SyntaxError: Unexpected token /
  at Object.parse (native)
  at /Users/lasserafn/.atom/packages/sass-autocompile/lib/sass-autocompile-view.coffee:158:38
  at ChildProcess.exithandler (child_process.js:756:5)
  at ChildProcess.emit (events.js:119:17)
  at maybeClose (child_process.js:1013:16)
  at Socket.<anonymous> (child_process.js:1181:11)
  at Socket.emit (events.js:116:17)
  at Pipe.close (net.js:477:12)

Commands
  2x -0:28.8 core:save (atom-text-editor.editor.is-focused)
     -0:27.5 core:backspace (atom-text-editor.editor.is-focused)
  4x -0:27.3 core:save (atom-text-editor.editor.is-focused)
     -0:03.9 core:move-right (atom-text-editor.editor.mini)
     -0:03.8 core:move-left (atom-text-editor.editor.mini)
  3x -0:03.5 core:move-right (atom-text-editor.editor.mini)
     -0:03.0 core:select-right (atom-text-editor.editor.mini)
     -0:02.7 core:confirm (atom-text-editor.editor.mini)
     -0:01.1 core:save (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "themes": [
      "seti-ui",
      "seti-syntax"
    ],
    "disabledPackages": [
      "atom-bootstrap3"
    ]
  },
  "sass-autocompile": {}
}

Installed Packages
# User
angularjs, v0.2.0
atom-beautify, v0.21.4
atom-handlebars, v0.4.0
autocomplete-plus, v2.4.1
color-picker, v1.4.4
emmet, v2.3.4
language-SCSS, v0.2.0
language-spacebars, v0.2.2
less-autocompile, v1.0.0
less-than-slash, v0.3.4
linter, v0.12.0
meteor-api, v2.12.0
minimap, v4.5.0
pretty-json, v0.3.2
project-manager, v1.15.5
sass-autocompile, v0.3.1
seti-syntax, v0.3.3
seti-ui, v0.6.3

# Dev
No dev packages

Thanks for you report!
I improved the error handling a lil' bit, so the exception you posted should not occur any more.
But have a look at the requirements. Have you installed node.js and node-sass (global installation)?

Thanks you!
Yes I have used the command to install (-g), but I can try reinstalling :-)


Support Google account to log in.

Cannot support Google account. When we choose "Log in with Google", it will open a new window to log in. We cannot log in Google in the original iframe.


Coda Daemon crashed multiple times: error: could not lock config file /home/ubuntu/.gitconfig: File exists

I just tried newly updated one to run, but resulted in crashing-roop.
There were some types of error messages like below.
mina.service: Main process exited, code=exited, status=1/FAILURE
mina.service: Failed with result 'exit-code'.
could not lock config file /home/ubuntu/.gitconfig: File exists

Here is the crashing-report.
crash.zip

Closing this issue as it is stale for a long time.


Configurable sidecar log level

Describe the feature you'd like to have
Currently, we have a single configuration to configure the log level for all the containers in the csi pods, we should have 2 configurations like what we have today in Rook and cephcsi to configure the log level for the cephcsi container and Kubernetes sidecar containers
Who is the end user and what is the use case where this feature will be valuable?
This is required for the feature compatibility with existing deployments and also to avoid too verbose logs on the sidecar when not required.
How will we know we have a good solution? (acceptance criteria)
Introduce a new argument in the Log struct for the sidecar log level configurations

@Madhu-1 Beside the point that this was the way it was used in the past integration of CSI, I would like to understand why it is needed. From my perspective this is an overkill and a middle ground at the same time. and if are going that route I would prefer to have finer control in the API where we control every individual sidecar log settings

Removing the good first issue label until we have the API design discussion settled

@Madhu-1 Beside the fact that this was the way it was used in the past integration of CSI, I would like to understand why it is needed. From my perspective, this is an overkill and a middle ground at the same time. and if we are going that route I would prefer to have finer control in the API where we control every individual sidecar log settings

@nb-ohad having a sidecar log-level was the overkill, we cannot use the same log level for both the cephcsi container and the sidecar containers, Most of the time we end up having very huge logs, Ideally in most the clusters the issues happen on the cephcsi containers where the log level will be set to 5 to generate the logs and all the sidecar log level will be set to 1 to generate only error logs we don't need to have to debug logs for the sidecar containers. IMO advertizing the log level per container can be done again as I mentioned it an overkill, For example, the GRPC timeout its 1 argument common for all the sidecars. This is going to be the same.

@Madhu-1 I am not sure it is an overkill. what will happen if future changes for one of the sidecars will result in considerably bigger logs for that sidecar vs the other ones vs the operator? I would like us to design the API change in a way that allows a central control and a granular control as an overwrite


Documentation issue on dart-lang/sdk Wiki Contributing

There are some issues related to dart-lang/sdk Wiki page( https://github.com/dart-lang/sdk/wiki/Contributing ). In the coding style category Google C++ style guide link which is redirecting to the http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml is giving an 404 error that says The requested URL /svn/trunk/cppguide.xml was not found on this server.

Updated link to https://google.github.io/styleguide/cppguide.html.


Avoid downloading the whole eclipse indigo sdk

Hi Simon,
I really appreciate your work and use your gradle plugin really often. Thank you for providing it.
I have created a damn small eclipse application to use the p2 command line applications and it's just 4.8 MB instead of 180 MB for the whole indigo sdk.
You can find it here: https://dl.bintray.com/simon-scholz/eclipse-apps/eclipse-p2-minimal.tar.gz
I would be happy if you merge this feature, since many customers of us use your gradle plugin and would be happy if they won't have to configure an eclipseHome property or even download the huge indigo sdk.
Let me know if I can help with further stuff.
Best regards,
Simon

Hi Simon,
thank you very much for the PR. I hope to give it a try on Friday. It's definitely a great idea to reduce the dependency to the Eclipse artifact to something that is much smaller.
As this also changes the way a custom artifact would be configured it might break things if someone did that. I'm not sure though if that really matters (i.e. if someone used that option). Do you know if there is any substantial difference in the p2 repo generation in the different Eclipse versions? I just stuck to Indigo because that was what I used initially and I never had any problems with it.
Best,
Simon

Hi Simon,

As this also changes the way a custom artifact would be configured it might break things if someone did that. I'm not sure though if that really matters (i.e. if someone used that option).

As first approach I also created a new variable and keept the eclipseMirror variable as it was, but IMHO the "old" indigo approach shouldn't be used after this has been merged.
If someone really used the eclipseMirror property in their own build.gradle file, which I doubt, I could write it into the release notes of version 1.6.0.
I've always used the eclipseHome property, which was not really good for portability, but now with this small 4.8 MB download I could easily omit the eclipseHome property and simply download it.

Do you know if there is any substantial difference in the p2 repo generation in the different Eclipse versions?

No there isn't my minimal p2 app example is based on Eclipse Oxygen(current release) though.
I just came up with this nice commit: https://github.com/stempler/bnd-platform/pull/46/commits/faac9db2a60507a62f4299872576cae289746655 on my master branch.
It seems that it now became part of this PR. I actually intended to create a new PR with this potentialOptionalImports task.
Would you prefer that I create different branches for the upcoming features, which I rebase once you've merged my PRs or should I continue working on my master branch and you can simply merge everything?
Since I am an Eclipse Comitter I am more familiar with the Gerrit workflow, where you have a new branch for each and every commit and where merging is way easier than on GitHub.

Finally came around to do a test run with your changes and it works nicely.

It seems that it now became part of this PR. I actually intended to create a new PR with this potentialOptionalImports task.

With the workflow in GitHub it usually makes sense to create feature branches for Pull requests, then you should not have that problem.

Would you prefer that I create different branches for the upcoming features, which I rebase once you've merged my PRs or should I continue working on my master branch and you can simply merge everything?

I would prefer to have separate PRs, but we can leave it like it is for this one.
But it would be great if you can keep changes due to formatting to a minimum in future PRs, as this kind of noise makes it hard to see the relevant changes.


Github organization move

With the move to the ansible orgnaization in Github, the repo permissions needed to be reset.
Please reach out if you have any issues related to this.
thanks-
Brad (cidrblock)

@cidrblock
Could I still have permission to merge PR/close issue?

It works. Thx, @cidrblock

done


[WIP] Merge PCS and LDT

In it's current state this PR adds an initial_statement flag to the parameters and replaces the LDT prover with the regular prover, while keeping the LDT verifier. It passes for --field Field256 but fails for Goldilocks.


Create SIT request form: Request SIT button becomes active when all required fields are completed

Description
Previous to this, the Send Request button in the Storage in Transit panel was disabled 100% of the time. Now, the Send Request button becomes active once all required fields are entered, it disables if any required fields are deleted, and then becomes active again once the field is filled in again.
Setup
Add any steps or code to run in this section to help others prepare to run your code:
make server_run
make tsp_client_run

Local login using<EMAIL_ADDRESS>navigate to any shipment, scroll down to Storage in Transit (SIT) and click Request Sit
Code Review Verification Steps

[x] There are no aXe warnings for UI.
[x] This works in IE.
[x] Request review from a member of a different team.
[x] Have the Pivotal acceptance criteria been met for this change?

References

Pivotal story for this change

Screenshots
all required fields filled in

missing something

re-filled in

When filling out the form I noticed that the Send Request button is enabled as soon as I start typing into the Zip/Postal Code field. The behavior should be for the button to be active once a full, valid zip has been inputted.


switch to github pages 🥺

heroku is slow

yeah. It's an old project I did for fun with angular many years ago. I don't think I'll be updating it.


Facilitate diffing of package when reviewing Dependabot PRs that update build

What
Speed up our reviews of Dependabot pull requests that introduce a change in the build by facilitating the comparison of the built files, first locally then on CI.
Why
We need to review whether Dependabot pull requests change the package. This takes a couple of steps, and the more consistent across each other we can be in how we do this, the better.
Having it run on CI automatically would free our time and ensure that step is not missed.
Who needs to work on this
Developers
Who needs to review this
Developers
Done when
### Done when
- [ ] Add a shell script to run locally for comparing the build of a branch with that of another branch (`main` by default)
- [ ] Automate the running of that script on CI, commenting the result on the pull request

Sneaky request to keep diffs looking good with js-beautify (or Prettier) like we do in:
https://github.com/alphagov/govuk-frontend/blob/fff4f701520b1d2fe44891663c4b6509fc178916/.github/workflows/diff-change-to-dist.yaml#L29-L33

Ready for review in https://github.com/alphagov/govuk-frontend/pull/4511


Error : Property does not exist on type 'Resource'

When you use resource models and create a method which calls a resource class method like this
getDoc(selectedDay: string): IDoc {
        return this.$resource.getDoc({ selectedDay: selectedDay });
    }

I get the following error when typescript compiles the files.
 Property 'getDoc' does not exist on type 'Resource'.

similar issue when you refer to instance variables like
this.id

type script version
"typescript": "~2.0.3"

Could you please provide full resource and model source code?

Model

@ResourceModelParams({
    providers: []
})
export class Warrior extends ResourceModel {
    static resourceClass = WarriorResource;

    constructor() {
        super();
    }

    getChallenge(selectedDay: string): IChallenge {
        return this.$resource.getChallenge({ warriorId: this.warriorId, selectedDay: selectedDay });
    }
}

Resource
@Injectable()
@ResourceParams({
    url: environment.apiBase + '/api/warriors'
})
export class WarriorResource extends ResourceCRUD<IQueryInput, IWarrior, Warrior> {
    static model = Warrior;

    @ResourceAction({ isArray: false })
    query: ResourceMethod<IQueryInput, any>;

    @ResourceAction({
        method: RequestMethod.Get,
        isArray: false,
        path: '/{!warriorId}/challenges'
    })
    getChallenge: ResourceMethod<{ warriorId: number, selectedDay: string }, IChallenge>;

}

Could you please update to 1.7.1 and try to use model like that
@ResourceModelParams({
    providers: []
})
export class Warrior extends ResourceModel<WarriorResource> {
    static resourceClass = WarriorResource;

    constructor() {
        super();
    }

    getChallenge(selectedDay: string): IChallenge {
        return this.$resource.getChallenge({ warriorId: this.warriorId, selectedDay: selectedDay });
    }
}

worked thanks

Great!


Selecting fields, question

Selecting fields in $eager is possible.
Is it possible or will be possible to select fields in general on the service? Not just related fields.

It supports the $select parameter from feathers


Add gauge value metric to Choreo Metrics published

Purpose

Add gauge value metric to Choreo Metrics published

Codecov Report

Merging #23495 into observability-improvements will not change coverage.
The diff coverage is n/a.

@@                     Coverage Diff                     @@
##           observability-improvements   #23495   +/-   ##
===========================================================
  Coverage                       14.59%   14.59%
===========================================================
  Files                              51       51
  Lines                            1411     1411
  Branches                          219      219
===========================================================
  Hits                              206      206
  Misses                           1189     1189
  Partials                           16       16

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 e588d5a...4f9c937. Read the comment docs.


How to specific index path when create index?

rt

Do you mean to put index in a certain directory? If yes, you can configure it by spark.sql.oap.index.directory

@JkSelf Could we also add some related info to README?

@gczsjdy  added the usage in readme.

Resolved by #824


Elvis does not distinguish ++ operator from +

The following rules make elvis complain about a missing space b/w the ++ operator.
#{rules => [{right, ","},
            {right, "++"},
            {left, "++"},
            {right, "+"},
            {left, "+"}
           ]}}

Fixed in https://github.com/inaka/elvis_core/pull/20


Install ripple-test-tools v1.4.0 will get error of EPERM in npm 6.11.0+

Checkout npm bug: https://npm.community/t/npm-6-11-x-breaks-npm-ci-with-eperm-error-for-private-github-package/9872
At meanwhile, please switch to npm 6.10.x.

No more issue in latest Ripple(1.5.7) and npm(6.13.7).


Enhance tests for JSONBySentenceFormatter

Coverage increased (+2.04%) to 80.49% when pulling ae89f0d42ecb92b2a2eff8502a7f517c439be6ae on takahi-i:enhance-jsonformatter-tests into 4c515af415c6e659549d0d8cbdb717de3843fdb0 on recruit-tech:master.


Ignore PackageManifets resources when listing components

What type of PR is this:
/kind bug
Feel free to use other labels as needed. However one of the above labels must be present or the PR will not be reviewed. This instruction is for reviewers as well.
-->
What does this PR do / why we need it:
Prevents PackageManifets to be shown as a component in odo list output.
before
▶ odo list
 ✓  Listing components from namespace 'test' [323ms]
 NAME                             PROJECT TYPE  RUNNING IN  MANAGED
 * devfile-nodejs-deploy          nodejs        None        odo
 my-nodejs-app                    nodejs        Dev         odo
 ibm-spectrum-scale-csi-operator  Unknown       Unknown     ibm-spectrum-scale-csi-operator
 vfunction-operator               Unknown       Unknown     operator
 my-cluster-name                  Unknown       Unknown     percona-server-mongodb-operator
 snyk-operator-marketplace        Unknown       Unknown     snyk-operator-marketplace

after
▶ odo list
 ✓  Listing components from namespace 'test' [314ms]
 NAME                     PROJECT TYPE  RUNNING IN  MANAGED
 * devfile-nodejs-deploy  nodejs        None        odo
 my-nodejs-app            nodejs        Dev         odo
 my-cluster-name          Unknown       Unknown     percona-server-mongodb-operator

PackageManifet is not a resource that would represent something running on the cluster. It is a representation of a record in the OpenShift catalog as such it should not be considered as a valid component.

/approve

IBM Cloud tests are passing so
/override ci/prow/v4.10-integration-e2e


some resources do not support moving

Hi, I checked here for supported resources but some of my resources are not supported, as they are in pre-view. are there any ways that I can move those resources? my resources include Azure Santa Cruz, Digital Twins, etc. Thank you.

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

ID: 51002d4a-d8de-53d1-2e78-cb0440f5f23e
Version Independent ID: 40f69d9c-2cb7-87e1-291d-525882347925
Content: Move resources to a new subscription or resource group - Azure Resource Manager
Content Source: articles/azure-resource-manager/management/move-resource-group-and-subscription.md
Service: azure-resource-manager
Sub-service: management
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@Karenzhang7717 - sorry, if the resource type does not support move, there is no direct way to move an existing instance. Your next best option is to redeploy the resource to the new resource group/subscription. You could export the template for a resource group and redeploy it in the new destination.

Thank you @tfitzmac for helping on the thread.
@Karenzhang7717 Please review the information shared by @tfitzmac and let us know if you have any further queries.
At this point it appears that there's no further edits or updates needed to the documentation. We will go ahead and close this issue, however if you have any further feedback on the document please tag us in your reply and will be happy to reopen the thread and continue the conversation. Thank you


BUG: Support for Postgres 15

The library errors as follows:
users_db_1   | 2023-01-26 17:47:59.294 UTC [76] ERROR:  permission denied for schema public at character 28
users_db_1   | 2023-01-26 17:47:59.294 UTC [76] STATEMENT:  CREATE TABLE IF NOT EXISTS "migrations_state" ("key" VARCHAR  PRIMARY KEY NOT NULL UNIQUE, "value" TEXT  NOT NULL, "run_on" T
IMESTAMP  NOT NULL)
turnstile_1  | [ERROR] unhandledRejection
turnstile_1  | [ERROR] error: permission denied for schema public
turnstile_1  |     at Parser.parseErrorMessage (/opt/app/node_modules/pg-protocol/dist/parser.js:287:98)
turnstile_1  |     at Parser.handlePacket (/opt/app/node_modules/pg-protocol/dist/parser.js:126:29)
turnstile_1  |     at Parser.parse (/opt/app/node_modules/pg-protocol/dist/parser.js:39:38)
turnstile_1  |     at Socket.stream.on (/opt/app/node_modules/pg-protocol/dist/index.js:11:42)
turnstile_1  |     at emitOne (events.js:116:13)
turnstile_1  |     at Socket.emit (events.js:211:7)
turnstile_1  |     at addChunk (_stream_readable.js:263:12)
turnstile_1  |     at readableAddChunk (_stream_readable.js:250:11)
turnstile_1  |     at Socket.Readable.push (_stream_readable.js:208:10)
turnstile_1  |     at TCP.onread (net.js:601:20)
turnstile_1  | npm ERR! code ELIFECYCLE
turnstile_1  | npm ERR! errno 1
turnstile_1  | npm ERR<EMAIL_ADDRESS>migrate: `db-migrate "up"`
turnstile_1  | npm ERR! Exit status 1
turnstile_1  | npm ERR!
turnstile_1  | npm ERR! Failed at the<EMAIL_ADDRESS>migrate script.
turnstile_1  | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
turnstile_1  |
turnstile_1  | npm ERR! A complete log of this run can be found in:
turnstile_1  | npm ERR!     /root/.npm/_logs/2023-01-26T17_47_59_320Z-debug.log

This error comes from an update in postgres 15 which requires updates to the public schema to be done by a user with particular explicitly-set permissions. Article / postgres documentation.
Stepping back to Postgres 14 fixes this issue but isn't a great long term solution.

feel free to shoot by a PR to fix this, am not on the matter yet what exactly changed in PG 15.

as far as i can see this is a permission problem. not a driver one. closing for now


Hyperlink DOIs to preferred resolver

Same as https://github.com/common-workflow-language/common-workflow-language/pull/827 ;-)

Thanks!

You're welcome, and thanks for merging :-)


Fix: Fixed possible System.NullReferenceException in ThemeHelper

Resolved / Related Issues

[x] Were these changes approved in an issue or discussion with the project maintainers? In order to prevent extra work, feature requests and changes to the codebase must be approved before the pull request will be reviewed. This prevents extra work for the contributors and maintainers.
Closes #issue...

Validation
How did you test these changes?

[ ] Did you build the app and test your changes?
[ ] Did you check for accessibility? You can use Accessibility Insights for this.
[ ] Did you remove any strings from the en-us resource file?

[ ] Did you search the solution to see if the string is still being used?

[ ] Did you implement any design changes to an existing feature?

[ ] Was this change approved?

[ ] Are there any other steps that were used to validate these changes?

Open app ...
Click settings button ...

Screenshots (optional)

https://github.com/files-community/Files/blob/c51f7a4f81f48a2cc930266828ed4bcf336ec131/src/Files.App/Helpers/ThemeHelper.cs#L46-L52
If currentApplicationWindow is null, a NullReferenceException may occur at line 52.

@hishitetsu thanks!


Organize data by variable rather than month?

In the Theme 2 meeting today @bsulman said that it might be more intuitive/useful for his workflows to have data organized by variable rather than month.
Something to consider for version 2 perhaps

I think this would be really helpful for data users, thanks!


Get some more information from a video

Hi, I needed to be able to get some more informations from a video.
Example :

view_count
like_count
dislike_count
repost_count
average_rating

I added the fields in the mapping class, also some getters and I updated a test class accordingly.
I also updated you README.md with the Maven way of importing your project.
Maybe you'll find that interresting enough to merge.
Regards and thanks for your work.

I forgot to update version in pull request. Now, done.


Make sure not to do same transactions multiple time during deploy

In the new-deploy we have multiple calls which are used several times during deployment. For instance enrollWatchers, is reused 2 times, in: enrollCores and enrollRemotes. Before making a transaction we should first make some checks that the job won't be done twice (hence gas paid twice).

do we have more specific examples? this one is fixed in 2013d53. Any others should be considered bugs at this point

@prestwich  Same with enrollGovernanceRouter. That must be it for now

closed by https://github.com/nomad-xyz/monorepo/pull/142


pyprland: 2.2.12 -> 2.2.15

Description of changes

Update pyprland: 2.2.12 -> 2.2.15
Changelog: https://github.com/hyprland-community/pyprland/compare/2.2.12...2.2.15
Add johnrtitor as maintainer

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 308345 run on aarch64-linux 1

2 packages built:

pyprland
pyprland.dist

@NixOS/nixpkgs-merge-bot merge


Add watchOS to podspec

This pull request adds watchOS to the podspec file so that the pod can be used on those devices.

The build failure looks unrelated to this PR.  I'm going to approve it and merge it anyway.


[D1 Retro]: Team Dynamics

Team Dynamics of D1
Areas done well

Areas of improvement:

Team Dynamics of D1
Areas done well

check on one another progression
fast response to each other's queries

Areas of improvement:

make all the team members involve in every discussion
more discussion among one another

Team Dynamics of D1
Areas done well

everyone try their best to be active

Areas of improvement:

no more last minute work

Team Dynamics of D1
Areas done well

good cooperation among team members

Areas of improvement:

every team member update project board consistently

Completed on 4/3/2023


Fix typo and delete unnecessary spaces

typo: Github -> GitHub
delete unnecessary spaces: As Markdown syntax, there was a large amount of half-width spaces that did not affect the display, so I deleted it

@changeworld : Thanks for your contribution! The author, @David-Noble-at-work, has been notified to review your proposed change.

@TrishaMc : Thanks for your contribution! The author, @David-Noble-at-work, has been notified to review your proposed change.

Verified editorial fix and layout in GitHub.


spack-stack release 1.5.1

Is your feature request related to a problem? Please describe.
We are planning a spack-stack release towards the end of the month (October 2023), which will be rolled out over a few days into early November. A project board was created for the release to capture all the PRs that go into there. So far, we've been trying to merge all changes into develop and release/1.5.1 in parallel (cherry-picking), but we should do a final merge of the release/1.5.1 branches (which were created from the release/1.5.0 branches) back into develop after the release.
Below is the checklist:

[x] Finalize code updates for release 1.5.1, except any potential site config updates and documentation updates

Project board: https://github.com/orgs/JCSDA/projects/4

[x] Roll out release, potential site config updates go back into the release branch

[x] Hercules (@climbfuji): /work/noaa/epic/role-epic/spack-stack/hercules/spack-stack-1.5.1/envs/unified-env

[x] https://github.com/JCSDA/spack-stack/pull/849

[x] Orion (EPIC) /work/noaa/epic/role-epic/spack-stack/orion/spack-stack-1.5.1 (@ulmononian)
[x] Discover (@climbfuji) /gpfsm/dswdev/jcsda/spack-stack/spack-stack-1.5.1/envs/unified-env

[x] https://github.com/JCSDA/spack-stack/pull/853

[x] Casper (@climbfuji) /glade/work/epicufsrt/contrib/spack-stack/casper/spack-stack-1.5.1/envs/unified-env

[x] https://github.com/JCSDA/spack-stack/pull/855

[x] Cheyenne (EPIC) last supported release on Cheyenne is 1.5.0
[x] Derecho (EPIC JCSDA this time because of https://github.com/JCSDA/spack-stack/issues/835)

[x] https://github.com/JCSDA/spack-stack/pull/853

[x] Acorn (EMC) @AlexanderRichert-NOAA

[x] https://github.com/JCSDA/spack-stack/pull/853

[x] Gaea C4 (@ulmononian) /lustre/f2/dev/wpo/role.epic/contrib/spack-stack/c4/spack-stack-1.5.1/envs/unified-env

[x] https://github.com/JCSDA/spack-stack/pull/855

[x] Gaea C5 (@climbfuji) /lustre/f2/dev/wpo/role.epic/contrib/spack-stack/c5/spack-stack-1.5.1/envs/unified-env

[x] https://github.com/JCSDA/spack-stack/pull/853

[x] Hera (@RatkoVasic-NOAA) /scratch1/NCEPDEV/nems/role.epic/spack-stack/spack-stack-1.5.1

[x] https://github.com/JCSDA/spack-stack/pull/855

[x] Jet (@RatkoVasic-NOAA) /mnt/lfs4/HFIP/hfv3gfs/role.epic/spack-stack/spack-stack-1.5.1

[x] https://github.com/JCSDA/spack-stack/pull/855

[x] Narwhal (@climbfuji)

[x] https://github.com/JCSDA/spack-stack/pull/853

[x] Nautilus (@climbfuji)

[x] https://github.com/JCSDA/spack-stack/pull/853

[x] S4 (@climbfuji) /data/prod/jedi/spack-stack/spack-stack-1.5.1/envs/unified-env

[x] https://github.com/JCSDA/spack-stack/pull/853

[x] Parallel Works (JCSDA installations; @climbfuji) /contrib/spack-stack/spack-stack-1.5.1/envs/unified-env

[x] AWS
[x] Azure
[x] Gcloud
[x] https://github.com/JCSDA/spack-stack/pull/855

[ ] Parallel Works (EPIC installations; @natalie-perlin)

[ ] AWS
[ ] Azure
[ ] Gcloud

[x] AWS ParallelCluster (@climbfuji): /mnt/experiments-efs/skylab-v7/spack-stack-1.5.1/envs/unified-env

[x] https://github.com/JCSDA/spack-stack/pull/853

[x] AWS Single-node AMI (@climbfuji) in progress

[x] https://github.com/JCSDA/spack-stack/pull/855

[x] JEDI CI containers (@climbfuji )

[x] intel-impi: uploaded with test tag to AWS ECR JCSDA-NOAA us-east-1 / JCSDA-USAF us-east-2
[x] gnu-openmpi: uploaded with test tag to AWS ECR JCSDA-NOAA us-east-1 / JCSDA-USAF us-east-2
[x] clang-mpich: uploaded with test tag to AWS ECR JCSDA-NOAA us-east-1 / JCSDA-USAF us-east-2
[x] https://github.com/JCSDA/spack-stack/pull/855

[x] Final documentation updates
[x] Tag spack, revert special changes in spack-stack (.gitmodules and container recipes), tag spack-stack
[x] Create release notes and publish release
[x] Merge release branches back into develop/jcsda_emc_spack_stack: created follow-up issue to track this #861

Completed


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_de32q0hl7o/clone/recipe/meta.yaml:16: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_de32q0hl7o/clone/recipe/meta.yaml:21: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_de32q0hl7o/clone/recipe/meta.yaml:28: missing_imports_or_run_test_py: Python packages require imports or a python test file in tests.
ERROR: /tmp/abs_de32q0hl7o/clone/recipe/meta.yaml:28: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: /tmp/abs_de32q0hl7o/clone/recipe/meta.yaml:34: missing_documentation: The recipe is missing a doc_url or doc_source_url
ERROR: /tmp/abs_de32q0hl7o/clone/recipe/meta.yaml:34: missing_dev_url: The recipe is missing a dev_url
ERROR: /tmp/abs_de32q0hl7o/clone/recipe/meta.yaml:34: missing_license_family: The recipe is missing the about/license_family key.
WARNING: /tmp/abs_de32q0hl7o/clone/recipe/meta.yaml:34: missing_description: The recipe is missing a description
Errors were found


bug: gitsigns is broken when I open a file first time in splitting window in oil.nvim

Did you check the docs and existing issues?

[X] I have read the docs
[X] I have searched the existing issues

Neovim version (nvim -v)
0.8.2
Operating system/version
MacOS 12.4
Describe the bug
I found that if I open the file for the first time, which means this file does not be opened by any buffer before, in the splitting window inoil.nvim, gitsigns.nvim could not show the difference normally.  I am not sure whether should I report this issue to gitsigns.nvim or oil.nvim.
By the way, I use neovim in iterm2(v3.4.19)
Thanks a lot !!!
I made a video to clearly describe this issues.
https://user-images.githubusercontent.com/70478084/212789229-94a11963-e52f-4e0a-bdb8-bf1f5286fb6b.mp4
Steps To Reproduce

git init
git add .
nvim -u repro.lua
:Oil
 to open a file in the splitting window
enter new lines or characters

Expected Behavior
gitsigns.nvim should show the difference in the file in splitting window.
For example,

Directory structure
No response
Repro
-- save as repro.lua
-- run with nvim -u repro.lua
-- DO NOT change the paths
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "runtime", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    "git",
    "clone",
    "--filter=blob:none",
    "--single-branch",
    "https://github.com/folke/lazy.nvim.git",
    lazypath,
  })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  {
    "stevearc/oil.nvim",
    config = function()
      require("oil").setup({
        -- add any needed settings here
      })
    end,
  },
  {
    "lewis6991/gitsigns.nvim",
    config = function()
      require("gitsigns").setup({
        -- add any needed settings here
      })
    end,
  },
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

Did you check the bug with a clean config?

[X] I have confirmed that the bug reproduces with nvim -u repro.lua using the repro.lua file above.

Thanks for the thorough repro! Made it easy to figure out what's going on.
Oil sets some window options when it opens, and one of those is signcolumn=no. We were restoring the previous window options when you left the oil buffer, but if you split the window it would clone the window options, but not the restore behavior. So the split window was getting stuck as signcolumn=no when you edited a file, and that was causing the gitsigns to not show up. Should be fixed now!


Cannot load the existing products

Hi i have in my main.ts
import *  as purchase from "nativescript-purchase";
(global as any).purchaseInitPromise = purchase.init(["xydGameCoin"]);
Then a servcie that loads the products
import *  as purchase from "nativescript-purchase";
import { Product } from "nativescript-purchase/product";
public loadProducts(){
return new Promise(()=>{
purchase.getProducts().then((products: Array) => {
products.forEach((product: Product) => {
console.log('HEEEEEERRREEREREREEE'+product.productIdentifier);
console.log(product.localizedTitle);
console.log(product.priceFormatted);
            });

        });
    });

}

But this block of code never gets the products from the google play store. I am missing something here ? do i have to create a file with the google store key or something?
Before hand thank you.

Hey @ebalestrini , from what I see you are not checking the promise that you have put in the global object, so probably the plugin is not fully initialized when you call you code. So try to use (global as any).purchaseInitPromise.then(() => loadProducts());

No further response so closing this one for now. In case you still have problems, please provide more details.

I have resolve this issue by doing some research; I found this:
This plugin will NOT work if you are running the app under the following scenarios:

In an emulator (generally google services are disabled.)
Without signature in a normal phone
In a phone that has not enabled google payments on the google play store.
Then how did i make it run?

Created a release version (--aab) signed and publish it to an alpha version in the play store.
Release it Install in from the google play tester's page Only then the plugin worked fine.


Fix: server rendering by checking document and window object are defined

Server side rendering was not working as the JavaScript threw the Reference Error.
Check this issue: https://github.com/Hacker0x01/react-datepicker/issues/179

+1 for this

+1

Should Tether even execute for server-side rendering? If the assumption is that Tether shouldn't even execute on the server, would it make sense to just wrap the entire file in a function that checks that document and window are defined? For example:
let Tether;
if (typeof window !== 'undefined' && typeof document !== 'undefined') {

    if (typeof TetherBase === 'undefined') {
      throw new Error('You must include the utils.js file before tether.js');
    }

    const {
      getScrollParent,
      getBounds,
      getOffsetParent,
      extend,
      addClass,
      removeClass,
      updateClasses,
      defer,
      flush,
      getScrollBarSize
    } = TetherBase.Utils;

    ...
}
```javascript

I agree. Tether should not execute on the SSR. But then if someone has used object methods like setOptions, then it would throw the error. So I think it is better to check for windows and document only when we use them.
I am fine with either option though.

An alternative of wrapping the entire file in an if condition, would be to check if window is defined at the top of utils.js:
if (typeof window === 'undefined') {
  return;
}

Since the output file is wrapped in a factory function, just the return statement would do the trick.

So after dwelling on this for a bit, I think the current implementation in this PR is fine for now since those are the only places where document and window gets called immediately due to them being inside IIFE.
Personally, I'm not completely satisfied with the solution, but it is a solution nonetheless and one that does seems to solve the issue well. Ideally, I would like to short-circuit the entire library when window and document  are undefined, but that may require some restructuring of the library.
Thanks again for your patience :+1:

@geekjuice The last solution I suggested would short-circuit the entire library without restructuring of the library.


[WIP] Simplify dependency flags to use a common set for all module types.

Fixes #1319.
Removes the --manage_closure_dependencies, --only_closure_dependencies, --closure_entry_point and --common_js_entry_module flags in favor of simplified set:

--dependencies_mode - Enum with NONE, LOOSE or STRICT as options. None is default. Loose is equivalent to the old --manage_closure_dependencies. Strict is equivalent to --only_closure_dependencies.
--entry_point - for ES6 and CommonJS moduels, this is the file path without the extension. For closure, it uses the module import syntax: goog:namespace

This change also allows the --dependency_mode flag to fully control CommonJS modules. Previously, CommonJS module dependencies implied --only_closure_dependencies and supported only a single entry point.

This branch is now fully functional - just waiting on #1341 to be merged. After that, I'll rebase this one for review. I'd also like to ping @nicks to make sure these changes work for his use as well.

I believe all the review items have been addressed. I did not want to define the behavior when the old flags and these new flags are used together, so I marked the old flags with a forbids option. However that requires updating our args4j version so #1350 will need merged first.
From @mprobst

We should clearly communicate what order of files users can expect, and maybe also make sure that we get repeatable file-ordering results between different runs, even if there's no defined total order of files (e.g. unrelated siblings).

I agree - but this may need to be handled on the wiki as it's a bit hard to document in a flag. We have an entire page that will need updated related to the manage closure dependencies flags.  Order is even trickier with --dependency_mode=LOOSE as files that do not have dependency information should retain their relative order. We haven't documented this well to date.

Some nits, LGTM otherwise.

Review items fixed and rebased to the top of the tree for Travis fixes. Should be gtg.
Also, @nicks weighed in via email:

Malte designed the Closure Compiler / CommonJS  system many years ago. It was very exploratory/experimental, and had very different goals than the goals we have now. (I may be misremembering, but i think he wanted the Closure Compiler to preserve the module structure -- so that if there were N inputs, there'd be N outputs, but with dead code removed and code moved into later modules when possible). I think it'd be reasonable to change the design.

Also, since #1350 isn't mergable, it no longer requires args4j to be updated first.

Rebased and fixed tests now that #1348 was merged.

Awesome!!!

I've updated the documentation to reflect this merge: https://github.com/google/closure-compiler/wiki/Managing-Dependencies

Hi Chad. Unfortunately, we rely on setClosureEntryPoints internally. I may rollback now and then rollforward once we get this sorted out.
Is there a straightforward mapping from the namespace name to the new entry point format?

@blickly I was worried about just this when @mprobst suggested it. Yes there is a very simple mapping - let me get a PR ready.

Sorry if I caused trouble here, I wasn't aware of that.

No problem. The separate command line runners cause some friction occasionally. MOE is improving so it should be easier to deal with this kind of thing soon.

@mprobst I think it was the right thing to do. I'm re-adding the setClosureEntryPoints method with the hope that it can eventually be removed.

@blickly #1415 should fix this. But I don't have a good way to test it myself.

Thanks Chad! I'll rollforward a version of this PR that includes that change.


bad HTTP: 403

I get the following error when I try to run the portable version:
letskencrypt: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 403
I also had to disable IPv6 since letskencrypt initially tried to connect via an IPv6 address.
I also made some changes to the code since it would not compile on my Debian.
In extern.h, I changed
include <bsd/stdlib.h>
include </bsdstring.h>
to
include <stdlib.h>
include <string.h>
BDW, the latter above is the correct way to include the standard header files.
I also changed main.c to use argv[0] instead of the BSD only 'getprogname()'.

letskencrypt-portable needs libbsd for Linux systems.  It seems that this ran away from my README file--I'll re-add it, thanks!  However, I can't do much about your IPV6: it's being returned as a valid address, so you probably need to fix your system.  (I'm sure other systems will also pull down IPV6 addresses...)
As for the 403, the newest version will dump the output buffer from the server when it encounters are 403.  It usually means that you're using an unknown account key.


Have problem in downloading apps

Hi my dear Madam or Sir
First of all, I'd like to give you all my love and thanks for your great job. Please accept my endless gratitude. ❤⚘🙏
I would be grateful if you could teach and show me how to download apps on your outstanding website. Please send your expert advice to my email. I'm looking forward to learning the processes needed to know to be able to download apps on your website. It is really complicated to download apps on your astonishing game changer website. Please make it easier to download apps on your website.
Sincerely

I'm looking forward to seeing your email with your easy way of teaching me on how to download in your amazing website. Make it easier please. Thanks a million my dear. Love you all 🙏⚘❤🌻🌿☘🍀


small changes

Fixes #
Proposed Changes

Any background context you want to provide?

Can one of the admins verify this patch?


Missing Biomes

Not sure this is still being maintained, but I've found it to be a wonderful tool to find out where I'm missing science.   Anyways, in the hope that it still is, I've noticed that there is a number of missing science biomes relating to the Kerbin space complex.   Basically what currently exists but with the "flying low" monkier attached.  E.g. flying low over launchpad, flying low over crawlerway, flying low over VAB, etc, etc.
Here is a link my save file -
http://s000.tinyupload.com/index.php?file_id=00463017414630875635


Ability to export a specific subject

Add an option to the Export Builder for export data from the current subject (B, C, D, E, F, G or H).
Should be a checkbox so it can be combiled with Everything and Selected Gesture.

Better yet, make it an Entry (textbox) where the user can list patterns to match the filenames against, so you can select subjects, trials or a combiantion of them.
(eg. if Entry has the content "B,D" it should get all trials by B and D; if Entry has the content "B001, B002" then retrieve B's first and second trial; if Entry has the content "005", get everyone's last trial; etc)

Filename filter that fulfils the aforementioned behaviour is implemented and added to the Export Builder's Magnitude section in issue a03daa403c6c2542c995638f7cc549d48cbcb07c.


Added integration test cases for Dedicated namespace scenarios

Test cases:
Test case 1 - Set "dedicated" to true, make sure that the domains deployed in the operator's namespace come up
Test case 2 - Set "dedicated" to true, set the domainNamespaces to something that does not contain the operator's namespace. make sure that the domains in the operator's targetNamespaces do not come up (because when dedicated is set to true, the operator's domainNamespaces value is ignored).
Test case 3 - Run scaling the cluster with "dedicated" set to true
4.    Negative tests

The CRD is not present or is deleted, verify that Operator fails with error
The CRD is present but is a lower than expected version, verify that Operator fails with error

@hzhao-github update the PR with latest jenkins results when you have them clean


Rely on the NATS cluster connection status when reporting the Eventing CR status

Description
Rely on the NATS cluster connection status when reporting the Eventing CR status.
Related issue(s)

https://github.com/kyma-project/eventing-manager/issues/267.

/hold

Remaining tasks:

[ ] Fix existing tests.
[ ] Add more tests if needed.

/hold cancel


Could someone update the ValveResourceFormat version and release?

ValveResourceFormat has been updated to 0.0.13 which contains a critical change that I need for my usage of this tool. Could someone update to the new version and release an update of this tool? Thanks!

Not sure what changes you needed, but there's been multiple releases since then.


The C# Sample in "Comparison: Automated Retry After an Exception"

The C# Sample in "Comparison: Automated Retry After an Exception" doesn't appear to be properly formatted.

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

ID: d90f60ed-891b-151d-c963-522a1b0b1c17
Version Independent ID: f9ab9cef-beda-06fb-c5c0-dce07969fbd5
Content: X++ and C# comparison - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/dev-itpro/dev-ref/xpp-cs-comparison.md
Service: dynamics-ax-platform
GitHub Login: @RobinARH
Microsoft Alias: robinr

Thanks for this feedback! I have updated the formatting and the changes will be published soon.


May I ask which file is the code for the implementation of bounding box augmentations?

Is it in the AnchorAugHead.py file?

Another question is what does the gt_bboxes in the fwd function parameter in the entire model file represent?
The last question is whether the bounding box enhancement method in your paper is enhanced based on the bounding box of the cropped foreground image, and is the RPN-based two-stage method used to obtain more prospals? In fact, I just want to know what to enhance to get so many prospals, if it is based on RPN, it is only suitable for the two-stage target detector.

@limbo0000


Remark on Prompt Flow is misleading

Please provide us with the following information:

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

Minimal steps to reproduce
Any log messages given by the failure
Expected/desired behavior
Understanding of how Prompt Flow could/could not be an alternative to the backend in the app.py
OS and Version?
Versions
Mention any other details that might be useful
In the "When should you use this repo?" section of the README.MD it is written that "If you need to customize your scenario beyond what Azure OpenAI on your data offers out-of-the-box, use this repository" and "If you don't require customizations" then "use Azure Machine Learning prompt flow".
But if you want to customize your scenario beyond the "Azure OpenAI on your data" solution then Prompt Flow is an option, right? It would be really helpful if the documentation could explain how PromptFlow is an alternative to the code in the app.py in this solution.

This is related to #915

This issue is solved


Bump Spark version to 2.1.0

Upgrades Spark version to 2.1.0, (related https://github.com/hazelcast/hazelcast-spark/issues/4)
Since Spark is built with Scala 2.11 starting with version 2.0, Scala version is also upgraded to 2.11.8

verify

Build passed. (https://hazelcast-l337.ci.cloudbees.com/job/Spark-pr-builder/8/)

👍


Get engine application info with interval

Why are the changes needed?

To prevent frequent call to resource manager.
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Codecov Report

Merging #4780 (09f67c6) into master (94c7273) will increase coverage by 0.00%.
The diff coverage is 27.77%.

@@            Coverage Diff            @@
##             master    #4780   +/-   ##
=========================================
  Coverage     57.92%   57.92%
  Complexity       13       13
=========================================
  Files           581      581
  Lines         32437    32459   +22
  Branches       4313     4313
=========================================
+ Hits          18788    18803   +15
- Misses        11837    11840    +3
- Partials       1812     1816    +4

Impacted Files
Coverage Δ

...ain/scala/org/apache/kyuubi/engine/EngineRef.scala
68.88% <27.77%> (-1.89%)
:arrow_down:

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

Thanks, merged to master


Remove unnecessary parentheses around if statements.

This will make newer flake8 happy.

LGTM, not sure why noetic is failing

Ah, I made a mistake when I opened it and opened the PR against the master branch.  That kicked off the Noetic build, but it won't possibly work; this code is all for ROS 2.  So we can safely ignore that.

CI:

Linux
Linux-aarch64
Windows


vim should not warn about unsaved content when opening stdin in readonly mode

The following should exit without a prompt:
shuf /usr/share/dict/words -n 200 | vim +"set readonly" -
:q<CR>

but currently throws error 37:
E37: No write since last change (add ! to override)

On 2019-01-04, Mahmoud Al-Qudsi wrote:

The following should exit without a prompt:
shuf /usr/share/dict/words -n 200 | vim +"set readonly" -
:q
but currently throws error 37:
E37: No write since last change (add ! to override)

Readonly or not, it's still true that the buffer has not been
written since it was last changed.  You would see the same message
if you ran view (or "vim -R" or "vim +'set readonly'"), made changes
to the buffer, and tried to exit with :q.
I have the following in my vimrc to avoid this problem.
" Fix the problem where when vim reads from stdin, it marks the
" buffer as modified so that you have to quit with :q!.
"
autocmd StdinReadPost * set nomodified

Regards,
Gary

Right, this works as intended.  Vim doesn't know whether the input can be discarded without losing valuable data.


Do not convert --test_filter a.py to a::py

Currently, if you try to filter a test target to a file with --test_filter some_test.py,
the shim converts it to some_test::py and deselects all test cases.

To test this change, in our workspace's MODULE.bazel, I added
git_override(
    module_name = "caseyduquettesc_rules_python_pytest",
    remote = "https://github.com/Benchling-Open-Source/rules_python_pytest.git",
    commit = "727a5037ec5b743ac2ffa52bbdd6968b427954be",
)

and ran
$ bazel test //tests/unit/some_target --test_filter some_test.py --test_output streamed
and confirmed that only the tests in some_test.py ran

wow, so fast! released already too! thanks!


[SPARK-36531][SPARK-36515][PYTHON] Improve test coverage for data_type_ops/* and groupby.

What changes were proposed in this pull request?
This PR proposes improving test coverage for pandas-on-Spark data types & GroupBy code base, which is written in data_type_ops/*.py and groupby.py separately.
This PR did the following to improve coverage:

Add unittest for untested code
Fix unittest which is not tested properly
Remove unused code

NOTE: This PR is not only include the test-only update, for example it includes the fixing astype for binary ops.
pandas-on-Spark Series we have:
>>> psser
0    [49]
1    [50]
2    [51]
dtype: object

before:
>>> psser.astype(bool)
Traceback (most recent call last):
...
pyspark.sql.utils.AnalysisException: cannot resolve 'CAST(`0` AS BOOLEAN)' due to data type mismatch: cannot cast binary to boolean;
...

after:
>>> psser.astype(bool)
0    True
1    True
2    True
dtype: bool

Why are the changes needed?
To make the project healthier by improving coverage.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Unittest.

Test build #142945 has started for PR 33850 at commit 07adc13.

Test build #142945 has finished for PR 33850 at commit 07adc13.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/142945/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47446/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47446/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47446/

Test build #142967 has started for PR 33850 at commit c429108.

Test build #142967 has finished for PR 33850 at commit c429108.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47466/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/142967/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47466/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47466/

Test build #143009 has started for PR 33850 at commit 429c0e1.

Test build #143009 has finished for PR 33850 at commit 429c0e1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47511/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47511/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143009/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47511/


Add storage provider contabo.com

Contabo seems to have a good offer. I tested it and it works perfectly!
This PR contains the instructions.

This is great! I wasn't familiar with them. Thank you for testing it out and going through the effort of documenting it,

For some reason the markdown parser doesn't like my style. My local build does not have this issue 😥

Super weird, it looks fine locally for me too! I guess the production rendering of Markdown uses different rules.  I went ahead and just moved the colons and it seems to be happier with that.

fine, thank you!


More banner fixes

Restore original banner (search box etc)
Make version banner dismissable
Better CSS styling

@SchrodingersGat looks very professional now. Kind of like Django's website


spork/fmt/format-print does not align elements in quoted tuples

Elements of quoted tuples are not left-aligned when passed through format-print:
repl:2:> (spork/fmt/format-print "'(:a\n:b\n:c)")
'(:a
   :b
   :c)

Elements of bracket tuples become aligned:
repl:3:> (spork/fmt/format-print "[:a\n:b\n:c]")
[:a
 :b
 :c]

May be this is intentional?
If so, I would like to understand why.  Any hints?

I've only glanced at the code but I don't think it's intentional; it's just there's no code at the moment that detects whether a form is quoted (and so is to be treated like a bracketed tuple). I think it would be cool if this were added, though.

I've only glanced at the code but I don't think it's intentional; it's just there's no code at the moment that detects whether a form is quoted (and so is to be treated like a bracketed tuple). I think it would be cool if this were added, though.

Some speculation is that the current implementation allows the use of parens in the construction of code inside macros while having indentation more suited to code.
If constructing "data" that isn't really representing code, perhaps it's better to just use square bracket tuples and get an alternate indentation style.
If these points summarize the current situation, it seems worth spelling this out somewhere.  May be it is already?

Some speculation is that the current implementation allows the use of parens in the construction of code inside macros while having indentation more suited to code.
If constructing "data" that isn't really representing code, perhaps it's better to just use square bracket tuples and get an alternate indentation style.
If these points summarize the current situation, it seems worth spelling this out somewhere.  May be it is already?

It's been a while, but nothing has change so I will answer this.
fmt treats any tuple with parens and the first element on it's own line as a "block" form, like do - (well, any form that doesn't start with another recursive data structure). And yes, we don't try and deduce from other contextual information like the quote that this is not a piece of code.

Thanks for the explanation.


Change visual item in hotbar after swapping away from scope.

Description
Hello,
I have models where the scope is seperated completly and run a different cusotom model data.
This means I use the same model/scope for different weapons.
If I hold a weapon, scope in (model is now changed to scope), then change to different id in hotbar. 1,2,3,4 whatever.
Then the gun remains on the scope model until the player goes back over it.
Would be nice that if you scope in, change hotbar or whatever. Then the gun changes back to it's original state.
It's a visual thing. But would be nice to have.
Thanks.
Configuration
Not needed

Hmm, but it doesn't even have any visible change anywhere? Like it looks the same in the inventory still even if its scope model

It does have a visual change when it's two different models.
I don't just change the first person view with that specific gun to line up the scope that is currently on.
I change the it to a different item.

Image is showing scoped in with a gun. If I swop away from it, then it stay as a scope in my hotbar. It doesn't change back to unscoped weapon.

Possible fix: apply skin onDequip using EntityEquipmentEvent

Possible fix: apply skin onDequip using EntityEquipmentEvent

Was this added in 1.11.10?

No, these are closed as soon as they get completed

not completed


Add support for Azure Virtual Machine Scale Sets

Feature Description

One-line feature description (can be used as a release note): Add support for Azure Virtual Machine Scale Sets (VMSS).
Primary contact (assignee): @feiskyer
Responsible SIGs: sig-azure
Design proposal link (community repo): https://github.com/kubernetes/kubernetes/issues/43287
Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @brendandburns @colemickens
Approver (likely from SIG/area to which feature belongs): @brendandburns @colemickens
Feature target (which target equals to which milestone):

Alpha release target v1.10
Beta release target v1.11
Stable release target v1.12

Are you planning to introduce support for Low-Priority VMs on VMSS?
In my opinion it would enable really interesting scenarios

@danigian Yep, I think so. Let me check this after v1.10 release.

@feiskyer
Any plans for this in 1.11?
If so, can you please ensure the feature is up-to-date with the appropriate:

Description
Milestone
Assignee(s)
Labels:

stage/{alpha,beta,stable}
sig/*
kind/feature

cc @idvoretskyi

@feiskyer please fill out the appropriate line item of the
1.11 feature tracking spreadsheet
and open a placeholder docs PR against the
release-1.11 branch
by 5/25/2018 (tomorrow as I write this) if new docs or docs changes are
needed and a relevant PR has not yet been opened.

@feiskyer -- We're doing one more sweep of the 1.11 Features tracking spreadsheet.
Would you mind filling in any incomplete / blank fields for this feature's line item?

@justaugustus Already updated. Thanks

Hey there! @feiskyer I'm the wrangler for the Docs this release. Is there any chance I could have you open up a docs PR against the release-1.12 branch as a placeholder? That gives us more confidence in the feature shipping in this release and gives me something to work with when we start doing reviews/edits. Thanks! If this feature does not require docs, could you please update the features tracking spreadsheet to reflect it?

@feiskyer --
Any update on docs status for this feature? Are we still planning to land it for 1.12?
At this point, code freeze is upon us, and docs are due on 9/7 (2 days).
If we don't here anything back regarding this feature ASAP, we'll need to remove it from the milestone.
cc: @zparnold @jimangel @tfogo

Thanks for the update!

@feiskyer would you have a list of items still needed to VMSS with k8s ?

I'm about to spin up Staging clusters with 1.11.3 so I will know more in the coming weeks :)
Right now, most of my concerns are with VM Extension error handling with cluster autoscaler. But that's out of scope for here, we can take it offline :)

GA and done now. Let's close it.
/close


Referencing previous elements in v-for

I have ran into an issue while trying to inspect previous element in a list in relation to the current one. In more detail, I'm working on an event log and would like to assign a special class to the first event in the series of events generated by a user. The logic is similar to any messaging app where it creates a little arrow to the chat bubble when a user, different from the previous, sends a message. When that user again sends a message, the markup doesn't happen because its the same user:
<-- userA
 -- userA
<-- userB
 -- userB
 -- userB
<-- userC
<-- userA

It is also not a straight-forward markup. Notice the filtering and sorting. As such, I cannot simply use events[index].data.user because events is the original data source that is not filtered or sorted. Moreover, I have a factory that returns the component type to be created:

 0" class="list-unstyled event-list">

        <compoent :is="eventFactory(event)" :info="event" :class="{'event-user-change': (index === 0 || event.data.user !== events[index].data.user)}"></compoent>

What is the best approach in this case for trying to access the previous or some abstract index within the underlying dataset of the v-for operation?

You aren't going to get answers to questions here. If you have an issue with the software, as in a possible bug, then you should post it here. Otherwise, there are the gitter channel and the forum to ask questions.
Sorry for the runaround, but you're going to get this answer from Evan himself anyway, so might as well close this issue and move your question to one of the other support areas. Thanks!
https://gitter.im/vuejs/vue
http://forum.vuejs.org/
Scott

This doesn't seem like a bug, so I'm closing it - please post similar questions to the forum instead.

@ardoramor Did you find a solution for this?


Exponential backoff

As per https://cloud.google.com/storage/docs/exponential-backoff, clients should use truncated exponential backoff for all requests to Google Cloud Storage.
This has been bothering me for quite some time now.
R: @bradrydzewski

We use this plugin and this LGTM (though my LGTM doesn't count on here)

LGTM

LGTM


Logs available in Azure table update

Added Log Analytics references, corrected caps and spacing in the "type of logs available in Azure" table.

@Nalith : Thanks for your contribution! The author, @UnifyCloud, has been notified to review your proposed change.

@TomShinder  - Would you review the proposed changes? Thanks.

Thank you for the changes!

#sign-off

@TomShinder: I'm sorry - only the author of this article, @UnifyCloud, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off

@TomShinder: I'm sorry - only the author of this article, @UnifyCloud, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off

@TomShinder: I'm sorry - only the author of this article, @UnifyCloud, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off

@TomShinder: I'm sorry - only the author of this article, @UnifyCloud, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@ktoliver : Thanks for your contribution! The author, @UnifyCloud, has been notified to review your proposed change.

#close-request

#please-close

@Nalith Thanks for your contribution. The article has been updated since your opened your pull request. Your suggested changes will be applied to the article in a new PR in the private repository. Thanks.


fixed sharded weight loading

I encountered this error AssertionError: Could not find DiT checkpoint at ./outputs/000-vDiT-XL-222/epoch999-global_step2000/model/ during smapling. I notice that shard=True is enabled when saving the model weights, we should provide a loading method for sharded weights.

thanks for your contribution!


add create and deactivate user operation

added create user operation
added deactivate user operation

closes #9 and #1


Add support for including the number of ESXi hosts per cluster in System Overview Report

Code of Conduct

[X] I have read and agree to the project's Code of Conduct.
[X] Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
[X] Do not leave "+1" or other comments that do not add relevant information or questions.
[ ] If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description
On System Overview Report in vSphere Cluster Overview will be good to have number of servers per cluster.
Use Case(s)
On System Overview Report we have ESXi host number details in Hardware Overview and vCenter Server Overview but if we can have number of host per cluster in vSphere Cluster Overview will be good to see the split of servers.
In some situation we have customers with stretched cluster in MGMT where they removed one host from each AZ and that is unsupported setup which we can easily detect with this.
Potential Configuration
Adding number of hosts per cluster in System Overview Report/vSphere Cluster Overview.
References
No response

Easy enough to add, Dusan!

Wow that was fast :) thank you!


[PE-D][Tester A] Inconsistent "invalid message"

When a module code with less than 4 numbers following the code is searched for with view, the message given is "Invalid module code: csxxx" while for a module code with more than 4 numbers, the message given is "csxxxxx not in NUS curriculum". I feel like these 2 cases should share the same message.

Labels: type.FeatureFlaw severity.VeryLow
original: WR3nd3/ped#4

Standardise error message to 'cs10000' invalid or not in current NUS curriculum


PS update design doc to reflect new path lookup strategy

In #2997 we introduced a new path lookup strategy in the PS but didn't adapt the design doc. We should update the design. The new strategy is described in #2454 .

This is outdated, we already have a newer path lookup strategy that is reflected in the design doc.