[Bug]: xpath prefix is not evaluated relative to the elementHandle

Bug expectation
The documentation states in several places that:

The method evaluates the XPath expression relative to the elementHandle. If xpath starts with // instead of .//, the dot will be appended automatically.

However, when I ran elementHandle.$$("xpath///div") I received all divs on the page.
Similarly, elementHandle.$("xpath///div") gave me the first div on the page.
Bug behavior

[ ] Flaky
[ ] PDF

Minimal, reproducible example
import puppeteer from "puppeteer";

(async () => {
	const browser = await puppeteer.launch({
		headless: false,
		devtools: true,
	});
	const page = await browser.newPage();
	await page.goto("https://example.com");

	function logEl(el) {
		console.log(el);
		page.evaluate(el => {
			console.log(el);
		}, el);
	}

	const firstP = await page.$("p");
	logEl(firstP);

	const a1 = await firstP.$("a");
	logEl(a1);

	const a2 = await firstP.$("xpath///a");
	logEl(a2);
	if (a2) {
		throw new Error("Expected a to not be found")
	}
})()

// After running, check the console, a1 is null as expected, a2 is not

Error string
Expected a to not be found
Puppeteer configuration
No response
Puppeteer version
19.7.2
Node version
18.5.0
Package manager
npm
Package manager version
8.12.1
Operating system
macOS

Note that adding the dot manually is a good workaround:
elementHandle.$("xpath/.//a");

So simply updating the documentation might also be a good fix.

Thanks for the issue. The documentation you pointed at was for $x not $$, however your assumption that the assumptions that apply to $x should transfer sounds reasonable.
We won't be changing behavior since the expected behavior of // is correct. You can just not use // and your example will work!

thank  u for pointig that xpath for child element should have   . before and be like .//


Use production config in production environment

As I know, dev-server won't be used in production mode.

@ragingwind Yeah, dev-server shouldn't be used used in production mode but having dev and start scripts pointing to the same location is a bit misleading.
Maybe this PR can be updated to create a production-ready server for users. WDYT?

npm start was not mentioned in doc which should be updated either package.json though. @ooade Good point but IMO, prod-ready server is not in the budget of this pwa template. It would be perfect to practical examples or projects.


Fix skipFirstLine functionality

This fixes https://github.com/svenkuegler/php-csv-validator/issues/1

Many thanks for the fix.


Dropping connection without noticing?

Weird thing is happening:
I manually connected to a peer:
curl -X POST -H "Content-Type: application/json" -d '{"pubkey": "031fe264e70b544b4469027ca557ce97bb3f1d0f3ed9e2f4c6565c2e942dad6a79", "address": "<IP_ADDRESS>:9735"}' http://localhost:8000/api/admin/connect -v

checked that the peer is connected with.
curl -X GET http://localhost:8000/api/admin/peers  | jq .

And after 1 minute or so I called it again and the connected peer is gone.
Nothing in the logs indicates that the connection was lost.

Closing this ticket, as it might be fixed with our deadlock fix. Please reopen if its happening again.


FOAM models for browser, web interface and browser APIs

FOAM models for browser, web interface and browsers added.
Essential methods for webAPIs are added.
Change webpack-helper.js to hardcoded require(), since require.context does not give any dependency options.

That's true, but it's still a potential robustness issue. For example, I
think this logic will results in myBrowserObject.clone() producing a
browser object with a different id, which is unexpected.
On Thu, Mar 9, 2017 at 10:41 AM, Tao Jing<EMAIL_ADDRESS>wrote:

@jingt06 commented on this pull request.
In lib/web_apis/browser.es6.js
https://github.com/GoogleChrome/confluence/pull/13#discussion_r105193658
:

},

