Colour scheme for lines

Hi!
May i know what are the available colours for the line?

These are the chartist default colours: https://github.com/gionkunz/chartist-js/blob/develop/src/styles/settings/_chartist-settings.scss#L69-L85
You can customize easily: http://gionkunz.github.io/chartist-js/getting-started.html#colour-up-your-charts


docs/scaffolding small typo: Large display is 1200px and up, currently listed as 1210px

Merged into 2.0.2-wip. Thanks!


Make --module input optional

Currently this value is required, example: php artisan make:controller TestController --module=module-1
This PR allows for us to just select it from a list, example: php artisan make:controller TestController --module

This would be so cool!

Nice one! Was looking for this as well.

But we need to account that we want to create something in the /app folder as well.

I'm not sure if I'm following. This PR allows modular and non-modular files to be generated.
php artisan make:model Flight (creates in /app)
php artisan make:model Flight --module
php artisan make:model Flight --module=airport

But we need to account that we want to create something in the /app folder as well.

If you don't add --module it will create it on the app folder by default.


convert our link attributes to json before saving to database

Root cause is from djangocms-attributes-field https://github.com/divio/djangocms-attributes-field/pull/8


Support Jubilee

Hi @MikaelBTC! We are in the process of testing and finalizing the release of Ordhook.
Note that if you're using Ordhook exclusively for BRC20, you will be perfectly fine with the current version. Yes the BRC20 indexers are adopting the latest release 0.14, but they will all be basing their indexing using the vindicated inscriptions - meaning they are completely ignoring the actual changes coming with the Jubilee.

Hi @MikaelBTC! We are in the process of testing and finalizing the release of Ordhook. Note that if you're using Ordhook exclusively for BRC20, you will be perfectly fine with the current version. Yes the BRC20 indexers are adopting the latest release 0.14, but they will all be basing their indexing using taking into account the vindicated flag - meaning they are completely ignoring the actual changes coming with the Jubilee.

Thank you very much @lgalabru, also which ordhook version will work same as Jubilee? V1.1.3 or V1.2.0 or both?

Jubilee support added in v2.0.0

@MikaelBTC If you'd like to stay on v1, 1.2.0 would probably best.

@MikaelBTC If you'd like to stay on v1, 1.2.0 would probably best.

Thank you so much for explaining.


Converted bullet points from Importing Markdown section into subsections. Fixes #669

What kind of changes does this PR include?

[x] Minor content fixes (broken links, typos, etc.)
[ ] New or updated content
[ ] Translated content
[ ] Changes to the docs site code
[ ] Something else!

Description

What does this PR change? Give us a brief description.

Converted bullet points from Importing Markdown section into subsections. Fixes #669

Did you change something visual? A before/after screenshot can be helpful.

N/A

Thanks, @felixsanz ! This is looking much cleaner!
@delucis @aFuzzyBear - With <h3>'s, each of these exported properties becomes their own entry in the right sidebar. What do we think about this? I'm not sure whether we want this, especially given what it would do on mobile.
One option would be to add something like ### Exported Properties and then the individual properties themselves can all become <h4> and would NOT show up in the right sidebar. Thoughts?

@sarah11918 @delucis Done!

this does make it look alot cleaner, wanna check the toc component on desktop when I'm back on,

this does make it look alot cleaner, wanna check the toc component on desktop when I'm back on,

i'm on desktop, they don't show now:


Pino instrumentation is not sending log message to the logHook method

What version of OpenTelemetry are you using?
    "@opentelemetry/instrumentation-pino": "0.44.0",

What version of Node are you using?
v20.11.1
What did you do?
I am adding pino log messages to the my span using logHook of pino instrumentation. I tried with winston instrumentation. Log messages are adding to the span and able to see it in the jaager UI.
What did you expect to see?
I want log message should be there part of record parameter as like to winston. So I can add it in the span.
What did you see instead?
I don't see log message. But I see only traceId, spanId and trace flags.
Additional context
I am using jaeger all in one collector to collect the traces from my service. I am using GRPC OLTP Trace Exporter to export the traces. I have used pino logger for logging and registered pino instrumentation for automatic log correlation with span Id, trace ID.
tracing.js
const { BatchSpanProcessor, AlwaysOnSampler} = require("@opentelemetry/sdk-trace-base");
const { NodeTracerProvider } = require("@opentelemetry/sdk-trace-node");
const { Resource } = require("@opentelemetry/resources");
const {
  SEMRESATTRS_SERVICE_NAME,
} = require("@opentelemetry/semantic-conventions");
const { diag, DiagConsoleLogger, DiagLogLevel } = require("@opentelemetry/api");
const { HttpInstrumentation } = require("@opentelemetry/instrumentation-http");
const { registerInstrumentations } = require("@opentelemetry/instrumentation");
const {
  OTLPTraceExporter,
} = require("@opentelemetry/exporter-trace-otlp-grpc");
const {
  B3Propagator,
  B3InjectEncoding,
} = require("@opentelemetry/propagator-b3");
const {
  ExpressInstrumentation
} = require('@opentelemetry/instrumentation-express');
const { PinoInstrumentation } = require('@opentelemetry/instrumentation-pino');

module.exports = {
  initTracing: (config) => {
    if (config?.tracing?.enableDebug) {
      diag.setLogger(new DiagConsoleLogger(), DiagLogLevel.ALL);
    }
    const exporter = new OTLPTraceExporter(config.tracing);

    const provider = new NodeTracerProvider({
      sampler: new AlwaysOnSampler(),
      resource: new Resource({
        [SEMRESATTRS_SERVICE_NAME]: config.service_name,
      }),
    });
    provider.addSpanProcessor(new BatchSpanProcessor(exporter, config?.batchSpanProcessorConfig));
    provider.register({
      propagator: new B3Propagator({
        injectEncoding: B3InjectEncoding.MULTI_HEADER,
      }),
    });

    registerInstrumentations({
      instrumentations: [
        new ExpressInstrumentation(),
        new HttpInstrumentation({
          ignoreIncomingRequestHook: function (request) {
            if (config.tracing.urls_to_be_skipped.includes(request.url)) {
              return true;
            }
          },
          applyCustomAttributesOnSpan: function (span, request, response) {
            span.updateName(request.path);
          },
          ignoreOutgoingRequestHook: () => true,
        }),
        new PinoInstrumentation(
            {
              enabled: true,
              logHook: (span, record) => {
                span.addEvent("log", record);
              },
            }
        ),
      ],
      tracerProvider: provider,
    });

    return provider;
  },
};

tl;dr: instrumentation-pino is working as designed. Though it isn't clear in the documentation, the record in logHook(span, record) was never designed to include the Pino log message.  I'll explain more below.
repro
I made the following change to your tracing.js to make it easier to debug/see what is going on:
--- tracing.js.orig	2024-12-11 12:44:45
+++ tracing.js	2024-12-11 13:29:28
@@ -1,4 +1,4 @@
-const { BatchSpanProcessor, AlwaysOnSampler} = require("@opentelemetry/sdk-trace-base");
+const { SimpleSpanProcessor, BatchSpanProcessor, AlwaysOnSampler, ConsoleSpanExporter} = require("@opentelemetry/sdk-trace-base");
 const { NodeTracerProvider } = require("@opentelemetry/sdk-trace-node");
 const { Resource } = require("@opentelemetry/resources");
 const {
@@ -24,7 +24,7 @@
     if (config?.tracing?.enableDebug) {
       diag.setLogger(new DiagConsoleLogger(), DiagLogLevel.ALL);
     }
-    const exporter = new OTLPTraceExporter(config.tracing);
+    const exporter = new ConsoleSpanExporter();

     const provider = new NodeTracerProvider({
       sampler: new AlwaysOnSampler(),
@@ -32,7 +32,7 @@
         [SEMRESATTRS_SERVICE_NAME]: config.service_name,
       }),
     });
