Unable to load "_lstm_ops.so" when using rnn.LSTMBlockCell on Windows 10

Environment info
Operating System:
Windows 10, 64 bit
Installed version of CUDA and cuDNN:
CUDA 8.0
cuDNN 5.1
Intalled TF by the following:
pip3 install --upgrade tensorflow-gpu
If possible, provide a minimal reproducible example (We usually don't have time to read hundreds of lines of your code)
import tensorflow as tf
from tensorflow.contrib import rnn
seq_max_len = 6
num_hidden = 5
sample_size = 4

#print(seq_len_arr)
x = tf.placeholder(tf.float32, [None, seq_max_len, sample_size], name='x')

seq_len = tf.placeholder(tf.int32, [None])

lstm_cell = rnn.LSTMBlockCell(num_hidden)
lstmLayers = rnn.MultiRNNCell([lstm_cell]*1)
outputs, states = tf.nn.dynamic_rnn(lstmLayers, x, sequence_length=seq_len, dtype=np.float32)
init_op = tf.global_variables_initializer()

Logs or other output that would be helpful
(If logs are large, please upload as attachment or provide link).
I c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\stream_executor\dso_loader.cc:135] successfully opened CUDA library cublas64_80.dll locally
I c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\stream_executor\dso_loader.cc:135] successfully opened CUDA library cudnn64_5.dll locally
I c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\stream_executor\dso_loader.cc:135] successfully opened CUDA library cufft64_80.dll locally
I c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\stream_executor\dso_loader.cc:135] successfully opened CUDA library nvcuda.dll locally
I c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\stream_executor\dso_loader.cc:135] successfully opened CUDA library curand64_80.dll locally
E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\core\framework\op_kernel.cc:943] OpKernel ('op: "BestSplits" device_type: "CPU"') for unknown op: BestSplits
E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\core\framework\op_kernel.cc:943] OpKernel ('op: "CountExtremelyRandomStats" device_type: "CPU"') for unknown op: CountExtremelyRandomStats
E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\core\framework\op_kernel.cc:943] OpKernel ('op: "FinishedNodes" device_type: "CPU"') for unknown op: FinishedNodes
E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\core\framework\op_kernel.cc:943] OpKernel ('op: "GrowTree" device_type: "CPU"') for unknown op: GrowTree
E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\core\framework\op_kernel.cc:943] OpKernel ('op: "ReinterpretStringToFloat" device_type: "CPU"') for unknown op: ReinterpretStringToFloat
E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\core\framework\op_kernel.cc:943] OpKernel ('op: "SampleInputs" device_type: "CPU"') for unknown op: SampleInputs
E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\core\framework\op_kernel.cc:943] OpKernel ('op: "ScatterAddNdim" device_type: "CPU"') for unknown op: ScatterAddNdim
E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\core\framework\op_kernel.cc:943] OpKernel ('op: "TopNInsert" device_type: "CPU"') for unknown op: TopNInsert
E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\core\framework\op_kernel.cc:943] OpKernel ('op: "TopNRemove" device_type: "CPU"') for unknown op: TopNRemove
E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\core\framework\op_kernel.cc:943] OpKernel ('op: "TreePredictions" device_type: "CPU"') for unknown op: TreePredictions
E c:\tf_jenkins\home\workspace\release-win\device\gpu\os\windows\tensorflow\core\framework\op_kernel.cc:943] OpKernel ('op: "UpdateFertileSlots" device_type: "CPU"') for unknown op: UpdateFertileSlots
Traceback (most recent call last):
File "debug_lstm_zeros2.py", line 33, in
outputs, states = tf.nn.dynamic_rnn(lstmLayers, x, sequence_length=seq_len, dtype=np.float32)
File "C:\Users\jun\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\ops\rnn.py", line 545, in dynamic_rnn
dtype=dtype)
File "C:\Users\jun\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\ops\rnn.py", line 712, in _dynamic_rnn_loop
swap_memory=swap_memory)
File "C:\Users\jun\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\ops\control_flow_ops.py", line 2626, in while_loop
result = context.BuildLoop(cond, body, loop_vars, shape_invariants)
File "C:\Users\jun\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\ops\control_flow_ops.py", line 2459, in BuildLoop
pred, body, original_loop_vars, loop_vars, shape_invariants)
File "C:\Users\jun\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\ops\control_flow_ops.py", line 2409, in _BuildLoop
body_result = body(*packed_vars_for_body)
File "C:\Users\jun\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\ops\rnn.py", line 695, in _time_step
skip_conditionals=True)
File "C:\Users\jun\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\ops\rnn.py", line 177, in _rnn_step
new_output, new_state = call_cell()
File "C:\Users\jun\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\ops\rnn.py", line 683, in
call_cell = lambda: cell(input_t, state)
File "C:\Users\jun\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\contrib\rnn\python\ops\core_rnn_cell_impl.py", line 655, in call
cur_inp, new_state = cell(cur_inp, cur_state)
File "C:\Users\jun\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\contrib\rnn\python\ops\lstm_ops.py", line 402, in call
use_peephole=self._use_peephole)
File "C:\Users\jun\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\contrib\rnn\python\ops\lstm_ops.py", line 122, in _lstm_block_cell
return _lstm_ops_so.lstm_block_cell(
AttributeError: 'NoneType' object has no attribute 'lstm_block_cell'
Thanks a lot for your assistance!
Jun

This is a duplicate of  #7500 - there was a bug that's since been fixed.  The nightly builds have the fix.


Config Initialisation

Whenever I run node .config, it gets an unexpected token error. I've only changed the mongo user/pass and Chromecast app ID.
{
"appId": "XXXX1234",
"mongoUser": "fionn",
"mongoPass": "atestpassword",
"mongoAuthSource": "admin",
"mongoHost": "<IP_ADDRESS>",
"mongoPort": 27017
}
Here's the full stack trace:
C:\dev\repos\multicast.config:2
"appId": "XXXX1234",
^
SyntaxError: Unexpected token :
at createScript (vm.js:80:10)
at Object.runInThisContext (vm.js:139:10)
at Module._compile (module.js:599:28)
at Object.Module._extensions..js (module.js:646:10)
at Module.load (module.js:554:32)
at tryModuleLoad (module.js:497:12)
at Function.Module._load (module.js:489:3)
at Function.Module.runMain (module.js:676:10)
at startup (bootstrap_node.js:187:16)
at bootstrap_node.js:608:3

node .config

is attempting to run the file .config as though it were a Node script. The command you're looking for is
multicast config

OR (note the space between . and config)
node . config

However, if you've already manually edited the .config file, this step is not necessary. You can get started by running
multicast start

OR
node .


Fix CNIEnv concurrency issue

This is very similar to #3522, and addresses another facet of the same underlying problem (CNIEnv not being safe to use concurrently).
Failure is typically showing-up with images in integration tests (on my laptop, shows up after 20+ runs).
This is not a good long-term solution (the right solution is to rewrite CNIEnv with concurrency in mind) - but it will alleviate the problem in a bunch of cases for now.

@AkihiroSuda ready to go.


Change The UI Of Landing Page With Adjusting The Navbar Section

Prerequisites

[X] I am an Open Source Contributor
[X] I checked to make sure that this issue has not already been filed

Description
I would Like To Update The  UI Of Landing Page With Adjusting The Navbar Section
Screenshots
No response
Code of Conduct

[X] I follow Contributing Guidelines of this project.

@Rakesh9100 Assign This Issue To Me Under SWOC

Do you want to put navbar in the landing page? @Kapileswar-Moharana

@Rakesh9100 I would Like To Update The UI Of the Landing Page With Adjusting The Navbar Section Font And I con According To The Theme of Webpage

Provide the screenshots and details of what changes you would like to make @Kapileswar-Moharana

UI enhancement issue is already open, closing this issue.


how to change app icon?

how do u change this to some other image?

⚠ It looks like there hasn't been any recent updates on this issue.  If you created this issue and no longer consider it
open, then please login to github and close the issue.
If there is no further activity on this issue, it will be automatically closed in the next week.

I am a bot reaching out to you with an automated response.


Step 3出错

Warning: no short audios found, this IS expected if you have only uploaded long audios, videos or video links.
this IS NOT expected if you have uploaded a zip file of short audios. Please check your file structure or make sure your audio language is supported.
重新按照说明书上传过几次，视频链接、长视频、长音频最后都会出现这个问题

this IS expected if you have only uploaded long audios, videos or video links.
就是说如果你上传的都是视频链接、长视频、长音频，这是EXPECTED的

那如果我短音频也报这个错误要怎么解决呀


multiple calls to done() don't cause a test to fail

describe('The features list contains a lie!', function() {
    it("should fail when done is called multiple times", function(done) {
        // this passes and it shouldn't
        done();
        done();
        done();
    });
});

this is by-design, sometimes APIs are written incorrectly and will invoke the callback several times, so this should fail

What does "detects multiple calls to done()" on the website mean, then?
And what was this issue fixing? https://github.com/visionmedia/mocha/issues/35
Or maybe I wasn't clear? I want it to fail and it doesn't.  That test passes.

oh fuck haha i really need to read things better, i missed that you said it didnt fail

hmm what version? it does fail for me:

  ..

  ✖ 1 of 1 tests failed:

  0) something should fail:
     Error: done() called multiple times
      at multiple (/Users/tj/Projects/mocha/lib/runnable.js:122:24)
      at done (/Users/tj/Projects/mocha/lib/runnable.js:127:26)
      at /Users/tj/Projects/mocha/lib/runnable.js:143:9
      at Test.fn (/Users/tj/Projects/mocha/test.js:5:5)
      at Test.run (/Users/tj/Projects/mocha/lib/runnable.js:140:15)
      at Runner.runTest (/Users/tj/Projects/mocha/lib/runner.js:271:10)
      at /Users/tj/Projects/mocha/lib/runner.js:315:12
      at next (/Users/tj/Projects/mocha/lib/runner.js:199:14)
      at /Users/tj/Projects/mocha/lib/runner.js:208:7
      at next (/Users/tj/Projects/mocha/lib/runner.js:157:23)
      at Array.0 (/Users/tj/Projects/mocha/lib/runner.js:176:5)
      at EventEmitter._tickCallback (node.js:192:40)

