Update troubleshooting-the-office-365-management-activity-api.md

Docs Build status updates of commit 34a1b4e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

office-365-management-api/troubleshooting-the-office-365-management-activity-api.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 34a1b4e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

office-365-management-api/troubleshooting-the-office-365-management-activity-api.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 0ab5587:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

office-365-management-api/troubleshooting-the-office-365-management-activity-api.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 0ab5587:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

office-365-management-api/troubleshooting-the-office-365-management-activity-api.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


warning when open spyder for the first time

Description
What steps will reproduce the problem?

first time open spyder

What is the expected output? What do you see instead?
Please provide any additional information below
File "C:\Users\plin\Downloads\WinPython-64bit-<IP_ADDRESS>Qt5\python-3.5.4.amd64\lib\site-packages\spyder\plugins_init_.py", line 511, in
toggled=lambda checked: self.toggle_view(checked),
File "C:\Users\plin\Downloads\WinPython-64bit-<IP_ADDRESS>Qt5\python-3.5.4.amd64\lib\site-packages\spyder\plugins\ipythonconsole.py", line 695, in toggle_view
self.create_new_client(give_focus=False)
File "C:\Users\plin\Downloads\WinPython-64bit-<IP_ADDRESS>Qt5\python-3.5.4.amd64\lib\site-packages\spyder\plugins\ipythonconsole.py", line 977, in create_new_client
self.connect_client_to_kernel(client)
File "C:\Users\plin\Downloads\WinPython-64bit-<IP_ADDRESS>Qt5\python-3.5.4.amd64\lib\site-packages\spyder\plugins\ipythonconsole.py", line 998, in connect_client_to_kernel
stderr_file)
File "C:\Users\plin\Downloads\WinPython-64bit-<IP_ADDRESS>Qt5\python-3.5.4.amd64\lib\site-packages\spyder\plugins\ipythonconsole.py", line 1387, in create_kernel_manager_and_kernel_client
kernel_manager.start_kernel(stderr=stderr)
File "C:\Users\plin\Downloads\WinPython-64bit-<IP_ADDRESS>Qt5\python-3.5.4.amd64\lib\site-packages\jupyter_client\manager.py", line 234, in start_kernel
"Currently valid addresses are: %s" % local_ips()
RuntimeError: Can only launch a kernel on a local interface. Make sure that the '

Thanks for reporting. This has been a commonly reported issue with WinPython, and does not appear to be a spyder problem, and indeed, a near-duplicate, #5101 , says as much. There is currently an issue over there, #582, that deals with this, so feel free to comment over there if you have something to add, and I would think this one can be closed.
In general, Spyder recommends the Anaconda distribution, as it avoids many of the problems and pitfalls found in other install methods, particularly for less experienced users, though you are welcome to try to get it to work on your own. Best of luck!


Error: cannot access Detox import com.wix.detox.Detox

What happened?
Hello Guys! How have you been?
I'm having a problem when I'm trying to build the android emulator to run detox tests. When I run:
npx detox build --configuration android.emu.debug

I'm getting this error here:

It seems like the error happens because is not finding the detox on my node_modules maybe...
But I made all the config mentioned.
Detox added at android/build.gradle:

Approach that I had
I read on Detox releases that on detox 20.18.5, Java 17 is required.
I'm working with Java 11, so, I made the suggested change by release docs but I didn't have good results :/

What was the expected behaviour?
Build android emulator to run the tests sucessfully;
Was it tested on latest Detox?

[X] I have tested this issue on the latest Detox release and it still reproduces.

Did your test throw out a timeout?

[X] I have followed the instructions under Identifying which synchronization mechanism causes us to wait too much.

Help us reproduce this issue!

Configure the app on android (following the docs)
run npx detox build --configuration android.emu.debug