-    provider.addSpanProcessor(new BatchSpanProcessor(exporter, config?.batchSpanProcessorConfig));
+    provider.addSpanProcessor(new SimpleSpanProcessor(exporter));
     provider.register({
       propagator: new B3Propagator({
         injectEncoding: B3InjectEncoding.MULTI_HEADER,
@@ -57,6 +57,7 @@
             {
               enabled: true,
               logHook: (span, record) => {
+                console.log('XXX logHook called with record=', record);
                 span.addEvent("log", record);
               },
             }

Then I used this main.js to use it:
const {initTracing} = require('./tracing');
initTracing({
    tracing: {}
});

const {trace} = require('@opentelemetry/api');
const pino = require('pino');
const tracer = trace.getTracer('example');

const log = pino();
tracer.startActiveSpan('manual-span', span => {
    log.info('hi')
    span.end();
});

For completeness, here is my package.json:
{
  "name": "asdf.20241211t084855",
  "version": "1.0.0",
  "main": "index.js",
  "dependencies": {
    "@opentelemetry/api": "^1.9.0",
    "@opentelemetry/exporter-trace-otlp-grpc": "^0.56.0",
    "@opentelemetry/instrumentation": "^0.56.0",
    "@opentelemetry/instrumentation-express": "^0.46.0",
    "@opentelemetry/instrumentation-http": "^0.56.0",
    "@opentelemetry/instrumentation-pino": "^0.45.0",
    "@opentelemetry/propagator-b3": "^1.29.0",
    "@opentelemetry/resources": "^1.29.0",
    "@opentelemetry/sdk-trace-base": "^1.29.0",
    "@opentelemetry/sdk-trace-node": "^1.29.0",
    "@opentelemetry/semantic-conventions": "^1.28.0",
    "pino": "^9.5.0"
  }
}

When I run that I see:
% node main.js
XXX logHook called with record= {
  trace_id: '035f1a614bec2a89d2f5f5342475897a',
  span_id: '3fcf38c90c1cb36e',
  trace_flags: '01'
}
{"level":30,"time":1733952890974,"pid":90371,"hostname":"peach.local","trace_id":"035f1a614bec2a89d2f5f5342475897a","span_id":"3fcf38c90c1cb36e","trace_flags":"01","msg":"hi"}
{
  resource: {
    attributes: {
      'service.name': undefined,
      'telemetry.sdk.language': 'nodejs',
      'telemetry.sdk.name': 'opentelemetry',
      'telemetry.sdk.version': '1.29.0'
    }
  },
  instrumentationScope: { name: 'example', version: undefined, schemaUrl: undefined },
  traceId: '035f1a614bec2a89d2f5f5342475897a',
  parentId: undefined,
  traceState: undefined,
  name: 'manual-span',
  id: '3fcf38c90c1cb36e',
  kind: 0,
  timestamp:<PHONE_NUMBER>974000,
  duration: 1847.834,
  attributes: {},
  status: { code: 0 },
  events: [
    {
      name: 'log',
      attributes: {
        trace_id: '035f1a614bec2a89d2f5f5342475897a',
        span_id: '3fcf38c90c1cb36e',
        trace_flags: '01'
      },
      time: [<PHONE_NUMBER>, 975422042 ],
      droppedAttributesCount: 0
    }
  ],
  links: []
}

As you said, the log message is not sent to the logHook:
XXX logHook called with record= {
  trace_id: '035f1a614bec2a89d2f5f5342475897a',
  span_id: '3fcf38c90c1cb36e',
  trace_flags: '01'
}

Going back to the original implementation of instrumentation-pino, the logHook() function was only ever passed a "record" of fields used for trace-correlation:
https://github.com/open-telemetry/opentelemetry-js-contrib/pull/432/files#diff-660728f57a3c2b22336bc39c10f17f768ce60fc9d3e706f7a648e61dc0ebf35bR140-R146
The original intent of the logHook was to be an "Optional hook to insert additional context to log object."
I.e. it was (and is) a way to provide additional fields that will be added to the log record.
why is the log "message" there with instrumentation-winston?
instrumentation-winston was created by the same author, and the intent of the logHook() was the same.
However, because of how the Winston logging pipeline internals work it was convenient to use the Winston info object, rather than using a new record object with the trace-context fields. The "info" object is a Winston object that holds both the additional fields for a log record and the log message.
XXX logHook called with record=  {
  message: 'hi',
  level: 'info',
  trace_id: '93db43c49c0f094b2bc2d2489203ce4b',
  span_id: 'db85c3c5aa5c264c',
  trace_flags: '01',
  [Symbol(level)]: 'info'
}

why is it called "record" then?
So why does logHook(span, record) use the term "record" then?
At the time this was implemented, I don't think OpenTelemetry has a logs signal yet, which defines a LogRecord type.
I think the term "record" here is part of the cause of confusion here. Perhaps a name like "fields" or "recordFields" would be more accurate.
what could be done here?
Getting access to the log message in the logHook function, or some other configurable hook, is effectively a feature request.
Currently the logHook hook in instrumentation-pino is using the pinomixin functionality which does not provide access to the message, so I'm not sure how simple or difficult it would be to provide this functionality.
Have you considered using the OpenTelemetry Logs signal and sending Pino log records via OTLP, rather than adding the log messages as Span Events?  To do that you'd want a change to tracing.js something like this:
% diff -u tracing.js tracing-and-logs.js
--- tracing.js	2024-12-11 13:29:28
+++ tracing-and-logs.js	2024-12-11 14:13:54
@@ -19,6 +19,9 @@
 } = require("@opentelemetry/instrumentation-express");
 const { PinoInstrumentation } = require("@opentelemetry/instrumentation-pino");

+const { ConsoleLogRecordExporter, SimpleLogRecordProcessor, LoggerProvider } = require("@opentelemetry/sdk-logs");
+const { logs } = require("@opentelemetry/api-logs");
+
 module.exports = {
   initTracing: (config) => {
     if (config?.tracing?.enableDebug) {
@@ -39,6 +42,14 @@
       }),
     });

+    const loggerProvider = new LoggerProvider({
+      resource: new Resource({
+        [SEMRESATTRS_SERVICE_NAME]: config.service_name,
+      })
+    });
+    loggerProvider.addLogRecordProcessor(new SimpleLogRecordProcessor(new ConsoleLogRecordExporter()));
+    logs.setGlobalLoggerProvider(loggerProvider);
+
     registerInstrumentations({
       instrumentations: [
         new ExpressInstrumentation(),
@@ -56,10 +67,6 @@
         new PinoInstrumentation(
             {
               enabled: true,
-              logHook: (span, record) => {
-                console.log('XXX logHook called with record=', record);
-                span.addEvent("log", record);
-              },
             }
         ),
       ],

Then re-running main:
% node main.js
{
  resource: {
    attributes: {
      'service.name': undefined,
      'telemetry.sdk.language': 'nodejs',
      'telemetry.sdk.name': 'opentelemetry',
      'telemetry.sdk.version': '1.29.0'
    }
  },
  instrumentationScope: {
    name: '@opentelemetry/instrumentation-pino',
    version: '0.45.0',
    schemaUrl: undefined
  },
  timestamp:<PHONE_NUMBER>837000,
  traceId: '55013ede26908c0e79d992141dac5485',
  spanId: '4ecf0d1274ca0470',
  traceFlags: 1,
  severityText: 'info',
  severityNumber: 9,
  body: 'hi',
  attributes: {}
}
{"level":30,"time":1733955335837,"pid":91340,"hostname":"peach.local","trace_id":"55013ede26908c0e79d992141dac5485","span_id":"4ecf0d1274ca0470","trace_flags":"01","msg":"hi"}
{
  resource: {
    attributes: {
      'service.name': undefined,
      'telemetry.sdk.language': 'nodejs',
      'telemetry.sdk.name': 'opentelemetry',
      'telemetry.sdk.version': '1.29.0'
    }
  },
  instrumentationScope: { name: 'example', version: undefined, schemaUrl: undefined },
  traceId: '55013ede26908c0e79d992141dac5485',
  parentId: undefined,
  traceState: undefined,
  name: 'manual-span',
  id: '4ecf0d1274ca0470',
  kind: 0,
  timestamp:<PHONE_NUMBER>837000,
  duration: 2046.458,
  attributes: {},
  status: { code: 0 },
  events: [],
  links: []
}

You can see that OpenTelemetry is emitting the LogRecord and separately the Span. The OpenTelemetry LogRecord has traceId and spanId to correlate with the span.
The main question is whether your current telemetry backend supports OTel Logs well or at all.


Add Oriented Box Colliders

Completed by looping through the struct array of boxes and running new box collision algorithm


403 Disallowed user agent from iOS device

I completed the entire codelab with no issues. Good job on the tutorial, I felt I learned a lot. While attempting to talk to myself from various devices I tried using my iPhone. When I attempted to authenticate from the phone I receive a 403 disallowed user agent error, I receive the same error when using an iPad. I did some searching on the issue but was not able to determine if this is actually a bug or maybe the authentication method in the codelab needs updated? I'm still learning so my apologies.

I believe this is related to: https://github.com/firebase/firebase-js-sdk/issues/77
Closing in it's favor


Tracker is not working after update 1.5.0

Describe the bug
Tracker is not working after update 1.5.0
no information today

manual resync and scan old logs not working too

https://mtgarena.pro/news/your-tracker-stopped-updating-after-v-1-5-0-release/

Now working, TY!


Feature/java spring cloud stream

More changes are probably coming, this isn't ready to be merged yet.

@damaru-inc can you convert the PR to a draft while it is still in progress, else I would think it is ready for review 😄


You may need an appropriate loader to handle this file type

I tried to start the packager but I got this error:
Unexpected token (47:2)
You may need an appropriate loader to handle this file type.
| const propTypes = {
|   ...View.propTypes,
|   style: ViewStyleExceptBorderPropType,
|   children: NotAllowedPropType,
 @ ./~/lottie-react-native/index.js 1:17-46
 @ ./src/components/Loading/Loading.js
 @ ./src/utils/utilityComponents.js
 @ ./src/components/withHelpers/withBranches.js
 @ ./src/components/Order/OrderHoc.js
 @ ./src/routes/SignedIn.js
 @ ./src/routes/index.js
 @ ./src/index.js
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

React Native 0.46.1
Lottie React Native 1.1.1

@jurajkrivda Do you still get this on master with a fresh npm install?


Enhanced Recurring Donations - Setting the default picklist value for the Recurring Type field to Fixed results in users not being able to enter Number of Planned Installments when creating a new Recurring Donation

Background
The New and Edit buttons on Recurring Donations use a Lightning component form (RD2_EntryForm) to help simplify creating and editing Recurring Donations by users. Elements of this RD2_EntryForm render dynamically, such that editing certain fields renders different form fields
Issue Summary
By default the Recurring Type field has a default value of Open and the RD2_EntryForm is expected a Recurring Type of Open when a new Recurring Donation is created and so it does not display the Number of Planned Installments field. As a result if an admin changes the default value of the picklist to Fixed, when a user creates a new Recurring Donation they will not be able to see the Number of Planned Installments field during record creation, a field that is crucial when creating a Fixed Recurring Donation.
Relevant code sections
https://github.com/SalesforceFoundation/NPSP/blob/master/src/lwc/rd2EntryFormScheduleSection/rd2EntryFormScheduleSection.js#L371
https://github.com/SalesforceFoundation/NPSP/blob/master/src/lwc/rd2EntryFormScheduleSection/rd2EntryFormScheduleSection.js#L306
Workarounds

During record creation, a user can change Recurring Type from Fixed to Open and then back again to Fixed they will be able to see and enter a value for Number of Planned Installments
After the record has been created, a user could immediately edit the record and enter the desired value for Number of Planned Installments
An admin can change the default value for Recurring Type back to Open and instruct users to change the value to Fixed when creating a Recurring Donation

W-9047953

Please follow this Known Issue in the Trailblazer Community for updates.


Hint/enhancement/85 notification refactor

Addresses #85.
This includes a pretty major refactoring of the notification system. Some nice side effects are:

it won't attempt to send notifications to users without a phone number
it won't add users without phone numbers to the notified_user_ids of a Need
methods are much easier to test (and are tested)

This is most-definitely a WIP, but wanted to get a draft PR opened so there's a place the diff can be easily viewed.
Soft goal for me right now is to get this wrapped up by next Thursday.

Whoops, just remembered I can make a draft PR. Going to close this and do that. Sorry for the noise! :)


Log lines written always with the same time

I have noticed that the log file has all the lines with the same moment, like 2017-06-14-22:00:01
My backup is scheduled using cron, once a day, always on 10 PM, and all the lines keep repeating the moment it started.
This backup can take more than one hour, based on the statistics output for the files backup, the latest step:
--------------[ Backup Statistics ]--------------
StartTime<PHONE_NUMBER>.45 (Wed Jun 14 22:46:33 2017)
EndTime<PHONE_NUMBER>.35 (Wed Jun 14 22:46:42 2017)

oops! That's seem to be the way I set variables. I'm not really convinced with the way it handles logs. It should be a better way.
Probably adding something like this:
#!/bin/bash -x exec > /var/log/alfresco-bart.log 2>&1


Add session ID generation

This change should generally be compatible with previous versions.  It's just adjusts the session IDs since some code expects the SDP to use a specific session ID (used in adapter.js).

Codecov Report

Merging #31 into master will decrease coverage by 0.17%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##           master      #31      +/-   ##
==========================================
- Coverage   90.14%   89.96%   -0.18%
==========================================
  Files           1        1
  Lines         284      289       +5
==========================================
+ Hits          256      260       +4
- Misses         28       29       +1

Impacted Files
Coverage Δ

sdp.js
89.96% <83.33%> (-0.18%)
:arrow_down:

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 46b6885...79fd14d. Read the comment docs.

Are you ok with contributing it under the terms of https://developercertificate.org/ (I need  to update the contributing file)?
Two minor comments inline, I can take care of them after merging.

I am happy with contributing under those terms.  Thanks!

Fab, thank you very much.
Sadly I forgot to hit the "submit review button". Will fix those issues after merging later today unless you beat me to it

I've updated the comments as suggested - makes sense.

squashed, merged and published as version 2.1.0


[Addition]: Please check this out

Hotspot b58 Addresses
11PLdRM2b5ZantqWKgQAHu9YmnpA75dVerM9FyFeTMnQwxXsyNB
11KqLBr7Z6ru5oNWgZQhfPekV9WzfGbSJskUWBvJ6MoQUF2zJRE
112DdH79aqBFjWMUbmQXVMz5im2YqcPw5EAscfdfGcTuNKphJAYT
112nw3TmqGSTPS1ncq9tfshuvnF7PUfViHFrVB2R78UN4WafJFuk
112nDM9Mij12kNrFP1Ch4XKG67t58YD4dXeeAsnok5UTb2YWNitT
11iu6LgD4TDEM3UVRA7p4XE7PL1DWrn56L14CpSAu9nNHtXncE6
112M4XPDiYx5wAD934cRpwyWnVswCDXsF1saF3VrHS6ns5T4dwX6
112AcKXq8mCHc3TA2ovo1j778gU3bZkQGV9bEHH9vArnVysCRMd
112Uo1dpGiwdC2HHx5r1eWZgWqNF4E1Hjts4T1mmhup4wQXVAiXi
112AcKXq8mCHc3TA2ovo1j778gU3bZkQGV9bEHH9vArnVysCRMd
Discord Handle
ivou
Reason(s)
All hotspots are owned by same owner   address 13HuKfHZyemeZxgu99uTDhnG2rEE1MucGEmaYypcg75JyDXwNZ1 and witnessing each other without witnessing other hotspot or being witnessed by other hotspots.

Also all hotspots placed in perfect locations


Unify Points Table More

Background
6 months ago, we had three tables: Plant, ToolSlot and GenericPointer. Each table was created independently. As the app grew, we needed the ability to query across all three tables. To avoid wiping out old data, we added polymorphic associations to a new points table.
This became tedious to deal with over time and querying was only marginally easier. This pull request gets rid of the polymorphic associations in favor of single table inheritance
What's New?

Unified plants, tool_slots and generic_pointers into one table via STI (see above)
Rename plants to legacy_plants, tool_slots to legacy_tool_slots etc.
Write migration stuff to transition old records to new format gradually.

What's Next?

Ability to archive points

Coverage remained the same at 90.075% when pulling 56a8b1fa3ae28d30b466b4925f31ad586a49fabf on RickCarlino:merge_pointer_tables into 4395ad458c2d9b7f4ff67e7db172cdd51e74dd60 on FarmBot:staging.


gift rains

what

also get_or_create returns the object as well as bool of whether it was getted or created so do user, _ = User.get_or_create()

right ok i forgor will fix it

done

i will look into this tomorrow its 1:20 am

ok cool


Request for adapting new version of rstudio

I'm a mac user. I see this dark theme in youtube and it's amazing. But when I use it in the latest Rstudio, there exist some bugs.
The update panel:

The global setting panel:

Maybe I can use the old version of Rstudio to have best experience, but I don't know which version it is. Finally, thanks for you dark theme, it's amazing.

My apologize, the version of my mac os is big sur 11.0.1 and the version of my rstudio is 1.3.1093


fixed small import issue

I tried to use this package, but I had some issues with these imports. It was probably a conflict with django forms. By using a relative path, it imports these modules from the fontawesome directory and this doesn't interfere with anything else.

+1
Found this package and immediately ran into this problem

+1 @mitzaM
Thanks for the fix. I had the same problem.


Fix text docs

This is unnecessary. We sub the canonical URL (canonical_url) in:
if @settings['text']
  canonical_text = "#{@settings['text']}"
  canonical_text = canonical_text.gsub /{{ url }}/, canonical_url
# Otherwise, use boilerplate
else
  canonical_text = "
This article was originally posted on my own site.
"
end

The canonical URL is created like this:
url =<EMAIL_ADDRESS>

It does not work for me with #{url}.

https://github.com/aarongustafson/jekyll-crosspost-to-medium#configuation


New release

@Zegnat what do you think? Release 0.2.0?

I am very much for iterative development. If you have nothing else you want to get merged, just mark as a new release.
Not yet 100% convinced of the previous changes to the factories, but I do feel they are improved from 0.1.0. That’s all that should be needed for a new release IMHO.

Great!.


Integrate the abuse ip db for guest comments

We already hit akismet in an api call, but there's also a database of spammy IPs that we could report to when spam is identified and check against when a guest comments.
https://www.abuseipdb.com/register
By adding 2 api calls inline on a comment post the user experience is degraded (akisment and now abuseipdb). We want to instead

[ ] Move both API calls into a new background job
[ ] Only send email to user out once we've proven it's not spam and not from an abusive IP

Hmmm....

Webmaster accounts have a rate limit of 3,000 requests/day. You can view your rate limits and API usage information by going to the accounts page page and clicking on the "API Usage" tab.

Note: In addition to the monthly rate limit, all accounts are limited to 60 requests per minute.

To prevent duplicate reports being submitted automatically through our API (such as via Fail2Ban integration), we limit each accounts to reporting the same IP once per 15 minutes.

@innatewonderer Any interest in taking this and https://github.com/sudara/alonetone/issues/249 on? We are getting hammered by comment spam in the moment.
I guess the complicated part is the API restrictions on abuseipdb — we'd need to take the incoming IP from a comment/track/user and check it against our own internal table of ips, and if there's no recent information / if the IP isn't blocked already, make an API request...

After going through spammer's IPs and evaluating them against the db, I've decided this won't be beneficial.


"Harvest" static files in addition to OAI

One major area that has not yet been addressed is the "harvesting" of static files.
The form of static records may include:

discrete XML files, one record per
aggregate XML file, with multiple records contained
CSV file mapped to metadata fields (e.g. DC, where nested standards like MODS might be hard to map)

To what degree these will all be supported, remains to be seen, but looking into the most common use cases.

Progress on static file harvesting:
https://github.com/WSULib/combine/tree/dc79a410d752cad89635a83029b3f4caad3fcba8
Refactored HarvestJob to allow for more specific sub-types of harvesting, including OAI, and now static files.
Because OAI is structured, and provides unique identifiers for each record, it's pretty straightforward to select documents and identifiers for each document.  That is not the case with static XML uploading, where it's unknown what format records will be in.
To counter this, the static harvest GUI allows for users to provide xpath queries for:

root of metadata document, e.g. /mods:mods
expression for finding a unique identifier, as text of an element, e.g. //mods:mods/mods:location/mods:url[@access]

Additionally, allows for pointing to a path on disk of the user wants to provide a directory of records that way.
Currently, supports uploading of zip files that it extracts, and expects a flat directory of XML files, one record per file.  Planning to support tar files as well.
One more nut to crack, accepting "aggregate" files with multiple records contained, e.g. MODS or METS files.

Handles zip, tar, other archives.  And "aggregate" XML files, that may contain many XML records (e.g. MODS or METS).
Closing.


Please add licensing information

This repository is lacking licensing information. As such, everything included in this repo is "All rights reserved".
Please note that in order to re-license this project you'll legally need ack from all existing contributors.

done, thank you.


Select data column with SelectSheet

Hi @brandondrew,
I am currently using
Excel::load($file)->first()->first();
How to correctly switch to
Excel::selectSheets('Sum')-> ????
My file is as attached
F_42000.xlsx
Thank you.

Sorry, it's been so long since I've used that.  I'm currently deep into
React and (back into) Rails now.  My Laravel days are behind me.
On Wed, Sep 6, 2017 at 12:31 AM, phamvanthanh<EMAIL_ADDRESS>wrote:

Hi @brandondrew https://github.com/brandondrew,
I am currently using
Excel::load($file)->first()->first();
How to correctly switch to
Excel::selectSheets($sheetname)-> ????
Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Maatwebsite/Laravel-Excel/issues/1347, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAAmfg4XpQ9Xml9zdQhYoaGqweusNSXXks5sfiAcgaJpZM4PN01F
.

--
Brandon Zylstra
<EMAIL_ADDRESS>

Thank you however. Anyone still support this package?


Remove unstable feature attribute for alloc crate

This crate has been very helpful in one of my projects, thanks a lot!
I noticed it needs nightly Rust because of the feature for the alloc crate. Since alloc has been stabilized in 1.36.0 for library crates, this is no longer necessary and removing it allows the library to be compiled in projects with stable Rust.

Published in 0.11.2.

That was quick, thank you!


Add support for Django 4.1

* Strip IDENTITY related suffixes auto fields are getting on Django 4.1.
  These suffixes are upsetting redshift.

Subject: Django 4.1 support
Feature or Bugfix

Feature

Purpose

Add support for Django 4.1

Detail

Clearing DatabaseWrapper.data_types_suffix which, on DJango 4.1, are responsible for adding "GENERATED BY DEFAULT AS IDENTITY" to auto fields, and which are upsetting Redshift. Actually makes impossible to create new table or django_migration table.

Relates

#106

pre-commit is... failing

Updated documentation and setup.cfg as well

IDENTITY related suffixes auto fields are getting on Django 4.1

The suffix related to IDENTITY appeared because Django 4.1 now creates AutoField with integer GENERATED BY DEFAULT AS IDENTITY available since postgres 10 instead of serial.
https://github.com/django/django/blob/bc3b8f152452ba0e41f28baa93c0bf8f39cddb09/django/db/backends/postgresql/schema.py#L44-L47
Therefore, the current PR will create tables with integer instead of serial, which is a different behavior than in django-4.0 and earlier.
I've been investigating for a couple of hours and haven't found a good fix yet. Please let me know if there is a way to fix it.

Hmmm... I thought the serial stayed since the tests checked the resulting SQL and without the suffixes it was the same as on earlier Django versions.

Where should I look? The AutoField data_type was already overriden by redshift-engine to integer identity(1, 1) so i guess somewhere is a part that also needs to be changed for postgresql to either vendor, or ditch the serial in favour of a modern GENERATED BY DEFAULT AS IDENTITY 🤔

@shimizukawa the way I see it is that the tests running directly on Postgres will become increasingly hard to maintain with each PostgreSQL/Django release (and redshift evolves too).
Maybe the best approach would be to fork the whole code from Django 4.0.x instead of inheriting from the Postgres engine from whatever Django is there underneath. Plus the Postgres implementation and redshift will become increasingly distinct 🤔
I tried to pinpoint what has changed between 4.0.x and 4.1.x but all I got was additional IntegerField generated with primary_key set to True. (copied get_field_type from 4.0.x)

Thank you @fizyk,
I apologize for the long delay. I was able to complete the implementation of django-4.2 support based on your proposal to vend django code base.
I'm closing this PR now that Django-4.2 support is complete.
Thank you for your great contribution.


xen: drop 4.17, move to by-name.

Description of changes

Migrate Xen to by-name, since it can't be migrated automatically.

This has the side effect of simplifying some Xen stuff.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux

[ ] 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 pr 345192". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[x] (Package updates) Added a release notes entry if the change is major or breaking

[ ] Fits CONTRIBUTING.md.

Intermediate commits will be squashed.

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

Do package sets work with by-name?

Do package sets work with by-name?

I don't think so. This also sends all xenPackages to the top-level attribute. (xenPackages.xen_4_19 -> xen_4_19).

I have reached the conclusion I have no idea what I'm doing.

Hate to say it, but this is a violation of the by-name contract. cc @infinisil for advice on the correct way to handle it, but the one being used for the Darwin SDK rework that seemed okay was to have the package take e.g. a xenVersion argument that the all-packages.nix calls override appropriately.
It’s also fine to just not be in by-name. It’s not expected that every package can currently fit into the schema.

I don't think contract is breached with buildXenPackage?

The problem is that by-name packages have to look like callPackage ../by-name/ab/abcd args and have to be derivations. With the current pkgs/by-name/xe/xen structure, it’s impossible to satisfy both.
With the xenVersion thing, you can even get fancy and make e.g. pkgs/by-name/xe/xen_4_18-slim/package.nix be { xen }: xen.override { xenVersion = "4.18"; xenSlim = true; } if you really don’t want any all-packages.nix entries.

I still don't see what exactly is wrong here?

But you only satisfy that condition because you violate this one:

For each package directory, the pkgs.${name} attribute must be defined as callPackage pkgs/by-name/${shard}/${name}/package.nix args for some args.

Got an OCaml-related build failure with 4.18.
 Looks like we'll still have to pin it after all.

We can only pin 4.18 and keep building 4.19 with latest ocaml?

We can only pin 4.18 and keep building 4.19 with latest ocaml?

Fixed. 4.18 now has an override to pin OCaml to 4.14.

Result of nixpkgs-review pr 345192 run on x86_64-linux 1

1 package marked as broken and skipped:

qubes-core-vchan-xen

1 package blacklisted:

nixos-install-tools

68 packages built:

appvm
collectd
diffoscope
diffoscope.dist
diffoscope.man
docker-machine-kvm2
gnome-boxes
guestfs-tools
htcondor
libguestfs
libguestfs-with-appliance
librenms
libvirt
libvirt-glib
libvirt-glib.dev
libvirt-glib.devdoc
libvmi
libvmi.dev
libvmi.lib
mgmt
minikube
multipass
ocamlPackages.ocaml_libvirt
perl536Packages.SysVirt
perl536Packages.SysVirt.devdoc
perl538Packages.SysVirt
perl538Packages.SysVirt.devdoc
python311Packages.guestfs
python311Packages.guestfs.dist
python311Packages.libvirt
python311Packages.libvirt.dist
python312Packages.guestfs
python312Packages.guestfs.dist
python312Packages.libvirt
python312Packages.libvirt.dist
qemu_xen
qemu_xen.debug
qemu_xen.ga
rubyPackages.ruby-libvirt
rubyPackages_3_1.ruby-libvirt
rubyPackages_3_2.ruby-libvirt
vagrant
virt-manager
virt-manager-qt
virt-manager.dist
virt-top
virt-viewer
xen (xen_4_19)
xen-guest-agent
xen-slim (xen_4_19-slim)
xen-slim.boot (xen_4_19-slim.boot)
xen-slim.dev (xen_4_19-slim.dev)
xen-slim.doc (xen_4_19-slim.doc)
xen-slim.man (xen_4_19-slim.man)
xen.boot (xen_4_19.boot)
xen.dev (xen_4_19.dev)
xen.doc (xen_4_19.doc)
xen.man (xen_4_19.man)
xen_4_18
xen_4_18-slim
xen_4_18-slim.boot
xen_4_18-slim.dev
xen_4_18-slim.doc
xen_4_18-slim.man
xen_4_18.boot
xen_4_18.dev
xen_4_18.doc
xen_4_18.man

I'd like to apologise in advance for the things you review here.


Refactor/ddf2

Please DON'T MERGE. This PR is only for code review.
Change for Schema & IDataSource.
Basically all ddf will be created from an IDataSource
In case of engine doesn't support a concrete datasource -> throw unsupported datasource exception
else Engine will do prepare and make ddf on this datasource.
/cc @sameerp @mbbui @steveyan777 @Huandao0812 @nhanitvn @hai-adatao @lebinh

@sameerp @PangZhi @mbbui @nhanitvn @Huandao0812 @lebinh @phvu could you help to review & comment on it.
more doc: https://docs.google.com/document/d/1iTAUREZnfua1xMEvjLpC4CO69zaXI-74QANRDqZnn9s/edit


Create collection EventVolunteers

Please do work for this task in a branch called issue-158.
We'll need a collection which stores all users who have signed up for an event. This collection will be useful for organization and admin users to retrieve users under events, and either remove them, add more, or even adjust volunteer hours done.

I think this issue is trivial. We have a collection VolunteerEvents which contains the same information. We can collect all volunteers of an event by querying all volunteers sharing the same eventID. Comment if you think otherwise


fultz, brambling

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[b,f]

/trunk merge


Color Per Tick Not Working

Version: <IP_ADDRESS>
Settings:

Expected Behavior:
Each tick uses its corresponding color
1: white
2: white
3: red
4: blue
5: green
Actual Behavior:
First 5 tick cycle: white
Second 5 tick cycle: white
Third 5 tick cycle: red
Fourth 5 tick cycle: blue
Fifth 5 tick cycle: green.
This was working at some point, but just noticed the issue when trying to use it today at colosseum.

Changing tick count to 1 solves the problem, however I still feel like it's not super intuitive that that is how the behavior works. Feel free to close if you disagree, but maybe worth changing the name of the setting or something?

Yeah that's intentional and I named it the same way as in the original metronome plugin but it does get a bit confusing with how many settings there are now. The description of the settings should clarify, it shows once hover your mouse over a setting.


cloud-init: remove local cloud-init.cfg

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary

What does the PR accomplish, why was it needed?
Remove local cloud-init.cfg file as azurelinux is officially supported in cloud-init upstream. We should deprecate our local version of cloud-init config (which are only used for marketplace image) and use default upstream config which reduces of burden of maintaining.
Change Log

remove local cloud-init.cfg and use upstream config
remove cloud-init.cfg from marketplace image install list
Some detailed changes:

the default login in user_name change from azl_user back to azurelinux
remove the lock_passwd=false setting on root to prevent password login on root
remove datasource_list, this is tested on Azure with no impact.
in cloud_init_modules add support for seed_random, ca_certs, set_passwords
in cloud_config_modules add support for keyboard, locale, ntp, timezone, disable_ec2_metadata
in cloud_config_modules add support for write_files_deferred, ansible, keys_to_console, phone_home, power_state_change
change azurelinux group from root, docker to wheel
specify networkd as default network renderer

Does this affect the toolchain?

NO
Associated issues

#xxxx

Test Methodology

Pipeline build id: 619144
Azure VM provisioning test. Check cloud-init log and status

Considering the risk of the change and no imminent needs I decided to close the PR now and making upstream PR instead to remove the modules Azl3 not supported.


process replay in all of CI

enables BEAM=2, benchmarks, CI, openpilot process replay with the same infra.

status: openpilot is the last one left with non deterministic process replay.


Finetune to others language ?

How I can finetune in other language , maybe vietnamese, ? thanks guys, awesome project

I can provide some steps:

check http://github.com/THUDM/icetk whether it can tokenize vietnamese. if so, it is possible to fine-tune it to vietnamese.
preparing some image-vietnamese pairs and other vqa data.
finetuning the model using sat.

I can provide some steps:

check http://github.com/THUDM/icetk whether it can tokenize vietnamese. if so, it is possible to fine-tune it to vietnamese.
preparing some image-vietnamese pairs and other vqa data.
finetuning the model using sat.

Thanks guy, I'try this !


Record typing test

Reproduces a bug in the lowering or other front-end phases of the compiler, where the initial type-check passes, but post lowering, the IR does not carry enough type information to check anymore (my best guess).
Thanks to @ninegua for reporting to the team Slack today, based on another dev's comment.
I'm not committing the new test outcome, because it's erroneous.
This message appears:
Ill-typed intermediate code after Desugaring (use -v to see dumped IR):
(unknown location): IR type error [M0000], subtype violation:
  {var myList : List<None>}
  {var myList : List<Nat>}

Investigating...

(Closing - fixed in #3268)


Add support for [attr.if.name]="boolean" syntax

Similar to [class.name]="boolean", which adds a class 'name' if boolean is true, and removes class 'name' _if boolean is false (or I think null?).
For example:
<button [attr.if.shiny]="isShiny"></button>

Would output <button shiny></button> if isShiny == true, and remove the 'shiny' attribute if isShiny != true. The reason for this new feature, versus re-using the existing [attr.shiny] syntax, is that it strictly coerces the values to strings, and writes them in the template:
<button [attr.shiny]="isShiny"></button>

... outputs <button shiny="true"></button>.
We talked about trying to check, and if the value is a bool use the new behavior, but that is (a) breaking, and (b) not definitive (it's possible for the value to be Object or bool and require runtime checks). It's probably not worth it.

BTW if anyone has better syntax alternatives, suggest them!

null as expression result is supposed to remove the attribute.
It's a while I used it, but I'm sure this worked already.
Are you requesting a different variant where false removes the attribute?

I think the best way would be to make it a breaking change to be (a) in line with e.g. [class.name]="boolean" and (b) to have the same behavior as other frameworks e.g Vue.js (if that counts) _if_ this could land before the stable release of Angular 5.
<button [attr.shiny]="false"></button>
<!-- <button></button> -->

<button [attr.shiny]="null"></button>
<!-- <button></button> -->

<button [attr.shiny]="myObject"></button>
<!-- <button></button> -->
<!-- Maybe a warn?: [attr.shiny] can only handle Boolean values. myObject is an object, therefore the attribute 'shiny' is not set. -->

<button [attr.shiny]="true"></button>
<!-- <button shiny></button> -->

We could also opt-in with:
<button [attr.bool.shiny]="isShiny"></button>
<!-- <button shiny="true"></button> -->
<!-- <button shiny="false"></button> -->

<button [attr.bool.shiny]="myObject"></button>
<!-- !!! throws a compile time error: myObject is not a Boolean. You can only use a Boolean value with [attr.bool.<foo>] !!! -->

As a bonus you could extend (in the future) the attribute binding with e.g. toJSON 😅
<button [attr.json.data-hero]='myObject'></button>
<!-- <button data-hero='{"name": "Batman", "realName": "Bruce Wayne"}'></button> -->

BTW, is it not possible to check at compile time if it is a Boolean or an object (I have no idea which code you are generating and if Dart allows this)?
So this (just brainstorming):
<button [attr.shiny]="myObject"></button>
<!-- <button></button> -->
<!-- Maybe a warn?: [attr.shiny] can only handle Boolean values. myObject is an object, therefore the attribute 'shiny' is not set. -->

... generates something like this:
try {
  if (attrShinyValue) {
     // logic to add the attribute to the HTML element
  }
} catch (e) {
   // ups, not a Boolean
   // inform the user with a warn/error message
}

Honestly I don't see any of the proposals carry it's weight.
I'd just leave it as it is.
There is no missing functionality as far as I am aware and
changing that behavior now for alternatives that don't seem to have a clear advantage
isn't worth it.

Yeah, just a suggestion because they talked about it. Just gave my two cents.

@akaufmann:

I think the best way would be to make it a breaking change

We've decided we are not adding any more (intentional) breaking changes to the framework before 6.0.0, so if we do add this it needs to be incremental (i.e. non-breaking).
@zoechi:

Honestly I don't see any of the proposals carry it's weight.
There is no missing functionality as far as I am aware.

There is, though. Users have not found a way to add/remove a value-less attribute. We could argue that isn't useful, but at least someone thinks it is, and they can't write the code today.

@matanlurey

found a way to add/remove a value-less attribute

Not sure what you mean by that. Currently Angular creates disabled="true" and the ="true" part can't be got rid of. That doesn't seems to be a real issue though. Still wondering why you mention "value-less attribute"
Have you checked if [attr.foo]="null" results in the attribute not being added (being removed).
That always worked for me, but I haven't used it since quite a while.
If this doesn't work, then there is of course work necessary.
If it does though, it's not clear what exactly is the feature request about.

Yes, they want to omit the ="true" part, which is not idiomatic.

I see.
Never saw real complaints about that in Angular TS world, just tons of questions how to get a bound attribute removed. One of my most successful answer on SO :D https://stackoverflow.com/questions/36745734/how-to-add-conditional-attribute-in-angular-2
In this case I'd prefer
 [attr.bool.shiny]

or if possible even better just
 [bool.shiny]

It could also be boolean.shiny because the bool is not related to the Dart type but to HTML "boolean attributes" (no strong opinion here)
I don't know about the amount of work which approach causes, but I think boolean attributes are special enough (but probably rather rare) so that their own prefix would be justified.
I don't think there is much difference in discoverability.
Even the null to get normal attributes removed is pretty hard to discover as the many upvotes to my SO question demonstrate.

I'll let @TedSander and @nshahan weigh in because its their team's request.

We see this code pattern a good amount of time:
[attr.raised] = "raised ? '' : null"
It is weird to use an API where you ask the user to use null instead of false. False is more natural value. Will also be better for non-nullablity. Seems like we could do better. It was so bad teams were trying to add Inputs/unperformant code just to get around writing this syntactic sugar in their template.
I would think it would be an easy nice to use syntactic sugar that could be added pretty easily. If it is hard to do in the compiler we don't NEED it, but if it is easier I think it has been shown by other frameworks and the code we see inside that it is useful.

@TedSander what about the DOM result raised="" instead of just raised? Does it matter?
I don't see much value in raised="false" (could always be achieved if necessary by [attr.raised]="'false'" anyway),  therefore an expression result of falseremoving the attribute (the same asnull`) seems reasonable to me.
I have no strong opinion either way. I'm just curious about this topic because I was involved a bit in the discussion back then with Angular TS (and I think I also argued for false removing the attribute)

I see this as convenient when you want have styles that target the presence of an attribute on an element in the dom.
my-component {
  [my-attribute] {
    // some special styles
  }

It gets confusing when you have to deal with the attribute being present, not present, present but "true", and present but "false". It would be easier if "true" and "false" were always represented as present or not present in the dom.
I think it would be nice to have syntactic sugar that would allow you to have an input binding between a dart bool and the presence of an attribute on the element.
That way, if you wrote <my-component my-attribute>...<\my-component> the input would be true. If the attribute isn't present then the bool in dart would be false.
At the same time if you set the value of the input to true, the attribute will be present, if you set it to false then the attribute will be removed entirely.

@zoechi raised="" vs raised doesn't matter. Most HTML APIs have the behavior that any value on the attribute means it is true.
This still autofocuses for example:
<input type="text" name="fname" autofocus="false">
Mostly we get to work around this because we deal with the JS property instead of the html attribute in angular, but we still need to deal with it for some HTML specific APIs like CSS as Nick mentioned, and other HTML like things.

We're moving forward here, non-breaking:

[attr.disabled.if]="isDisabled" == [attr.disabled]="isDisabled ? '' : null"`

(This is some-what similar to style.width.px, in-that it modifies the binding itself instead of toString)
It would have been nice to just do [attr.disabled]="isDisabled", but:

That's yet-another breaking change
It won't work properly in contexts like [attr.disabled]="checkA(thing)".

We can always revisit making this implicit in a future major release or behind a flag.

Closed in #1439.


Install-WindowsUpdate fails frequently on Azure VM

The following commands at the end of my script frequently fail, but not each time with the same error:
Install-WindowsUpdate -AcceptEula
if (Test-PendingReboot) { Invoke-Reboot }

Error 1:
Service 'Windows Update (wuauserv)' cannot be stopped due to the following error: Cannot stop wuauserv service on computer

Error 2:
Waiting for service 'Windows Update (wuauserv)' to finish starting...,    This command cannot be executed on target computer('BOX-2008-CORE') due to following error: A system shutdown is in progress.

I run this against an Azure VM based on image a699494373c04fc0bc8f2bb1389d6106__Win2K8R2SP1-Datacenter-201505.01-en.us-127GB.vhd, which is the latest of family Windows Server 2008 R2 SP1.
My full script does something like this:
# update chocolatey
cup chocolatey -y

# disable kickstarter message
(Get-Content "C:\ProgramData\chocolatey\chocolateyinstall\chocolatey.config") | ForEach-Object { $_ -replace "<ksMessage>true</ksMessage>", "<ksMessage>false</ksMessage>" } | Set-Content "C:\ProgramData\chocolatey\chocolateyinstall\chocolatey.config"

# install other programs
cinst git.install
cinst nxlog

# install powershell 4
Invoke-FromTask "cmd /c wusa.exe ${provisioningDataFolder}\Installers\Windows6.1-KB2819745-x64-MultiPkg.msu /quiet"-IdleTimeout 300

# update windows
Install-WindowsUpdate -AcceptEula

if (Test-PendingReboot) { Invoke-Reboot }

I'm betting that wusa.exe is restarting the computer around the exact same time that Install-WindowsUpdate is trying to start up the windows update service.
I would add /norestart to the wusa.exe call sothat it does not unexpectadly restart the machine. If the box does need a reboot after installing PS4, the Install-WindowsUpdate command should recognize that and do it.


Pickle the input value if it is a function

If Python function is used as the input of a task, we serialize it using pickle before saving it into the node.base.extras.

Codecov Report
Attention: Patch coverage is 80.00000% with 2 lines in your changes missing coverage. Please review.

Project coverage is 79.91%. Comparing base (5937b88) to head (204cd33).
Report is 44 commits behind head on main.

Files
Patch %
Lines

aiida_workgraph/engine/workgraph.py
75.00%
1 Missing :warning:

aiida_workgraph/utils/analysis.py
80.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #262      +/-   ##
==========================================
+ Coverage   75.75%   79.91%   +4.16%
==========================================
  Files          70       65       -5
  Lines        4615     4874     +259
==========================================
+ Hits         3496     3895     +399
+ Misses       1119      979     -140

Flag
Coverage Δ

python-3.11
79.91% <80.00%> (+4.24%)
:arrow_up:

python-3.9
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


HTTP Error 403 and 418 on add_url in paper-qa

When I try to add url in Doc, it gives me 403 and 418 for some URLs even though they are publicly available.
My code
docs = Docs(llm=llm_client)
for url in urls:
    try:
        docs.add_url(url)
    except Exception as e:
        print(f'Exception in adding URL {url}: {e}')

Examples for failed cases:
403 Forbidden Error:

https://dl.acm.org/doi/pdf/10.1145/3581783.3612034
https://bsj.uobaghdad.edu.iq/index.php/BSJ/article/download/7168/4295

418 Unknown Error:

https://ieeexplore.ieee.org/ielx7/6287639/10005208/10024290.pdf
https://ieeexplore.ieee.org/ielx7/6287639/9668973/09712284.pdf

Can someone kindly explain why is it happening for a few URLs but for others it works fine?

Many websites, especially publishers, will block requests that look like they arise from non-users (e.g., Python). You're seeing that here. You can try to research scraping to get the URLs in an automated way or you can just download them manually first and then use paths


Hw02 - Classes and Parameter/Return Passing techniques

Students are asked to develop a Point class in which they utilize various parameter passing techniques.

Sorry I did not get to this over the weekend:
I am looking at the instructions for Task 1.7 and it says to modify lines 41 & 43 on CMakeLists.txt. The Solution and the assignment I accepted via blackboard do not match on these two lines.


stable/external-dns oracle cloud infrastructure (oci) support

Can we get provider support for OCI?
We are currently utilizing the incubator for deployment to oci, and would like to use the helm chart if possible. Thanks!

Sure @srflaxu40 !! Thanks for the suggestion
I guess you're following this guide: https://github.com/kubernetes-incubator/external-dns/blob/master/docs/tutorials/oracle.md
Do you want to make the contribution to the chart yourself? I'd be glad to review your PR if you add support for OCI.
In case you're requesting the community to add it, I'd open a task and we'd try to work on adding this feature as soon as possible.


No source code here

May be a silly question, but I have to ask it: do you know in this repository there is not source code?

Yes I know :-)
I plan to refactor the code in order to make it open source, but I didn't have the time  and I haven't done it yet

Source code released. Enjoy :-)


SAK-50161 Remove mycalendar, myconnections, sitemembers, sitedescription

My opinion is do it. Remove them. Webcomponents would a be a way better way of doing this kind of thing anyway.


superset cache ignoring "current_user_id()" being used in SQL queries

Expected results
To show relevant data to currently logged in user, "current_user_id()" is being used in WHERE clause of SQL query. It should show data filtered by currently logged in user even if cache is used.
Actual results
It is showing results cached by the last logged in user from.
How to reproduce the bug

Create a dashboard/slices using the "current_user_id()" in WHERE clause of the query.
Log in as User A, it shows result filtered for User A.
Log in as User B, it still shows result filtered for User A (from cache).

Environment
(please complete the following information):

superset version: 0.30.0
python version: 3.6.8

Checklist
Make sure these boxes are checked before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.
 Masked URL: postgresql+psycopg2://XXXXXXXXX:XXXXXXXXXX@localhost:XXXX/XXXXXX
2019-10-28 15:30:58,159:INFO:root:Database.get_sqla_engine().  Masked URL: postgresql+psycopg2://XXXXXXXXXXXXXXXXXXX@localhost:XXXX/XXXXXX
2019-10-28 15:31:36,343:INFO:root:Database.get_sqla_engine(). Masked URL: postgresql+psycopg2://XXXXXXXXXXXXXXXXXXX@localhost:XXXX/XXXXXX
2019-10-28 15:31:36,397:INFO:werkzeug:<IP_ADDRESS> - - [28/Oct/2019 15:31:36] "GET /superset/dashboard/superset-cache-test/ HTTP/1.1" 200 -
2019-10-28 15:31:36,580:INFO:werkzeug:<IP_ADDRESS> - - [28/Oct/2019 15:31:36] "GET /superset/favstar/Dashboard/51/count HTTP/1.1" 308 -
2019-10-28 15:31:36,591:INFO:werkzeug:<IP_ADDRESS> - - [28/Oct/2019 15:31:36] "GET /csstemplateasyncmodelview/api/read HTTP/1.1" 401 -
2019-10-28 15:31:36,615:INFO:werkzeug:<IP_ADDRESS> - - [28/Oct/2019 15:31:36] "GET /superset/favstar/Dashboard/51/count/ HTTP/1.1" 401 -
2019-10-28 15:31:37,112:INFO:root:Cache key: 862c72a68170adca4ea48a48df000685
2019-10-28 15:31:37,119:INFO:root:Serving from cache
2019-10-28 15:31:37,123:INFO:root:Cache key: db13e84d6d9883b0655add7ce96da1ea
2019-10-28 15:31:37,125:INFO:root:Serving from cache
2019-10-28 15:31:37,129:INFO:werkzeug:<IP_ADDRESS> - - [28/Oct/2019 15:31:37] "POST /superset/explore_json/?form_data=%7B%22slice_id%22%3A817%7D HTTP/1.1" 200 -
2019-10-28 15:31:37,132:INFO:werkzeug:<IP_ADDRESS> - - [28/Oct/2019 15:31:37] "POST /superset/explore_json/?form_data=%7B%22slice_id%22%3A816%7D HTTP/1.1" 200 -
2019-10-28 15:31:38,276:INFO:werkzeug:<IP_ADDRESS> - - [28/Oct/2019 15:31:38] "POST /superset/log/?explode=events&dashboard_id=51 HTTP/1.1" 200 -

If you upgrade to the latest release (0.34.1), you can use cache_key_wrapper() to make sure your username is considered when calculating the cache key.

works fine on v0.34.1 with cache_key_wrapper(). Thanks


Use PR diff as base and revision

In a setup where you are tracking the oas.yaml in git, you would expect to check the diff in the context of a pull request. This means you automatically set the following:

base to the oas.yaml of the branch your pull request is on
revision to the oas.yaml of the last commit of your pull request

This is the behavior of other actions like https://github.com/kamilkisiela/graphql-inspector
Any thoughts?

Tried to do the same, unfortunately it's a deal breaker. Tried using checkout and supplying the path but it doesn't pick up changes. Tried giving it the blob url but doesn't play nicely with private repos

My solution to use the oasdiff library separately rather than this action. Probably not the most efficient code but does the basics that we need for now
    runs-on: ubuntu-latest
    name: Check out and try oasdiff
    steps:
      - name: Set up Go 1.21.6
        uses: actions/setup-go@v5
        with:
          go-version: 1.21.6
          check-latest: true
          cache-dependency-path: backend/go.sum
      - name: code-checkout
        uses: actions/checkout@v2
        with:
          sparse-checkout: api-docs
          ref: ${{ github.base_ref }}
          path: base
      - name: code-checkout
        uses: actions/checkout@v4
        with:
          sparse-checkout: api-docs
          ref: ${{ github.head_ref }}
          path: head

      - name: install oasdiff
        run: |
          go install github.com/tufin/oasdiff@latest
      - name: run oasdiff diff
        run: |
          oasdiff diff ${{ github.workspace }}/base/api-docs/openapi.yaml ${{ github.workspace }}/head/api-docs/openapi.yaml
      - name: run oasdiff changelog
        run: |
          oasdiff breaking ${{ github.workspace }}/base/api-docs/openapi.yaml ${{ github.workspace }}/head/api-docs/openapi.yaml -f githubactions
      - name: run oasdiff breaking changes
        run: |
          oasdiff changelog ${{ github.workspace }}/base/api-docs/openapi.yaml ${{ github.workspace }}/head/api-docs/openapi.yaml -f githubactions

It is possible to achieve this behaviour when you check out both the base and head branches in your GH action script.
I have managed to do it as follows:
`
const checkoutBaseBranch: Step = {
name: 'Checkout base branch',
uses: 'actions/checkout@v4',
with: {
ref: '${{ github.event.pull_request.base.ref }}',
path: 'base'
}
}
const checkoutHeadBranch: Step = {
name: 'Checkout head branch',
uses: 'actions/checkout@v4',
with: {
ref: '${{ github.event.pull_request.head.ref }}',
path: 'head'
}
}
const checkBreakingChanges: Step = {
name: 'Running OpenAPI Spec diff action',
uses: 'oasdiff/oasdiff-action/breaking@main',
with: {
base: base/${PATH},
revision: head/${PATH}
}
}
export default new Workflow(CHECK_OAS)
.on('pull_request', { paths: ... })
.addJob('check', {
steps: [
checkoutBaseBranch,
checkoutHeadBranch,
checkBreakingChanges
]
})
`


Translations update from Hosted Weblate

Translations update from Hosted Weblate for basxConnect/basxConnect Core.
It also includes following components:

basxConnect/basxConnect Contributions

Current translation status:

Due to consistency  I would prefer to have "Core" not be translated into the german word.


Applies to: other Dynamics products?

I accessed this page by following a link from an automated email about planned D365 for Finance and Operations. If correct, this page should be enhanced with instructions for systems other than D365 for Customer Engagement please.
Planned system maintenance
To: <removed>
Company Name: <removed>
LCS Project ID: <removed>
LCS Project Name: <removed>
Environment Name: <removed>
Environment Id:<removed>
We’ve scheduled Dynamics 365 for Finance and Operations for planned system maintenance. Your organization will experience a period of downtime within your region's maintenance window.
This planned system maintenance is to apply operating system level security updates.
Maintenance duration: 180 minutes
Maintenance window: 05 January 2019 03:00 UTC - 05 January 2019 06:00 UTC
Additional information: Planned maintenance window FAQ
Thank you for your patience while we do this. We want you to have the best possible Online Service experience and sometimes that means we need to perform maintenance activities. Our priority is always the health of your organization.
Please refer to the Office 365 Message Center for up to date information about maintenance activities. Going forward we will be moving maintenance notifications to the Office 365 Message Center for activities that do not impact your ability to access your Dynamics organization. If maintenance is required resulting in a short period of service interruption, we will send notification emails as well as post to Message Center. For additional information on accessing the Office 365 Message Center you can review Service Administrator Access <link to this page on docs.microsoft.com was here>  and install our Mobile Application.
Sincerely,
The Microsoft Dynamics 365 for Finance and Operations service team
Information about the communications your organization receives, and the recipients of these communications is contained in our Policies and Communications for Dynamics 365 article. For information regarding managing the recipients of those email communications, please refer to the Manage email notifications article.
This email was sent by an automated system. Please do not reply to this message. ©2018 Microsoft Corporation. All rights reserved.

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

ID: 2bc0e430-037c-c08a-3bb6-9ab04a16ce57
Version Independent ID: f51bb8e3-8263-45b5-e4e1-0b170906e124
Content: Use the Dynamics 365 for Customer Engagement apps (online) service admin role to manage your tenant
Content Source: ce/admin/use-service-admin-role-manage-tenant.md
Service: crm-online
GitHub Login: @jimholtz
Microsoft Alias: jimholtz

@NatIFD, Thanks for the suggestion. I have forwarded your suggestion to the Finance and Operations team.


WIP

Coverage remained the same at 36.858% when pulling 8c99cbcdc1d224111fae6220989a2c834f17caac on RickCarlino:weinre_updates into ec0566f11390f4566db1508fc857dae2cec1b222 on FarmBot:master.


python3: can't open file '/content/dalle-pytorch-pretrained/DALLE-pytorch/generate.py'

change
!wget "https://github.com/lucidrains/DALLE-pytorch/archive/refs/tags/0.14.3.zip" -O /content/
to
!wget "https://github.com/lucidrains/DALLE-pytorch/archive/refs/tags/0.14.3.zip" -O /content/0.14.3.zip

I am getting the same error.


A way to avoid scrollbars

Is there any way to avoid scrollbars on desktops when the content of my sidr are taller than the viewport?  I'd be happy if it either scrolled with the entire page/body, or just didn't have its own scrollbars.  As of now, its taking me back to the days of frames in websites, since it's displaying a scrollbar on the left side sidr and another scrollbar on the body content.

To further clarify a bit, what I'm wondering is is there a simple way to just have the off canvas portion the slides/overlaps in just scroll with the entire page as opposed to being fixed and limited by the height of the viewport?  (I've already moved my close menu button to within the menu itself, so regardless of scrolling it should be easy to close.)

Add overflow:visible to the element with a scrollbar.

Sorry for being late answering. Stackoverflow is better for doubts. You could customize it with a custom scrollbar library or probably do it with CSS + the Sidr API, something like:
overflow-y: visible;
position: absolute;
height: auto;
left: -260px;
This will not be added as a feature because it generates complexity and can be handle outside Sidr.


Incorrect weight copy in feature expanding while increasing tag size

In https://github.com/lancopku/pkuseg-python/blob/d581c95e3ddec3f236ebe74fd626b6e1cfe112ee/pkuseg/model.py#L25
While increasing n_tag such copy neglects the spacing, and simply put original weights at the ending side. This is inconsistent to the addressing method in _get_tag_tag_feature_id.

But thank goodness in raw cases people will expand  n_tag so this problem doesn't go explicit.


How to pass datasets info

Great feature, but how to pass dataset information in and out?

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

ID: a176f27b-f9fc-e0ff-0a48-aa42036051f2
Version Independent ID: d2356b83-3101-4b56-baaf-8bdf31e3bb57
Content: Run a Databricks Notebook with the Databricks Notebook activity in Azure Data Factory
Content Source: articles/data-factory/transform-data-using-databricks-notebook.md
Service: data-factory
GitHub Login: @nabhishek
Microsoft Alias: abnarain

@robert4os Thanks for the feedback. We are investigating the issue and will update you shortly.

@robert4os You can pass parameters using the settings tab in the Notebook activity as shown in the below screenshot :

Please refer to the steps mentioned in this doc for more info.

But there is no way to make use of pre-existing concepts in ADF, like Datasets? Say a ADF-dataset that refers to a storage location... it would be useful to pass this to Databricks, without manually channeling it through the parameters.

@robert4os You can pretty much send any information from a pipeline using the above mentioned way and by adding dynamic content in the parameters that you pass. You can basically create pipeline parameters and variables to hold these dynamic values to be passed and then pass them as mentioned above.

@robert4os I will now proceed to close this issue. Please feel free to still comment and tag me if you have any queries.


chore: remove DownloadFile definition

Moved to speakeasy-core since this method is used in CLI as well for remote URL support.

Closing this PR as we likely don't want to reference any private code in this public repo.


UNMET PEER DEPENDENCY<EMAIL_ADDRESS>

Fresh installation;
npm install<EMAIL_ADDRESS>
── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>invalid

npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.

@chilion may be you missed the steps. first run
 npm install npm@latest -g
this command will make sure to get the latest version
and then reinstall what you expected to install(because it is not yet installed) and no need to uninstall anything

I had the same problema and try run this code but dont work. The problem continue.

@hudjoubert  I think it's all about npm version :/

I ran into the same issue, but was able to get it installed using yarn.

@jacobhenke Can you please be a bit more specific on how you resolved this with yarn? I'm getting this error too, and have not been able to solve it yet.

If you have yarn installed already...
react-native init ProjectName
cd ./ProjectName
yarn add react-native-camera
npm link react-native-camera

When you use yarn to add react-native-camera, it DOES give you a warning about the version, but it seems to install it anyway, vs npm fails because of the version mismatch.
Hopefully this helps you!

Yea, I try do this, Really install even with notice, but when I run, the code don't work, so the problem continue.

I did

npm install npm@latest -g
npm prune
npm install react-native-camera
Worked for me!

As stated you need install latest react globally. This is not react-native-camera issue.

@prashantalhat
`Last login: Mon May  8 14:58:50 on ttys002
DuangLink-MacBook-Pro:AwesomeProject duanglink$ react-native -v
react-native-cli: 2.0.1
react-native: 0.44.0
DuangLink-MacBook-Pro:AwesomeProject duanglink$ npm install npm@latest -g
/usr/local/bin/npm -> /usr/local/lib/node_modules/npm/bin/npm-cli.js
/usr/local/lib
└──<EMAIL_ADDRESS>DuangLink-MacBook-Pro:AwesomeProject duanglink$ npm prune
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
DuangLink-MacBook-Pro:AwesomeProject duanglink$ npm install react-native-camera
<EMAIL_ADDRESS>/Users/duanglink/ReactNativeProjects/React-Native-Stable/AwesomeProject
└──<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.`

@prachil007
DuangLink-MacBook-Pro:AwesomeProject duanglink$ sudo npm install -g<EMAIL_ADDRESS>Password:
Sorry, try again.
Password:
/usr/local/lib
└──<EMAIL_ADDRESS>
DuangLink-MacBook-Pro:AwesomeProject duanglink$ npm install react-native-camera
<EMAIL_ADDRESS>/Users/duanglink/ReactNativeProjects/React-Native-Stable/AwesomeProject
└──<EMAIL_ADDRESS>
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.

This worked for me:

npm install npm@latest -g
npm prune
npm install --save<EMAIL_ADDRESS>npm install react-native-camera

install with yarn worked in my case.

npm install npm@latest -g
npm prune
npm install
worked for me! thank you for the tips!


[$250] Task – Broken image appears when assign task to non-existing user

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.81-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4609197
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause - Internal Team
Action Performed:

Go to https://staging.new.expensify.com/
Log in
Click on +/Assign task
Enter title and press Next
Assign task to non-existing user and press Confirm task

Expected Result:
Chat with task opens
Actual Result:
Broken image appears on the top of the chat when assign task to non-existing user
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/d1219e46-6af9-4208-bd88-2e3412ce7c5a
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01b79e3b17638011f0
Upwork Job ID:<PHONE_NUMBER>509974162
Last Price Increase: 2024-06-10

Issue OwnerCurrent Issue Owner: @fedirjh

@tgolen  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #vip-vsp

I wasn't able to reproduce this locally or on staging. I'm going to demote it for now.

OK, I'll just close this then. Thank you for confirming!


Python Assignment <2>

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
I added code to open and read the first file in the data set, calculate the mean, max and min flare up experienced by each patient and then detected patients with a mean inflammation score of zero.
What did you learn from the changes you have made?
I learned the importance of properly defining a path so that our code is able to access the right data in the right location.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
I thought of using the readline method like the homework suggested but went with the method that was shown in class when handling csv files.
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
It was a challenge setting up the functions because I wasn't always sure if I was assigning variables to the right expression.
How were these changes tested?
I checked these changes by running the code to see if the expected output is what I got.
A reference to a related issue in your repository (if applicable)
n/a
Checklist

[x] I can confirm that my changes are working as intended

Assignment marked.


hck: 0.7.0 -> 0.7.1

Motivation for this change
https://github.com/sstadick/hck/compare/v0.7.0...v0.7.1
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 147753 run on x86_64-linux 1

1 package built:

hck


Project Stage 1 Checklist

Project Stage 1 Checklist

[x] text is in C# and use .NET
[x] build succeeded
[x] all UT are green
[x] Object model representing process data
[x] Data layer is clearly stated using language terms only (no database of file access is required)
[x] Data API is abstract
[x] Logic layer is clearly stated using language terms only
[x] Logic API is clearly stated
[x] Logic uses only the abstract Data layer API
[x] Presentation layer is clearly stated using language terms only
[x] mvvm and xaml is applied to implement GUI
[x] rective and interactive programming is used
[x] Unit Test - layers are tested independently using abstract API
[x] Dependency injection (additional framework is not required)
[x] Mock is used for testing purpose (expected but not required)

Stage 1 passed


CIV-11543 case state and notify respondent

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/CIV-11543
Change description
Add upload translated claimant intention doc flow
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

In your ticket Kiera has Mentioned this point
Once documents are uploaded claimant should receive notification in uploaded documents flow, defendant should receive 2 notifications, one to inform them of claimant response, and another to inform them of uploaded documents
So you may have to add 1 more notification for defendant for 'Claimant Response.'

Thanks Neeta. I implemented that originally but then told Kiera that the notification task we have is for LR (sends to claimant solicitor email address). She said to omit that notification and she has created a ticket to cover it CIV-12364


[feat] Add auto fix feature to object-curly-spacing rule

With this you can run tslint with --fix option and all curly braces paddings will be fixed.

Thank you so much for the first fixer ever in this repo. I'll try to get the other PRs merged soon so that we can see where the CI is complaining. Looking forward to creating the fixers for the other rules now that you are showing the way to creating tests for them.

@aksyonov I have merged https://github.com/buzinas/tslint-eslint-rules/pull/173 which fixes the issues with the most recent typescript. Could you merge master to see if the PR is ok?

@jmlopez-rod I rebased my branch, ci should be ok now.

That's awesome, all tests are passing. Merging for now, I'll try to do a release once I finish with some of the other issues this weekend. Thanks again.

Thank you too, looking forward for a new release.


added shockwaves to the AssetDatabase; support for enemy weaknesses and weak points in the enemy proxy; Random.rotation value

Added PhysicalShockwave, PhysicalShockwaveHarmless, and PhysicalShockwavePlayer under the explosions heading in the AssetDatabase

I don't know if I did this correctly either.  I also seem to have a different file path for the Assembly-CSharp, so hopefully that doesn't make things too difficult.

Manually fixed the assembly references from within github.  Physically cannot stop it from adding a line break at the end.


Run error

jingle@jingle:~/Desktop$ app-outlet
[2060:0427/084910.798673:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /opt/App Outlet/chrome-sandbox is owned by root and has mode 4755.
追踪与中断点陷阱

We need more information about your system.

Which distro
which version
which app-outlet version
Which installation method (deb, AppImage, rpm)

We need more information about your system.

Which distro
which version
which app-outlet version
Which installation method (deb, AppImage, rpm)

deepin 20 beta    1.3.2   deb


ESP reboots if it cannot get ntp time

If ESP connects to access point and there is no internet (or cannot access ntp server) it reboots or stop working and needs reboot...

You are right, this is something I like to fix in a next release.


Requires an old version of Node

I'm trying to install the lib in my personal project but it seems require a very old node version:
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version "^16.14.0". Got "18.17.0"

I don't think it would be good to force a downgrade to version 16 of node


how to run  in   kubernetes

Hi, when disconf can  run in kubernetes  in someday?when disconf  can compatible with  kubernetes 。I expect  in someday.

Hi, when disconf can run in kubernetes in someday?when disconf can compatible with kubernetes 。I expect in some


Add hotkey feature to capture clip and save the clip to Temp directory

Hotkey is only working when I am running the program from terminal but not working when I have exported that as exe.
See: https://stackoverflow.com/questions/70082230/pyinstaller-hotkey-not-working-in-exe-with-pynput-module

Hotkey feature is only working with script not with the exe.


Implement #1143: custom culture/locale for documentation texts

As described, this allows the user to set a culture for documentation texts (such as summary texts for properties and constructors) in stylecop.json
Currently implemented:

[x] Add entry to settings file
[x] Property summaries (SA1623, SA1624)
[x] Constructor summaries (SA1642)
[x] Destructor summaries (SA1643)
[x] Resource file for de-DE
[x] Resource file for en-GB
[x] Resource file for es-MX
[x] Resource file for fr-FR
[x] Resource file for pl-PL
[x] Resource file for pt-BR
[x] Resource file for ru-RU
[x] Update configuration documentation

Current coverage is 96.77% (diff: 100%)

Merging #2198 into master will increase coverage by <.01%

@@             master      #2198   diff @@
==========================================
  Files           575        575
  Lines         77793      77806    +13
  Methods        3388       3389     +1
  Messages          0          0
  Branches       3008       3008
==========================================
+ Hits          75282      75295    +13
  Misses         1676       1676
  Partials        835        835

Powered by Codecov. Last update 09075ff...c2ce519

Alright, I think I'm done. I don't have much time left to test it in a real world scenario because I only have half an hour left before my weekend starts but so far it looks good.

I agree that this might become a problem. On the other hand, if no string is found in the selected locale, ResourceManager should automatically fall back to the default locale (en-US) so at least nothing will break. Whenever someone reports a missing translation we can assume they speak the language well enough to give us a suggestion.
We might also be able to contact the contributors of StyleCop/StyleCop from where all of the strings in my pull request were taken.

Another solution might be to just ship en-US, en-GB and de-DE for now and add the others if they get requested by someone who can maintain them.

Any updates on this?

@pdelvo @sharwell Guys? Any answer to my suggestions?

I think that we can maintain en-US, en-GB and de-DE for now. @vweijsters might be able to maintain nl-NL? I don't think we should include the other ones until we have someone that is a native speaker for that language.

I can definitely do nl-NL if there is interest in having it.

I can help with pt-BR

Okay, this is getting ridiculous... this MR is almost two months old and there has been hardly any activity from the project maintainers...

Hey guys, any update?

I'm playing catch-up on a few projects. Hoping to resolve many items including this one in the next two weeks.

Alright, I merged your changes. Looks good so far.


Upgrade to Chrome 41

Upgrade to Chrome 41
Upgrade to io.js 1.5.2

Some memory corruption is crashing the webview :(

@zcbenz If it repros on Windows you could turn on AppVerifier to try to catch it, you might get lucky

It turns out that it is caused by missing defines. Some APIs in render_frame.h are guarded by #if defined(ENABLE_PLUGINS), however brightray doesn't have ENABLE_PLUGINS defined, this resulted in a wrong declaration of RenderFrame and messed up everything when we call RenderFrame's methods.


Update console_bot.js for auto whitdraw and auto close alert box bot verification

this is my first time doing a pull request. I apologize if I did something wrong.

Does not seem like automatic withdrawal is a good idea. The website owner pays extra attention to only withdraw to real people so you need to contact them on twitter as well. Otherwise withdrawal never gets processed. Ill get this through to console_bot but i personally am using a different file - bot.js


[ruby] Fixed Pseudo-Variables as Literals

Although the parser rule for picking up pseudo-variables seems fine, it may sometimes choose to represent it as a local variable. This fixes this and adds the related tests.

it may sometimes choose to represent it as a local variable

That's very likely due to some ambiguity in the grammar spec. It might be beneficial (in the future) to remove the pseudo-variable rule in the parser if we end up needing to test it in the AST building phase anyway, so that the parser loses this ambiguity and becomes more responsive.


Every time on debugging the Threads panel comes back and gets the focus.

To me personal it would make more sense to give the output panel the focus on debugging.
The IDE doesn't remember the layouts, is there something wrong with my install or is there a setting that I overlooked?
I'm using FlashDevelop <IP_ADDRESS> for .NET 2.0 (master#f290597ff8) on Windows 7 Enterprise SP1 x86. As far as I remember earlier versions also didn't remember the layouts.
Any info on this will be greatly appreciated.
Thank you, Cornelis.

Fixed for FD5.


Import users from DfE Signin API

Currently, when users perform an action when logged in as an admin user, we record their DfE Sign-in ID against the action. This is just a plain UUID as a string, and, if we wanted to find out exactly who'd done something, we'd have to access the database, get the UUID and then check the DfE Signin API to get their user details.
As part of the process of displaying a user's name against actions that have been performed, this does three things:

Sets up a DfeSignIn::User model
Adds an endpoint to get all users from the DfE Sign-in API
Adds a class and job to add/update users at 2am every day

It also runs the add/update class as a data migration to ensure that we have all the users available when we deploy.
Once this is merged and deployed, we can then change existing updated_by columns from strings to proper UUID references.

 Display the name of the service operator who took an action

The way the DfE sigin UUID is saved as 'our' UUID is making me a little nervous - I struggled to see how we were storing it until you pointed it out to me, which made it a bit magical for a simpleton like me!
I think it's that we are using a third party bit of data as our own UUID here that worries me, I've tried to think through why that is and can't come up with too much concrete, I guess it's just in my jellies!?
I checked the UUID docs for Postgres and had a look at the DfE signin UUIDs and they seem to follow the RFC standard, but should we rely on that in our own system, what happens if for whatever reason we get a malformed or duplicate UUID back from DfE sigin, are we relying too heavily on DfE signin by baking this in to our application?
My train of thought led me to ask 'what is the alternative' and I guess it would be storing the DfE siginin UUID in it's own column and letting Postgres take care of our own UUIDs. I think I feel like although not as clever, it would make the code more accessible for someone like myself.
I was also thinking about the advantage of using the DfE UUID as our own, I can see how it would make fetching the name from the UUID super simple and it is really neat - but I do wonder if the 'magic' could happen in fetching the name rather than in how we store the DfE UUID?
What are your thoughts?

Nope, I'm totally with you. I don't think it makes much sense at all to use the same UUID, especially given they should be Universally Unique (the clue's in the name 😄). I'll tweak it so we have two IDs.

👍


Feature/two factor

Pull request checklist
Please check if your PR fulfills the following requirements:

[x] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[ ] Tests (npm run test) was run locally and all passed.
[x] Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type
Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[x] Documentation content changes
[ ] Other (please describe):

What is the current behavior?
Issue Number: N/A
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[x] No

Other information

This close #28


swift-aws-lambda-runtime and aws-swift-sdk: release build issue

I have also posted this on the aws-swift-sdk repo
https://github.com/swift-aws/aws-sdk-swift/issues/337
Describe the bug
When using swift-aws-lambda-runtime and aws-swift-sdk I get an error when building the package for release.
error: the Package.resolved file is most likely severely out-of-date and is preventing correct resolution; delete the resolved file and try again
I have tried deleting the Package.resolved file and the same error occurs.
To Reproduce
Steps to reproduce the behavior:
Here is my Package.swift file
// swift-tools-version:5.2
// The swift-tools-version declares the minimum version of Swift required to build this package.`

import PackageDescription

let package = Package(
  name: "sf-api",
  platforms: [
      .macOS(.v10_13),
  ],
  products: [
    .executable(name: "sf-api", targets: ["sf-api"]),
  ],
  dependencies: [
    .package(url: "https://github.com/swift-server/swift-aws-lambda-runtime.git", .upToNextMajor(from: "0.2.0")),
    .package(url: "https://github.com/swift-aws/aws-sdk-swift.git", from: "5.0.0-alpha")
  ],
  targets: [
    .target(
      name: "sf-api",
      dependencies: [
        .product(name: "AWSLambdaRuntime", package: "swift-aws-lambda-runtime"),
        .product(name: "AWSLambdaEvents", package: "swift-aws-lambda-runtime"),
        .product(name: "AWSDynamoDB", package: "aws-sdk-swift"),
      ]
    ),
  ]
)

Here is my build script
#!/bin/bash

set -eu

executable=sf-api
workspace="$(pwd)"

echo "-------------------------------------------------------------------------"
echo "preparing docker build image"
echo "-------------------------------------------------------------------------"
docker build . -t builder
echo "done"

echo "-------------------------------------------------------------------------"
echo "building \"$executable\" lambda"
echo "-------------------------------------------------------------------------"
docker run --rm -v "$workspace"/:/workspace -w /workspace builder \
       bash -cl "swift build --product $executable -c release"
echo "done"

echo "-------------------------------------------------------------------------"
echo "packaging \"$executable\" lambda"
echo "-------------------------------------------------------------------------"
docker run --rm -v "$workspace"/:/workspace -w /workspace builder \
       bash -cl ./scripts/package.sh
echo "done"

and package.sh script
#!/bin/bash

set -eu

executable=sf-api

target=".build/lambda/$executable"
rm -rf "$target"
mkdir -p "$target"
cp ".build/release/$executable" "$target/"
# add the target deps based on ldd
ldd ".build/release/$executable" | grep swift | awk '{print $3}' | xargs cp -Lv -t "$target"
cd "$target"
ln -s "$executable" "bootstrap"
zip --symlinks lambda.zip *

Full Output
./scripts/build-and-package.sh
-------------------------------------------------------------------------
preparing docker build image
-------------------------------------------------------------------------
Sending build context to Docker daemon  160.8kB
Step 1/2 : FROM swiftlang/swift:nightly-amazonlinux2
 ---> 0f45823328d8
Step 2/2 : RUN yum -y install      git      libuuid-devel      libicu-devel      libedit-devel      libxml2-devel      sqlite-devel      python-devel      ncurses-devel      curl-devel      openssl-devel      tzdata      libtool      jq      tar      zip
 ---> Using cache
 ---> 939f6ea94a42
Successfully built 939f6ea94a42
Successfully tagged builder:latest
done
-------------------------------------------------------------------------
building "sf-api" lambda
-------------------------------------------------------------------------
Fetching https://github.com/apple/swift-metrics.git
Fetching https://github.com/apple/swift-nio.git
Fetching https://github.com/swift-aws/aws-sdk-swift-core.git
Fetching https://github.com/swift-server/swift-backtrace.git
Fetching https://github.com/apple/swift-nio-extras.git
Fetching https://github.com/apple/swift-nio-transport-services.git
Fetching https://github.com/apple/swift-nio-ssl.git
Fetching https://github.com/apple/swift-log.git
Fetching https://github.com/swift-server/async-http-client.git
Fetching https://github.com/swift-server/swift-aws-lambda-runtime.git
Fetching https://github.com/swift-aws/aws-sdk-swift.git
Cloning https://github.com/swift-aws/aws-sdk-swift.git
Resolving https://github.com/swift-aws/aws-sdk-swift.git at 5.0.0-alpha.5
Cloning https://github.com/swift-server/swift-aws-lambda-runtime.git
Resolving https://github.com/swift-server/swift-aws-lambda-runtime.git at 0.2.0
Updating https://github.com/swift-server/swift-aws-lambda-runtime.git
Updating https://github.com/swift-aws/aws-sdk-swift.git
Updating https://github.com/apple/swift-metrics.git
Updating https://github.com/swift-server/async-http-client.git
Updating https://github.com/apple/swift-nio-transport-services.git
Updating https://github.com/apple/swift-log.git
Updating https://github.com/swift-server/swift-backtrace.git
Updating https://github.com/apple/swift-nio-ssl.git
Updating https://github.com/apple/swift-nio-extras.git
Updating https://github.com/swift-aws/aws-sdk-swift-core.git
Updating https://github.com/apple/swift-nio.git
Fetching https://github.com/apple/swift-crypto.git
Cloning https://github.com/swift-server/async-http-client.git
Resolving https://github.com/swift-server/async-http-client.git at 1.1.1
Cloning https://github.com/apple/swift-nio.git
Resolving https://github.com/apple/swift-nio.git at 2.19.0
Cloning https://github.com/apple/swift-nio-transport-services.git
Resolving https://github.com/apple/swift-nio-transport-services.git at 1.7.0
Cloning https://github.com/swift-aws/aws-sdk-swift-core.git
Resolving https://github.com/swift-aws/aws-sdk-swift-core.git at 5.0.0-alpha.5
Cloning https://github.com/apple/swift-metrics.git
Resolving https://github.com/apple/swift-metrics.git at 2.0.0
Cloning https://github.com/swift-server/swift-backtrace.git
Resolving https://github.com/swift-server/swift-backtrace.git at 1.2.0
Cloning https://github.com/apple/swift-crypto.git
Resolving https://github.com/apple/swift-crypto.git at 1.0.2
Cloning https://github.com/apple/swift-log.git
Resolving https://github.com/apple/swift-log.git at 1.3.0
Cloning https://github.com/apple/swift-nio-ssl.git
Resolving https://github.com/apple/swift-nio-ssl.git at 2.8.0
error: the Package.resolved file is most likely severely out-of-date and is preventing correct resolution; delete the resolved file and try again

Additional context
I have also tried the following package variations
 .package(url: "https://github.com/swift-aws/aws-sdk-swift.git", .branch("5.x.x"))
 .package(url: "https://github.com/swift-aws/aws-sdk-swift.git", .branch("swift-5.3-package-resolution"))

This is an aws-sdk-swift issue with the latest swift 5.3 amazonlinux2 docker images.