are you using it in the browser or node?

I'm using it in the browser. I installed whatever you get when you run "npm install mocha" yesterday. How do I check the version of the npm package again?

I'm using it with chai's expect interface for assertions, but surely that can't make a difference? The test case above doesn't do any assertions, so I guess not. I just ran it again as a sanity test and that test still passes.

hmm you're right, in the browser it appears to not be working, I'll mark this as a bug

I may have a related issue.  I have a test that calls done() once, but the test fails with "Error: done() called multiple times".
The test looks like this:
it ("returns json", function (done) {
    getConcept (function (statusCode, string, response, contract) {
	response.data.concept.should.exist;
	log.log ("about to call done");
	done();
    });
});

I only see "about to call done" once in the console output.  Is this a bug in Mocha?

I was able to resolve the issue I just described by increasing the timeout (--timeout option).  Not sure if this would be considered a bug or not, leaving it here in case it is.

I can confirm that this happens for me in the browser version too.
It looks like the HTML Reporter is causing the problem. If you switch to the Spec reporter and make process.stdout.write output via console.log it works as per the CLI.


Schedule Hold not populating in preset_modes

Describe the bug
"Schedule Hold" is returned by the S30 any time the fan or temperature is changed from the default, in property preset_mode.  This causes an error to pop up in the thermostat card on load, such as:
Preset mode is not valid. Valid preset modes are: schedule IQ, Summer, Winter, Fall/Early Spring, Default, away, cancel hold, cancel away mode, none.
The above list of modes is populated in property preset_modes (note plural)
To Reproduce
Steps to reproduce the behavior: create a thermostat card tied to the HVAC zone, change either the fan or temperature setting
Expected behavior
Schedule Hold should be a member of the list in preset_modes to prevent the above error
Screenshots/Logs

Version

Home Assistant: 2024.6.*
This Integration: 2024.6.0

**Integration Configuration **

Cloud or Local Connection: Local
Inverter or Sensor Diagnostics Enabled: Sensor

Additional context
N/A

Thanks for reporting.  Should be fixable.
Couple of potential approaches.
a) if the thermostat is in Schedule Hold, Schedule Hold will be added to the valid list of presets
b) if the thermostat is not in Schedule Hold, Schedule Hold will not be in the valid list of presets
c) any attempt to set the preset to "Schedule Hold" will generate an error.
Alternate approach
a) always have schedule hold in the list of presets
b) any attempt to set the preset to "Schedule Hold" will generate an error.
Thoughts?

Personally, I would probably approach it the same as cancel hold, since that is not an actual preset. Barring that, it would appear that Schedule Hold should be available on every unit, so probably statically add it to the list?

In further thought, the first approach makes more sense and it appears you are already headed that direction in the PR.

. I don't suppose we can tell what preset we're coming from to trap the error and set the preset back to a valid one?

I think we can.  Lennox uses numerical ids for the schedules. So 1-16 are the user presets.   When we cancel it, it goes back to 3.  How would you see this working?

That sounds promising

So it turns out that we can't add that preset in sometimes.  So we are going with
a) always have schedule hold in the list of presets
b) any attempt to set the preset to "Schedule Hold" will generate an error.
Note, when attempting to do B in the climate card and error is reported to the UI; however the climate cards "optimistic" mode will show schedule hold temporarily until it's timer expires or the card is reloaded.

This should be fixed in


Various Jira Program Changes

Hello @jszmajda,
Could you take a look at these changes and merge them? This PR's highlights:

Refactor the Jira Issue Class to use modules for SLA time tracking and triage time tracking, as the class had too many responsibilities and was growing too large. This will make adding additional features easier (QA time tracking or Kate is in the works).
Update definition of workday to be 8 am to 6 pm. This means that if a P4 issue is created after 6pm, the due date of said issue will be one business day later.
Make P4 issues due at the end of the business day by default (6pm).
Clean up code through rubocop and general program maintenance

Thank you so much!
Gabo

Looks great!


Fix support for arrays

The SDK had support for static non-string arrays when the format was T[n] as specified here https://github.com/FuelLabs/fuel-specs/blob/master/specs/protocol/abi.md#array
But now arrays in Sway are defined as [T; size] for type T and the generated ABI looks like "type":"[T; size]".
This broke the array support in the SDK and we should fix it by changing the parsing from T[n] to [T; size].

[ ] Change ABI parsing from T[n] to [T; size];
[ ] Update all tests in harness to include the right json ABI;
[ ] Update the fuel-specs's ABI section.

👀

👀

Was about to tag you and the TS folks haha. The same issue should exist in fuels-ts.


Restore interlace

Should FastTransforms copy over the interlace definition instead of relying on this package?

Probably. We can remove it in the next breaking version


Add SecretRef to top-level resources

Description
This pr adds the secret ref to the top-level external network resources, in order to make easier for external tools to understand when the gateway is set up

/build

/merge


Improve SEO

The search engine optimization of the website isn't great and could be improved. Work needs to be scoped out. This will act as an umbrella issue.

The website currently shows up at the no. 2 spot for me in an incognito window. I think this is ok for now but could maybe still be improved for other search terms.


[sbt 2] Remove usage of Manifest in Structure.scala

I introduce KeyTag to convey information about the nature of the attribute - a setting, a task, an input task - and its type argument. We don't need to coerce any scala.reflect.Manifest anymore.

@eed3si9n I need a new approval to merge this.


Snippets search

Search bar on snippets page to filter snippets by:

title
description
code
language

enhancement: clear button that appears with text.


what version of Docker?

Describe the bug
[A clear and concise description of what the bug is.]
(docker: 'compose' is not a docker command.)
To Reproduce
Steps to reproduce the behavior:
docker compose up -d
Expected behavior
To work. That command complains about the -d, if I leave it off then get above message.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Installed version is 24.05
app-containers/docker
Available versions:  24.0.5-r1^sti ~24.0.6^sti ~24.0.7-r1^sti ~25.0.1^sti ~25.0.4^sti ~26.1.0-r1^sti

Ok, for Gentoo users, you need docker, docker-cli and docker-compose
Stable is fine as of time of writing, to get it installed.
Not working yet, only shows option for OpenAI and not Ollama...

Can close.


feat: Mongo Connection String Secrets

Description
Adds functionality in service deployment templates to conceal database connection strings that might contain credentials. This functionality is similar to how s3.secretAccessKey is handled by creating a base64 encoded string from the value in values.yaml. Additionally, provides option to configure more secure, custom secret objects such as External Secrets.
This is done by conditionally suppressing the default secret-mongoConnectionString.yml template creation, while still directing the deployment templates to render yaml for a secretKeyRef. This works so long as the custom secret object's name, the key match what is expected in the secretKeyRef.
For example this secret object's metadata.name and spec.data[*].name parameters respectively match the secretKeyRef.name and secretKeyRef.key :
#custom-mongoSecret.yaml
apiVersion: 'kubernetes-client.io/v1'
kind: ExternalSecret
metadata:
  name: {{ include "sorry-cypress-helm.fullname" . }}-mongodbsecrets
spec:
  backendType: systemManager
  data:
    - key: /path/to/parameter
      name: MONGODB_URI

#templates/deployment-director.yml
 52           valueFrom:
 53             secretKeyRef:
 54               name: {{ include "sorry-cypress-helm.fullname" . }}-mongodbsecrets
 55               key: MONGODB_URI

Two parameters were added to values.yaml to configure the secrets when using a mongodb connection string. This leaves mongodb.mongoConnectionString intact and unchanged.
#values.yaml
274   mongoSecretConnectionString:
275     enableSecret: false
276     enableCustomSecret: false

When mongodb.ConnectionString is empty, it is ignored. MONGODB_URI will be rendered in the API and Director deployment with a template default.
When mongodb.ConnectionString is not empty MONGODB_URI will be rendered in the API and Director deployment with its value.
When mongodb.ConnectionString is not empty and either mongoSecretConnectionString.enableSecret: true or mongoSecretConnectionString.enableCustomSecret: true MONGODB_URI will be rendered in the API and Director deployment with the secretKeyRef name and key.
mongoSecretConnectionString.enableSecret: true means that the default secret-mongoConnectionString.yml file be rendered and it will be set to a base64 encoded version of mongodb.mongoConnectionString
mongoSecretConnectionString.enableCustomSecret: true means that the default secret-mongoConnectionString.yml file won't be rendered. However, the secretKerRef in the API and Director deployment will be rendered using what is provided in a custom secret's object.
If both are true, there could be a conflict with the default secrets file and a custom one applied to in the same Kubernetes namespace.
Related Issue
https://github.com/department-of-veterans-affairs/va.gov-cms/issues/9665
https://github.com/sorry-cypress/charts/issues/126
Motivation and Context

Department of Veterans Affair's VA.gov modernization project is looking for a way to parallelize cypress tests in support of our Content Management System.  Sorry-Cypress is deployed into an AWS EKS cluster and using all of the other AWS Cloud integrations supported by Sorry-Cypress e.g. DocumentDB, S3.
AWS DocumentDB provides Applications access to it's cluster using a URI that contains credentials. We commit our values.yaml so Argo CD can manage the deployment of the app. By best practice we shouldn't commit secrets to a source code repository. Using Helm's pattern for secrets is effectively the same situation.
This is a feature that allows Sorry-Cypress to accept MongoDB Connection Strings as a secret and from an alternative secrets repository.

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Helm Tests and Chart Testing tool. Expanded existing tests to explicitly cover areas in template logic that rely on the value of mongodb.mongoConnectionString

[x]  mongo-connectionstring-values.yaml
[x] mongo-secret-connectionstring-values.yaml

Checklist:

[x] Expand test coverage
[x] Update changelog
[x] Update documentation

A couple of additions if you wouldn't mind?
Please can you update the changelog and explain how people handle the breaking change?
If feels like the CI might benefit from additional tests? Could you add some please? https://github.com/sorry-cypress/charts/tree/main/charts/sorry-cypress/ci https://github.com/sorry-cypress/charts/tree/main/charts/sorry-cypress/templates/test
Thanks

A couple of additions if you wouldn't mind?

