[psLib] StringIO -> BytesIO fails with AttributeError: no attribute 'buf'

extractor can't load Type1 fonts any more due to a change in psLib module, which replaced StringIO.StringIO with io.BytesIO. Unlike the former, the latter does not have a 'buf' attribute.
https://github.com/behdad/fonttools/commit/bf0e336d316518115a7b47da4f721bb8a009b3e1#diff-d80be98c7272686386f0942c395e1ac3
Traceback (most recent call last):
  File "<untitled>", line 14, in <module>
  File "extractor/formats/type1.pyc", line 23, in extractFontFromType1
  File "extractor/formats/type1.pyc", line 186, in _extractType1GlyphOrder
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/fontTools/misc/psLib.py", line 159, in interpret
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/fontTools/misc/psLib.py", line 53, in getnexttoken
AttributeError: 'PSTokenizer' object has no attribute 'buf'

while debugging this, I also discovered that the whole t1Lib is not working with Python 3 because of unicode vs bytes issues...
This will take a while. :-/

sigh...

yeah.
$ python Lib/fontTools/misc/psLib_test.py
Traceback (most recent call last):
  File "Lib/fontTools/misc/psLib_test.py", line 11, in <module>
    ttFont = T1Font(t1path)
  File "/Users/cosimolupo/Documents/Github/fonttools/Lib/fontTools/t1Lib.py", line 55, in __init__
    self.data, type = read(path)
  File "/Users/cosimolupo/Documents/Github/fonttools/Lib/fontTools/t1Lib.py", line 112, in read
    return readOther(path), 'OTHER'
  File "/Users/cosimolupo/Documents/Github/fonttools/Lib/fontTools/t1Lib.py", line 207, in readOther
    chunks = findEncryptedChunks(data)
  File "/Users/cosimolupo/Documents/Github/fonttools/Lib/fontTools/t1Lib.py", line 315, in findEncryptedChunks
    eBegin = data.find(EEXECBEGIN)
TypeError: 'str' does not support the buffer interface

but don't worry, I'll fix this ;)

yeah.
$ python Lib/fontTools/misc/psLib_test.py
Traceback (most recent call last):
File "Lib/fontTools/misc/psLib_test.py", line 11, in
ttFont = T1Font(t1path)
File "/Users/cosimolupo/Documents/Github/fonttools/Lib/fontTools/t1Lib.py", line 55, in init
self.data, type = read(path)
File "/Users/cosimolupo/Documents/Github/fonttools/Lib/fontTools/t1Lib.py", line 112, in read
return readOther(path), 'OTHER'
File "/Users/cosimolupo/Documents/Github/fonttools/Lib/fontTools/t1Lib.py", line 207, in readOther
chunks = findEncryptedChunks(data)
File "/Users/cosimolupo/Documents/Github/fonttools/Lib/fontTools/t1Lib.py", line 315, in findEncryptedChunks
eBegin = data.find(EEXECBEGIN)
TypeError: 'str' does not support the buffer interface

Humm.  Is psLib_test something you just wrote?  I don't have it.  But it looks like you are not opening the test data in binary there...

Yes, it was something I am writing for testing the issue. The data is open in binary. It's actually the constant EEXECBEGIN which is a str (that is, unicode in py3).
I'll look into it tomorrow.
On Tue, Oct 20, 2015 at 7:48 PM, Behdad Esfahbod<EMAIL_ADDRESS>wrote:

yeah.
$ python Lib/fontTools/misc/psLib_test.py
Traceback (most recent call last):
File "Lib/fontTools/misc/psLib_test.py", line 11, in
ttFont = T1Font(t1path)
File "/Users/cosimolupo/Documents/Github/fonttools/Lib/fontTools/t1Lib.py", line 55, in init
self.data, type = read(path)
File "/Users/cosimolupo/Documents/Github/fonttools/Lib/fontTools/t1Lib.py", line 112, in read
return readOther(path), 'OTHER'
File "/Users/cosimolupo/Documents/Github/fonttools/Lib/fontTools/t1Lib.py", line 207, in readOther
chunks = findEncryptedChunks(data)
File "/Users/cosimolupo/Documents/Github/fonttools/Lib/fontTools/t1Lib.py", line 315, in findEncryptedChunks
eBegin = data.find(EEXECBEGIN)
TypeError: 'str' does not support the buffer interface
Humm.  Is psLib_test something you just wrote?  I don't have it.  But it looks like you are not opening the test data in binary there...

Reply to this email directly or view it on GitHub:
https://github.com/behdad/fonttools/issues/391#issuecomment-149664850

OK, I realised that there's too much work to do in order to make t1Lib.py and related modules work with python3...
So what I'll do to fix the current Robofont/extractor issue with Type1 fonts is to revert to the old python2-only StringIO.StringIO as a base class for the PSTokenizer, and explicitly -- but hopefully, only temporarily -- drop support for t1Lib if sys.version[0] > '2'.
I'll open a separate issue to track the t1Lib/python3 issues.


Environment variables not being expanded on merge comment

Hi, not sure if this is the right place to ask this kind of question, for this project, sorry if not. I'm trying to set a merge comment in the "GitHub Pull Request Merger" postbuild action similar to what github uses:
Merge pull request #${ghprbPullId} from ${ghprbPullAuthorLogin}/${ghprbSourceBranch}

${ghprbPullTitle}

${ghprbPullLongDescription}

However the environment variables are not being expanded, how can this be done?
Thanks! :)

That would be an oversight(bug) on my part.  I will get that fixed and pushed out this week.

@DavidTanner thanks a lot! :blush:


Copy and Set Styles

HI. I have two requests that are related to each other.
When I use "update face and view styles from template" only the currently used style is copied. Would it be possible to add an option to copy all the styles present in the template?
The second request concerns the possibility of setting a style when saving images of the pieces.
For example, when modeling the parts I use a gray background while when saving the images I set a style with a white background.
If it were possible to copy all the styles and set a style when saving it would be a nice progress in my opinion.
Thanks anyway for the excellent work.

Those are great ideas.  They're on the list!  Thank you!

@farfilli couldn't I just adopt your technique from UpdateDrawingStylesFromTemplate to tackle this one?

I think there is an API to easily manage the styles, I will have a look and return it

@tempod I appreciate your great suggestions!  It should be working now.  If you can't compile from source, let me know and I'll zip up a pre-release for you.
@farfilli I copied your technique from UpdateDrawingStylesFromTemplate.  Much easier and better.  I didn't even have to touch your CopyProperties code.  Nice!

Closing as complete.

wow! thank you so much. unfortunately i dont know how to compile from source...

OK, no problem.  I've got one last issue to address, then am going to release it for beta test.  It should be ready in a week or two.  I'll let you know when it has posted and you can try it out then.

@tempod
I published the latest version of Housekeeper this morning.  Here are a couple of links to get you started:
Release Notes
Installation Instructions
Release Page
If you get a chance to try it out, I would welcome any feedback you may have.
Robert


Parse error messages, if any, constructing a useful error string to retu...

...rn

@cianclarke & @jasonmadigan thoughts on error strings being returned here? (see test/errors.js comment for sample messages)

Looks like a good list to me

thanks.
based off the rhc gem https://github.com/openshift/rhc/blob/552a5668e0f9ce1c7a870534aed066124d6e3f9d/lib/rhc/rest/client.rb#L735

Looks great, Dave! Cherry on top would be a README.md heading on errors with one simple example error-response, but no big deal if no time


Add An Organizer Summary Email

Fixes #192, I feel like the copy is missing something...

Sounds like a plan!
From Sam
On Tue, Aug 22, 2023 at 1:17 AM Gary Tou @.***> wrote:

I'll review this tmrw! I can retroactively send these organizer summaries
after the first digest batch is sent
—
Reply to this email directly, view it on GitHub
https://github.com/hackclub/hackathons-backend/pull/194#issuecomment-1687702712,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJP3VREDTCKGUDDKAUYSONTXWRTKBANCNFSM6AAAAAA3ZQD7HA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Was that a rhyme? 😆

didn't intend it but sure... that's my email signature for primary school lol

@garyhtou thanks for the review! hopefully I understood you correctly here, just pushed the restructure


Fix typo in index.md

What I did

Fixed Typo I found here: https://rocket.modern-web.dev/guides/

No changeset should need to be included in this PR

with the "new" version of Rocket using its own @rocket/engine this is probably no longer applicable.
If it still is then feel free to reopen or creating an issue 🤗


Refactor: Poll price feeds registered within WitnetPriceRouter contract

And enabled within new external JSON configuration file.

Scheduled timeout when dry running data requests is not working properly, due to Python's known issues:

https://bugs.python.org/issue31935
https://bugs.python.org/issue30154

To avoid piping the STDOUT from the subprocess, a file descriptor can be used instead. Apparently, this seems to workaround the issue. See https://github.com/witnet/price_feed_poller/pull/32/commits/9979530df57761e9d7425f31740f4609456ff467.


App crash in iOS 8.1

Xcode 9.1
XLPagerTabStrip 8.0, build with Carthage
Simulator: iPhone 4s with iOS 8.1
Console output:

2017-11-19 23:35:21.452 applicationName[87544:882431] Warning once only: Detected a case where constraints ambiguously suggest a height of zero for a tableview cell's content view. We're considering the collapse unintentional and using standard height instead.

And in
File name: PagerTabStripViewController.swift
Line: 105 reloadViewControllers()

Thread 1: Fatal error: viewControllers(for:) should provide at least one child view controller

Other simulator just work fine.

Change sequence of setup tab bar to br more priority and it is work

Answer is not clear, please provide more details.


[DO NOT MERGE] Add feedback component

This PR has been superseded by https://github.com/alphagov/govuk_publishing_components/pull/163

Build the new feedback form to go at the foot of all GOV.UK pages. This is based on the code from the Service Manual but with some changes, as this version requires additional functionality.
Ultimately this component will be moved to the publishing components gem, but I started building it in static so getting it reviewed here because the commit history might prove useful to that.
Initial state:

Users have three options:

click 'yes' (page is useful) records a GA event and shows a 'thanks for your feedback' message
click 'no' (page is not useful) opens a form to take an email address to send a link to a survey to. This is a rework of the form that currently appears underneath the header of GOV.UK for some users at some times (you can trigger this by visiting GOV.UK and running GOVUK.userSurveys.displaySurvey(GOVUK.userSurveys.defaultSurvey) in the browser console)
click 'is there anything wrong with this page?' opens a feedback form. This is a rework of the existing feedback form at the foot of GOV.UK

Result of option 1 (and the others, if submitted successfully):

'Page is not useful' form:

'Something wrong with page' form:

If javascript is disabled, this form should be the only element that appears, and should still function.

Trello card
Component guide

