Paste into select2 is not working in IE when using select2 within  bootstrap modal

Prerequisites

[x] I have searched for similar issues in both open and closed tickets and cannot find a duplicate
[x] The issue still exists against the latest master branch of Select2
[ ] This is not a usage question (Those should be directed to the community)
[x] I have attempted to find the simplest possible steos to reproduce the issue
[ ] I have included a failing test as a pull request (Optional)

Steps to reproduce the issue

http://jsfiddle.net/o0d3vtek/66/

Expected behavior and actual behavior
Try to paste into select2, in IE. using ctrl+v
It works fine in other browsers, also works in IE when it is not used within a bootstrap modal.
Environment
Browsers

[ ] Google Chrome
[ ] Mozilla Firefox
[x] Internet Explorer

Operating System

[x] Windows
[ ] Mac OS X
[ ] Linux
[ ] Mobile

Libraries

jQuery version: 2.1.3
Select2 version: 4.0.2.rc1

Isolating the problem

[ ] This bug happens on the examples page
[ ] The bug happens consistently across all tested browsers
[ ] This bug happens when using Select2 without other pluigns
[x] I can reproduce this bug in a jsbin
http://jsfiddle.net/milz/o0d3vtek/2/

I Can Solve this problem by adding the line below:
$.fn.modal.Constructor.prototype.enforceFocus = function() {};

Duplicate of https://github.com/select2/select2/issues/600#issuecomment-102857595.


OPCPublisher disconnected due to Communication_Error

I am running OPCPublisher 2.7.199 on Windows VM Windows Container.
Frequently I get Communication errors. How to fix this? Do I loose data?
[12:37:38 INF Microsoft.Azure.IIoT.OpcUa.Edge.Publisher.Engine.DataFlowProcessingEngine]
DIAGNOSTICS INFORMATION for : opc.tcp://<IP_ADDRESS>:49310_cf9df0a198e2a4285a8571bb30a5d3b70493d245
Ingestion duration : 00:04:28:57 (dd:hh:mm:ss)
Ingress DataChanges (from OPC) : 13,232 (0.82/s)
Ingress ValueChanges (from OPC) : 1,137,593 (70.49/s)
Ingress BatchBlock buffer size : 0
Encoding Block input/output size : 0 | 0
Encoder Notifications processed : 1,137,636
Encoder Notifications dropped : 0
Encoder IoT Messages processed : 2,147
Encoder avg Notifications/Message : 530
Encoder avg IoT Message body size : 172,313 (66%)
Encoder avg IoT Chunk (4 KB) usage : 42.1
Estimated IoT Chunks (4 KB) per day: 494,281
Outgress Batch Block buffer size : 0
Outgress input buffer count : 0
Outgress input buffer dropped : 0
Outgress IoT message count : 2,147 (0.13/s)
Connection retries : 0
[12:37:54 INF Microsoft.Azure.IIoT.Module.Framework.Client.IoTSdkFactory] 4: Module dev-meg-iotdevice01_OPCPublisher_1 disconnected due to Communication_Error - now Disconnected_Retrying...
[12:38:09 INF Microsoft.Azure.IIoT.Module.Framework.Client.IoTSdkFactory] 4: Module dev-meg-iotdevice01_OPCPublisher_1 reconnected due to Connection_Ok.
[12:38:38 INF Microsoft.Azure.IIoT.OpcUa.Edge.Publisher.Engine.DataFlowProcessingEngine]
DIAGNOSTICS INFORMATION for : opc.tcp://<IP_ADDRESS>:49310_cf9df0a198e2a4285a8571bb30a5d3b70493d245
Ingestion duration : 00:04:29:57 (dd:hh:mm:ss)
Ingress DataChanges (from OPC) : 13,269 (0.82/s)
Ingress ValueChanges (from OPC) : 1,140,987 (70.44/s)
Ingress BatchBlock buffer size : 0
Encoding Block input/output size : 0 | 0
Encoder Notifications processed : 1,141,030
Encoder Notifications dropped : 0
Encoder IoT Messages processed : 2,154
Encoder avg Notifications/Message : 530
Encoder avg IoT Message body size : 172,265 (66%)
Encoder avg IoT Chunk (4 KB) usage : 42.1
Estimated IoT Chunks (4 KB) per day: 494,055
Outgress Batch Block buffer size : 0
Outgress input buffer count : 0
Outgress input buffer dropped : 0
Outgress IoT message count : 2,154 (0.13/s)
Connection retries : 0

Hey, please provide the full log file with debug log level.

Hey, please provide the full log file with debug log level.