I certainly can! I initially called this a breaking change based on how I repurposed the use of mongodb.mongoConnectionString. I realized I didn't need to do that and it would be easier to leave it alone in favor of adding other parameters.  As is, this shouldn't break anything, and is backwards compatible. I'm still testing this out on our infrastructure.
I'll take the PR out of draft as soon as I complete:

[ ] Expand test coverage
[ ] Update changelog
[ ] Update documentation

@tico24 I think I need some help with the tests. New to helm testing.
First, I'm kind of confused how ct finds the the values files in charts/charts/sorry-cypress/ci. The ct documentation talks about how ct looks for a ci folder in the chart's root directory. charts/charts/sorry-cypress/ci/ doesn't look like the root. Am I over thinking this?
More importantly, I think test coverage should be expanded to test an explicit mongoConnectionString when .Values.mongodb.internal_db.enabled is true. However, the other case when external_db.enabled is true seems harder to test. Is the latter too far out of test scope to cover with mongoConnectionString?
Fishing for hints on what tests you think will be beneficial.

@tico24 I think I need some help with the tests. New to helm testing.

I had to think a while on it but I discovered one way to add test coverage to areas using mongodb.mongonConnectionString. The ci yaml files use name overrides to set the names of database resources so a MONGODB_URI can use that predetermined name for connections.
Two test files validate the the use of mongodb.mongonConnectionString:

mongo-connectionstring-values.yaml Specifies the name of the Mongo DB K8s service and sets the connection string to that name in a mongo URI. It validates that the logic in the Director and API deployment templates uses those values correctly.
mongo-secret-connectionstring-values.yaml Does the same as above but use a helper template to base64 encode the connection string. This validates the same as the above, as well as the creation of a K8s Secret object that contains the base64 encoded connection string.

The other use cases involve connecting to an external DB. I'm not sure if it's possible to mock that test in ci.

It's possible... just not particularly fun. We'd need to update the github workflow to deploy a mongodb to the cluster, and then reference that as our 'external' database. We'd end up always deploying mongodb for every test case though, so maybe that's not practical.
I'm more than happy for you to not test that if that's something you'd prefer.

My GUESS would be that the service goes to both the primary and the read-only replica of mongodb... so you occasionally hit the 'not master' error.
There's probably another service just for the primary db.
I'm afraid I don't have much time today to properly investigate

From memory. I think you can cheat and set mongodb.architecture: standalone and it'll only create you one db instance.. no replication.

Looking at the MongoDB pod configuration shows the replica set name: MONGODB_REPLICA_SET_NAME:         rs0 appending the replicaSet parameter to the connection string set to rs0 should do the trick. No need to cheat :)
The Director service should be able to find the master node with mongodb://hostname:serviceport/?replicaSet=rs0


A helper function for simple HTML tag removal

See https://github.com/apify/crawlee/blob/master/packages/utils/src/internals/cheerio.ts#L42-L85 for inspiration.
The Python version should probably use BeautifulSoup and tell the user to install crawlee[beautifulsoup] if they try to use it without dependencies.

I think that BS should already handle it using: soup.get_text("\n", strip=True)
https://www.crummy.com/software/BeautifulSoup/bs4/doc/#get-text . So maybe I should just wrap that in our utility function.


Adding sample JSON object to Ajax documentation

This pull request includes a

[ ] Bug fix
[ ] New feature
[ ] Translation

The following changes were made
Hi, I'm just trying to add a sample JSON object to the Ajax documentation - it would have saved me a little time when I was looking for it. The change is in docs_includes\options\data\ajax.html. Please take a look and let me know what you think.

It would be also worth adding that the id attribute is required, and must start at 1.

There appear to be multiple PRs addressing this section:
#5002
#4863
#4861
#4814
#4662
We should pick one of these, or integrate several to provide the most comprehensive answer.

Not sure what "status" : 200 does in the context of Select2, but the pagination info is useful.

Thanks, this has been merged with some of the other PRs for this section, and is now reflected on the live docs.  See http://select2.github.io/options.html#what-should-the-results-returned-to-select2-look-like


Fastlane Supply: Distribute the build to testers for Alpha/Beta Track

Hi, Would like to setup Fastlane for Android and wanted to submit the apps for Beta/Alpha Track. Now my requirement is, once uploaded, I need to distribute the version for the list of testers who are already configured. Is there anything to distribute to Android Testers please, like the way for iOS TestFlight. I have nearly 30+ apps to submit for testing, looking for automated distribution to testers. Please let me know if this already available in your documentation. Thanks

Here is the env details:
Generating fastlane environment output, this might take a few seconds...
🚫 fastlane environment 🚫
Stack

Key
Value

OS
10.11.6

Ruby
2.0.0

Bundler?
false

Git
git version 2.10.1 (Apple Git-78)

Installation Source
~/.rvm/gems/ruby-2.0.0-p648/bin/fastlane

Host
Mac OS X 10.11.6 (15G1217)

Ruby Lib Dir
~/.rvm/rubies/ruby-2.0.0-p648/lib

OpenSSL Version
OpenSSL 1.0.2e 3 Dec 2015

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode_8.app/Contents/Developer/

Xcode Version
8.2.1

System Locale

Error

No Locale with UTF8 found 🚫

fastlane files:
`./fastlane/Fastfile`
# Customise this file, documentation can be found here:
# https://github.com/fastlane/fastlane/tree/master/fastlane/docs
# All available actions: https://docs.fastlane.tools/actions
# can also be listed using the `fastlane actions` command

# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`

# If you want to automatically update fastlane if a new version is available:
# update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "2.14.2"

default_platform :android

platform :android do
  before_all do
    # ENV["SLACK_URL"] = "https://hooks.slack.com/services/..."
  end

  desc "Runs all the tests"
  lane :test do
    gradle(task: "test")
  end

  desc "Submit a new Beta Build to Crashlytics Beta"
  lane :beta do
    gradle(task: "assembleRelease")
    crashlytics

    # sh "your_script.sh"
    # You can also use other beta testing services here
  end

  desc "Deploy a new version to the Google Play"
  lane :deploy do
    gradle(task: "assembleRelease")
    supply
  end

  # You can define as many lanes as you want

  after_all do |lane|
    # This block is called, only if the executed lane was successful

    # slack(
    #   message: "Successfully deployed new App Update."
    # )
  end

  error do |lane, exception|
    # slack(
    #   message: exception.message,
    #   success: false
    # )
  end
end

# More information about multiple platforms in fastlane: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Platforms.md
# All available actions: https://docs.fastlane.tools/actions

# fastlane reports which actions are used
# No personal data is sent or shared. Learn more at https://github.com/fastlane/enhancer

`./fastlane/Appfile`
json_key_file "" # Path to the json secret file - Follow https://github.com/fastlane/supply#setup to get one
package_name "com.*.*" # e.g. com.krausefx.app

fastlane gems

Gem
Version
Update-Status

fastlane
2.23.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

executable-hooks
1.3.2

bundler-unload
1.0.2

rubygems-bundler
1.4.4

bundler
1.14.3

slack-notifier
1.5.1

rouge
1.11.1

xcpretty
0.2.4

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.5.0

babosa
1.0.2

colored
1.2

highline
1.7.8

commander-fastlane
4.4.4

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

gh_inspector
1.0.2

mini_magick
4.5.1

multi_json
1.12.1

rubyzip
1.1.7

security
0.1.3

xcpretty-travis-formatter
0.0.4

i18n
0.7.0

thread_safe
0.3.5

tzinfo
1.2.2

activesupport
<IP_ADDRESS>

json
1.8.3

excon
0.54.0

plist
3.2.0

faraday
0.11.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20161129

faraday_middleware
<IP_ADDRESS>

fastimage
2.0.1

public_suffix
2.0.5

addressable
2.5.0

CFPropertyList
2.3.5

claide
1.0.1

nanaimo
0.2.3

xcodeproj
1.4.2

unicode-display_width
1.1.1

terminal-table
1.7.3

generated on: 2017-03-27

Hi @arokiagetz 👋
It sounds like you're getting started with Android beta testing, so let me suggest a couple resources:
To better understand things from the perspective of Google Play, check out: https://support.google.com/googleplay/android-developer/answer/3131213?hl=en
On the fastlane side, you'll want to make sure you've done the steps for setting up supply. After that, you should be ready to get started with beta deployment with fastlane 👍
I hope that helps you get things going! 🚀

thanks @mfurtak, will setup supply and get back


feat(control_performance_analysis): add new functionalities to evaluate the control modules

Description
Please see (#567).
To close this issue, I want to add new functionalities to control_performance_analysis package.
New Design:

The outputs which are marked with * will be added.
 For BUS ODD, we need to stay public transportation limits.
Transportation Limits

Referance
Also, with trajectory_generator_node, we will able to test our control modules with custom paths without any map data.
Related links
Tests performed
Notes for reviewers
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@brkay54 Thank you for the PR. The basic design looks good to me.
I have some questions:

what does the tracking_curvature_discontinuity_ability mean?
controller_processing_time is in the output of the control_performance_analysis, but it needs to be calculated in the control module itself.

FYI, some values are also calculated in the planning_evaluator node.

* what does the `tracking_curvature_discontinuity_ability` mean?

I didn't explain it sorry for that. Actually, we want to measure the capability to deal with curvature discontinuity. It will be scored with: delta(curvature) * (1 / (1 + delta(lateral_error))) (but I'm not sure with this equation, I need to think about it more. If you have any suggestion please share with me.)

* `controller_processing_time` is in the output of the `control_performance_analysis`, but it needs to be calculated in the control module itself.

Yes you are right. I will change this output name. It will measure the time between the control messages.

FYI, some values are also calculated in the planning_evaluator node.

Thank you, I will check there.

cc @xmfcx @maxime-clem @mitsudome-r
In current BUS ODD architecture, we have nav_msgs::Odometry output from localization stack. See here.
There is no measured acceleration output there. However in localization discussion, people decided to (I guess) add measured acceleration output to localization stack. Please see here.
Issue #567 was labeled with BUS ODD. It is little confusing. Should I assume there will be measured acceleration output from localization stack? Otherwise, I will calculate the estimated acceleration and I will evaluate the control stack with that acceleration.