The position of "Don’t have an email" link (https://user-images.githubusercontent.com/861310/35866363-ec492160-0b4e-11e8-8a2e-557e5ab9b61a.png) should be near to the form field it’s associated with rather than the submit button. I'm also not sure that we should be floating links next to buttons.

click 'is there anything wrong with this page?' opens a feedback form. This is a rework of the existing feedback form at the foot of GOV.UK

Can you indicate the need to update the existing form fields?

I've spoken to Lee about the above and the copy/fields for the feedback part should probably remain identical to what's live, but he needs to confirm with Imeh.

This component has now been moved to the components gem and a new PR created - https://github.com/alphagov/govuk_publishing_components/pull/163


Kaycee Beta Support

I think an easy way to allow adding cards to the game for kaycee mod would be to make a hotkey for card creation maybe home key? Also please remove all leshy noises.

Kaycee's Mod support is being worked on.
I will consider adding a keybind, but the current process of entering the card creator is already quite fast.
I won't be removing Leshy noises as that's not this mod's responsibility.

Added v1.2.0 (and only 1.2.0) to support Kaycee's Mod.
Keybinds might be added in the planned 2.0 rewrite.


Where's the option for fallback function?

Which fallback function are you referring to? Do you mean callback functions?
https://github.com/sony/gobreaker/blob/master/gobreaker.go#L106-L107

Hi, @YoshiyukiMineo ,
in hystrix pattern, an optional fallback function is used when the original func failed. Here's the wiki.

I didn't see fallback specifically in the example, but cb.Execute returns a specific error immediately if the request is not going to be allowed (this is documented). It looks like you can check for gobreaker.ErrOpenState to trigger fallback logic. Something like:
mySuccessReturn, err := cb.Execute(func() (interface{}, error) {
    // do stuff
})
if err != nil {
    if errors.Is(err, gobreaker.ErrOpenState) {
        // circuit is open
        // this is where a fallback option happens
    } else { // this will be the returned error from "do stuff"
    }
}

@timjonesdev what you suggested to implement the circuit breaker default fallback is good as it's true. However, if there's a default function passed with the setting struct it will be more easy to point, simple to change without touch the actual implementation, and descriptive for each service.

@ahmedashraff hello, i think we can customize trigger conditions by replacing cb.afterRequest(generation, err != nil) with cb.afterRequest(generation, cb.shouldChangeState(err)) like this:
type CircuitBreaker struct {
    ...
   shouldChangeState func(err error) bool
}

func defaultShouldChange(err error) bool {
    if err != nil {
        return true
    }
  return false
}

func (cb *CircuitBreaker) Execute(req func() (interface{}, error)) (interface{}, error) {
        ...
	result, err := req()
	cb.afterRequest(generation, cb.shouldChangeState(err))
	return result, err
}


Remove figma ds

Working on replacing components from react-figma-plugin-ds with components in the package

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 75.862%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
430

Relevant Lines:
546

💛  - Coveralls


Always detecting multiple definitions of symbol when peek (Alt+F12) or goto defintions (F12)

Issue Type: Bug
Defined functions as below,
file1.js
exports.Fn1=async function(){

}
exports.Fn2=async function(){

}
exports.Fn3=async function(){

}

calling functions in another file
file2.js
var file1=require("./file1");
file1.Fn2();

Actual: When trying to goto/peek definition of Fn2 from file2.js, VS code shows two definitions (Note we defined only one definition in the symbol).
Expected: When peek/goto symbols, VS Code should goto symbol directly if only one definitions exist. And display the number of definitions in case of multiple.
Before some release back (dont remember the exact version), this was working as expected.
VS Code version: Code 1.39.2 (6ab598523be7a800d7f3eb4d92d7ab9a66069390, 2019-10-15T15:35:18.241Z)
OS version: Windows_NT x64 10.0.16299

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz (4 x 2808)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.83GB (8.52GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none

Duplicate of https://github.com/microsoft/TypeScript/issues/33520


Adding custom TaskList tags

Hello, I have a question. Would it be possible for me to add custom TaskList tags to the highlighter using diffent styles? Thanks.

see prefix manager.cs last line for the words


[Bug]: Personal spatial database change execution failed

ODC version
odc424
OB version

What happened?

What did you expect to happen?
Execution succeeded
How can we reproduce it (as minimally and precisely as possible)?
Personal space execution database changes
Anything else we need to know?
No response
Cloud
No response

pass


Fix/keep alive

@AnonymousBit0111 did the work, just reverting a commit so that this can get merged.

This closes #117


Custom exceptions

Hi,
I'm looking for a way to raise custom exceptions per assertion..
Looking at the code, it currently seems only possible to override Assert::reportInvalidArgument for all assertions..
The only way I see around this is to add an optional argument to every assertion, allowing to pass a custom exception class.. Would you be open for a PR to support this? Or do you see another way to achieve what I'm after?

Currently the way to do this in this library is to overwrite the reportInvalidArgument method as you mentioned.
I'm not 100% sure about adding a new optional argument. I'm not sure if that would be a BC break or not, as that may break users who extend the Assert class and who overwrite some methods.
Depending on the implementation we could work out something.

@tvdijen what would be the use case for custom exceptions?

Well, to me InvalidArgumentException is just too generic.. I work on a library that processes complex XML structures and sometimes an assertion failing means something like 'Protocol violation' (i.e. a missing element) and sometimes it means 'Value is not a valid emailaddress'.. Sometimes we can recover from it and sometimes we can't, but right now I have no way of distinguishing certain types of exceptions, other than catching them all and test exception messages..

But in this case wouldn't more custom validation oriented checks be more appropriate? This library goal was to enable to add guards for things the PHP type system cannot catch. Those guards are the last line of defence that should never be reached.
This is also why it's throwing InvalidArgumentException which derivates from LogicException and not RuntimeException

I see your point, but I think you're missing mine..
This library could work well for both purposes.. Why not use it to cover the business logic checks and replace them with a one-liner as well?

Because usually when you start dealing with validation (your case) instead of assertions, you start to have:

laziness (you prefer to provide a maximum of validation errors at once not a fail fast)
validation error formatting
validation error translation

And suddenly it's a lot more complex.
Another reason is because Assert is a static stateless utility. As soon as you open reportInvalidArgument it no longer is: you have global configuration state. Which also means while you can customize your exception, you don't get to pick where exactly, it's gonna be done globally.
That said: I'm not saying it should be done. I simply want to make clear what it entails, the limitations and the drawbacks and try to see where the line should be drawn.
Actually counter point: isn't it already doable? https://3v4l.org/JVap6
So you can have your "domain/validation assertions" whilst the rest of the application can have regular assertions

I was trying to avoid what you're suggesting, because it means that for every custom exception I would have to create a class extending Assert... But I guess it is what it is and I'll go with that!

Those guards are the last line of defence that should never be reached.

I agree with that. But when they are reached how is it an InvalidArgumentException?

It's by design: this assert library is here to compensate the typesystem gaps not provide a domain validation.
But as pointed out in https://github.com/webmozart/assert/issues/177#issuecomment-599469858, you can if you desire adapt it.

That's not how the original beberlei-lib was designed

But this is not the beberlei lib... One example is the lack of laziness support.
In any case: I already provided an example on how to extend it with minimal efforts. Isn't it [the extension point] good enough for your use case?

Let's not start over the entire discussion...
It's a horrible design choice and I'm glad to see I'm not alone.

You are free to abstain from commenting if it's to throw degrading comments without any form of constructive argumentation 🙄

@githoober We've created a wrapper for this, should you need this in the mean time;  https://github.com/simplesamlphp/assert


[node-sdk] Missing @opentelemetry/exporter-jaeger raises an error on Next.js app

What happened?
Steps to Reproduce
Create a basic Next.js app and follow the steps to manually add OpenTelemetry to the application.
Use the OpenTelemetry setup code below. Don't set any environment variables, so that a ConsoleSpanExporter gets configured.
Start the dev server (npm run dev) and launch the app.
Expected Result
I see the default OpenTelemetry spans from my request in the console.
Actual Result
I get an error message from a failed import: Can't resolve '@opentelemetry/exporter-jaeger'. See the full trace below.
Additional Details
It looks like node-sdk imports TracerProviderWithEnvExporters. As a side effect of which, a Map of registered providers is built that assumes Jaeger is available and throws an error if it isn't. Since the dependency was removed in v0.44, the error gets thrown.
Edit:
Note that I'm not using Jaeger. ~I'll add the dependency to solve the error, but I would rather not have to include it at all.~ I can't include @opentelemetry/exporter-jaeger in my project because #3759 happens.
OpenTelemetry Setup Code
//instrumentation.ts
import { settings } from '@/config'
import { Span, SpanOptions, SpanStatusCode, trace } from '@opentelemetry/api'

export const tracer = trace.getTracer(settings.SERVICE_NAME)

export async function register() {
  if (settings.DISABLE_OTEL) {
    console.info('OpenTelemetry is disabled')
    return
  }

  if (process.env.NEXT_RUNTIME === 'nodejs') {
    await import('./instrumentation.node.ts')
  }
}

//instrumentation.node.ts

import { settings } from '@/config'
import * as grpc from '@grpc/grpc-js'
import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-grpc'
import { Resource } from '@opentelemetry/resources'
import { NodeSDK } from '@opentelemetry/sdk-node'
import {
  BatchSpanProcessor,
  ConsoleSpanExporter,
  SimpleSpanProcessor
} from '@opentelemetry/sdk-trace-node'
import { SemanticResourceAttributes } from '@opentelemetry/semantic-conventions'

function getProcessor() {
  if (settings.HONEYCOMB_API_KEY) {
    const metadata = new grpc.Metadata()
    metadata.set('x-honeycomb-team', settings.HONEYCOMB_API_KEY)

    const exporter = new OTLPTraceExporter({
      url: 'grpc://api.honeycomb.io:443/',
      credentials: grpc.credentials.createSsl(),
      metadata
    })

    // Values from https://github.com/honeycombio/intro-to-o11y-nodejs/blob/main/src/tracing.js
    return new BatchSpanProcessor(exporter, {
      maxQueueSize: 16000,
      maxExportBatchSize: 1000,
      scheduledDelayMillis: 500
    })
  }

  console.info('Using console exporter')
  return new SimpleSpanProcessor(new ConsoleSpanExporter())
}

const sdk = new NodeSDK({
  resource: new Resource({
    [SemanticResourceAttributes.SERVICE_NAME]: settings.SERVICE_NAME,
    [SemanticResourceAttributes.SERVICE_NAMESPACE]: settings.PROJECT_NAME,
    [SemanticResourceAttributes.SERVICE_VERSION]:
      settings.VERCEL_GIT_COMMIT_SHA,
    [SemanticResourceAttributes.DEPLOYMENT_ENVIRONMENT]: settings.VERCEL_ENV
  }),
  spanProcessor: getProcessor()
})

sdk.start()

package.json
{
  "name": "my-app",
  "version": "0.1.0",
  "private": true,
  "type": "module",
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint",
    "format": "prettier --write ."
  },
  "dependencies": {
    "next": "^14.0.2",
    "react": "^18.2.0",
    "@opentelemetry/api": "^1.7.0",
    "@opentelemetry/exporter-trace-otlp-grpc": "^0.45.1",
    "@opentelemetry/resources": "^1.18.1",
    "@opentelemetry/sdk-node": "^0.45.1",
    "@opentelemetry/sdk-trace-node": "^1.18.1",
    "@opentelemetry/semantic-conventions": "^1.18.1",
    "tailwind-merge": "^2.0.0",
    "tailwindcss": "^3.3.5",
    "tailwindcss-animate": "^1.0.7",
  },
  "devDependencies": {
    "@ianvs/prettier-plugin-sort-imports": "^4.1.1",
    "@tailwindcss/typography": "^0.5.10",
    "@types/node": "^20.9.0",
    "@types/react": "^18.2.37",
    "@types/react-dom": "^18.2.15",
    "@types/ws": "^8.5.9",
    "autoprefixer": "^10.4.16",
    "dotenv": "^16.3.1",
    "dotenv-cli": "^7.3.0",
    "eslint": "^8.53.0",
    "eslint-config-next": "^14.0.2",
    "eslint-config-prettier": "^9.0.0",
    "eslint-plugin-tailwindcss": "^3.13.0",
    "postcss": "^8.4.30",
    "prettier": "^3.1.0",
    "prettier-plugin-tailwindcss": "^0.5.7",
    "ts-node": "^10.9.1",
    "typescript": "^5.2.2"
  },
  "postcss": {
    "plugins": {
      "tailwindcss": {},
      "autoprefixer": {}
    }
  }
}

Relevant log output
<EMAIL_ADDRESS>Module not found: Can't resolve '@opentelemetry/exporter-jaeger' in '/Users/julien/projects/my-app/node_modules/@opentelemetry/sdk-node/build/src'

Import trace for requested module:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>./src/instrumentation.node.ts
./src/instrumentation.ts
./src/services/dataset.ts
./src/app/datasets/page.tsx

Encountering the same issue with next.js app.
As far as I understand https://github.com/open-telemetry/opentelemetry-js/pull/4214 was supposed to fix this, but we still have the issue.
 "@opentelemetry/api": "^1.7.0",
    "@opentelemetry/exporter-metrics-otlp-http": "^0.47.0",
    "@opentelemetry/exporter-trace-otlp-http": "^0.47.0",
    "@opentelemetry/instrumentation-http": "^0.47.0",
    "@opentelemetry/resources": "^1.20.0",
    "@opentelemetry/sdk-metrics": "^1.20.0",
    "@opentelemetry/sdk-node": "^0.47.0",
    "@opentelemetry/sdk-trace-node": "^1.20.0",
    "@opentelemetry/semantic-conventions": "^1.20.0",

Import trace for requested module:
../../node_modules/.pnpm/@opentelemetry+sdk-node@0.47.0_@opentelemetry+api<EMAIL_ADDRESS>../../node_modules/.pnpm/@opentelemetry+sdk-node@0.47.0_@opentelemetry+api<EMAIL_ADDRESS>../../node_modules/.pnpm/@opentelemetry+sdk-node@0.47.0_@opentelemetry+api<EMAIL_ADDRESS> ⚠ ../../node_modules/.pnpm/@opentelemetry+sdk-node@0.47.0_@opentelemetry+api<EMAIL_ADDRESS>Module not found: Can't resolve '@opentelemetry/exporter-jaeger' in 'C:\Users\macie\Documents\src\sphere\node_modules\.pnpm\@opentelemetry+sdk-node@0.47.0_@opentelemetry+api@1.7.0\node_modules\@opentelemetry\sdk-node\build\src'

I am encountering this as well.  I think the core issue is that the attempt to lazy load exporter-jaeger doesn't work because Nextjs is trying to bundle the library via webpack.  So it searches out the dynamic require() calls and can't find the module.  If I manually add exporter-jaeger, I get back to the original problem list in #4214 . I also tried fixing ansi-color (which is the offending module in #4214) but that still yields wanrings due to other dynamic imports. I think testing this library against webpack will be necessary in order for it to work properly with Nextjs.

UPDATE: I was able to work around these issues for my server components in nextjs by adding this to my nextjs.config.js file:
experimental: {
serverComponentsExternalPackages: ['@acme/package'],
},
In my case, all of the OpenTelemetry stuff was already isolated in an NPM package, so I just added that to the stanza above.  If you are directly importing the OTel libraries, you may need to specify multiple modules here.  My understanding is that this directive tells Next not to bundle the given library, avoiding webpack and avoiding all of the errors from dynamic loading.

Encountering the same issue with next.js app. As far as I understand #4214 was supposed to fix this, but we still have the issue.
 "@opentelemetry/api": "^1.7.0",
    "@opentelemetry/exporter-metrics-otlp-http": "^0.47.0",
    "@opentelemetry/exporter-trace-otlp-http": "^0.47.0",
    "@opentelemetry/instrumentation-http": "^0.47.0",
    "@opentelemetry/resources": "^1.20.0",
    "@opentelemetry/sdk-metrics": "^1.20.0",
    "@opentelemetry/sdk-node": "^0.47.0",
    "@opentelemetry/sdk-trace-node": "^1.20.0",
    "@opentelemetry/semantic-conventions": "^1.20.0",

Import trace for requested module:
../../node_modules/.pnpm/@opentelemetry+sdk-node@0.47.0_@opentelemetry+api<EMAIL_ADDRESS>../../node_modules/.pnpm/@opentelemetry+sdk-node@0.47.0_@opentelemetry+api<EMAIL_ADDRESS>../../node_modules/.pnpm/@opentelemetry+sdk-node@0.47.0_@opentelemetry+api<EMAIL_ADDRESS> ⚠ ../../node_modules/.pnpm/@opentelemetry+sdk-node@0.47.0_@opentelemetry+api<EMAIL_ADDRESS>Module not found: Can't resolve '@opentelemetry/exporter-jaeger' in 'C:\Users\macie\Documents\src\sphere\node_modules\.pnpm\@opentelemetry+sdk-node@0.47.0_@opentelemetry+api@1.7.0\node_modules\@opentelemetry\sdk-node\build\src'

I forgot to update:
I managed to fix this issue by... actually following docs.
https://nextjs.org/docs/app/building-your-application/optimizing/open-telemetry
This part is really important:
Now you can initialize NodeSDK in your instrumentation.ts. Unlike @vercel/otel, NodeSDK is not compatible with edge runtime, so you need to make sure that you are importing them only when process.env.NEXT_RUNTIME === 'nodejs'.

What happened on my side is that I've put register function in a condition based on NEXT_RUNTIME and one other var we care about but... not the import. It's actually important to import conditionally as well, as some OTel stuff will initialize in the background the moment it's require'd, We've moved our OTel registration stuff to a separate file that we import conditionally based on runtime and it works fine now. Spans from next.js are really weird and I'm to this day not sure if I can get any useful info from them on my own but it does work.

I tried @djboulia's approach, but it didn't work for me, unfortunately. However, since I submitted this issue, Vercel has updated their @vercel/otel library to allow for more configuration. This is what I needed to configure a Honeycomb.io exporter.
So I ended up with an hybrid of @lewinskimaciej's solution and Next's automated setup.
It looks something like this:
In instrumentation.ts:
import { settings } from '@/config'
import { SemanticResourceAttributes } from '@opentelemetry/semantic-conventions'
import { registerOTel } from '@vercel/otel'

export async function register() {
  if (settings.DISABLE_OTEL) {
    console.info('OpenTelemetry is disabled')
    return
  }

  if (process.env.NEXT_RUNTIME === 'nodejs') {
    const { getProcessor } = await import('./instrumentation.node')
    registerOTel({
      serviceName: settings.SERVICE_NAME,
      attributes: {
        [SemanticResourceAttributes.SERVICE_NAMESPACE]: settings.PROJECT_NAME
      },
      spanProcessors: [getProcessor()]
    })
  }
}

And in instrumentation.node.ts:
import { settings } from '@/config'
import * as grpc from '@grpc/grpc-js'
import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-grpc'
import {
  BatchSpanProcessor,
  ConsoleSpanExporter,
  SimpleSpanProcessor,
  type SpanProcessor
} from '@opentelemetry/sdk-trace-base'

export function getProcessor(): SpanProcessor {
  if (settings.HONEYCOMB_API_KEY) {
    const metadata = new grpc.Metadata()
    metadata.set('x-honeycomb-team', settings.HONEYCOMB_API_KEY)

    const exporter = new OTLPTraceExporter({
      url: 'grpc://api.honeycomb.io:443/',
      credentials: grpc.credentials.createSsl(),
      metadata
    })

    // Values from https://github.com/honeycombio/intro-to-o11y-nodejs/blob/main/src/tracing.js
    return new BatchSpanProcessor(exporter, {
      maxQueueSize: 16000,
      maxExportBatchSize: 1000,
      scheduledDelayMillis: 500
    })
  }

  console.info('Using console exporter')
  return new SimpleSpanProcessor(new ConsoleSpanExporter())
}

I still need to Node-only conditional import, because grpcneeds Node API that are missing on the edge platform.
Hope that can help folks navigate this issue.

This saved me! Thank you so much 🚀

i found alternative solution, you might find it useful -
const nextConfig = {   experimental: {     instrumentationHook: true,   },   webpack: (config, options) => {     return {       ...config,       resolve: {         ...config.resolve,         fallback: {           ...config.resolve.fallback,           stream: false,           zlib: false,           http: false,           tls: false,           net: false,           http2: false,           dns: false,           os: false,           fs: false,           path: false,           https: false,         },       },     };   }, };

I tried @djboulia's approach, but it didn't work for me, unfortunately. However, since I submitted this issue, Vercel has updated their @vercel/otel library to allow for more configuration. This is what I needed to configure a Honeycomb.io exporter.
So I ended up with an hybrid of @lewinskimaciej's solution and Next's automated setup.
It looks something like this:
In instrumentation.ts:
import { settings } from '@/config'
import { SemanticResourceAttributes } from '@opentelemetry/semantic-conventions'
import { registerOTel } from '@vercel/otel'

export async function register() {
  if (settings.DISABLE_OTEL) {
    console.info('OpenTelemetry is disabled')
    return
  }

  if (process.env.NEXT_RUNTIME === 'nodejs') {
    const { getProcessor } = await import('./instrumentation.node')
    registerOTel({
      serviceName: settings.SERVICE_NAME,
      attributes: {
        [SemanticResourceAttributes.SERVICE_NAMESPACE]: settings.PROJECT_NAME
      },
      spanProcessors: [getProcessor()]
    })
  }
}

And in instrumentation.node.ts:
import { settings } from '@/config'
import * as grpc from '@grpc/grpc-js'
import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-grpc'
import {
  BatchSpanProcessor,
  ConsoleSpanExporter,
  SimpleSpanProcessor,
  type SpanProcessor
} from '@opentelemetry/sdk-trace-base'

export function getProcessor(): SpanProcessor {
  if (settings.HONEYCOMB_API_KEY) {
    const metadata = new grpc.Metadata()
    metadata.set('x-honeycomb-team', settings.HONEYCOMB_API_KEY)

    const exporter = new OTLPTraceExporter({
      url: 'grpc://api.honeycomb.io:443/',
      credentials: grpc.credentials.createSsl(),
      metadata
    })

    // Values from https://github.com/honeycombio/intro-to-o11y-nodejs/blob/main/src/tracing.js
    return new BatchSpanProcessor(exporter, {
      maxQueueSize: 16000,
      maxExportBatchSize: 1000,
      scheduledDelayMillis: 500
    })
  }

  console.info('Using console exporter')
  return new SimpleSpanProcessor(new ConsoleSpanExporter())
}

I still need to Node-only conditional import, because grpcneeds Node API that are missing on the edge platform.
Hope that can help folks navigate this issue.

I'm not using vercel otel configuration but manual config. Is there a fix for this?

Solution for me was to add sdk initialization with the condition, inside register function

What does your opentelemetry file look like?

This is how I fixed it. I just had to prevent auto-instrumentation and sdk-node from server components.
/** @type {import("next").NextConfig} */
const config = {
 reactStrictMode: true,
 experimental: {
   instrumentationHook: true,
   serverComponentsExternalPackages: [
     "@opentelemetry/auto-instrumentations-node",
     "@opentelemetry/sdk-node",
   ],
 },
}

This is how I fixed it. I just had to prevent auto-instrumentation and sdk-node from server components.
/** @type {import("next").NextConfig} */
const config = {
 reactStrictMode: true,
 experimental: {
   instrumentationHook: true,
   serverComponentsExternalPackages: [
     "@opentelemetry/auto-instrumentations-node",
     "@opentelemetry/sdk-node",
   ],
 },
}

The experimental.serverComponentsExternalPackages has been deprecated and replaced by:
https://nextjs.org/docs/app/api-reference/next-config-js/serverExternalPackages

@shawnmclean This is in my array, it's working now in Next.js 15.
serverExternalPackages: [
'@azure/monitor-opentelemetry',
'@azure/opentelemetry-instumentation-azure-sdk',
'@opentelemetry/auto-instrumentations-node',
'@opentelemetry/sdk-node',
'@opentelemetry/instrumentation',
'@opentelemetry/api',
'@opentelemetry/exporter-jaeger',
],


Add dependabot.yml for version updates

What
Adding base config for dependabot.yml, which enables automatic PRs for dependency version updates through Dependabot. This base config sets version updates to run on a weekly schedule, groups PRs for version updates according to major vs minor/patch updates, and sets max PRs that Dependabot can create for version updates  per package-ecosystem.
But if you would like, several config options can be added to dependabot.yml as per configuration-options-for-the-dependabot.yml-file to customize version updates, such as:

Group PRs for version updates by different criteria
Set dependency-type option in allow option to all for enabling version updates for both direct and indirect dependencies (as well as prod and dev dependencies). By default, PRs for only updating direct prod+dev dependencies versions are created.
Set reviewers for Dependabot version updates PRs
Etc.

Also, automatic PRs for security updates through Dependabot are already enabled through a global setting. PRs for security updates will be grouped as much as possible across directories and per ecosystem through the global setting (grouping-dependabot-security-updates). But dependabot.yml can also be used for more granular security updates settings in addition to version updates (some of the options in dependabot.yml are shared across security and version updates), such as:

Grouping security updates according to custom criteria: overriding-the-default-behavior-with-a-configuration-file
Only allowing automatic PRs for security updates for certain dependencies by configuring allow directive to a certain value such as production, development, direct, indirect. By default, security updates are applied to all dependencies (direct, indirect, production, development).
Etc.

Why
To enable using the latest package versions, and provide a way to customize Dependabot security updates PRs.
Known limitations
N/A

stellar-disbursement-platform-frontend-preview is available here:http://sdp-frontend-pr118.previews.kube001.services.stellar-ops.com/

stellar-disbursement-platform-frontend-preview is available here:http://sdp-frontend-pr118.previews.kube001.services.stellar-ops.com/


Build examples

It'd be good to build some solid examples of using the library.  Since we're fairly agnostic about the code a fixture runs, we can try out a few different kinds of fixtures:

[ ] Non database fixtures (ssh server/request bin?)
[ ] Direct sqlite access
[ ] Ecto.Fixtures
[ ] Ecto on it's own

Started the first work on an ecto sample here: https://github.com/obmarg/ex_unit_fixtures/tree/feature/ecto_sample


[REVIEW] Add DatetimeAccessor for datetimelike properties of the Series values.

Build will fail until updates from master are merged in.

Thanks @andersy005! A couple of small changes recommended. Also please merge from upstream/master

@andersy005 LGTM other than fixing some minor flake8 issues. Thanks!

@kkraus14, Just pushed changes that fix the flake8 issues.

Can one of the admins verify this patch?

add to whitelist


Not to escape debuggerPath of pipeTransport in launch.json

VSCode Version:
1.11.0-insider
OS Version:
RHEL 7.3

Steps to Reproduce:

Generate launch.json to set up remote debug configuration.

{
  "version": "0.2.0",
  "configurations": [
    {
        "name": ".NET Core Docker Remote Attach",
        "type": "coreclr",
        "request": "attach",
        "processId": "21",
        "pipeTransport": {
            "pipeProgram": "docler",
            "pipeArgs": [ "exec", "remotedebug-1-mispn"],
            "debuggerPath": "/opt/app-root/src/clrdbg/clrdbg",
            "pipeCwd": "${workspaceRoot}"
        },
        "sourceFileMap": {
            "/opt/app-root/src": "${workspaceRoot}"
        }
    }
  ]
}

Start debug ".NET Core Docker Remote Attach"

Failed to execute docker command. This is because VS Code escape the debuggerPath with parameters.

"docker" exec remotedebug-1-mispn "/opt/app-root/src/clrdbg/clrdbg --interpreter=mi"

The docker command recognizes "/opt/app-root/src/clrdbg/clrdbg --interpreter=mi" as one file path, then failed. I'm not sure which version, but the previous version (maybe 1.10.x-insider or 1.9.x-insider) VS Code didn't escape with option but not escaped like below.
"docker" exec remotedebug-1-mispn /opt/app-root/src/clrdbg/clrdbg --interpreter=mi

I submitted to StackOverflow as a question. But, I found this issue occurred with not only "oc (OpenShit CLI)" command but also "docker" command. So I decided to submit this issue as a bug.
http://stackoverflow.com/questions/42731558/how-not-to-escape-debuggerpath-of-pipetransport-in-launch-json
This issue prevents me from executing remote debug from VS Code to docker.

@tanaka-takayoshi please file .NET related issues against https://github.com/OmniSharp/omnisharp-vscode/issues

This issue was moved to OmniSharp/omnisharp-vscode#1318


Convert deps to Go modules, add BitBox02 dependency for the HSM

I skipped go mod vendor for now, which means that all go build, go test etc. automatically fetch the deps from a cache proxy based on the go.sum file.
We can add vendoring back later if desired.

Thank you for doing this :+1:. Looks good to me and make ci runs fine locally.
IMO @Stadicus should give it a try as well to make sure everything is setup correctly for him to build mender images.

Looks good to me and make ci runs fine locally.

make ci is not run by Travis because assembling the image takes too long? Maybe Travis could still build and tests the Go code and potentially other things which are not heavy.

make ci is not run by Travis because assembling the image takes too long? Maybe Travis could still build and tests the Go code and potentially other things which are not heavy.

Which is what we do: https://travis-ci.org/digitalbitbox/bitbox-base/builds/607586093?utm_source=github_status&utm_medium=notification

IMO @Stadicus should give it a try as well to make sure everything is setup correctly for him to build mender images.

Will try do build the Go tools as usual using make docker-build-go, but there are no direct dependencies from within building the image (just the binaries must be available at ./bin/go/)

Command make docker-build-go works without any issues, but I did not test the resulting binaries.

Can you rebase?

I merged now, trusting the two approvals means you tested running the middleware :smile:


⚠ GitHub has degraded performance

In 24a300a, GitHub (https://www.githubstatus.com/api/v2/status.json) experienced degraded performance:

HTTP code: 200
Response time: 126 ms

Resolved: GitHub performance has improved in d8747e9 after 8 minutes.


demos: 0.7.8-1 in 'dashing/distribution.yaml' [bloom]

Increasing version of package(s) in repository demos to 0.7.8-1:

upstream repository: https://github.com/ros2/demos.git
release repository: https://github.com/ros2-gbp/demos-release.git
distro file: dashing/distribution.yaml
bloom version: 0.8.0
previous version for package: 0.7.7-1

The travis CI build actually passed, but isn't updating here.  I'm going to close and reopen to rekick it.


[KOGITO-4554] Error boundary event implementation

This includes the missing Boundary Error Event implementation in Kogito.
The processes used to test and included in the integration tests module in codegen were:

Boundary Error on Task

Boundary Error on Sub-Process

Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[ ] You have read the contributors guide
[ ] Your code is properly formatted according to this configuration
[ ] Pull Request title is properly formatted: KOGITO-XYZ Subject
[ ] Pull Request title contains the target branch if not targeting master: [0.9.x] KOGITO-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

How to retest this PR or trigger a specific build:

Pull Request
Please add comment: Jenkins retest this

Quarkus LTS checks
Please add comment: Jenkins run LTS

Native checks
Please add comment: Jenkins run native

Full Kogito testing (with cloud images and operator BDD testing)
Please add comment: Jenkins run BDD
This check should be used only if a big change is done as it takes time to run, need resources and one full BDD tests check can be done at a time ...

The Linux check has failed. Please check the logs.

jenkins retest this

The Linux check has failed. Please check the logs.

jenkins retest this

The Linux check is successful.

jenkins retest this

The (build) Optaplanner check is successful.

The (build) Apps check is successful.

The (build) Runtimes check is successful.

The (build) Examples check is successful.

@cristianonicolai sonar is happy now.
@MarianMacik would you like to take a look at this one or are we ok to merge?
Thanks

@tiagodolphine Looking into it.

The (build) Apps check is successful.

The (build) Optaplanner check is successful.

The (build) Runtimes check has failed. Please check the logs.

jenkins retest this

The (build) Examples check is successful.

The (build) Optaplanner check is successful.

The (build) Runtimes check has failed. Please check the logs.

The (build) Apps check has failed. Please check the logs.

The (build) Examples check is successful.

Jenkins rerun apps tests

Jenkins rerun runtimes tests

The (build) Runtimes check has failed. Please check the logs.

The (build) Apps check is successful.

Jenkins rerun runtimes tests

The (build) Runtimes check has failed. Please check the logs.

Jenkins rerun runtimes tests

The (build) Runtimes check is successful.


Fix types on added matchers

Currently using a lot of any. These could be better.

This is internal to my project, not a brookjs issue.


Automatically set timezone?

The timezone in mobile app is set with setTimezone method as per wiki:

Android: https://github.com/snowplow/snowplow/wiki/Android-Tracker#315-set-timezone-with-settimezone
iOS: https://github.com/snowplow/snowplow/wiki/iOS-Tracker#36-set-timezone-with-settimezone

Should there be an option to set the timezone automatically?

In the Android tracker, this is already done(the device timezone is set as the default in the builder):
https://github.com/snowplow/snowplow-android-tracker/blob/master/snowplow-tracker/src/main/java/com/snowplowanalytics/snowplow/tracker/Subject.java#L85

Thanks for clarifying @mhadam! Closing


Locking: Multiple readers, single writer

Find how to do that in a reliable and efficient way...

for hdf5: https://portal.hdfgroup.org/display/HDF5/Single+Writer+Multiple+Reader++-+SWMR

Good news!
3 mars 2021 19:00:18 Evgeny Posenitskiy<EMAIL_ADDRESS>
for hdf5: https://portal.hdfgroup.org/display/HDF5/Single+Writer+Multiple+Reader++-+SWMR
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub[https://github.com/TREX-CoE/trexio/issues/19#issuecomment-789938871], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ABNRVYWFWTPHBB7UWQ4E6YTTBZ2KZANCNFSM4YRVOO2A].
[data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAFQAAABUCAYAAAAcaxDBAAAABHNCSVQICAgIfAhkiAAAADJJREFUeJztwQENAAAAwqD3T20ON6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB4NW6UAAFvMNJxAAAAAElFTkSuQmCC###24x24:true###][Image de pistage][https://github.com/notifications/beacon/ABNRVYWHUDX2UZDPR75GATLTBZ2KZA5CNFSM4YRVOO2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOF4KYFNY.gif]

For now I think the best solution for hdf5 is to introduce a new open mode (probably 's') that will act as 'w' but using the SWMR functionality which doesn't lock the file, thus allowing multiple readers to access it.

It is not yet clear to me if the SWMR mode should be the default or not. I have to think about it. Can we postpone a bit?


test(NODE-5929): convert txn legacy spec tests

Description
Node verification of https://github.com/mongodb/specifications/pull/1502
What is changing?
Syncs all the transaction unified tests, removes the legacy tests, fixes read preference issues and error message comparison issues in the unified runner.
Is there new documentation needed for these changes?
None
What is the motivation for this change?
NODE-3299/DRIVERS-1709

Double check the following

[x] Ran npm run check:lint script
[x] Self-review completed using the steps outlined here
[x] PR title follows the correct format: type(NODE-xxxx)[!]: description

Example: feat(NODE-1234)!: rewriting everything in coffeescript

[x] Changes are covered by tests
[x] New TODOs have a related JIRA ticket

Remaining random failures related to https://jira.mongodb.org/browse/DRIVERS-2816. Underneath the hood the extra command started events are from the txn aborting due to a migration conflict and then retrying.


Recommendations

This PR adds the ability to fetch a paged list of recommendations from a given media entry.
In addition, this addresses #7 due to not being able to run unit tests.
Please advise if I need to address anything.

Thanks for the new feature!

No problem. Any chance to get a release pushed?

I'll try to push a new release as soon as possible! Maybe I'll try to finish some todo items while I'm at it.

If you'd like, I can help out. I need the recommendation feature for something I'm working on this week, so anything I can do to help to speed up the release, I will.
I was planning to add AniList documentation to all the DTOs already, so let me take care of that one today.

Any help would be great!
I'll be pushing a new release on Friday. Any new feature/fixes made will be added to the new release.


Python 3.8 removed from latest ubuntu runners

Python 3.8 is not present on the latest runner images for ubuntu, as it is no longer actively maintained. Not only does this result in a need to pin to older runner images, but means the deployment workflow relies on a version of python which doesn't receive security updates anymore.
Unpinning to just use whatever python version is present on the runner image might be the cleanest solution here.

Thanks for the report, Matt - I believe to address this we'll need to publish a new dagster-cloud.pex on a more recent Python version - right now we only have published one for 3.8.

@benpankow is there any tentative timeline when this is gonna happen? We still need to use ubuntu-20.04.
I just tried with action v0.1.43 and failed with the same reason
/usr/bin/env: ‘python3.8’: No such file or directory


Write unittest to test method "ConsumerMdib.reload_all()"

Is there an existing issue for this?

[X] I have searched the existing issues

Feature idea
After a change of the Mdib SequenceId the "ConsumerMdib" (in consumermdib.py) will not update any received data.
An application using "class ConsumerMdib" has to call reload_all() to "reactivate" the processing of received reports.
reload_all() is not tested yet.
Write unittest to test reload_all after e.g. a SequenceId change. Verify that received reports are processed and other functionality is preserved (e.g. )
self._is_initialized == True
self._sequence_id_changed_flag == False
observable properties are working
MDIB version is as expected
Alternatives

Implementation idea
No response
Participation

[ ] I am willing to submit a pull request to implement this feature.

Link to the idea discussion
No response

After a change of the sequence id it is unclear if the provider stopped sending notifications. In the reload phase the consumer should check if the existing subscriptions are still alive by sending renew or getstatus reequests and subscribe again if neccessary.


Escaped "short" word and added ability to stop updatingRoute in beforeUpdateRoute

Closing this PR. We are that we want api for canceling the route change, but it's not that simple (we need to revert the $location), so here is an issue for that: #592

Currently in our project we are reverting location url in more less this way
this.$on("$beforeRouteChange", function(scope, next, current, stopCallback)
if(!current){
self.lastUrl = $location.url();
return;
}
if (next && userWantToGo()){
  self.lastUrl = null;
} else {
  stopCallback();
  $location.url(self.lastUrl);
}

});
It could be integrated inside $route service.

yep, the problem is, when route change is induced by outside change (browser's url change) - e.g. user has typed into address bar or clicked on link (in hashbang $location mode)...
We have to consider these cases as well...


fix typos in seq2seq tutorial document

Sequance -> Sequence
Seqeunce -> Sequence
Archtecture -> Architecture
reccurent -> recurrent
aditional -> additional
vacaburary -> vocabulary

Jenkins, test this please.

LGTM!


flatmap filter added

as requested at #14, this PR introduces the flatmap based filters so elements in collections can be manipulated just like any other element in a map

this completes the process started at https://github.com/devopsfaith/krakend/pull/230


expand default object case for lodestar-utils toJson and apply in gossip validation

resolves #1754 by expanding the default object case for the lodestar-utlis toJson and applying it in gossip validation

To address the issue https://github.com/ChainSafe/lodestar/issues/1754 I suggest you add test cases to the formating unit tests toJson and toString
https://github.com/ChainSafe/lodestar/blob/10e261546c4c054811e272ebcb12bf736ef627dd/packages/lodestar-utils/test/unit/json.test.ts#L10
With data like the gossip module sends to the logger
{code: "ERR_PARENT_UNKNOWN", parentRoot: fromHexString("0x111111111111111111111111111111111...")}


Add direct upload config flag for Google cloud storage, fixes #177.

use getBoolean is probably better.  But the current getBoolean takes in the default value, we kind of want all the default value to come in from the properties file (not through java code).  How about you provide a getBoolean which doesn't take in default value and then you can use this new getBoolean

@jgagnon1 @HenryCaiHaiying i specifically used the getString.equals("true") code because that is exactly how secor does it for getSeperateContainersForTopics() (secor.swift.containers.for.each.topic) and I wasn't sure if this is the recommended way. The other boolean setting i could find in this config is getAwsProxyEnabled() (which simply uses getBoolean), i used that first, but then found out the former (and again wasn't sure why these two different ways are both used).
@HenryCaiHaiying i'm a little perplexed by your comments:

there is getBoolean, not just on PropertiesConfiguration but on SecorConfig itself as well,
both has signatures for with and without default value,
i don't understand why would we want to not have a default (this setting should not be mandatory, it should be off by default, e.g. opt-in)

That all said i'm fine with changing to one of the getBoolean forms, implementing anything else (especially adding new functionality) please feel free to do yourself.

For the properties default, secor want to keep a convention that all properties are mandatory (needs to be specified in properties file, and with the default value provided in properties file), we don't want to keep the default logic in two places (in properties file and in java code since they might diverge as times goes on).  Have every property explicitly listed in property file would force the adopter to take a look and examine the impact of any new property.  But sometimes this convention is not strictly enforced, that's when you see some inconsistencies.
There is one SecorConfig.getBoolean() which calls underlying PropertiesConfiguration.getBoolean(), it currently asks for the default.  I think we should also have a form of getBoolean which does not ask for default (i.e. the property needs to be present in property file).  This new getBoolean(propertyName) method would just call the corresponding getBoolean(propertyName) in PropertiesConfiguraration.  And you can use the new getBoolean() method in your code.

@HenryCaiHaiying i don't understand. https://github.com/pinterest/secor/blob/master/src/main/java/com/pinterest/secor/common/SecorConfig.java#L407 vs https://github.com/pinterest/secor/blob/master/src/main/java/com/pinterest/secor/common/SecorConfig.java#L411. am i missing something here?

@HenryCaiHaiying ok i'll use that method and amend my commit. not sure if you saw but i only added the config/setting to src/main/config/secor.dev.gs.properties, should i add it somewhere else? i checked secor.common.properties but i only saw mandatory GS settings there (e.g. secor.gs.credentials.path is only present in secor.dev.gs.properties, not really sure).

Didn't realize they used a separate properties file, we should just use one
properties file: secor.common.properties, that's the one used for
production environment.
On Sat, Feb 20, 2016 at 11:35 AM, eLod<EMAIL_ADDRESS>wrote:

@HenryCaiHaiying https://github.com/HenryCaiHaiying ok i'll use that
method and amend my commit. not sure if you saw but i only added the
config/setting to src/main/config/secor.dev.gs.properties, should i add
it somewhere else? i checked secor.common.properties but i only saw
mandatory GS settings there (e.g. secor.gs.credentials.path is only
present in secor.dev.gs.properties, not really sure).
—
Reply to this email directly or view it on GitHub
https://github.com/pinterest/secor/pull/183#issuecomment-186669383.

@HenryCaiHaiying ping (sry, but not sure if github is notifying you if i update commit)

LGTM

@eLod looks good to me, thanks for the contributions.
P.S.  The github actually didn't notify me your new update to the change, feel free to ping me if you don't get response.


⚠ Roblox TextFilter Api has degraded performance

In a681aa5, Roblox TextFilter Api (https://textfilter.roblox.com) experienced degraded performance:

HTTP code: 200
Response time: 2346 ms

Resolved: Roblox TextFilter Api performance has improved in eb9e483.


exactVersion property missing from az vm show output

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
exactVersion property not returned by "az vm show"
To Reproduce
Steps to reproduce the behavior.
az vm show -g ubuntu -n ubuntu --query storageProfile.imageReference
{
"id": null,
"offer": "UbuntuServer",
"publisher": "Canonical",
"sku": "16.04-LTS",
"version": "latest"
}
Expected behavior
The exactVersion property was added in API version 2019-07-01, so CLI should return it too.
Use Try It and change API version to 2019-07-01 - https://docs.microsoft.com/en-us/rest/api/compute/virtualmachines/get
"storageProfile": {
  "imageReference": {
    "publisher": "Canonical",
    "offer": "UbuntuServer",
    "sku": "16.04-LTS",
    "version": "latest",
    "exactVersion": "16.04.201909091"
  },

Environment summary
azure-cli 2.0.75
Additional context
Add any other context about the problem here.

We have received your feedback. We'll investigate it.

The definition of ImageReference has no exactVersion. So even the response has exactVersion, the model we build cannot have exactVersion field. Added a service attention to try to make it consistent.
https://github.com/Azure/azure-rest-api-specs/blob/master/specification/compute/resource-manager/Microsoft.Compute/stable/2019-07-01/compute.json
"ImageReference": {
      "properties": {
        "publisher": {
          "type": "string",
          "description": "The image publisher."
        },
        "offer": {
          "type": "string",
          "description": "Specifies the offer of the platform image or marketplace image used to create the virtual machine."
        },
        "sku": {
          "type": "string",
          "description": "The image SKU."
        },
        "version": {
          "type": "string",
          "description": "Specifies the version of the platform image or marketplace image used to create the virtual machine. The allowed formats are Major.Minor.Build or 'latest'. Major, Minor, and Build are decimal numbers. Specify 'latest' to use the latest version of an image available at deploy time. Even if you use 'latest', the VM image will not automatically update after deploy time even if a new version becomes available."
        }
      },
      "allOf": [
        {
          "$ref": "#/definitions/SubResource"
        }
      ],
      "description": "Specifies information about the image to use. You can specify information about platform images, marketplace images, or virtual machine images. This element is required when you want to use a platform image, marketplace image, or virtual machine image, but is not used in other creation operations."
    },

It looks like the the API spec has been updated. So this should be available in an upcoming release of the CLI: https://github.com/Azure/azure-rest-api-specs/blob/master/specification/compute/resource-manager/Microsoft.Compute/stable/2019-07-01/compute.json

This issue is fixed. Download the latest Azure CLI and have a try!


Web upload DnD: Unclear how to cancel

Testing #97714
When uploading a very large directory, it would be helpful to have a way to cancel the operation. I'd expect a notification progress indicator with a cancel button or a cancel option onclick of the statusbar indicator.

You click on the status bar entry to see a notification that has the "Cancel" button. Did you try that?

Oh, seems like that only works on chromium. On Safari clicking the status bar doesn't seem to do anything.

Ok, thanks. Safari is currently not supported.


Minimum supported Django version

The documentation for the Django integration says the minimum version required is 1.6, and tox.ini and various bits of the code apparently agree. But setup.py says the minimum version is 1.8, if you use the Django extra. I guess setup.py should be fixed to match what's actually being tested, right? It looks like it's been wrong ever since the extra was added.
I saw there's discussion about dropping support for these ancient versions, which is fair. It would be nice to get a release out with this dependency corrected first though, so dependency resolvers can pick a correct version of sentry-sdk to match whatever version of Django somebody is actually using.
I'm currently working through the upgrade path for an old project. When (not if) I screw that up and visitors hit bugs, I want Sentry to give me as much information as it can. So I want to get new Sentry bits as early as possible in the upgrade process. I've almost made it to Django 1.6… 😅

thank you for your contribution we will update the docs

(and we will probably just move everything to Django 1.8, because 1.6 is really ancient)


[IOTDB-6218] Rename storage_query_schema_consensus_free_memory_proportion to datanode_memory_proportion

https://issues.apache.org/jira/browse/IOTDB-6218

We're currently processing your upload.  This comment will be updated when the results are available.


gpu_operator_wait_deployment: update to support new (>= v1.7.0) GPU Operator validator

When PR 217 will be merged in the GPU Operator, the master branch testing will fail as they are changing the way the operator internally validates its deployment.
This PR allows the testing of the old Pod-based validation and new DS-based validation, by checking if the ClusterPolicy has the .spec.validator.version stanza or not.
I tested this PR locally and it works as expected when everything is correctly deployed,
and it's also part of https://github.com/openshift-psap/ci-artifacts/pull/151 where I'm working with NVIDIA to getting the PR to work properly on OpenShift.
--
This PR can be merged independently of NVIDIA's, as it must work properly before (testing of versions < 1.7.0) and after the merge (testing of master+upcoming versions)

/test gpu-operator-e2e

/approve
On Wed, May 12, 2021 at 1:45 PM openshift-ci[bot] @.***>
wrote:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process
https://git.k8s.io/community/contributors/guide/owners.md#the-code-review-process,
please ask for approval from kpouget after the PR has been reviewed.
The full list of commands accepted by this bot can be found here
https://go.k8s.io/bot-commands?repo=openshift-psap%2Fci-artifacts.
Needs approval from an approver in each of these files:

OWNERS
https://github.com/openshift-psap/ci-artifacts/blob/master/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/155#issuecomment-839704894,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIQLIVY7N6XWVGRVF23TNJS3VANCNFSM44YN36YQ
.

/test gpu-operator-e2e

/test gpu-operator-e2e
On Wed, May 12, 2021 at 6:06 PM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following test failed, say
/retest to rerun all failed tests:
Test name Commit Details Rerun command
ci/prow/gpu-operator-e2e e67482b
https://github.com/openshift-psap/ci-artifacts/commit/e67482bed61534dbc221c8c4e4ecfe788bcf1a84
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/155/pull-ci-openshift-psap-ci-artifacts-master-gpu-operator-e2e/1392479276091052032 /test
gpu-operator-e2e
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=155.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/155#issuecomment-839900504,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQIQGFRPE2AUN3VSNDC3TNKROTANCNFSM44YN36YQ
.

/lgtm


Google Analytics

get GA tracking code
add to page

fixed by https://github.com/DevProgress/more-tacos/pull/75


Bump junit version to latest, 5.8.2

Codecov Report

Merging #64 (9de42ba) into master (f5f3347) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #64   +/-   ##
=========================================
  Coverage     72.95%   72.95%
  Complexity      444      444
=========================================
  Files            73       73
  Lines          1305     1305
  Branches        138      138
=========================================
  Hits            952      952
  Misses          319      319
  Partials         34       34

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 f5f3347...9de42ba. Read the comment docs.


Add flatten and join methods to Array class

Hi, I just added flatten and join methods to Array class. I'm not that fluent with golang yet, so I would really appreciate it if you would comment whatever crosses your mind.
Thanks! 😄

@shuheiktgw Thank you! It LGTM, I'm going to merge it.


substrate: support bare v5 extrinsics

resolves https://github.com/subsquid/squid-sdk/issues/348

Thank you!

@Tbaut already released! the fix is available in a transitive dependency so you need to execute the following command:
rm -rf node_modules/ package-lock.json && npm i

Amazing, thank you.


Add the JAL language as a full open-source PIC solution

JAL language has jalv2 as compiler and jallib as a collection of headers, libraries and examples for all PICs form PIC10 to PIC18.
See the web site http://justanotherlanguage.org/ where you can find the official package and some books and tutorials...
Repositories:
https://github.com/jallib/jallib
https://github.com/jallib/jalv2compiler

Thanks for your info.
JALV2/Jallib and related demo codes added to tutorial.
I tried to build a release archive from jallib sources (from git), but failed. thus use jallib-1.7.0 release archive directly, it should be OK since jallib release archive also contains all the source codes but flattened.


Ontologies loaded into the Minerva triplestores

Right now, the minerva triplestore seems to load only the gocam models but no ontologies.
This means that any SPARQL query requesting meta data on a GO term or a gene product will failed. Some ART queries are failing because of that (e.g. accessing the taxon of a gene or the subclasses of a GO terms)
Tagging @balhoff @kltm

That is correct, Minerva does not host ontology content apart from their tranformation into rules in Arachne.  Nor should it I expect.  We don't need another endpoint for the same content.  Perhaps you could run a distributed query to access the ontology content from rdf.go

For testing some of the stuff that @tmushayahama is trying to do in the short term, it may be useful to at least test with the ontology added on noctua-dev and see what we get. If federation is slow and the preferred path, it may be good to revisit exactly what it is slowing it down and trying optimize for the core of what we need.
@goodb To make sure that we can still get at the reactome entities, how hard would it be produce another merged ontology for Minerva that contained the additional ontologies? (At some point we should probably make it easier for Minerva to take multiple arguments.)

@kltm I'm not exactly following you here.  To answer your question, ontology merge is not hard and is nicely handled by robot.  But, I think modifying the import list that is the go-lego file that minerva eats for breakfast is a quite reasonable way to add whatever ontologies you like into the system (mainly meaning into Arachne).  If for modifications to the go-lego file were not allowed, it would also not be hard to modify the startup command line options to accept a list of ontology files as an input.

@goodb in theory, I would agree: that's the promise of federated queries. And that's a very cool concept that I want/hope to see evolve over time (e.g. our discussions with wikipathways people).
In practice however, I tend to avoid federated queries as much as I can for performance considerations, especially when we are the sole owner of the data. At the moment, the SPARQL queries for ART already takes too much time and the store contains only ~2200 models whereas we are aiming for hundreds of thousand.
In addition, it's a matter of consistency: both the snapshot and "end-user" production triplestores contain both NEO and GO, there is no real the "end-curator" production triplestore to be different. It's also not great for sharing optimized queries, which in SPARQL, can take some time design.
Tagging @cmungall on this and we can discuss it during the hackathon.

Note.  A use case from @tmushayahama is for the annotation review tool.  Populate type aheads in annotation review tool.  - I suggest this would best be handled by a dedicated, re-usable service that lives outside the Minerva context.  Of which several candidates already exist.

@goodb so just to clarify, the type aheads should have at least one model with it. in other words if that taxon_id is put in search it should give at least one result. So far in dev there are only 30 taxa out of many

Minerva now makes use of two internal triple stores.  One holds the models and their metadata, the other holds all information about ontology terms, including genes.  This other go-lego-triplestore is being used to handle much of the above.
Note that we are no longer intending to provide direct sparql access to either of these from the clients anymore.  All requests should come in via API (and internally will be rerouted to sparql or whatever else is needed to make it work).


Uncaught APIConnectionError in utils.py line 8159

Aider version: 0.60.0
Python version: 3.12.7
Platform: macOS-15.1-arm64-arm-64bit
Python implementation: CPython
Virtual environment: Yes
OS: Darwin 24.1.0 (64bit)
Git version: git version 2.39.5 (Apple Git-154)
An uncaught exception occurred:
Traceback (most recent call last):
  File "default.py", line 72, in map_httpcore_exceptions
  File "default.py", line 236, in handle_request
  File "connection_pool.py", line 216, in handle_request
  File "connection_pool.py", line 196, in handle_request
  File "connection.py", line 99, in handle_request
  File "connection.py", line 76, in handle_request
  File "connection.py", line 154, in _connect
  File "sync.py", line 152, in start_tls
  File "contextlib.py", line 158, in __exit__
  File "_exceptions.py", line 14, in map_exceptions
httpcore.ConnectError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1000)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "main.py", line 1586, in completion
  File "chat.py", line 1139, in completion
  File "http_handler.py", line 373, in post
  File "http_handler.py", line 356, in post
  File "_client.py", line 926, in send
  File "_client.py", line 954, in _send_handling_auth
  File "_client.py", line 991, in _send_handling_redirects
  File "_client.py", line 1027, in _send_single_request
  File "default.py", line 235, in handle_request
  File "contextlib.py", line 158, in __exit__
  File "default.py", line 89, in map_httpcore_exceptions
httpx.ConnectError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1000)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "aider", line 8, in <module>
  File "main.py", line 776, in main
  File "base_coder.py", line 730, in run
  File "base_coder.py", line 773, in run_one
  File "base_coder.py", line 1212, in send_message
  File "base_coder.py", line 1895, in auto_commit
  File "repo.py", line 110, in commit
  File "repo.py", line 195, in get_commit_message
  File "sendchat.py", line 46, in wrapper
  File "_sync.py", line 105, in retry
  File "sendchat.py", line 104, in simple_send_with_retries
  File "sendchat.py", line 85, in send_completion
  File "utils.py", line 1086, in wrapper
  File "utils.py", line 974, in wrapper
  File "main.py", line 2847, in completion
  File "utils.py", line 8194, in exception_type
  File "utils.py", line 8159, in exception_type
litellm.exceptions.APIConnectionError: litellm.APIConnectionError: AnthropicException - [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1000)

Thanks for trying aider and filing this issue.
This looks like a duplicate of #1756. Please see the comments there for more information, and feel free to continue the discussion within that issue.
I'm going to close this issue for now. But please let me know if you think this is actually a distinct issue and I will reopen this issue.


Add TryFromSliceError StdError helper

Instead of using map_err and StdError::generic_err to handle these errors, it would be nice to have an automatic handler for them, using thiserror [from] or similar.

I doubt we should do that. If we get into the business of converting every std:: error to an StdError we have a hard time and are never done. StdError means emitted in cosmwasm_std, so the conversion is misleading.
The now promoted conversion chain is StdError -> ContractError. A contract can then convert StdError -> ContractError as well as std:: error -> ContractError.
I'd love to see the specific use case in order to think about a different strategy to solve it.

Same as #1123
Agree unneeded

I have mixed feelings about the two convertest that exist:
impl From<std::str::Utf8Error> for StdError {
    fn from(source: std::str::Utf8Error) -> Self {
        Self::invalid_utf8(source)
    }
}

impl From<std::string::FromUtf8Error> for StdError {
    fn from(source: std::string::FromUtf8Error) -> Self {
        Self::invalid_utf8(source)
    }
}

On the one hand the argument above applies. On the other hand there is the specific error case StdError::InvalidUtf8 that we can convert into.

You are very right, this is a fundamental problem. StdError cannor handle everything beyond cosmwasm_std. But then there is StdResult used everywhere. And at the end of the day all errors are converted to string (or "generic error" aka. unstructured string) in order throw them around as if they were String exceptions. No idea how to solve this.

In cw-plus we use Result<Response, ContractError> everywhere, where the minimal ContractError looks like:
#[derive(Error, Debug, PartialEq)]
pub enum ContractError {
    #[error("{0}")]
    Std(#[from] StdError),

    #[error("Unauthorized")]
    Unauthorized {},
}

It is easy enough to extend inside a contract.
This comes up mainly in utility classes we define in cw-plus. Or more specifically in storage-plus.
Maybe we just make StorageError type? It really is package dependent...
(Not sure how much overhead this will add to the code)


0.x versions of Store and Publisher REST APIs need to be marked as deprecated

Description:
Currently both APIM 3.0.0 and the upcoming 3.1.0 are shipping with Store and Publisher REST API versions 1.x and 0.x. The versions less than 1(0.x), should be marked as deprecated as the recommended versions for use are the 1.x versions.
Currently there is nothing to indicate this to users in the docs and they might tend to use the 0.x versions unintentionally. So this needs to be highlighted clearly.
Content Positioning in Documentation:

Link: https://apim.docs.wso2.com/en/latest/develop/product-apis/restful-apis/

Fixed in -
https://github.com/wso2/docs-apim/pull/1135 | 3.0.0
https://github.com/wso2/docs-apim/pull/1137 | 3.1.0


Fix infinite loop in test_str_to_map_expr_random_delimiters

Fixes #10012.  test_str_to_map_expr_random_delimiters could infinitely loop if the data generator emitted two identical scalars.  Updated the test to use a custom data generator that only emits unique values.  Manually verified that the custom generator is retrying the underlying data generator for the specific DATAGEN_SEED value that originally triggered the infinite loop.

build

CI failed due to unrelated issue, filed #10017

build


Imprint text is missing

@vronk
On the info page, at the section imprint:
https://dhcr.clarin-dariah.eu/info#imprint
there was an imprint text shown.
Yesterday I noticed that it doesn't work any more. It loads the file specified below:
https://shared.acdh.oeaw.ac.at/acdh-common-assets/api/imprint.php?serviceID=7435
Do we need to update the link?

Yes, we need to update the link.
This should work by using https://imprint.acdh.oeaw.ac.at/7435
Check the doc of the imprint service:
https://github.com/acdh-oeaw/imprint-service

Implemented in 2024-07.
@IvdL22 @PixlTracer
Can you change the label to Done, if you agree?

@patrickakk Done, thanks


Is there a way i can test it out on my data on Google Colab?

Could you please provide a setup notebook to run this in Google Colab?

I'm also curious about this

I'm also curious about this

There is an implementation in the Colab mentioned in this blog post on huggingface:
https://huggingface.co/blog/autoformer


[23309] ERROR [405f9] duplicate entry for collection name

My Environment

ArangoDB Version:        3.7.2
Storage Engine:             RocksDB
Deployment Mode:       Cluster
Deployment Strategy:   ArangoDB Starter
Configuration:               3 nodes clustered
Infrastructure:               physical servers
Operating System:        RHEL 8.1
Total RAM in your machine:
Disks in use:
Used Package:

Component, Query & Data
Affected feature:

AQL query (if applicable):

AQL explain and/or profile (if applicable):

Dataset:

Size of your Dataset on disk:

Replication Factor & Number of Shards (Cluster only):

Steps to reproduce

restarted cluster with arabgod --starter.join=<IP1>:8528,<IP2>:8528,<IP3>:8528 --auth.jwt-secret=secert.jwt command to reset db connections
cannot start one of three cluster nodes with some errors, including collection name duplication, etc.

Problem:
cannot start one of three cluster node with these errors,
[23309] ERROR [405f9] duplicate entry for collection name 's12010684'. collection id 16010048 has same name as already added collection 14010063
[23309] ERROR [8d427] {engines} error while opening database: duplicate entry for collection name 's12010684'. collection id 16010048 has same name as already added collection 14010063
Expected result:

Was the cluster running and shut down normally? Is there any chance that a second collection with the same name was created while the cluster health was not okay, e.g. during a network partition? Can you share the server logs?
What was the configuration like, what replication factors and number of shards?
It would be great to get an agency dump or insight into what the current state is like. If only one of the nodes cannot join, could you try to add a fresh node (new database folder)?

Was the cluster running and shut down normally? Is there any chance that a second collection with the same name was created while the cluster health was not okay, e.g. during a network partition? Can you share the server logs?
What was the configuration like, what replication factors and number of shards?
It would be great to get an agency dump or insight into what the current state is like. If only one of the nodes cannot join, could you try to add a fresh node (new database folder)?

Hi Sirman,
The server doesn't have any event when I restart the cluster with Arango Starter (arangodb --starter.data-dir= --sterter.join=:8528,:8528,:8528 --auth.jwt-secret=)
the replication factor is 1 and when I tried to with a new database folder with arangodb Starter, it says 'ArangoDB Starter listening on <IP_ADDRESS>:8528" and nothing happen.

Hi Sirman,
The server doesn't have any event when I restart the cluster with Arango Starter (arangodb --starter.data-dir= --sterter.join=:8528,:8528,:8528 --auth.jwt-secret=)
the replication factor is 1 and when I tried to with a new database folder with arangodb Starter, it says 'ArangoDB Starter listening on <IP_ADDRESS>:8528" and nothing happen.

Hello,
Can I get some advice on how I can shut down the Arango cluster safely?  And use 'arangodb --starter.join=xxxxx:8528,yyyy:8528,zzzz:8528 --auth.jwt-secrete=jwt.sec' to make it alive.
And what happens if I shut down one of three cluster nodes by force? I think it should work even though they lost one of three nodes because it's clustered, right?
Thank you

Hi @spoh-ally ,
I will provide instructions through JIRA,
best Frank

Data corruption resolved through JIRA by joining a new starter with the two running nodes.


Member - copy member path from tab

Type: Bug
When right-clicking on an open member, there are two options that seem to have an issue
Copy Path
Copy Relative Path
Using these adds the wrong slashes \ instead of /.
Also noticing that the relative path behaves the same as the  other option (I'd think it would leave off the member name).
Using the option is convenient because the copied/clipboard information can then be used with the Ctrl+Alt+P feature to quickly find other members.
Thanks!!
Extension version: 2.10.1
VS Code version: Code 1.89.1 (dc96b837cf6bb4af9cd736aa3af08cf8279f7685, 2024-05-07T05:13:33.891Z)
OS version: Windows_NT x64 10.0.22631
Modes:

@jkdavew The two functions are provided by VS Code and not from this extension - and VS Code formats the path according to the OS you're running on. That's why slashes are converted to backslashes - because you're on Windows. On a Linux (and probably Mac) system the slashes are kept as slashes.
We may have a look into this - to see if we can change this behavior...

I don't believe there to be a way we can change this by default. Though, perhaps there is something in the FS API that allows us to force which slash to use.

Ahh, I see.  Since you may not be able to change that, could another context menu option be added: "Copy Member Path" and you'd have full control over that?

I'm sure there are many more important things to work on with this extension, but I found the following will work to allow for a new "Copy Member Path" context menu option when a member is open (when clicking on the tab, or in the source).
extension.js
	context.subscriptions.push(vscode.commands.registerCommand('code-for-ibmi.copy_member_path', function (input) { 		try{ 			vscode.env.clipboard.writeText(input.path.substring(1)).then(()=>{ 				vscode.window.showInformationMessage('Member path has been copied'); 			}); 		}catch(e){} 	}));
package.json (add "commands" and "menus" as a properties within the "contributes" property)
		"commands": [ 			{ 				"command": "code-for-ibmi.copy_member_path", 				"title": "Copy Member Path" 			} 		], 		"menus": { 			"editor/title/context": [ 				{ 					"command": "code-for-ibmi.copy_member_path", 					"when": "resourceScheme == member", 					"group": "1_copypath@1" 				} 			], 			"editor/context": [ 				{ 					"command": "code-for-ibmi.copy_member_path", 					"when": "resourceScheme == member", 					"group": "1_copypath@1" 				} 			] 		},


Enum options does not respect real Azure API values

There are sometimes some difference between enum options in specs and values which we have in API response.
For example, for storage ( https://github.com/Azure/azure-rest-api-specs/blob/master/arm-storage/2016-01-01/swagger/storage.json  ):
 "statusOfPrimary": {
          "readOnly": true,
          "type": "string",
          "description": "Gets the status indicating whether the primary location of the storage account is available or unavailable.",
          "enum": [
            "Available",             // Issue: Capital A
            "Unavailable"           // Issue:  Capital U
          ],
          "x-ms-enum": {
            "name": "AccountStatus",
            "modelAsString": false
          }
        },

but https://management.azure.com/subscriptions/[subscripbtionId]/resourceGroups/[resourceGroupName]/providers/Microsoft.Storage/storageAccounts/[storageAccountName]?api-version=2015-05-01-preview returns:
{
  "id": "/subscriptions/[subscriptiopnId]/resourceGroups/[res]/providers/Microsoft.Storage/storageAccounts/publicommons",
  "location": "West Europe",
  "name": "[storageAccountName]",
  "properties": {
    "accountType": "Standard_LRS",
    "creationTime": "2016-04-22T13:11:17.1629017Z",
    "primaryEndpoints": {
      "blob": "https://[storageAccountName].blob.core.windows.net/",
      "file": "https://[storageAccountName].file.core.windows.net/",
      "queue": "https://publicommons.queue.core.windows.net/",
      "table": "https://publicommons.table.core.windows.net/"
    },
    "primaryLocation": "West Europe",
    "provisioningState": "Succeeded",
    "statusOfPrimary": "available" // Issue: only lowercase letters
  },
  "tags": {},
  "type": "Microsoft.Storage/storageAccounts"
}

To have Available as Enum option and available in the response value makes difficulties with deserialization in case-sensetive languages.

Same situation we have with Compute (https://github.com/Azure/azure-rest-api-specs/blob/822b51ed9d19cb79f6684220cca21b673f804bb7/arm-compute/2016-03-30/swagger/compute.json). Azure API Response:
"osDisk": {
        "osType": "Linux",
        "name": "TestImageVMCentOS",
        "createOption": "FromImage", // Issue here
        "vhd": {
          "uri": "https://dsvmssa2.blob.core.windows.net/vhds/TestImageVMCentOS201623011657.vhd"
        },
        "caching": "ReadWrite"
      },

But in the spec :
"createOption": {
          "type": "string",
          "description": "Gets or sets the create option.",
          "enum": [
            "fromImage", // Issue here
            "empty",
            "attach"
          ],
          "x-ms-enum": {
            "name": "DiskCreateOptionTypes",
            "modelAsString": false
          }
        }

Hi @ivanignatiev
We(Storage) already fixed this issue since api version 2016-05-01, please refer to newest version for the updated spec:https://github.com/Azure/azure-rest-api-specs/blob/master/arm-storage/2016-12-01/swagger/storage.json#L751

Cleaning up old issues from 2016 - 2018. Please reactivate this if it is still a problem.


Authentication and 'Try it out'

Hi,
There is auth devise in the app and before_filter :authenticate_user! is applied to the action which I want to achieve by 'Try it out'. Is it possible to authenticate before calling 'Try it out'?
Many thanks.

I think you are asking a question about Swagger UI, which is not this project. Please see https://github.com/fotinakis/swagger-blocks#filing-issues


Use the right native and foreign SVs in the index

In the index today, we do not have SV for "US native population" (nativity=Native).  What exists is "US natives born outside US".  So fix that.
Also, for "foreign born population", we have placeOfBirth=ForeignBorn, rather than nativity=ForeignBorn.  This makes comparing against native population not entirely accurate (esp considering nativity has a dpv of >5 years).
So, this PR makes the following replacements in the SV index:

Count_Person_ForeignBorn => Count_Person_5OrMoreYears_ForeignBorn
Count_Person_NativeBornOutsideTheUnitedStates => Count_Person_Native

Diffs are clean - https://storage.mtls.cloud.google.com/datcom-embedding-diffs/shanth_medium_ft_2024_01_10_17_44_39.html - except for a "use electricity" change that I'm not fully sure (will poke some more).

Thanks!
Regarding the Electricity topic diff, it's not a real diff. See: https://screenshot.googleplex.com/BQcBuyxgW37F4u6 and notice the top SV in all these three topics is the same (hence, the same top matching score). So I bet it's randomly changing the order of the topics here. We should probably figure out if these three topics are different enough or could be collapsed somehow?

Nice, thanks for finding that!

Thanks!
Regarding the Electricity topic diff, it's not a real diff. See: https://screenshot.googleplex.com/BQcBuyxgW37F4u6 and notice the top SV in all these three topics is the same (hence, the same top matching score). So I bet it's randomly changing the order of the topics here. We should probably figure out if these three topics are different enough or could be collapsed somehow?

Sorry missed addressing the question.  I think we should sort deterministically.  While not ideal, we do have the same concept represented by different SVs/topics, where different SVs have data for different places (US vs. global vs. SDG).  We could merge, but it would also be subject to #svs we open up for performance.
I've filed b/319546168 for follow up.


boards: Fix 2 liners copyright

Convert 2 lines copyright before this new format starts creating
the new in vogue style.
Signed-off-by: Erwan Gouriou<EMAIL_ADDRESS>

@Nukersson I initially thought this format was required because it didn't fit into the 80 lines, but this is not the case.
So, let's convert to usual format before this starts creeping in (as seen here).


digdag-ui: reduced flow errors

npm run flow found 32 errors.
I resolved 17 of them.
I also have some questions related this PR.

What do you think about flowtype?

These errors seem to be left for a long time.
Type errors are not checked in CI.

Can I update flow-bin?

VSCode plugin doesn't work because installed flow-bin is extremely old

On the other hand, newer flow-bin will find more than 100 errors in this project.

Do you have any plan to change over to TypeScript?

Flow seems to prioritize Facebook internal usage.

Thank you for creating this PR!

What do you think about flowtype?

To be honest, it's been around for a long time, and I don't know the background on the use of flowtype, so I couldn't comment from an accurate position.

Can I update flow-bin?

Feel free to update it, but it will be hard to fix the errors, though.

Do you have any plan to change over to TypeScript?

My understanding is that there has never been a clear plan to change to TypeScript. In my opinion, migrating to typescript is a better choice than trying hard to upgrade/maintain flow. Let me create an issue for that.

@szyn
Thank you very much for your honest comment.

Let me create an issue for that.

Thank you. Describing as an issue makes community to be able to improve it.

I resolved conflict rebasing branch.
Correcting types will also help migration.


inject failures for read pool

Previously proposed in https://github.com/pingcap/tikv/pull/2713
It would be nice to use failure injection to cover some error conditions (like snapshot failed).

@brson
maybe we need to add a doc about how to use fail-rs to let contributors use fail.

Closed in https://github.com/tikv/tikv/pull/4376


"Let's Encrypt" catalog service spinning very rapidly

Rancher Version: 0.63.1
Docker Version: 1.10.3
OS: Ubuntu 14.04.4 LTS on DigitalOcean
Steps to Reproduce:

Create a "Let's Encrypt" service from the catalog with the following options:

"I Agree to the Let's Encrypt TOS": "yes"
"Let's Encrypt API version": "production"
"Email address": valid email address
"Domain names": enter three comma-separated domain names handled by your DigitalOcean account
"Public Key Algorithm": "RSA-4096"
"Renewal Time of Day": "5"
"DNS Provider": "DigitalOcean"
"DigitalOcean API Access Token": valid DO API token

Results: Container attempts to start and dies on a repeating interval of about 2 seconds. Log:
3/18/2016 8:27:04 AMlevel=info msg="Starting Let's Encrypt Certificate Manager v0.2.5 a31b992"
3/18/2016 8:27:04 AMlevel=info msg="Generating private key (4096) for<EMAIL_ADDRESS>3/18/2016 8:27:07 AMlevel=info msg="Creating Let's Encrypt account for<EMAIL_ADDRESS>3/18/2016 8:27:08 AMlevel=info msg="Trying to obtain SSL certificate for rancher.r24y.net | project.r24y.net | git.r24y.net"
3/18/2016 8:27:09 AMlevel=error msg="[rancher.r24y.net] Failed to obtain certificate: Error presenting token HTTP 404: not_found: The resource you were accessing could not be found."
3/18/2016 8:27:09 AMlevel=error msg="[project.r24y.net] Failed to obtain certificate: Error presenting token HTTP 404: not_found: The resource you were accessing could not be found."
3/18/2016 8:27:09 AMlevel=error msg="[git.r24y.net] Failed to obtain certificate: Error presenting token HTTP 404: not_found: The resource you were accessing could not be found."

Expected: Let's Encrypt service would run.

Any templates from our Community Catalog is contributed and maintained by our community. Rancher will not be maintaining those templates. Please feel free to add your issue in the community and ping the owner who contributed it.


No "Edit Model" button on web.blockbench.net

I would like to use the Minecraft Entity Wizard plugin with the web app at web.blockbench.net. The tutorial mentions that this is a supported configuration, and also says that there should be an "Edit Model" button on the last page of the wizard. However that button does not appear on the web app. So there doesn't seem to be any way to use this wizard to create new entities based on existing Minecraft entities using the Minecraft Entity Wizard via web.blockbench.net. Would it be possible to add this feature?

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

ID: 79c7652f-5c4e-768c-ca52-1ac2ff1790f5
Version Independent ID: 794cb3ed-7c30-59af-7d62-3f109de1d553
Content: Getting Started with Minecraft Entity Wizard
Content Source: creator/Documents/MinecraftEntityWizard.md
Product: gaming
GitHub Login: @v-josjones
Microsoft Alias: v-josjones

We've passed this feedback along to the Blockbench team. For assistance on that product and any feature requests, I'd recommend you visit their site here: https://www.blockbench.net/ or their Github repo here: https://github.com/JannisX11/blockbench
Closing this issue as this Github is for logging issues specific to the documentation on our site.


Regression test fixes

The biggest fix is that the tests are now cleaning up after themselves which currently blocks RHEL CI.
This pull request includes:

[ ] adequate testing for the new functionality or fixed issue
[ ] adequate documentation informing people about the change such as

[ ] submit a PR for the guides repository if this PR changed any behavior described there: https://www.osbuild.org/guides/

I forgot to set -s when calling composer-cli delete in regression-old-worker-new-composer.sh. Force-pushed a fix.