{

 name: 'OSVersion',

 required: true,

},
{

 name: 'id',

},
],
methods: [
{

 name: 'init',

 document: `After the browser object is created, hashCode function is

   used to assign this browser a unique browser id`,

 code: function() {

   this.id = foam.util.hashCode(this);

The hashCode function should only be called once in initialization. After
that, the browserId can be accessed via browser.id.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/confluence/pull/13#discussion_r105193658,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABsWSKVLl5h_A63iZ68EmL3wm9Wb55tJks5rkB2igaJpZM4MXGvR
.

We should avoid using hyphens. We could do org.chromium.apis or
org.chromium.apis.web.
On Fri, Mar 10, 2017 at 6:36 AM, Philip Jägenstedt<EMAIL_ADDRESS>
wrote:

@foolip commented on this pull request.
In lib/web_apis/browser.es6.js
https://github.com/GoogleChrome/confluence/pull/13#discussion_r105380511
:

you may not use this file except in compliance with the License.

You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software

distributed under the License is distributed on an 'AS IS' BASIS,

WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

See the License for the specific language governing permissions and

limitations under the License.

*/
+'use strict';

+foam.CLASS({

name: 'Browser',
package: 'com.web.api',

I guess we have to use a reverse domain name? In that case, org.chromium
plus whatever token is going to be the interesting part of the actual URL.
If we're calling the thing web-apis, then org.chromium.web-apis?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/confluence/pull/13#discussion_r105380511,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABsWSEUZ6D8u7l1UrRE-6xc_GIhO4Svzks5rkTXPgaJpZM4MXGvR
.


Is source map working properly?

Hello,
I came to know this great tool for service worker. I've learned many thing by this tool. Thank you. :)
But I get to have question while using it.
For debugging I have used source-map that was built.
First I had a problem because of source map path in sw-toolbox.js
//# sourceMappingURL=./build/sw-toolbox.map.json
But It's not big problem to me. I can be solved by remove build.
//# sourceMappingURL=./sw-toolbox.map.json
But my big problem is "I could not take a break point" although its source tree appears on dev tools.

I've tried to make break point on Router.prototype.matchMethod function (router.js) but the break point is made on fastest.js(53). Some breakpoints are made well. but most of all are not made on proper code.
So I tried another way of making source map by modifying gulpfile.
I referenced this
https://github.com/gulpjs/gulp/blob/master/docs/recipes/browserify-uglify-sourcemap.md
 var bundler = browserify({
    entries: ['./lib/sw-toolbox.js'],
    standalone: 'toolbox',
    debug: true
  });
  var bundle = function() {
    return bundler
      .bundle()
      .pipe(source('sw-toolbox.js'))
      .pipe(buffer())
      .pipe(sourcemaps.init({loadMaps: true}))
      .pipe(uglify())
        // Add transformation tasks to the pipeline here.
      .pipe(sourcemaps.write('./'))
      .pipe(gulp.dest('./build/'));
  };
  return bundle();

It works very well.
What was my problem? How can I use source-map by not modifying gulf file.
Thank you for your help in advance.

Yep, seems like out source map is not working properly. Sorry about that! We'll take a look.

@wibblymat Thank you! 👍


Fix AppVeyor test setup to fail build when tests fail

Ensure that the AppVeyor  build fails if npm [run] test  fails.
Fixes #177.

Closed by #193.


better readability for 'RD_AdvancedSettings_HUD_MapDrawing' option

The setting RD_AdvancedSettings_HUD_MapDrawing can be boiled down into:
RD_AdvancedSettings_HUD_MapDrawing -> "Draw on Minimap" (before: "Map Drawing")
RD_AdvancedSettings_HUD_MapDrawing_BriefingOnly -> "Disabled" (before: "Briefing Map Only")
RD_AdvancedSettings_HUD_MapDrawing_AllowMinimap -> "Enabled" (before: "Allow Minimap Drawing")
Instead of mentioning the briefing map, because it also allows you to draw in the ingame-map (press TAB) and debriefing map too anyway.

This isn't relevant anymore since the new ui hit.


TypeError: 'NoneType' object is not callable

To load model weights, I create an instance of the same model first, and then load the parameters using load_state_dict() method.
model = PatchCore()
train_dataset = StreamingDataset()
test_dataset = StreamingDataset()
train_paths = "D:\\OK"
test_paths = "D:\\NG"
for root, dirs, paths in os.walk(test_paths):
    for path in paths:
        f = Image.open(os.path.join(root, path))
        test_dataset.add_pil_image(f)
# train images
for root, dirs, files in os.walk(train_paths ):
    for file in files:
        train_dataset.add_pil_image(Image.open(os.path.join(root, file)))
# model.to(device)
# model.fit(DataLoader(train_dataset))
PATH = "test.pth"
# torch.save(model.state_dict(), PATH)
print("One image testing ...")
model.load_state_dict(torch.load(PATH))
model.eval()
for test_idx in range(test_dataset.size):
    sample, *_ = test_dataset[test_idx]
    img_lvl_anom_score, pxl_lvl_anom_score = model.predict(sample.unsqueeze(0))

C:\ProgramData\Anaconda3\envs\knn\python.exe D:/ind_knn_ad-master/test.py
One image testing ...
 Please do not use them for anything important until they are released as stable. (Triggered internally at  ..\c10/core/TensorImpl.h:1156.)
  return torch.max_pool2d(input, kernel_size, stride, padding, dilation, ceil_mode)
Traceback (most recent call last):
  File "D:/ind_knn_ad-master/test.py", line 146, in <module>
    img_lvl_anom_score, pxl_lvl_anom_score = model.predict(sample.unsqueeze(0))
  File "D:\ind_knn_ad-master\indad\models.py", line 278, in predict
    resized_maps = [self.resize(self.average(fmap)) for fmap in feature_maps]
  File "D:\ind_knn_ad-master\indad\models.py", line 278, in <listcomp>
    resized_maps = [self.resize(self.average(fmap)) for fmap in feature_maps]
TypeError: 'NoneType' object is not callable

Hey x12901, sorry I missed this issue. Have you checked all of the model's attributes? I'm not sure if my current model structure supports full serialization.


cli control delay

When issue miio --control ip --token token --method get_prop command, it always takes 3-5s to complete, is there any way to make it quickly response? Thanks.

The miio command isn't really intended to be used for controlling devices in that way. It's mainly for managing tokens and figuring out the API of devices.
Pull requests are welcome for better control-functionality with faster connections and use of the actual device API instead of the raw protocol commands.
I'll close this issue, but feel free to open another one if you have any other questions.


spec: need to specify iteration order of struct comprehension

Originally opened by @myitcv in https://github.com/cuelang/cue/issues/474

What version of CUE are you using (cue version)?

$ cue version
cue version +304b02e linux/amd64

Does this issue reproduce with the latest release?
Yes
What did you do?
exec cue eval

-- a.cue --
package x

m: banana: 4
-- b.cue --
package x

m: apple: 3
-- cue.mod/module.cue --
module: "mod.com"
-- x.cue --
package x

m: {
        aardvark: 5
}

l: [ for k, _ in m {k}]

What did you expect to see?
From the spec I'm unclear what to expect. My intuition is that the iteration order of the struct comprehension would be defined as [filename, offset].
What did you see instead?
m: {
    banana:   4
    apple:    3
    aardvark: 5
}
l: ["banana", "apple", "aardvark"]

which matches my intuition.
That said I think clarifying this in the spec is probably necessary?
See also discussion in https://github.com/cue-lang/cue/issues/1348

FYI, https://github.com/cue-lang/cue/discussions/1896#discussion-4346676 contains a use-case for order-preserving iteration.


Delayed jobs can cause system hangs when the jobs queue is full with a many failed jobs

In the following cases
https://github.com/cloudfoundry/cloud_controller_ng/blob/master/app/jobs/services/delete_orphaned_binding.rb#L45
https://github.com/cloudfoundry/cloud_controller_ng/blob/master/app/jobs/services/delete_orphaned_instance.rb#L28
https://github.com/cloudfoundry/cloud_controller_ng/blob/master/app/jobs/services/delete_orphaned_key.rb#L29
the "max_attempts” property of the jobs is 11. We had a scenario where the API worker established a connection to the service broker successfully, but the service broker was hung and didn’t respond. In consequence, the job re-attempted 11 times (since the request continued to fail), resulting in many failed jobs being scheduled on the api workers. With a timeout set to 60s, you very quickly have any failed attempt re-scheduled almost immediately since only 1 job is processed per worker.
Obviously, the main issue was the service broker being hung and unresponsive, but we believe the API worker should be more resilient and handle this situation properly.

@dieucao, could anyone from the CAPI team comment on that  ? I might have ideas on how to solve this, but we'd like to get the CAPIs team point of view on it first.

@smoser-ibm The team has made some changes.  You can see the commits on the tracker story.  The changes will be in the next cf-release.  Okay to close this issue and if you continue to see problems could you open a new issue?

sure, lets do ti like that


Typewriter Scroll Mode

Issue Type: Feature Request
When editing all files, I want to have a "typewriter scroll mode" that keeps the current line that I'm working on in the vertical center of the screen.
Yes, I know there is an extension to do this for markdown and text files, but I would want it for all files that I edit.  For code, this is useful because you can more easily see the code below the line you are working on, without mucking about with having to "overscroll."

There is an extension, named "scrolloff", that may help you. If you activate "scrolloff.alwaysCenter", then when you'll edit a line, this line will be kept at the center of your screen.
You can still scroll with your mouse, but as soon as you hit your keyboard, you automatically scroll to the line you're writing on.

scrolloff also has the following in its readme:

This feature is now built into VSCode with the addition of the editor.cursorSurroundingLines property. See this issue for more details. This extension is now obsolete. This is good news because this extension always had a few issues that could never be solved within the limitations of the VSCode extension API.

If you set high value, like "editor.cursorSurroundingLines": 100 it will always center.
Value should be >= (total lines in your editor screen) / 2

@hediet Reference?

@meydjer isn't your suggestion the workaround for this feature?
Otherwise, what is this workaround using "editor.cursorSurroundingLines": 100 missing from the requested feature?


"fop.xconf" no longer exists in DITA OT 2.0.1 distribution.

I downloaded "DITA-OT2.1.0-M1_standard_bin.zip"
The folder:
DITA-OT2.1.0-M1\plugins\org.dita.pdf2\fop
only contains license, notice and readme files.
		C:\Users\radu_coravu\Desktop\DOT2.0.1\DITA-OT2.1.0-M1\plugins\org.dita.pdf2\fop\conf\fop.xconf (The system cannot find the path specified)
			at java.io.FileInputStream.open(Native Method)
			at java.io.FileInputStream.<init>(Unknown Source)
			at java.io.FileInputStream.<init>(Unknown Source)
			at sun.net.www.protocol.file.FileURLConnection.connect(Unknown Source)
			at sun.net.www.protocol.file.FileURLConnection.getInputStream(Unknown Source)
			at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:1036)
			at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
			at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
			at org.ditang.relaxng.defaults.RelaxDefaultsParserConfiguration.parse(RelaxDefaultsParserConfiguration.java:150)
			at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
			at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
			at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
			at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
			at org.apache.avalon.framework.configuration.DefaultConfigurationBuilder.buildFromFile(DefaultConfigurationBuilder.java:186)
			at org.apache.fop.apps.FopFactoryConfigurator.setUserConfig(FopFactoryConfigurator.java:337)
			at org.apache.fop.apps.FopFactory.setUserConfig(FopFactory.java:703)

I built 2.1-M1 and 2.0.1 off of the same clone (different branches) - but 2.0.1 has a lot of JAR files in that directory along with license / notice / readme. @jelovirt do you think the build process has changed for the 2.1 copy? Don't think I changed any environment settings between builds.

Just investigating. We could actually not stick the FOP dependency JARs into our Git, but rather get they with Ivy.

Yup, it's excluded https://github.com/dita-ot/dita-ot/blob/develop/build.xml#L213 but only partially. Per http://www.dita-ot.org/2.0/readme/distribution_packages.html the standard package should not contain FOP. The build would need to be fixed to skip fop directory completely.

Oh of course, I didn't even realize this was for the standard dist. Everything is there in the client package (which is what I checked for 2.0.1).

In my opinion if the fop.xconf is different than the one coming by default with Apache FOP (if it has DITA OT-specific related changes) it should also get included in the standard dist.

The standard package should not have FOP bundled at all. It's a build bug that the license files get included and the whole plugins/org.dita.pdf2/fop directory should be omitted.

Marking this closed as obsolete - we no longer ship a standard package, so any files that were missing from that (but present in the full package) are no longer an issue.


listener: cache grpc access log service and tracing config

This PR

Caches HTTP gRPC access log config similar network filters
Caches Tracing Config

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
37904946495a19f2cf6c0a1e387572dc6d76b97e
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
bb8b761f6cacedfeab99591107979cd191952587
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

Absolutely, the build process just take several cpu cycle


.tsx code format broken

From @mbilling on July 11, 2016 11:51

VSCode Version: Code - Insiders 1.4.0-insider (f6227ca157caed3ce3224ad9f760a8d5c8ed0e4d, 2016-07-11T05:07:20.965Z)
OS Version: Windows_NT ia32 10.0.10586

Steps to Reproduce:

Open new VSCODE
Paste kode from file Configurations.txt into Untitled-1
Save as e.g. "test.tsx"
Jump to line 1457
Press Alt + Shift + F or run format code command
Nothing happens - code is still the same (i believe the format code service dies here)
Create a new .tsx file make some simple typescript, e.g.

function(test:string)
   {
      let example      =   test;
   }

Press Alt + Shift + F and nothing happens. You need ´to restart VSCode to run "Format Code" again

/Michael
Copied from original issue: Microsoft/vscode#9067

Was able to reproduce this. It is a bug in the tsserver. The request returns with the following error:
Response received: configure (7). Request took 3 ms. Success: true
Sending request: format (8). Response expected: yes. Current queue length: 0
Arguments: {
    "file": "p:/mseng/VSCode/Playgrounds/bugs/9067/test.tsx",
    "line": 1,
    "offset": 1,
    "endLine": 1947,
    "endOffset": 1
}

Response received: format (8). Request took 293 ms. Success: false . Message: Error processing request. Debug Failure. False expression:

From @mbilling on July 11, 2016 12:2
Also try and fold the code on the render() method (line 1294)
This shows a bug in code folding - maybe there are some issues reported on that too.
So maybe a fix fixes multiple bugs

what is the status on this one?

@zhengbli have you fixed a bug similar to this one?

this looks fixed in latest builds of TS.

@dbaeumer @mhegazy Which release contains a fix to this issue?
I have attached screenshot of the version i'm running.

It's still a major obstacle for me every day.
It's not fixed in the insiders release, and I haven't seen this fixed in any of the insiders releases i have had installed.

By default VSCode comes in with TS 1.8. this issue is fixed in TS 2.0.2. to point VSCode to use newer version of TS, set typescript.sdk, see https://github.com/Microsoft/TypeScript-Handbook/blob/master/pages/Nightly Builds.md#visual-studio-code for more details.


Skill prep fails to initialize on shared skills

This recent change from 6e8d28a1a7df66e1fe1c3bd369fdbfe76d6da8a5 to fix the healer skillsahre s3 issue also causes abilities to initialize after skillshares are initialized, which causes skill prep not to apply to shared skills. Skill prep users all lost a noticeable chunk of dps on the static chart.

4aafc1c66b8140b86d876612c0144836192f208a


missing icon in title bar

Do you know what icon is supposed to be used?

I think we need to make one. This is a placeholder for that task.

Maybe for now this image could be used: https://raw.githubusercontent.com/KitwareMedical/UTM/main/Figures/UTM-3D-example.png
But I'd like to make a more symbolic icon-- I can look into this later


Indeterminate state for egui::Modifiers fields

Is your feature request related to a problem? Please describe.
I have Shortcuts which don't require any modifiers. However I noticed Modifiers::matches and consequently InputState::consume_shortcut requires no modifiers to be pressed in that case, which is a bummer, because it doesn't feel right when using the program.
Describe the solution you'd like
I'd like to see a third option for each of the modifier fields, so that you could set the value to "require pressed", "require not pressed" and "don't care". Option<bool> might possibly work, but I'm not completely sure how memory efficient that would be.
Describe alternatives you've considered
I have considered using InputState::consume_key instead of InputState::consume_shortcut for the shortcuts that don't require modifiers, but it doesn't seem quite right to me in case I would like to make them changeable by the user later.

Oh, it actually seems that Option<bool> takes up only 1 Byte, same as bool. Makes sense, though, as you actually only need one bit to express None/Some and one bit to express false/true.


Add Theme Rose Pine

Adding new theme Rose Pine and variants [https://github.com/rose-pine/alacritty]

Adding new themes is fairly simple and should be well documented in the readme. If you're interested in having a theme supported, you should try adding it yourself.
Since everyone can easily add themes themselves, it doesn't make sense to add themes based on issue request. It causes unnecessary work for maintainers and indicates that nobody is even interested enough to throw up a PR to do it.


How do I use these language packs?

Are they compatible with the latest version of the program?

@liaofeifan001 These are added automatically to LM Studio when it's updated. Currently, more languages are available in the latest beta: https://lmstudio.ai/beta-releases
To change the language in LM Studio, go to Settings -> General -> Language -> Choose from the dropdown.


SDK Docs

Description

Renamed samples to examples to be consistent with all other SDKs
Update home page README
Add daprdocs repo with all content to be rendered in docs.dapr.io
Split client examples into sub-directories

Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Extended the documentation

@rynowak @vinayada1 @msfussell there are 3 areas I haven't completed on this and need input:

daprdocs\content\en\dotnet-sdk-docs\dotnet-client.md needs examples for secrets and bindings
daprdocs\content\en\dotnet-sdk-docs\dotnet-sdk-extensions\dotnet-aspnet.md needs content
daprdocs\content\en\dotnet-sdk-docs\dotnet-sdk-extensions\dotnet-configuration.md needs content

@rynowak @vinayada1 @msfussell there are 3 areas I haven't completed on this and need input:

daprdocs\content\en\dotnet-sdk-docs\dotnet-client.md needs examples for secrets and bindings
daprdocs\content\en\dotnet-sdk-docs\dotnet-sdk-extensions\dotnet-aspnet.md needs content
daprdocs\content\en\dotnet-sdk-docs\dotnet-sdk-extensions\dotnet-configuration.md needs conent

@AaronCrawfis - can you resolve conflicts here? Also should this target release/1.0 instead?


feat(temporal-join): Temporal join executor

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?

Checklist For Contributors

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[x] I have demonstrated that backward compatibility is not broken by breaking changes and created issues to track deprecated features to be removed in the future. (Please refer to the issue)
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Checklist For Reviewers

[x] I have requested macro/micro-benchmarks as this PR can affect performance substantially, and the results are shown.

Documentation

[x] My PR DOES NOT contain user-facing changes.

Click here for Documentation
Types of user-facing changes
Please keep the types that apply to your changes, and remove the others.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note

#8123

Something we may refine for the cache in future PRs :)

call evict every epoch
clear the cache if necessary on scaling (see as_update_vnode_bitmap)

cc @wsx-ucb


[Feature Request]: Support for multiple conditions in the where metadata filtering.

Describe the problem
Including more than one condition in the where filtering results in the error below, despite it being explicitly mentioned in the documentation in Collection.py#L118
import chromadb
client = chromadb.Client()

collection = client.create_collection("all-my-documents")

collection.add(
    documents=["This is document1", "This is document2", "This is document3"],
    metadatas=[{"source": "notion", "good": "True"}, {"source": "google-docs", "good": "False"}, {"source": "google-docs", "good": "True"}],
    ids=["doc1", "doc2", "doc3"],
)
print(collection.query(
    query_texts=["This is a query document"],
    where={"source": "google-docs", "good": "True"},
))

Similarly, the issue occurs with the get function
print(collection.get(
    where={"source": "google-docs", "good": "True"},
))

$ python3 code.py

Traceback (most recent call last):
  File "/mnt/code/code.py", line 12, in <module>
    print(collection.query(
  File "/usr/local/lib/python3.9/site-packages/chromadb/api/models/Collection.py", line 183, in query
    where = validate_where(where) if where else None
  File "/usr/local/lib/python3.9/site-packages/chromadb/api/types.py", line 154, in validate_where
    raise ValueError(f"Expected where to have exactly one operator, got {where}")
ValueError: Expected where to have exactly one operator, got {'source': 'google-docs', 'good': 'True'}

An advanced use case would also include queries like less_than and greater_than and so on.
The code was ran:
Chroma Version 0.3.26
MacOS 13.4.1 (22F82)
Python version 3.9.13
Describe the proposed solution
The code above would utilize all filters simultaneously
For the query function, it would return:
>>> collection.query(query_texts=["This is a query document"], where={"source": "google-docs", "good": "True"})
{'ids': [['doc3']], 'embeddings': None, 'documents': [['This is document3']], 'metadatas': [[{'source': 'google-docs', 'good': 'True'}]], 'distances': [[0.412462321315]]}

For the get function, it would return:
>>> collection.get(where={"source": "google-docs", "good": "True"})
{'ids': ['doc3'], 'embeddings': None, 'documents': ['This is document3'], 'metadatas': [{'source': 'google-docs', 'good': 'True'}]}

Alternatives considered
I can write some code to post-process the results of the queries in python, which would do something like:

Utilize one of the filters while using the query or get functions
Post-process the results to apply the remaining filters.

However, this will be extremely inefficient once the filter selected doesn't reduce the amount of search results significantly. For example, if I have 2M documents, with 1M of them have {"good": True}, and the other 1M have {"good": False}, post-processing 1M documents in Python is very inefficient. This can be enhanced by checking in advance which filters divide the data significantly, but this is basically implementing multi-indexes for all columns, which is building a core database functionality, which would eventually lead me to just use another database.
Importance
i cannot use Chroma without it
Additional Information

I believe you can get your desired behaviour with the  $and operator
collection.get(
    where={"$and": [{"source": "google-docs" }, { "good": "True"}] }
)

This indeed solved the issue, thanks a lot!
Can this be better documented though? There are multiple mentions of the misleading documentation, like this, and (2 other occurrences in this file alone).
Also, I could not find a single explanation on https://docs.trychroma.com/ for how to use the $and and $or literals, I thought it is a JS feature. https://docs.trychroma.com/api-reference would be a suitable place.

There are some examples in the usage guide, here: https://docs.trychroma.com/usage-guide#using-logical-operators
But you are right, some of the documentation for the python API for where filters looks incorrect.

I believe you can get your desired behaviour with the $and operator
collection.get(
    where={"$and": [{"source": "google-docs" }, { "good": "True"}] }
)

This solution cannot be compatible with or and and at the same time


Support time varying depth dimensions for xarray datasets

Follows from issue #1128
Test notebook is on the following gist

I just pushed a small fix to the PR; it turned out that the depth fields were never connected to the grid because the Field.dataFiles is None for Fields created from xarray and therefore the following lines evaluate True https://github.com/OceanParcels/parcels/blob/f6e2ed7f7a2e45eed9acbb2603caf3c124a3c831/parcels/fieldset.py#L271-L272
This seems to be fixed now by changing the last bit to
or (f.dataFiles is None and f.creation_log != 'from_xarray_dataset'):

Can you check if this now works as expected?

I think it does indeed, see the gist !
Thanks for your help.
What next, should we try to adresse the large number of tests that are failing?
or work on a tutorial?
I also have a somewhat indirectly related question: could you please confirm using xarray does leverage its lazy capability (i.e. does not load full datasets in memory) ?

Great to hear that this fix seems to work, @apatlpo! I've just pushed a set of fixes (one related to PEP8, the other to a bug in reading the depth dimension from the dictionary when depth is set) so hopefully the CI should now give green ticks
I don't think we need a tutorial for this, but I've just added a sentence that this works in FieldSet.from_xarray_dataset() in the timevarying depth dimension tutorial. We do need a unit test though, I'll create that based on your gist and put it in tests/test_grid.py

I also have a somewhat indirectly related question: could you please confirm using xarray does leverage its lazy capability (i.e. does not load full datasets in memory) ?

Hmm, good question. To be honest I don't know. We haven't used FieldSet.from_xarray_dataset() in real-life applications yet, so no need to test/check this. I'd be very keen to hear the answer though; hopefully the lazy capabilities work out of the box!

Ok, I'll give a shot to test the lazyness of the code and report back

Ok, I'll give a shot to test the lazyness of the code and report back

Closing this PR for now, as there was no action for a long time


Serde allows external implementation of formats

This changes serde to allow external format implementations and statically registered them according to which support one wants.

The document will be updated in a following PR.


Feature: Allow permissive mode to be enabled/disabled per namespace

Please describe the Improvement and/or Feature Request

Permissive mode, while not as secure as the alternative, is the simplest way to get up and running with OSM. As such, many users may want to enable permissive mode on a per-namespace basis for various use-cases (e.g. multi-tenancy, selective onboarding, implicit trust in vendor namespaces, etc.)
Scope (please mark with X where applicable)

Permissive Traffic Policy  [X]

Possible use cases

Sure thing!
So essentially, OSM has two different trust models by default:

everything's trusted
nothing's trusted

My proposal is to add a third mode of operation: everything in my namespace is trusted. This matches Kubernetes convention where the namespace boundary is also the boundary for trust. This tertiary mode of execution is useful in scenarios where users may want to enable permissive mode for complex or brownfield workloads, but not for new services being deployed in other namespaces. Another example is one I've worked on personally: you may have namespaces for certain baseline/vendor services (e.g. redis cluster, grafana dashboard, vault) that have multiple intra-namespace components that are inherently trusted (perhaps because they were part of the same helm chart).

Sure thing!
So essentially, OSM has two different trust models by default:

everything's trusted
nothing's trusted

My proposal is to add a third mode of operation: everything in my namespace is trusted. This matches Kubernetes convention where the namespace boundary is also the boundary for trust. This tertiary mode of execution is useful in scenarios where users may want to enable permissive mode for complex or brownfield workloads, but not for new services being deployed in other namespaces. Another example is one I've worked on personally: you may have namespaces for certain baseline/vendor services (e.g. redis cluster, grafana dashboard, vault) that have multiple intra-namespace components that are inherently trusted (perhaps because they were part of the same helm chart).

Do you see a need to allow permissive mode for apps across namespaces to communicate? If we can keep the configuration simple (all or just within selected namespaces), it seems reasonable. If it is intended to support more complex permutations, I would consider enabling them through a more granular policy mechanism.

@shashankram no - I think the we keep things simple and not try to handle the cross-namespace case. That's a security issue waiting to happen, and at that point, users should be configuring granular access rules anyway

@shashankram no - I think the we keep things simple and not try to handle the cross-namespace case. That's a security issue waiting to happen, and at that point, users should be configuring granular access rules anyway

I don't think that should be a security issue as the intent would be explicit, but rather result in additional permutations that are not intuitive.
Note that the current permissive mode is about automatic service discovery and connectivity configuration vs explicit authorization policies. Apps still connect with each other in a trusted manner using mTLS, just that this happens without authorization policies. So the "trust" word can be misleading here.
If the ask is to support 2 forms of permissive mode (all namespaces, or within specific namespaces only), it seems more reasonable.

So the "trust" word can be misleading here.
That's fair - my original comment was concerning the "default" (i.e. out of the box) trust modes when first installing OSM; apologies if that wasn't clear.

I see where you're coming from with simplifying the permutations for permissive mode, and I'm good with that. The 2 forms you described make sense 👍🏾

"trust" should be re-phrased as "allowed" or "authorized".
I agree with these 2 forms of permissive mode as well. We can scope this feature as follows:
The permission policies among namespaces should be stored somewhere. If permissive mode is enabled in MeshConfig, by default it should be the all-namespace permissive mode. If a namespace has specified permission policy, then only the allowed namespaces will be added as the source of the RBAC filter in their Envoy sidecars. In this way, if a namespace only sets itself as the allowed namespace, this matches the case that Keith mentioned in the issue description.


What do the symbolic expressions in DIM file mean?

Hello：
I was just using your opensource software Symoro. It is so perfect and is easy for us to use. But some doubts confuse me while I’m working on it.
The first question is:
·	There are so many symbolic expressions in the dynamic identification model (D.I.M) file. They should be the elements of the  regression matrix D. But I can not identify the corresponding dynamic paramters. For example, to the element I1ZZ, what is the symbolic expression in matrix D?
The second question is:
·	The base inertial parameters have been calcualted in the software directly. But how can I know the corresponding regression matrix? Maybe I should manually regroup the dynamic identification model according to the base inetial paramters?
Many thanks and looking forward to hearing from you.

I also have the same questions. Have you to solved it?
Thank you!

I also want to know the symbolic expressions and matrix D.Have you solved it?
Thank you!


Implementation of new Footer component

Fixes
Fixes #60  by @OsujiPius
Description
The PR implements the brand new footer component similar to the one used in creativecommons.org
Tests
Start up the project locally on localhost:8080
Screenshots

Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main or master).
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no
visible errors.

Developer Certificate of Origin

For the purposes of this DCO, "license" is equivalent to "license or public domain dedication," and "open source license" is equivalent to "open content license or public domain dedication."

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@OsujiPius looks good

@dikehprosper thanks a bunch 😉

Thank you for taking the time to submit this PR as a contribution! ❤
As noted, on the Issue related to this, the Footer should follow the footer from https://opensource.creativecommons.org/ (I think that may have been what you meant instead when you wrong creativecommons.org).
You can see the difference by comparison that this PR does not match the footer precisely, which should look like this instead:

The mismatches would need to be corrected to account for this, before this PR could be accepted and merged.

Please see above comment about the mismatch in styles.

@possumbilities working on the changes now

Good work , all the best

@OsujiPius are you still working on this?

@OsujiPius Closing this as stale. If you work out a stable implementation at a future date, please feel free to submit a fresh PR ❤


Separate encryption key for each tenant

Description
From a security point of view it'd be a great option to have different encryption keys for each tenant. By default Laravel uses the APP_KEY env variable for the encryption, which if I'm not mistaken is shared by all tenants, meaning that all encrypted data can be decrypted with the given key regardless of the tenant.
Why this should be added
Separate encryption key for each tenant would greatly enhance the security of any multi-tenant application, could help with compliance requirements, etc.

On tenant creation you can generate an APP_KEY and store in your tenant data column:
'base64:' . base64_encode(      \Illuminate\Encryption\Encrypter::generateKey($this->laravel['config']['app.cipher'])  );
Then you can use Tenant Config feature to configure it.

That works but there aren't really any security gains associated with using this.

Separate encryption key for each tenant would greatly enhance the security of any multi-tenant application

How? And if you used tenant-specific keys where would you store them?

Well, this is not an easy question, of course. The default Laravel implementation stores the key in the .env file. In that case at least it's separated from the database. If the databased is dumped due to some kind of vulnerability then the key is not present in the DB. Or, if the DB is physically separated from the application (i.e. the DB is on a different server) then compromising one of the servers might not be enough to decrypt the values.
@darkons idea works I guess, but in that case the key is stored in the DB, which is a not a good idea, I'm afraid.
What we could do is to store the tenant's key in a file, not in the DB. And the tenants' keys could be encrypted with the central's key (.env APP_KEY).
What do you think?

Ultimately if the app can access the key in any way (it needs to, so that it's able to serve tenants), then the type of security compromise that you're trying to protect against would still lead to all tenant data being accessible.
One valid use case of this can be to make sure sessions/cookies are different on each domain I think.

That's true, but that's the case with all encryption. Even if you store the keys in HSM the app still needs to somehow decrpyt the data so at least in the memory there will be something that could be used by attackers, but that's out of the scope of this question.
Sessions/cookies are indeed a great example.
The main thing is to protect the data at rest. Also, most of the compliance requirements states to use different encryption keys in a multi-tenant environment (along with different databases and database users, but these are covered as far as I'm aware). And it just makes sense in a secure by design approach IMO.

@stancl will v4 provide something for this?

We can consider that, but I'd need to hear some arguments about actual security benefits that'd come from this.
As I stated above, an attacker would gain access to data by compromising the application in the vast majority of cases. And when the application is compromised, all tenant keys would be exposed because the application has access to them.
I can only see this being beneficial in cases where the attacker would gain access to a single tenant's data. Which is only realistic in uncommon setups. And even then — what would this actually protect against? If the data were encrypted using the app key and the attacker had the app key, then he presumably compromised the application already, thus gaining access to all tenant keys. And if the attacker would only have the data but not the key, there's no difference in what key is used.

One can imagine that depending on the tenant, a different security posture may be adopted.
For example, some tenants might want APP_KEY rotation while others might not.
You can also imagine a use case where the key is weak / compromised because of a tenant implementation, you then would benefit from a separated one.


Feature: Google Colab compatibility with TF 2.0.

Colaboratory is a free research tool for machine learning education and research. It’s a Jupyter notebook environment that requires no setup to use. Colab works with most major browsers, and is most thoroughly tested with desktop versions of Chrome and Firefox.
The purpose of this issue will be to track TF 2.0 compatibility with Colab.

I wonder what would be the transition period. Since for some time people would still have models with TF1 and just upgrading over night could be pretty radical.
I mean potentially colab can introduce another param for  runtime or Notebook settings, something like different cuda drivers

Looks like CUDA 10 support has landed for Google Colab!

I am closing the tracking issue as it was resolved. TF2.0 is completely compatible with Colab. Thanks!


[SPARK-9757] [SQL] Fixes persistence of Parquet relation with decimal column

PR #7967 enables us to save data source relations to metastore in Hive compatible format when possible. But it fails to persist Parquet relations with decimal column(s) to Hive metastore of versions lower than 1.2.0. This is because ParquetHiveSerDe in Hive versions prior to 1.2.0 doesn't support decimal. This PR checks for this case and falls back to Spark SQL specific metastore table format.

Merged build triggered.

Merged build started.

Test build #40641 has started for   PR 8130 at commit 194d7db.

Test build #40641 has finished for   PR 8130 at commit 194d7db.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #40650 has started for   PR 8130 at commit a5f39ba.

Test build #40650 has finished for   PR 8130 at commit a5f39ba.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
   * It is safe to add arguments modified by other methods in this class (such as

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Merged build triggered.

Merged build started.

Test build #40660 has started for   PR 8130 at commit 5ffe310.

Merged build finished. Test FAILed.

Test build #1501 has started for   PR 8130 at commit 5ffe310.

Test build #1501 has finished for   PR 8130 at commit 5ffe310.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

Test build #40660 has finished for   PR 8130 at commit 5ffe310.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #1507 has started for   PR 8130 at commit d42a0ef.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

Test build #1507 has finished for   PR 8130 at commit d42a0ef.

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

Test build #1525 has started for   PR 8130 at commit f4e4c2c.

Test build 1507 is not for the latest commit. I manually triggered 1525.

Test build #1525 has finished for   PR 8130 at commit f4e4c2c.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class QRDecomposition[QType, RType](Q: QType, R: RType)

Verified under my local MySQL backed Hive 0.13.1 metastore and it works. Merging to master and branch-1.5.

@yhuai @marmbrus Thanks for the review and helping fixing it! I'm merging this to master and branch-1.5.


Port to VS Code 1.3+

Hi,
I'm using VScode and the fantastic Material theme. But the VS extension for this theme is not compatible with vscode 1.2.29 and previous.
It could be great if you can update Kode Studio to 1.3.0 and more versions of VS Code.
Thank for your great work

It's bound to happen, every Kode Studio version is based on the most recent vscode version at the time of its release.

thanks, for that.
If someone is interested, I've created an extension that uses the color settings of that theme
It can be used in VScode 1.29-  (and in Kode Studio 18.1).
Can be found here
https://gitlab.com/vscodedev/gameamea-vs-themes


Fix the localization bug

The localizations for the error messages cannot be used because loading them causes a security error in itself. Consider using doPrivileged, since we now allow that in the SecurityManager since ca2d91adc04d65fc6fbdde9e35947e4a5cbea465. This should work.

No longer an issue due to doPrivileged already present down the line.


WAMP - "Unknown encoder libfaac" error

I have downloaded ffmpeg package from http://ffmpeg.zeranoe.com/builds for windows 64-bits and have set the ffmpeg.exe path in environment variables. Now, if I simply run the code to transcode the video :
$ffmpeg = FFMpeg\FFMpeg::create();
$video = $ffmpeg->open($video_path);
$format = new FFMpeg\Format\Video\X264();
$format->setKiloBitrate(1000)
->setAudioChannels(2)
->setAudioKiloBitrate(256);
$video->save($format, public_path().$path.$save_filename);
it gives error "Unknown encoder 'libfaac' "
FFMpeg\Exception\RuntimeException
"Encoding failed"
Can you please let me know how to over come this?

May be you have the same problem as: https://github.com/PHP-FFMpeg/PHP-FFMpeg/issues/89
Anyway, have you tried this:
$format->setAudioCodec("libmp3lame");

I have the same problem but I cannot use libmp3lame as it is not producing audio in iOS devices. Please let me know how to solve this?

Try any of the following: libvo_aacenc, libfaac, libmp3lame, libfdk_aac
$format ->setAudioCodec("libvo_aacenc");

Seems your version missing an encoder. Anyway, try the official ffmpeg version, not a fork or whatever Zeranoe is..

Related to: #222 #231 #137 #212 #165


fixed Waters "Unknown Generic Error"

fixed Waters "Unknown Generic Error" due to calling GetDriftTime() on functions existing in Waters .RAW but not listed in _extern.inf
Reported by Laura (Rozas?) and tomas-pluskal

Closes https://github.com/ProteoWizard/pwiz/issues/1409

@bspratt Just merged it.


Specify compatibility with govuk-frontend v5

The plugin works with either v4 or v5 of govuk-frontend

v5 of govuk-frontend is coming (and can be tested already using a prerelease).  The plugin works with v5 already, so we can specify this to avoid these warnings:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/govuk-frontend
npm ERR!   govuk-frontend@"github:alphagov/govuk-frontend#5b2bfde4f" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@x-govuk/govuk-prototype-components
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/govuk-frontend
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@x-govuk/govuk-prototype-components
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Alternatively - we could remove the dependency on govuk-frontend entirely, as we already depend on govuk-prototype-kit which itself depends on govuk-frontend?
cc @paulrobertlloyd @colinrotherham
(I'm a little bit out of my depth on this stuff)

Thinking about @paulrobertlloyd's comments in #110 a bit more:

Move govuk-frontend to peerDependencies. We need to indicate that this package only works with v4.1.0 or later (due to ESM changes in govuk-frontend and SCSS dependencies).

The warning above is doing exactly as designed, I think?
I'd wonder if you need optionalDependencies but do widen govuk-frontend if you need it at all?
-  "optionalDependencies": {
-    "govuk-prototype-kit": "^13.13.1"
-  },
  "peerDependencies": {
-   "govuk-frontend": "^4.1.0"
+   "govuk-frontend": "^4.1.0 || ^5.0.0"
  },

I'd assume you can temporarily use "^4.0.0 || ^5.0.0 || ^5.0.0-testing" to test out the preview

Watch out for other plugins requesting govuk-frontend via govuk-prototype-kit too
For example, running npm ls govuk-frontend in govuk-prototype-filters outputs:
└─┬<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>

Brainy hurty. Meanwhile: https://github.com/alphagov/govuk-frontend/issues/4353


rulesDirectory in extended configuration should also be resolved against the current dir

Bug Report

TSLint version: 2.9.1
TypeScript version: 2.6.2
Running TSLint via: CLI

I have a company-wide tslint configuration which is used by various projects via "extends" configuration.
I don't seem to be able to configure tslint-defocus to be included in the shared configuration.
The shared configuration:
{
  "defaultSeverity": "warning",
  "extends": "tslint-eslint-rules",
  "rulesDirectory": [
    "codelyzer",
    "./node_modules/tslint-defocus/dist"
  ],

Projects use this configuration in the following way:
{
  "extends": [
    "shared-configuration"
  ],

This is not an npm problem. tslint-defocus gets correctly installed in node_modules in the projects, but every time I run tslint in such project, I get the following error:
 ng lint

Failed to load AAA\tslint.json: Could not find custom rule directory: ./node_modules/tslint-defocus/dist
FatalError: Failed to load AAA\tslint.json: Could not find custom rule directory: ./node_modules/tslint-defocus/dist
    at new FatalError (C:\Users\matste\uptime\uptime\ui\ui-frontend\node_modules\tslint\lib\error.js:27:28)
    at Object.findConfiguration (C:\Users\matste\uptime\uptime\ui\ui-frontend\node_modules\tslint\lib\configuration.js:55:15)
    at lintConfigs.map (C:\Users\matste\uptime\uptime\ui\ui-frontend\node_modules\@angular\cli\tasks\lint.js:67:48)
    at Array.map (<anonymous>)

I tried all options: node_modules/tslint-defocus/dist, tslint-defocus/dist.
Looking at the code of the configuration.ts, it seems that when tslint sees tslint-defocus/dist, it first try to resolve it as a node module and fails predictably (the module is called 'tslint-defocus', not 'tslint-defocus/dist'). Then it tries to resolve it as a local path, but tslint resolves it relative to where the shared configuration is installed (relativeTo !== undefined).
export function getRulesDirectories(directories?: string | string[], relativeTo?: string): string[] {
    return arrayify(directories)
        .map((dir) => {
            if (!useAsPath(dir)) {
                try {
                    return path.dirname(resolve.sync(dir, { basedir: relativeTo }));
                } catch (err) {
                    // swallow error and fallback to using directory as path
                }
            }

            const absolutePath = relativeTo === undefined ? path.resolve(dir) : path.resolve(relativeTo, dir);
            if (absolutePath !== undefined) {
                if (!fs.existsSync(absolutePath)) {
                    throw new FatalError(`Could not find custom rule directory: ${dir}`);
                }
            }
            return absolutePath;
        });
}

In my opinion, tslint should also try local path (ignoring relativeTo), when the above options fail.

You could give it a go on a more recent version - I think this is available since 5.2.0

Tried on 5.11.0, running into the same issue.
Does getRulesDirectories ever get called relative to the extending config's directory? If so I'm not seeing it :/

Also hitting this on 5.11.0.
The rulesDirectory paths should be resolved relative to the extended package, not the extending package (which is what seems to be happening).

This bug is fixed in 5.14.0  🎉
(not sure about 5.12.x or 5.13.x)


SB-594

@geoand I think the name of the directories are fine

@metacosm Damn... Then I changed mine for nothing :P


added deploy --trigger to COMMAND_WTIHOUT_WORKSPACE_OPTIONS

Summary
Includes netlify deploy --trigger in the list of commands that don't require a workspace.
If you can, point me in the right direction for updating the tests necessary for this change and I can get it changed.
3 babies watching the ice cube for me

Hi @BlenderDude
Thanks for the PR! I'm wondering what the use case is for this - in the case of a monorepo you may have many different sites in one repository, and the workspace options are there to specify which site you'd like to deploy with netlify deploy --trigger.
If you'd like to pre-select the site you're deploying, you can use the --filter option, or --cwd to set the working directory.

Closing due to non-response. Please open an issue if you believe there is still a bug here!


is it possible to use an existing (gpg) ed22519 signing key or must we create another?

as per title - is it possible?
if not, is the created key able to be imported into gpg as my signing key?
P.S Thank you for your work - it is appreciated!

they are differs of format significantly, so yes, create another.
And you can't import it directly to the PGP.


PF power supplies accounting

In GitLab by @rkemp on May 23, 2018, 09:43
I have added a new contribution to the electrical energy required for the CS and PF coils.
Electrical energy is dissipated in PFC power supplies only when they increase or decrease the poloidal field energy.  This assumes that the power supplies include an energy storage system and that currents in the coils can be varied without loss when there is no change in the energy in the poloidal field. Energy is dissipated only when energy moves into or out of the store in the power supply.
(The poloidal field energy is the energy stored in the poloidal magnetic field, due to the plasma, the CS, and the PF coils.  Their separate contributions cannot be distinguished, as the energy density is not linear in the field.  It is possible, however, to distinguish the energy in the poloidal field from that in the toroidal field which is orthogonal.
  !+ad_vars  etapsu /0.9/ : Efficiency of transfer of PF stored energy into or out of storage.
  real(kind(1.0D0)) :: etapsu = 0.9D0

    do time = 1,5
        ...
        ! Electrical energy dissipated in PFC power supplies as they increase or decrease the poloidal field energy
        ! This assumes that the energy storage in the PFC power supply is lossless and that currents
        ! in the coils can be varied without loss when there is no change in the energy in the poloidal field.
        ! Energy is dissipated only when energy moves into or out of the store in the power supply.
        ! Issue #713
        pfdissipation(time) = abs( poloidalenergy(time+1)-poloidalenergy(time) ) * (1 /etapsu - 1)
    end do
    ! Mean power dissipated
    ! The flat top duration is the denominator, as this is the time when electricity is generated.
    pfpower = sum(pfdissipation(:)) / (time(5) - time(4))
    pfpowermw = pfpower / 1.d6
    ...
    !  PF wall plug power dissipated in power supply for ohmic heating (MW)
    !  This is additional to that required for moving stored energy around
    wall_plug_ohmicmw  = pohmmw * (1 /etapsu - 1)
    ! Total mean wall plug power dissipated in PFC and CS power supplies.  Issue #713
    pfwpmw = wall_plug_ohmicmw + pfpowermw

    ! Waste heat generated in PFC and CS power supplies (MW),
    ! classed as "secondary waste heat"
    pfsec = pfwpmw

For simplicity I have left the output description unchanged:
Electric power for PF coils (MW)                                         (pfwpmw)                      1.061  OP

The value of this power loss has increased from about 0.15 MW to 1 MW.

Original issue
There seems to be a significant error in accounting for the power fed to the PF coils. There is a variable
!+ad_vars  etapsu /0.9/ : Efficiency of ohmic heating

which is then used as follows:
    !  PF Power requirements
    !  Wall plug power (MW)
    pfwp = pohmmw / etapsu

This in turn is used for the power balance:
    !  Electrical power consumed by fusion power core systems
    !  (excluding heat transport pumps and auxiliary injection power system)
    !  Added pfwp (waste heat from PF coil ohmic heating)
    pcoresystems = crypmw + fachtmw + ppumpmw + tfacpd + trithtmw + vachtmw + pfwp

This is not correct.  The ohmic power pohmmw is always small, and is actually zero for non-inductive machines.
To see the magnitude of this apparent error, in the 2018 baseline, ramp-up of the PF system (including the plasma and CS) requires 59 MW of power to be fed in, while during the ramp-down 212 MW must be extracted, and dissipated or stored.  I don't think these large power flows are taken into account.

Note Richard's original comment:
In the 2017 baseline I see under the section "Electric Power Requirements"

PF coil power supplies (MW)                                              (ppfmw)                   1.160E+02  OP

and then

Total pulsed power (MW)                                                  (pacpmw)                  6.031E+02  OP

which is the sum of the powers in that section. However, under the plant electrical power balance this PF power is missing. Under the 'intermittent power usage' table the PF power during burn is indeed very low, but none of the numbers in this table match the 116 MW from ppfmw. What does this number actually represent and why is the total pulsed power inconsistent with the power consumption during a pulse?

Papercut review 2024
The content of this issue was merged into develop on the old GitLab repo back in July 2019 6a9b4e89 and therefore should be closed.
#972 is an extension of this issue with a discussion to replace the existing calculations with something new. Further work on this should be carried out there.


Improved JS code for markers and Directions

changed the code for markers
add eventlistener for click on map and get latlng
added code for directions
added function to add distance and duration
add event listener to input distance to form
add event listener to input duration to form
add html id class to distance
add html id class to duration

Please review and if approved merge to main


OLS-1203: Update all langchain libraries

Description
Update all langchain libraries
Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[x] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[x] Bump-up dependent library
[ ] Bump-up library or tool used for development (does not change the final image)
[ ] CI configuration change
[ ] Konflux configuration change

Related Tickets & Documents

Related Issue #OLS-1203
Closes #

/unhold

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

Project coverage is 73.76%. Comparing base (110cb1a) to head (19d1665).
Report is 4 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #1838       +/-   ##
===========================================
- Coverage   94.95%   73.76%   -21.19%
===========================================
  Files          61       59        -2
  Lines        2793     2718       -75
===========================================
- Hits         2652     2005      -647
- Misses        141      713      +572

see 34 files with indirect coverage changes

/test unit

/override "Red Hat Konflux / ols-enterprise-contract / lightspeed-service"
/approve


Adding "00" in empty cell in calculator

In the calculators, we often see a cell containing 00 , not sure if it is needed, but it would improve the calculator.
As of now it is missing and a empty cell is available too.
Would like to implement this under GSSOC' 21.
Thanks!
Screenshot Reference:

Go ahead
deadline: 23 April 2021


A cookbook?

It would be great to have a cookbook where you could offer code snippets for easy use (a nav, a sidebar, a hamburger, the typical front-end suspects.)
Very excited by this project especially the focus on AWS deployment!

This is a great idea!
We will definitely be working on something like this in the near future.
Thanks for checking Enhance out 🙌


Can't do black level correction (blc) to bayer raw.

for sensor raw (bayer), we should do blc before adjust the color and luma, otherwise the contrast after adjustment will be a problem.
could you please add blc function? Thanks.

Support black/white level correction:

https://github.com/carina-studio/PixelViewer/commit/261f6f5660deab9280928307f27fdf9607d67a25
https://github.com/carina-studio/PixelViewer/commit/1aa9d382ac97050d4e54a7b183bd3b66853b4681


Is this in working order?

Hi, Love the ideas behind this project! Looks interesting and promising!
Is this in current working order?

The instance seems to crash when adding a server?

https://kiki.network/ is also reporting a 502 Bad Gateway -- Maybe a possible cause?

Yeah server is up now

I've been playing with this thing all night and set-up a new federation of my own. I assume https://kiki.network/ is the default federation/region? How do I follow/friend you? :)

Yeah, the network was down, but now it is up.
If you click the pencil and then click "public" you should see a public feed. Then you can click on anyones name and follow them.

My question is however; if you setup your own region how do you follow
someone from another region? :)
James Mills / prologic
E<EMAIL_ADDRESS>W: prologic.shortcircuit.net.au
On Sun, Dec 23, 2018 at 1:15 AM Zack<EMAIL_ADDRESS>wrote:

Yeah, the network was down, but now it is up.
If you click the pencil and then click "public" you should see a public
feed. Then you can click on anyones name and follow them.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/schollz/kiki/issues/5#issuecomment-449577149, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABOv-h3aMN6FVy2lXhA_bHhij5LB0cQRks5u7kyLgaJpZM4ZcRw6
.

Your server is down again :)


ERROR  Exception in callback BaseSelectorEventLoop._read_from_self()

I'm using connection through VPN, and at some point server starts to display the following message several times a second.
ERROR  Exception in callback BaseSelectorEventLoop._read_from_self()
handle: <Handle BaseSelectorEventLoop._read_from_self()>
Traceback (most recent call last):
File "asyncio\events.py", line 88, in _run
File "asyncio\selector_events.py", line 119, in _read_from_self
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host
However the server seems to work just fine, at least for some time.
Still this issue inflates logs enormously until finally the server crashes.
Could you please share any thoughts on this?

Ive been seeing more and more issues related to stuff like this recently. I'm unable to do anything right now but I'll look into it when I get off work


Add screenshot to README.md

Hi, it would be great if you added a screenshot in README.md so people can see what does the app look like.
I honestly find it looks great, it is unfortunate to not show it!

Hi, thanks for your feedback and support.
Credit for the design goes to @lumiqcreative.
After implementing the Morse key (#38) I will add screenshots to the README.md.

Hey @luc65r, Morse version 1.6 will be released soon. Are you interested in doing the screenshots yourself then?


.NET Core Version of System.Web.UI.HtmlTextWriter

Following on from https://github.com/dotnet/corefx/issues/24169. What is the alternative? I'm using this type to do XSL transforms like so:
private static Stream XslTransform(XDocument document, XmlReader xslReader)
{
    var xslTransform = new XslCompiledTransform();
    var stringBuilder = new StringBuilder();

    using (var stringWriter = new StringWriter(stringBuilder))
    {
        using (var htmlWriter = new HtmlTextWriter(stringWriter))
        {
            xslTransform.Load(xslReader);
            xslTransform.Transform(document.CreateReader(), new XsltArgumentList(), htmlWriter);
            htmlWriter.Flush();
        }
    }

    return new MemoryStream(Encoding.UTF8.GetBytes(stringBuilder.ToString()));
}

@rynowak ?

@RehanSaeed in this scenario, what does using an HtmlTextWriter provider? Can you just use a plain TextWriter and get the same results? That is, just call:
            xslTransform.Transform(document.CreateReader(), new XsltArgumentList(), stringWriter);

One of the things it provides is the ability to output HTML5 (
) instead of XHTML (
).

Does it really do that as part of a transformation? I thought HtmlTextWriter just added a few additional features on top of the regular TextWriter, such as some extra APIs (for doing HTML-ish stuff), and then adding indentation support to existing APIs.

It certainly does. There is a list of HTML tags and whether they are closing or non-closing here.
My use case and probably the most common use case is XSLT transformation via HTML text writer, so in this scenario I don't use any of the extra API's that let you manually write HTML tags.

Hmm, odd, I just don't see how that code is used in the XSLT scenario. As far as I recall (and from a brief look at the code), those mapping are used only when someone is calling the HtmlTextWriter-specific APIs, such as RenderBeginTag. Does the XSLT transform downcast the writer and call HTML-specific APIs?

Here is some relevant sample code:
        public string Translate(XDocument document)
        {
            using (var stream = this.GetXsltStream())
            {
                using (var xslReader = XmlReader.Create(stream))
                {
                    return Transform(document, xslReader);
                }
            }
        }

        private static string Transform(XDocument document, XmlReader xslReader)
        {
            var xslTransform = new XslCompiledTransform();
            var stringBuilder = new StringBuilder();

            using (var stringWriter = new StringWriter(stringBuilder))
            {
                using (var htmlWriter = new HtmlTextWriter(stringWriter))
                {
                    xslTransform.Load(xslReader);
                    xslTransform.Transform(document.CreateReader(), new XsltArgumentList(), htmlWriter);
                    htmlWriter.Flush();
                }
            }

            return stringBuilder.ToString();
        }

We're closing this issue because it is not planned for any upcoming release.

I agree with op, this is a need. XMlTextWriter closes tags that it sholdn't IE, Edge, Chrome puke those tags.


simplify units: use cm throughout in place of Angstroms

I also switched from wls to λs in a couple places for more consistency.

Do you know why the macOS tests failed?

Do you know why the macOS tests failed?

Not sure, it looks like it timed out?  We can look into it if it happens again.


American

@A2tb is this a mistake?

@A2tb is this a mistake?

well no I wanted to take some short with you I hope that does not bother you


SCRUM-4335: bugfix after rc-1 on beta

Library publishing failed during beta deployment. This PR upgrades maven wrapper to try to fix the publishing
Removes transactional annotation from the rolldown method. It fails owed to the 2 persistence units since quarkus-3.8.2, and I did'n notice it in the alpha deploy (alpha rolldown does nothing)

Bugfix already merged in https://github.com/alliance-genome/agr_mati/pull/78


Enabling more fail on error scenarios

Turning on a number of compiler linting errors so we can be more stringent. Suppressing a small number of the failures, and fixing the rest.
This PR also modifies the azure pipelines config files so that builds that are configured to run under JDK 11 are using the java-lts profile to enable the JDK 11 compilation targets.

Changes are still happening in azure-core, it isn't finalised yet.

@mitchdenny Any concern with the yml changes?


[Adaptive] Re-evaluate all events exposed via Adaptive dialog including protocol, dialog and adaptive events.

Filing this ticket so we review and distill the set of events exposed via adaptive. The current set is a union of protocol level events, dialog events as well as adaptive events. we should pare back the list to only those that are backed by actual user scenarios as well as consider adding new events that help fulfill core unmet user needs.

We should setup a meeting to go through the current list of events.

Also onTurn for OAuth

Also remove StepChangeType.endSequence. We shouldn't need this because of cancelAllDialogs()

From a discussion with @stevenic: we should move away from using step count and mvoe towards recording in memory whether there was n interruption and act based off whether interrupted is true or false

@tomlm is this complete with your last PR or is there any remaining work?

Here's the final list of adaptive events and handlers for Ignite release.


Proper MacOSX support?

I am working toward fixing all MacOSX bugs, and making compiling on all platforms relatively easy.

Basic support is added with a few bugs relating to fetching mouse input which is covered more in #23


STRUCTURE of SRC

assets
images
styles
components
pages

Home.jsx
About.jsx
ProjectGallery.jsx
Project.jsx
Contact.jsx

common

Header.jsx
Footer.jsx

navigation

Nav.jsx

App.css
App.jsx
index.css
main.jsx
...

Issue successfully addressed!
I've implemented the structure for your React project, incorporating all the specified components and elements as per the requirements. The code includes individual components for common elements, navigation, and pages.


Larger assets are not correctly scaled

In my project, I only have<EMAIL_ADDRESS>Packager scales it down nicely, I guess on iPhone it will device read dimensions by 3.
However, Haul loads it raw resulting in the image taking too much space.
Screenshot:

CC: @satya164

Any update on this? Need to release a new version soon 💯

@grabbou oh sorry, I'll send the pr soon. just some testing needed

No worries, juts wanted to follow up on status.
On Wed, 14 Jun 2017, 17:20 Satyajit Sahoo<EMAIL_ADDRESS>wrote:

@grabbou https://github.com/grabbou oh sorry, I'll send the pr soon.
just some testing needed
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/callstack-io/haul/issues/166#issuecomment-308465502,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACWcxoeSfV4ZUIpoJT5qrCdazg4L7fTkks5sD_pMgaJpZM4Nzx_9
.

Is this fixed now?


Add test for input-ref app

Fixes #70

Codecov Report

Merging #71 (4b7709d) into main (2b9a19c) will increase coverage by 8.86%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #71      +/-   ##
==========================================
+ Coverage   80.75%   89.61%   +8.86%
==========================================
  Files          24       24
  Lines         530      549      +19
==========================================
+ Hits          428      492      +64
+ Misses        102       57      -45

Impacted Files
Coverage Δ

...ddata_vegattributes/app/input_reference_samples.py
83.72% <100.00%> (+83.72%)
:arrow_up:

...oddata_vegattributes/csv_reference_sample_store.py
97.61% <100.00%> (+7.87%)
:arrow_up:

fooddata_vegattributes/reference_samples_csv.py
98.59% <100.00%> (+5.60%)
:arrow_up:

fooddata_vegattributes/indexed_fooddata.py
97.61% <0.00%> (+2.38%)
:arrow_up:

...ddata_vegattributes/indexed_fooddata_food_store.py
75.00% <0.00%> (+3.57%)
:arrow_up:

fooddata_vegattributes/fdc_app.py
100.00% <0.00%> (+100.00%)
:arrow_up:

Continue to review full report at Codecov.

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


Trying to get Accordion component to work

What did you do?
I installed react-foundation using npm.
Then in my component I imported the necessary react-foundation components.
import { Accordion, AccordionItem, AccordionContent, AccordionTitle} from 'react-foundation'
Then  I set up my component as shown below (there's an axios get being called in componentDidMount to set the donors state).
<Accordion>
	{this.state.donors.map(function(donor, i) {
		return(
			<AccordionItem key={donor.title}>
				<AccordionTitle>{donor.title}</AccordionTitle>
				<AccordionContent>
					<div dangerouslySetInnerHTML={{__html: donor.markup}} />
				</AccordionContent>
			</AccordionItem>
		);
 	})}
</Accordion>

What did you expect to happen?
I expected the accordion to open and collapse when clicking the titles
What actually happened?
Nothing happens when you click the titles. The content is never shown.
What version of this module are you using?
Latest version

@kbrabrand maybe you can help since you added this?

Sorry about the delay, I've been on vacation ☀.
Yeah. This is the discussion mentioned in #30 regarding stateful vs. stateless component. When implementing I had to make a choice on whether the state should be kept by the component or should be something that the app that use the component should keep the state and pass it to the component.
The decision was to let the components be stateless and keep the state outside react-foundation. We might want to revisit this, but it involves a fair bit of logic to check for component types in relation to automagically setting click handler props on accordion panels and so forth. What do you think, @Jalle19?

Here is an example of how we've used it in a project:
import React, { Component } from 'react';
import PropTypes from 'prop-types';
import autobind from 'react-autobind';

import {
  Accordion as BaseAccordion,
  AccordionItem,
  AccordionTitle,
  AccordionContent,
} from 'react-foundation';

import Text from './Text';

export default class Accordion extends Component {
  static propTypes = {
    panels: PropTypes.arrayOf(PropTypes.object).isRequired,
  }

  constructor(props) {
    super(props);
    autobind(this);
  }

  state = { openPanels: {} }

  togglePanel(id) {
    this.setState({
      openPanels: {
        ...this.state.openPanels,
        [id]: !this.state.openPanels[id],
      },
    });
  }

  render() {
    const { panels = [] } = this.props;
    const { openPanels } = this.state;

    return (
      <BaseAccordion>
        {panels.map((panel) => {
          const active = !!openPanels[panel.id];

          return (
            <AccordionItem key={panel.id} isActive={active}>
              <AccordionTitle
                onClick={() => this.togglePanel(panel.id)}
              >{panel.heading}</AccordionTitle>

              <AccordionContent isActive={active} style={{ display: active ? 'block' : 'none' }}>
                <Text text={panel.text} />
              </AccordionContent>
            </AccordionItem>
          );
        })}
      </BaseAccordion>
    );
  }
}

@kbrabrand I have no opinion on any of this, I'm not a front-end developer.

@kbrabrand I agree with the original decision as there are far too many edge-cases to account for.


scale up the images in instructor insights

For instructor images, scale them up to full column width.
Designs and Mockups
Before:

After:

Acceptance Criteria:

[ ] this change should probably be limited to instructor insights

@pdpinch I have created a PR for this but I have few things in mind:

All images are scaled and since images have different sizes, so scaling relatively smaller images, to cover 100% width will cause distorted pixels. But if the images coming are of high quality then we are good!

Since all the content is coming from .md files and content is being rendered like this:

which is being reused for other sections as well and global css is applied to it so I'm not sure whether we can limit this change to instructor insights only. Perhaps, @gumaerc might have any suggestion?

In the Instructor Insights section, the images should all be high enough resolution for this to work.
If this change affects all images though, we might have some undesirable effects on:

video gallery pages like https://ocwnext.odl.mit.edu/courses/18-404j-theory-of-computation-fall-2020/video_galleries/video-lectures/
courses with tiny thumbnails like https://ocwnext-rc.odl.mit.edu/courses/9-00sc-introduction-to-psychology-fall-2011/pages/brain-ii/

Okay, I'll look into it

@pdpinch I have updated the PR and now this change (scaling images) is only applied to Instructor insights and the PR is ready for review. However, I'm still thinking that maybe this should a fix in studio, from where all the images are being generated/coming, as we only have to give width:100% to those images which we need to scale.
Perhaps, @gumaerc can share his thoughts?


Special Projects: Arbitrum Special Projects

Ongoing work on Special Projects closing on 03/29

Specs and tickets are ready. Waiting for smart contract work


Both of the services are down

http://pwndb2am4tzkvold.onion/
http://pwndb2am4tzkvold.onion.pet/

Can confirm, tried pwndb,py, no avail.

Confrimed, still unreachable

Now it seem to be online


add k8s 1.28 to test matrix

Describe the solution you'd like
[A clear and concise description of what you want to happen.]
add 1.28.0 to test matrix
https://github.com/eraser-dev/eraser/blob/7cdb6eb5a14eece9a2b35a19d0485067e8728318/.github/workflows/e2e-test.yaml#L46
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

Eraser version:
Kubernetes version: (use kubectl version):

Could I pick this up? 🖐🏼
Also, will we want to keep the other Kubernetes versions (1.25.11) in the matrix?
And/or would it be worth updating them to their latest patch releases while we're here? (1.25.13, 1.26.8, 1.27.5`)

Ideally we want to make sure to test on all supported version so we want to append 1.28 while keeping the remaining same but feel free to bump to latest patch version available in https://hub.docker.com/r/kindest/node/

Ah thanks! I was basing releases off of their release page, but noticing we're at the latest releases based on what's pushed to docker 👍🏼


Removing yarn audit from CI

Looks like it gets in the way, e.g. these builds fail, but yarn audit stops failing after updating yarn.lock:
https://travis-ci.com/github/nearprotocol/nearlib/jobs/296530318
https://travis-ci.com/github/nearprotocol/nearlib/jobs/296530604
However it has nothing to do with security of library, as yarn.lock from this repo isn't honored when installing library as dependency.

@janedegtiareva I think it might make sense include the check as part of the process when cutting release builds vs running for every PR (which gets in a way). Maybe just add to pre-publish script now (so that np checks for it when publishing).


flutter pwa not work offline

Hi
I just create a flutter web project and compile it.flutter version 3.0.4
I upload to my host .
first it doesnt work so i change <base href="/"> to <base href="">
after that i check application and it say page does not work offline.and install app not show.
I test this page https://gallery.flutter.dev/.it work correct.
can anyone help me?example?
thanks

Hi @mzelecom, running PWA offline is not fully supported as of today. Please see this issue for more details https://github.com/flutter/flutter/issues/60069.
Closing this issue as a duplicate.


refactor(@embark/cmd): make build command work again

This commit refactors the build command to use the newly refactored
event APIs.

Let's wait for #1784 to land first as it introduces compileAndDeploySmartContracts(engine) which can be used in build() as well.


No button icons and exit-fullscreen button not working

I'm having multiple issues with the plugin, which could be related. I installed from GitHub directly ("leaflet-fullscreen": "git://github.com/runette/Leaflet.fullscreen.git"  in package.json). This is what I see when displaying a map:

The icon in the fullscreen button is missing. When I click the button, the map is displayed in fullscreen as expected. There is still no icon in the button.
When I click the button again in fullscreen mode, nothing happens (it should exit fullscreen, I would expect).
There are no messages in the console.
Am I doing something wrong? Is the plugin broken? Thanks!
Maybe related to https://github.com/Leaflet/Leaflet.fullscreen/issues/121

I solved part of it - apparently I had to explicitly import the CSS file. The exit-fullscreen issue seems to be caused by the plugin not realizing that it is in fullscreen, as the button icon does not change when going fullscreen. When I use pseudo-fullscreen instead, it does work. However that is suboptimal, and the escape button does not seem to work in that mode.

Can you show your problem at codepen or something similar?


Let peers add threads from self + replicate

Avoids extraneous dials when the data can assume to be already available locally (self dials). This is useful/required for multi-tenant setups where a single peer may be managing multiple threads/logs on behalf of other (remote) peers. For instance, we don't want clients to 'care' if their remote host is already be replicating a thread they are involved in.
Ideally, there would be some logic in here to catch things like this (or other combinations of local vs remote addrs):
import manet "github.com/multiformats/go-multiaddr-net"
...
// Early out if we aren't going to be able to dial this peer
if !manet.IsPublicAddr(addr) {
	err = fmt.Errorf("addr must be publicly routable address")
	return
}

But I don't think we can assume, based on address alone, that we can filter something out. We might be,

A local peer dialing another peer on the same machine
A local peer dialing another peer on another machine on the same local network
A local peer dialing another peer on another machine on the internet
A client peer controlling a remote peer to do any of the above

So I'm going to leave most of the 'filtering' logic to clients. For now, the Go client will not do any filtering, because likely it is operating via a localhost, but the Javascript clients should filter out local host addrs by default.

Cheers!


Accessing compile-time generated service metadata at listener init phase

Service declarations create service objects and attach themselves to listeners by passing references to service objects. Listeners use service objects to extract the information required to route requests to related resources or remote functions.
Some of these protocol listeners need to access additional compile-time generated service metadata. E.g., GraphQL schema, OpenAPI description, gRPC protobuf mappings. We need to figure out a way to pass such service metadata to listeners.
The gRPC uses a service-level annotation, but it is generated by the gRPC tool (not compile-time).
We could use the same approach in other scenarios. What if we generate the OpenAPI description during the compile-time and add a service-level annotation to each HTTP service? We need the CodeModifier compiler plugin to implement this, though.
Regardless of the implementation complexity, what do you think about this? @shafreenAnfar @daneshk @azinneera

Yeah, sounds good. If we can annotate the meta information as part of the service, that would be the ideal solution for us.

Removing GraphQL label since this is now implemented


feat(#214): Correct Directory For Generated Sources

Change output directory from jeo/xmir to generated-sources/xmir.
Closes: #214.

History:

feat(#214): Change default directory from 'jeo/xmir' to 'generated-sources/xmir'
feat(#214): fix all integration tests

PR-Codex overview
This PR focuses on refactoring file paths in the codebase.
Detailed summary

Updated file paths in multiple Java files from "jeo/xmir" to "xmir".
Updated file paths in multiple Groovy test files from "jeo/xmir" to "xmir".
Updated file paths in Maven plugin configuration files from "jeo/xmir" to "generated-sources/xmir".
Updated file paths in the README.md file from "target/jeo" to "target/generated-sources".
Updated file paths in Groovy test files from "target/jeo" to "target/generated-sources".

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@maxonfjvipon Could you take a look, please?

@maxonfjvipon reminder

@rultor merge

@rultor merge

@volodya-lombrozo OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@volodya-lombrozo Done! FYI, the full log is here (took me 3min)


[account-web-vault]: Modal CSS conflicts with bootstrap css

Problem
The connect  modal does not display when the package is used in a js framework set up with bootstrap CSS, this happens as a result of CSS conflict when the bootstrap/dist/css/bootstrap.min.css is imported
see the discord thread of the observation :
https://discord.com/channels/664594912460668960/1026461094421729340/1028925314300129330
cc @nick-verida @tahpot

@tahpot,
While going through ShinzoHiro#3741 observation  concerning this error from the discord channel
I could see where bootstrap defined this global CSS rule which overrides the hidden attribute set in our account vault modal

// Hidden attribute
//
// Always hide an element with the `hidden` HTML attribute.

[hidden] {
  display: none !important;
}

Removing the hidden attribute in the parent modal div from the account-web-vault packages resolves this because the parent div with class name verida-modal-wrapper has its initial display set to none .
What are your thoughts on this?
cc @nick-verida @aurelticot

@cmcWebCode40 Sorry, I don't understand your question.
Do you have a proposed code change to review that fixes the problem?

After discussion, this ("Removing the hidden attribute in the parent modal div from the account-web-vault") seems like a good solution. @cmcWebCode40 will do a PR.

@cmcWebCode40 Sorry, I don't understand your question.
Do you have a proposed code change to review that fixes the problem?

@taphot I have opened a PR that fixes the issue here https://github.com/verida/verida-js/pull/240


Remove Python 2 from setup.py

Fixes #44.

Let's get this in fast. You'll need a new version number and tag number for it to go to pypi.


New version: TaylorIntegration v0.7.0

Registering package: TaylorIntegration
Repository: https://github.com/PerezHz/TaylorIntegration.jl
Created by: @PerezHz
Version: v0.7.0
Commit: 1c419c96754d0a947f9801f0ea70c067d4af171c
Reviewed by: @PerezHz
Reference: https://github.com/PerezHz/TaylorIntegration.jl/issues/87#issuecomment-545125937

Your new version pull request does not meet all of the guidelines for automatic merging.
Specifically, your pull request does not meet the following guidelines:

The following dependencies do not have a compat entry that has an upper bound: DataStructures, DiffEqBase, Espresso, Reexport, Requires, TaylorSeries, julia

It is important to note that if your pull request does not meet the guidelines for automatic merging, this does not mean that your pull request will never be merged. It just means that your pull request will require manual review by a human.

These guidelines are intended not as requirements for packages but as very conservative guidelines, which, if your new package or new version of a package meets them, it may be automatically merged.

On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.
Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)
If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.

[noblock]

Your new version pull request does not meet all of the guidelines for automatic merging.
Specifically, your pull request does not meet the following guidelines:

The following dependencies do not have a compat entry that has an upper bound: DataStructures, DiffEqBase, Espresso, Reexport, Requires, TaylorSeries, julia

It is important to note that if your pull request does not meet the guidelines for automatic merging, this does not mean that your pull request will never be merged. It just means that your pull request will require manual review by a human.

These guidelines are intended not as requirements for packages but as very conservative guidelines, which, if your new package or new version of a package meets them, it may be automatically merged.

On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.
Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)
If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.

[noblock]

Any hints to understand the problem why this has some tests that are not succesfull and cannot be merged?
cc @PerezHz

Your new version pull request does not meet all of the guidelines for automatic merging.
Specifically, your pull request does not meet the following guidelines:
Any hints to understand the problem why this has some tests that are not succesfull and cannot be merged?

It is given in the previous comment: https://github.com/JuliaRegistries/General/pull/4612#issuecomment-545130953

Please fix the compatibility bounds for the next release such that it will be automatically merged.


chore: cleaning up the repository

This is to keep the focus on the app only
by removing resources related to the launcher
and probably others release workflows that
are not required for now.
The 16.x branch was created to preserve the
removed configuration and resources.

Coverage remained the same at 85.161% when pulling c0533332a3a3828a95ab2a3ee464bb17e5e30e0e on cleanup into 94cce5e4056f58511bd1b66576e64594e5ac4d4f on main.


when using add() in string literals multiple times it continuously increases the date

Describe the bug
When using a moment object repeatedly in a string literal it repeats the addition.
To Reproduce
Steps to reproduce the behavior:

Create a js file with the following code:

const moment = require("moment");
let strDate = "22/10/2020"
let startDate = moment(strDate, "DD/MM/YYYY")
console.log(startDate.format("DD/MMM/YYYY"))
console.log(`${startDate.add(1, "d").format("DD MMM YYYY")} ${startDate.add(1, "d").format("DD MMM YYYY")}`)

2. Running the js file with node  produces the output:

22/Oct/2020
23 Oct 2020 24 Oct 2020

Expected behavior
I would have expected the output:

22/Oct/2020
23 Oct 2020 23 Oct 2020

Desktop (please complete the following information):

OS: win10
Browser Electron Chromium and in Node.js terminal

This behavior is intended:

Mutates the original moment by adding time.

You'll have to clone at each step.

I see... apologies for the confusion and thanks for the response.


Consider providing zstd tarballs on static.r-l.o

To compensate for https://github.com/rust-lang/infra-team/issues/89.

Decompression is probably still faster with .gz but if we care about that zstd-compression is probably the better option.

I benchmarked rustc + rust-std + cargo + clippy + rustfmt + llvm-tools to help choose a compression level:

compression
size (MB)
extraction time (sec)

none
649
N/A

gz
215
3.6

xz
127
8.4

zstd -1
232
1.2

zstd -2
217

zstd -3
207
1.2

zstd -4
203

zstd -5
198

zstd -6
193

zstd -7
190

zstd -8
188

zstd -9
184

zstd -10
182
1.25

zstd -11
182

zstd -12
181

zstd -13
181

zstd -14
181

zstd -15
180

zstd -16
174

zstd -17
166

zstd -18
159

zstd -19
158
1.4

At level 19, decompressing in 1.4 seconds is significantly faster than 8.4 seconds for xz. Users will notice this.
The tradeoff is that this loses 35% of the bandwidth benefit of #89.
The user must also be able to download 31 MB in 7 seconds (35 Mbps; 4.4 MiB/s) in order to see any benefit. For comparison, I get 90+ MiB/s from static.rust-lang.org so zstd would definitely be a speedup for me. Perhaps rustup could choose between xz and zstd based on the observed speed. I imagine https://github.com/rust-lang/rustup/issues/731 would also be relevant to choosing optimally.

Relevant discussion on the rustup side:

https://github.com/rust-lang/rustup/issues/1858
https://github.com/rust-lang/rustup/issues/2488
https://github.com/rust-lang/rustup/pull/2676

Is there any update on this? I'm using rules_rust in CI (github actions), so I'm downloading rust a lot, and we're really suffering those decompression times. It'd be great if we could get official zst tarballs, at least for releases!


FixCode.xcplugin' not present in DVTPlugInCompatibilityUUIDs

Hello,
i am using FixCode plugin with Fastlane it seems to install
[14:32:34]: --- Step: install_xcode_plugin ---
[14:32:34]: ----------------------------------
[14:32:34]: $ curl -Lso /var/folders/my/m6ynh3bn6tq06h7xr3js0z7r0000gn/T/plugin.zip https://github.com/fastlane/FixCode/releases/download/0.2.0/FixCode.xcplugin.zip
[14:32:34]: $ unzip -qo '/var/folders/my/m6ynh3bn6tq06h7xr3js0z7r0000gn/T/plugin.zip' -d '/Users/travis/Library/Application Support/Developer/Shared/Xcode/Plug-ins'
[14:32:34]: Plugin FixCode.xcplugin installed successfully
[14:32:34]: Please restart Xcode to use the newly installed plugin
but then later on in my build i get a few errors / warnings like the one below
xcodebuild[1552:6251] [MT] PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/FixCode.xcplugin' not present in DVTPlugInCompatibilityUUIDs
do i need to run another command to restart xcode?

Please use the latest version of the plugin, which is 0.5.0 which should contain the required compatibility UUID.

cool cool, thanks!
i was using
https://github.com/fastlane/FixCode/releases/download/0.2.0/FixCode.xcplugin.zip