cc @xmfcx @maxime-clem @mitsudome-r @MertClk
In current BUS ODD architecture, we have nav_msgs::Odometry output from localization stack. See here.
There is no measured acceleration output there. However in localization discussion, people decided to (I guess) add measured acceleration output to localization stack. Please see here.
Issue #567 was labeled with BUS ODD. It is little confusing. Should I assume there will be measured acceleration output from localization stack? Otherwise, I will calculate the estimated acceleration and I will evaluate the control stack with that acceleration.

We are working on a new message for the localization output, will post the PR here tomorrow.

Summary: We re-calculated error accelerations with @boyali , I implemented them. Ali is going to check them again. In vehicle monitoring ( monitoring accelerations and jerks), I calculated them by using timestamps of messages but I am going to change them. I will calculate them with delta_location and delta_velocity. After that I am going to clear up the code, and it will be ready for review.

@maxime-clem @boyali It is ready for review, instructions are written in readme.md. Can you try the evaluation tool? If you see any problem please share with me.

@xmfcx merge please?


[WIP] First draft of backwards compatibility promise

So i made a small first draft of what could be the backwards compatibility promise based on Semver  (#14) . Please feel free to provide feedback. Anything is welcome, things that should be added, things that should be specified in specific ways, things that need to be improved, etc.

Closes #14

LGTM


HL-697 | Index all applications with tabs, add app to a batch

Description :sparkles:

Rewrite handler front page to use tabs
Add two new views to list handled applications, both accepted and rejected ones
Add feature to push applications to a batch (or create one if not existing)

Testing
Front end

Create some applications:

docker exec -it --user appuser benefit-backend python manage.py seed --number=10

Go to https://localhost:3100/ and log in

Marvel and look at new tabs at the front page

Myönnetyt / Kielletyt tabs allow you to push apps to a batch
Confirm that they are in a accepted / rejected batch by visiting https://localhost:8000/v1/applicationbatches/

Applications get bound to the first created batch with matching proposal_for_decision and status="draft"
If there is no existing batch, create one

Backend

Run docker exec -it --user appuser benefit-backend pytest applications/tests/test_application_batch_api.py

Preview

API branch is deployed to platta: https://kesaseteli-pr1974.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

API branch is deployed to platta: https://kesaseteli-pr1974.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

HANDLER branch is deployed to platta: https://handler-pr1974.dev.hel.ninja :rocket::rocket::rocket:

EMPLOYER branch is deployed to platta: https://kesaseteli-pr1974.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://handler-pr1974.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://kesaseteli-pr1974.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://youth-pr1974.dev.hel.ninja :laughing::tada::tada::tada:

API branch is deployed to platta: https://kesaseteli-pr1974.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

YOUTH branch is deployed to platta: https://youth-pr1974.dev.hel.ninja :rocket::rocket::rocket:

HANDLER branch is deployed to platta: https://handler-pr1974.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://handler-pr1974.dev.hel.ninja :laughing::tada::tada::tada:

EMPLOYER branch is deployed to platta: https://kesaseteli-pr1974.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://kesaseteli-pr1974.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://youth-pr1974.dev.hel.ninja :laughing::tada::tada::tada:

API branch is deployed to platta: https://kesaseteli-pr1974.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

HANDLER branch is deployed to platta: https://handler-pr1974.dev.hel.ninja :rocket::rocket::rocket:

EMPLOYER branch is deployed to platta: https://kesaseteli-pr1974.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://handler-pr1974.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe employer result is failed for https://kesaseteli-pr1974.dev.hel.ninja :crying_cat_face::anger::boom::boom:

YOUTH branch is deployed to platta: https://youth-pr1974.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://youth-pr1974.dev.hel.ninja :laughing::tada::tada::tada:

API branch is deployed to platta: https://kesaseteli-pr1974.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

YOUTH branch is deployed to platta: https://youth-pr1974.dev.hel.ninja :rocket::rocket::rocket:

EMPLOYER branch is deployed to platta: https://kesaseteli-pr1974.dev.hel.ninja :rocket::rocket::rocket:

HANDLER branch is deployed to platta: https://handler-pr1974.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://kesaseteli-pr1974.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://youth-pr1974.dev.hel.ninja :laughing::tada::tada::tada:


Add in simple regex query support

closes #84
There may be more efficient ways to do this. But this was my naive approach based on the fuzzy term query.
Please let me know what you would like changed. I'll be adding the document strings after work, but wanted to get this in your hands.
I did not handle the string parsing aspect mentioned in the issue. If this PR looks good I'd like to take a pass through a more comprehensive "query" parsing from a string so we can do regex, distance, phrase, etc from a single string. If that makes sense to do so. :)

I think this looks good.
Let me have a closer look tomorrow, I need to sleep :)
The story about string parsing was about a different ticket.

LGTM merging


Adding Static and Media Files

Configure Static and Media Files in settings.py:
STATIC_URL = '/static/'
MEDIA_URL = '/media/'
MEDIA_ROOT = BASE_DIR / 'media'

Create Static and Media Folders:
mkdir static media

Load Static Files in Templates:
{% load static %}
<link href="{% static 'css/bootstrap.min.css' %}" rel="stylesheet">

Successfully added static and media files folders.


Can metaseg input a video and output the class label?

Thanks for your great work!
I have a specific requirement for my project and I'm wondering if metaseg can cater to it. I need to input an image with dimensions HW3 (height * width * 3 channels) and obtain an "image" output with class labels in the form of HW1 (height * width * 1 channel). The "1" in this context represents that the pixels belong to different classes, rather than representing exact semantic labels.
Before I proceed, I'd like to confirm if metaseg has the capability to handle such a task. Your response would be highly valuable to me. Thank you for your time, and I'm looking forward to hearing from you.

I found the solution, but a new problem has emerged.
What I want to do is to segment a video and label each class. My first idea is to assign different class labels to different mask_image colors (you can see what I did for this below). However, I noticed that the output mask video changes the colors between different frames, making it difficult for me to track the labels (such as cookie/person and so on). I checked your code and found that you did the same thing to the video as the images. So, it is not surprising to get such a result.
Therefore, I wonder if you could share some of your ideas regarding this. Thanks!
What I did  (In sam_predictor.py  line 139):
'''
combined_mask = mask_image
# combined_mask = cv2.add(frame, mask_image)
out.write(combined_mask)
'''

The video is too large (46M) to preview on the github. Here is an link:
https://cloud.tsinghua.edu.cn/d/fefe751e32d549ad8aab/

How to do input video to get class labels？

How did you do it: "1" means the pixel belongs to a different class, not the exact semantic label？

Hello, I can't make it through this method.  Maybe you can have a look at issue #92 . I provide some methods for this issue.


Bug (contrib/azure) - unable to add new discovery URL to azure-user-data

The command ./create-azure-user-data $(curl -s https://discovery.etcd.io/new) did not correctly parse the user-data-template file to replace value of DISCOVERY_URL in the azure-user-data file. The end result was  discovery: null. This was also mentioned in #4593

Thanks for opening this @ritazh! I recently ran into this problem myself but failed to open up a separate issue. Could you take a look at the fix I linked into your PR and let me know if that seems like a reasonable alternative fix to yours?

@sgoings Just tested your fix. Seems to fix the issue as well. What's the best way to proceed?

I'm a little biased, but I'd say let's go with the fix I provided as it doesn't change the highly shared coreos/user-data contents (requiring a matrix of testing). Do you agree and want to head down that road? If so, you're welcome to pull my code over and update your PR #4680.

@sgoings New commit with your changes: https://github.com/ritazh/deis/commit/6718a752d2935a2eb881219db12436437de106af


Update invite.js

Enhancement Proposal for React Invitation Component
The code for the React invitation component presents opportunities for improvements aimed at readability, modularity, and robustness. Below are specific proposals to enhance different aspects of the code:

Modularization of Conditional Rendering:

Introduction of separate functions to render the invite revocation section. This contributes to the clarity and readability of the main code.

Style Enhancement with Default Properties in CopyInput:

Addition of default properties for styles in CopyInput, promoting flexibility and avoiding redundancies in the code.

Robustness Assurance: Null Guest Check:

Inclusion of a check to ensure that the invite object is valid before accessing its properties, reducing potential errors related to undefined properties.

Improved Accessibility with Addition of ARIA Properties:

Insertion of accessibility properties such as aria-label and role to enhance the experience for users with visual impairments.

Additional Modularization with Reusable RevokeSection Component:

Extraction of the invite revocation logic into a separate component, promoting modularity and reusability in the code.

These proposals aim to strengthen the code's quality, following best development practices and providing a solid foundation for future iterations in the React invitation component.

Modularization of Conditional Rendering:
The RevokeSection function was introduced to render the invitation revocation section. This improves the code's modularity, making it clearer and more readable.
Style Enhancement with Default Properties in CopyInput:
The CopyInputWithDefaults constant was created, a customized version of the CopyInput component with default properties. This promotes flexibility and avoids redundancies in the code.
Robustness Assurance with Null Guest Check:
A check was added to ensure that the invite object (invite) is valid before accessing its properties. This helps reduce potential errors related to undefined properties.
Improved Accessibility with Addition of ARIA Properties:
ARIA properties, such as aria-label and role, were added to enhance accessibility and the user experience, especially for users with visual impairments.
Additional Modularization with Reusable RevokeSection Component:
The invitation revocation logic was extracted into the RevokeSection component, further promoting modularity and reusability in the code.

As I said in your other PR, while we appreciate the effort to contribute, absent a change that adds functionality, refactors from people who haven't previously contributed to the project don't really make sense.


Steam Controller not working

I tried to use my steam Controller with GamerOS and it doesn't work. Neither through USB cable (which works on my Fedora box) nor connection through the dongle. Other controllers on the same (powered) hub work fine. Steam asked me to power the controller though, which makes me think the dongle was discovered (haven't checked with lsusb yet).
I think under Fedora I needed to install the kernel-extras package, but I am not sure.

That is strange. My Steam controller works out of the box and I know it works for others too.
What exactly happens when you turn the controller on? Does the Steam logo turn on fully or is it flashing?