In what environment did this happen?
Detox version: 20.18.5
React Native version: 0.72.10
Has Fabric (React Native's new rendering system) enabled: no
Node version: v20.11.1
Device model: Android Emulador (Pixel_2_API_31)
Android version:
openjdk version "11.0.22" 2024-01-16 LTS
OpenJDK Runtime Environment Zulu11.70+15-CA (build 11.0.22+7-LTS)
OpenJDK 64-Bit Server VM Zulu11.70+15-CA (build 11.0.22+7-LTS, mixed mode)

Test-runner: jest
Detox logs
Detox logs
paste logs here!

Device logs
Device logs
paste your device.log here!

More data, please!
No response

I can bypass this issue by downgrading detox to version 20.1.4

I fixed it by modifying this line in the build.gradle file: 'androidTestImplementation('com.wix:detox-legacy:+')'.

Same issue in my expo project

same issue

I can bypass this issue by downgrading detox to version 20.1.4

Unfortunately this solved the mentioned issue, but created another issue TypeError: by.testID is not a function


Add fixture resolution to LibTXT and enable testing on the buildbots.

Currently, that unit-test target is only run on the workstation.

cc @jason-simmons

Changes for this have landed: https://github.com/flutter/engine/pull/13180


500 Backend error on sending message(Gmail API:users.messages.insert)

I sometimes get "500:backend error" on sending message(Gmail API: users.messages.send) with media upload. However, I sometimes succeed with same request. Following logs was confirmed using MediaHttpUploaderProgressListener.
04:24:08.916 [main] INFO com.example.Sender - started to execute request. contentsSize=25,324,196, chunkSize=10,485,760, disableGzip=false
04:24:08.917 [main] INFO com.example.Sender - uploaded:INITIATION_STARTED 0[bytes](0.0%)
04:24:09.492 [main] INFO com.example.Sender - uploaded:INITIATION_COMPLETE 0[bytes](0.0%)
04:24:19.732 [main] INFO com.example.Sender - uploaded:MEDIA_IN_PROGRESS 10,485,760[bytes](41.4%)
04:24:30.382 [main] INFO com.example.Sender - uploaded:MEDIA_IN_PROGRESS 20,971,520[bytes](82.8%)
04:25:43.825 [main] WARN com.example.Sender - failed to send message. 500:Backend Error

// com.google.api.services.gmail.Gmail api = ...
// javax.mail.internet.MimeMessage mimeMessage = ...

try (ByteArrayOutputStream baos = new ByteArrayOutputStream()) {
  mimeMessage.writeTo(baos);
  AbstractInputStreamContent mediaContent = new ByteArrayContent("message/rfc822", baos.toByteArray());
  Gmail.Users.Messages.Send request = api.users().messages().send(email, new Message(), mediaContent);
  MediaHttpUploader mediaHttpUploader = request.getMediaHttpUploader();
  mediaHttpUploader.setProgressListener(new MediaHttpUploaderProgressListener() {
    @Override
    public void progressChanged(MediaHttpUploader uploader) throws IOException {
      logger.info(String.format("  uploaded:%s %,3d[bytes](%2.1f%%)",
        uploader.getUploadState(), uploader.getNumBytesUploaded(),
        uploader.getProgress() * 100.0));
    }
  });
  logger.info(String.format("started to execute request. contentsSize=%,3d, chunkSize=%,3d, disableGzip=%s",
    mediaContent.getLength(), mediaHttpUploader.getChunkSize(),
    mediaHttpUploader.getDisableGZipContent()));

  com.google.api.services.gmail.model.Message sentMessage = request.execute();
  logger.info("done.");

} catch (GoogleJsonResponseException e) {
  GoogleJsonError e_ = e.getDetails();
  logger.warn(String.format("failed to send message. %d:%s", e_.getCode(), e_.getMessage()), e);
}

A 500 error code may mean the problem is not on client-side, however, it may be possible that the client is doing something that is more likely to cause a failure.
This is for the client library itself, not for service-related issues. Please try stackoverflow with gmail-api tag instead.


Add ability to add/remove svelte components from example?

Looks great so far...
It would be really nice to see an example of being able to add/remove svelte components from the example site and also maybe a walkthrough of that, unless I missed it in the read me...

Nope. that is not yet added to README. svelte components are just nodes. You should be able to find something in Tiptap docs on how to work with them.


🧠 Logic: json_prolog array serialization issue

Issue description
When unifying a json array through a Prolog empty list to its string representation, it outputs to the string "[]" instead of an empty json array: [].
How to reproduce
This can easily reproduced with a Ask query using the CLI:
> okp4d query logic ask "json_prolog(X, [])." -ojson | jq -r '.answer.results[-1].substitutions[-1].term.name'
'"[]"'

We can observe the same results specifying the '[]' atom instead of an empty list:
> okp4d query logic ask "json_prolog(X, [])." -ojson | jq -r '.answer.results[-1].substitutions[-1].term.name'
'"[]"'

The reason under this behavior is related to the equality between an empty list and the '[]' atom at the interpreter level:
> okp4d query logic ask "[] = '[]'." -ojson | jq -r '.answer.success'
true

First Analysis
An issue has been opened on the interpreter: https://github.com/ichiban/prolog/issues/296.
It seems this behavior is expected, the SWI-PROLOG implementation having its specific empty list type being not standard.
Should the Prolog interpreter in the logic module be aligned on the standard or the SWI-PROLOG implementation? And then, how do we address the JSON array marshaling?

@bdeneux @ccamel I propose to respect to Prolog standard and not head towards SWI-PROLOG "unconventional" empty list consideration.
We still need a solution though, amending the original specification.
A json(Attributes) predicate was introduced to manage JSON objects (e.g. {"b": "a", "a":"c"} => json([a-c,b-a])), may I suggest a similar predicate to handle JSON arrays, like json_array(Elements)? It would be consistent with the way we manage objects. Moreover, the original issue is only related to empty arrays so we can support both.
As an example, the following Prolog:
json([
    empty-json_array([]),
    filled-[with, something],
    alsoFilled(json_array([0, 1]))
])

What are your thoughts?
Would represents:
{
    "empty": [],
    "filled": [
        "with",
        "something"
    ],
    "alsoFilled": [
        0,
        1
    ]
}

@amimart Ok that seems a good solution we could use to allow empty list in json. Maybe to make more consistency we should rename the json(Attributes) predicate to json_obj(Attributes) or json_object(Attributes).
We have another solution, is to create a specific atom to represent an empty list, like null (@(null)) or boolean value (@(true)), we could create the atom @([]). But this one is not common so I don't know what is the best solution...

I have a deep feeling, whose origin eludes me, that the choice of using the functor @ with [] as argumentwould be the most appropriate for designating the special value that is the empty list.

I have a deep feeling, whose origin eludes me, that the choice of using the functor @ with [] as argument would be the most appropriate for designating the special value that is the empty list.

@ccamel Yeah it seems simple, just add an @ in the case of an empty array, I'm ok with that :)

:tada: This issue has been resolved in version 5.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Docker:  RADARR_A_PROFILE_FILTER env variable does not function, and RADARR_A_PROFILE_FILTER_ID filters everything

Describe the bug
Bug A:  RADARR_A_PROFILE_FILTER does not function - all movies are synced to Radarr B
Bug B:  RADARR_A_PROFILE_FILTER_ID filters everything - no movies are synced to Radarr B
Version
Current Docker Version
Config
RADARR_A_PROFILE_FILTER = $K-RadarrSync
RADARR_A_PROFILE_FILTER_ID = 7

Issue on my end


SSL Support

According to the Uchiwa documentation, SSL support is present by using:
{
  "uchiwa": {
    "auth": {
      "privatekey": "/path/to/uchiwa.rsa",
      "publickey": "/path/to/uchiwa.rsa.pub"
    }
  }
}

If i look into the docs and the uchiwa.json.erb file, I don't see any reference to the Auth: section.
Is it possible for you guys to implement this? Would be much appreciated!

Woops, missed it. Apparantely it's monday...


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

Codecov Report

Merging #401 (56e3f17) into main (2974dfe) will increase coverage by 12.36%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##             main     #401       +/-   ##
===========================================
+ Coverage   83.33%   95.69%   +12.36%
===========================================
  Files           2        1        -1
  Lines         126      395      +269
  Branches       31       53       +22
===========================================
+ Hits          105      378      +273
+ Misses         21       17        -4

Impacted Files
Coverage Δ

src/index.ts
95.69% <100.00%> (+13.69%)
:arrow_up:

example/src/main.ts

Continue to review full report at Codecov.

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


Feature Request: Add support for algorithms from liboqs (Quantum Safe)

See https://github.com/open-quantum-safe/liboqs#supported-algorithms for documentation and https://github.com/open-quantum-safe/liboqs-rust for example binding (albeit in Rust).

Adding support for Kyber-1024 (offering security roughly equivalent to AES-256) is already under investigation. Currently, Kyber is the only algorithm relevant in this context that is (or will be) standardized. However, it is not decided yet whether it will actually be added to this project and - if yes - when this will happen.
Symmetric encryption, especifically AES-256 is believed to be quantum-resistant. That is, quantum computers are not expected to be able to reduce the attack time enough to be effective if the key sizes are large enough. In case that information will be published invalidating this assumption, the priority to add support for post-quantum algorithms will be increased, of course.

Just as a side note: all (key encapsulation) algorithms offered by liboqs are asymmetric algorithms. For SQLite3 Multiple Ciphers we need symmetric algorithms. So, none of the liboqs algorithms can be used directly.

After doing some further research we come to the following conclusion:
Symmetric encryption algorithms are believed to be quantum resistant, as long as the key size is sufficiently large. SQLite3 Multiple Ciphers already offers support for 2 well-known algorithms with 256-bit keys: AES-256 and ChaCha20.
Adding support for asymmetric encryption algorithms doesn't make much sense in the context of SQLite database encryption, because asymmetric encryption requires very long keys and can not be performed as efficiently as symmetric encryption. Therefore this issue will be closed for now as not planned.

@utelle can you please share your research and references to support this statement?

Symmetric encryption algorithms are believed to be quantum resistant

First hints can be found in the Wikipedia article about Post-Quantum Cryptography (see 3rd paragraph in 1st section). This article contains references to various sources.
However, you can easily find further references by looking for articles about quantum-resistant cryptography. For example

Quantum-Resistant Cryptography by John Preuß Mattsson, Ben Smeets, Erik Thormarker
The Impact of Quantum Computing on Present Cryptography by Vasileios Mavroeidis, Kamer Vishi, Mateusz D. Zych, Audun Jøsang

just to name a few.
Adding support for new quantum-resistant algorithms will be reconsidered, as soon as it is proven that current symmetric algorithms are not quantum-safe. I'm pretty sure that new quantum-resistant symmetric algorithms will be developed in this case.


Load multiple json response via java

Proposal
How to import multiple stub json files? When i run below command i can only see one stub file. But i want load multiple stub files via java please advise
http://localhost:8080/__admin/mappings
Reproduction steps
http://localhost:8080/__admin/mappings/imports are also failing with below error
{
"errors": [
{
"code": 10,
"source": {},
"title": "Error parsing JSON",
"detail": "Unexpected character ('-' (code 45)) in numeric value: expected digit (0-9) to follow minus sign, for valid numeric value\n at [Source: (String)"----------------------------208472049742120374679453\r\nContent-Disposition: form-data; name="file"\r\n\r\nCreateAccessDomainSucces.json\r\n----------------------------208472049742120374679453--\r\n"; line: 1, column: 3]"
}
]
}
References
No response

Please post questions/help requests to the community Slack or Stackoverflow


hex_primes.fj test

primes sieve - hex.print_as_digit all primes till (hex) input n.
(maybe n upto 32bits / 8hexes).
Edit: maybe just up to a fixed number, like all primes up to 1000.

done in #240 in file prime_sieve.fj (and tests prime_sieve*).


Header variables to scss alias

How to theme the header needs some more thought put into it so I'm closing this pr in the meanwhile


Patch 1

https://developer.work.weixin.qq.com/document/path/90208
{
    "id": 2,
     "name": "广州研发中心",
     "name_en": "RDGZ",
     "department_leader":["zhangsan","lisi"],
     "parentid": 1,
     "order": 10
}

add department_leader

Thx for your PR, pls review v2.0.5 @beijibeijing


How to set custom sound in this Alarm App

My main target is to set Text-To-Speak in Alarm Sound, Can you help me in this regard

Hi, sure. So the actual alarm (sound, vibration,..) is treated as a normal notification, as you can see here.
Back when I created this, you could just use [NotificationBuilder#setSound](https://developer.android.com/reference/android/app/Notification.Builder#setSound(android.net.Uri, android.media.AudioAttributes) (used here in rn-alarm codebase) to use a custom sound, but now it's deprecated since API level 26.
Instead of that, you now need to create a NotificationChannel and call setSound on that object, see [documentation](https://developer.android.com/reference/android/app/NotificationChannel#setSound(android.net.Uri, android.media.AudioAttributes). Later on you can assign a notification channel to a NotificationBuilder object, as seen in constructor documentation.
I think this is a (hopefully correct) high level overview of needed changes. Note that I didn't test my instructions in a real app, so you may need to add additional code in order for this to work.


chore(auth)

Fix/clean/rebase pr for ldap and modularizing the auth module more
This is a clone of #66 without their newrelic mods since a newer newrelic based mod exists on our master, cleaned up, reviewed, and configured to preserve backwards compatibility better.

Auth section is now abstracted out into separate auth handlers (htpasswd, passthru, ldap)
Implentation of LDAP auth (using ldapauth npm module)
Configuration (local_settings) can be used to choose which auth_method to use

@kaustavha please rebase.

@kaustavha ping

@mburns pong

Right so:

I forgot to add the ldap dep from the original pr in the package.json of this pr, when i added it the build started to fail on all versions of node above 0.10
I support the refactor of the auth module, it cleans it up and makes it more modular
It is currently out of scope to add ldap auth via this pr because the library it depends on is uh not good because:

It's old and dead, not touched since 2013
https://github.com/trentm/node-ldapauth/commits/master
It relies on a git sha of another ldap library which imo is a little sketchy
https://github.com/trentm/node-ldapauth/blob/master/package.json#L21
It relies on an ancient version of bcrypt which causes the build failures on node >v0.10
https://github.com/trentm/node-ldapauth/blob/master/package.json#L20
https://github.com/dcodeIO/bcrypt.js

I propose we scrap the ldap portion of this PR and merge in the auth module refactor, create an issue for ldap integration and revisit it in the future.

I propose we scrap the ldap portion of this PR and merge in the auth module refactor, create an issue for ldap integration and revisit it in the future.

@kaustavha ok, let's do that then and wrap this up. I'd like to land these improvements.

That should do it.

(doesn't work in staging)


GDF plugin, correct result but no-match

I am trying to build a POC with the GDF plugin.
However there is something interesting going on here. I said "what's your name" and it returned the configured result, "My name is DialogFlow".
But for some reason the response I get is no-match at the end:
2018-10-14 01:09:52:152412 [INFO]   Received Response: status [1] type [unspecified] id [5eb52af1-93cd-4141-9a1d-dbe45d18ca65] <eff4ae433ee049bb@gdf>
2018-10-14 01:09:52:152567 [INFO]   Query result: {
 "queryText": "what's your name",
 "parameters": {},
 "allRequiredParamsPresent": true,
 "fulfillmentText": "My name is Dialogflow!",
 "fulfillmentMessages": [
  {
   "text": {
    "text": [
     "My name is Dialogflow!"
    ]
   }
  }
 ],
 "intent": {
  "name": "************REMOVED*************",
  "displayName": "Do you have a name?\n"
 },
 "intentDetectionConfidence": 1,
 "languageCode": "en-us"
}
 <eff4ae433ee049bb@gdf>
2018-10-14 01:09:52:319807 [INFO]   Received Response: status [1] type [unspecified] id [] <eff4ae433ee049bb@gdf>
2018-10-14 01:09:52:320170 [INFO]   Received Response: status [0] type [unspecified] id [] <eff4ae433ee049bb@gdf>
2018-10-14 01:09:52:320727 [INFO]   Process RECOGNITION-COMPLETE Event <eff4ae433ee049bb@speechrecog> [1]
2018-10-14 01:09:52:320745 [INFO]   State Transition RECOGNIZING -> RECOGNIZED <eff4ae433ee049bb@speechrecog>
2018-10-14 01:09:52:320796 [INFO]   Send MRCPv2 Data ************REMOVED*************:1544 <-> ************REMOVED*************:39550 [130 bytes]
MRCP/2.0 130 RECOGNITION-COMPLETE 1 COMPLETE
Channel-Identifier: eff4ae433ee049bb@speechrecog
Completion-Cause: 001 no-match

2018-10-14 01:09:52:356418 [INFO]   TCP/MRCPv2 Peer Disconnected ************REMOVED*************:1544 <-> ************REMOVED*************:39550

Also I can see the same result in the FS log:
2018-10-14 01:09:52.328268 [DEBUG] mod_unimrcp.c:2786 (ASR-11) result:

Completion-Cause: 001
2018-10-14 01:09:52.348270 [INFO] switch_ivr_async.c:4409 (sofia/internal/1002@************REMOVED*************) DETECTED SPEECH
EXECUTE sofia/internal/1002@************REMOVED************* log(CRIT Completion-Cause: 001)

Am I missing anything? I pretty much have the default configuration:
<?xml version="1.0" encoding="UTF-8"?>
<umsgdf license-file="umsgdf_*.lic" gapp-credentials-file="*.json">
   <license-server
      enable="false"
      server-address="<IP_ADDRESS>"
      certificate-file="unilic_client_*.crt"
      ca-file="unilic_ca.crt"
   />
   <streaming-recognition
      interim-results="false"
      start-of-input="service-originated"
      language="en-US"
      max-alternatives="1"
      project-id="***********REMVOED************"
      skip-unsupported-grammars="true"
      transcription-grammar="transcribe"
   />
   <results
      format="json"
      indent="0"
      replace-dots="true"
      confidence-format="auto"
   />
   <builtin-grammars>
      <builtin-grammar enable="false" mode="speech" name="boolean" action="builtin.boolean" parameter-name="option" project-id=""/>
      <builtin-grammar enable="false" mode="dtmf" name="boolean" action="builtin.boolean" parameter-name="option" project-id="" length="1" input="event"/>

      <builtin-grammar enable="false" mode="speech" name="number" action="builtin.number" parameter-name="number" project-id=""/>
      <builtin-grammar enable="false" mode="dtmf" name="number" action="builtin.number" parameter-name="number" project-id="" input="text"/>
   </builtin-grammars>
   <speech-contexts>
      <speech-context id="booking" enable="false">
         <phrase>I would like to book a flight from New York to Rome with a ticket eligible for free cancellation</phrase>
         <phrase>I would like to book a one-way flight from New York to Rome</phrase>
      </speech-context>
      <speech-context id="boolean" speech-complete="true" enable="false">
         <phrase>yes</phrase>
         <phrase>sure</phrase>
         <phrase>correct</phrase>
         <phrase>no</phrase>
         <phrase>not sure</phrase>
         <phrase>incorrect</phrase>
      </speech-context>
   </speech-contexts>
   <speech-dtmf-input-detector
      vad-mode="2"
      speech-start-timeout="300"
      speech-complete-timeout="1000"
      speech-incomplete-timeout="3000"
      noinput-timeout="5000"
      input-timeout="10000"
      dtmf-interdigit-timeout="5000"
      dtmf-term-timeout="10000"
      dtmf-term-char=""
      speech-leading-silence="300"
      speech-trailing-silence="300"
      speech-output-period="200"
   />
   <utterance-manager
      save-waveforms="false"
      purge-existing="false"
      max-file-age="60"
      max-file-count="100"
      waveform-base-uri="http://localhost/utterances/"
      waveform-folder=""
   />
   <rdr-manager
      save-records="true"
      purge-existing="false"
      max-file-age="60"
      max-file-count="100"
      record-folder=""
   />
   <monitoring-agent refresh-period="60">
      <usage-change-handler>
         <log-usage enable="true" priority="NOTICE"/>
         <update-usage enable="false" status-file="umsgdf-usage.status"/>
         <dump-channels enable="false" status-file="umsgdf-channels.status"/>
      </usage-change-handler>
      <usage-refresh-handler>
         <log-usage enable="false" priority="NOTICE"/>
         <update-usage enable="false" status-file="umsgdf-usage.status"/>
         <dump-channels enable="false" status-file="umsgdf-channels.status"/>
      </usage-refresh-handler>
   </monitoring-agent>
</umsgdf>

Many thanks,
Zoltan

Update: the beta TTS option was turned on on the dialogflow agent side.

Since the Dialogflow plugin is built against GA v2 API, the option "beta services and APIs" must be disabled on the corresponding Dialogflow agent. Otherwise, the behavior is unpredictable.


files keep randomly disappearing

Issue Type: Bug
not sure if its vscode or git, but every so often files come up missing. its happened about 5 times thus far, and i can't pinpoint the cause.
my git workflow is:
git commit -am <MY COMMIT MESSAGE> && git push && git checkout master && git pull && git merge <MY BRANCH> && git push && git checkout <MY BRANCH>

I run this command when i am deploying code for a feature branch, so that i can quickly merge to master and trigger a deploy then switch back to my working branch.
occassionally files will be missing after this, and i have to perform a git stash, at which time the files are restored. its so bizarre, but i can't tell if its bad behavior from vscode, the shell, or a problem with my git workflow.
so far the files that have come up missing:

react-date-picker from my node modules, entire directory was gone.
src/components/RedactedComponentName.js
src/lib/tools.js
package.json
scripts/build.js

VS Code version: Code 1.28.2 (7f3ce96ff4729c91352ae6def877e59c561f4850, 2018-10-17T00:23:51.859Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (8 x 3392)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.91GB (10.19GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (4)

Extension
Author (truncated)
Version

twigcs
cer
0.4.2

php-debug
fel
1.12.6

php-intellisense
fel
2.3.5

php-pack
fel
1.0.2

(1 theme extensions excluded)

Well, please do some testing and make sure it's VS Code. If it happens to be, let me know.


Add ability of pre-releases

The plan is to make  pre-release with #373

Codecov Report

Merging #375 (57155bf) into master (2c0aa43) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #375   +/-   ##
=========================================
  Coverage     87.15%   87.15%
  Complexity      372      372
=========================================
  Files            32       32
  Lines          1432     1432
  Branches        164      164
=========================================
  Hits           1248     1248
  Misses          115      115
  Partials         69       69

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Just to let you know, I made an automated created pre-release https://github.com/matomo-org/matomo-sdk-android/releases/tag/4.2-beta1 by setting just a beta in tag name to see if it works


Add UnoTelly as an VPN server

UnoTelly has an OpenVPN service that I use succesfully with Linux Mint 18 and woukld love to have UnoTelly added as an pre-configured service...
More info here...
http://help.unotelly.com/support/solutions/articles/184300-openvpn-info-and-files-please-read-

I've added it to the list of futures for VPN Manager, but this has nothing to do with my Kodi repo...


fix(apify): add @apify/timeout to dependencies

Fixes #75

I am quite sure you also need to update the lock file, but lets merge, I can regenerate it later myself.


RPi installation instructions need updating.

Using Stretch on a RPi 3B+, I cloned this repo, changed the working directory to raylib/src and ran make PLATFORM=PLATFORM_RPI. This was the error message:
In file included from external/mini_al.h:8894:28: fatal error: alsa/asoundlib.h: No such file or directory...

I fixed it by running sudo apt-get install libasound-dev, then carrying on with the instructions in the wiki. However, apt-get selected libasound2-dev automatically, so the command should be sudo apt-get install libasound2-dev.
After that, everything seems fine. I built and ran the core_2d_camera and core_basic_window examples without any trouble at least.
I haven't updated the wiki, just incase I didn't understand something (this is all new to me).

Hey @carlsmith! Thanks for reporting!
Including @mackron to be aware of this issue.

Darn, I was debugging stuff and accidentally left that #include in there. That's my bad. mini_al does not depend on ALSA development packages so no need to update the wiki. Instead I've pushed a fix to the master branch of mini_al. @raysan5 you can go ahead and copy that over (I figure that will be easier than doing a pull request).

Thanks for the update @mackron. Already updated mini_al on raylib in commit https://github.com/raysan5/raylib/commit/5b09630d45ec5bfaa301c5dc0f27c0d44f57bbb8.

Thanks guys. Nice one.


Function is not redeployed after being deleted

If a function is deleted and recreated just after that the function is never deployed:
$ kubeless function delete post-python
$ kubectl get pods
NAME                           READY     STATUS             RESTARTS   AGE
post-python-2010894748-bv4f2   1/1       Terminating        0          12m
$ kubeless function deploy --runtime python2.7 --from-file ./examples/python/hellowithdata.py --handler hellowithdata.handler --trigger-http post-python
$ kubectl get pods
No resources found.
$ kubeless function ls
+-------------+-----------+-----------------------+-----------+------+-------+--------------+
|    NAME     | NAMESPACE |        HANDLER        |  RUNTIME  | TYPE | TOPIC | DEPENDENCIES |
+-------------+-----------+-----------------------+-----------+------+-------+--------------+
| post-python | default   | hellowithdata.handler | python2.7 | HTTP |       |              |
+-------------+-----------+-----------------------+-----------+------+-------+--------------+

Can you also give the actual logs on the controller pod ?

I checked the logs but it didn't show anything relevant just the usual "success" messages:
time="2017-09-27T15:38:29Z" level=info msg="Processing change to Function default/test2" pkg=controller
time="2017-09-27T15:38:30Z" level=info msg="Updated Function default/test2" pkg=controller

I need to do a deep debug yet.

+1 - I see the PR but just wanted to say we noticed the same issue over the last couple of days


Update AddVegetation.cs

Adding missing ResetTerrain.Execute to AddVegetation.cs

There actually was a reset done in a patch under the ResetTerrain. But for some reason this doesn't work anymore.
Since your way works, I will just use that. Thanks!


createReducer handle type/action not giving same action type

Description
When creating reducer by createReducer<State, Action> you not get same action type when using handleType and handleAction if your action was created by createAsyncAction.
Mandatory info
How to Reproduce
export interface IUser {
  id: number;
  email: string;
  full_name: string;
  data: {};
  roles: [];
}

export enum EActionTypes {
  FETCH_PROFILE_REQUEST = '@@auth/FETCH_PROFILE_REQUEST',
  FETCH_PROFILE_SUCCESS = '@@auth/FETCH_PROFILE_SUCCESS',
  FETCH_PROFILE_FAILURE = '@@auth/FETCH_PROFILE_FAILURE',
}

export const fetchProfileAsync = createAsyncAction(
  EActionTypes.FETCH_PROFILE_REQUEST,
  EActionTypes.FETCH_PROFILE_SUCCESS,
  EActionTypes.FETCH_PROFILE_FAILURE
)<undefined, IUser, Error>();

Create reducer like so and you get type error:
const reducer = createReducer<IState, RootAction>(initialState).handleAction(
  fetchProfileAsync.success,
  (state, action) => {
    return {
      ...state,
      profile: action.payload,
    };
  }
);

You get action type: (parameter) action: {     type: EActionTypes.FETCH_PROFILE_SUCCESS;     payload: {}; } | PayloadAction<EActionTypes.FETCH_PROFILE_SUCCESS, IUser> and because that you get type error.
Create reducer like so and everything is ok:
const reducer = createReducer<IState, RootAction>(initialState).handleType(
  EActionTypes.FETCH_PROFILE_SUCCESS,
  (state, action) => {
    return {
      ...state,
      profile: action.payload,
    };
  }
);

Expected behavior
action should be type: (parameter) action: PayloadAction<EActionTypes.FETCH_PROFILE_SUCCESS, IUser>
Suggested solution(s)
Project Dependencies

Typesafe-Actions Version: latest
TypeScript Version: latest
tsconfig.json:

{
  "compilerOptions": {
    "target": "esnext",
    "module": "commonjs",

    "jsx": "react-native",

    "noEmit": false,

    "strict": true,

    "noUnusedLocals": true,
    "noUnusedParameters": true,

    "moduleResolution": "node",

    "esModuleInterop": true,

    "forceConsistentCasingInFileNames": true,

    "skipLibCheck": true,
    "resolveJsonModule": true
  },
  "exclude": ["node_modules"]
}

Environment (optional)

OS: Win10
Node Version: 12

Your RootAction type is wrong


Adam additions

-some monoFont stuff have their docs hidden, I think it should not be hidden
-there are some docs about angle conversion:
Degrees start from 0 pointing East and then go counterclockwise.
So:
90 degrees is up (north)
180 degrees is pointing left (west)
280 degrees is pointing down (south)
This is true for the standard math plane where y axis is going up but on the screen the y axis is going down. So on a computer s creen Pi/2(90 dergrees) is actually going down. If you drawpoint(cos(a),sin(a)) on screen coordinates it will go clockwise... I this doc is confusing and not usefull
(I need more time to test and read more..)

-some monoFont stuff have their docs hidden, I think it should not be hidden
-there are some docs about angle conversion:
Degrees start from 0 pointing East and then go counterclockwise.
So:
90 degrees is up (north)
180 degrees is pointing left (west)
280 degrees is pointing down (south)
This is true for the standard math plane where y axis is going up but on the screen the y axis is going down. So on a computer s creen Pi/2(90 dergrees) is actually going down. If you drawpoint(cos(a),sin(a)) on screen coordinates it will go clockwise... I this doc is confusing and not usefull
(I need more time to test and read more..)

-in view.wx the additions (AcceptsTouchEvent and others) are commented out!
-in canvas.wx the method lineIntersectshould be in some math/geom file IMHO and must not contain Print(line 1315 and 1319)

-in view.wx the additions (AcceptsTouchEvent and others) are commented out!
-in canvas.wx the method lineIntersectshould be in some math/geom file IMHO and must not contain Print(line 1315 and 1319)

@abakobo

-in view.wx the additions (AcceptsTouchEvent and others) are commented out!

It is commented out because it is not complete and/or not working yet.

@abakobo

-in view.wx the additions (AcceptsTouchEvent and others) are commented out!

It is commented out because it is not complete and/or not working yet.


Documentation update

Description
Please include a summary of the change and which is fixed.

Documentation update
Benchmark scores update

How has this been tested?
Please describe the tests that you ran to verify your changes.

[x] UnitTest
[ ] Benchmark

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.53%. Comparing base (2efea3f) to head (ee86733).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #525   +/-   ##
=======================================
  Coverage   90.53%   90.53%
=======================================
  Files         127      127
  Lines        4394     4394
  Branches      707      707
=======================================
  Hits         3978     3978
  Misses        274      274
  Partials      142      142

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


Unable to Save Data Using ChatGPT Retrieval Plugin with Memory Enabled

I've followed the instructions on the ChatGPT Retrieval Plugin with Memory GitHub page to enable memory for the retrieval plugin. This involved copying the contents of openapi.yaml and ai-plugin.json from the example into the main files of the same names.
After enabling memory, I've been able to successfully perform queries. However, I'm encountering issues when trying to save data into my database through the plugin. Specifically, when I try to use prompts to save data, the plugin seems to treat these as queries instead of upsert operations.
Here's a screenshot of the issue I'm encountering:

I'm looking for any tips or guidance on how to resolve this issue. Has anyone else encountered this problem and found a solution?

I always answer my questions when asking haha.
If you run into the same issue, you need to be aware of cache by going into private navigation when trying out your plugin and be sure of the openAPI file that is taken into account. Don't know why it's the local one on my side.

Is it just the browser cache you are talking about or something else? I am having a similar problem. ChatGPT does not seem to recognize its ability to upsert. I've tried clearing the browser cache and opening a private window but am getting the same problem.


why broccoli not process command in Brocfile.js?

I wrote a broccoli plugin broccoli-filter-asciitree recently. broccoli simple and clear, especially for other language user, because it is not relate to stream api.
at same time, I read some gulp's doc and code.I think whatever gulp can do, broccoli can do. but there been a big difference between two, gulp treat gulffile.js as program, but broccoli treat Brocfile.js as a data struct. very few thing you can do with Brocfile.js.
gulp move all command to gulpfile.js, builtin or customs. broccoli only has two builtin command, server and built, If I want customize the server behavior, I found no way.
If broccoli refactoring the command system, make it more open, it will more competitive.

the general idea is that broccoli is to be a build-pipeline used by other systems. The cli provided is more of a POC.

I see.So, if I wrote an adapter(wrapper) to connect broccoli's node with gulp's vinyl stream, broccoli should work with gulp.


[stable] std.math.operations: Slightly revise extractBitpattern()

Incl. fixing an out-of-bounds read on 32-bit x86 with real.sizeof == 12 (detected via an LLVM assertion after merging to LDC).

Sorry, due to personal reasons, I'll not find the time to review this. It was not doable by just a first glimse.


Drag and Drop components within the Infinite Canvas

Bug description
I am trying to use the Draggable component (via react-draggable) to place components within the Infinite Canvas that can be draggable. This will allow for a "workspace" environment. When I try to use the Draggable component, I have an issue where clicking on the component that should be draggable, ends up moving the canvas around instead.

Expected result
There needs to be some differentiation between clicking on the Canvas and on the Draggable component.

Actual result
The canvas itself moves around instead of the component that should be draggable.
Is there a way to update the InfiniteCanvas component such that custom component can be draggable within the canvas to give a "workspace" feel

Steps to reproduce

Your Environment

Version used:
Browser Name and version:
Operating System and version:
Link to your project:

Hi @aragop25, I understand what you are facing and I will try to fix this. Thanks for reaching out.


Only watch and update toleration/priority class for managed components

Longhorn shouldn't modify user deployed components (e.g., manager, driver,
UI) because doing so would have problems for users who deploy Longhorn using
GitOps tools.

This PR adds a new labels longhornio/managed-by: longhorn manager to all
managed components. Then Longhorn only watchs and updates toleration/priority class for those
managed components

This PR also makes sure that the labels is added after upgrade Longhorn from
an older version.

Now that we only watch/update managed components, we should allow user to specify Helm values for user deployed components (manager, driver, UI). This is tracked at https://github.com/longhorn/longhorn/pull/2348
longhorn/longhorn#2120

The PR itself LGTM. But I am thinking there are too many (util) functions for the labels. What do you think? Do we need to/Can we simplify them to make the code more readable?

Yeah, I agree that there are too many util functions for label updating.  I thought about this before but couldn't find a clean way to reduce the duplicated. I think there are 2 options but both of them are not usable:

Redefine the types (Deployment, Pod, Daemonset, etc ...) and add UpdateLabels method to each type. Then we can call the method when updating labels. I think the option even increases the amount of code
Have a genetic function that can update labels for all find of types: updateLabels(obj *object, howToGetNewLabels func, howToUpdateObj func) . Then we need to define functions like howToGetNewLabelsForMangerPods(), howToGetNewLabelsForShareManagerPods(), etc,...

Do you have a better idea of how to fix reduce the code?

@PhanLe1010 No exact solution right now. But we need to consider if we can standardize the Label schema for Longhorn components and the naming of the keys. There are some issues right now:

One Longhorn component can have 2 keys. e.g.:

LonghornNodeKey     = "longhornnode"
LonghornLabelNode                 = "node"

The naming patterns vary:

LonghornLabelVolume               = "longhornvolume"
LonghornLabelShareManager         = "share-manager"

Too many functions involved for the labels of one CR. The 2nd solution you provide may be a good choice.

Anyway. The issue is beyond this PR. We can handle them in the future. This PR LGTM. But we need to wait for the code unfreezing right now.

@PhanLe1010 No exact solution right now. But we need to consider if we can standardize the Label schema for Longhorn components and the naming of the keys. There are some issues right now:

One Longhorn component can have 2 keys. e.g.:

LonghornNodeKey     = "longhornnode"
LonghornLabelNode                 = "node"

The naming patterns vary:

LonghornLabelVolume               = "longhornvolume"
LonghornLabelShareManager         = "share-manager"

Too many functions involved for the labels of one CR. The 2nd solution you provide may be a good choice.

Anyway. The issue is beyond this PR. We can handle them in the future. This PR LGTM. But we need to wait for the code unfreezing right now.

cc https://github.com/longhorn/longhorn/issues/2353

Ping @shuo-wu
Can we merge this PR?


Archive history button should be named

Operation System: Windows 10
Beaker version: Beaker v0.8.0-prerelease.2
The archive history button should have a named title instead of just an icon, to make it more clear what the icon does. I did discover what it was for after clicking on it, but I could not have guessed it by just looking at the icon.

We've decided to go with an icon and tooltip (on hover) for now


fixed duplicated copy text for navigation feature

fix for copy/paste mistake introduced in 4da89065cf1d62f7304196e0dd8394c9c0f0caa0

Thanks for merging!!!


Key Vault access issue from TFE

So this module works great locally without any problems, but once we move to TFE the temporary user that gets permission on the key vault to manage it we start having issues.
Because TFE uses a new user each time it connects to get the state of the keyvault this new user lacks permission to get the state of keyvault and causes TFE to fail with errors.
The solution would be to add the TFE group IP, which is a var from each workspace, as a permission set within the keyvault so TFE will always have access required.
Below are the errors that come up when TFE tries to access keyvault for any run after keyvault has been deployed
Error: Error making Read request on Azure KeyVault Secret hashicorp-vault-init: keyvault.BaseClient#GetSecret: Failure responding to request: StatusCode=403 -- Original Error: autorest/azure: Service returned an error. Status=403 Code="Forbidden" Message="The user, group or application 'appid=1e3d98b4-4f3c-482e-9a46-5bb6aeee6662;oid=b9eb66e8-b52b-401f-945b-ade1626026d4;numgroups=1;iss=https://sts.windows.net/bc877e61-f6cf-4461-accd-0565fa4ca357/' does not have secrets get permission on key vault 'tmxdevopstmxhcvn18;location=eastus'. For help resolving this issue, please see https://go.microsoft.com/fwlink/?linkid=2125287" InnerError={"code":"AccessDenied"}
Error: keyvault.BaseClient#GetKey: Failure responding to request: StatusCode=403 -- Original Error: autorest/azure: Service returned an error. Status=403 Code="Forbidden" Message="The user, group or application 'appid=1e3d98b4-4f3c-482e-9a46-5bb6aeee6662;oid=b9eb66e8-b52b-401f-945b-ade1626026d4;numgroups=1;iss=https://sts.windows.net/bc877e61-f6cf-4461-accd-0565fa4ca357/' does not have keys get permission on key vault 'tmxdevopstmxhcvn18;location=eastus'. For help resolving this issue, please see https://go.microsoft.com/fwlink/?linkid=2125287" InnerError={"code":"AccessDenied"}

With the linked PR the only remaining issue is that TFE lacks permission to delete the keyvault that is created. So the purge permission needs to be added to the list so TFE can delete the keyvault as needed


Fix for browserify

Browserify can't process dynamic require() expressions so use static ones.

Hi @hiddentao, thank you for your pull request.
Can you explain what you tried to fix? or what is your use case?
Your change is equivalent to the old code. Be aware that usage in browser need to cross browser compatible (browser.js). There is a build script for generating browser releases

@vanng822 I want to require() this module into front-end code that then gets bundled using Browserify. Browserify usually automatically grabs it from the node_modules folder, scans the require() calls within and includes all the necessary files. In order to do this it can't have dynamic require() statements as you had.
I can see why the calls were dynamic. It saves on code repetition. But it also breaks Browserify's operation. I had a look at Browserify's docs to see if I could get it to understand the dynamic expressions but to no avail. And explicitly telling Browserify that it needed to bundle the addition files in the lib folder didn't feel like the right solution to me.

@hiddentao I haven't used Browserify but it feels like they should support dynamic require. I can think of many packages out there doing dynamic require.
Another note here is that there is a browser.js in the lib. I separated it to make clear that part of the code should be loaded in browser but not in node-environment. It patches Object.keys and util.inherits
Wonder if Browserify support any spec file, such as browserify.js? or any spec in package.json? I haven't really done any frontend coding for the latest 5 years so I haven't spend much time on support other nice tools than the traditional way of loading code into browser.

Ok, I guess I can have a look at browser.js and see if I can make it work that way. Will let you know how it works out.

With that I mean that it is ok to make require for each file but we need to require browser.js

Thanks, it would be nice if we can solve this.

Here it is https://github.com/substack/browserify-handbook#browser-field
{
"name": "mypkg",
"version": "1.2.3",
"main": "main.js",
"browser": "browser.js"
}

would be good to call it browserify.js instead of browser.js :-)

Ok just took a look at browser.js. It seems that all it does is patch other functions. You'd still need to include the other files.
When I incorporate this patch browserify is automatically able to go and include all the other files, which means I don't even need to use browser.js. Browserify pulls in and provides browser-friendly versions of node's util module.
From https://github.com/substack/node-browserify/issues/377 it seems that using dynamic require expressions aren't within browserify's scope. However there is a bulkify transform for browserify which may can be used to "bulk require" glob paths. This looks for calls using bulk-require.
So either we rewrite index.js to use a require-bulk call and then specify the use of bulkify in the docs or we actually build a self-contained module and save that as browser.js which can then be used with browserify (and make building that part of the build process).

If it handles Object.keys then we can go with your changes. And you have tested them in different browsers?
I unfortunately don't have my home computer today so can not test (and also take some time to set up browserify).

@hiddentao I will merge now

It is now published
thank you for your PR!

Thanks for the merge. Sorry I couldn't get back to you in time, but it does work in all browsers (mostly thanks to Browserify doing the right thing).


WorkQueueManagerWMBSFileFeeder slowly adding data to dbsbuffer tables

Related to https://github.com/dmwm/WMCore/issues/8528
I've seen WorkQueueManagerWMBSFileFeeder heartbeat alarms since the past weekend, which is hitting us in at least a couple of agents (vocms0252, vocms0254).
Checking the logs on vocms0252...
2018-08-12 15:19:52,946:140043577100032:INFO:WorkQueue:Adding WMBS subscription for vlimant_ACDC0_task_HIG-RunIIFall17wmLHEGS-01118__v1_T_180808_124312_4167
... almost 2 days later ...
2018-08-14 13:11:00,644:140043577100032:INFO:WMBSHelper:Inserting in bulk all the file info into WMBS for vlimant_ACDC0_task_HIG-RunIIFall17wmLHEGS-01118__v1_T_180808_124312_4167
2018-08-14 13:25:55,078:140043577100032:INFO:WMBSHelper:Inserting all the file info into DBSBuffer for vlimant_ACDC0_task_HIG-RunIIFall17wmLHEGS-01118__v1_T_180808_124312_4167
... and now slowly going through these dbsbuffer insertions...

and vocms0254 seems to be stuck processing this ACDC
2018-08-13 16:30:33,521:139965766612736:INFO:WorkQueue:Adding WMBS subscription for vlimant_ACDC0_task_HIG-RunIIFall17wmLHEGS-01122__v1_T_180808_130708_5376

Given the amount of data objects created, it doesn't surprise me that the memory footprint goes up to 5GB (at least for this specific workflow in vocms0254). I'm working on a debug patch to try to pin point the expensive code sections.

Sigh... it took me 450 secs to get all that _wmbsPreparation execution for
vlimant_ACDC0_task_HIG-RunIIFall17wmLHEGS-01122__v1_T_180808_130708_5376
in a testbed+mariadb agent.

@amaltaro, Alan it seems it is slow due to the workflow contain so many files in one block
I see in vocms0254 following workflow has 62536 files in one block
Adding ACDC files into WMBS for vlimant_ACDC1_task_HIG-RunIIFall17wmLHEGS114__v1_T_180815_170325_4076: files: 62536
and vocms0252 below workflow has 223K files in one block
Adding ACDC files into WMBS for vlimant_ACDC0_task_HIG-RunIIFall17wmLHEGS-01118__v1_T_180808_124312_4167: files: 223343
And it take long time to check ~0.5 sec
https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/WorkQueue/WMBSHelper.py#L610

I created the patch to improve the performance.

One other question I have is whether we need to add unmerged ACDC files in DBSBuffer.
I guess if we have parents files we need to add it to tract it but in case we don't have parents we might not need this. (In that case, I can create another patch to skip that)

Good catch, Seangchan! I think we quickly discussed those exists() the last time we were investigating this issue.
About unmerged files in DBSBuffer, I can't think of anything else. So I think you're right and we could skip unmerged insertion into DBSBuffer, unless those files contain parents.


Release beta6

It is not published to Nuget.org, for both:

https://www.nuget.org/packages/Microsoft.Framework.CodeGenerators.Mvc/
https://www.nuget.org/packages/Microsoft.Framework.CodeGeneration/

The tag is there, but not release:
https://github.com/aspnet/Scaffolding/releases/tag/1.0.0-beta6

I closed my issue at aspnet/Mvc since @giggio created it here in scaffolding. This is creating a lot of problems for users. Including this issue

I noticed it has been published to the aspnetmaster feed on myget: https://www.myget.org/gallery/aspnetmaster
I added it to my nuget.config file and it seems to be working. But I have to do more tests.

@sayedihashimi @danroth27 to confirm but I believe we're pointing people at the Yeoman generators instead of these packages for now. We're not sure what the future is for these packages. That they were tagged as beta6 is I think just an artifact of our build publishing scripts. We do still build the package and publish to MyGet, but not to NuGet.org anymore.

This resolved the issue for me now as well.

I wonder if this is a good idea, especially after .tt support discussion.
I can't even start to image how would someone iterate through C# type in yeoman's js.

That is the exact problem of using yeoman to run a scaffolding. It is fine to use yeoman to bootstrap the project, but JavaScript cannot work with Roslyn to find types and create the correct files.
The current implementation with Razor is beautiful and works really well. We are creating our own scaffoldings using it. I hope Microsoft won't drop this package/repo. I also hope they keep it up to date with beta7, etc, until 1.0, even if not supported.

@sayedihashimi @danroth27 to confirm but I believe we're pointing people at the Yeoman generators instead of these packages for now.

Not exactly, I'll try and clear it up here.
First let's make sure that we are using the same language since "scaffolding" means different things to different people. First let's consider it through the lens of Visual Studio 2013. In VS2013 we have the following ways to add ASP.NET related files.

New Project
Add New Item
Add New Scaffolded Item

The difference between Add New Item and Add New Scaffolded Item is that the former is just a static text based item template, which at most may contain replacement parameters. Where as Add New Scaffolded Item will generate content based on the project artifacts. For example it can generate views/controllers based on an Entity Framework model. So Add New Scaffolded Item has to be able to understand the project.
So scaffolding has these two high level definitions.

Generate static assets
Generate assets based on existing assets

I think yeoman is great at the first part Generate static assets. We already have existing yo generators which are equivalent to File->New Project and Add New Item from Visual Studio for ASP.NET 5. For ASP.NET 5 to generate assets based on the project (i.e. views/controllers for an EF Model) will require inspecting the project (i.e. loading the types and understanding them) so it will require DNX support. So having a yeoman only story to generate views/controllers doesn't really make too much sense.
Now back to the question, what are our plans with scaffolding? For scaffolding there are two high level scenarios.

Scaffolding in VS
Command line scaffolding

The in VS experience has always been a higher priority. When we started looking at the scaffolding experience we were thinking to build an experience inside of VS which was built on top of a command line experience. A few months back we created the command line scaffolding prototype. Since then we have decided that defining a great command line experience for scaffolding would take more time than what we currently have. Our thoughts are to enable an in Visual Studio experience for scaffolding and then at a later time create a cross platform command line experience. The initial support is likely to be based on the UI that we already have for VS2013 and will likely use T4 as the engine to create the content like it was in VS2013.
So to answer the question, what's the future of the CodeGenerator nuget package. Development is pretty much "on hold" for that now. Once we have time we will revisit our command line scaffolding experience and we are not sure what exactly that will entail. We are not likely to even think about this until 1.0 is shipped which is currently slated for Q1 2016.
If there is enough interest in a command line scaffolding story created by the community let me know. I'd love to be involved in that effort.

@heathyates

do you have some updated articles you are aware of for yeoman generators to create the Controllers/Views for an MVC project

Here is the latest on yo aspnet http://blogs.msdn.com/b/webdev/archive/2015/07/04/updates-to-asp-net-5-yeoman-generators-for-beta-5.aspx
@Muchiachio

I wonder if this is a good idea, especially after .tt support discussion.
I can't even start to image how would someone iterate through C# type in yeoman's js.

See my reply https://github.com/aspnet/Scaffolding/issues/105#issuecomment-127765528
@giggio

That is the exact problem of using yeoman to run a scaffolding. It is fine to use yeoman to bootstrap the project, but JavaScript cannot work with Roslyn to find types and create the correct files.

Yes I agree. See my reply https://github.com/aspnet/Scaffolding/issues/105#issuecomment-127765528.


Route parameters with dots or other punctuation not working

Hi, Thanks for the great work on Sanic!
I just started using it for a small project of mine. One bug which i ran into was its inability to parse parameters with punctuation in them, like so:
@app.route('/entries/domain/<domain>')
async def get_entries_for_domain(request, domain):
...

GET http://<IP_ADDRESS>:8000/entries/domain/kernel.org

Error: Requested URL /entries/domain/kernel.org not found

But at the same time fetching the /entries/domain/kernel_org endpoint works.
Any way to work around this?

Fix by mindflayer pushed, closing issue :)

Thanks guys, that's awesome!


Make VCAP_SERVICE parsing more configurable

Refactor the VCAP_SERVICES parsing to:

Add the ability to select which service is returned (when there is
ambiguity, such as multiple instances of the MQ Light service are bound to
an application)
Consider services with labels that start 'messagehub' as candidates when
locating a set of credentials to use.
Return errors if more than one valid service is found.
Increase unit test code coverage of this capability.

:+1:


dvr 生成的文件owner是root怎么破

想要通过php把它移动到另外一个目录，结果没权限，有解决方案么？

你没有 网站服务器权限？
2018-04-16 7:23 GMT+08:00 wony<EMAIL_ADDRESS>
想要通过php把它移动到另外一个目录，结果没权限，有解决方案么？
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ossrs/srs/issues/1118, or mute the thread
https://github.com/notifications/unsubscribe-auth/ATo8PC1C39_C3MsOjWlIf8kpvnD7tFOFks5to9aLgaJpZM4TVsen
.

Dup to #1111


[logging] Pulling base image message should include image name at least

In default mode werf does not print pulling progress bar, which is unnecessary. But it should print image name that being pulled:

solved


feat: add configurable queries with method chaining

Feature:
Introduce configurable queries so we can set consistency and other query options by using method chaining.
E.g.
 let model = Model {
        pk_field: partition_key,
        ck_field: clustering_key,
        ..Default::default()
    }
    .find_by_primary_key()
    .consistency(Consistency::All)
    .execute(&caching_session)
    .await?;

Todo:

[x] Update find API
[x] Update insert API
[x] Update update API
[x] Update delete API
[x] Update & Unify Callbacks - (from now one we gonna have single callbacks trait)
[x] Update docs
[x] Prepare cargo version 0.4.0

test


Screen Reader does not work as expected

Issue Type: Bug
I've just opened the software and it asked me if I use a screen reader (so I said yes). I use NVDA because I can see a little (using magnify) but I want to listen too. The problem is that when I am navigating with keyboard I have the cursor in a line and screen reader reads the previous line.
It is not posible for me to work like that so I wanted to adress the problem.
Thank you.
VS Code version: Code 1.66.0 (e18005f0f1b33c29e81d732535d8c0e47cafb0b5, 2022-03-30T05:50:14.623Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No

System Info

Item
Value

CPUs
AMD FX(tm)-6300 Six-Core Processor              (6 x 3900)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.95GB (3.31GB free)

Process Argv
--crash-reporter-id 5d0546a0-92a0-4be0-9516-41ebe37fb929

Screen Reader
yes

VM
0%

Extensions: none
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
pythonvsnew555:30457759
vscscmwlcmt:30465135
cppdebugcf:30466690
vscaat:30438848
pynewfile477:30463512

@ANAZHTHTHS thanks for opening this issue and sharing feedback.
I could not reproduce this. So you are saying that you turn on NVDA, and as you move the cursor NVDA always reads the previous line?
Can you reproduce this for every file? Can you reproduce if you do not use magnify? Can you reproduce with VS Code Insiders https://code.visualstudio.com/insiders/

Thank you for your quick response. I’ve tried it again today both standard and insiders version. There is no problem with the lines any more.
The problem now is that when I am reading a line of code and I am moving to the next line with keyboard arrows, the magnifier (default magnifier for windows 10  21H2 19044.1586 x65) loses the target (like in the screenshot).
Also I have set NVDA so as to speak whatever is under the mouse cursor. But in the VSC and VSC insider it doesn’t read the code (it works perfect with the buttons).
Thank you for your time.
PS: English is not my native language so forgive me for any mistakes.
Georgios Tsagkalidis
Special Education Teacher
Στάλθηκε από την Αλληλογραφία για τα Windows
Από: Isidor Nikolic
Αποστολή: Τρίτη, 5 Απριλίου 2022 10:23 πμ
Προς: microsoft/vscode
Κοιν.: ANAZHTHTHS; Mention
Θέμα: Re: [microsoft/vscode] Screen Reader does not work as expected (Issue#146773)
@ANAZHTHTHS thanks for opening this issue and sharing feedback.
I could not reproduce this. So you are saying that you turn on NVDA, and as you move the cursor NVDA always reads the previous line?
Can you reproduce this for every file? Can you reproduce if you do not use magnify? Can you reproduce with VS Code Insiders https://code.visualstudio.com/insiders/
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

I am sorry I didn’t attached the screenshot.
Στάλθηκε από την Αλληλογραφία για τα Windows
Από: Isidor Nikolic
Αποστολή: Τρίτη, 5 Απριλίου 2022 10:23 πμ
Προς: microsoft/vscode
Κοιν.: ANAZHTHTHS; Mention
Θέμα: Re: [microsoft/vscode] Screen Reader does not work as expected (Issue#146773)
@ANAZHTHTHS thanks for opening this issue and sharing feedback.
I could not reproduce this. So you are saying that you turn on NVDA, and as you move the cursor NVDA always reads the previous line?
Can you reproduce this for every file? Can you reproduce if you do not use magnify? Can you reproduce with VS Code Insiders https://code.visualstudio.com/insiders/
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

I believe you are hitting this issue https://github.com/microsoft/vscode/issues/105558
I suggest to use the workaround for now In the meantime, set editor.accessibilityPageSize: 1 in your vscode settings.
If you do that can you still reproduce the issue?


[SPARK-43700][SPARK-43701][CONNECT][PS] Enable TimedeltaOps.(sub|rsub) with Spark Connect

What changes were proposed in this pull request?
This PR proposes to enable pandas-on-Spark TimedeltaOps.sub & TimedeltaOps.rsub for Spark Connect.
Why are the changes needed?
To support pandas API with Spark Connect.
Does this PR introduce any user-facing change?
pandas-on-Spark API TimedeltaOps.(sub|rsub) are available on Spark Connect.
How was this patch tested?
Reusing existing UTs.

Merged to master.


(Testing) Post 4 - invalid use statement within 'main.rs'

The following line produces an error during compilation:
https://github.com/phil-opp/blog_os/blob/d3e4c55fc5a8a7bff16badbdae16a15b6f67ad79/src/main.rs#L7
Error:
error[E0432]: unresolved import `blog_os`
 --> src/main.rs:7:5
  |
7 | use blog_os::println;
  |     ^^^^^^^ use of undeclared type or module `blog_os`

In order to fix this compilation error it must be changed to:
use blog_os::{println};

lib.rs must also explicitly link all dependencies or compilation also fails (at least in my experience):
#[macro_use]
extern crate lazy_static;
extern crate spin;
extern crate uart_16550;
extern crate volatile;
extern crate x86_64;

Concerning your first problem, use blog_os::{println}; is strictly equivalent to use blog_os::println;, so your problem might come from somewhere else.
Regarding your second problem, the explicit link of the dependencies is not required.
What is the version of your compiler ?
Mine is 1.38.0-nightly (60960a260 2019-08-12).

That was my assumption as well, but for some reason it could not find the reference to println. Just thought I would post in case anyone else ran into issues and were looking for a resolution. Similar case with my second issue as well, I was under the assumption that explicit links were not required, but for some reason compilation fails without it. Only the minor changes I stated above supplied everything needed by the compiler.
I'm running rustc 1.39.0-nightly (521d78407 2019-08-25) which may explain the discrepancies here.

@ciehanski Do these errors also happen when building this repository, e.g. the post-04 branch? We regularly verify that the repository builds with the latest nightly using continuous integration and I did not see this error for any nightlies.

@phil-opp your branch compiles and runs just fine as expected, no clue why I was having issues with my version. I'll go ahead and close this issue. Hopefully, if someone else gets stuck as I was, they can be referred here.
Thanks for a wondering blog!

@ciehanski Thanks for the update! Do you have your code online somewhere? Maybe we can understand what was happening here.


Scheduling RollupJob

I have been using Declarative Lookup Rollup Summaries for about a year now, and it makes Salesforce so much more usable, I absolutely love it.
Recently I have run into problem where I keep getting the "dlrs Too many SOQL queries: 101" error. I understand from doing some research that I can get around that by using "Scheduled Incremental Calculate" mode for several rollups as described in this article: "https://github.com/afawcett/declarative-lookup-rollup-summaries/wiki/What-you-need-to-know-about-Scheduling-Rollups". However the problem that I am running into is that I only seem to be able to schedule the RollupJob apex class to run daily or monthly. I would be able to use this if I could run it something like every 30 mins. Can you tell me if there is a way to use "Scheduled Incremental Calculate" mode and schedule it to run every 30 mins?

Sorry thats not possible due to a platform restriction for scheduling Apex jobs. The only other option would be schedule it a few more times throughout the day. But be aware you have a limited number of scheduled jobs per org.


CASMCMS-8249: Document known issue with logging into gitea web page

Description
Document known issue with logging into gitea web page where users are required to log in twice.
Checklist Before Merging

[X] If I added any command snippets, the steps they belong to follow the prompt conventions (see [example][1]).
[X] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in [Cray-HPE][2].
[X] My commits or Pull-Request Title contain my JIRA information, or I do not have a JIRA.

/backport release/1.2


Add FAQ Section

Solution
Add FAQ section in the README.md for users to reference when problem occurs.

Windows Frequent problems:

Postgres error:
/usr/local/bin/docker-entrypoint.sh: /docker-entrypoint-initdb.d/init.sh: /bin/bash^M: bad interpreter: No such file or directory
Solution:
git config --global core.autocrlf input
Delete your local repository.
Clone it again.

@natanasow for consideration in upcoming sprint


Update examples page

Moved examples/00_basic and examples/01_tips_n_tricks from the pymechanical repo to the pymechanical-examples repo See related PR
Added an example script that implements the same example in a remote session or an embedded instance
Changed the layout of the examples landing page to only contain cards

Embedding Examples: links to the embedding examples URL
Remote Session Examples: links to the remote session examples URL
Embedding Instance and Remote Session Examples: links to the remote session & embedding instance script

Have a look at the rendered version of my proposal @klmcadams - see last commit. You can revert it if you prefer some other layout.


[WIP] Fix sporadic pq deadlocks

Coverage increased (+0.05%) to 88.189% when pulling 5c09b5c0800bbe9d0b1377a1b14e8a997f44689a on fix-sporadic-deadlocks into bd66c4f65c769dfd86d976b73b9d661d8cdea161 on master.


Unable to run evaluation. Testbed is having trouble creating a specified conda environment

First, kudos to opensourcing such an inspiring body of work, your scripts are incredibly easy to run.
But, I've encountered a problem that I'm not quite sure what is wrong, could you please help me with reproducing your results?
The following error was thrown when I tried to execute run_evaluation.sh using generated results from GPTs you uploaded in previous issue:
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command 'source /home/yangzhiyu/workspace/SWE-bench/testbed/gpt-4-32k-0613/django__django/4.1/tmpkaujz6pc/miniconda3/bin/activate django__django__4.1 && echo 'activate successful' && pip install -r /home/yangzhiyu/workspace/SWE-bench/testbed/gpt-4-32k-0613/django__django/4.1/tmp9l993fhu/requirements.txt' returned non-zero exit status 127.
It seems like the testbed is having trouble creating a specified conda environment, but I have faithfully followed your instructions on creating the swe-bench environment. Please help.

2024-03-19 18:09:26,914 - INFO - [Testbed] Setting up testbed for django__django__4.1
2024-03-19 18:10:16,867 - INFO - [Testbed] Cloned django/django to /home/yangzhiyu/workspace/SWE-bench/testbed/gpt-4-32k-0613/django__django/4.1/tmp9l993fhu/django__django__4.1
2024-03-19 18:10:16,868 - INFO - [Testbed] Creating environment django__django__4.1; Command: /home/yangzhiyu/workspace/SWE-bench/testbed/gpt-4-32k-0613/django__django/4.1/tmpkaujz6pc/
miniconda3/bin/conda create -n django__django__4.1 python=3.9 -y
2024-03-19 18:11:23,833 - INFO - [Testbed] Installing dependencies for django__django__4.1; Command: source /home/yangzhiyu/workspace/SWE-bench/testbed/gpt-4-32k-0613/django__django/4.
1/tmpkaujz6pc/miniconda3/bin/activate django__django__4.1 && echo 'activate successful' && pip install -r /home/yangzhiyu/workspace/SWE-bench/testbed/gpt-4-32k-0613/django__django/4.1/
tmp9l993fhu/requirements.txt
2024-03-19 18:11:23,872 - ERROR - Error: Command 'source /home/yangzhiyu/workspace/SWE-bench/testbed/gpt-4-32k-0613/django__django/4.1/tmpkaujz6pc/miniconda3/bin/activate django__djang
o__4.1 && echo 'activate successful' && pip install -r /home/yangzhiyu/workspace/SWE-bench/testbed/gpt-4-32k-0613/django__django/4.1/tmp9l993fhu/requirements.txt' returned non-zero exi
t status 127.

@KevinCL16 thanks for notifying us of the issue! We've been debugging this problem ourselves, I'm quite certain this has to do with conda resolution not working properly, perhaps related to the miniconda installation links we are using in harness/context_manager.py file
We're actively working on a fix, and will be sure to follow up here when we've pushed a commit that will resolve this issue!

Much appreciated for your immediate response! Looking forward to give your benchmark a try!

+1, having the same issues

Why did you choose to use conda environments?
I think it will be easier to use Python virtual environments. Just create a venv for each repository and apply diffs based on the base commit, then run pytest on it.
I have faced the same issues, and they were so difficult to solve with minor code changes. I've decided to do this instead.

Why did you choose to use conda environments? I think it will be easier to use Python virtual environments. Just create a venv for each repository and apply diffs based on the base commit, then run pytest on it. I have faced the same issues, and they were so difficult to solve with minor code changes. I've decided to do this instead.

Why did you choose to use conda environments? I think it will be easier to use Python virtual environments. Just create a venv for each repository and apply diffs based on the base commit, then run pytest on it. I have faced the same issues, and they were so difficult to solve with minor code changes. I've decided to do this instead.

Yes, I was thinking the same. Is it possible that you share this code?

The issue is with the pip/python resolution (apart from conda resolution, but if the first problem goes away things start working)
patch:
diff --git a/harness/context_manager.py b/harness/context_manager.py
index ae5e804..c23da94 100644
--- a/harness/context_manager.py
+++ b/harness/context_manager.py
@@ -284,7 +284,7 @@ class TestbedContextManager:

                     # Install dependencies
                     path_to_reqs = get_requirements(setup_ref_instance, self.testbed)
-                    cmd = f"source {path_activate} {env_name} && echo 'activate successful' && pip install -r {path_to_reqs}"
+                    cmd = f"source {path_activate} {env_name} && echo 'activate successful' && {path_conda}/envs/{env_name}/bin/pip install -r {path_to_reqs}"
                     logger_testbed.info(
                         f"[Testbed] Installing dependencies for {env_name}; Command: {cmd}"
                     )
@@ -329,7 +329,7 @@ class TestbedContextManager:

                 # Install additional packages if specified
                 if "pip_packages" in install:
-                    cmd = f"source {path_activate} {env_name} && pip install {install['pip_packages']}"
+                    cmd = f"source {path_activate} {env_name} && {path_conda}/envs/{env_name}/bin/pip install {install['pip_packages']}"
                     logger_testbed.info(
                         f"[Testbed] Installing pip packages for {env_name}; Command: {cmd}"
                     )
@@ -546,6 +546,8 @@ class TaskEnvContextManager:
         if "install" not in specifications:
             return True

+        if specifications['install'].startswith("python") or specifications['install'].startswith("pip"):
+            specifications['install'] = f"{self.conda_path}/envs/{self.venv}/bin/" + specifications['install']
         cmd_install = f"{self.cmd_activate} && {specifications['install']}"
         logger_taskenv.info(
             f"[{self.testbed_name}] [{instance[KEY_INSTANCE_ID]}] Installing with command: {cmd_install}"

I was able to fix this issue by forcing usage of my existing miniconda version instead of a locally installed one. This might point towards the source of the issue being incorrect resolving of which conda version to use.

I was able to fix this issue by forcing usage of my existing miniconda version instead of a locally installed one. This might point towards the source of the issue being incorrect resolving of which conda version to use.
Concretely I applied this patch to my local fork, then supplied the main conda installation
diff --git a/harness/engine_validation.py b/harness/engine_validation.py
index 3ed1028..fa32546 100644
--- a/harness/engine_validation.py
+++ b/harness/engine_validation.py
@@ -91,7 +91,7 @@ def setup_testbed(data: dict):
         data_dict.task_instances,
         data_dict.log_dir,
         conda_link=data_dict.conda_link,
-        path_conda=data_dict.path_conda,
+        path_conda=data_dict.conda_path or data_dict.path_conda,
         testbed=data_dict.testbed,
         temp_dir=data_dict.temp_dir,
         timeout=data_dict.timeout,
diff --git a/harness/run_evaluation.py b/harness/run_evaluation.py
index b72baf1..21dfbfd 100755
--- a/harness/run_evaluation.py
+++ b/harness/run_evaluation.py
@@ -61,6 +61,7 @@ def main(
     log_dir: str,
     testbed: str,
     conda_link: str,
+    conda_path: str,
     log_suffix: str,
     skip_existing: bool,
     timeout: int,
@@ -173,6 +174,7 @@ def main(
                 args.timeout = timeout
                 args.verbose = verbose
                 args.conda_link = conda_link
+                args.conda_path = conda_path

                 # Remove predictions that have already been evaluated
                 repo_version_predictions = map_repo_version_to_predictions[repo][version]
@@ -245,6 +247,7 @@ if __name__ == "__main__":
     parser.add_argument("--swe_bench_tasks", type=str, help="Path to SWE-bench task instances file", default="dev")
     parser.add_argument("--testbed", type=str, help="Path to testbed directory", default="/tmp")
     parser.add_argument("--conda_link", type=str, default=None, help="(Optional) URL to conda installation to use")
+    parser.add_argument("--conda_path", type=str, help="(Optional) URL to conda path to use", default="/path/to/miniconda3/")
     parser.add_argument("--log_suffix", type=str, help="(Optional) Suffix to append to log file names", default=None)
     parser.add_argument("--skip_existing", action="store_true", help="(Optional) Skip existing logs")
     parser.add_argument("--timeout", type=int, help="(Optional) Timeout in seconds (default: 900)", default=900)

I further had to remove the shellenv to fix issues of not being able to import required test libraries during test evaluation
diff --git a/harness/context_manager.py b/harness/context_manager.py
index 669fa3f..244c5bd 100644
--- a/harness/context_manager.py
+++ b/harness/context_manager.py
@@ -447,16 +447,16 @@ class TaskEnvContextManager:
         )
         self.timeout = timeout

-        shellenv = os.environ.copy()
-        condabinpath = os.path.join(self.conda_path, "bin")
-        shellenv["PATH"] = condabinpath + os.pathsep + shellenv["PATH"]
+        # shellenv = os.environ.copy()
+        # condabinpath = os.path.join(self.conda_path, "bin")
+        # shellenv["PATH"] = condabinpath + os.pathsep + shellenv["PATH"]
         self.exec = ExecWrapper(
             subprocess_args={
                 "check": True,
                 "shell": False,
                 "capture_output": True,
                 "text": True,
-                "env": shellenv,
+                # "env": shellenv,
             }
         )

I ran into the same issue, quickly got around by making the following changes
diff --git a/harness/context_manager.py b/harness/context_manager.py
index 923c98e..1804191 100644
--- a/harness/context_manager.py
+++ b/harness/context_manager.py
@@ -281,7 +281,7 @@ class TestbedContextManager:

                     # Install dependencies
                     path_to_reqs = get_requirements(setup_ref_instance, self.testbed)
-                    cmd = f"source {path_activate} {env_name} && echo 'activate successful' && pip install -r {path_to_reqs}"
+                    cmd = f". {path_activate} {env_name} && echo 'activate successful' && pip install -r {path_to_reqs}"
                     logger_testbed.info(
                         f"[Testbed] Installing dependencies for {env_name}; Command: {cmd}"
                     )
@@ -326,7 +326,7 @@ class TestbedContextManager:

                 # Install additional packages if specified
                 if "pip_packages" in install:
-                    cmd = f"source {path_activate} {env_name} && pip install {install['pip_packages']}"
+                    cmd = f". {path_activate} {env_name} && pip install {install['pip_packages']}"
                     logger_testbed.info(
                         f"[Testbed] Installing pip packages for {env_name}; Command: {cmd}"
                     )
@@ -437,7 +437,7 @@ class TaskEnvContextManager:
         self.log_file = os.path.join(log_dir, log_file_name)

         self.cmd_activate = (
-            f"source {os.path.join(self.conda_path, 'bin', 'activate')} "
+            f". {os.path.join(self.conda_path, 'bin', 'activate')} "
             + f"{self.venv} && echo 'activate successful'"
         )
         self.timeout = timeout

I'm getting a similar issue when testing on the gold patches. Almost all of the astropy and requests samples fail with the following in the log
Init Failed: Command 'source /Users/thesofakillers/repos/swe-bench/harness/sweb-testbed/gold_model/astropy__astropy/1.3/tmp6t4i8zbe/miniconda3/bin/activate astropy__astropy__1.3 && echo 'activate successful' && pip install -e .[test]' returned non-zero exit status 1.

@thesofakillers I get a similar issue with several of the Django issues such as django__django-10087:
  File "/root/SWE-bench/harness/testbed/ground-truth-unassisted/django__django/2.2/tmp96drtl6g/miniconda3/lib/python3.11/site-packages/Django-2.2.dev20180622141950-py3.11.egg/django/utils/translation/trans_real.py", line 119, in _new_gnu_trans
    return gettext_module.translation(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: translation() got an unexpected keyword argument 'codeset'

>>>>> Some Tests Failed

Did some research and it looks like it's a problem with my Python version being too new, and it does look like it's using 3.11 from theh logs. Not sure why it's not selecting the right version in the run_evalation.py script.

@kevinlu1248 weird, i had the impression that the conda environments that get created for each sample would take care of using the correct python version 🤔

@thesofakillers It seems to be intermittent. Sometimes it would use the right version but other times it wouldn't. I'll take a better look. I also ran the ground truth results on quarter of the test set and I'm getting only 292/547 passes.

Can folks facing this check if this PR fixes it? https://github.com/princeton-nlp/SWE-bench/issues/55 -- things work for me, but I might've missed something.

Hi all, thanks so much for your patience and the great suggestions. Apologies about the delay in response, we'll be sure to respond more promptly going forwards.
As a summary, here are a couple good takeaways I noticed in the thread (feel free to let me know if I characterized any of these incorrectly)

Use . instead of source (Detailed by @brombaut)
The conda installation version being a potential source of error (Detailed by @nielstron)
A number of installation errors (Detailed by @thesofakillers, @kevinlu1248)

We've also noticed these issues on our side and have spent the last couple weeks putting forth a number of fixes that should address a number of these issues. You can see the report we wrote about it here.
w.r.t the issues mentioned in this thread:

We incorporated the fix to use . instead of source.
We added a lot more detailed installation specifications that should eliminate a good amount of the non-determinism that was being caused by underspecified installation specifications from before.

To this end, if it's possible + convenient, would you mind re-running evaluation to see if any of the original issues are solved? You can also use the check_harness.jsonl predictions file to more rigorously verify whether your harness is installing properly for every repo/version pair in SWE-bench.
Happy to follow up on any further questions.

Closing this thread due to inactivity. Thanks everyone for all the incredibly helpful feedback.
Just as a heads up, we will be introducing a re-vamped version of the SWE-bench evaluation harness that incorporates Docker containers into the evaluation logic. This should eliminate a lot of the issues people are having that can be attributed to running SWE-bench evaluation on different machines / OS's.
We're planning on doing this release within the next two weeks. If you're still interested in evaluating on SWE-bench, please check it out when it comes out! 😄


Android <--> IOS

Why can't Android see iOS?

Getof, what about my project? Why are you acting like this? You said yourself that you did not deceive me and will continue the project!!! Get in touch on a freelance or messenger...

Commit


PyDMD based DMD ROMs

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
Closes #2343
What are the significant changes in functionality due to this change request?
Addition of pydmd library for the importing of several DMD based algorithms
Created interface with RAVEN ROMs
And automatic documentation
And associated tests

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[ ] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

Job Test mac on 3a2b5d8 : invalidated by @Jimmy-INL

Job Test CentOS 8 on 532124e : invalidated by @alfoa

@joshua-cogliati-inl  in Ubuntu PIP machine
ERROR: Could not install packages due to an OSError: [Errno 28] No space left on device

ERROR: exiting with code 1

**Test CentOS 8 ** —

Same on Test CentOS 8

Job Test CentOS 8 on 7470d51 : invalidated by @alfoa

Job Test CentOS 8 on 7470d51 : invalidated by @alfoa

Job Test Ubuntu 18 PIP on 7470d51 : invalidated by @alfoa

Job Mingw Test on 7470d51 : invalidated by @alfoa

@wangcj05 @joshua-cogliati-inl @Jimmy-INL  FY: if you can send feedbacks within tomorrow I can try to address them before leaving on Friday. Otherwise it will need to wait till September.

I will leave today. So this MR will need to wait to September.

Job Test Ubuntu 18 PIP on 7470d51 : invalidated by @Jimmy-INL

Job Test CentOS 8 on 7470d51 : invalidated by @Jimmy-INL

Job Test Ubuntu 18 PIP on 7470d51 : invalidated by @Jimmy-INL

Job Test Ubuntu 18 PIP on 7470d51 : invalidated by @Jimmy-INL

Job Test CentOS 8 on 7470d51 : invalidated by @joshua-cogliati-inl
Cleaned up files on test machine.

Job Test Ubuntu 18 PIP on 7470d51 : invalidated by @joshua-cogliati-inl
Cleaned up files on test machine.

Job Test Ubuntu 18 PIP on 7470d51 : invalidated by @joshua-cogliati-inl
Cleaned up files on test machine.

@wangcj05 @Jimmy-INL can anyone review this? I will fly back on Saturday and I would like to close this if possible.

@wangcj05 @mandd addressed your comments.

Job Precheck on 6dda477 : invalidated by @alfoa

All jobs on 1f77cd0 : invalidated by @wangcj05

Job Mingw Test on 1f77cd0 : invalidated by @joshua-cogliati-inl
windows job killed

@aalfonsi : FYI:

@aalfonsi : FYI:

@wangcj05 fixed

Job Test mac on 1952aeb : invalidated by @alfoa

Job Test mac on 1952aeb : invalidated by @aalfonsi

Changes are good. Checklist is good too.


hot reload(HMR) not work when use other domain

Version
3.0.0-rc.5
Reproduction link
http://www.baidu.com/no-url-here
Steps to reproduce
pls look the domain:
http://<IP_ADDRESS>:8080/sockjs-node/info?t=1532447208549
ws://<IP_ADDRESS>:8080/sockjs-node/095/w330zyvl/websocket
http://www.dev..com/b0b2f0652cccee4c5b96.hot-update.json

when:

my url is  "www.dev.com/test.htm",  and    <script type="text/javascript" src="http://<IP_ADDRESS>:8080/js/pingjia4.js"></script>  in test.htm.
vue-cli-server, listen to "http://<IP_ADDRESS>:8080/"

What is expected?
the domain is wrong
What is actually happening?
the domain is wrong

<EMAIL_ADDRESS>

Use devServer.public in vue.config.js to specify your public HMR URL:
module.exports = {
  devServer: {
    public: 'www.dev.com/test.htm'
  }
}

I upgrade vue-cli to 3.0.0-rc.11 was resolve this issue.

@yyx990803 Thank you very much. That resolves an issue I was having.


[AUTO-CHERRYPICK] Patch CVE-2024-7006 in libtiff - branch main

This is an auto-generated pull request to cherry-pick commit 99483fc7e13a96e7cf7cf331976a971c5b393249 to main. Original PR: #10136

Buddy build.


Static File ?

hi ,
in the camera example (http://developer.xamarin.com/recipes/android/other_ux/camera_intent/take_a_picture_and_save_using_camera_app/)
this is from the MainActivity.cs under take_a_picture_and_save_using_camera_app
don't understand how is this working  you cannot create static file, or use it in a static class. what am i missing here?
public static class App {
public static File _file;
public static File _dir;
public static Bitmap bitmap;
}

sorry need to use Java.IO  instead of System.IO  :)  new to xamarin


Controller 'ngModel', required by directive 'uibDatepickerPopup', can't be found!

Trying to solve this error https://github.com/vitalets/angular-xeditable/issues/450 by upgrading to latest angular-bootstrap I get a different error.
angular-bootstrap: 1.3.2
angular: 1.4.0
angular-xeditable: 0.1.12
<small editable-bsdate="myDate"
             e-name="my-date" e-uib-datepicker-popup="dd/MM/yyyy"
             e-is-open="data.isOpen" e-ng-click="data.isOpen = true" e-on-open-focus="false">
                          {{myDate | date) || 'empty'}}
      </small>

Did you see my comments in #450 or the comments in #449?

Well, I did but non of them helps me to solve both issue I rose. It seems to me that there is a bug in xeditable plugin as it doesn't handle the ng-model properly, however I didn't dig deep into the code...

Can you provide a JSFiddle/Plunker showing your issue?

Sure, here it is: http://plnkr.co/edit/3Z6wvZROmdR6d1uJlRX5?p=preview When you click on the date it throws an error to console...

Here is your issue e-uib-datepicker-popup="dd/MM/yyyy"
It should be e-datepicker-popup="dd/MM/yyyy"
Here is a link to the documentation

I experience the same issue. The official demo has the same issue. Just try opening the datepicker twice:
https://vitalets.github.io/angular-xeditable/#bstime

Thanks a lot @ckosloski It works for me  :smile:

Try using the latest release (0.2.0).  It looks like #489 might have fixed the issues.

This actually fixes it...


[git] Convert one-liner functions to aliases and longer ones to git subcommands

I would like to use the shell functions from the git module as $ g <subcommand> (with the alias g for git) and not, e.g. $ git-dir.
The one liners (e.g. git-dir, git-root) could actually be converted to git aliases if I am not mistaken.
I am not sure how zimfw could register them.
Others would have to be converted to proper shell scripts which git can find and call. Git officially supports custom subcommmands.
This is documented under https://github.com/git/git/blob/master/Documentation/howto/new-command.txt and there are many google results for git own subcommand.
However, doing this right might be a little bit more than simply converting them to standalone shell scripts: setting up completion and also a manpage describing the command would be great.
I guess https://github.com/tj/git-extras could be considered as an example.
What are the thoughts of others?

The one-liners are git-branch-current and git-root and I agree with making them aliases instead. Not sure if we can convert git-dir to a one-liner too.  Or if we use --absolute-git-dir, but that's only available starting from git v2.13.0.
You have a good point with using git subcommands. Our "motto" in Zim is to look for the simpler and faster solutions. The only function we have using completion is git-branch-delete-interactive. If setting up its completion would be easier in case it were a git subcommand, for example, that would already be a con of using subcommands.
@kiryph, do you want to give this a try and submit separate PRs for the aliases and the subcommands?


Failed to install extension - extension is not packaged properly

Getting the error in the title from Playnite when double clicking the pext:

Using latest versions at the time of writing-
Playnite: 8.1
playnite-indiegala-plugin: 1.0
Relevant playnite.log excerpt:
15-10 15:35:54.352|INFO|PlayniteApplication:Executing command "ExtensionInstall" from pipe with arguments "F:\Downloads\IndiegalaLibrary_1_0.pext"
15-10 15:35:54.352|ERROR|ExtensionInstaller:Extension package is invalid, no extension ID found.
15-10 15:35:54.352|ERROR|PlayniteApplication:Failed to install extension.Playnite.SDK.LocalizedException: Extension is not packaged properly.
   at Playnite.Plugins.ExtensionInstaller.VerifyExtensionPackage(String packagePath) in E:\Devel\Playnite\source\Playnite\Plugins\ExtensionInstaller.cs:line 310
   at Playnite.PlayniteApplication.InstallExtensionFile(String extensionFile) in E:\Devel\Playnite\source\Playnite\App\PlayniteApplication.cs:line 1005
15-10 15:35:54.352|INFO|PlayniteApplication:Application already running, shutting down.

So looks like this is the issue: Extension package is invalid, no extension ID found

I posted on forum the resolved package.
https://playnite.link/forum/thread-344-post-2090.html#pid2090

Thanks!
Why not create a GitHub release though?
Most people would prefer downloading from here, it's a reputable sire with automatic AV scans etc...

The release on Github is updated.

I created a issue: https://github.com/Lacro59/playnite-indiegala-plugin/issues/7
Can you post there your Playnite.log for investigate?