Please find attached. Debug log level is Default.  Please let me know if you want me to set to different log level and also how to set the log level.
From: Monika Varshney<EMAIL_ADDRESS>Sent: Friday, January 15, 2021 4:07 AM
To: Azure/iot-edge-opc-publisher<EMAIL_ADDRESS>Cc: Annamalai, Subbu<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Azure/iot-edge-opc-publisher] OPCPublisher disconnected due to Communication_Error (#289)
Hey, please provide the full log file with debug log level.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/iot-edge-opc-publisher/issues/289#issuecomment-760876570, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQSD57PTYSQWT7O3QWHT6CLS2AOUZANCNFSM4WD4DQLA.

Please find attached. Debug log level is Default.  Please let me know if you want me to set to different log level and also how to set the log level.
From: Monika Varshney<EMAIL_ADDRESS>Sent: Friday, January 15, 2021 4:07 AM
To: Azure/iot-edge-opc-publisher<EMAIL_ADDRESS>Cc: Annamalai, Subbu<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Azure/iot-edge-opc-publisher] OPCPublisher disconnected due to Communication_Error (#289)
Hey, please provide the full log file with debug log level.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/iot-edge-opc-publisher/issues/289#issuecomment-760876570, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQSD57PTYSQWT7O3QWHT6CLS2AOUZANCNFSM4WD4DQLA.

OPCPublisher_1_20210114.log
Log level Default.  Please let me know if you would like to different log level and let me know how to set the new log level.

OPCPublisher_1_20210114.log
Log level Default.  Please let me know if you would like to different log level and let me know how to set the new log level.

Please provide edgeHub logs as well.

Please provide edgeHub logs as well.

EdgeHub re-authenticates all connected clients periodically, and if any of them have expired tokens, those connections are dropped. The IoTHub SDKs create tokens of 1 hour duration by default. So unless you are using your own SDK, or overriding the token duration, that would explain why the client connection is being dropped every hour.
But this behavior is completely normal – what is expected is that the client should immediately re-connect to EdgeHub and resume its activity. If the client is not re-connecting, that would be a bug in the SDK.
From the logs you provided, this is not a bug as reconnection is happening every hour and there is no data loss. Hope this helps.


Post man chaallenge point no added

https://github.com/GSSoC24/Postman-Challenge/pull/286#issuecomment-2254478541
@sanjay-kv  as you told on discord to make a direct PR whose postman challenge score is not counted so i am making ths same please check

I will merge it at night

Okay


guide how to use it in xml.

I want to implement this library for my app. but i am stucked howto use this as we have code view in doc but dont know how to make my recyclerview get cast to your library?

Watch the demo, there are multiple usage scenarios.


Add search operator to specify rotations.

This is based off of https://github.com/Alsciende/netrunnerdb/pull/414 by @opaldes.
I incorporated my feedback on the original PR and updated the syntax pages as well.
I picked this up because we haven't heard back for a while.
Partially addresses #309
(note that we already de-dupe to the latest card when multiples are present, so yo don't see some of the cards in the original core set)

Runner cards, 2017 rotation

Runner cards, 2018 rotation

Runner cards, 2019 rotation

cool, thanks @NoahTheDuke !  This is in better shape now.


Can you please host some Intune PRs for these?

I wrote some Intune Proactive Remediation Scripts so that these commands can be deployed properly from Intune.
https://github.com/AdamGrossTX/Toolbox/tree/master/Intune/Proactive Remediations/DefenderFirewallReportingAuditing

@denisebmsft Please merge this PR. Thanks


fix scikit dep

tested trivally, seems to work. also need to merge this onto other branches.

to test this, you can run the current workshop (you can use the "Test Workshop" link from https://sa-workshops.prod-3.eden.elastic.dev/), create a new requirements.txt using VSCode in /workspace/workshop/requirements.txt with the following:
matplotlib==3.8.1
numpy==1.23.5
pandas==1.5.3
torch==2.1.0
torchvision==0.16.0
tqdm==4.64.0
streamlit==1.30.0
#Add Custom worlshop packages below:
openai==1.3.9
elasticsearch==8.12.0
eland==8.11.1
transformers==4.35.0
sentence_transformers==2.2.2
python-dotenv==1.0.0
elastic-apm==6.20.0
inquirer==3.2.1
sentencepiece==0.1.99
tiktoken==0.5.2
cohere==4.38
elastic-apm==6.20.0
langchain==0.1.3
beautifulsoup4==4.11.2
scikit-learn>=1.2.2
scipy==1.11.4
elasticsearch-llm-cache==0.9.5
git+https://github.com/elastic/notebook-workshop-loader.git@main```

then open a VSCode terminal (swipe up from the bottom), cd to `/workspace/workshop`, and run `pip install -I -r requirements.txt` (this will force reinstall of all deps to what's in requirements.txt), and then run the workshop.


Date pipe with 'medium' format adds/truncates zero from single-digit hours and seconds

From @otaran on May 22, 2017 19:39
Steps to reproduce

Create date with hours < 10 and seconds < 10.
Display this date with date pipe and medium format:

@Component({
    template: `
})
export class DateComponent {
    now = Date.parse('2017-05-22T07:05:09Z');
}

Expected result
The date doesn't have leading zero in hours, has leading zero in seconds and has a comma after year: May 22, 2017, 7:05:09 AM (in UTC timezone).
Actual result
The date has leading zero in hours, doesn't have leading zero in seconds and doesn't have a comma after year: May 22, 2017 07:05:9 AM (in UTC timezone).
Notes
Plunker to demonstrate expected Angular behavior: https://embed.plnkr.co/eF8VFN/
Nativescript app to demonstrate actual behavior: tns-date-pipe.zip
Copied from original issue: NativeScript/nativescript-angular#815

@otaran thank you for reporting this one! After creating this test application I can confirm that indeed using Date pipe with format medium or mediumTime is not rendering the expected result.
example:

where now is the same as in the above example
now = Date.parse('2017-05-22T07:05:09Z');

From @otaran on May 23, 2017 14:16
@NickIliev thanks for verifying this! Should I report this issue to nativescript-intl project?

@otaran indeed this appears to be a limitation coming from nativescript-intl plugin. Currently, you can use all other Date pipes apart from medium and mediumTime where the issue with the seconds appears.

@NickIliev just FYI this issue is reproducible on both Android and iOS.


Add comments for Manually Merged feature

In case I would forget it again one day .....

.

.

.


Add API functionality to obtain full output file path for each result

Currently, binwalk doesn't provide any API mechanism to obtain the output file path for a given signature match result, because the extract.conf file allows any command to be executed with unpredictable effect on the extraction directory state.
This is problematic in a number of ways, for example, extractor.py:427 attempts to guess at the output file name in order to prevent deletion of a preexisting file, but is not necessarily always correct. Likewise, extractor.py:450 attempts to clean up the output result if it is an empty file, but doesn't account for e.g. an empty squashfs-root directory.
In order to resolve this, I propose to add another field to the rule file format in extract.conf that can be used to encode the output file name. For example, %d could be used to indicate that the output is equivalent to splitext(%e)[0]. Any existing commands that use the %% placeholder could have the %%<path>%% field moved to this new field, and replaced with another placeholder such %o. These new rules would be similar to the following examples:
^lzma compressed data:7z:%d:7z e -y '%e':0,1
^squashfs filesystem:squashfs:%%squashfs-root%%:unsquashfs -d '%o' '%e':0:False

Although this would open up a potential race condition between the pre-existing file check at extractor.py:427 and the actual extraction at extractor.py:433, since the extraction operation is not security sensitive, and these two operations are quite close together, I feel like this is not an issue.

This could work, but I'm hesitant to keep adding things to the rules file, they've already gotten more complex than I ever originally intended. Since binwalk relies on external utilities for most extraction, there is also no guarantee that all future extraction utilities will support an output file/directory option, so I'd rather a more generic solution (granted, this would be unlikely).
The problems mentioned in extractor.py are legitimate, but the reason for that code was primarily due to the large number of false positive LZMA results, which resulting in huge numbers of 0-size files. With the (semi-)recent updates which drastically improve LZMA signatures, it is no longer needed.
As such, the --rm feature is still available, but it no longer removes 0-size files. It also does not remove the original file if its MD5 hash has changed after running an extractor.
Further, a full list of both carved (i.e., files dd'd out of the firmware by binwalk) and extracted (i.e., files created by extraction utilities) are now available via the API (see the API documentation for an example).


Add additional methods to SourceSet providers based on name

Expected Behavior
Providers created from SourceSetContainer contain additional methods for retrieving values derived from the name, perhaps from subclassing or extending NamedDomainObjectProvider<SourceSet>.
Current Behavior (optional)
No response
Context
Given that a SourceSet contains methods like getApiConfigurationName() that appears to be only derived from the name of the SourceSet, perhaps providers of SourceSet should have additional methods so that we have something like this:
interface SourceSetProvider : NamedDomainObjectProvider<SourceSet> {
    val apiConfigurationName: String
    val classesTaskName: String
}

fun ConfigurationContainer.getApiConfiguration(sourceSet: SourceSetProvider) = named(sourceSet.apiConfigurationName)
fun TaskContainer.getClassesTask(sourceSet: SourceSetProvider) = named(sourceSet.classesTaskName)

Suppose you have this:
val sourceSet: NamedDomainObjectProvider<SourceSet> = sourceSets.named("main")

Normally, you can only extract its name without calling get(). However, a SourceSet has a bunch of properties that appear to be derived from only its name - for example, apiConfigurationName. It would be great if the Gradle API were to be expanded so that SourceSetContainer would return a specific subinterface of Provider that exposed those names:
val sourceSet: SourceSetProvider = sourceSets.named("main")
val apiConfigurationName: String = sourceSet.apiConfigurationName

Which, of course, could lead to an extension method on ConfigurationContainer:
fun ConfigurationContainer.api(sourceSet: SourceSetProvider): NamedDomainObjectProvider<Configuration> = named(sourceSet.apiConfigurationName)

Similarly for task names derived from source sets, but for TaskContainer, of course.

Thanks for the more detailed explanation, but what is the original problem you are trying to solve? Why do you need sourceSet.apiConfigurationName in the first place?

This was an artifact about building a new feature variant where the feature variant's configurations needed to be manually wired to extend their counterpart from the main source set:
val myFeature by sourceSets.registering
java.registerFeature(myFeature.name) { ... }
configurations.named(myFeature.get().compileClasspathConfigurationName) {
    extendsFrom(configurations.compileClasspath)
}

Something like that. (Not actually asking for such work to be wired on our behalf, because there's probably a legitimate use case where you don't want that out of a feature variant.)

This issue needs a decision from the team responsible for that area. They have been informed. Response time may vary.

I think this is a more general container/Provider question.  In general, I think we want higher level models, so that it's not necessary to look up things by name at certain points in time.
e.g., the example might become:
jvmLibrary {
   features {
       val myFeature by registering {
             extendsFrom features.main
       }
   }
}

I've added this to our configuration-model label so it can get attention later.


Updated the Caddyfile for use with wordpress

I updated the PR but I did leave the root directive with an angled bracket note saying to put your own wordpress directory in there.

Thanks!! :100:


Autocomplete activation event onWebviewPanel

This PR fixes #139564
How to Test

Open a VSCode extension project
In the package.json file, under "activationEvents", start typing onWebviewPanel.
Hit Ctrl+Space for IntelliSense to show recommendations

You should see the onWebviewPanel in the recommendations as well as a description.

Thanks!


[UnexpectedToken]: Transform function returned a code string got a BABEL_PARSER_SYNTAX_ERROR

Describe the bug
Recently I tried to use this plugin to replace the the lodash used by dependencies  with lodash-es all over the codebase. I tried to return an AST Node before, which would be wrapped with parentheses and you'v fixed it in https://github.com/sxzz/unplugin-ast/issues/22, then I tried to return the code string directly, which still failed. Could you please help me out?
I have made a reproduction at codesandbox
WebpackAstPlugin({
  include: [/\.[jt]sx?$/],
  transformer: [
    ({
      onNode: node => node.type === 'VariableDeclaration'
        && node.declarations?.[0].type === 'VariableDeclarator'
        && node.declarations[0].init?.type === 'CallExpression'
        && node.declarations[0].init.callee?.name === 'require'
        && node.declarations[0].init.arguments[0]?.type === 'StringLiteral'
        && /lodash\/\w+/.test(node.declarations[0].init.arguments[0]?.value),
      transform(node) {
        const originNode = node.declarations[0].init;
        const importer = originNode.arguments[0].value;
        const importSource = importer.replace('lodash', 'lodash-es');
        const code = `var ${node.declarations[0].id.name} = require('${importSource}').default;`;
        console.log(code); // var isNull = require('lodash-es/isNull').default;
        return code;
      },
    }),
  ],
})

Reproduction
https://codesandbox.io/s/unplugin-ast-bug-reproduction-w4np5f?file=/vue.config.js
System Info
System:
    OS: macOS 13.0.1
    CPU: (8) arm64 Apple M2
    Memory: 79.88 MB / 8.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.11.0 - ~/.nvm/versions/node/v18.11.0/bin/node
    Yarn: 1.22.19 - ~/Library/pnpm/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.11.0/bin/npm
  Browsers:
    Chrome: 107.0.5304.110
    Safari: 16.1

Used Package Manager
pnpm
Validations

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

Fixed in<EMAIL_ADDRESS>

So fast🤣


Client API update

This PR updates the API of Spine web client.
Now, the API is a bit more flexible and tries to mimic the new Java API where appropriate.
In general, the new API looks as follows:
// Query.
client.select(Customer.class)
      .byId(westCoastCustomerIds())
      .withMask("name", "address", "email")
      .where([Filters.eq("type", "permanent"),
              Filters.eq("discount_percent", 10),
              Filters.eq("company_size", Company.Size.SMALL)])
      .orderBy("name", OrderBy.Direction.ASCENDING)
      .limit(20)
      .run(); // The returned type is `Promise<Customer[]>`.

// Subscription to entities.
client.subscribeTo(Task.class)
      .where(Filters.eq("status", Task.Status.ACTIVE))
      // Additional filtering can be done here.
      .post()
      .then(({itemAdded, itemChanged, itemRemoved, unsubscribe}) => {
          itemAdded.subscribe(_addDisplayedTask);
          itemChanged.subscribe(_changeDisplayedTask);
          itemRemoved.subscribe(_removeDisplayedTask);
      });

// Subscription to events.
client.subscribeToEvent(TaskCreated.class)
      .where([Filters.eq("task_priority", Task.Priority.HIGH),
              Filters.eq("context.past_message.actor_context.actor", userId)])
      .post()
      .then(({eventEmitted, unsubscribe}) => {
          eventEmitted.subscribe(_logEvent);
      });

// Command.
client.command(logInUser)
      .onOk(_logOk)
      .onError(_logError)
      .observe(UserLoggedIn.class, ({subscribe, unsubscribe}) => {
          subscribe(event => _logAndUnsubscribe(event, unsubscribe));
          setTimeout(unsubscribe, EVENT_WAIT_TIMEOUT);
      })
      .observe(UserAlreadyLoggedIn.class, (({subscribe, unsubscribe}) => {
          subscribe(event => _warnAboutAndUnsubscribe(event, unsubscribe));
          setTimeout(unsubscribe, EVENT_WAIT_TIMEOUT);
      })
      .post();

Notable changes

The client now allows to observe the events that are the immediate result of handling the posted command. This can be done using the observe method, in a similar way to the example above. Note, that in the example we make sure the event subscriptions are always cancelled, even if the event of the corresponding type is never received. This can be done in some other way but all the subscriptions created with observe should be cleaned up manually.

The event subscriptions will now always write spine.core.Event instances to the Firebase database and always receive spine.core.Event instances instead of event messages on the client, in the subscription objects.

A service which keeps the active subscriptions "alive", will no longer ignore the erroneous response received from the server. If the subscriptions can't be "kept-up", it will be removed from the list of active subscriptions and the "keep-up" requests will no longer be sent for it.

The entity subscription will now be notified about the no-longer-matching objects with the help of itemRemoved callback. Previously, it was done with the itemChanged callback with null body, which raised some problems when it was necessary to identify the object which stopped matching the subscription.

Changes to the old API
Removed

Client.fetch(...) - please use Client.select(...).byId(...).run() instead;
Client.subscribe(...) - please use Client.subscribeTo[Event](...).byId(...).post() instead.

Renamed

Client.subscribeTo(Topic) -> Client.subscribe(Topic).

Deprecated

Client.execute(Query) - please use Client.read(Query) instead;
Client.sendCommand(...) - please use Client.command(...).onOk(...) ... .post() instead.

All other API remains intact.
Other
Spine version advances to 1.2.9.

@dmdashenkov PTAL.
The coverage is low because the changes are mostly covered by the integration tests which do not count towards coverage.

@dmdashenkov PTAL again.

@dmdashenkov PTAL again.


Add Pull Request Support for BitBucket

With https://github.com/amazeeio/lagoon/commit/5cee6b71e29bfea3c26c53c8ea9f93fac6c3d3ba and https://github.com/amazeeio/lagoon/commit/def96065f51c4b92e6dcd22a9cb4afc47b02ea76 we have pull request support for GitHub.
Now we would also need it for BitBucket.

This would be nice!

We definitely like this to be implemented ! (since our company wide versioning system is only bitbucket)

Closing this was released in - https://github.com/amazeeio/lagoon/pull/539


[WIP] Fixes to the CI document

Various fixes to the CI document.
Replaces #1556
Fixes #1454

Stand-by ... I'll see if I can get that failure fixed.

@mairaw Stand by on this one for a sec. I'm doing a Rex Tune-up:tm: on it. One more pass on it when I get back from the :muscle:, and it will be ready for a look.

@mairaw I'll probably give it one more peek in the morning, but it's good enough now for a 1st draft look :eye::eye:. The PS script works, but I haven't tried the bash script. I should be able to give that a quick test here, so I'll do that in the morning just to make sure it doesn't :boom:.

@mairaw Yes, the bash script required a touch of work, too. There's a question there tho on a problem at the end of the script getting the path to dotnet stored into a var for later use. Who is our go-to for bash-related questions?
Except for the little bash problem, this is ready for :eyes:.

@mairaw @rpetrusha Nice ... a little extra polish on this last pass. It's ready for :eyes: now.


Show percent processed when churning through chunks

Big wav files take a long time to process.   A simple percentage complete display instead of flooding the screen with Processing...

Thank you for your contribution! The code structure has changed now due to new version. Your name was added to the "Thanks" section. Thank you again!


Updating coveralls to 3.0.0

Please update coveralls to version 3.0.0.
If this passes your tests you can merge it in.  If not please use this branch for changes.

2ed4d09 major version bump for node > 4.x
5ebe57f bump version
428780c Expand allowed dependency versions to all API compatible versions (#172)
eb1b723 Update Mocha link (#169)
b9032a1 better Jenkins detection
2821200 version bump
ef7e811 Parse commit from packed refs if not available in refs dir. (#163)
e476964 Merge pull request #162 from evanjbowling/patch-1
63a7f92 Update README.md
d571dac merge, version bump
8dfcfd6 version bump
4bc93ac Merge branch 'master' of github.com:nickmerwin/nod…
671acca removed codeship badge
1575050 branching WIP
f390392 Merge pull request #152 from ndaidong/master

See the full change log for everything that changed in this release.

Coverage remained the same at 97.382% when pulling 6f88ec0b50b532a25a3b71b21bff822cbd1fefe4 on bithound.coveralls.3.0.0 into f547076bfc25f30d7e569dde4f1ef893bc3ee6fa on master.


Allow adding custom headers

For some OGC services I need to add a custom header for authorization. However, currently it does not seem possible with this library to add a custom header. I guess a change needs to be done here: https://github.com/camptocamp/ogc-client/blob/main/src/shared/http-utils.ts
I can try to provide a fix. If you have any hint or preference how to implement it, please let me know.

Very good point. To me the following optional parameters would be relevant:

headers: a dict of headers by name and value
mode: either cors, no-cors, or same-origin
credentials: either omit, same-origin or include
referrer: a string

Taken from https://developer.mozilla.org/en-US/docs/Web/API/fetch#parameters

I found out that OpenLayers has a WMS parser as well that is enough for my purposes: https://openlayers.org/en/latest/examples/wms-capabilities.html
There I can provide custom headers.
That's why, for the moment, I will not use ogc-client for this task anymore. Hence, I also do not plan to make a PR anymore. Sorry for the confusion.
Thanks anyway for the great library 🎖

Thanks, leaving this open because this is still relevant!

@jahow another option to implement this, would be to allow to hand over custom fetch instances. (see https://rapidapi.com/guides/interceptors-fetch )
It might be easier to implement, because all HTTP stuff can be configured in fetch, whereas this library just does stuff within the OGC API world ...

Hmm, interesting. Maybe instead of having to provide a full fetch instance we could offer a pre-process and post-process hook. The issue I see is that this will not be possible in the worker, so using these hooks would need to disable worker usage altogether.
So I guess at first it would be reasonable to take in an options object for each layer, as this is at least serializable.

@jahow your suggestion sounds good as well.


Is it compatible with Xcode Cloud

Can it be used normally on Xcode Cloud? Because it uses a plugin to generate code, I've encountered issues with other repositories where I didn't have write permissions on Xcode Cloud, which prevented the code from being generated normally. [Link to GitHub issue]
Thanks for any reply

@leecaa yes, it’s possible. But as you noted, it requires permissions. This post on the developer forums explains how to get the plugin working in Xcode Cloud: https://developer.apple.com/forums/thread/732893.
Hope this helps.


chore: import repository https://github.com/xwang2713/jxv3-quickstart-py.git

this commit will trigger a pipeline to generate the CI/CD configuration which will create a second commit on this Pull Request before it auto merges

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Blank search results sometimes

BookStack Version: 0.20.0 (Docker)
PHP Version: 7.1.10 (Apache, Docker)
MySQL Version: 10.2 (MariaDB, Docker)
I am running all of this with Docker using the docker-compose.yml file from solidnerd/bookstack, only changing from mysql to mariadb.
Expected Behavior
Search results. Either some or zero. Example when searching "ips"
Current Behavior
No results at all; blank search area. Example when searching "ip"
Window will quickly show some results, but then immediately change to being blank and the error is thrown.
Steps to Reproduce
Inconsistent... appears to happen with certain words, but acts differently for another user at my workplace. (eg: Searching "user" fails, but "user to ips" also fails)
Here is the error that gets thrown in the console when I perform a search that fails.
common.js?version=v0.20.0:23 ReferenceError: NAME is not defined
    at At.eval (eval at Zi (common.js?version=v0.20.0:25), <anonymous>:2:14293)
    at At.e._render (common.js?version=v0.20.0:25)
    at At.r (common.js?version=v0.20.0:23)
    at da.get (common.js?version=v0.20.0:25)
    at new da (common.js?version=v0.20.0:25)
    at Ee (common.js?version=v0.20.0:23)
    at At.$mount (common.js?version=v0.20.0:25)
    at At.$mount (common.js?version=v0.20.0:25)
    at At.e._init (common.js?version=v0.20.0:25)
    at new At (common.js?version=v0.20.0:23)

If I search for the word "user" it says this instead.
common.js?version=v0.20.0:23 ReferenceError: USER is not defined
    at At.eval (eval at Zi (common.js?version=v0.20.0:25), <anonymous>:2:14450)
    at At.e._render (common.js?version=v0.20.0:25)
    at At.r (common.js?version=v0.20.0:23)
    at da.get (common.js?version=v0.20.0:25)
    at new da (common.js?version=v0.20.0:25)
    at Ee (common.js?version=v0.20.0:23)
    at At.$mount (common.js?version=v0.20.0:25)
    at At.$mount (common.js?version=v0.20.0:25)
    at At.e._init (common.js?version=v0.20.0:25)
    at new At (common.js?version=v0.20.0:23)

I have the same issue with docker container, most searches return for half a second the results and then the blank page remains. In fact, research is unusable.

@IAreKyleW00t Looking into this I think it may be a case of the search results clashing if containing vue syntax.
Do you have any text in your pages that matches {{USER}} or {{NAME}} including the braces?

I think not have pages  that matches {{USER}} or {{NAME}}.
The change made works correctly now in searches. Thank you for finding and fixing this annoying bug that did not allowed to properly use the search. Thank you, great project!

@alegiovannelli Thanks for confirming.
I'll close this now that v0.20.1 has been released with the likely fix.
@IAreKyleW00t Feel free to request this to be re-opened if you don't find the issue fixed after updating.


Fixes issue where transparent brushes were invisible in Quest passthrough mode.

I can't figure out where I got the idea setting eyeFovPremultipliedAlphaModeEnabled to false was necessary when I implemented the passthrough brush. I was following a tutorial or some docs but I can't find the source now.

I restored the deleted branch, but it was just in this commit:
commit 1513027a4e41882954bcab8188c3ccb8926ed4e2 (feature/backdrop-passthrough-settings)
Author: Andy Baker<EMAIL_ADDRESS>Date:   Sat Dec 9 10:42:06 2023 +0000

    First stab at a passthrough brush

No particular explanation there either :-/


Update top-level readme with active Alpha engagements

Signed-off-by: Michael Scovetta<EMAIL_ADDRESS>

Approving


reshape not working properly

This test is not passing:
    val dense = DenseMatrix(
        DenseVector(1D, 2D, 1D, 2D, 1D, 2D),
        DenseVector(3D, 4D, 3D, 4D, 3D, 4D))

    val reshaped = dense.reshape(6, 2)
    val expected = DenseMatrix(
        DenseVector(1D, 2D),
        DenseVector(1D, 2D),
        DenseVector(1D, 2D),
        DenseVector(3D, 4D),
        DenseVector(3D, 4D),
        DenseVector(3D, 4D))

    Assert.assertEquals(expected, reshaped)

Result in Breeze is:
1.0  2.0
3.0  4.0
2.0  1.0
4.0  3.0
1.0  2.0
3.0  4.0

NumPy works fine:
>>> import numpy as np
>>> dense = np.array([[1,2,1,2,1,2], [3,4,3,4,3,4]])
>>> dense.reshape(6,2)
array([[1, 2],
       [1, 2],
       [1, 2],
       [3, 4],
       [3, 4],
       [3, 4]])

I'm using: org.scalanlp:breeze_2.11:0.13.2

Breeze uses column major ordering while NumPy uses row major ordering (read more about these orderings here). The major ordering determines how values will be ordered in operations like reshape.

So maybe the bug is in the cheat sheet, because the behavior of numpy reshape is different from breeze reshape.


Added relevant documents section, and bibtex entries

Added relevant docs, bibtex entries.
May be good to start citing our documentation rather than hyperlinking them.

closes #181

there is a small formatting issue with where the references are placed probably add \newpage on line 507
\bibliographystyle{plainnat}

\bibliography{../../refs/References}

\newpage

added


Review draft guidance on subtitles and colour and iterate

Rich Kelly has drafted some guidance.
Tasks

[x] Review and consider including it in the accessibility guidance:
https://github.com/nhsuk/nhsuk-service-manual-community-backlog/issues/347#issuecomment-878137153
[x] Sara to make content changes
[x] Run it by Leigh and Alistair
[ ] Publish

This guidance as it stands looks great as a starting point.
I think there's more guidance we can add in due course but we can add this later.

I've reopened this Karl as I need to do the content review. I'll take your name off though.

With Leigh, Alistair and @mcheung-nhs for review.

Approved by Leigh and Michael.
@danjohnstonUX, would you mind casting your eye over this on review/1-subtitles please? Just to make sure all looks OK from a design point of view. If you're happy with it, it's ready to release.

Ready for release.


Loudness limitation in marimbabor_behaviour

When we try to decrease loudness level, robot performs well and hits slower to the bars.
However, when we tried to increase loudness level all the way, robot does not increase loudness as its maximum.
Possible reason : in interpreter.py, note.velocity is devided by 127 regardless. and that result is passed into hitsequenceelement to perform planning.

in prettyMIDI library, notes have a velocity (volume) from 1 to 127, from quietest to loudest. In that case we need to investigate this constant division.

Haven't had time to investigate yet

code was modified and tested, issue fixed. See #242


Ability to have dynamic scenarios

I am currently looping through all possible values for a dropdown and filling out the form associated with each value. I'd like each case to be a separate scenario so that one failure doesn't cause my test suite to fail. I just want that particular dropdown value to fail and keep going.
Something like this:
for (let i = 0; i < dropdown.length; i++) {
 Scenario(dropdown[i], function() {
     //do stuff and test this dropdown value's dynamic form. If it fails, go to next scenario
 });

}

I think you can actually try to generate Scenarios dynamically the way you proposed in code. Did you try to do that?

@DavertMik you are completely right...I was looping through values which I was setting in a previous scenario so I had to do some shifting and put everything I wanted to set in an _init() call, but it worked.


🍒[5.10][Distributed] Generic reqs must be forwarded to accessor from enclosing actor

Issue: Without this change, in debug builds the requirement machine validation infra would crash to compile. This prevents advanced Distributed Actors users with lots of generics from using NIGHTLY builds. Stable builds have this assertion turned off.
Description: If we don't do this, the generic parameter has no requirements at all, which a) is incorrect to begin with, it should have the exact same signature as the method it is the accessor for, and b) it would trip up verification which is enabled on linux in snapshot builds -- causing crashes.
Affected versions: All the way since initial introduction, but ONLY in debug builds -- i.e. nightly snapshots on linux. Released stable Swift versions don't have this assertion and would "happen to work".
Risk: Low, this only adds missing requirements to distributed function accessors which is the correct thing to do. Missing them "worked by accident".
Review by: @slavapestov @xedin
Testing: CI testing; verified manually on reproducer project provided in issue
Radar: rdar://115497090
Original PR: https://github.com/apple/swift/pull/68859
Resolves https://github.com/apple/swift/issues/68517

@swift-ci please test

Friendly ping - if possible we'd like to be able to tests nightly toolchains on Linux too :-)

@swift-ci please test

Seems the original PR made it but the cherry pick not; let's fix that.


Problem Using .html Extension

Hi, i have problem when changing ext option from .ect to .html.
The error is "Failed to lookup views..."

Works for me
var ectRender = require("ect")({watch : true, root : path.join(__dirname, 'views'), ext : ".html"});
app.set("view engine", "html");
app.engine("html", ectRender.render);


Fix CI dependency problem

Pandas causes problems in containers and must be fixed to run successfully CI workflow.

Solved this by moving pandas from pip to Alpine's local dependencies.


Build lxml for WebAssembly

emscripten-forge

[ ] https://github.com/emscripten-forge/recipes/issues/311
[ ] https://github.com/emscripten-forge/recipes/pull/326

pyodide

[x] built-in package

JupyterLite

[ ] Provide test evidence (notebook/screenshot, etc.)

Compare the Pyodide lxml recipe: pyodide/packages/lxml


ActionMenu keyboard navigation: opening the dropdown menu does not focus the first item

When a user opens the ActionMenu dropdown by pressing enter or space, none of the menu items have focus.
After pressing arrow down, the focus will start to move between items. Then when closing and reopening the menu, the index of the focused item is the same as when the menu was closed. So if the second item is focused and the menu is closed, upon re-opening the menu the second item will be focused instead of the first.
It seems that for each ActionMenu on the page, the "index" of the focused item is not reset after closing the menu. I believe the expected behavior is that the first item should always have focus after opening the dropdown.
Screen recording
https://github.com/primer/view_components/assets/15002980/676292ae-3a77-47c4-970b-77348e6188f0

Hey @keithamus, can you take a look at this one? Not sure what's going on here, as we specifically have a test for this.

#2002 fixed this, I forgot to add the ref. This can be closed, as https://github.com/primer/view_components/releases/tag/v0.1.9 has the fix.


Hook for left column in task form

Added hook 'template:task:form:right-column'
Could be useful for default form customization.

relates to #234


Test failure: ServerThrowsHubExceptionIfStreamingHubMethodCannotBeResolved

This test fails occasionally with the following error:
System.Exception : 1 error(s) logged.
Microsoft.AspNetCore.Http.Connections.Client.Internal.LongPollingTransport - ErrorPolling - RVwH3zULmhl9KAICdQuEZQ - Error while polling 'http://<IP_ADDRESS>:50262/dynamic?id=RVwH3zULmhl9KAICdQuEZQ'.
===================
System.NotSupportedException: Stream does not support reading.
   at System.IO.Stream.CopyToAsync(Stream destination, Int32 bufferSize, CancellationToken cancellationToken)
   at System.Net.Http.DelegatingStream.CopyToAsync(Stream destination, Int32 bufferSize, CancellationToken cancellationToken)
   at System.Net.Http.StreamToStreamCopy.CopyAsync(Stream source, Stream destination, Int32 bufferSize, Boolean disposeSource, CancellationToken cancellationToken)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Net.Http.HttpContent.<LoadIntoBufferAsyncCore>d__49.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Net.Http.HttpClient.<FinishSendAsyncBuffered>d__58.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Http.Connections.Client.Internal.LongPollingTransport.<Poll>d__19.MoveNext()
===================
   at Microsoft.AspNetCore.SignalR.Tests.VerifyNoErrorsScope.Dispose()
   at Microsoft.AspNetCore.SignalR.Tests.ServerLogScope.Dispose()
   at Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.<ServerThrowsHubExceptionIfStreamingHubMethodCannotBeResolved>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
------- Stdout: -------
| [0.001s] TestLifetime Information: Starting test ServerThrowsHubExceptionIfStreamingHubMethodCannotBeResolved-json-LongPolling-/dynamic at 2018-08-06T22:59:00
| [0.001s] TestLifetime Information: Starting test ServerThrowsHubExceptionIfStreamingHubMethodCannotBeResolved_json_LongPolling_dynamic at 2018-08-06T22:59:00
| [0.001s] ServerLogScope Information: Server log scope started.
| [0.003s] SERVER Microsoft.AspNetCore.Hosting.Internal.WebHost Information: Request starting HTTP/1.1 POST http://<IP_ADDRESS>:50262/dynamic/negotiate  0
| [0.003s] SERVER Microsoft.AspNetCore.Hosting.Internal.WebHost Information: Request finished in 0.7132ms 200 application/json
| [0.003s] Microsoft.AspNetCore.Http.Connections.Client.Internal.LongPollingTransport Information: RVwH3zULmhl9KAICdQuEZQ - Starting transport. Transfer mode: Text.
| [0.011s] SERVER Microsoft.AspNetCore.Hosting.Internal.WebHost Information: Request starting HTTP/1.1 GET http://<IP_ADDRESS>:50262/dynamic?id=RVwH3zULmhl9KAICdQuEZQ
| [0.012s] SERVER Microsoft.AspNetCore.Hosting.Internal.WebHost Information: Request finished in 7.4695ms 200 application/octet-stream
| [0.012s] Microsoft.AspNetCore.Http.Connections.Client.HttpConnection Information: RVwH3zULmhl9KAICdQuEZQ - HttpConnection Started.
| [0.012s] Microsoft.AspNetCore.SignalR.Client.HubConnection Information: RVwH3zULmhl9KAICdQuEZQ - Using HubProtocol 'json v1'.
| [0.012s] SERVER Microsoft.AspNetCore.Hosting.Internal.WebHost Information: Request starting HTTP/1.1 GET http://<IP_ADDRESS>:50262/dynamic?id=RVwH3zULmhl9KAICdQuEZQ
| [0.013s] SERVER Microsoft.AspNetCore.Hosting.Internal.WebHost Information: Request starting HTTP/1.1 POST http://<IP_ADDRESS>:50262/dynamic?id=RVwH3zULmhl9KAICdQuEZQ  32
| [0.013s] SERVER Microsoft.AspNetCore.Hosting.Internal.WebHost Information: Request finished in 0.6593ms 200 text/plain
| [0.013s] SERVER Microsoft.AspNetCore.SignalR.HubConnectionContext Information: RVwH3zULmhl9KAICdQuEZQ - Completed connection handshake. Using HubProtocol 'json'.
| [0.014s] Microsoft.AspNetCore.SignalR.Client.HubConnection Information: RVwH3zULmhl9KAICdQuEZQ - HubConnection started.
| [0.014s] SERVER Microsoft.AspNetCore.Hosting.Internal.WebHost Information: Request finished in 1.9032ms 200 application/octet-stream
| [0.014s] SERVER Microsoft.AspNetCore.Hosting.Internal.WebHost Information: Request starting HTTP/1.1 GET http://<IP_ADDRESS>:50262/dynamic?id=RVwH3zULmhl9KAICdQuEZQ
| [0.014s] SERVER Microsoft.AspNetCore.Hosting.Internal.WebHost Information: Request starting HTTP/1.1 POST http://<IP_ADDRESS>:50262/dynamic?id=RVwH3zULmhl9KAICdQuEZQ  11
| [0.015s] SERVER Microsoft.AspNetCore.Hosting.Internal.WebHost Information: Request finished in 0.6528ms 200 application/octet-stream
| [0.015s] SERVER Microsoft.AspNetCore.Hosting.Internal.WebHost Information: Request finished in 0.7708ms 200 text/plain
| [0.015s] SERVER Microsoft.AspNetCore.Hosting.Internal.WebHost Information: Request starting HTTP/1.1 GET http://<IP_ADDRESS>:50262/dynamic?id=RVwH3zULmhl9KAICdQuEZQ
| [0.015s] SERVER Microsoft.AspNetCore.Hosting.Internal.WebHos
...

Other tests within that build may have failed with a similar message, but they are not listed here. Check the link above for more info.
CC @Eilon,@muratg,@mkArtakMSFT
This issue was made automatically. If there is a problem contact @ryanbrandenburg.

Please use this workflow to address this flaky test issue, including checking applicable checkboxes and filling in the applicable "TODO" entries:

Is this actually a flaky test?

No, this is a regular test failure, fix the test/product (TODO: Link to commit/PR)
Yes, proceed below...

Is this test failure caused by product code flakiness? (Either this product, or another product this test depends on.)

[ ] File a bug against the product (TODO: Link to other bug)
Is it possible to change the test to avoid the flakiness?

Yes? Go to the "Change the test!" section.
No?

[ ] Disable the test (TODO: Link to PR/commit)
[ ] Wait for other bug to be resolved
[ ] Wait for us to get build that has the fix
[ ] Re-enable our test (TODO: Link to PR/commit)
[ ] Close this bug

Is it that the test itself is flaky? This includes external transient problems (e.g. remote server problems, file system race condition, etc.)

Is there is a way to change our test to avoid this flakiness?

Yes? Change the test!

[ ] Change the test to avoid the flakiness, for example by using a different test strategy, or by adding retries w/ timeouts (TODO: Link to PR/commit)
[ ] Run the test 100 times locally as a sanity check.
[ ] Close this bug

No?

[ ] Delete the test because flaky tests are not useful (TODO: Link to PR/commit)

This comment was made automatically. If there is a problem contact @ryanbrandenburg.

What a bizzare exception. Maybe something is copying the get request stream?

This is definitely an odd one. It seems to be happening within HttpClient.SendAsync (from FinishSendAsyncBuffered on the stack). We don't do anything fancy here:
https://github.com/aspnet/SignalR/blob/1874368a5caa4f562d1d693e58ae5b68a24d6166/src/Microsoft.AspNetCore.Http.Connections.Client/Internal/LongPollingTransport.cs#L149-L170

cc @geoffkizer @davidsh @stephentoub

I'm guessing the CancellationToken is firing here? Just a guess, but we may have a race where the connection is being closed due to cancellation, but LoadIntoBufferAsyncCore is trying to read the response body anyway, and somehow this gets manifested as "stream does not support reading".

Ah, that's definitely possible. We do trigger that cancellation token on shutdown. Should we just suppress that error and treat it as OperationCanceledException?

Well, we still shouldn't throw the weird stream exception in this case. But assuming that cancellation is being triggered, it's less concerning than just random failures.
BTW what version of .NET is this running on?

Looks like the failure is on .NET Framework 4.6.1 (at least that's the build output we're running, not sure exactly which runtime is on the machine)

Yeah, if it's caused by another product I would say mark it as blocked and use this as a tracking issue for the other issue. That's what we were trying to convey in the checklist, any suggestions on how to make that more clear?

But this only repros on .NET Framework, not .NET Core?

Correct. Filed https://github.com/dotnet/corefx/issues/31748

I have a few more updates in the linked issue, but I did indeed verify that the cancellation token was triggered immediately before this exception occurred.

But this only repros on .NET Framework, not .NET Core?

Correct.

I should clarify. We've only seen it on .NET Framework. I have no idea if the same condition could exist in the .NET Core code :)

What's left to track is when we consume the fix they produce.

We've fixed the immediate test issue, and there's nothing we need to track here anymore.


Wrong moment-timezone package

If you install mrt:moment-timezone package, it will throw an error.
Use risul:moment-timezone instead, it has proper dependencies!

Closing all issues. The plugin was a proof of concept which others have forked and made better alternatives.


[BUG] Can't find scraper

Describe the bug:
I followed the instructions to download mov-cli and the mov-cli-youtube, copying the commands in the documentation exactly. I put [mov-cli.plugins] youtube = "mov-cli-youtube"
In my config.toml, however I get met with an error when I type the command mov-cli -s --debug youtube blender studio stating the scraper didn't exist.
Upon installing mov-cli-files and running mov-cli -s files "*" the same issue was occuring
Mov-cli version: {4.4.15}
Expected behaviour:
I expected to not be met with an error and be able to find and watch videos using mov-cli.
Steps to reproduce:

Install mov-cli
Install the a plugin, namely mov-cli-youtube
Add the plugin to your config.toml
Attempt to run mov-cli

Logs:
[ERROR] (mov_cli) - Could not find a scraper by the id 'youtube'! Are you sure the plugin is installed and in your config? Read the wiki for more on that: 'https://github.com/mov-cli/mov-cli/wiki#plugins'.
Available Scrapers -> test.default | test.test

* Did you mean: test.test

[ERROR] (mov_cli) - You must choose a scraper to scrape with! You can set a default scraper with the default key in config.toml.

Platform:

OS: Windows 11 Home
Version: 23H2

Checklist

[Yes] I have added logs.
[Yes] I have added my platform.
[Yes] I have added my version number.
[Yes] I am sure that this issue is not related to a plugin.

Did you install mov-cli via pipx?

I have tried installing with pipx and pip, both yield the same errors.

with pipx you need to do: pipx inject mov-cli mov-cli-youtube have you done that?

Yes. Now that I have also cleared the cache, a different error is yielded.
Here are the logs.
[INFO] (mov_cli) - [Config] .env file created at 'C:\Users\loven\AppData\Local\mov-cli\.env'.
[CRITICAL] (mov_cli) - [Config] Failed to read config.toml! Please check you haven't made any mistakes in the config.All values will fallback to default.
Error: What? plugins already exists?{'plugins': {'youtube': 'mov-cli-youtube'}} (line 3 column 1 char 46)

and here is my config
[mov-cli.plugins]
youtube = "mov-cli-youtube"
[mov-cli.plugins]
files = "mov-cli-files"

[mov-cli.plugins]
youtube = "mov-cli-youtube"
files = "mov-cli-files"

[mov-cli.plugins] is only required once.

I'm almost too embarrassed to say thank you.

No worries, so is it all good?


KafKaDirectDstream should filter empty partition task or rdd

To avoid submit stages and tasks for 0 events batch.

Merged build triggered.

Merged build triggered.

Merged build started.

Test build #41018 has started for   PR 8237 at commit 4e4764d.

Test build #41018 has finished for   PR 8237 at commit 4e4764d.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

We have rejected such ideas before because not generating an RDD in a batch will actually cause problems in semantics of the downstream operations. For example, if you are doing updateStateByKey with the kafka stream, it is expected that the updatefunction will be called for each key in each batch interval. If there is no RDD generated, then its not clear what the semantics become. So I am against making this change.

@tdas, yean, I agree with it will be confused in semantics, and for a batch streaming system, it will not blocked the next batch as long as it will finished quickly, even not larger than batch time. Ah...I still have a little uncomfortable for launching empty tasks to executor, as we run spark on yarn, the resource is based soft isolation, so it will occurs resource competition, some times, even for empty task, the process time will larger than batch time.

I understand and I have debated about this before. This is one of those grey areas where there is no golden solution. In such cases, I think it is better to err towards having a solution better understandable semantics with slight inefficiency as opposed to having the most efficient solution without an hard-to-reason semantics.

@tdas Ok, as you already discussed before, so let's stay the same.

Thanks! Appreciate your understanding.
On Tue, Aug 18, 2015 at 7:51 PM, Shan Hu<EMAIL_ADDRESS>wrote:

@tdas https://github.com/tdas Ok, as you already discussed before, so
let's stay the same.
—
Reply to this email directly or view it on GitHub
https://github.com/apache/spark/pull/8237#issuecomment-132427763.


Delayed expected state/validation

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
I have an Ecoflow which has flakey WiFi. When you use a service or UI to change settings such as charge rate, the value takes hold for a short time but reverts back to the previous value because the connection failed.
Describe the solution you'd like
An ability to delay the expected state or validation parameter to cater for the above scenario. For example, allowing an expected state check to occur 30 seconds after the initial service call should work.
Describe alternatives you've considered
None.
Additional context
I believe what I am seeing from Ecoflow is Home Assistant takes the changes as the current state but when the cloud integration updates (not sure if this is push or pull), it will revert to the actual state of the setting.

v2.12.0 adds a new state_delay parameter. Documentation can be found here.
@dannytsang  , please let me know if it's working and addressing your needs.

Ah brill. I'll report back soon.

@amitfin I'm getting an extra keys not allowed error when I use state_delay. I checked the automation and I think it's right. Can you see if there's anything wrong?

@dannytsang did you upgrade to v2.12.0? It requires a reboot.

@amitfin i was not! That's annoying considering other HACS integration had updates between 28th and now. I have updated and restarted. I will hopefully test it in the next couple of days.
Thanks again.

Worked great and even got the failed notification. Thanks @amitfin


UploadSet does not render {fileName} correctly

OpenUI5 version: latest
Browser/version (+device/version): Edge Chromium (latest)
Any other tested browsers/devices(OK/FAIL): FAIL (Firefox)
URL (minimal example if possible):
User/password (if required and possible - do not post any confidential information here): contact me
Steps to reproduce the problem:

Select any request in the list
Check out the uploaded File (there is 1 available)

What is the expected result?
Item is displayed correctly. (File name, URL)
What happens instead?
Item is not being displayed at all. Upon removal of the {fileName} data binding, the item is shown, but still without any details.
The Network request seems to be fine and returns 1 item with all the details.
Any other information? (attach screenshot if possible)
I suspect this could be connected to oData v2, although I was not able to test it with v4.
I have implemented an UploadSet:
<upload:items>
    <upload:UploadSetItem
        fileName="{fileName}"
        mediaType="{mediaType}"
        url="{url}"
        enabledEdit="false"
        visibleEdit="false"
        openPressed="onOpenPressed"
        thumbnailUrl="sap-icon://pdf-attachment"
    >
        <upload:attributes>
            <ObjectAttribute
                title="URL"
                text="{url}"
                active="false"
            />
        </upload:attributes>
    </upload:UploadSetItem>
</upload:items>

On loaf of the page, the following error is displayed:
Uncaught TypeError: Cannot read property 'slice' of null

Hello @schanjan
Thank you for sharing this finding. I've created an internal incident<PHONE_NUMBER>. The status of the issue will be updated here in GitHub.
Regards,
Georgi

Issue has been solved by internal incident and will be available in the next release.


ERROR: Your adapter can not transmit to channel 149, frequency band 5GHz.

I'm using Archlinux, and I installed create_ap with yaourt -S create_ap.
Also manually installed those dependencies. When I tried to set up a wireless access point from my Ethernet, I got the result:
$ sudo create_ap wlp3s0 enp4s0f2 Soaph huangkaishabi
[sudo] hk 的密码：
Config dir: /tmp/create_ap.wlp3s0.conf.TE9xj8nH
PID: 13053
Warning: nmcli (1.0.6) and NetworkManager (1.0.4) versions don't match. Use --nocheck to suppress the warning.
Network Manager found, set ap0 as unmanaged device... DONE
wlp3s0 is already associated with channel 149 (5745 MHz), fallback to channel 149
Creating a virtual WiFi interface... Warning: nmcli (1.0.6) and NetworkManager (1.0.4) versions don't match. Use --nocheck to suppress the warning.
Warning: nmcli (1.0.6) and NetworkManager (1.0.4) versions don't match. Use --nocheck to suppress the warning.
Warning: nmcli (1.0.6) and NetworkManager (1.0.4) versions don't match. Use --nocheck to suppress the warning.
Warning: nmcli (1.0.6) and NetworkManager (1.0.4) versions don't match. Use --nocheck to suppress the warning.
ap0 created.

ERROR: Your adapter can not transmit to channel 149, frequency band 5GHz.

Doing cleanup.. done

Even if I add --freq-band 2.4 will I get the same output.
How should I get this successful? Thanks!

Here is my iw list output:
Wiphy phy0
        max # scan SSIDs: 20
        max scan IEs length: 425 bytes
        max # sched scan SSIDs: 20
        max # match sets: 11
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Device supports RSN-IBSS.
        Device supports AP-side u-APSD.
        Supported Ciphers:
                * WEP40 (00-0f-ac:1)
                * WEP104 (00-0f-ac:5)
                * TKIP (00-0f-ac:2)
                * CCMP (00-0f-ac:4)
                * 00-0f-ac:10
                * GCMP (00-0f-ac:8)
                * 00-0f-ac:9
                * CMAC (00-0f-ac:6)
                * 00-0f-ac:13
                * 00-0f-ac:11
                * 00-0f-ac:12
        Available Antennas: TX 0 RX 0
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * monitor
                 * P2P-client
                 * P2P-GO
                 * P2P-device
        Band 1:
                Capabilities: 0x11e2
                        HT20/HT40
                        Static SM Power Save
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 3839 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 4 usec (0x05)
                HT Max RX data rate: 300 Mbps
                HT TX/RX MCS rate indexes supported: 0-15
                Bitrates (non-HT):
                        * 1.0 Mbps
                        * 2.0 Mbps (short preamble supported)
                        * 5.5 Mbps (short preamble supported)
                        * 11.0 Mbps (short preamble supported)
                        * 6.0 Mbps
                        * 9.0 Mbps
                        * 12.0 Mbps
                        * 18.0 Mbps
                        * 24.0 Mbps
                        * 36.0 Mbps
                        * 48.0 Mbps
                        * 54.0 Mbps
                Frequencies:
                        * 2412 MHz [1] (22.0 dBm)
                        * 2417 MHz [2] (22.0 dBm)
                        * 2422 MHz [3] (22.0 dBm)
                        * 2427 MHz [4] (22.0 dBm)
                        * 2432 MHz [5] (22.0 dBm)
                        * 2437 MHz [6] (22.0 dBm)
                        * 2442 MHz [7] (22.0 dBm)
                        * 2447 MHz [8] (22.0 dBm)
                        * 2452 MHz [9] (22.0 dBm)
                        * 2457 MHz [10] (22.0 dBm)
                        * 2462 MHz [11] (22.0 dBm)
                        * 2467 MHz [12] (22.0 dBm) (no IR)
                        * 2472 MHz [13] (22.0 dBm) (no IR)
        Band 2:
                Capabilities: 0x11e2
                        HT20/HT40
                        Static SM Power Save
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 3839 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 4 usec (0x05)
                HT Max RX data rate: 300 Mbps
                HT TX/RX MCS rate indexes supported: 0-15
                VHT Capabilities (0x038071a0):
                        Max MPDU length: 3895
                        Supported Channel Width: neither 160 nor 80+80
                        short GI (80 MHz)
                        TX STBC
                        SU Beamformee
                VHT RX MCS set:
                        1 streams: MCS 0-9
                        2 streams: MCS 0-9
                        3 streams: not supported
                        4 streams: not supported
                        5 streams: not supported
                        6 streams: not supported
                        7 streams: not supported
                        8 streams: not supported
                VHT RX highest supported: 0 Mbps
                VHT TX MCS set:
                        1 streams: MCS 0-9
                        2 streams: MCS 0-9
                        3 streams: not supported
                        4 streams: not supported
                        5 streams: not supported
                        6 streams: not supported
                        7 streams: not supported
                        8 streams: not supported
                VHT TX highest supported: 0 Mbps
                Bitrates (non-HT):
                        * 6.0 Mbps
                        * 9.0 Mbps
                        * 12.0 Mbps
                        * 18.0 Mbps
                        * 24.0 Mbps
                        * 36.0 Mbps
                        * 48.0 Mbps
                        * 54.0 Mbps
                Frequencies:
                        * 5180 MHz [36] (22.0 dBm) (no IR)
                        * 5200 MHz [40] (22.0 dBm) (no IR)
                        * 5220 MHz [44] (22.0 dBm) (no IR)
                        * 5240 MHz [48] (22.0 dBm) (no IR)
                        * 5260 MHz [52] (22.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 1434183 sec)
                          DFS CAC time: 0 ms
                        * 5280 MHz [56] (22.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 1434183 sec)
                          DFS CAC time: 0 ms
                        * 5300 MHz [60] (22.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 1434183 sec)
                          DFS CAC time: 0 ms
                        * 5320 MHz [64] (22.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 1434183 sec)
                          DFS CAC time: 0 ms
                        * 5500 MHz [100] (22.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 1434183 sec)
                          DFS CAC time: 0 ms
                        * 5520 MHz [104] (22.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 1434183 sec)
                          DFS CAC time: 0 ms
                        * 5540 MHz [108] (22.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 1434183 sec)
                          DFS CAC time: 0 ms
                        * 5560 MHz [112] (22.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 1434183 sec)
                          DFS CAC time: 0 ms
                        * 5580 MHz [116] (22.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 1434183 sec)
                          DFS CAC time: 0 ms
                        * 5600 MHz [120] (22.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 1434183 sec)
                          DFS CAC time: 0 ms
                        * 5620 MHz [124] (22.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 1434183 sec)
                          DFS CAC time: 0 ms
                        * 5640 MHz [128] (22.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 1434183 sec)
                          DFS CAC time: 0 ms
                        * 5660 MHz [132] (22.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 1434183 sec)
                          DFS CAC time: 0 ms
                        * 5680 MHz [136] (22.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 1434183 sec)
                          DFS CAC time: 0 ms
                        * 5700 MHz [140] (22.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 1434183 sec)
                          DFS CAC time: 0 ms
                        * 5720 MHz [144] (22.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 1434183 sec)
                          DFS CAC time: 0 ms
                        * 5745 MHz [149] (22.0 dBm) (no IR)
                        * 5765 MHz [153] (22.0 dBm) (no IR)
                        * 5785 MHz [157] (22.0 dBm) (no IR)
                        * 5805 MHz [161] (22.0 dBm) (no IR)
                        * 5825 MHz [165] (22.0 dBm) (no IR)
        Supported commands:
                 * new_interface
                 * set_interface
                 * new_key
                 * start_ap
                 * new_station
                 * new_mpath
                 * set_mesh_config
                 * set_bss
                 * authenticate
                 * associate
                 * deauthenticate
                 * disassociate
                 * join_ibss
                 * join_mesh
                 * remain_on_channel
                 * set_tx_bitrate_mask
                 * frame
                 * frame_wait_cancel
                 * set_wiphy_netns
                 * set_channel
                 * set_wds_peer
                 * start_sched_scan
                 * probe_client
                 * set_noack_map
                 * register_beacons
                 * start_p2p_device
                 * set_mcast_rate
                 * channel_switch
                 * set_qos_map
                 * add_tx_ts
                 * connect
                 * disconnect
        Supported TX frame types:
                 * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
        Supported RX frame types:
                 * IBSS: 0x40 0xb0 0xc0 0xd0
                 * managed: 0x40 0xd0
                 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
                 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
                 * mesh point: 0xb0 0xc0 0xd0
                 * P2P-client: 0x40 0xd0
                 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
                 * P2P-device: 0x40 0xd0
        WoWLAN support:
                 * wake up on disconnect
                 * wake up on magic packet
                 * wake up on pattern match, up to 20 patterns of 16-128 bytes,
                   maximum packet offset 0 bytes
                 * can do GTK rekeying
                 * wake up on GTK rekey failure
                 * wake up on EAP identity request
                 * wake up on 4-way handshake
                 * wake up on rfkill release
                 * wake up on network detection, up to 11 match sets
                 * wake up on TCP connection
        software interface modes (can always be added):
                 * AP/VLAN
                 * monitor
        valid interface combinations:
                 * #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1,
                   total <= 3, #channels <= 2
        HT Capability overrides:
                 * MCS: ff ff ff ff ff ff ff ff ff ff
                 * maximum A-MSDU length
                 * supported channel width
                 * short GI for 40 MHz
                 * max A-MPDU length exponent
                 * min MPDU start spacing
        Device supports TX status socket option.
        Device supports HT-IBSS.
        Device supports SAE with AUTHENTICATE command
        Device supports low priority scan.
        Device supports scan flush.
        Device supports per-vif TX power setting
        P2P GO supports CT window setting
        P2P GO supports opportunistic powersave setting
        Driver supports a userspace MPM
        Device supports static SMPS
        Device supports dynamic SMPS
        Device supports WMM-AC admission (TSPECs)
        Device supports configuring vdev MAC-addr on create.

wlp3s0 is already associated with channel 149 (5745 MHz), fallback to channel 149

Most of wifi adapters can only use one channel. So, if they are connected to an AP then create_ap can only create an AP on that channel. You are connected to a 5GHz channel but your adapter does not support trasmition on that channels.
        valid interface combinations:
                 * #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1,
                   total <= 3, #channels <= 2

Probably your adapter can have two different channels, edit create_ap and remove line CHANNEL=$WIFI_IFACE_CHANNEL (now is at 1425 line). After that try again and tell me if it works or not.

Thanks, I will have a try and tell you if it works or not. :)

Well, still not working. This time, the output becomes like this.
$ sudo create_ap wlp3s0 enp4s0f2 Soaph huangkaishabi
Config dir: /tmp/create_ap.wlp3s0.conf.GGPcxFs4
PID: 1528
Network Manager found, set ap0 as unmanaged device... DONE
wlp3s0 is already associated with channel 149 (5745 MHz), fallback to channel 149
Creating a virtual WiFi interface... ap0 created.

ERROR: Your adapter can not transmit to channel 1, frequency band 5GHz.

Doing cleanup.. done

Find the function is_wifi_connected and replace it with:
is_wifi_connected() {
    return 0
}

Unfortunately, not working... T_T
$ sudo create_ap wlp3s0 enp4s0f2 Soaph huangkaishabi
Config dir: /tmp/create_ap.wlp3s0.conf.PwcIDDGU
PID: 29058
Network Manager found, set ap0 as unmanaged device... DONE
Creating a virtual WiFi interface... ap0 created.
RTNETLINK answers: Device or resource busy

ERROR: Maybe your WiFi adapter does not fully support virtual interfaces.
       Try again with --no-virt.

Doing cleanup.. done

Ok thanks. I'm closing the issue since it's not a bug.
To workarround this you can do one of the following:

Buy second adapter for the transmition.
Buy an adapter that support both frequencies for transmition.
If you have access to the AP, change its frequency to 2.4ghz.

However, in windows, I could easily create a AP with a tool, maybe it's the settings issue.

You can still create AP with your adapter, but you can not use 5ghz frequency. Because you are connected an AP then you can only transmit to the frequency your are already connected. If you connect to another AP that uses 2.4ghz or get your Internet access from another interface (ethernet or another wifi adapter) then you will not have any problem.

BTW, if on Windows can create 5ghz AP, then it's a driver limitation. Your iw list reports that you can only transmit on 2.4ghz. So, to bypass this limitation then you can edit the driver code in the kernel.

Thank you so much, you helped me find the way to fix this problem! :)

No problem :)

@oblique FWIW those two edits (CHANNEL line removal and is_wifi_connected) actually worked for mine! I am connected to a 5GHz network as the INternet connection and broadcasting on 2.4. Thanks for the tips!

I know this is an old thread but I wanted to say this worked for me too!   One thing I will add for future readers... You need to run make again to build the create_ap after you make the edits.   I don't think that was mentioned here.  Might be obvious but I know some may try this without knowledge of what you are actually doing.

@rapidrex I just edited the script directly last time. You probably edited in the build directory and the Makefile just copies to /usr/bi. You can edit directly in /usr/bin if desired.

Yep.. worked for me too!

These two changes worked for me as well.

Works for me after two mentioned changes.

unfortunatelly, it doesn't work for me

I resolved my problem by using the command "sudo create_ap wlp3s0 wlp3s0 ssid password &" , and my drive supports software AP,  you can reference this article https://bbs.deepin.org/forum.php?mod=viewthread&tid=45024

I was facing this too, so using https://github.com/oblique/create_ap/issues/107#issuecomment-140786781 and https://github.com/oblique/create_ap/issues/107#issuecomment-140064666 worked.
However, maybe this could be just fixed properly by making create_ap to honor --freq-band parameter? So that if 2.4 is used to repeat a 5Ghz network it just works?

Find the function is_wifi_connected and replace it with:
is_wifi_connected() {
    return 1
}

This worked for me. Thanks to oblique!

Could you please tell me where the function is? I can't find it

Find the function is_wifi_connected and replace it with:
is_wifi_connected() {
    return 1
}

Thanks. It works

(no IR)
sudo iw reg set NZ

Hi all!
Sorry I'm a wifi AP newbie here;
My machine is connected through Ethernet and I would like to broadcast using its Wifi chip/antennas using the 5GHz frequency band. It works on 2.4GHz but I get the following error when trying on 5GHz (with other 5GHz channels too):
ERROR: Your adapter can not transmit to channel 36, frequency band 5GHz.

Where can I find if my Wifi device actually supports AP mode in 5GHz in the output from iw list?
I have attached the output of iw list.
Thanks!

@qdm12 What OS are you using? Arch at least has a crda package where you only have to uncomment a line in /etc/conf.d and reboot the machine.

Oh good to know!
I'm indeed using Arch, I probably also installed crda as well. Anyway, it works now hopefully it can help a fellow user!

Works for me after two mentioned changes.
my laptop is ThinkPad E470c with 05:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31)

Find the function is_wifi_connected and replace it with:
is_wifi_connected() {
    return 1
}

This worked for me. Thanks to oblique!

Could you please tell me where the function is? I can't find it

you need to edit  /usr/bin/create_ap file.
worked for me too.

Find the function is_wifi_connected and replace it with:
is_wifi_connected() {
    return 1
}

solved, thanks

in my case i was able to solve the problem by first switching off the wifi connection at first and then created the AP through command line. after that i again tried to connect to wifi network , which i got connected successfully. So i would probably say that first try to disconnect your system from connected wifi network , after that try to make AP and after that connect to wifi network.
Hope this may help.

Find the function is_wifi_connected and replace it with:
is_wifi_connected() {
    return 1
}

Worked for me too, thanks!

Find the function is_wifi_connected and replace it with:
is_wifi_connected() {
    return 1
}

This worked for me (in combination with the previous modification)!!! I'm successfully using my laptop to extend a 5ghz hotspot over 2.4ghz :smile:
So clearly there is room for improvement. Can this issue please be re-opened??


reorganize a bit; add mocking

This PR does two things:

makes it such that repartition_layer returns a MaterializedLayer instance instead of a new Array collection. Array.repartition gets a few more lines that handles instantiating a new collection from the new layer.
add mocking logic to optimize.py so that we just return the same array (a collections typetracer array representation is of course invariant under repartitioning)

The warnings have gone away with
pytest tests/test_structure.py -k "repartition"

but with more digging around I'm unconvinced the changes I added here are solid yet

OK nevermind, I introduced warnings and then removed them! So now I'm not sure if we're accomplishing anything yet. Do you have some code that triggers the optimization failure?


Adds maliput bindings

Related to https://github.com/maliput/delphyne/issues/846#issuecomment-1176384022
Summary
For context check https://github.com/maliput/delphyne/issues/846#issuecomment-1176384022
In this PR:

RoadNetworkWrapper inclusion was reverted. (Last 2 commits)
Adds maliput bindings

For reviewers
To review f81ac09

Once this is approved.  The following PRs should be created

delphyne_gui: https://github.com/maliput/delphyne_gui/tree/francocipollone/adds_bindings_instead
delphyne_demos: https://github.com/maliput/delphyne_demos/tree/francocipollone/adds_bindings_instead

And #847 issue should be rewritten


migrator: teach the driver to support multiple migration script sets.

To support migration from both Swift 3 and 4, this patch
teaches the driver to pick up the right set of migration scripts
according to the given Swift version. We also pushed some placeholder script
files for migration from Swift 4. This patch also brings the migrator
up-to-date by avoiding migration if the Swift version is already 4.2.

@swift-ci please smoke test

@swift-ci please clean test

Build failed
Swift Test Linux Platform
Git Sha - b561a0177c7565405fb2307eccbb921ff24a56bd

@swift-ci please clean test

Build failed
Swift Test OS X Platform
Git Sha - b561a0177c7565405fb2307eccbb921ff24a56bd

Build failed
Swift Test Linux Platform
Git Sha - b561a0177c7565405fb2307eccbb921ff24a56bd

Build failed
Swift Test OS X Platform
Git Sha - b561a0177c7565405fb2307eccbb921ff24a56bd

@swift-ci please smoke test

@swift-ci please clean test

Build failed
Swift Test OS X Platform
Git Sha - 6ba93ac7f4efc339b6e5a41953374b5da8273085

Build failed
Swift Test Linux Platform
Git Sha - 6ba93ac7f4efc339b6e5a41953374b5da8273085


Added virtual file system to the compiler and IDE support

Description
This PR adds support for virtual file system, allowing the compiler to build a package from files kept by the IDE in memory.
It also fixes an existing bug (https://github.com/move-language/move/issues/1082) where source files used in the symbolicator (obtained from resolution graph) and source files used by the compiler could be modified between the two uses resulting in different file hashes which can ultimately lead to crash when translating diagnostics (generated by the compiler and using "compiler file hashes") using symbolicator source files (and "symbolicator file hashes")
Test Plan
All existing tests must pass. Also, manually tested the IDE no longer needs file saves to reflect changes in the file (e.g., compiler diagnostics appear as the code is being typed).

Superceded by https://github.com/MystenLabs/sui/pull/16330


Questions about the TestSplitVote2AA test

Here is the difference.

I have a question about the TestSplitVote2AA test case, why is it judged to be a candidate for the Splitvote case? I refer to the relevant details in the raft paper. When a splitvote situation occurs, the two raft nodes will vote for each other, and then convert themselves to Followers, so that the two will always be in the voting process.It's right?Thanks for your answer！

@liiuzq-xiaobai
First of all, they don't vote for each other. A candidate only votes for itself according to the paper.
Splitting case happens when no one gets votes from the majority and therefore no one becomes the leader.
In this case, all of the candidates will not change their state until:
0.
Election timeout, start a new election and win the campaign -- become a leader.
In this test case, these two candidates share the same term, so No.0 won't happen. Also, no one wins the election so no one will send out heartbeats, therefore No.1 won't happen.
As for No.2, however, it will happen in a few lines below your screenshot. Actually, I think what you've misunderstood here is how the test cases work. Try to look into the send method a few lines above your screenshot. It shows how your msgs are transferred and processed(basically it's just a single-threaded FIFO). In short, this test case uses MessageType_MsgHup to trigger leader election instead of timeout, suspends at the stage when split-vote just happens, and then triggers a new round of election using MessageType_MsgHup again. There is no tick in here, no real election timeout, everything happens under the control of msg. It's a step-by-step test.


Use latest micronaut-data

@jesperancinha Using latest micronaut-data and micronaut-openapi seems to resolve compile error. Please look at this fix.

@jesperancinha Using latest micronaut-data and micronaut-openapi seems to resolve compile error. Please look at this fix.

Thanks @radovanradic , Let's see how it goes!

Right, compile works but reactive repository tests are failing. This is usually fixed by having
@MicronautTest(transactional = false)

annotation.

Hey @radovanradic , just to say thank you again for helping out! The build was successful and the changes were just automatically merged back to master. I did had to make some changes in the Kong framework to get Swagger to work and I will probably need to revise them later, but for the time being everything works.


Multi threading read support for precomputed

Precomputed can currently concurrently write data to storage but not reading
time estimate: <1d

This will improve efficiency of the pipeline by making reading volumes faster

This is done already:
https://github.com/seung-lab/neuroglancer/blob/quantizedaffinities/python/neuroglancer/pipeline/volumes/cloudvolume.py


Simmilar to https://github.com/AvaloniaUI/Avalonia/issues/12182

Simmilar to https://github.com/AvaloniaUI/Avalonia/issues/12182
and to https://github.com/AvaloniaUI/Avalonia/discussions/11726
If we set AllowAutoHide to false in datagrid ScrollBar selector in this way
				<Style Selector="ScrollBar">
					<Setter Property="Background" Value="Blue"/>
					<Setter Property="AllowAutoHide" Value="False"/>
				</Style>

last row is not visible..  for demonstration i used  very big ScrollBarSize
		<DataGrid.Resources>
			<x:Double x:Key="ScrollBarSize">20.0</x:Double>
		</DataGrid.Resources>

i found than I can achieve this effect by editing Fluent.xaml in Avalonia.Controls.DataGrid/Themes

by changing Grid.RowSpan/Grid.ColumnSpan

from 2,3 to respectivly 1,2 is there any way to ovveride this values ?
https://github.com/AvaloniaUI/Avalonia/blob/e0fb7db6c56f745027ef1b041ea0ca24feb27ab5/src/Avalonia.Controls.DataGrid/Themes/Fluent.xaml#L538
i tried this.. Color works but row/column spans not :(
				<Style Selector="DataGridRowsPresenter#PART_RowsPresenter">
					<Setter Property="Grid.RowSpan" Value="1"/>
					<Setter Property="Grid.ColumnSpan" Value="2"/>
					<Setter Property="Background" Value="Green"/>
				</Style>

Originally posted by @KrzysztofDusko in https://github.com/AvaloniaUI/Avalonia/discussions/14445

@timunie Can I try with this ?


Linux build

Hello,
do you have a Linux Build?
Is possible to build the project for Linux?
Thank you.

Hi, I don't have Linux on my computer. It uses electron and should be simple to build. I've uploaded the source code to https://www.dropbox.com/s/iya9paljnawnpqt/clay-viewer-0.2.1-src.zip?dl=0 . You can download it and build the project with electron-builder
Here is an example.
npm install -g electron-builder
build

Hello, thank you for the project but i was not able to build:
  • electron-builder version=20.2.0
  • loaded configuration file=package.json ("build" field)
  • description is missed in the package.json appPackageFile=/home/linux/Download/clay-viewer-0.2.1-src/package.json
  • writing effective config file=dist/electron-builder.yaml
  • no native production dependencies
  • packaging       platform=linux arch=x64 electron=1.7.9 appOutDir=dist/linux-unpacked
Downloading tmp-31717-1-SHASUMS256.txt-1.7.9
[============================================>] 100.0% of 2.93 kB (2.93 kB/s)
  • building        target=snap arch=x64 file=dist/clay-viewer_0.2.1_amd64.snap
  • building        target=AppImage arch=x64 file=dist/clay-viewer-0.2.1-x86_64.AppImage
  • downloading               path=/home/linux/.cache/electron-builder/appimage/appimage-9.0.7 url=https://github.com/electron-userland/electron-builder-binaries/releases/download/appimage-9.0.7/appimage-<IP_ADDRESS>z
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x5feb8a]

goroutine 19 [running]:
github.com/develar/app-builder/pkg/util.mapAsync.func1(0xc420184070, 0xc420184000, 0xc4200a81e0, 0xc4200a8180, 0x0)
	/Users/develar/go/src/github.com/develar/app-builder/pkg/util/async.go:54 +0x7a
created by github.com/develar/app-builder/pkg/util.mapAsync
	/Users/develar/go/src/github.com/develar/app-builder/pkg/util/async.go:40 +0x181
Error: /usr/lib/node_modules/electron-builder/node_modules/app-builder-bin-linux/x64/app-builder exited with code 2
    at ChildProcess.childProcess.once.code (/usr/lib/node_modules/electron-builder/node_modules/builder-util/src/util.ts:252:14)
    at Object.onceWrapper (events.js:317:30)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:925:16)
    at Socket.stream.socket.on (internal/child_process.js:346:11)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at Pipe._handle.close [as _onclose] (net.js:554:12)
From previous event:
    at LinuxPackager.resolveIcon (/usr/lib/node_modules/electron-builder/node_modules/electron-builder-lib/out/platformPackager.js:610:11)
    at /usr/lib/node_modules/electron-builder/node_modules/electron-builder-lib/src/targets/LinuxTargetHelper.ts:43:35
    at Generator.next (<anonymous>)
From previous event:
    at LinuxTargetHelper.computeDesktopIcons (/usr/lib/node_modules/electron-builder/node_modules/electron-builder-lib/out/targets/LinuxTargetHelper.js:73:11)
    at Lazy.LinuxTargetHelper.iconPromise.Lazy (/usr/lib/node_modules/electron-builder/node_modules/electron-builder-lib/src/targets/LinuxTargetHelper.ts:13:54)
    at Lazy.get value [as value] (/usr/lib/node_modules/electron-builder/node_modules/lazy-val/src/main.ts:18:23)
    at LinuxTargetHelper.get icons [as icons] (/usr/lib/node_modules/electron-builder/node_modules/electron-builder-lib/src/targets/LinuxTargetHelper.ts:21:29)
    at /usr/lib/node_modules/electron-builder/node_modules/electron-builder-lib/src/targets/snap.ts:135:23
    at Generator.next (<anonymous>)
From previous event:
    at SnapTarget.build (/usr/lib/node_modules/electron-builder/node_modules/electron-builder-lib/out/targets/snap.js:174:11)
    at taskManager.addTask.default.map.it (/usr/lib/node_modules/electron-builder/node_modules/electron-builder-lib/src/platformPackager.ts:121:67)
From previous event:
    at LinuxPackager.packageInDistributableFormat (/usr/lib/node_modules/electron-builder/node_modules/electron-builder-lib/src/platformPackager.ts:121:23)
    at /usr/lib/node_modules/electron-builder/node_modules/electron-builder-lib/src/platformPackager.ts:116:10
    at Generator.next (<anonymous>)
    at runCallback (timers.js:789:20)
    at tryOnImmediate (timers.js:751:5)
    at processImmediate [as _immediateCallback] (timers.js:722:5)
From previous event:
    at LinuxPackager.pack (/usr/lib/node_modules/electron-builder/node_modules/electron-builder-lib/out/platformPackager.js:188:11)
    at /usr/lib/node_modules/electron-builder/node_modules/electron-builder-lib/src/packager.ts:372:24
    at Generator.next (<anonymous>)
    at xfs.stat (/usr/lib/node_modules/electron-builder/node_modules/fs-extra/lib/mkdirs/mkdirs.js:56:16)
    at /usr/lib/node_modules/electron-builder/node_modules/graceful-fs/polyfills.js:287:18
    at FSReqWrap.oncomplete (fs.js:153:5)
From previous event:
    at Packager.doBuild (/usr/lib/node_modules/electron-builder/node_modules/electron-builder-lib/out/packager.js:441:11)
    at /usr/lib/node_modules/electron-builder/node_modules/electron-builder-lib/src/packager.ts:316:52
    at Generator.next (<anonymous>)
    at /usr/lib/node_modules/electron-builder/node_modules/graceful-fs/graceful-fs.js:99:16
    at /usr/lib/node_modules/electron-builder/node_modules/graceful-fs/graceful-fs.js:43:10
    at FSReqWrap.oncomplete (fs.js:135:15)
From previous event:
    at Packager._build (/usr/lib/node_modules/electron-builder/node_modules/electron-builder-lib/out/packager.js:385:11)
    at /usr/lib/node_modules/electron-builder/node_modules/electron-builder-lib/src/packager.ts:278:23
    at Generator.next (<anonymous>)
    at runCallback (timers.js:789:20)
    at tryOnImmediate (timers.js:751:5)
    at processImmediate [as _immediateCallback] (timers.js:722:5)
From previous event:
    at Packager.build (/usr/lib/node_modules/electron-builder/node_modules/electron-builder-lib/out/packager.js:341:11)
    at /usr/lib/node_modules/electron-builder/node_modules/electron-builder-lib/src/index.ts:50:40
    at Generator.next (<anonymous>)
From previous event:
    at build (/usr/lib/node_modules/electron-builder/node_modules/electron-builder-lib/out/index.js:47:21)
    at build (/usr/lib/node_modules/electron-builder/src/builder.ts:228:10)
    at then (/usr/lib/node_modules/electron-builder/src/cli/cli.ts:48:33)
    at runCallback (timers.js:789:20)
    at tryOnImmediate (timers.js:751:5)
    at processImmediate [as _immediateCallback] (timers.js:722:5)
From previous event:
    at Object.args [as handler] (/usr/lib/node_modules/electron-builder/src/cli/cli.ts:48:33)
    at Object.runCommand (/usr/lib/node_modules/electron-builder/node_modules/yargs/lib/command.js:235:44)
    at Object.parseArgs [as _parseArgs] (/usr/lib/node_modules/electron-builder/node_modules/yargs/yargs.js:1042:24)
    at Object.get [as argv] (/usr/lib/node_modules/electron-builder/node_modules/yargs/yargs.js:957:21)
    at Object.<anonymous> (/usr/lib/node_modules/electron-builder/src/cli/cli.ts:42:15)
    at Module._compile (module.js:643:30)
    at Object.Module._extensions..js (module.js:654:10)
    at Module.load (module.js:556:32)
    at tryModuleLoad (module.js:499:12)
    at Function.Module._load (module.js:491:3)
    at Function.Module.runMain (module.js:684:10)
    at startup (bootstrap_node.js:187:16)
    at bootstrap_node.js:608:3

Did you run npm install to install the dependencies under that folder?

yes

Same here


Chat Copilot App stops working after enabling WebSearcher Plugin

Description:
Chat Copilot App stops working after enabling WebSearcher Plugin.
To Reproduce:
Steps to reproduce the behavior:

After deploying plugin
Launch the Chat Copilot App and enable WebSearcher Plugin
After enabling WebSearcher Plugin, start interacting with Chat Copilot App. Error: Unable to generate bot experience. Deatils: Error: 500 Internal Server Error.

Expected behavior:
Expecting Chat Copilot App to interact and suggest/reply to the ask.
Screenshots:

Platform:

OS: Windows
IDE: VS Code

@karthikkc24  can you try it again and if it is not working open an issue at https://github.com/microsoft/chat-copilot


Prototype relies on javascript number behaviour

Unfortunately Solidity doesn't have support for fixed point numbers.. Instead solidity rounds to 0  when dividing numbers.
To simulate that behaviour in our prototype I have called Math.floor whenever we divide a value. This causes the tests to fail.

sanity check: why can't I observe the failing test through GitHub?

sanity check: why can't I observe the failing test through GitHub?

It looks like GH actions don't get triggered unless there's an actual created PR. Now that I've created the PR you can see the failure here

@lalexgap anything else that remains here?

@lalexgap anything else that remains here?

No, I think this is complete with your PR.


Fix for grants template and execution

This fixes the unary operator expected error in the grants script, as well as the execution block.
Fixes issue: https://github.com/sinfomicien/mariadb/issues/108

@jwmarshall what does bash -e change exactly? Could not find this documented and only know about the echo -e behaviour. Is this related?

bash -e causes a script to exit on the first error (non-zero exit code) it encounters. Unfortunately it does not actually catch the unary operator issue (nor would it exit) as it only catches error codes for commands executed in the script.
Nevertheless I believe it is the correct behaviour that this script should exit and throw a non-zero exit code if either of the two commands (one to look up the root user rows, the second to run move that user) should fail.

Added a quick fix to the foodcritic complaint that was failing your CI tests.

@sinfomicien @joerocklin


Reconciler error" err="providerClient authentication err: Get "https://10.x.x.x:5000": tls: failed to verify certificate: x509: certificate signed by unknown authority"

Hi,
I am trying to use magnum-cluster-api driver with magnum in kolla-ansible openstack deployment (1 ctl + 1 comp)
I have deployed cluster-api in kind k8s cluster on a seperate ubuntu VM on KVM.
OpenStack APIs are using https certs self signed private CA certificates by Kolla-Ansible for external APIs.
when I try to create Kubernetes cluster in openstack it shows below error in kind cluster capo-controller-manager :
kubectl -n capo-system logs deploy/capo-controller-manager -f
"Reconciler error" err="providerClient authentication err: Get \"https://10.x.x.x:5000/\": tls: failed to verify certificate: x509: certificate signed by unknown authority" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" OpenStackMachine="magnum-system/kube-2k150-default-worker-6ljfm-nzmjk-8pnw7" namespace="magnum-system" name="kube-2k150-default-worker-6ljfm-nzmjk-8pnw7" reconcileID="fdca9177-8b21-4df7-b28a-2ee6be9517a2"
ubuntu@k8s-kind:~/debugging$ kubectl -n magnum-system get clusters kube-2k150
NAME         CLUSTERCLASS     PHASE          AGE   VERSION
kube-2k150   magnum-v0.21.2   Provisioning   17h   v1.27.4

when I check certificate secrets in kind cluster it show below:
ubuntu@k8s-kind:~$ kubectl get secret -n magnum-system
NAME                      TYPE                      DATA   AGE
kube-2k150-ca             cluster.x-k8s.io/secret   2      15h
kube-2k150-cloud-config   Opaque                    2      15h
kube-2k150-etcd           cluster.x-k8s.io/secret   2      15h
kube-2k150-proxy          cluster.x-k8s.io/secret   2      15h
kube-2k150-sa             cluster.x-k8s.io/secret   2      15h

If I edit the certificate value in secret kube-2k150-cloud-config  to kolla-ansible root CA certificate then it works fine.
Temporary Fix is editing the cacert value in cloud-config secret everytime when I create k8s in magnum.

kubectl edit secret -n magnum-system kube-b4rv4-cloud-config

I followed below guides for magnum-cluster-api deployment with kolla-Ansible:
https://satishdotpatel.github.io/openstack-magnum-capi/
https://www.roksblog.de/openstack-magnum-cluster-api-driver/
It could be related to certifi certificates in magnum/kolla but I am not sure how to fix it.
Can someone help here ?

you can add an option in magnum.conf
[drivers]
verify_ca = false
Which will make capi driver to bypass ca verification for your self signed cert.

If cluster cannot connect openstack api due to option: ca-file=/etc/config/ca.crt in cloud.conf - it is possible to comment out
[drivers]
#openstack_ca_file = /usr/local/share/ca-certificates/magnum.crt