What exactly happens when you turn the controller on? Does the Steam logo turn on fully or is it flashing?

Steam asks me to power the controller while pressing X. When I do this, the Steam logo on the Controller flashes for just a millisecond.

That sounds like the batteries are dead. Are you sure you are using good
batteries?
On Sat, 31 Oct 2020 at 10:18, Mario Wenzel<EMAIL_ADDRESS>wrote:

What exactly happens when you turn the controller on? Does the Steam logo
turn on fully or is it flashing?
Steam asks me to power the controller while pressing X. When I do this,
the Steam logo on the Controller flashes for just a millisecond.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/gamer-os/gamer-os/issues/152#issuecomment-719940200,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIWMWB2X4NA7F7WWYB7EVTSNQMCFANCNFSM4TEXBR5A
.

Okay, so the batteries I thought were rechargeable weren't, and they were indeed dead. And the cable which I thought worked, didn't.
Replaced both. Both wired and wireless work fine now.


Errors Encountered During nim-operator Startup

1. Quick Debug Information

Container Runtime Type/Version(e.g. Containerd, CRI-O, Docker): Containerd
K8s Flavor/Version(e.g. K8s, OCP, Rancher, GKE, EKS): K8s
NIM Operator Version: main

2. Issue or feature description
I have encountered a couple of issues while using the nim-operator, and I wanted to share them along with the solutions I found.

Initial Startup Error:

I received the following error during the startup of nim-operator:

E1107 03:29:01.158923       1 reflector.go:158] "Unhandled Error" err="sigs.k8s.io/controller-runtime/pkg/cache/internal/informers.go:106: Failed to watch *v2.HorizontalPodAutoscaler: failed to list *v2.HorizontalPodAutoscaler: horizontalpodautoscalers.autoscaling is forbidden: User "system:serviceaccount:k8s-nim-operator-system:k8s-nim-operator-controller-manager" cannot list resource "horizontalpodautoscalers" in API group "autoscaling" at the cluster scope" logger="UnhandledError"

Upon investigation, I discovered that in the config/rbac/role.yaml file, the term horizontalpodautoscalars should be corrected to horizontalpodautoscalers

After correcting the spelling mistake, the nim-operator reported another error:

2024-11-07T04:24:46Z INFO Starting Controller {"controller": "nimservice" "controllerGroup" "apps.nvidia.com" "controllerKind": "NIMService"}
2024-11-07704:24:46Z ERROR controller-runtime.source.EventHandler  if kind is a CRD, it should be installed before calling Start {"kind": "NemoGuardrail.apps.nvidia.com", "error": "no matches for kind "NemoGuardrail" in version "apps.nvidia.com/vlalpha1""}
sigs.k8s.io/controller-runtime/pkg/internal/source.(*Kind[...]).Start.func1.1
/workspace/vendor/sigs.k8s.io/controller-runtime/pkg/internal/source/kind.go:71
k8s.io/apimachinery/pkg/util/wait.loopConditionUntilContext.func1
/workspace/vendor/k8s.io/apimachinery/pkg/util/wait/loop.go:53
k8s.io/apimachinery/pkg/util/wait.loopConditionUntilContext
/workspace/vendor/k8s.io/apimachinery/pkg/util/wait/Loop.go:54
k8s.io/apimachinery/pkg/util/wait.PollUntilContextCancel
/workspace/vendor/k8s.io/apimachinery/pkg/util/wait/poll.go:33
sigs.k8s.io/controller-runtime/pkg/internal/source. (*Kind[...]).Start.func1
/workspace/vendor/sigs.k8s.io/controller-runtime/pkg/internal/source/kind.go:64

This issue was resolved by installing bases/apps.nvidia.com_nemoguardrails.yaml in the config/crd/kustomization.yaml.
With these changes, nim-operator is now running correctly:

kubectl get po -n k8s-nim-operator-system
NAME                                                   READY   STATUS    RESTARTS   AGE
k8s-nim-operator-controller-manager-68d67d4b69-rr2rn   1/1     Running   0          177m

Additionally, I have made the relevant code changes. Would it be possible for me to submit these modifications to the community?
Thank you!

@wqlparallel Thanks for point this out. Yes, please feel free to raise a PR with your suggested changes. With the Helm chart these are setup right, but directly install from the generated manifests will fail. You need to update the RBAC here and generate manifests again.

How to reproduce this issue as we did not see before?


Force the solution deployment to use the upgrade approach

Describe the issue
These changes will force the upgrade action when building and deploying a solution to any environment. This feature will be applied only when deploying to PR, UAT or PRD environments. For DEV environments the import process will remain the same.
Changes included in the PR

Added an action to check if a solution exists in a particular environment. Based on that the solution could be imported using the update or upgrade approach.
Updated the build-deploy-solution workflow to force the upgrade.

Screenshots

We intentionally do not default to upgrade because updates are faster and generally speaking, when using source control based ALM, you only need to perform upgrades when you know you want to delete something from a solution in the target environment.


Jcs/import people

Issue #659

Doesn't catch empty/no file upload. The other 2 CSV's return Message = "File not selected". People just errors out.


Spotlight effect in Vue Tour

Hi All
Is there an easy way to highlight a section of the screen, and grey out the rest? Basically adding a spotlight effect?
Thank you!

Hi @Gabvo94,
Yes there is! Here is the documentation for it: https://github.com/pulsardev/vue-tour/wiki/Features#highlight-v12x.
You can also customize the CSS of the backdrop to make it fill the entire screen (see https://github.com/pulsardev/vue-tour/wiki/Features#customization).


feat(go/adbc/driver/snowflake): add '[ADBC]' to snowflake application name

To help Snowflake track adoption and usage of the ADBC driver, we can explicitly add a prefix to any client application name to indicate the ADBC driver is the source of the requests.

My intent was to prefix to the users choice so we can still track it, but I'm fine with just having it not override at all if we think that's better.

IMO if gosnowflake doesn't prefix we shouldn't either (does it?); and in Go and Python we should set defaults if they're not set by the user (so Snowflake can track the Go/Python drivers otherwise)

If only there were separate user-agent and application fields

gosnowflake has an internal application name that is not externally changeable so regardless of the User's application name, snowflake can track it's coming from the Go driver. So they don't need to prefix

Ah...and we can't get access to that? :sweat_smile: It would be nice if we could expose this sort of thing separately

Ah...and we can't get access to that?

Yeap. We can't get access to that unfortunately. They said the preferred method would be to pass it as the application name or prefix the user's choice.

Ah...and we can't get access to that?

Yeap. We can't get access to that unfortunately. They said the preferred method would be to pass it as the application name or prefix the user's choice.

Ah, sorry...if they are OK with prefixing the user's choice then I'm ok with that too.


Example doesn't compile

git clone https://github.com/drifting-in-space/stateroom.git
cd stateroom
cd examples
cd native-echo
cargo check

the cargo check command line output https://app.warp.dev/block/IZrKz6eqSmHFYpjeeJb0TI

Thanks Evan. Looks like maybe an update to Actix broke it, I’ll have a look this week.


Update our action encoding to allow battlecry targets.

Our current pytorch action encoding does not allow our bots to summon cards with battlecries.  We need a way to encode the battlecry target, and to calculate the probability of a card to summon + battlecry target and take its derivative.
I am thinking that we could first calculate a probability distribution using a softmax over all cards to play, then once we chose the card, we could feed that sampled choice back to the network to have it choose the target.

Also known as a pointer network (see the alphastar paper for an example of how its used).


Edited Meet the Team Page

@BAAHUBALI7781 That's mostly repetition of code that you have added.

No description provided.

You have copied a HTML snippet and edited that for every user, instead create JS objects and use the various names, links as object attributes. Display it using v-for.
This is what you too pointed out @RitikaShrestha-me , isn't it?

I just wanted to say that he had some code that was just copy pasted and not required. The our_team:hover part had same code as normal our_team part. Which was not adding value but just extra code.

You have copied a HTML snippet and edited that for every user, instead create JS objects and use the various names, links as object attributes. Display it using v-for.
This is what you too pointed out @RitikaShrestha-me , isn't it?

Yeah! @RitikaShrestha-me you are right, I just wanted to add the border radius style while hovering and I did it by copying the above code which could have been avoided. Thank you for pointing that out.

That's the only thing I was telling :)

Yeah! @RitikaShrestha-me you are right, I just wanted to add the border radius style while hovering and I did it by copying the above code which could have been avoided. Thank you for pointing that out.


Refresh subscription instead of group

Fixes #617

Could we make the refresh implementation different on the node itself rather than having this weird edge case in the command defintion?
Like, if you call GroupingTreeItem's refresh, it's implementation will handle passing up the subscription/parent node? Or do we not have that capability anymore?

We haven't done it that way for v2, however that's probably a good approach.

Is it possible to do that now or should I just go ahead and approve this for merge, and we can leave an issue for it later?

Is it possible to do that now or should I just go ahead and approve this for merge, and we can leave an issue for it later?

I will change it sometime today (hopefully). 😄

Since this is sorta a special case, I think for now this implementation if fine. None of the solutions I have feel right since it's just for this one edge case.

Alright, definitely something to keep in mind when we convert a hefty boy like Functions.


There was a decoding error with chunk (base64)

While using bubbleprof on a Typescript project I get the error on the title with the request to open an issue here.
I attached the chunk. Let me know if you also need the generated files
clinic-bubbleprof-base64-chunk.txt

Can you create a reproductible example?

Hi. Sorry for the delay. Creating a reproducible example is hard, since my application depends on a set of docker containers run from a docker-compose.yml and is written in typescript.

I ran into this today, it said to report the following chunk:
There was a decoding error with chunk (base64):
 ... see attached file
Please open an issue on https://github.com/clinicjs/node-clinic-bubbleprof with the above output.

base-64-chunk.txt

Hi @stearm yes I know. My project was to large to slim it down at that moment and time was an issue. Sorry for the noise. I'll do better next time.

Hi @stearm yes I know. My project was to large to slim it down at that moment and time was an issue. Sorry for the noise. I'll do better next time.

No worries, we're here to help each other 😄 !

i am facing same error. Error is encoded and unreadable

i am facing same error. Error is encoded and unreadable

Please open a new issue with a reproducible code.


chore: de-mathlib Data/List/Pairwise.lean

All included statements are the same as mathlib4, but a good number of lemmas are dropped. See diff.
Depends on #99 #95.

Looks good to me. See https://github.com/leanprover-community/mathlib4/pull/6743 for the mathlib changes.

I think based on the Mathlib PR being painless, this should be safe to merge.


Is the Medium article available?

This link https://medium.com/@lukejonesme/optical-adjustment-b55492a1165c is returning a 410 error code; it looks like this has been deleted. Besides looking in an internet archive, do you know if this article is currently hosted somewhere?

Found this! https://marvelapp.com/blog/optical-adjustment-logic-vs-designers


Fatal error: Uncaught exception 'Less_Exception_Chunk' with message 'ParseError: missing closing */

After updating wp-less to 1.8.0 I have this error when I activate the wp plugin.
Fatal error: Uncaught exception 'Less_Exception_Chunk' with message 'ParseError: missing closing `*/` in layout.less on line 371, column 3 369| } 370| 371| } /* /media query  372| ' in /home/www/website/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Parser.php:535 Stack trace: #0 /home/www/website/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Parser.php(343): Less_Parser->GetRules('/home/www/79ide...') #1 /home/www/website/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Tree/Import.php(277): Less_Parser->parseFile('/home/www/79ide...', '', true) #2 /home/www/website/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Tree/Import.php(193): Less_Tree_Import->ParseImport('/home/www/79ide...', '', Object(Less_Environment)) #3 /home/www/website/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Tree/Ruleset.php(248): Less_Tree_Import->compile(Object(Less_Environment)) #4 /home/www/website/wp-content/plugins/wp-less/vendor/oyejorge/less.p in /home/www/website/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Parser.php on line 535

Any ideas what can I do?

it was caused by the WP theme. The author of the theme patched their code and the issue was fixed.


Raster blending renders differently to PDF and SVG than to PNG

This is perhaps a known issue, and related to the mapnik output plugins rather than node-mapnik, but anyway...
When I blend two raster layers (either using opacity, or comp-op:grain-merge), I get expected results when producing png's, but the blending does not work for pdf and svg exports; one layer completely covers the other, with full alpha.
Is this expected behaviour?

Compositing at the "style" level (e.g. <Style comp-op="..." opacity=".."/>) is only implemented for the AGG rendering backend. So, it is expected that these options do nothing for PDF output (which uses the "Cairo" backend).
Compositing at the feature level (e.g. <PolygonSymbolizer comp-op="..." />) is supported for the Cairo backend. Although it often triggers rasterization of vector features, which may not be desirable.

Ah, got it! Thanks!


"Date" menu don't close with multiple datetimepicker

When multiple datetimepicker on a form, if I open one and click in another one, the first doesn't close. To close them I need to click elsewhere on the document.
see http://plnkr.co/edit/rvb6ByQuzHHz1y3Uatnq

Each datepicker is independent of the other ones, so in this case, you will need to programmatically close the datepicker using date-opened attribute. See https://github.com/zhaber/angular-js-bootstrap-datetimepicker and https://github.com/angular-ui/bootstrap/issues/3432


Animating markers on mapview

Hi,
I'm using the google Maps marker animation logic given here.
https://gist.github.com/broady/6314689
My marker gets animated,but after each marker.setPosition(newPosition); I need to call mapView.invalidate();which refreshes the entire map resulting in very sluggish animation.
Is there any workaround?

i have the same problem too.
@adolfdsilva  could you find a solution ?

Can you invalidate just the market?
On Jul 1, 2016 9:24 AM, "Reza"<EMAIL_ADDRESS>wrote:

i have the same problem too.
@adolfdsilva https://github.com/adolfdsilva could you find a solution ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/osmdroid/osmdroid/issues/139#issuecomment-229945707,
or mute the thread
https://github.com/notifications/unsubscribe/AB4kGYDzBNTtp38lwvA2HVfewKAkoIcRks5qRRUggaJpZM4FWlJW
.

@spyhunter99 does marker have this capability ? i couldn't find any invalidate method on Marker and Overlay

apparently not. I bet @MKergall will have an idea

Old pending issue: see OSMBonusPack issue #88.
You could try to use MapView.invalidateMapCoordinates(Rect dirty).
The difficulty is to build this dirty rect. Most of the code can be found in Marker.draw method:
mPositionPixels is the marker position, and rect is the icon bounds.
So dirty = rect.offset(mPositionPixels).
@RezaOruji if you succeed, providing this feature as a Marker.invalidate method would be really relevant.

@MKergall  Thank you . i will inform you  if it works.

@RezaOruji Did you find a solution?
@MKergall
From my test, no matter what I  invalidate is the whole mapview or a certain small area using invalidateMapCoordinates, ALL of my overlays onDrawItem are called, am I missing some other settings here?
If I use wrong rect for the invalidateMapCoordinate function, the overlay won't be refreshed but onDrawItem is still being called.
What I'm trying to do is refresh the user's location overlay's (customised one) rotation according to device orientation changes, the changes are very frequent and I also have bunch of other overlays on the map so the cpu becomes really busy if I invalidate the whole map all the time.
 All overlays draw methods have to be called (the osmdroid framework cannot guess which object has to be really drawn), but low level drawing calls are performed with a clipping set on the reduced area.
You have to set your update frequency as a compromise between smooth display and cpu usage. Possible hint: redraw only if the rotation change is "significant" (above a certain level).

@MKergall Yeah, thanks for the hint, I already used a compromised frequency.
Just one more question, where does the low level drawing calls that apply clipping area happen? In Android's View class or osmdroid framework?

@always-beta  i wrote a method but i think it also invalidates the whole view :
    public void invalidate(MapView mapView) {
        if (mIcon == null)
            return;

        final Projection pj = mapView.getProjection();

        pj.toPixels(mPosition, mPositionPixels);
        int width = mIcon.getIntrinsicWidth();
        int height = mIcon.getIntrinsicHeight();
        Rect rect = new Rect(0, 0, width, height);
        mapView.invalidateMapCoordinates(rect);
    }

@always-beta Low-level drawing calls are the calls to Android drawing methods, inside the draw method of each overlay class.
Examples:

Marker.draw is calling Overlay.drawAt, calling Drawable.draw(canvas) => low-level, Android.
Polyline.draw is calling Canvas.drawPath => low-level, Android.

@MKergall got it.
@RezaOruji Yeah I tried that and it eventually triggers overlaymanager's onDraw which will iterate all overlays and redraw them.
I guess it's hard to do decent animations for overlays in my case since I have lots of overlays to show, I probably end up using another way to show what I'm trying to indicate rather than using overlay.

operation timeout. please reopen or comment back if you have further questions


Parse failed rows as part of the package

Failed dbt test results return an error message that includes the number of failed rows.
Today we load the message as is in the package, and parse the number in the CLI using Python.
If we move the parsing to the package, users could run their analysis on these data.

Hello!
Would it be also possible to return the number of total failed rows. For now, the error messages includes the number of singular different failed rows but not the total occurrences of rows that are failed. The goal is to track over time the percentage of failures through our tests.
Thanks!

@oravi
I checked the result object as you said, and saw the 'failures' field:
message='Got 3100 results, configured to fail if != 0', failures=3100
message='Got 1 result, configured to fail if != 0', failures=1
Do you think it's better to use it?

Hi @aqwvinh, we think that this might be a quicker win than the regex.
What do you say?

Hello! I will try to find some time to work on the PR this week but as a quick answer to your last message, it can be quicker indeed ! But what about if the test passes? Does it return failures=0?

Good question, it returns the number of failures.
If the test has no special config and passes it returns 0.
If the test is configured to fail on failures>100 and there are 5 failures, it will return 5 for a passed test.
If there is an error in running the test - it returns None.
(I checked on dbt 1.0.0 and above)

Released on 0.4.12 of the dbt pakage!
@aqwvinh


Simplifications & general improvements

Changes

Operation and FutureOperation has been removed
Considerable parts of the README was moved to the crate's doc
source code was reformatted with cargo fmt
breaking changes documented

@coolreader18 may I ask you to review the PR?

Thank you for the review!

Thank you for the review!


Import section missing for cloudflare_api_token

Confirmation

[X] My issue isn't already found on the issue tracker.
[X] I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version
Terraform v1.5.1
on linux_arm64

provider registry.terraform.io/cloudflare/cloudflare v3.35.0

Affected resource(s)

cloudflare_api_token

Terraform configuration files
resource "cloudflare_api_token" "terraform" {
  name = "Terraform - Edit all resources"

  policy {
    permission_groups = [
      data.cloudflare_api_token_permission_groups.all.account["Access: Apps and Policies Write"]
    ]
    resources = {
      "com.cloudflare.api.account.${var.cloudflare_account_id}" = "*"
    }
    effect = "allow"
  }

  not_before = "2023-02-21T00:00:00Z"
  expires_on = "2023-05-22T00:00:00Z"

  condition {
    request_ip {
      in = [
        "<IP_ADDRESS>"
      ]
    }
  }
}

Link to debug output

Panic output
No response
Expected output
There should be an import section on the documentation page for cloudflare_api_token. The following command should be documented:
terraform import cloudflare_api_token.terraform <token_id>
Actual output
There is no import section on the documentation page for cloudflare_api_token.
Steps to reproduce

Go to the documentation page for cloudflare_api_token (https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/api_token).
Scroll all the way to the bottom.
There is no import section.

Additional factoids
No response
References
No response

API tokens should not be importable as the value is only shown once and never available after that point.
it is a bug that the provider allows this and should be removed.


[fix] On returning generic error, store actual error in extended error info

Addresses https://github.com/chipsalliance/caliptra-sw/issues/335

We should add assertions for this extended error info to the existing test cases.

Discussed of offline; crypto function failures are not tested by integration tests.


Change Source to pointer in Channel

What this PR does / why we need it:
ChannelSource is now pointer, which allows to have it not set. Which gives the API more flexibility.
Signed-off-by: Petr Kotas<EMAIL_ADDRESS>Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

This change is

@rmohr I have created separate PR to change the underlying KubeVirt API so we do not have multiple changes in single PR. This PR is related to the #1543

@petrkotas could you please merge this into #1543


running time issue in the discussion

You mentioned in the discussion of the paper:

The weakness of our current solution is that the FLOPS numbers are not directly transferable to the
running time due to CUDA kernel and hardware support.

Is it mainly due to the corrf() function which does for loops?
You also state in the readme that the corr() function can speed up inference, but how much precisely?
Finally, from other repos of optical flow I can find several implementations which compute the correlation without python for loops and support backward, e.g. PWCNet, IRR; how are their implementation different from yours?

Hi, corr() reduces the running time by ~20ms. Please also refer to the updated readme for some analysis on why the current version is slow.
When doing correlation, we keep the channel-wise feature products as-is (without summing them up), and use them (we refer to as multi-channel cost volumes in Sec.3.3) for later 4D filtering.


Tax reports do not work

The tax reports do not seem to works. Regardless if I work with online or offline queries I get the spinning wheel of dead and a error message pop-up later (see attached image). I can also choose different time frame I want the report from always with the same result.

Hi @one4many for tax report query needs to be set as offline.
We would work in creating something more intuitive

Hi @ezewer, thank you for letting me know. But as I stated before, the same error also turn's up in 'offline-mode'.

Hi @one4many, can I ask you to try to fetch this kind of report (it will make some fresh error logs) and then open a new issue via the menu bar as it's shown on the screenshot? It would attach additional debug info and help to understand where the issue

@ZIMkaRU here we got ... new issue is open

thanks


Ability to configure to also update PRs in draft status

Currently it appears auto-update will only update PRs that are not in Draft state. It would be nice to be able to configure this.
Like my other feature request, let me know if you are open to accepting PRs. Someone on my team or I would be happy to submit one!

Hi Bian,
As explained in the README, I mostly see this action as a way to easily merge PRs without having to manually go back to their dedicated page and click on the Update Branch button to get a fresh green CI. Draft PRs don’t really fit here since they’re used as a way to denote that the work is not ready to be merged yet.
Do you have something else in mind?

@tibdex I guess I see the value here as more than just the ability to easily auto merge with Github's new auto feature. Being able to keep feature branches up to date while PRs come into them until they come out of draft status would still be helpful. This needs to happen anyway, and if this happens whenever the target branch is updated, IMO that is a better time for devs to see those updates and potential conflicts than at the end of their work.
I understand that our process might be drifting out of the scope of your initial intentions. I think this would still be valuable to be a configuration option and I agree with updating draft PRs would not be the default and something that you would want to opt-in on.

https://github.com/tibdex/auto-update/commit/f3214295c70ec1baa64262fdd3cdfd4d534cac9a simplifies this action: it removes the need for a label by only looking at pull requests with auto-merge enabled. Draft pull requests cannot have auto-merge enabled so I'm closing this.


[SPARK-35259][SHUFFLE][3.1] Update ExternalBlockHandler Timer variables to expose correct units

ExternalBlockHandler exposes 3 metrics which are Dropwizard Timer metrics, and are named with a millis suffix:
    private final Timer openBlockRequestLatencyMillis = new Timer();
    private final Timer registerExecutorRequestLatencyMillis = new Timer();
    private final Timer finalizeShuffleMergeLatencyMillis = new Timer();

However these Dropwizard Timers by default use nanoseconds (documentation).
This PR adds a new Timer subclass, TimerWithCustomTimeUnit, which accepts a TimeUnit at creation time and exposes timing information using this time unit when values are read. Internally, values are still stored with nanosecond-level precision. The Timer metrics within ExternalBlockHandler are updated to use the new class with milliseconds as the unit.
This introduces a user-facing change as the values of the metrics themselves have changed, to expose milliseconds instead of nanoseconds. Note that this does not affect metrics such as openBlockRequestLatencyMillis_count or openBlockRequestLatencyMillis_rate1, only the Snapshot-related metrics (max, median, percentiles, etc.). For the YARN case, these metrics are not exposed prior to 3.2, so there is no change. It was possible for the nanosecond values to be consumed by some other metrics reporter reading the Dropwizard metrics directly, but I'm not aware of any such usages, so this PR is primarily code cleanup and to make branch 3.1 match with 3.2/master.
Note that this differs from the master/3.2 version (#33116) primarily because there are no changes needed in YarnShuffleServiceMetrics.
Unit tests have been updated.

fyi @Ngone51

Test build #141645 has started for PR 33523 at commit ececc53.

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

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

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

Test build #141645 has finished for PR 33523 at commit ececc53.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class TimerWithCustomTimeUnit extends Timer

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


Show sidebar outline for tests written with Jest

Hello, first of all, great job with the extension!
Even without the functionality of running and debugging tests I think its awesome to just have an outline of the tests suite in the sidebar, helps a lot with navigation. I am using Jest at the moment and would like to have the same awesomeness in that project (Jest also uses the "describe" and "it" statements).
Is there any configuration I can do to not run the tests but to only show the outline in the sidebar?
If not, I am thinking of making a fork and stripping this extension down to just showing the test suite outline and be able to navigate to individual tests. I think some other people might find that useful as well. Do you think this is doable without to much effort? Any pointers of were I should start looking?

first thanks, currently you cant navigate using jest.
it's on my roadmap to support jest.
if you want we can work together on that feature :)
Maty Z
On Thu, Mar 8, 2018 at 1:55 PM, Simon Johansson<EMAIL_ADDRESS>wrote:

Hello, first of all, great job with the extension!
Even without the functionality of running and debugging tests I think its
awesome to just have an outline of the tests suite in the sidebar, helps a
lot with navigation. I am using Jest at the moment and would like to have
the same awesomeness in that project (Jest also uses the "describe" and
"it" statements).
Is there any configuration I can do to not run the tests but to only show
the outline in the sidebar?
If not, I am thinking of making a fork and stripping this extension down
to just showing the test suite outline and be able to navigate to
individual tests. I think some other people might find that useful as well.
Do you think this is doable without to much effort? Any pointers of were I
should start looking?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/maty21/mocha-sidebar/issues/77, or mute the thread
https://github.com/notifications/unsubscribe-auth/AE_nuZDA4Gsa2qqsXs7HQe30qB9KaBwKks5tcRxBgaJpZM4Siket
.

Great to hear that it is in the roadmap!
Adding Jest support sounds like quite a big undertaking, I was hoping for a quick-and-dirty solution 😁

I ended up writing a dedicated mapper for the vs code extension CodeMap. Seems to work so far.
Gist can be found here: https://gist.github.com/simon-johansson/3be2f96affd6e152d371d18fb96ed362

Seems to be nice extension thanks for your supporting


Ensure server has queue client

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 5 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 40.067%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

server/server.go
0
5
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
359

Relevant Lines:
896

💛  - Coveralls


Distinct True filters on filtered layers

This PR addresses an issue related to when we use layers that are filtered in the workspace to use filter current.
If you then apply a distinct true filter on an infoj entry you will see any values from the database table (regardless of if they should have been filtered out or not).
This PR adds a layerFilter flag to the infoj filter entries configured as so -
  "filter": {                         "type": "in",                         "distinct": true,                         "layerFilter": true                     }
When layerFilter is provided, the current layer filter will be passed into the SQL query to return distinct values from the database.
However, I have not yet got this working correctly - so please could i get some help on this one?

SQL cannot be sent from client to the host. Only parameters to be substituted in a stored template.


Request for WordPress-specific folder icon

WordPress uses 2 dirs for plugins:

plugins
mu-plugins

First one is recognized (as expected), the second one has that mu- prefix that doesn't work. I think it would make sense to use some simple regex to allow different prefixes/suffixes to be prepended/appended to the word 'plugins'. From what I've seen in other apps over the years these combinations come to my mind:

plugins
mu-plugins
network-plugins
plugins-disabled
disabled-plugins
inactive-plugins
plus, different separator symbol - hyphen, underscore and dot.

For mu-plugins dir only, this:
<regex name="plugin" pattern="^(mu-)?plugins?$" icon="/icons/folders/plugin.svg"/>
instead of this:
<regex name="plugin" pattern="^plugins?$" icon="/icons/folders/plugin.svg"/>
should do the job.

@mallowigi please see #19


poc: search bar

This pr is a poc for a search bar based on the fzf lib (Details https://github.com/redhatcloudx/cloud-image-directory-frontend/issues/75). In addition to the listings of aws, gcp and azure images, another tab leading to a search is added.
There you will find an unoptimized search, which renders all hits as links to the detail api point in the page.
Example:

This draft contains todos (with links to tutorials) further optimization.

During the implementation, I noticed that there is no modal for a detailed view of the images. This means that it is not possible to share specific images as a link. Does it make sense to add a route for it?
Another point is the search. Maybe it makes more sense to put the bar immediately in the "headline" and limit the suggestions (hits with the highest score) to 5-10 items. Similar to the google search.

wdyt @FKolwa @major @schogges @miyunari  ?

@FKolwa @schogges do not wonder, I updated the branch and did some clean-up. :nail_care:
One thing i noticed is, direct links do still not work.

Weird https://localhost:9000/browser/google/global/rhel_9_arm64 does work, while https://localhost:9000/browser/google/global/rhel_8.2_sap_x86_64 does not. :raccoon:

One thing i noticed is, direct links do still not work. !
Yeah thats an issue for the WSGI server (the webpack server) running on your local machine. I think this is related to the missing 404 redirect in the development environment. The one page application is redirecting subdirectory calls to the router (or simpler, calls index.html) and renders the subpage accordingly. This works fine in our staging environment or in production but the webpack server does not (yet) know how to handle these calls. We should open an issue for that.

Weird https://localhost:9000/browser/google/global/rhel_9_arm64 does work, while https://localhost:9000/browser/google/global/rhel_8.2_sap_x86_64 does not. 🦝

Yeah I ran into the exact same thing. I don't know why some of them are properly redirect and others won't. In prod the CDN handles the proper redirect just fine, the dev server doesn't..

hm... seems there is still an issue with fetch in the unittests. if i understand it correctly, the problem is that fetch is not available. Which confuses me a bit. It should be available since v18.x that is used in the CI.
Anyway, I tried to install node-fetch. But that seems to expect types. Adding the type Map<string, number> as data response type in app/components/ImageDataTable.tsx fixed this, but when i tried to run webpack-dev afterwards, it seemed like hundreds of packages were missing.
For now, I have reverted the changes, what would you suggest to fix this? @FKolwa @schogges ? :racehorse:

https://stackoverflow.com/questions/48433783/referenceerror-fetch-is-not-defined

Anyway, I tried to install node-fetch. But that seems to expect types. Adding the type Map<string, number> as data response type in app/components/ImageDataTable.tsx fixed this, but when i tried to run webpack-dev afterwards, it seemed like hundreds of packages were missing.

Hmm. Okay so one problem is that fetch is a browser specific tool. As our jest tests aren't running in an actual browser fetch is simply not available. We didn't have this issue in our tests so far because they weren't testing anything where fetch was executed. Jest can run in different test environments, one of them is node. The node-fetch package was specifically made for enabling fetch in node. Our current test environment uses jsdom instead of node which at this moment doesn't support fetch (https://github.com/facebook/jest/issues/13834) .
So I'd say there are at least two ways of doing this: Further try to find a way around fetch in jsdom or try to rewrite our tests to use node instead (and require node-fetch in test-setup.js).
What do you think? @frzifus @schogges
I see is that our jest test cases use the jsdom environment (jest.config.js). node-fetch as a package will only be

Seems like even though they announced to remove the --experimental-fetch flag with release of v18, this was not the case.
I guess the easiest way to fix this now would be to use platform agnostic cross-fetch.

Seems like even though they announced to remove the --experimental-fetch flag with release of v18, this was not the case. I guess the easiest way to fix this now would be to use platform agnostic cross-fetch. Another option for the future might be to use something like react-query as it ships some more features like caching, state values (isLoading, error, ...) and more 🙂

I like it! I'd say we go with cross-fetch for now to keep within the scope of the issue and create a new issue to transition to react-query. That'll be a great replacement for the fetch calls we use to create the tables in our browser views.

Ok, i will try to change it once iam home :)

oh i guess it would have been better to squash all this back and forth. :face_with_spiral_eyes: :sweat_smile:


runtime(java): Fold multi-line comments with the syntax kind of &fdm

Also:

Restore the capability to mark as an error braces nested
in parens with g:javaInParen.
Try not to fold top-level-type bodies.  (Defining multiple
package-private top level types in a single source file is
not recommended as it can impose order among compilation
units; so it is assumed that only one such top level type
is usually defined.)
Compose ‘method header’ highlighting and block braces
folding.
Do not highlight block braces whenever ‘method header’
highlighting is requested.

This bundling of ‘method headers’ and block braces for
highlighting can be traced back to Vim v5.0; however, no
comment or documentation entry conveys any justification.
For example, it is hard to discover the connection between
block braces for while, if, etc., statements and method
body block braces.  The former behaviour can be attained in,
e.g. ~/.vim/after/syntax/java.vim:
if exists("g:java_highlight_functions")
    syn clear javaBlock javaInParen
    syn match javaBlockOther "[{}]"
    syn region javaBlock transparent matchgroup=javaBlockStart
	\ start="\%(^\|^\S[^:]\+\)\@120<!{" end="}" fold
    hi def link javaBlockStart javaFuncDef
    hi def link javaBlockOther javaBlockStart

    if exists("g:java_mark_braces_in_parens_as_errors")
	syn match javaInParen contained "[{}]"
    endif
endif

Note: Read ‘a method header omitting a throws clause’ for
every ‘method header’ appellation used above.

As I have already mentioned it elsewhere, folded lines are
always treated as opened for a syntax test when calculating
the line offsets and determining what next batch of lines to
dump to a file; hence, the generated dump files for them
exceed the required number because more lines are repeated.

thanks!


fix: Fixed WAF Reliability validation in avm/res/network/bastion-host

Description
Fixes failing WAF Reliability validation

Pipeline Reference

Pipeline

Type of Change

[ ] Update to CI Environment or utlities (Non-module effecting changes)
[x] Azure Verified Module updates:

[x] Bugfix containing backwards compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[x] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
[ ] Breaking changes and I have bumped the MAJOR version in version.json.
[ ] Update to documentation

Checklist

[x] I'm sure there are no other open Pull Requests for the same update/change
[x] I have run Set-AVMModule locally to generate the supporting module files.
[x] My corresponding pipelines / checks run clean and green without any errors or warnings

@AlexanderSehr: This is the WAF Reliability test, which I mentioned yesterday, where I think, that the PS Rule test may not work as expected...
The test is complaining about following failed rules:

AZR-000158: Azure.PublicIP.StandardSKU. Public IP addresses should be deployed with Standard SKU for production workloads.
AZR-000395: Azure.PublicIP.MigrateStandard. Use the Standard SKU for Public IP addresses as the Basic SKU will be retired.

The Bastion module is cross-referencing the module br/public:avm/res/network/public-ip-address:0.3.2 for Public IP creation, which has a default skuName set to 'Standard'. But the test is failing anyway: https://github.com/krbar/bicep-registry-modules/actions/runs/8381280524
I even explicitly added the skuName: 'Standard', which should not be necessary, but the test failed again: https://github.com/krbar/bicep-registry-modules/actions/runs/8382290824
When I skip the static validation and perform the deployment validation, the SKU of the deployed Public IP in each test is 'Standard' for each test case.
the Basic SKU is not used

Do you have any ideas?

I've created a PSRule issue to get some help on this: https://github.com/Azure/PSRule.Rules.Azure/issues/2795

I've created a PSRule issue to get some help on this: Azure/PSRule.Rules.Azure#2795

Solved: https://github.com/Azure/PSRule.Rules.Azure/pull/2798


feat: edition 2021 and update crypto deps

bumps msrv to 1.56

depends on https://github.com/RustCrypto/block-modes/pull/17

Are there any news on this PR? Is there anything I can do to get this PR unstuck?


Fix for Issue #32 - Changed xIPAddress so that DHCP status is not checked for IPv6

This is a fix for #32.
The change prevents the test for DHCP status to be performed on IPv6 addresses. If this test is allowed then Test-TargetResource will return $false even if the IPv6 address is correctly assigned and set to static. This causes the resource to continuously apply the IPv6 address every time it runs - which can cause intermittent network connectivity issues.
This change actually only wraps the DHCP test code in a check to see if it is IPv4.

Could we add a warning or something to indicate to the operator that DHCP for IPv6 isn't supported?

Like
else {
    Write-Warning 'DHCP  for IPv6 is not supported in this module'
}

I reckon you're right - we should add some sort of message. But need to figure out the wording. Because technically DHCP is implemented in IPv6 and this resource will still use it when a static address is not assigned but the check to see if it is enabled is meaningless and reports that DHCP is always enabled (even if a static is assigned). This is because DHCPv6 state isn't reported in the same way as DHCPv4 - they sort of have a slightly different definition and purpose in IPv4 vs IPv6.
I hope that kind of makes sense :smile: But I'll put a warning in covering this - definitely worth doing.

When I was thinking about the appropriate warning message to show, I think there might be a better way of doing this.
I think the test for DHCP status needs to be removed completely. It shouldn't be in this resource at all.  It is as you said in Issue #17 - there should be a really simple xDHCPClient resource which simply sets DHCP property to enable/disable on the NetIPInterface (limited by AddressFamily).
The reason why I think this test is not useful here is this:

When a static IP Address is assigned to an IPv4 interface the DHCP Status is automatically disabled - so simply assigning an IP address sets this and there is no point in testing for it because if the assigned IP Address is different to desired IP address then Set-TargetResource will fire anyway, which will disable DHCP.

When a static IP Address is assigned to an IPv6 interface the DHCP Status is not changed.

Note: As it stands currently the xIPAddress resource has no way to enable DHCP anyway and it is never disabled by any other method except setting the IPv4 address.
So, I think I'd be much better removing this test completely and implementing an xDHCPClient resource that can be used to enable DHCP (or disable it).
Sorry about all the too-ing and fro-ing on this, but best get it right.

Makes sense to me. Would you mind opening an issue saying we need an xDHCPServer resource specifically? I know #17 talks about it but it's a bit obscure that we actually decided to move forward on it.

Absolutely! Consider it done.

oh bother, could you be so kind as to update the readme.md? I remembered that as soon as I clicked merge.

Done! Sorry I should have noticed that myself. Doh!


Updated nexus standards, shacl and prov-o contexts

The shacl and standard contexts will be obtained from nexus-common once this pull request is merged


Recurring contributions are missing information about gift cards

Describe the bug
Transactions created when running subscriptions (monthly or yearly) doesn't fill the UsingVirtualCardFromCollectiveId. This has two consequences:

The info is missing from the transactions section

We're not acknowledging the amount in "Total donated" for the gift card emitter

To Reproduce
Steps to reproduce the behavior:

Create an organization
Create gift cards from /org_slug/edit/gift-cards-create
Claim the gift cards
Go to a collective contribution flow (ie. /babel/donate) and make a monthly contribution
Go to your profile. You should notice that this first contribution does include Using a gift card from ...
Using a database UI (you can try DBeaver, PgAdmin or Postico) edit your subscription's nextChargeDate to something in the past.
Run npm run script cron/daily/00-charge-subscriptions.js
Go back to the profile and see transaction with missing gift card info

Expected behavior

New transaction created from subscriptions should include UsingVirtualCardFromCollectiveId
All existing transactions should be updated with this field in a migration

The bug is now fixed in prod. Transactions were properly updated, see https://opencollective.com/betree/transactions.


Unable to add app or driver to manifest

Using the command: hpm manifest-add-app --location=https://raw.githubusercontent.com/tonesto7/echo-speaks/master/smartapps/tonesto7/echo-speaks.src/echo-speaks.groovy --required=true --oauth=true
An error occurred: The app Groovy file https://github.com/tonesto7/echo-speaks/master/smartapps/tonesto7/echo-speaks.src/echo-speaks.groovy either was not found or is not valid.

I tried this on both windows and mac

@tonesto7 thanks, I figured it out. I just released 1.3.0 which should fix it.